Dynamics 365 Unified Operations Sandbox Tier 5: Premier Performance Testing for Government — Pricing, Plans & What's Included

Dynamics 365 Unified Operations Sandbox Tier 5: Premier Performance Testing for Government is a non-production sandbox environment subscription, because it is listed as a Government-segment Dynamics 365 Operations sandbox offer. It is intended for eligible government customers that need a Tier 5 Premier Performance Testing sandbox for Dynamics 365 Unified Operations scenarios, not for production application use.

This subscription includes the Dynamics 365 Unified Operations Sandbox Tier 5: Premier Performance Testing environment entitlement, because the catalog offer is specifically a sandbox/performance testing add-on. It provides access to the Governmental Community Cloud purchasing path for eligible Government customers, subject to Microsoft availability and tenant requirements at order time.

Production Dynamics 365 application licensing is not included, because this SKU is a sandbox/performance testing add-on rather than a Finance, Supply Chain Management, Commerce, or Human Resources user license. User licenses, other Dynamics 365 apps, Microsoft 365, Teams, Copilot, Azure services, and third-party testing tools must be licensed separately if required.

No, this SKU should not be used as a production environment, because it is explicitly a Sandbox Tier 5: Premier Performance Testing offer. Government buyers should confirm their production Dynamics 365 application licenses and environment entitlements separately before ordering this add-on.

Eligible Government customers can buy this offer, because the catalog availability shown for this SKU is limited to the Government segment. IT Partner should confirm the organization’s Government eligibility, tenant type, and applicable government cloud purchasing requirements before the order is placed.

Do not assume GCC or GCC High from the SKU name alone, because the source catalog identifies the offer as Governmental Community Cloud Pricing but does not specify the exact cloud environment or residency boundary. Government buyers should confirm with IT Partner and Microsoft which government cloud environment, tenant type, and data residency requirements apply before purchase.

No, Microsoft Teams is not included, because this is a Dynamics 365 Unified Operations sandbox environment subscription rather than a Microsoft 365 collaboration license. If project users need Teams for testing coordination, meetings, or collaboration, those rights must come from separate Microsoft 365 or Teams licensing appropriate for the government tenant.

No, Copilot is not included by this sandbox SKU, because the offer is for a Tier 5 Premier Performance Testing sandbox environment and not a Copilot license. Copilot availability in government clouds, prerequisites, data boundaries, and licensing can differ by service, so IT Partner should validate any Copilot requirement separately.

User and application prerequisites may be required, because this sandbox add-on does not grant production application or user rights by itself. Before ordering, IT Partner should verify the customer’s Dynamics 365 application licensing, tenant configuration, and Microsoft environment setup requirements for the intended Unified Operations workload.

Potentially yes, if the planned activity fits Microsoft’s current rules for this specific sandbox tier, because the offer is positioned for Premier Performance Testing. Government customers should confirm supported testing activities, performance limits, capacity specifications, and provisioning rules with IT Partner before relying on it for go-live or major release validation.

This Government sandbox is purchased as a sandbox environment subscription, because the unit of measure is not a user seat. The catalog supports different commitment and payment structures, including monthly commitment paid monthly, annual commitment paid upfront, and annual commitment paid monthly, with final availability verified at quote or order time.

No, the catalog does not show a trial for this Government SKU, because the source data marks the offer as not having a trial. Buyers should plan procurement around a paid subscription term rather than a trial conversion path.

Start by confirming eligibility, prerequisites, and the required government cloud environment, because provisioning depends on the customer’s tenant and Microsoft’s current Dynamics 365 environment rules. IT Partner can help validate the SKU, term, billing option, and order details, then coordinate the steps needed to make the sandbox available for the Dynamics 365 project team.

A move may be possible, but it should be planned as an environment and licensing change rather than assumed as an automatic in-place upgrade, because Microsoft provisioning rules and Dynamics 365 environment constraints can vary. IT Partner should review the existing sandbox, tenant, project stage, data needs, and current Microsoft guidance before recommending the safest path.

It should not directly affect production use, because this SKU is a non-production sandbox subscription. However, performance testing, data refreshes, integrations, and release validation can interact with project processes, so administrators should plan environment access, data handling, and test schedules carefully.

A CSP partner change is typically a commercial administration change rather than a tenant migration, because the Microsoft tenant and cloud services remain in place. IT Partner should validate the current subscription state and transfer path, but the goal is to avoid service downtime while moving CSP management to IT Partner.

The underlying Microsoft Government catalog offer should remain the same when the same SKU and term are used, because a CSP management change does not require changing the product identity. Final quoted partner pricing, taxes, billing setup, and any term restrictions should still be confirmed before transfer.

Renewal follows the selected CSP subscription term and Microsoft commerce rules, because the offer can be purchased under different commitment and payment structures. Government buyers should review renewal date, auto-renewal status, billing frequency, and any planned environment changes with IT Partner before the renewal window.

Cancellation is governed by Microsoft CSP and the selected subscription term, because annual and monthly commitments have different commercial rules. IT Partner should confirm the applicable cancellation window, refund eligibility, and end-of-access timing before purchase and again before attempting cancellation.

This is not managed like a user-seat license, because the unit is a sandbox environment subscription rather than individual users. Any quantity, environment, or tier change should be validated with IT Partner against Microsoft’s current CSP rules and Dynamics 365 environment provisioning requirements.