Suger is now Fours. Read the announcement

Connect Dynamics 365 to Your Marketplace Pipeline

Marketplace tooling is built for Salesforce and HubSpot. If your CRM is Dynamics 365 — which it often is at a Microsoft-first ISV — here is what connecting it actually involves.

Samantha Ho
Aug 10, 2026 ·

Updated November 12, 2026: the Dynamics 365 integration now syncs opportunities at the org level, its application user does not need System Administrator, the user-level connection also asks for your tenant ID, and a new section covers the Dynamics 365 App, in preview.

A Dynamics 365 marketplace integration connects your CRM to the systems that hold marketplace offers, entitlements, and revenue — so a private offer, its acceptance, and the money that follows appear against the opportunity your sellers already work in, rather than in a portal they do not open.


There is a category of ISV that keeps hitting the same wall: Microsoft-first companies whose product runs on Azure, whose enterprise buyers purchase through Microsoft Marketplace, and whose CRM is Dynamics 365.

Everything in the cloud go-to-market tooling market assumes Salesforce, or occasionally HubSpot. So the Microsoft-first company — the one whose marketplace motion is arguably the most native — ends up with the least connected pipeline. Marketplace state sits in Partner Center. CRM state sits in Dataverse. A human copies between them.

This post is about closing that gap: what the connection actually involves, what moves in which direction, and which objects to map first.


What does a Dynamics 365 marketplace integration do?

It puts marketplace facts on the CRM record. Specifically: which of your accounts have a marketplace agreement, which offers are outstanding, when an entitlement starts and ends, and what has been billed against it.

That matters because of who is asking. A seller working a renewal needs to know whether the customer bought through Microsoft Marketplace, because that changes the renewal mechanics entirely. A partner manager needs to know whether a co-sell referral exists. A finance lead needs to know whether an opportunity marked closed-won has an entitlement behind it. None of those people should be opening Partner Center.

The integration is not a replacement for the marketplace console. It is the join that lets your CRM answer marketplace questions.


What Fours’ Dynamics 365 integration supports

Fours documents Dynamics 365 as a first-class CRM integration alongside Salesforce and HubSpot: “Sync sales, customer, and operational data between Dynamics 365 and Fours.”

The capability matrix is worth reading carefully before you design anything, because it is narrower than the Salesforce connector:

CapabilityOrg levelUser level
Read dataSupportedSupported
Write dataSupportedSupported
Sync dataSupported (opportunities)Not supported
WebhooksNot supportedNot supported

Fours states this plainly: “Webhooks are not supported at this time.”

That line should shape your design. Read and write both work, so a workflow, job, or agent can read CRM records and write back to Dataverse, and the org-level connection syncs your opportunities so they can become co-sell referrals. What you do not get is a push notification when something changes in Dataverse: everything other than opportunities moves when a workflow, job, or API call moves it — initiated, not ambient.

Practically, that means:

  • Choose a cadence deliberately. Nightly is usually right for entitlements and revenue; faster for offers in flight.
  • Do not build anything that assumes near-real-time CRM change detection. If a Dynamics field change must trigger a marketplace action within seconds, that trigger has to come from the Dynamics side.
  • Design for idempotency. Pull-based movement means the same record will be processed more than once. Every write needs a stable external key.

Setting it up: two auth paths

Fours documents two ways to connect, and the choice is not cosmetic — it determines whose permissions the integration inherits.

Org level, via Azure AD credentials. You need the Dynamics 365 instance URL, the tenant ID from Azure AD, an application user in Dynamics 365 linked to your Azure AD app registration, and security roles assigned to that application user through the Power Platform Admin Center: Fours Integration (plus Fours Integration Write if Insulin writes to Dynamics 365) when you install the Dynamics 365 App, or a role of your own with the privileges Fours lists. The application user does not need System Administrator.

User level, via OAuth 2.0. You need the instance URL and your Azure AD tenant ID, Microsoft credentials for the individual, and that person’s consent to grant Fours data access.

Use org level for anything that must keep running when a person changes role. Use user level only where the action genuinely should be scoped to one individual’s permissions.

One constraint to plan around, because it has no workaround: “For security purposes, editing an existing Microsoft Dynamics 365 integration is not allowed.” Get the instance URL, tenant, and application user right the first time. Changing them means creating a new integration, which means anything keyed to the old one has to be repointed.

Fours’ published integration timeline puts the Salesforce connector at “approx. 1 hour” and the HubSpot connector at “approx. 10 minutes.” It gives no figure for Dynamics 365; expect most of that setup to happen in Dynamics 365 and the Power Platform Admin Center, creating the application user and assigning its roles, rather than in Fours.

The Dynamics 365 App, in preview

The Dynamics 365 App is a managed solution for Dynamics 365 Sales that adds a Fours button to the opportunity record page. Its side pane shows the opportunity’s co-sells, offers, and agreements (entitlements), and lets your team create AWS and Azure Marketplace private offers, AWS offer sets, resale authorizations, and amendments, and work AWS co-sells, all through the org-level connection above, so users do not sign in to Fours. It is in preview and not yet listed on Microsoft AppSource; to try it, contact your Fours account team for the install package. It does not support Google Cloud yet, and the button is on the opportunity record page only. The Dynamics 365 App documentation covers the install and the security roles.


Which objects to map first

Do not try to mirror everything. Map the objects that answer a question somebody is currently asking a human.

Fours’ own records give you the vocabulary: the buyer, the offer a buyer purchases through, the entitlement created when the buyer accepts it, the revenue billed against that entitlement, and the co-sell referral shared with the cloud partner.

A sensible first pass:

ObjectDirectionLands onAnswers
BuyerMarketplace → CRMAccountIs this account a marketplace buyer at all?
OfferMarketplace → CRMOpportunityIs an offer outstanding, and for how much?
EntitlementMarketplace → CRMAccount / OpportunityWhen does this contract start and end?
Billed revenueMarketplace → CRMAccountWhat has actually been billed?
Co-sell referralBothOpportunityDoes a Microsoft co-sell record exist for this deal?
Opportunity IDCRM → MarketplaceOffer, referralWhich CRM deal is this offer for?

The last row is the one teams skip and later regret. Microsoft Partner Center carries an optional CRM ID field on a co-sell deal — “ID of the opportunity in your CRM system (used as a tag for your tracking purposes).” Populating it with the Dynamics opportunity ID is the cheapest reconciliation you will ever build, and it costs nothing at creation time. Leave it blank and every later attempt to tie Partner Center records back to Dynamics is fuzzy matching on customer name.

Two things not to sync

Account ownership. Decide which system is authoritative for the account record and leave the other one read-only on that field. Bidirectional ownership sync produces update loops and a lot of confused audit history.

Anything you would not want a seller to act on. Offer state before it is real, provisional pricing, internal notes. The CRM is the most widely read system you own.


The Microsoft-first advantages worth using

If you are on Dynamics and selling through Microsoft Marketplace, two things line up in your favour.

Identity is already common. Partner Center, Azure AD, and Dynamics can all sit inside the same tenant. The org-level auth path is an app registration you probably already know how to create, and the admin who owns Power Platform often also manages Partner Center access.

Committed spend is visible earlier. Partner Center shows whether a selected customer account has a Microsoft Azure Consumption Commitment. Getting that flag onto the Dynamics account record turns a deal-desk question into a field a seller can see while qualifying — what a MACC is covers why that changes the deal shape.

The rest of the Microsoft motion — listing types, Partner Center, private offers versus private plans — is covered in how to sell on Azure Marketplace and Azure private offers vs private plans.


Frequently asked questions

Does Fours integrate with Microsoft Dynamics 365? Yes. Fours documents Dynamics 365 as a CRM integration alongside Salesforce and HubSpot, supporting reads and writes at both organization level and user level.

Does the Dynamics 365 integration support real-time sync? Not by push. Fours syncs Dynamics 365 opportunities over the org-level connection, but webhooks are not supported, so other changes move when a workflow, job, or API call reads or writes them.

What do I need to connect Dynamics 365? For org-level access: the instance URL, your Azure AD tenant ID, an application user in Dynamics 365 linked to an app registration, and security roles assigned through the Power Platform Admin Center. For user-level access: the instance URL, the tenant ID, and Microsoft credentials with consent.

Can I edit a Dynamics 365 integration after creating it? No. Fours does not allow editing an existing Microsoft Dynamics 365 integration, for security reasons. Changing the instance, tenant, or application user means creating a new integration.

Which records should I sync first? Buyers, offers, and entitlements onto the account and opportunity, plus your CRM opportunity ID pushed back onto marketplace and co-sell records. That last one is what makes later reconciliation possible.

Does Microsoft Partner Center hold a CRM reference? Yes. A co-sell deal in Partner Center has an optional CRM ID field for the opportunity ID in your own system. It is optional, frequently left blank, and the cheapest reconciliation key available.


Takeaways

  • Dynamics-first ISVs are the least served by marketplace tooling and often the most native to the Microsoft motion. The gap is connection, not capability.
  • Fours’ Dynamics 365 integration reads and writes at org and user level and syncs opportunities at org level; it has no webhooks, so other movement is initiated and cadence is a design decision.
  • Org-level auth needs an app registration, an application user, and security roles from the Power Platform Admin Center, not System Administrator. User-level auth is OAuth against an individual.
  • The integration cannot be edited after creation. Get the instance, tenant, and application user right the first time.
  • Map buyers, offers, entitlements, and revenue into the CRM; push your opportunity ID back out.
  • Populate Partner Center’s optional CRM ID field. It is the difference between reconciliation and name matching.

Your CRM should not be the last system to learn that a customer bought. See how Fours’ integrations connect marketplace offers and entitlements to the CRM your sellers already work in — including Dynamics 365, not only Salesforce.

Sources

Primary sources for the platform rules cited above. Last verified November 12, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.

Browse every post on the Fours Blog

Stay Updated

New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.

Follow Fours on LinkedIn