Dynamics 365 Customer Insights — Pricing, Plans & What's Included

Dynamics 365 Customer Insights is a Microsoft Dynamics 365 offering for organizations that want to unify customer data and use it to support targeted, personalized engagement, because the Commercial catalog includes options for Customer Insights, Data capacity, Journeys capacity, Attach scenarios, and user licensing. It is best evaluated as a customer data and journey-orchestration purchase, not as a generic Dynamics 365 user license.

You receive only the specific Commercial SKU option and term you purchase, because the catalog separates Dynamics 365 Customer Insights, Customer Insights Attach, Data T1/T2/T3 Unified People, Journeys T1/T2/T3 Interacted People, and Customer Insights User License. The exact capacity, usage rights, and user access should be confirmed against current Microsoft licensing terms before checkout.

Implementation services, data cleansing, integrations, campaign operations, and licenses for other Dynamics 365 apps are not shown as included, because the supplied catalog data lists subscription SKUs rather than deployment services or bundled application licenses. Capacity beyond the purchased tier is also not established by the catalog data and should be validated before purchase.

You should choose the SKU based on the workload you need, because the Commercial catalog separates the base Customer Insights option from Data tiers measured as Unified People, Journeys tiers measured as Interacted People, Attach, and user licensing. IT Partner should review your tenant, data volume, journey activity, and any prerequisite licenses before you buy.

The Data T1, T2, and T3 SKUs are capacity-tier options measured as Unified People, because the Commercial catalog labels them as Customer Insights Data tiers. The source catalog provides the tier names but not the included quantity definitions, so the current Microsoft licensing terms should be checked before selecting a tier.

The Journeys T1, T2, and T3 SKUs are capacity-tier options measured as Interacted People, because the Commercial catalog labels them as Customer Insights Journeys tiers. The supplied data does not define the exact included quantities or counting rules, so buyers should confirm Microsoft’s current licensing definitions before ordering.

Dynamics 365 Customer Insights Attach is a Commercial catalog option for attach scenarios, because Microsoft lists it separately from the standard Customer Insights, Data, Journeys, and User License SKUs. Attach eligibility can depend on the customer’s existing Microsoft licensing position, so it should be verified against the tenant and current licensing terms before purchase.

Not by itself, because the User License SKU is listed separately from the Customer Insights, Data, Journeys, and Attach capacity SKUs. It should be treated as a user-access licensing component whose exact rights must be confirmed with the selected Customer Insights SKU and current Microsoft licensing terms.

No Commercial trial SKU is listed in the supplied catalog data, because every Commercial option shown is marked as non-trial. If a trial-first evaluation is required, confirm current Microsoft trial availability or use a guided requirements review before purchasing a paid CSP subscription.

Commercial purchasing supports month-to-month, one-year, and three-year commitments, because the catalog includes monthly, annual, and three-year term structures. One-year terms can be paid annually or monthly, while three-year terms can be paid annually, monthly, or triennially; upfront billing is usually the stronger cost posture, while monthly billing improves cash-flow flexibility.

Cancellation and reduction rights depend on the CSP term and Microsoft new commerce rules, because annual and three-year commitments generally limit mid-term decreases compared with month-to-month subscriptions. Increases are usually easier than reductions, so capacity tiers, Attach eligibility, and user licensing should be validated before checkout and again before renewal.

Yes, additional capacity or higher-tier purchases are typically possible through the CSP lifecycle, because the Commercial catalog includes multiple Data and Journeys tier options. The right change path depends on the exact SKU, term, billing schedule, and Microsoft’s current subscription-change rules, so IT Partner should confirm the order mechanics before changes are made.

No Teams license is shown as included in the supplied Dynamics 365 Customer Insights catalog data, because the listed Commercial SKUs are Customer Insights, Data, Journeys, Attach, and User License options. If your marketing or collaboration process depends on Teams, license Teams separately through the appropriate Microsoft 365 or Teams plan and confirm integration requirements.

Do not assume Copilot licensing is included, because the supplied catalog data does not list a Copilot SKU or entitlement as part of these Customer Insights options. Some AI-assisted capabilities may depend on product availability, tenant settings, geography, and separate Microsoft licensing, so confirm current Copilot requirements before purchase.

Review data sources, consent and compliance requirements, messaging channels, Dataverse, Power Platform, Azure usage, and identity configuration, because Customer Insights projects usually depend on more than the subscription SKU itself. The catalog does not include implementation or integration work, so prerequisites should be mapped before checkout.

Dynamics 365 Customer Insights runs in Microsoft’s cloud ecosystem and uses tenant-level security controls such as Microsoft Entra ID, because access and data governance are managed through the customer’s Microsoft environment. Buyers still need to configure roles, data ingestion, consent, retention, and compliance processes for their own use case.

Not automatically, because the Commercial SKU path is for standard Commercial organizations and is not the same as a government cloud purchasing motion such as GCC or GCC High. Government buyers or regulated entities with specific residency, compliance, or sovereign-cloud requirements should confirm the correct Microsoft cloud and SKU availability before buying.

They may be able to buy Commercial SKUs, but they should not assume nonprofit or education eligibility benefits apply, because the supplied catalog separates Commercial from Charity and Education segments. Nonprofits should validate Charity eligibility and any grant context, while schools should confirm whether the buyer is an institution, faculty, staff, or student scenario before choosing a segment.

Start with a requirements review, because the correct purchase depends on whether you need Customer Insights, Data capacity, Journeys capacity, Attach, user licensing, or a combination. A practical first step is to inventory data sources, customer identity strategy, consent rules, expected audience size, journey volume, and required integrations before selecting the CSP SKU and term.

A CSP partner transfer is normally an administrative change rather than a tenant migration, because the Microsoft tenant, users, and service data remain in place. The selected Microsoft catalog SKU and term should stay aligned during the transfer, but IT Partner should confirm the subscription details, renewal date, and final invoice terms before the move.