THE FIELD GUIDES
Practical processes for the people responsible for several estates.
MSP service leads and internal cloud operations teams
A practical process for turning Azure retirement notices into owned, source-backed migration work across customer or business-unit tenants.
Read the guide →Azure administrators reviewing lifecycle exposure
Understand the different evidence you get from a published retirement catalogue, Azure Advisor recommendations and Service Health notices.
Read the guide →Teams importing their first estate into Arctic Parade
Build a useful, minimal inventory export with stable resource IDs, tenant context and enough detail to investigate lifecycle notices.
Read the guide →MSPs, group IT teams and cloud platform owners
A shared workflow for MSP customer estates and internal IT teams responsible for several tenants or business units.
Read the guide →Subscription administrators and MSP cloud operators
Set up an authorised read-only Azure application, map a subscription to a customer and understand sync evidence.
Read the guide →MSP account managers, service leads and Azure engineers
A practical customer-review format that separates confirmed impact from investigation and gives each Azure retirement an owner, deadline and next step.
Read the guide →MSP operations teams and internal IT service owners
Use ownership, internal deadlines and completion evidence to move a sourced retirement notice through a multi-tenant team’s workflow.
Read the guide →Azure engineers reviewing noisy lifecycle queues
Distinguish repeated inventory rows, separate retirement features and broad service-review candidates before treating an action count as affected resources.
Read the guide →MSP administrators evaluating shared lifecycle workflows
Choose workspace roles, invite colleagues safely and plan offboarding without confusing screen masking, account access and Azure permissions.
Read the guide →