Power Automate connects to Dynamics 365 and Business Central through Premium connectors, which require a standalone Power Automate licence — that is the first fact to establish, because it decides which of these ten workflows are worth building at your headcount.
Licensing, before design
Both the Microsoft Dataverse and Business Central connectors are classified as Premium. Teams routinely prototype against them on a trial, demonstrate something impressive, and then discover the per-user cost of rolling it out.
Establish the licence position first. It frequently changes the design — for instance toward a smaller number of service-principal-owned flows instead of per-user automations.
The three Business Central triggers
| Trigger | Fires on | Use it when |
|---|---|---|
| When a record is created (V3) | Row insert | New entity needs downstream provisioning. |
| When a record is modified (V3) | Any field change | Rarely — it fires far more often than you expect. |
| When a business event occurs (V3) | A defined business event | Almost always. It fires on meaning, not on a row changing. |
The modified trigger is the usual cause of a flow that runs thousands of times a day and does nothing useful in most of them. Prefer business events wherever one exists.
Ten workflows worth building
| Workflow | What it does |
|---|---|
| Purchase order approval routing | Threshold-based approval cards in Teams and Outlook, escalating by value. |
| Vendor invoice extraction | AI Builder reads PDF attachments into draft ledger entries for human approval. |
| Reorder point alerts | Warns procurement before a stockout instead of reporting one afterwards. |
| Exchange rate and statement sync | Pulls daily rates and bank statements into the financial ledgers. |
| Credit limit holds | Places a sales order on hold automatically when a customer exceeds their limit. |
| Daily executive digest | Revenue, cash position and margin delivered to Teams each morning. |
| Onboarding provisioning | Creates the Entra ID and ERP accounts and assigns roles from one request. |
| Carrier tracking sync | Polls logistics APIs and writes tracking back onto the sales order. |
| E-commerce stock balance sync | Keeps storefront availability aligned with warehouse stock. |
| Tax document archival | Generates compliant tax invoice PDFs and files them to SharePoint. |
Note what they have in common. Each moves information or routes a decision to a person. None of them decide anything on their own. That is not timidity — it is the pattern that survives contact with a finance team.
Three rules for running them
- Service principals, not people. A flow owned by an employee stops the day their account is disabled, usually discovered a week later.
- DLP boundaries per environment. Development flows must not be able to reach production connectors. This is configuration, and it is the cheapest control in the platform.
- Failure has to be visible. A flow that fails silently is worse than no flow, because people have stopped doing the manual step it replaced.
Automation earns its keep by removing the re-keying, not the thinking. The flows that last are the ones that put the right item in front of the right person with everything needed to decide.