IFS Cloud and Microsoft Dynamics 365 Sales integration

What moves between them

The primary flow runs from IFS Cloud into Microsoft Dynamics 365 Sales. Customer records from IFS (CustomerSet) sync into Dynamics as accounts, maintaining a mapping between IFS customer codes and Dynamics account IDs. Sales orders from IFS (CustomerOrderSet) and their line items sync into Dynamics as salesorders, creating associated order lines with product references. Quote records flow the same direction. Reference data such as products and price levels are aligned so sales order items map to valid Dynamics products. Opportunity and lead data flows from Dynamics back to IFS as potential orders, but Dynamics 365 Sales has no GL account or AP ledger structure, so financial posting remains in IFS.

How ml-connector handles it

ml-connector obtains IFS OAuth tokens using the client credentials flow against the tenant-specific token endpoint and stores them encrypted with automatic refresh before expiry. On the Dynamics 365 Sales side, it authenticates via Microsoft Entra ID using the same Client Credentials pattern. Because IFS offers no self-registerable webhooks, ml-connector polls the IFS OData API on a schedule tied to your sales cycle, filtering by modified timestamps to find new and changed customers and orders. Mutations in IFS require reading the ETag header first, then including it in the PATCH request for optimistic concurrency. Dynamics 365 Sales webhooks are registered via Dataverse Web API and listen for ConvertQuoteToSalesOrder and FulfillSalesOrder events to trigger order fulfillment flows back into IFS. Product mapping is done by matching IFS item numbers to Dynamics product codes, and the integration tracks ETags and webhook subscription IDs to handle retries and prevent duplicate processing. Rate limiting on IFS (429 responses) is handled with exponential backoff, and Dynamics webhook delivery failures are retried automatically by the platform.

A real-world example

A mid-sized manufacturing and distribution company runs IFS Cloud for order management, inventory, and finance. The sales team uses Dynamics 365 Sales to track opportunities and manage the customer relationship. Before the integration, orders won in Dynamics were manually re-entered into IFS, creating delays and keying errors, and customer master data was managed separately in both systems. With IFS Cloud and Dynamics 365 Sales connected, salespeople quote and book orders directly in Dynamics, which flow into IFS automatically for inventory allocation and fulfillment. Customer changes sync from IFS back to Dynamics, so the sales team always sees current terms, credit limits, and shipping addresses. Month-end reconciliation between CRM pipeline and order fulfillment is now instant.

What you can do

• •Sync customer master data from IFS Cloud into Dynamics 365 Sales as accounts, keeping customer codes and attributes aligned.
• •Replicate IFS Cloud sales orders and line items into Dynamics 365 Sales as orders, with full product and pricing details.
• •Convert Dynamics 365 Sales quotes to orders and push the result back to IFS Cloud for fulfillment and accounting.
• •Authenticate IFS Cloud with tenant-specific OAuth 2.0 and Dynamics 365 Sales with Microsoft Entra ID, managing token expiry on both sides.
• •Poll IFS Cloud on a configurable schedule with timestamp filters and handle ETag-based concurrency, plus Dataverse webhook retries with exponential backoff.

Questions

Which direction does data move between IFS Cloud and Dynamics 365 Sales?

The primary flow is IFS Cloud into Dynamics 365 Sales. Customer records and sales orders sync from IFS into Dynamics, and opportunity and lead data flows the opposite direction. Reference data such as products and price levels are aligned in both directions. GL accounts, AP/AR ledger entries, and vendor records stay in IFS because Dynamics 365 Sales has no financial ledger structure.

How does ml-connector handle IFS Cloud's tenant-specific URLs and lack of self-registerable webhooks?

ml-connector accepts the full IFS Cloud tenant URL per customer and stores the OAuth 2.0 credentials encrypted, obtaining tokens from the tenant-specific token endpoint. Because IFS does not support self-registerable webhooks, the integration polls the OData API on a schedule tied to your sales cycle, filtering by modified timestamps to detect new and changed records. ETag headers are captured on reads and included on mutations to enforce optimistic concurrency control.

What happens when Dataverse webhooks fail or IFS rate limits are exceeded?

Dynamics 365 Sales automatically retries webhook deliveries once on 502/503/504 errors. IFS rate limiting returns HTTP 429; ml-connector backs off exponentially with jitter and retries the request. All record processing carries a full audit trail, so failed webhook events and rate-limited API calls can be replayed once the downstream system recovers.