Oracle Fusion Cloud ERP and Microsoft Dynamics 365 Sales integration

What moves between them

The main flow moves from Oracle Fusion Cloud ERP into Microsoft Dynamics 365 Sales. Customer records sync first, establishing the account master in D365. Quotes, sales orders, and invoices follow, mapped to the corresponding customer accounts. The sync runs on a schedule you control, typically every 5 to 15 minutes. D365 Sales reads this data and allows your sales team to see current quotes and order status without leaving the CRM. No data flows backward from D365 Sales into Oracle Fusion; the ERP is the source of truth for all transaction data.

How ml-connector handles it

ml-connector stores encrypted OAuth2 credentials for both systems. On the Oracle Fusion side, it polls the REST API for new or updated customers, quotes, sales orders, and invoices using query filters on last-update timestamp, and respects the customer-specific pod URL per deployment. On the D365 Sales side, it presents the Entra ID credentials and creates or updates records through the Dataverse API. When a D365 webhook fires for a quote conversion or order fulfillment, ml-connector can ingest that event (optional). Customer records are synced first, then orders and quotes are matched to accounts by customer ID. Invoice data includes the original order reference so the CRM shows the complete deal lifecycle. Both systems use OAuth2 with tokens that expire in 60 minutes, and ml-connector handles refresh automatically. Webhook payloads in D365 Sales are limited to 256 KB, so large transactions are polled rather than pushed. Every record carries full audit trail.

A real-world example

A mid-market B2B technology company runs Oracle Fusion Cloud ERP for order management, invoicing, and AR across two regions. The sales team uses Microsoft Dynamics 365 Sales to manage the pipeline, qualify opportunities, and track deal progress. Before the integration, quotes were generated in Oracle Fusion, exported to PDF, and manually entered into D365 Sales for deal tracking. When a deal closed, the sales ops team pulled the order from D365, re-entered it into Oracle Fusion, and waited for the invoice to cycle back into the CRM. With the integration, customers and quotes sync automatically from Oracle Fusion into D365 Sales within minutes of creation. When sales closes a deal in D365, the corresponding sales order and invoice from Oracle Fusion appear in the CRM, so the team sees the complete order-to-cash cycle without switching systems or manual re-entry.

What you can do

• •Sync customer accounts from Oracle Fusion Cloud ERP into Microsoft Dynamics 365 Sales and keep them current with each update.
• •Move quotes, sales orders, and invoices from Oracle Fusion into D365 Sales, mapped to the correct customer accounts in the CRM.
• •Poll Oracle Fusion on a schedule you control, filtering by last-update timestamp to retrieve only new or modified records.
• •Authenticate both systems with OAuth2 credentials, refresh tokens automatically when they expire, and track tokens per-tenant.
• •Maintain a complete audit trail of every sync, including record creation, updates, and any transformation or mapping errors.

Questions

Which direction does data move between Oracle Fusion Cloud ERP and Microsoft Dynamics 365 Sales?

Data moves from Oracle Fusion Cloud ERP into Microsoft Dynamics 365 Sales. Customers, quotes, orders, and invoices are synced to the CRM so your sales team always sees current data. No data flows backward from D365 into Oracle Fusion; the ERP remains the source of truth for all transactions.

Can I sync GL accounts, vendors, or AP/AR data from Oracle Fusion into Dynamics 365 Sales?

No. Microsoft Dynamics 365 Sales is a CRM designed for sales pipeline and customer management. It does not include general ledger accounts, vendor records, or AR/AP ledger entries. Those belong in Dynamics 365 Finance or Business Central. ml-connector syncs only the sales-facing data: customers, quotes, orders, and invoices.

How does polling work, and what happens when data changes in Oracle Fusion?

ml-connector polls the Oracle Fusion REST API on a schedule you define, typically every 5 to 15 minutes. It uses query filters on last-update timestamp, so only new or changed records are retrieved. Changes in Oracle Fusion appear in D365 Sales within one poll interval, ensuring your CRM stays current without overwhelming either system with requests.