MSPs, group IT teams and cloud platform owners
Manage lifecycle changes across multiple tenants
A shared workflow for MSP customer estates and internal IT teams responsible for several tenants or business units.
Published by Arctic Parade LTD · Updated 2026-09-17 · Sources and editorial process
Distinguish the service provider from the managed estate
The organisation using Arctic Parade owns a workspace. The customers or business units inside it identify the estates being managed. A Microsoft tenant is an identity boundary; it is not automatically the same thing as a customer, subscription or business unit. Document the mapping rather than inferring it from an email domain.
Keep login and inventory permissions separate
Signing into a workspace proves an identity. Reading a customer subscription requires a separate authorisation decision. Ask which people may enter the workspace, which customer resources it may read, and who can approve that access. Treat these as separate questions in both onboarding and offboarding.
Use a common queue with explicit ownership
Standardise the information captured for a change: source, affected feature, date, customer, resource, reviewer and next action. An MSP may hand off the work to a customer engineer; internal IT may hand it to an application owner. The evidence should remain understandable after that handoff.
Plan offboarding at the same time as onboarding
Know how to revoke inventory access, remove a user, stop notifications and handle retained records. A customer leaving the service should not depend on someone remembering an old API credential. Test offboarding with a sample tenant before relying on a new connector.
Start narrow without hard-coding one provider
Use provider, account or tenant, resource ID, source and feature as explicit fields. Keep the evidence behind each provider-specific matching rule. Azure, AWS and Google Cloud expose different kinds of inventory and lifecycle information; forcing them into identical discovery behaviour hides useful differences. Arctic Parade starts with an Azure catalogue while keeping vendor-labelled inventory and source adapters separate.
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.