When LinkedIn Sales Navigator CRM sync stops working with Dynamics 365, the cause is almost always an expired OAuth connection, a Sales Navigator admin permission change, or a broken field mapping. Start by reconnecting the CRM integration in Sales Navigator Admin Settings, then verify the Dynamics 365 service account still has read/write access and that scheduled sync hasn't silently failed.
Most teams discover the sync died weeks before anyone noticed, so check your last successful sync timestamp first. That single date tells you whether you're chasing a recent config change or a slow-burning credential expiry.
Confirm the sync is actually broken (not just slow)
Sales Navigator's CRM sync isn't instant. Activity writeback and data sync run on a schedule—typically every few hours—so a missing record might just be in the queue. Open Sales Navigator > Admin > CRM Settings and look at the connection status banner. A green "Connected" state with a recent sync timestamp means the pipe is open. A red or amber banner, or a timestamp more than 24 hours old, confirms a real failure.
Cross-check inside Dynamics 365. Go to Sales Navigator embedded controls on a contact or lead record. If the widget shows "Unable to load" or asks you to sign in again, the OAuth token between the two platforms has expired.
Fix the OAuth and authentication chain
The most common root cause is a stale connection. LinkedIn's enterprise OAuth tokens to Dynamics 365 expire or get revoked when an admin's password changes, MFA policy updates, or the connecting user leaves the company.
Reconnect the integration
In Sales Navigator Admin, find the Dynamics 365 connection and click Disconnect, then Reconnect. You'll be prompted to authenticate with a Dynamics 365 account. Use a dedicated service account—not a personal admin login that might get deactivated. The account needs:
- A valid Dynamics 365 Sales license
- System Administrator or a custom security role with read/write on Lead, Contact, Account, and Opportunity
- An active Azure AD identity with current MFA enrollment
After reconnecting, force a manual sync if the option is available, then recheck the status banner.
Check Azure AD and conditional access
If reconnection fails immediately, the problem is often upstream in Microsoft Entra ID (formerly Azure AD). A new conditional access policy can block the LinkedIn enterprise app from authenticating. Have your Microsoft admin review sign-in logs in the Microsoft Entra admin center and filter for the LinkedIn Sales Navigator application. Look for failures with error codes like AADSTS50105 (user not assigned) or AADSTS53003 (blocked by conditional access).
Verify field mappings and entity permissions
A sync that connects but doesn't move data usually has a mapping or permission problem on the Dynamics side. LinkedIn writes activities, notes, and account/lead matches back into Dynamics 365 entities. If those entities were customized—renamed fields, new required fields, or changed entity ownership—the writeback fails silently.
Check for required fields added to Lead or Contact entities that Sales Navigator doesn't populate. A newly required custom field will reject every inbound record. The fix is to either make the field optional or set a default value at the entity level.
| Symptom | Likely cause | Fix |
|---|---|---|
| Widget won't load, asks to re-sign-in | Expired OAuth token | Reconnect integration with service account |
| Connected but no new activities | Required custom field rejecting writeback | Make field optional or set default |
| Some records sync, others don't | Security role missing entity access | Grant read/write on affected entity |
| Reconnect fails instantly | Conditional access policy block | Whitelist LinkedIn app in Entra ID |
Check Sales Navigator seat and admin status
CRM sync requires an active Sales Navigator Advanced (formerly Team) or Advanced Plus contract. If your contract renewal lapsed or seats were reassigned, the integration drops. Confirm in the LinkedIn Sales Navigator contract admin view that CRM sync is still an enabled feature on your plan. Advanced Plus is required for full bidirectional Data Validation and writeback—the lighter tiers only support one-way embedded profiles.
If you've recently downgraded or your account team changed the contract, this is the overlooked culprit.
Rule out Dynamics 365 environment issues
Sometimes the break has nothing to do with LinkedIn. A Dynamics 365 environment moved to a new region, a sandbox-to-production swap, or a changed org URL will orphan the existing connection. The Sales Navigator integration stores a specific Dynamics org endpoint; if that URL changed, you must disconnect and reconnect to register the new endpoint.
Also check API throttling. Microsoft enforces service protection API limits, and a bulk import job or another integration hammering the API can cause Sales Navigator's sync requests to get throttled (HTTP 429). These usually resolve on their own, but a persistent 429 means you need to stagger your integrations.
When to escalate to support
If the connection status stays red after a clean reconnect with a verified service account, gather your last successful sync timestamp, the exact error banner text, and any Entra ID sign-in error codes, then open a ticket with LinkedIn Sales Navigator support. Microsoft documents the integration setup in their Dynamics 365 Sales LinkedIn integration guide, which is worth re-reading after major Dynamics updates since field mappings occasionally change between releases.
While you're tightening up your prospecting stack, it's worth comparing how AI tools can automate personalized cold outreach once your data is flowing cleanly again, and reviewing whether LinkedIn InMail response rates justify the seat cost on your current plan.
Key takeaways
Start with the status banner and last sync timestamp to confirm a real failure. Reconnect the OAuth integration using a stable service account with the right Dynamics security role. Check Entra ID conditional access, required custom fields, and your Sales Navigator contract tier. Most sync failures trace back to expired credentials or a permission change—not a bug in the integration itself.