Customer Insights tenant licensing and how Data and Journeys sit under it

What it does

Dynamics 365 Customer Insights is licensed per tenant, not per named user, and one licence covers the whole product family — the Data app and the Journeys app both draw on it. Microsoft Learn states the per-tenant model and then hands off every actual number to the Dynamics 365 Licensing Guide PDF, so the structure is documented publicly but the entitlements are not.

Key facts

The licence is a tenant-level purchase that "includes multiple capabilities". There is no per-seat Customer Insights user licence to assign in the way you would assign a Sales Enterprise licence.
Data and Journeys are two apps under the same purchase. Each is installed into a Dataverse environment, and they do not have to live in the same one.
Learn's licensing page carries exactly two pointers: the public pricing page on microsoft.com, and the Dynamics 365 Licensing Guide (go.microsoft.com/fwlink/?LinkId=866544) for "capacity and entitlements". Anything precise — profile counts, add-on pack sizes, minimum purchase — is only in that PDF, and it is reissued regularly.
The Data app is reached at home.ci.ai.dynamics.com with a work or school account. A first sign-in gives you an environment with sample data.
Installing Data requires an existing Dataverse environment that does not already have Customer Insights - Data installed. One install per Dataverse org.
Customer Insights - Data administrators are automatically given the Dataverse System Administrator role. An admin without a Dataverse licence still gets Administrative access only, not read-write.
Region, storage option and Dataverse settings are fixed at environment creation. Name, default-environment flag and owner are the only things you can edit afterwards.
Sandbox environments do not support scheduled refresh. Production environments are the ones with full scale and scheduling.
Learn does not publish a maximum number of Customer Insights environments per subscription. Treat any number a stakeholder quotes as coming from the licensing guide or a deal sheet, and go and check it.

When to use / skip

There is nothing optional here — if the client is buying Customer Insights at all, this is the shape of what they are buying, and you need it straight in week one. The reason it matters on delivery is that the per-tenant model quietly changes who you have to talk to. On a per-user product you scope by headcount; here you scope by data volume and by how many environments you want, and neither of those is a conversation the client's licensing contact usually expects. Get it out of the way before the unification design starts, because the answer to "how many profiles are we entitled to" determines whether you unify the whole customer base or a filtered slice of it.

Skip the detail only if you are on a pure Journeys engagement that never touches unified profiles — even then, the interacted-people quota is shared, so you will be back.

Configuration decisions

How many Customer Insights environments the engagement needs, and which of them are sandbox versus production — sandbox loses scheduled refresh, which shapes what you can actually rehearse in test.
Which Dataverse organisation each app lands in. Data and Journeys in the same org is simpler for profile-to-contact work; separate orgs give you cleaner ALM boundaries.
Region for each environment, chosen once and not changeable. If you are also bringing your own storage, the storage account must match, so decide both together.
Whether Customer Insights administrators get a Dataverse licence. Without one they are administrative-only, which is enough to configure and not enough to inspect data.
Who owns each environment. Ownership is a single user, not a group, and it drives reset and delete rights.
Whether the client starts on a trial or goes straight to a paid production environment, given a trial cannot be converted in place.

Gotchas

Region, storage option and Dataverse binding are one-way doors. Getting any of them wrong means a new environment and a configuration copy, not a settings change.
A single environment owner is a real operational risk. If that person leaves and their account is deleted, another admin has to use the Take ownership button that appears at the top of the pages — worth writing into the runbook rather than discovering it during a handover.
Deleting an environment from inside Customer Insights is possible but Microsoft points you at the Uninstall option in the Power Platform admin center instead. Use their route; the in-app delete is owner-only and leaves less of a trail.
Admins with no Dataverse licence hit a confusing wall: they can see configuration screens but not the data those screens describe. It reads like a permissions bug and is not one.
The licensing guide is the authority and it moves. A statement of work that quotes entitlement figures inline will be wrong within a couple of release waves. Reference the guide by name and date instead.
Sandbox environments quietly cannot run a scheduled refresh, so a "we tested it in test" claim about overnight refresh timing is not evidence of anything.

Consultant notes

Ask the client for their own order confirmation or CSP subscription detail early, plus the current licensing guide. Do not price from memory and do not repeat list prices in delivery documents — you will be held to them.
Demo the environment picker and the Edit environment pane together. Seeing which fields are greyed out after creation communicates the one-way doors better than any slide.
Push back on requests to spin up extra environments casually. Each one carries a Dataverse org, a region decision and a share of tenant capacity, and the tidy-up later is not free.
Before go-live, confirm every named administrator has a Dataverse licence, and confirm the environment owner is someone who will still be there in six months.
If the client's licensing is being handled by a partner or reseller, get the entitlement figures in writing from them. Learn will not back you up.

Worth another look whenever Microsoft reissues the Dynamics 365 Licensing Guide, or if the per-tenant model changes shape in a release wave.