# D365 Finance and Supply Chain Integration Interface Register > Source: https://netray.co/tools/d365-fo-integration-interface-register > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable interface inventory for D365 F&O with pattern, direction, frequency, volume and owner, summing daily message volume. ## Category microsoft-dynamics ## Erp Microsoft Dynamics 365 Finance and Supply Chain ## Audience - Integration architect - D365 F&O technical consultant - Project manager ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Interface ID **Key:** id **Type:** text #### Interface **Key:** name **Type:** text #### External system **Key:** system **Type:** text #### Direction **Key:** direction **Type:** select **Options:** - Inbound - Outbound - Bidirectional #### Pattern **Key:** pattern **Type:** select **Options:** - OData - Custom service - Data management package - Business events - Dual-write - File drop (SFTP) - Power Automate - Azure Synapse Link #### Runs per day **Key:** freq **Type:** number #### Records per run **Key:** msgs **Type:** number #### Records per day **Key:** daily **Type:** number **Expr:** freq * msgs **Format:** integer #### Owner **Key:** owner **Type:** text #### Criticality **Key:** criticality **Type:** select **Options:** - High - Medium - Low **Rows:** #### Customer orders from e-commerce **Id:** INT-001 **System:** Web shop **Direction:** Inbound **Pattern:** OData **Freq:** 96 **Msgs:** 15 **Owner:** Integration team **Criticality:** High #### Inventory availability to portal **Id:** INT-002 **System:** Customer portal **Direction:** Outbound **Pattern:** Business events **Freq:** 288 **Msgs:** 5 **Owner:** Integration team **Criticality:** Medium #### Bank statements import **Id:** INT-003 **System:** Bank **Direction:** Inbound **Pattern:** File drop (SFTP) **Freq:** 1 **Msgs:** 400 **Owner:** Treasury **Criticality:** High #### Shop floor production reporting **Id:** INT-004 **System:** MES **Direction:** Bidirectional **Pattern:** Custom service **Freq:** 480 **Msgs:** 3 **Owner:** Manufacturing IT **Criticality:** High #### Product master sync **Id:** INT-005 **System:** PLM **Direction:** Inbound **Pattern:** Data management package **Freq:** 4 **Msgs:** 120 **Owner:** Engineering **Criticality:** Medium **Totals:** #### Interfaces **Key:** id **Agg:** count **Format:** integer #### Total records per day **Key:** daily **Agg:** sum **Format:** integer #### Largest interface per day **Key:** daily **Agg:** max **Format:** integer **Summary:** #### Average records per interface per day **Key:** avg_daily **Expr:** sum_daily / count **Format:** integer **Notes:** Add error handling, retry, monitoring and authentication details in extra columns after export. Check current Microsoft service protection limits and API throttling guidance for your version when sizing high-volume interfaces. ## Content **Intro:** Every D365 Finance and Supply Chain project underestimates integrations at the start. An interface register lists each connection, pattern and owner in one place, so effort, risk and monitoring are planned rather than discovered. **Sections:** #### How to use the register **Body:** Add one row per interface and direction. Pick the integration pattern that fits: OData for real-time record-level access to data entities, custom services for specific logic, the data management framework for bulk package import and export, business events for outbound notifications, dual-write for Dataverse synchronization, file drops for legacy partners, Power Automate for lightweight flows, and Azure Synapse Link for analytics. Enter runs per day and records per run to see daily volume. **Bullets:** - One row per interface and direction - Record the owner on the business side too - Rate criticality to plan monitoring and support - Use the volume column to spot throttling risk #### Choosing a pattern **Body:** Use bulk patterns for large, scheduled volumes and record-level APIs for interactive, low-volume exchange. Real-time chatty OData calls from external systems can run into service protection throttling, so batch where you can. Prefer standard data entities over custom services if they cover the need, because they are maintained through updates. Avoid direct database access, which is not supported in cloud-hosted production. #### What to capture beyond the basics **Body:** For each interface, extend the register with authentication method (Microsoft Entra ID app registration), error handling and retry, monitoring and alerting, data owner, test approach and cutover behavior. Decide who is called at night when it fails. These operational details are what turn a working integration into a supportable one. #### Common mistakes **Body:** Frequent problems are missing interfaces discovered late, no idempotency so retries create duplicates, tight coupling to a field that changes in an update, and no owner for monitoring. Also remember reporting extracts and bank files, which are often forgotten because they are not called integrations in workshops. **Cta:** If your integrations need constant triage, Netray can help build private monitoring that explains failed messages in plain language and proposes fixes for human approval. **Faq:** #### What is the best integration pattern for D365 F&O? **Answer:** There is no single best. Use bulk data management packages for large scheduled loads, OData or custom services for interactive exchange, and business events to notify other systems. Choose by volume, latency, and how stable the interface must be through updates. #### How do I avoid API throttling? **Answer:** Batch requests, reduce polling, and avoid parallel bursts from one client. Follow Microsoft's published service protection guidance for your environment, and test with realistic peak volumes before go-live. #### Do I list every file transfer? **Answer:** Yes. Bank files, EDI documents and reporting extracts are integrations too. If it moves data in or out of the system on a schedule, it should be on the register with an owner. #### Should integrations be in the fit-gap too? **Answer:** Include a summary row in the fit-gap register so effort is counted, and keep the detail in this register. Cross-reference by interface ID to prevent drift. ## Search terms d365 integration inventory template, dynamics 365 interface list excel, d365 fo integration register, erp interface inventory template, d365 integration design template, d365 integration patterns list --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json