Dynamics 365 Customer Service Professional — Nonprofit Pricing, Plans & What's Included

Dynamics 365 Customer Service Professional gives assigned nonprofit users access to the Customer Service Professional app, because it is a named-user Dynamics 365 license for standard customer service scenarios. It is commonly evaluated for case management, constituent or donor service desks, account/contact activity tracking, and knowledge-management needs, but the exact current feature entitlement should be confirmed before purchase.

The Charity license does not include implementation, migration, training, or configuration services, because the catalog SKU is a software subscription entitlement. It also does not include a qualifying Dynamics 365 base license for attach users, a trial license, or separate add-ons such as advanced digital channels, voice, AI, extra capacity, or related Microsoft services unless those are licensed separately.

Dynamics 365 Customer Service Professional is licensed per named internal user or agent, because each internal person who accesses the application needs an assigned user license. Shared logins should not be used to avoid licensing; confirm any external customer, donor, constituent, or portal-access scenario against current Microsoft Dynamics 365 licensing terms.

Yes, a nonprofit can buy the attach option only when the specific user already has a qualifying Dynamics 365 base offer, because attach licenses are dependent licenses rather than standalone access rights. Do not assign the attach SKU until IT Partner or Microsoft licensing guidance confirms that the user’s base license qualifies.

Choose the base license when the user does not already have a qualifying Dynamics 365 base license, because the base SKU provides the primary Customer Service Professional entitlement. Choose the attach license only for users who qualify through another Dynamics 365 base offer, because buying attach without eligibility can leave the user improperly licensed.

No trial SKU is shown in the current Charity catalog source for Dynamics 365 Customer Service Professional, because the listed nonprofit offers are paid subscription options. If a nonprofit wants to test the product before committing, it should ask IT Partner to confirm whether Microsoft has any separate evaluation route available at that time.

Charity pricing is available with month-to-month and annual commitment options, because the catalog includes both flexible monthly commitments and annual commitments with different billing choices. Annual upfront is the lowest per-seat catalog option shown in the source, annual commitment paid monthly runs higher than annual upfront, and month-to-month is the most flexible.

You can generally add seats during an active CSP term, because Microsoft subscription management supports increasing licenses when more named users need access. Reductions and cancellations are more restricted, especially on annual commitments, so confirm the current Microsoft CSP cancellation window and seat-reduction rules before choosing the term.

At renewal, the nonprofit can typically continue, adjust, or change eligible subscription options, because renewal is the normal point to revisit term length, billing frequency, and seat counts. Review the license mix before renewal, especially if some users can move from base to attach licensing or no longer need access.

Cancellation depends on the Microsoft CSP term and timing, because monthly and annual commitments have different flexibility. In Microsoft’s commerce model, cancellation and seat reductions are usually most flexible near purchase or renewal and more limited after the cancellation window, so verify the current rules with IT Partner before ordering.

A properly handled CSP partner transfer or new CSP relationship should not require moving Dynamics 365 data, because the Microsoft tenant and Dynamics environment remain in place. IT Partner should coordinate the timing with the current partner and renewal dates so billing and administration change cleanly without interrupting user access.

For the same Microsoft SKU, segment, term, and billing option, the Microsoft catalog price basis should be the same, because CSP partners transact Microsoft’s published cloud subscriptions rather than creating a different product entitlement. Any final invoice can still depend on tenant eligibility, taxes, term selection, proration, and partner-specific services, so confirm the quote before transfer.

No, Dynamics 365 Customer Service Professional does not by itself include a Microsoft Teams license, because Teams is normally licensed through Microsoft 365 or another eligible plan. Dynamics 365 and Teams can be used together for collaboration scenarios where supported, but the nonprofit must ensure users have the required Teams/Microsoft 365 licensing and configuration.

Do not assume every Copilot or AI capability is included, because Microsoft’s Dynamics 365 AI features can depend on product edition, geography, tenant settings, prerequisites, and separate licensing. A nonprofit should confirm the current Customer Service Professional entitlement and any required Copilot, AI, or capacity add-ons before purchase.

Advanced omnichannel, digital messaging, and voice capabilities should not be assumed to be included, because Microsoft often licenses those workloads or add-ons separately from the core Customer Service Professional entitlement. If the nonprofit needs live chat, SMS, social messaging, voice, or contact-center routing, confirm the correct Dynamics 365 Customer Service, Digital Contact Center, or add-on licensing path first.

Dynamics 365 Customer Service Professional uses Microsoft cloud identity and application security controls, because access is assigned through licensed users and governed by Microsoft Entra ID, Dynamics 365/Dataverse security roles, and tenant administration. Nonprofits should still design role-based access, environment governance, data-loss-prevention policies, and audit practices appropriate to their donor, client, or constituent data.

It may be suitable for many nonprofit service and donor-support scenarios, because Dynamics 365 runs on Microsoft’s cloud compliance and security framework. However, compliance is shared between Microsoft, the tenant administrator, and the nonprofit’s configuration, so organizations with regulated health, legal, child-services, government-funded, or residency requirements should validate the exact compliance obligations before deployment.

Do not assume Charity commercial nonprofit pricing applies to GCC or GCC High, because Microsoft Government cloud licensing, eligibility, residency, and availability rules are separate from standard nonprofit commercial offers. If the nonprofit is a government contractor, handles controlled government data, or requires GCC High residency or compliance, confirm the correct Government-cloud licensing path before buying this Charity SKU.

The organization must be approved for Microsoft nonprofit/Charity licensing, because the Charity SKU is intended for eligible nonprofit tenants only. Nonprofit eligibility approval is not included in the license itself, and grant or donated offers are separate from this paid Charity catalog subscription, so eligibility and available nonprofit benefits should be checked before checkout.

Start by confirming licensing, user roles, data model, and required workflows, because the subscription provides application access but not a finished service-desk implementation. Typical planning includes mapping current cases or tickets, accounts and contacts, activities, knowledge content, reporting needs, integrations, and any required add-ons before importing data or assigning users.