CRM integration · Updated November 15, 2026

Microsoft Dynamics 365 integration

We connect Dynamics 365 to WordPress, Webflow, Astro or Next.js sites and custom software, through Customer Insights – Journeys forms or the Dataverse Web API. Enquiries arrive as leads or contacts with their consent attached, and the site can show records your team keeps in Dataverse.

Rated 5.0 out of 5,72 Google reviews

Microsoft Dynamics 365 at a glance

Connects
Customer Insights – Journeys forms and form capture, the Dataverse Web API, Power Automate and Power Pages.
WordPress
The Journeys embed script, or a small plugin that writes to the Dataverse API from the server. Microsoft makes no WordPress plugin.
Webflow
The Journeys embed script in an Embed element, or form capture on a native Webflow form.
Astro or Next.js with Sanity
Server routes call the Dataverse Web API, signed in through an Entra ID app registration.
Custom software
The Dataverse Web API with an application user; Power Pages when you want Microsoft to host the portal.
Complexity
Medium to high. An embed is quick, but the API route needs your Microsoft admin to set up Entra ID and a security role.
Typical setup
2 to 4 days for embedded forms, 5 to 15 days for API sync or a portal.

How we connect Microsoft Dynamics 365

  • WordPress

    The quickest route is the JavaScript snippet Customer Insights – Journeys generates for each form, pasted into a block. To keep your own form design, we use form capture or a small plugin that posts to the Dataverse Web API from the server. Third-party plugins hold your Dataverse credentials, so we review one before installing it.

  • Webflow

    A Webflow Embed element can hold the Journeys snippet. To keep a native Webflow form, we add Journeys form capture, which maps your fields to Dataverse; Microsoft turns it off by default and says it needs a developer. Either way, your domain goes on the allowed list for external form hosting, or the browser blocks the submission.

  • Astro or Next.js with Sanity

    A server endpoint checks the form and writes a lead or contact through the Web API as an Entra ID application user. The secret or certificate never leaves the server. The same route can read public records, cached to spare your API allowance.

  • Custom software

    Portals and internal tools call the Dataverse Web API directly. If outside users need to sign in and see their own records, Power Pages is Microsoft's hosted option: table permissions decide what anonymous visitors and signed-in users can read. We build a custom portal when Power Pages can't handle your design or workflow.

What organizations use Microsoft Dynamics 365 for

  • Public bodies already on Microsoft 365

    Many municipalities and agencies run Microsoft 365 and Entra ID. Dynamics keeps service enquiries and stakeholder contacts in the same tenant, and the website form writes straight into it under IT's existing security model.

  • Investor and event contacts for enterprises

    Event registrations, investor enquiries and newsletter sign-ups use Journeys forms tied to a compliance profile. Consent is stored against the contact, and a journey can send the follow-up.

  • Enquiry routing for energy and industrial firms

    Supplier, partner and community enquiries arrive as leads with the page they came from. A Power Automate flow or our server code assigns the owner and alerts the right team.

What to watch out for

  • Consent and privacy

    Each Journeys form links to one compliance profile, whose purposes and topics hold the consent. Under CASL, use a profile with double opt-in for commercial email. Microsoft says Journeys forms are served through Azure CDN and may move data outside your chosen region, so a Quebec Law 25 privacy impact assessment should cover that.

  • Entra ID and security roles

    We use a single-tenant app registration and an application user whose custom security role can only create leads and read the tables the site shows. A certificate is safer than a client secret. An expired secret stops every submission, so we alert on failures.

  • API limits

    As of November 15, 2026, Dataverse allows 6,000 requests per user in a 5-minute window on each web server and answers with a 429 and a Retry-After when you go over. Application users share a daily tenant pool of 500,000 requests plus 5,000 per user licence. We cache reads and queue writes.

Sources

Checked against Microsoft's docs on November 15, 2026.

Questions about Microsoft Dynamics 365

Can our Dynamics 365 data stay in Canada?

Dynamics 365 has a Canadian region (crm3.dynamics.com). Microsoft's docs group Canada with the United States in a North America macro region and only guarantee in-country storage with Advanced Data Residency, so check where your environment sits in the Power Platform admin centre. Journeys forms go through Azure CDN, which may process data outside the region.

Our old Dynamics 365 Marketing forms stopped working. Why?

Microsoft removed outbound marketing in May 2026. Forms now come from Customer Insights – Journeys, so old outbound forms need rebuilding as Journeys forms or with form capture.

Do we need a Power Automate licence?

Not for embedded forms or server code we write. Flows that use premium connectors need a Premium or Process licence, so we check a flow's connectors before recommending one.

Can the forms be in French?

Yes. We build a French version of each Journeys form, with its own confirmation message and emails, for the French pages. Dynamics 365 itself adds languages through language packs per environment.

Running Dynamics 365?

Tell us which forms and records should reach the site. We'll say whether an embed, form capture or the API fits, and what your Microsoft admin will need to set up.

Book a call