Azure Partner Shared Services is retiring on June 30, 2027. Microsoft’s November 18, 2026 announcement makes this an operational deadline for CSP direct bill partners and CSP distributors with APSS subscriptions—not just a change to a legacy price list.
Any workload that needs to continue must be moved before retirement. Remaining subscriptions will be disabled on July 1, 2027, and Microsoft says they cannot be reactivated. Partners should therefore start with subscription discovery and workload ownership, then build an exit plan around application continuity and data protection.
Which subscriptions are affected?
The announcement concerns Azure Partner Shared Services, identified by offer MS-AZR-159P. Microsoft describes APSS as a legacy Azure product predating the 2022 transition to the new commerce experience for CSP partners.
The affected audience is CSP direct bill partners and CSP distributors that have these subscriptions. This should not be read as a retirement notice for every Azure subscription sold or managed through CSP.
The first task is to establish whether the organization actually holds APSS subscriptions. Identify them by the stated offer rather than relying only on subscription names, which may reflect internal naming conventions instead of the commercial product.
The dates partners need to track
| Date | Announced change | Practical implication |
|---|---|---|
| January 4, 2027 | New APSS subscription creation ends | Do not plan new deployments around additional APSS subscriptions. |
| February 1, 2027 | The APSS Legacy Pricelist is removed from Partner Center | Review internal processes that depend on that price list. |
| June 30, 2027 | APSS retires | Move retained workloads or shut them down beforehand, with required data backed up. |
| July 1, 2027 | Remaining APSS subscriptions are disabled | Resources stop and are deallocated; deployment is blocked and reactivation is unavailable. |
Set an internal completion target ahead of retirement. The extra time is for testing and resolving dependencies, not an assumed Microsoft grace period.
What happens if a partner does nothing?
Microsoft says that when the remaining subscriptions are disabled, resources are stopped and deallocated, new resources cannot be deployed, and no further charges accrue. Disabled APSS subscriptions cannot be reactivated.
The end of charging is not a continuity feature. A workload that depends on those resources will not be protected merely because its subscription remains visible in an inventory.
The announcement also warns about data loss and links to Microsoft’s data management guidance. It does not provide a universal resource-by-resource deletion timeline in the notice itself. Do not build a recovery plan around an assumed retention window after retirement.
Review Microsoft’s data management information, but treat migration and verified backups before the deadline as the primary controls.
Where Microsoft says to move retained workloads
Microsoft directs partners to move workloads they want to keep to a direct agreement or a Microsoft Customer Agreement for Enterprise, or MCA-E.
That statement identifies destination agreement options; it is not a guarantee that every workload can be moved using a single subscription transfer or a uniform resource-move operation. The announcement does not specify a technical migration mechanism for each Azure service.
Before committing to a method, review the APSS retirement guidance and confirm the supported route for the affected subscriptions and resources. Validate the destination commercial arrangement as well as the technical migration path.
Partners should not substitute an assumed destination merely because another Azure subscription type is familiar. Where eligibility or the migration route is unclear, resolve it before scheduling the cutover.
Build a workload-level exit inventory
A subscription list is necessary, but it is not enough to control the project. For each APSS workload, record:
- The subscription and resource groups involved.
- The business and technical owners.
- Whether the workload will be retained or retired.
- Dependencies on other workloads, connectivity, identities, and external integrations.
- The proposed destination and supported migration approach.
- Backup, validation, and cutover requirements.
- A target completion date and a named owner for sign-off.
These are recommended planning fields, not additional requirements stated in the announcement. Their purpose is to prevent a subscription from appearing “handled” while an overlooked dependency remains active inside it.
Pay particular attention to shared infrastructure. A resource with low direct usage may still support authentication, connectivity, automation, or monitoring for another service.
Test continuity, not just resource presence
For retained workloads, define acceptance criteria before moving anything. A successful project should demonstrate that the application works from its intended access paths, dependencies are reachable, and the operating team can monitor and support it in the destination.
Where the supported migration method requires rebuilding or data transfer, account for synchronization and cutover behavior. Where resource moves are supported, validate the limitations for the specific resources involved rather than assuming support across the entire subscription.
Recommended checks include application functionality, identity and access, network reachability, backup operation, monitoring, and billing ownership. The relevant checks will vary by workload.
Keep the old and new operating arrangements understandable throughout the transition, and establish contingency options appropriate to the supported method. Do not treat reactivation after July 1 as a fallback: Microsoft explicitly rules it out.
Retiring workloads still need an owner
If a workload is no longer needed, confirm that decision with its business owner and identify any data that must be retained. Complete backups before retirement and, where recovery matters, validate that the data can actually be restored.
Also document downstream dependencies before shutting resources down. A planned retirement should be an intentional service change, not an untested assumption that nobody uses the workload.
Bottom line
APSS retirement has a clear consequence: remaining subscriptions are disabled on July 1, 2027, without reactivation. Partners with offer MS-AZR-159P should inventory now, confirm supported destinations and migration routes, and finish workload moves or backed-up shutdowns before June 30. The objective is verified continuity or deliberate retirement—not simply an empty task list.