Microsoft Dynamics 365 F&O and Mailchimp integration

What moves between them

The main flow runs from Microsoft Dynamics 365 F&O into Mailchimp. ml-connector reads F&O customer accounts and contact details and creates or updates the matching Mailchimp list members and e-commerce store customers, keyed on email address. Posted sales from F&O become Mailchimp e-commerce orders under a store linked to the target audience, carrying order total, currency, and line items so campaign reports can attribute revenue. Product records sync into the store catalog so order lines reference real items. A smaller reverse flow applies Mailchimp subscribe, unsubscribe, profile, and email-change events back to F&O so marketing consent and contact fields stay accurate. Mailchimp is never treated as a financial source, so no GL entries are read from it.

How ml-connector handles it

ml-connector stores both credential sets encrypted. It obtains the F&O bearer token through the Entra ID client credentials flow against the environment host and refreshes it when a call returns 401, and it presents either the Mailchimp API key over Basic auth or the OAuth token, resolving the data center prefix from the key suffix or the OAuth metadata endpoint before building the base URL. On the F&O side it accepts the full tenant URL per customer because there is no shared host, and it adds cross-company filtering where multiple legal entities are in scope. Because Business Events deliver only identifier stubs and ordering is not guaranteed, the connector polls CustomersV3 and sales entities on a schedule and uses each event only as a trigger to fetch full records over OData. A Mailchimp store must exist and be tied to an audience before any e-commerce customer or order is written, so ml-connector ensures the store first. F&O customer accounts map to Mailchimp members and store customers by email, and the connector skips re-subscribing addresses Mailchimp has marked cleaned, since those writes fail. F&O OData returns 429 with Retry-After and Mailchimp returns 429 when the 10-connection limit is hit, so the connector backs off and retries within both ceilings, and it caps parallel F&O reads at the documented concurrency limit. Inbound Mailchimp webhooks carry no signature, so ml-connector secures them with an unpredictable URL token over HTTPS rather than an HMAC check. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized consumer products manufacturer with roughly 300 staff runs Microsoft Dynamics 365 F&O for finance, order management, and the customer master, and runs marketing campaigns in Mailchimp. Before the integration the marketing team exported customer lists from F&O to a spreadsheet and re-imported them into Mailchimp every few weeks, so audiences were always stale, unsubscribes never made it back to the ERP, and campaign reports could not tie email engagement to actual orders. With Microsoft Dynamics 365 F&O and Mailchimp connected, new and updated customers flow into the right audience automatically, posted sales appear as e-commerce orders for attribution, and unsubscribe events update the customer record in F&O. The manual export step is gone and marketing works from a current list.

What you can do

• •Sync Microsoft Dynamics 365 F&O customer accounts into Mailchimp audiences and e-commerce store customers, keyed on email.
• •Post F&O sales transactions as Mailchimp e-commerce orders with totals, currency, and line items for campaign attribution.
• •Keep the Mailchimp store catalog aligned with F&O products so order lines reference real items.
• •Apply Mailchimp subscribe, unsubscribe, and profile events back to F&O so marketing consent stays current.
• •Bridge Entra ID OAuth on the F&O side with Mailchimp API key or OAuth, resolving the data center, with retries and a full audit trail.

Questions

Which direction does data move between Microsoft Dynamics 365 F&O and Mailchimp?

The main flow is F&O into Mailchimp. Customer accounts become Mailchimp list members and store customers, and posted sales become e-commerce orders for attribution. A smaller reverse flow brings subscribe, unsubscribe, and profile events from Mailchimp back into F&O so consent and contact fields stay accurate. Mailchimp is never read as a financial source.

Does Mailchimp store invoices or GL postings from F&O?

No. Mailchimp is an email marketing platform and has no GL accounts, invoices, vendors, or purchase orders. The closest analog to a sales transaction is the e-commerce order object, which carries an order total, currency, and line items. ml-connector maps posted F&O sales into those orders for marketing reporting, not as accounting records.

How does the integration handle authentication and Mailchimp webhooks?

ml-connector obtains an Entra ID bearer token for F&O through the client credentials flow and refreshes it on expiry, while presenting the Mailchimp API key over Basic auth or an OAuth token and resolving the data center prefix first. Mailchimp Marketing webhooks carry no cryptographic signature, so the connector secures the endpoint with an unpredictable URL token over HTTPS and verifies events by calling back to the Mailchimp API where needed.