Power Automate connectors for Dynamics 365
The standard and premium Power Automate connectors for Dynamics 365 — what each one does, the differences, and the licensing implications.
Power Automate connectors are the bridges between flows and other systems. For Dynamics 365 customers, several connectors matter — and the difference between standard and premium connectors is important for licensing and capability.
Microsoft Dataverse connector. The right connector for any CRM-side D365 app (Sales, Customer Service, Field Service, Project Operations, Customer Insights, Power Apps with Dataverse). Triggers on row created/updated/deleted/added; actions for full CRUD, executing actions, file uploads, and relating records. Supports filtering and column selection. Premium connector — flows using it require a Power Automate per-user or per-flow licence beyond what's included with most Dynamics 365 SKUs.
Common Data Service (current environment) connector. The older name; functionally equivalent and being phased out in favour of "Microsoft Dataverse". Still appears in older flow templates.
Dynamics 365 connector (legacy). An older connector for CRM-side apps, predating Dataverse-native. Microsoft recommends migrating to the Dataverse connector.
Dynamics 365 Business Central connector. First-party. Triggers and actions for Customer, Vendor, Item, Sales Order, Purchase Order, Sales Invoice, Sales Quote, Journal Lines, Locations, and many more. Standard CRUD and bound actions for posting, releasing, and cancelling documents. Premium.
Dynamics 365 Finance and Operations (legacy) connector. Targets F&O data entities. Premium.
Dynamics 365 for Fin & Ops (Recurring Integrations). A separate connector that targets the recurring integration API for batched data project imports/exports.
Custom connectors. When the first-party connector doesn't expose what you need, build a custom connector from an OpenAPI/Swagger definition. Custom connectors are premium and use the same authentication and policy framework as built-in ones.
Licensing. This is where teams get caught out. A flow that uses only standard connectors (SharePoint, Outlook, Teams, Office 365) can run on the free Power Automate licence bundled with M365. A flow that uses a premium connector — Dataverse, Business Central, F&O, SQL Server, HTTP, custom connector — requires a premium Power Automate licence on the flow owner. Per-user (one user, unlimited flows) or per-flow (one flow, unlimited users) plans are available. Most Dynamics 365 SKUs include limited premium Power Automate rights, often labelled "Power Automate for Dynamics 365" — these allow flows that are directly related to the licensed Dynamics 365 app, but not arbitrary Power Automate use.
Throttling. Each connector has request limits per user per 24h, plus shorter spike limits. Bursty flows can hit the limits and produce HTTP 429s. Throttle limits are documented per connector; the most common D365 connector limits are generous but real.
The pattern. For any non-trivial flow involving Dynamics 365, plan: which premium connectors does it call, who owns it, what licence does the owner have.
Related guides
- Azure API Management in front of DataverseHow API Management acts as a façade for Dynamics 365 APIs — rate limiting, authentication, transformation, observability, and developer portal — and why it matters at scale.
- B2C authentication with Dynamics 365 — Entra External ID and beyondHow to authenticate external customers and partners against Dynamics 365 — Entra External ID (formerly Azure AD B2C), Power Pages authentication, and the patterns for B2C identity in CRM and ERP.
- Batch operations in the Dataverse Web APIHow to make multiple Dataverse Web API calls in one HTTP round-trip — $batch requests, change sets, and the performance gains at scale.
- Entra External ID for customer accessHow Microsoft Entra External ID provides customer-grade identity for Power Pages portals and external Dynamics 365 access — sign-up flows, branding, social identity, and the migration from Azure AD B2C.
- FetchXML vs OData in DataverseTwo query languages for Dataverse — what each does, performance and capability differences, and when to choose which.