Customer Insights base licence structure

What it does

Dynamics 365 Customer Insights is sold as a single tenant-level base licence that covers both apps — Customer Insights - Journeys and Customer Insights - Data. It isn't a per-seat product: you buy capacity, not user licences, and then top it up with add-on packs.

Key facts

The base licence is bought once per tenant. If the client has more than one tenant, they buy again for each — entitlements don't cross tenant boundaries.
One base licence carries two independent meters: interacted people (the Journeys meter) and unified people (the Data meter). Both are counted at tenant level.
Microsoft publishes the current base entitlement figures on the Customer Insights pricing page and in the Dynamics 365 Licensing Guide; at time of writing the documented base grant is 10,000 interacted people and 100,000 unified people. Read the guide for the live numbers rather than quoting these back to a client.
There are two prices for the same entitlement: the full-price base offer and the "attach" base offer, discounted for tenants that already own a pre-qualifying Dynamics 365 app (Sales, Customer Service, Field Service, Supply Chain Management, Finance, Commerce) with enough seats. The entitlement definition is identical — only the price differs.
Dataverse capacity that comes with the base offer is granted once, no matter how many base offers you buy. Add-on packs of interacted people and unified people each carry their own incremental Dataverse entitlement.
Because it isn't seat-based, the licence doesn't appear under Licenses in the Microsoft 365 admin centre. Look under Billing > Your Products.
User access is free. Anyone with a licence for any model-driven Dynamics 365 app can use Journeys with only a security role assigned, and there is a $0 Dynamics 365 Customer Insights - Journeys User License in the admin centre catalogue for users who have no other Dynamics licence.
SMS is not included. The licence buys the orchestration, not the phone number or the message delivery — you sign up separately with a supported provider (Azure Communication Services, Twilio, Infobip and others).
Legacy standalone SKUs still exist on older tenants: Dynamics 365 Marketing (standalone) and Dynamics 365 Customer Insights (standalone), both pre-September 2023. The newer entitlements do not retro-fit onto them. Microsoft's purchase page states the Marketing standalone licence is no longer available for renewals as of September 2025.
After purchase, allow up to 24 hours for the licence to show up in the Dynamics 365 licensing system and the Power Platform admin centre.

When to use / skip

There is no "skip" here — if the client wants Journeys, this is the only way in. The real question is which base offer they qualify for and whether they've noticed. Attach pricing is a meaningful discount and plenty of clients who already run Sales or Customer Service buy at full price because nobody checked. Ask early, before the quote goes to procurement.

The other decision is whether to move off a legacy Marketing standalone licence now or ride out another renewal cycle. Staying put is cheaper short term and keeps outbound running, but it locks the client out of Customer Insights - Data and out of the entitlement model everything new is built against. For anything with a multi-year horizon, move.

Configuration decisions

Full-price base offer or attach — confirm the qualifying Dynamics 365 apps and seat counts on the tenant before pricing the deal.
How much interacted people capacity to buy up front, sized on the client's peak month rather than their average month.
Whether the tenant needs Customer Insights - Data at all in year one, or whether the unified people entitlement will sit unused while Journeys runs off Dataverse contacts and leads.
Purchase channel: direct through the Microsoft admin centre marketplace, through a CSP or reseller, or through an EA. This changes how long the licence takes to land on the tenant and who you chase when it doesn't.
Whether to move legacy standalone licences off at renewal or run both in parallel for a period.
How users get access: rely on automatic Entra user sync into the environment, or assign the $0 user licence explicitly.

Gotchas

The $0 Journeys user licence only grants Journeys. It doesn't open other Dynamics 365 apps and carries no Dataverse capacity entitlement of its own. Don't let it become the client's answer to "can we give Sales access too".
Buying two base offers does not double the Dataverse entitlement. Only the add-on packs stack.
Licences purchased through a partner or volume channel can take days to appear on the tenant, and Microsoft support can't help until they do. If the client is waiting on install, the reseller is the escalation path, not the product team.
If old standalone licences overlap with a new base licence during a transition, the tenant shows the sum of both entitlements until the old ones expire. That inflated number is temporary — don't size the next purchase from it.
Do not uninstall and reinstall the Journeys or Data apps when the licence type changes. The apps are the same across old and new licences and the reinstall buys you nothing but downtime.
On a single-geo tenant, licences only surface in the home tenant geography. Multi-geo clients used to need Microsoft to convert the tenant; the docs say that restriction was removed after June 2024, but check the tenant in front of you.

Consultant notes

Get the client's tenant admin to screenshot Billing > Your Products at the start of discovery. Half the licensing arguments on a Journeys project come from nobody knowing what's actually been bought.
Tell the client plainly that the price is driven by how many people they market to and how often, not by how many marketers use the tool. It reframes the conversation away from "how many seats do we need".
Push back on buying add-on capacity in the first month of a project. Run a real campaign cycle, watch the quota page, then size it.
The detailed entitlement terms live in the Dynamics 365 Licensing Guide PDF, not on Microsoft Learn. If you're advising on commercial terms, read the current guide — the Learn pages summarise it and lag it.
Before go-live, confirm at least one named person on the client side can see the quota page and knows what it means. Otherwise the first overage notification lands with nobody who understands it.

Worth another look when the licensing guide refreshes, or when the legacy standalone SKUs finally drop off renewals.