What it does

Customer Insights ships with a default quota of profiles and interactions attached to the tenant licence, and you raise it by buying more capacity or more licences. The numbers themselves live in the Dynamics 365 Licensing Guide, but the tenant's own purchased-versus-used figures are readable in the product, on the Journeys side, under Settings > Overview > Quota limits.

Key facts

• Quota is calculated at tenant level and tracked at environment level. That is the pooling behaviour: several environments draw on one pot rather than each getting a private allocation.
• The Quota limits page shows total purchased quota, current usage against each quota, a monthly interaction usage chart, an annual interacted-people trend, and a per-environment breakdown where the organisation has more than one environment.
• The interacted-people quota counts leads, contacts and Customer Insights profiles — but only those actually engaged through an outbound channel. A profile sitting in the database that nobody has emailed does not consume interacted-people quota.
• Contacts with no interactions for twelve months drop off the interacted-people count. The quota is a rolling engaged population, not a high-water mark.
• The monthly interaction quota is ten times the interacted-people quota and resets on the first day of each month. Interactions include email, text messages and push notifications.
• US-based instances get 1,000 free text messages a month through Azure Communication Services toll-free numbers. Paid SMS is tracked but settled with the third-party provider.
• On overage, Learn describes in-app notifications as you approach and then exceed paid consumption limits, and tells you to upgrade the subscription. It does not describe a hard cut-off, and I would not promise a client one either way without testing it.
• The unified-profile entitlement for the Data app itself is not published on Learn. It is a licensing guide figure.
• Trial, preview and paid tenants have different quota levels. Do not size from what you see in a trial.

When to use / skip

Every unification design is implicitly a capacity decision, so this is not optional reading on a Data project. The moment a client asks "can we just load all fifteen years of transaction history and every dormant account", you are in this conversation whether you wanted to be or not.

Where you can go lighter is a pure Journeys engagement with a small, stable contact base and no plans for unified profiles — the quota page still applies, but it is unlikely to be the constraint. The projects that get hurt are the ones where unification scope was agreed in a workshop, capacity was checked six weeks later by someone else, and the two numbers do not meet.

Configuration decisions

• Whether to unify the full customer base or a filtered subset. Filtering at ingestion is the cheapest lever you have and the hardest to retrofit once segments and measures depend on the wider set.
• How to treat dormant records — leaving them out of unification entirely, or unifying them and accepting they simply never become interacted people.
• Which environment does the heavy unification. Since quota pools at tenant level, a sandbox doing full-volume runs is spending the same pot as production.
• Whether to buy add-on capacity up front or start at the default and watch the Quota limits page for a quarter. The second option is honest but needs a named owner watching it.
• Who monitors quota after go-live, and on what cadence. In-app notifications only help someone who logs in.
• How multi-brand or multi-country divisions share the pooled quota, and whether anyone needs a reporting split by environment.

Gotchas

• People conflate service limits with licensing limits constantly. The 1,000 combined active segments and measures ceiling, the guidance to split calculated measures above ten million rows, and the twenty-hop relationship path limit are platform service limits — nothing to do with what you bought, and no amount of add-on capacity moves them.
• Pooled quota means one team can quietly consume another team's headroom. There is no per-environment reservation, only per-environment reporting after the fact.
• The interacted-people count is not the profile count. A client who reads the Quota limits page and concludes their unified profile count is fine has read the wrong number.
• Twelve-month drop-off cuts both ways: a dormant-reactivation campaign can pull a large population back into the count in a single send.
• The monthly interaction quota resets on the first, so a campaign calendar loaded into the last week of a month has no runway if the quota is already tight.
• Quota figures are visible in Journeys. On a Data-only engagement, nobody may have the Journeys app open at all, and the numbers go unwatched for months.

Consultant notes

• Take a screenshot of Settings > Overview > Quota limits during discovery and put the date on it. It is the only tenant-specific entitlement evidence you will get without going through procurement.
• Tell the client plainly that Microsoft publishes the counting rules but not the numbers, and that the numbers come from the licensing guide plus their own order. That framing prevents a lot of "why can't you just tell us" later.
• Push back on unifying dormant data purely because it exists. Ask what segment or measure needs it; if nobody can name one, leave it out and revisit.
• Before go-live, agree a named owner for quota monitoring and a threshold at which they escalate. In-app notifications with no owner are the same as no notifications.
• If the client is coming off a legacy separate-SKU arrangement, do not assume their old entitlement carried across. Check the current subscription rather than the folklore.

---

Worth revisiting if Microsoft surfaces profile capacity in the Data app itself, or when the licensing guide changes how interacted people are counted.