Dynamics 365 Sales Enterprise — Charity Pricing, Plans & What's Included

Dynamics 365 Sales Enterprise for Charity customers is the Dynamics 365 Sales Enterprise application purchased through Microsoft Non-Profit Pricing SKUs, because eligible nonprofits can buy charity-priced versions of the standard user license, attach license, or device license. It is not a separate product called “Sales Enterprise for Nonprofits,” so nonprofit-specific fundraising, donor, or grant-management scenarios should be validated before purchase.

Eligible Charity customers can choose a standard Dynamics 365 Sales Enterprise user SKU, an attach SKU, or a device edition SKU, because Microsoft lists all three Non-Profit Pricing paths for this product. The right choice depends on whether users need named-user access, whether the organization already owns a qualifying Dynamics 365 base offer, or whether a shared-device model fits the real access pattern.

The Dynamics 365 Sales Enterprise Charity license includes access to the Dynamics 365 Sales Enterprise product under the selected nonprofit SKU, because the Charity offer is a licensing and pricing path for the Sales Enterprise application. Buyers should still confirm the current Microsoft entitlement list before relying on a specific AI, forecasting, or revenue-intelligence feature, because Microsoft can package advanced capabilities differently across Sales editions and add-ons.

Dynamics 365 Sales Enterprise Charity licensing does not include nonprofit eligibility approval, implementation services, data migration, Microsoft 365 licensing, or other Dynamics 365 workloads, because it is a license for the Sales Enterprise application only. It also should not be assumed to include out-of-box donor management, grant management, sponsorship, major-gift, or fundraising-management functionality; those scenarios may require configuration, another product, or a separate service engagement.

Only organizations approved for Microsoft Charity or nonprofit licensing are eligible, because the listed offers are Non-Profit Pricing SKUs. Eligibility is not granted by buying the license itself, so the purchasing organization should confirm its current Microsoft nonprofit status before ordering through IT Partner or any CSP provider.

Maybe, but it must be confirmed before purchase, because Microsoft nonprofit grants, discounts, and eligible workloads can vary by program, country, tenant status, and current Microsoft policy. A Charity price on the CSP list does not automatically mean the license is covered by a grant, so the organization should verify grant applicability in the Microsoft nonprofit process or with IT Partner.

A nonprofit should choose the Dynamics 365 Sales Enterprise attach SKU only when it already has a qualifying Dynamics 365 base offer for the same licensed user, because attach licensing is a discounted secondary-license model tied to base-license eligibility. If the qualifying base license is missing or assigned to a different user, the standard Sales Enterprise Charity SKU is usually the safer licensing path.

A nonprofit should choose the device license only when access is primarily through a shared device and the device-use rules fit the organization’s workflow, because device licensing is a separate model from named-user licensing. If staff members need access across personal laptops, phones, and browsers, named-user licensing is usually easier to manage and should be compared with IT Partner before purchase.

The listed Charity SKUs include monthly-commitment monthly billing and annual-commitment options with either annual billing or monthly billing, because Microsoft publishes those purchase paths for this product. Annual commitment with annual billing is the lowest-cost option shown, annual commitment paid monthly costs more, and monthly commitment provides the most flexibility.

Yes for flexible monthly commitments at the next applicable renewal point, but annual commitments are more restrictive, because Microsoft CSP subscription terms generally lock the commitment for the term after the allowed cancellation window. Seat increases are typically easier than seat reductions, so nonprofits should size annual commitments carefully and use the live configurator or IT Partner to confirm current New Commerce rules.

No trial is listed for the Dynamics 365 Sales Enterprise Charity SKUs in the current source data, because the published Charity rows are paid nonprofit offers rather than trial offers. If a nonprofit wants to evaluate the product first, it should ask IT Partner about Microsoft evaluation options, demos, or a pilot subscription before committing broadly.

No, Dynamics 365 Sales Enterprise Charity does not include Microsoft Teams licensing by itself, because it is a Dynamics 365 Sales application SKU rather than a Microsoft 365 or Teams bundle. Teams collaboration can be used when the organization has the required Microsoft 365 or Teams licenses and the integration is configured correctly.

Do not assume all Copilot, Sales Premium, forecasting, or revenue-intelligence features are included, because advanced AI and premium sales capabilities may be separately licensed or edition-specific. Before buying based on an AI requirement, the nonprofit should confirm the current Microsoft Sales Enterprise entitlement list and any required Copilot, Microsoft 365, or add-on licenses with IT Partner.

Yes, Dynamics 365 Sales Enterprise can integrate with Microsoft 365 experiences such as Outlook and Teams when the required Microsoft 365 services are licensed and configured, because those services are separate from the Sales Enterprise license. The Sales SKU should not be treated as including Exchange, Outlook desktop apps, Teams, or Microsoft 365 identity services unless those are licensed separately.

Dynamics 365 Sales Enterprise uses Microsoft cloud identity, environment, and role-based access controls, because it runs on the Dynamics 365 and Dataverse platform. Nonprofits should configure Microsoft Entra ID, multifactor authentication, security roles, auditing, data-loss-prevention policies, and environment governance according to their risk profile rather than assuming the license alone creates a compliant deployment.

It may support regulated-data programs when configured properly, but compliance is not guaranteed by the license alone, because obligations depend on tenant configuration, data location, access controls, contracts, and the specific regulation. Nonprofits handling health, financial, child, donor, or government-funded program data should validate Microsoft compliance commitments and implementation design before purchase.

Not automatically, because Charity eligibility and Government cloud eligibility are separate Microsoft programs and cloud environments. If a nonprofit has government contract, residency, GCC, or GCC High requirements, it should confirm cloud availability, tenant type, and licensing eligibility with IT Partner before buying a standard Charity SKU.

A nonprofit should plan migration as a separate project, because the Dynamics 365 Sales Enterprise license does not include data cleansing, mapping, import, deduplication, customization, or user training services. IT Partner can help scope whether standard Sales tables meet the requirement or whether donor, grant, event, or fundraising processes need configuration or another solution.

Yes, a properly executed CSP transfer can typically be done without user downtime, because the Microsoft tenant, users, and Dynamics 365 environments remain in place while the CSP relationship or subscription management changes. The Microsoft-published nonprofit SKU basis remains the same, but the final CSP quote, partner services, and transfer timing should be confirmed before initiating the move.

No, the Charity SKU is for eligible nonprofit organizations only, because Microsoft publishes separate licensing segments for Charity, Commercial, Education, and Government customers. Schools should validate Education licensing and any student-versus-faculty rules, government entities should validate Government or GCC options, and standard businesses should use Commercial licensing rather than nonprofit pricing.