What we do
Tools
Industries
Department
How we workLet's talk →
Home/Dynamics 365/Dynamics 365 Integrations Outside Microsoft
Microsoft Dynamics 365

Dynamics 365 Integrations With the Systems Microsoft Doesn't Make

Your Dynamics partner set up Outlook, Teams and Power BI in an afternoon. Then someone asked for the web store's orders, the warehouse system's shipments and the old CRM's history, and the estimate came back in weeks. Inside Microsoft's stack, Dynamics 365 comes pre-wired. Outside it, each app has its own API, and the work depends on which one you run.

The integration surface of each Dynamics 365 app

The short version of each app's interface. For endpoints, auth and versions, see the Dynamics 365 API page.

If you run Integrations go through Worth knowing
Sales, Customer Service, Field Service or other customer engagement apps The Dataverse Web API, an OData v4 REST interface, and the Microsoft Dataverse connector in Power Automate. Every table you customize shows up in the Web API too, so custom fields don't need a separate interface.
Business Central The Business Central API v2.0, custom API pages, webhooks on API entities, and the Dynamics 365 Business Central connector. Microsoft's docs note the Power Automate connector doesn't support service-to-service authentication, so flows run on a user's connection.
Finance, Supply Chain Management (Finance and Operations apps) OData over public data entities, the Data management framework for bulk imports and exports, business events, and the Fin & Ops Apps connector. Data entities, not tables, are the unit. If the entity you need isn't public, it has to be extended before anything outside can reach it.
Finance and Operations plus a customer engagement app Dual-write, which keeps F&O and Dataverse in near real-time sync both ways. It only joins Microsoft's own apps. A third system still needs its own integration to one side or the other.

Power Automate flow or a coded integration?

A Power Automate flow

When the job is small and Microsoft-shaped

  • A trigger in Dynamics 365 and a handful of steps, like posting a Teams message or saving a file to SharePoint.
  • Low volume, where the odd retry or delay is fine.
  • The other system has a certified connector, or a simple HTTP call does the job.
A coded integration

When records have to stay correct in both systems

  • Orders, invoices, stock or customer records moving at volume, both ways.
  • Matching rules, duplicate checks and field mapping that would turn a flow into a maze.
  • A system with no connector, where the logic sits against the Dataverse, Business Central or F&O API directly.

Plenty of setups use both: flows for notifications and small handoffs, a coded integration for the records the business runs on.

The bridge you need while a migration is still running

A lot of Dynamics 365 integration work is temporary. A company moving from an older CRM or an on-premises ERP rarely cuts over in one weekend, so for weeks or months both systems have to agree on customers, open orders and balances while teams move across in stages.

That bridge has a start and an end date, and it has to cope with both sides changing as the migration goes. n-frames builds it to run until the last team switches, then retires it, and builds the permanent connections that should stay once Dynamics 365 is the system of record.

Integration choices that come back to bite after go-live

A Business Central flow running on one employee's login

How you'll know: Orders stop syncing the week that person leaves or changes their password.

Fix: Use a dedicated integration account for flows, or build the sync as a service with its own registered app and permissions.

Polling F&O for changes every few minutes

How you'll know: Slow data entity calls and throttling at busy times.

Fix: Subscribe to business events where they exist, and move bulk loads to the Data management framework instead of record-by-record OData calls.

Expecting dual-write to reach a third system

How you'll know: F&O and Dataverse agree, but the web store or WMS still shows stale data.

Fix: Dual-write only joins Microsoft's apps. Pick one side as the source for each record and integrate the third system with that side only.

One integration assumed to cover every Dynamics 365 app

How you'll know: A connector bought for Sales doesn't work once Business Central arrives.

Fix: Each app has a different API. Plan the integration per app, even when the vendor sells them all as Dynamics 365.

Dynamics 365 integration questions

Does Dynamics 365 integrate with SharePoint?

Yes, and it's built in. Dynamics 365 records can store and open their documents in SharePoint, and setup is one of the better-supported connections in Microsoft's stack. Business Central and Finance and Operations have their own document options as well.

Can I integrate a non-Microsoft CRM with Office 365?

Depends on the CRM. Many larger ones maintain their own Office 365 connector for email and calendar sync. Smaller or industry-specific CRMs often don't, and that's where a build against Microsoft Graph comes in.

What software integrates with Dynamics 365 Finance and Operations for accounts receivable?

Several AR automation and collections platforms list purpose-built connectors for Finance and Operations, but coverage varies by vendor and version. If yours doesn't have one, n-frames builds the link through F&O's data entities and business events, so invoices, payments and dunning status stay current on both sides.

Is there one Dynamics 365 integration tool that works for everything?

No. Sales and the other customer engagement apps sit on Dataverse, Business Central has its own API, and Finance and Operations works through data entities. A tool that handles one well may not touch another, so check which app a connector actually supports.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.