Quick Summary
Summarize this article instantly with your preferred AI model.
LinkedIn Ads and Microsoft Dynamics 365: How to Connect Them
LinkedIn Ads and Microsoft Dynamics 365: How to Connect Them
Connecting LinkedIn Ads to Microsoft Dynamics 365 sends your lead gen form submissions straight into Dynamics as lead records, automatically, with no CSV export in between, using a native connector that is free because Microsoft owns both LinkedIn and Dynamics 365. Microsoft acquired LinkedIn in 2016, and that shared ownership is what makes this integration different from the others: the lead sync is first-party and costs nothing to install, so the basic connection needs no third-party middleware. The connector, called the Dynamics 365 Connector for LinkedIn Lead Gen Forms, matches each submission to a lead in Dynamics, where it can drop into real-time journeys, segments, and scoring, and from there you can push audiences and conversions back so LinkedIn optimizes for pipeline. This guide covers what syncs, how the native connector works, how to set it up, the Sales versus Customer Insights - Journeys question, the personal-email fix, and how to track leads to revenue.
Key takeaways
- Because Microsoft owns both LinkedIn and Dynamics 365, the lead-sync connector is native and free, so the basic sync needs no third-party tool.
- Lead gen form submissions sync into Dynamics as lead records automatically, with a manual Sync Submissions option, so leads reach your team without a CSV export.
- Only lead gen form campaigns sync; website-CTA campaigns are tracked with your own forms, pixels, and the Conversions API instead.
- In Customer Insights - Journeys, synced leads can drop straight into real-time journeys, segments, and scoring, which is where Dynamics earns its keep.
- LinkedIn forms pre-fill personal emails, which breaks routing and account matching, so add an enrichment step to attach the work email and company.
Why connect LinkedIn Ads to Dynamics 365?
Because a lead sitting in Campaign Manager is a lead Dynamics cannot see, and a LinkedIn conversion only means something once you can follow it to an opportunity and a closed deal. Connected, a lead gen form submission becomes a Dynamics lead the moment it syncs, so it enters your routing, your journeys, and your pipeline reporting without anyone exporting a file. The connection also runs the other way: the segments you hold in Dynamics can target or exclude on LinkedIn, and the conversions you record in Dynamics can flow back so LinkedIn learns which leads became revenue. For a Microsoft shop, this is the step that turns LinkedIn from a channel that reports clicks into one you can judge on pipeline, and because both products are Microsoft’s, it is the cheapest and tightest of the major CRM integrations to stand up.
What syncs between LinkedIn and Dynamics 365?
The value is the loop: leads and data in, audiences and conversions out.
| Direction | What syncs | Why it matters |
|---|---|---|
| LinkedIn to Dynamics | Lead gen form submissions become lead records | Leads reach journeys and sales instantly |
| LinkedIn to Dynamics | Campaign and ad source on the lead | Lets you attribute the lead to its LinkedIn campaign |
| Dynamics to LinkedIn | Segments as matched audiences | Exclude customers and open deals, retarget stalled leads |
| Dynamics to LinkedIn | Conversions via the Conversions API | LinkedIn optimizes toward pipeline, not clicks |
| Within Dynamics | Leads into journeys, scoring, and dashboards | Work and measure every lead automatically |
Leads coming in is the headline, but the journeys and scoring inside Dynamics, plus the conversions going back out, are what connect spend to revenue.
How does the native LinkedIn connector work?
Microsoft provides a free connector, the Dynamics 365 Connector for LinkedIn Lead Gen Forms, that links your LinkedIn Campaign Manager account to Dynamics so lead gen form submissions sync in as leads. You install the connector, authorize your Campaign Manager account once through a LinkedIn user profile record in Dynamics, and from then on submissions sync automatically, with a manual Sync Submissions button on hand if you want to pull the latest submissions on demand. Each submission is matched into a lead that carries its source context, so you can see which LinkedIn campaign and form produced it, and out-of-the-box dashboards can report on campaign effectiveness. The important limit is the same as every CRM integration: only lead gen form campaigns feed this connector. A campaign that sends people to your website with a plain call to action does not sync this way, so those conversions are tracked through your own web forms and pixels, and ideally the Conversions API, instead.
How do you set up the integration?
The native connection is a short, one-time setup, not a project. The order matters more than any single step.
- Install the Dynamics 365 Connector for LinkedIn Lead Gen Forms into your Dynamics 365 environment from Microsoft AppSource, or enable the LinkedIn lead generation integration if you are using Customer Insights - Journeys.
- Make sure you have a LinkedIn Campaign Manager account, which needs a LinkedIn Page and billing set up, and admin access to it.
- In Dynamics, create a LinkedIn user profile record and authorize it with your Campaign Manager credentials, so the two accounts are linked.
- Map each lead gen form field to the matching Dynamics field, including any custom questions, so nothing arrives with nowhere to land.
- Decide how a submission that matches an existing lead or contact is handled, so you do not pile up duplicates.
- Add an enrichment step so the work email and company are attached before routing and scoring run.
- Route the synced leads into a journey or scoring model, and check the sync with Sync Submissions after launching each new form.
Menu labels shift as Microsoft updates Dynamics, so confirm the exact wording in your environment, but the sequence holds: install, connect, authorize, map, dedupe, enrich, route.
Sales app versus Customer Insights - Journeys: which path?
Two LinkedIn integrations live in the Dynamics world, and it helps to keep them straight. The lead gen connector that syncs form submissions into Dynamics as leads is the one this guide is about, and it is the LinkedIn Ads integration. Separately, Dynamics 365 Sales has a LinkedIn connector tied to Sales Navigator that surfaces LinkedIn profile data on lead, contact, and account records, which is about selling, not about your ad campaigns. On licensing, the lead gen connector runs on a Dynamics 365 Online environment, historically one with the Sales app enabled, while the Customer Insights - Journeys path uses that app’s own built-in LinkedIn lead generation integration, so confirm what your setup covers. If your goal is to get LinkedIn ad leads into Dynamics and worked automatically, the Customer Insights - Journeys path is the richer one, because a synced lead can drop straight into a real-time journey, a segment, or a scoring model. If you are on the Sales app, the lead gen connector still brings the leads in; you just handle the follow-up with Sales tools rather than marketing journeys.
The personal-email problem, and how to fix it
Here is the wrinkle specific to LinkedIn lead gen forms, and it applies to Dynamics exactly as it does to any CRM. The forms pre-fill from the member’s LinkedIn profile, and the email they pre-fill is often a personal one, a gmail.com or similar, not the work address. That quietly breaks the things Dynamics does by email domain: routing the lead to the right owner, matching it to an existing account, and firmographic scoring all assume a work domain, and a personal email defeats them. The fix is an enrichment step between the sync and your scoring: when a lead arrives, enrich it to attach the work email, company, and firmographic data, so routing and matching work as intended. Enrichment complements the native connector rather than replacing it; the connector gets the lead in, enrichment makes it usable.
Sending audiences and conversions back to LinkedIn
The reverse direction is where efficiency lives. Build matched audiences from your Dynamics segments and sync them to LinkedIn so you can exclude open opportunities and recent customers from prospecting, and retarget stalled leads with tailored campaigns, refreshing the audience on a schedule so it stays current. Through the Conversions API, send first-party conversions back to LinkedIn, uploaded from Dynamics or sent through a connection, including offline outcomes like a qualified lead or a closed-won deal, so LinkedIn’s optimization chases the leads that become revenue rather than the cheapest clicks. The inbound lead sync is the fully native, free part; the audiences and conversions going back take a little more setup, but they are what turn the integration from a one-way lead pipe into a loop that gets smarter each quarter.
The first-party stack test
The mental model that tells you whether to lean on the native Dynamics integration is a quick three-question test we call the first-party stack test. First, is your CRM Dynamics 365? If so, the connector is free and first-party, so start there rather than paying for a middleware tool. Second, are your lead campaigns using lead gen forms? Only those sync natively, so website-CTA campaigns need their own tracking. Third, do you want leads worked automatically? In Customer Insights - Journeys, a synced lead can go straight into a journey and a scoring model, which is the real payoff. If the answer to all three is yes, the native route is your default, and a third-party tool is only for the gaps it leaves, such as enrichment or routing leads into a system Dynamics does not cover.
Common Dynamics 365 integration mistakes
The mistakes are mostly broken links in the chain from form to revenue. Not carrying the campaign source onto the lead, so attribution stops at the click, is the big one. Having no dedupe rule, so matching leads and contacts pile up as duplicates, corrupts your data. Skipping enrichment, so personal emails break routing and account matching, wastes good leads. Leaving synced leads sitting in Dynamics with no journey or owner, so they go cold before anyone works them, throws away the speed the integration gives you. And not monitoring the sync, so a silent failure goes unnoticed for weeks, is the one that quietly loses leads you paid for. Run Sync Submissions and check the connection after launching any new form.
Close the loop: track leads to revenue in Dynamics
Here is the thread. A LinkedIn lead is only worth what it becomes, and in a Microsoft shop it only becomes visible once it is a Dynamics lead you can follow through a journey to an opportunity and revenue. Use the free native connector to sync the leads in and keep the campaign source so attribution survives, fix the personal-email problem so routing works, push audiences and conversions back so LinkedIn optimizes toward pipeline, and treat it the same way you would any CRM integration or server-side tracking. Then judge LinkedIn on the pipeline Dynamics confirms, not the conversions Campaign Manager claims. If you want your LinkedIn and Dynamics 365 set up for closed-loop tracking to revenue, you can book a demo.
Frequently Asked Questions
Q1. How do you connect LinkedIn Ads to Microsoft Dynamics 365?
Install Microsoft’s free Dynamics 365 Connector for LinkedIn Lead Gen Forms from AppSource, or enable the LinkedIn lead generation integration in Customer Insights - Journeys. Create a LinkedIn user profile record in Dynamics and authorize it with your Campaign Manager credentials, then map each lead gen form field to a Dynamics field. Once connected, lead gen form submissions sync into Dynamics as leads automatically, with a manual Sync Submissions option on hand.
Q2. Is the LinkedIn Dynamics 365 integration free?
Yes, the native lead gen connector is free to install, because Microsoft owns both LinkedIn and Dynamics 365, so the basic lead sync costs nothing beyond your ad spend and your Dynamics licensing. The connector runs on a Dynamics 365 Online environment, historically with the Sales app enabled, and the marketing path uses Customer Insights - Journeys, so confirm which licensing your setup needs. Third-party tools cost money, so start with the free native connector.
Q3. Does the LinkedIn connector create a lead in Dynamics 365?
Yes. A LinkedIn lead gen form submission is matched into a Dynamics lead record, carrying its source context so you can see which campaign and form produced it. From there, in Customer Insights - Journeys, the lead can enter a real-time journey, a segment, or a scoring model, so it is worked automatically rather than sitting in a list. Keep the campaign source on the lead so attribution survives to revenue.
Q4. Do LinkedIn lead gen form leads sync to Dynamics automatically?
Yes, once the connector is set up and authorized. Submissions sync into Dynamics as leads automatically, and there is also a manual Sync Submissions button if you want to pull the latest submissions on demand. This works for any ad format that carries a lead gen form. Campaigns that send people to your website with a plain call to action do not sync through this connector, so track those with your own forms and the Conversions API.
Q5. What is the difference between the LinkedIn connector in Dynamics 365 Sales and Customer Insights - Journeys?
The lead gen connector syncs LinkedIn ad form submissions into Dynamics as leads, which is the LinkedIn Ads integration. The Sales app also has a LinkedIn connector tied to Sales Navigator that surfaces LinkedIn profile data on records, which is about selling, not your ad campaigns. For getting ad leads worked automatically, the Customer Insights - Journeys path is richer, because synced leads can drop straight into journeys and scoring.
Q6. Why do LinkedIn leads arrive with personal email addresses?
Because LinkedIn lead gen forms pre-fill from the member’s profile, and the email on file is often a personal address rather than a work one. That breaks domain-based routing, account matching, and firmographic scoring in Dynamics. The fix is an enrichment step that attaches the work email, company, and firmographic data when the lead arrives, so your routing and matching work as intended.
Q7. Do you need a third-party tool to connect LinkedIn Ads and Dynamics 365?
Not for the basic lead sync, which is native and free through Microsoft’s connector. A third-party tool is mainly useful for enrichment, for routing leads into a system the native connector does not cover, or for more complex workflows. Start with the native connection, since it costs nothing and is first-party, and add a tool only for the jobs it genuinely leaves open, such as attaching work emails and firmographics.
Q8. How do you track LinkedIn ad revenue in Dynamics 365?
Keep the campaign source on every synced lead, route leads through journeys to opportunities, and follow those opportunities to closed-won revenue, so you can report pipeline and revenue by LinkedIn campaign. Send closed-won and qualified-lead conversions back to LinkedIn through the Conversions API so its optimization learns what revenue looks like. The key is the unbroken chain from form to revenue, with the campaign source intact at every step.
More Featured Blogs
View All Blogs
LinkedIn Audience Network: Reach Off LinkedIn Without Wasting Spend
LinkedIn Ads and Salesforce: How to Connect Them and Why
LinkedIn BrandLink: Brand Video Alongside Creators and Publishers