MSP service leads and internal cloud operations teams
An Azure retirement checklist for multi-tenant teams
A practical process for turning Azure retirement notices into owned, source-backed migration work across customer or business-unit tenants.
Published by Arctic Parade LTD · Updated 2026-09-17 · Sources and editorial process
Start with the tenant and subscription list
Write down the tenants and subscriptions you are responsible for, their business owners, and where you have permission to review them. Record missing access as a gap. An empty result from one subscription says nothing about subscriptions you have not checked.
Gather the notices and keep their dates
Review Azure Advisor retirement recommendations and the original retirement guidance. Capture the feature being retired, the stated date, the source URL and the date you checked it. A service name alone is not enough: a notice can apply to an SDK, authentication method, runtime version, tier or networking feature rather than the entire service.
Separate discovery from confirmed impact
Create three states in your working process: needs review, confirmed affected, and reviewed not applicable. Compare the notice with the actual resource configuration. For application changes, check the deployed code or dependency manifest as well as the Azure resource. A current resource can still use an old client library.
Assign one accountable owner
For each confirmed item, record the customer or business unit, resource, owner, migration task, test plan and target completion date. Set your internal date earlier than the vendor date to allow validation and rollback. Keep the evidence for a not-applicable decision so the next reviewer does not repeat the investigation.
Close the loop after deployment
Verify the new configuration, run the relevant application tests and update inventory. Preserve the original notice and the change record. Mark the work complete only after the affected path has been tested; a planned change window is not a completed migration.
Use Arctic Parade as a review queue
The current product imports CSV inventory and presents service-level review candidates from the published Microsoft catalogue. Those candidates require confirmation. An authorised Azure connection can add tenant-specific Advisor evidence; the workflow is not a guarantee that all retirements have been discovered.
Sources and further reading
Related field guides
Put the process to work.
Explore the current Azure retirement catalogue, then try a small estate scan. Read the coverage limits before acting on a match.