Dynamics 365 Sales Professional for Government — Pricing, Plans & What's Included

Dynamics 365 Sales Professional for Government gives a licensed named user access to the Sales Professional CRM offer through an eligible government purchase path, because the Government source pack includes the full Sales Professional SKU. It is intended for sales and relationship teams that need a streamlined Dynamics 365 sales application rather than a broader enterprise sales plan. Confirm the current Microsoft feature list before purchase if users require specific advanced sales capabilities.

Dynamics 365 Sales Professional for Government does not include a qualifying base license for the Attach SKU, because Attach is only appropriate when the same user already has an eligible Dynamics 365 base offer. It also does not include rights from other Dynamics 365 Sales plans, separate add-ons, or a trial offer. If a requirement depends on another Microsoft cloud service or an advanced sales feature, validate the needed license before ordering.

Buy the full Dynamics 365 Sales Professional for Government SKU when the user needs Sales Professional as their primary Dynamics 365 sales license, because it is the standalone licensing path in the Government source pack. Use the Attach SKU only when that same named user already has a qualifying Dynamics 365 base offer. IT Partner should review the user’s existing licenses before ordering Attach to avoid under-licensing.

No, the Dynamics 365 Sales Professional Attach SKU should not be assigned by itself, because it depends on the user already having a qualifying Dynamics 365 base offer. The base license must already exist or be purchased separately for the same named user. If the qualifying base license is uncertain, choose a licensing review before purchase.

Yes, Dynamics 365 Sales Professional is available in the Government segment in the current source pack, because both the full Sales Professional SKU and the Attach SKU are listed for Governmental Community Cloud pricing. Government eligibility, tenant alignment, and the correct purchase path still need to be validated before ordering. This is especially important if the agency has multiple tenants or special cloud requirements.

Do not assume this Dynamics 365 Sales Professional for Government offer is valid for every government cloud environment, because the source pack identifies a Governmental Community Cloud purchase path but does not prove suitability for every GCC High or specialized tenant scenario. GCC, GCC High, and other regulated government environments can have different eligibility, availability, and provisioning requirements. Confirm the tenant cloud and purchase path with IT Partner before ordering.

No single license listing should be treated as a complete data residency or compliance guarantee, because residency and compliance depend on the Microsoft cloud environment, tenant configuration, service availability, and customer requirements. Dynamics 365 Sales Professional for Government must be matched to the correct government tenant and Microsoft government cloud path. Agencies should validate residency, compliance, and contractual requirements before purchase.

No trial is shown for Dynamics 365 Sales Professional for Government in the current source pack, because the product record marks the offer as having no trial. Buyers should plan around a paid subscription rather than a trial conversion path. If evaluation is required, IT Partner can help identify the safest evaluation or pilot approach available for the agency’s tenant.

Dynamics 365 Sales Professional for Government should not be treated as including Microsoft Teams, because Teams is licensed separately through eligible Microsoft 365 or Teams offers. Dynamics 365 can integrate with Teams in supported environments, but the user still needs the appropriate Teams rights and the feature must be available in the government tenant. Confirm Teams licensing and integration availability before deployment.

No, Dynamics 365 Sales Professional for Government should not be assumed to include Copilot or Microsoft 365 Copilot for Sales, because Copilot capabilities and add-ons have separate licensing, eligibility, and government-cloud availability considerations. Some AI features may also vary by cloud, region, or tenant configuration. Confirm current Copilot availability and prerequisites with IT Partner before including it in the project scope.

Dynamics 365 Sales Professional for Government includes the rights needed for the licensed Sales Professional app, but it should not be treated as a blanket license for every Power Platform, Dataverse capacity, or Dynamics add-on, because add-ons are licensed separately when required. Extra storage, automation, integrations, portals, or premium capabilities may require additional licensing. Review the planned solution design before ordering seats.

No, Dynamics 365 Sales Professional for Government is licensed per named user, because the source pack identifies the unit of measure as a named-user subscription. Shared accounts or rotating access are not a compliant substitute for licensing each person who uses the service. Service accounts and integrations should be reviewed separately for the correct licensing model.

Getting started requires assigning licenses to named users, confirming the correct government tenant, and configuring the Sales Professional environment, because the license provides access but does not automatically design the CRM process. Agencies should plan security roles, data model, email integration, migration scope, and user training before broad rollout. IT Partner can help validate the SKU, tenant, and implementation path before the order is placed.

Yes, migration is possible, but the license purchase itself does not migrate data, because data mapping, cleansing, security design, and import tooling are implementation activities. Government buyers should review contacts, accounts, opportunities, activities, ownership, and retention requirements before migration. If the source CRM contains regulated data, confirm the target government cloud and data-handling requirements first.

Yes, a CSP transfer or partner change is typically handled at the Microsoft tenant and subscription relationship level, because the customer’s tenant, users, and Dynamics 365 data remain in place. It should not require a data migration or planned application downtime when handled correctly. IT Partner should review current subscriptions, renewal dates, and tenant access before initiating the transfer.

Moving CSP management to IT Partner does not change the underlying Microsoft product rights, because the service remains a Microsoft Dynamics 365 subscription in the customer’s tenant. Commercial terms should be quoted from the applicable Microsoft CSP government offer at the time of transfer or renewal. Validate the exact term, billing option, and any proration or renewal timing before approving the move.

Dynamics 365 Sales Professional for Government is shown with monthly commitment and annual commitment options, because the Government source pack lists both term types. Annual commitment can be billed annually or monthly, while monthly commitment may fit agencies that need a shorter commitment window. Pricing, term, and billing should be validated at quote time.

Cancellation and seat reductions depend on the Microsoft commerce term and timing, because annual commitments are less flexible than monthly commitments after the allowed cancellation or adjustment window. In general, agencies should expect to add seats during a term but reduce or cancel seats only under the applicable Microsoft rules, often at renewal or within a limited post-purchase window. Confirm the current CSP cancellation and reduction rules before ordering.

A nonprofit should not assume it qualifies for the Government Dynamics 365 Sales Professional offer, because government and charity eligibility are separate purchase contexts even though the product family is present in multiple segments. Nonprofit grant or charity pricing eligibility must be validated under the appropriate Charity or nonprofit program path, not by using a government SKU. IT Partner can help determine whether the buyer should use Government, Charity, or another segment.

Schools, students, faculty, and standard businesses should not buy the Government SKU unless they meet the applicable government eligibility and tenant requirements, because Education and Commercial are separate segments from Government. Education buyers need to validate student versus faculty licensing rules under the Education path, and commercial businesses should use the Commercial path. The correct segment matters for eligibility, provisioning, and compliance alignment.