Dynamics 365 Customer Insights — Charity Pricing, SKUs & Billing Options

Dynamics 365 Customer Insights for Charity / Non-Profit Pricing is a Microsoft CSP catalog offer set for eligible nonprofit organizations, because the source catalog lists Charity-specific SKUs for Dynamics 365 Customer Insights. The catalog includes separate options for Customer Insights, Attach, Data Unified People tiers, Journeys Interacted People tiers, and a User License SKU, but it does not define product capabilities or bundled entitlements.

The Charity catalog includes multiple Dynamics 365 Customer Insights SKU types, because the source lists the base Customer Insights SKU, an Attach SKU, Customer Insights Data Unified People tier SKUs, Customer Insights Journeys Interacted People tier SKUs, and a Customer Insights User License SKU. These are listed as separate purchasable catalog entries, so do not assume they are bundled together unless IT Partner confirms the licensing rules for your tenant.

Not necessarily, because the source catalog lists separate Charity SKUs rather than stating that all options are bundled together. A buyer should confirm which combination is required for their scenario, especially where Customer Insights, Attach, Unified People, Interacted People, and User License options appear together in the catalog.

The catalog shows both a Dynamics 365 Customer Insights SKU and a Dynamics 365 Customer Insights Attach SKU, but it does not specify the entitlement differences or prerequisite licenses. Treat the Attach SKU as needing validation before ordering, because attach offers commonly depend on qualifying base licenses and the source does not document those requirements.

Customer Insights Data Unified People tiers are catalog-listed Charity capacity options, because the source includes T1, T2, and T3 Unified People SKUs. The source does not define tier thresholds, included capacity, or overage behavior, so IT Partner should confirm the correct tier before purchase.

Customer Insights Journeys Interacted People tiers are catalog-listed Charity capacity options, because the source includes T1, T2, and T3 Interacted People SKUs. The source does not define how an interacted person is counted, what each tier includes, or what happens if usage exceeds the tier, so those details should be confirmed before quoting.

No trial SKU is present in the provided Charity catalog, because every listed Charity entry is marked as non-trial. If a nonprofit wants to evaluate the service before committing, IT Partner should confirm whether Microsoft has a separate evaluation path outside this specific catalog offer set.

The Charity catalog includes one-month, one-year, and three-year commitment terms, because those terms are listed across the available SKUs. One-month terms bill monthly; one-year terms can bill monthly or annually; and three-year terms can bill monthly, annually, or triennially, depending on the SKU option. Confirm the exact term and billing schedule at quote time because longer-term monthly-billed options can differ from annual or triennial billing options.

Charity / Non-Profit Pricing is intended for eligible nonprofit organizations, because the catalog entries are explicitly labeled for nonprofit pricing. Eligibility is not defined in the source catalog, so the customer tenant’s nonprofit validation status should be confirmed before quoting or ordering. Nonprofit grants, discounts, and licensing eligibility are separate checks and should not be assumed from the SKU name alone.

Do not assume GCC or GCC High availability, because the source catalog shows Charity, Commercial, and Education segments but does not show Government availability for this product. If the nonprofit requires GCC, GCC High, or specific government cloud residency, IT Partner should verify availability and compliance requirements in Microsoft’s current government cloud licensing documentation before quoting.

The source catalog does not state that Microsoft Teams is included, because it only lists Dynamics 365 Customer Insights-related SKUs and capacity/user-license options. If Teams integration, collaboration, or webinar functionality is required, confirm the separate Teams licensing and any integration prerequisites before purchase.

Copilot inclusion is not confirmed by the source catalog, because the catalog does not list Copilot entitlements, AI feature availability, or required add-ons. If the buying decision depends on Copilot, generative AI, or automation features, IT Partner should verify Microsoft’s current product documentation and licensing terms for the tenant and region.

Some options may require prerequisites, but the source catalog does not identify them, because it only lists the available Charity SKUs and not their dependency rules. The Attach SKU, capacity tiers, communication services, and User License SKU should all be reviewed before ordering so the nonprofit does not buy an incomplete or non-assignable configuration.

The Charity catalog includes a Dynamics 365 Customer Insights User License SKU, but the source does not state its assignment model, usage requirement, or relationship to capacity SKUs. Do not treat it as proof that every user is fully licensed for all Customer Insights capabilities; confirm the licensing role of this SKU with IT Partner before deployment.

Security and compliance capabilities must be confirmed from Microsoft’s current service documentation, because the source catalog only provides licensing SKU, term, and billing information. Dynamics 365 services generally operate within Microsoft cloud compliance and identity frameworks, but specific requirements such as data residency, audit, encryption, retention, consent, and regulatory controls should be validated for the tenant’s region and cloud environment.

The source catalog does not confirm communication-channel inclusions or provider costs, because it only lists Customer Insights, Journeys Interacted People, Data Unified People, Attach, and User License SKUs. If the nonprofit plans to send email, SMS, or other outreach, confirm which channels are included, which require configuration, and whether any third-party or Azure-related costs apply.

Start with a licensing and data-scope review, because the Charity catalog separates Customer Insights, Data Unified People tiers, and Journeys Interacted People tiers. Before ordering, define the data sources, expected profile volume, engagement volume, user roles, and required channels, then have IT Partner confirm the correct SKU mix and any capacity implications.

A CSP reseller transfer is normally a partner-of-record and subscription-management change rather than a tenant migration, because the Microsoft cloud tenant and service data remain in place. IT Partner should still review the existing subscription term, renewal date, nonprofit eligibility, and SKU mapping before transfer so licensing continuity is maintained and downtime is avoided.

A CSP transfer should be quoted from the current Microsoft CSP catalog for the same Charity SKU, term, and billing option, because the underlying Microsoft offer determines the catalog pricing basis. Any partner-specific services, support agreements, or billing policies should be separated from the Microsoft license quote so the nonprofit can compare like for like.

Renewal and cancellation rules depend on the commitment term and billing option, because the Charity catalog includes one-month, one-year, and three-year terms with different payment schedules. Reductions, cancellations, and midterm changes may be limited after the Microsoft cancellation window, so confirm the exact CSP subscription rules before purchase or renewal.