Microsoft Dynamics 365 is not a standalone application. Somewhere there’s an online store, a WMS, a shipping account, a CRM that the sales team refuses to leave, and EDI files from a big-box customer. Everyone needs the data that the ERP, the Enterprise Resource Planning system, has, and each of those third-party apps must stay in sync with it.
Methods of Microsoft Dynamics 365 Integration
The REST API (v2.0)
Business Central has three kinds of web services: REST API, OData, and SOAP. Microsoft clearly states that REST is preferred and that REST and OData are both based on OData version 4. The same page says its endpoints will be removed in a later release. SOAP is on the way out.
For Business Central online, in the cloud, API (v2.0) is enabled by default, so this is the fastest way to begin using it. One early limitation: Microsoft says it can’t extend the standard APIs to include extra fields, for now. If you need a field that the built-in customer or item API does not expose, you create a custom API page or API query in AL, and Microsoft’s guidance is to always set ODataKeyFields = SystemId. However, without a single GUID key, some integrations, such as Power Automate and Power Apps, will not work with it.
After October 1, 2022, the old basic auth option, access keys, no longer worked for online tenants, and OAuth 2.0 became the only option.
The OData and Batch APIs
The finance and operations apps expose data entities that flatten the underlying tables to a business concept, so “Customer” comes over as one thing, not four joined tables. You can flag each to be used as a public API, for data management purposes, or both.
That flag is the key decision point, and Microsoft’s integration overview clearly indicates the recommended path. OData is synchronous, not batch. The batch data API is asynchronous and built for volume. For more than a few hundred thousand records, use the batch data api.
Microsoft’s worked examples show that product creation and updates occur at about 1,000 records per hour on OData, while sales order imports occur at about 200,000 records per hour on the batch API.
The OData here is at {root}/data and has some limitations worth knowing before you commit: $expand only supports first-level expansion, the has and in operators are unsupported, and OData actions added via extensions are also unsupported. Unless you pass cross-company=true, queries return only the user’s default company.
There is the REST API data management package and recurring integrations for bulk work. They differ in where the schedule lives. Two details are important: ImportFromPackage runs a batch job and must not be called on parallel threads; exported blobs are deleted after seven days.
Webhooks and Business Events
Polling the ERP to see if anything has changed does not scale well. Business Central has support for API subscriptions, which are webhooks. The important number is three. Subscriptions are valid for three days, unless you renew them.
The system waits 30 seconds after the first change before informing you. If more than 1,000 records change in that time, you get one collection notification instead of many. Retry only on 408, 429, and 5xx responses over 36 hours.
Business events are used in Finance and Supply Chain Management, triggered by workflow actions such as a purchase requisition approval and non-workflow actions such as a purchase order confirmation.
Microsoft is clear that these are not a data export mechanism, are not designed to carry large payloads, and do not guarantee delivery order. The endpoints are Azure Service Bus, Event Grid, Event Hubs, Blob Storage, HTTPS webhooks, Power Automate, and Dataverse. The Azure endpoints are created in your own subscription and may incur costs.
Power Platform, Azure, and EDI
Automated flows on record creation, modification, and deletion. For lighter workflows, Power Automate is the low-code path, a powerful tool for simple flows. One caveat for teams that are already using Business Central: The Business Central connector currently doesn’t support service-to-service, service principal, or managed identity authentication.
Azure Integration Services has the answer for anything with real traffic. Microsoft’s general integration guidance mentions Logic Apps, Service Bus, Functions, and Azure Synapse Link and notes that high-frequency flows (e.g., ecommerce) might require more robust real-time integration.
Electronic Data Interchange itself is a gap. Microsoft’s e-invoicing FAQ states, “By default, electronic invoicing does not send the output file directly to the customer as an EDI transaction.” In its outbound-goods reference architecture, it routes orders through a partner EDI platform and describes itself as EDI partner agnostic.
Third-Party Integration Platforms
It’s not a competing method. It’s how most companies run the ones above. An integration solution. A platform such as DCKAP Integrator still talks to Business Central using API v2.0 and to the finance and operations apps using OData and business events. What it does remove is authentication, field mapping, retries, scheduling, error alerting, throttling logic, and the endpoint changes that come with each release wave.
The scope is the delta to Microsoft’s own tooling. Dataverse and the Power Platform, like other Microsoft solutions, bring data to the Microsoft ecosystem. The entire landscape is built around the ERP-first platform, because a distributor runs a CRM, an ecommerce platform, a PIM, and logistics with the ERP as the source of truth.
| DCKAP Integrator | Power Automate and Azure Logic Apps | |
| Core focus | ERP integration for distributors and manufacturers | General workflow automation across Microsoft and third-party apps |
| eCommerce sync | Prebuilt flows for Adobe Commerce, BigCommerce, Shopify, and deep ERP <> ecommerce integration experience | Built flow by flow from available connectors |
| Distribution logic | Contract pricing, multi-warehouse inventory mapped from the start, customization possible for unique needs | Configured by your team |
| Who builds it | DCKAP integration experts, with low-code tools for your team | Your IT team, a power user, or a Microsoft partner |
| Ongoing monitoring | Included from DCKAP’s team | Managed by your team |
| Pricing | Based on the number of systems, pipes and extent of customizations | Per user, per flow, or per run, depending on plan |
Integration Use Cases
Online store to ERP
Business Central has a first-party connector for Shopify that synchronizes items and customers in both directions and imports orders from the online store, Shopify POS, and B2B channels, including shipping costs, payment terms, and refund information. It gets Shopify Payments payout data. That same flow operates on APIs for other ecommerce platforms.
Real-time inventory across channels
Inventory Visibility is a first-party microservice built on Dataverse that provides real-time visibility of on-hand postings across data sources like 3rd-party ERP systems, POS, and WMS, which are integrated via REST APIs. Soft reservations are in place to prevent overselling via channels.
An external CRM is integrated with the ERP
Many distributors run CRM systems like Salesforce or HubSpot instead of Microsoft’s own apps for customer relationship management, Sales, Customer Service, and Field Service.
The reads are simple via API v2.0 or OData. The direction is the most challenging part. Contact information and quotes are in the CRM, close to the customer relationships that create them. Credit terms, pricing, and order status are in the ERP.
Lead generation tools like LinkedIn Sales Navigator and a team’s marketing efforts feed the CRM first, and only qualified leads that convert need to reach the ERP.
Reporting and business insights
Power BI reports are built into Business Central pages. As of October 2023, Microsoft has deprecated Export to Data Lake. Existing users can continue to use it until November 1, 2024.
For organizations already on Fabric, Microsoft now recommends Link to Fabric and Azure Synapse Link; otherwise, Edit in Microsoft Excel publishes changes back, while Open in Excel does not, and records shared to Microsoft Teams become interactive cards closer to the desk, tying the Microsoft products your team already uses back to the ERP.
Across all of them, the business insights are only as trustworthy as the underlying data quality, since a report is only as good as the raw data feeding it, so the right people see numbers they can trust.
Best Practices for Dynamics 365 Integration
- Design for throttling from the start. Finance and operations apps reply with 429 with a Retry-After header in seconds that grows if a client keeps calling. In Business Central, documented ceilings are a maximum of five concurrent requests, 100 operations per batch, and a page size of 20,000 entities. The maximum execution time is 10 minutes.
- Rate your integrations. With priority-based throttling, you assign a low, medium, or high priority to each Entra app or user. This means that a nightly catalog push is throttled before order intake is.
- Identify the owning system of each field. The customer data is stored in both the CRM and the ERP system. Map and enforce it in one direction only. Agree on authority for addresses, credit terms, and pricing before mapping. Bidirectional sync on an ownerless field leads to a loop.
- Credentials are narrowly defined. Provide each integration with its own Entra application and only the API scopes it requires. Never share an admin account. A CRM sync that only reads customers and writes orders has no business touching payroll or general ledger, and a tightly scoped credential reduces the blast radius if one ever does get leaked.
- Don’t reflexively automate everything. Microsoft’s WMS inventory balance architecture points out that the majority of WMS providers, including Manhattan, do not recommend the automation of inventory balance. There has to be some human intervention.
- Test error handling at real volumes.” Broken production: duplicate records, partial failures in the middle of the sequence, and empty required fields are not the happy path you gave us in the demo. That’s where a platform like DCKAP Integrator can help, exposing failed syncs via detailed loggers and email alerts before a missing order turns into a customer support call.
Why Choose DCKAP For your 365 Integration Needs
DCKAP’s ERP-first integration platform is built specifically for distributors and manufacturers, ensuring that their ERP is placed at the very core of their entire operations. Packed with robust features, new AI functionalities, and a fully managed model, the platform is customized to specific needs, while ensuring critical systems talk to each exactly as needed.
Plumbing Distributors Inc. ran Shopify Plus against Epicor Eclipse and decreased the sync time for 15,000 records from about 1.5 hours to around 5 minutes. Action Spa Parts, on Distribution One, cut order processing time by up to 95%. No need for an internal integrations team; a dedicated team of experts handles integrations.
Reasons why users choose DCKAP include:
1. You skip the build
DCKAP’s team scopes, builds, tests, and monitors your integrations. You get working connections without staffing a Power Platform specialist.
2. Distribution logic comes included
Customer-specific pricing, contract catalogs, units of measure, and stock across warehouses are already mapped. A general tool has to learn all of that from scratch.
3. Your storefront matches your ERP
Prices, inventory, and order status flow between Dynamics 365 and your eCommerce site. B2B buyers see accurate data every time they log in. Orders land in Dynamics without rekeying.
4. One platform for every connection
Connect Dynamics 365 to eCommerce, CRM, PIM, EDI, and marketplaces from one place. You manage one vendor instead of a pile of separate flows.
5. Updates don’t break your business
Microsoft ships frequent updates to Dynamics 365. DCKAP’s team keeps your integrations running through them, so you don’t rebuild after each release.
Conclusion
Microsoft Dynamics 365 third-party integration isn’t a one-project-one-answer situation. Business Central has API v2.0, custom API pages, and webhook subscriptions. Finance and Supply Chain Management has OData for real-time work, a batch data API for volume, custom services for logic, and business events for notification.
Check which app and version you are on. Match the method to the size. Select owners for each plot of land. “Plan to throttle before it plans for you.” You can either build against the APIs or let a platform like DCKAP Integrator handle it with pre-built connectors and custom solutions.
FAQs
Why Businesses Integrate Dynamics 365 With Third-Party Applications
To prevent retyping data between systems. The most vocal example is order entry, where manual data entry of a web order that arrived by email adds labor costs across business operations and invites human error. Next is inventory, as the ERP has the stock, and the ecommerce platform, marketplace listing, and WMS all pull from their own copy. One-third is reporting.
Does Dynamics 365 include a built-in EDI capability?
No. Microsoft has no EDI translator in the finance and operations apps; its e-invoicing service doesn’t send output files directly to customers as EDI transactions, and its outbound-goods architecture routes orders through a partner EDI platform.
Should I use OData or the batch data API for Finance and Supply Chain Management?
Volume decides. Microsoft recommends the batch data API past a few hundred thousand records and OData for synchronous, lower-volume work.
Do I need to replicate ERP data in Dataverse to build a Power App?
Not for finance and operations apps. Virtual entities expose all OData entities in Dataverse with full CRUD and no data copied, and Business Central has equivalent virtual tables. Dual-write is for when data must persist on both sides.
