MSP operations teams and internal IT service owners
Assign Azure retirement work across tenants without losing the evidence
Use ownership, internal deadlines and completion evidence to move a sourced retirement notice through a multi-tenant team’s workflow.
Published by Arctic Parade LTD · Updated 2026-09-17 · Sources and editorial process
Define the estate boundary first
A workspace is the organisation using the review tool. A customer or business unit is the estate being managed. Azure tenants and subscriptions provide additional identity and resource boundaries. Write down that mapping and who is authorised to review each subscription. Signing into a workspace does not grant permission to read a customer tenant.
Use an investigation state before assigning migration work
A catalogue match is a reason to inspect the resource, not proof that a configuration is affected. Keep needs-review, confirmed-affected and reviewed-not-applicable decisions distinct. Assign the investigation as well as the eventual migration. Record the source, the configuration inspected and the reason for the decision so a service lead can understand the handoff.
Give the work one owner and an achievable target
Choose one accountable owner even if several engineers contribute. Keep the internal target separate from the vendor deadline and include a test and rollback step. If the customer must approve downtime, make that an explicit dependency. Do not use a target date as a substitute for agreement on the migration scope.
Require evidence before closure
A recommendation disappearing from a successful snapshot warrants review. It can reflect changed provider observations or scope; it is not automatically proof that an application has migrated. Record the completed change and relevant checks before resolving. If the same recommendation returns, reopen the action and preserve the earlier completion evidence instead of silently overwriting it.
Practise the handoff without a customer tenant
The Arctic Parade sample estate lets you assign a fictional action, simulate recommendation disappearance, record completion and simulate return. These inputs exercise the application workflow and are clearly labelled. They do not validate live Azure authentication, permissions or coverage. Start with that controlled exercise before bringing authorised customer inventory.
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.