Azure landing zones canary approach with multiple tenants
When you have multiple Microsoft Entra tenants, you can handle Azure landing zones canary environments the same way you handle them within a single Microsoft Entra tenant. If you're a multitenant ALZ consumer, follow the canary guidance in each Microsoft Entra tenant separately.
Canary Azure landing zones environment can be independently used to author and test ALZ deployments before you deploy them into the production environment. The term canary is used to avoid confusion with application development environments or test environments. This name is used for illustration purposes only.
Deployment stamps approach
If you're a customer that's following a deployment stamps pattern for each of your Microsoft Entra tenants ALZ deployments (for example, each of the ALZ deployments is the same in structure, apart from a few naming changes), you might only need to have a single canary deployment because all your ALZ deployments are the same.
Note
This approach is common in a Managed Service Provider (MSP) environment where the MSP manages several Microsoft Entra tenants for different clients that are all similar, except for their naming.
Tip
Customers that follow the deployment stamp style pattern might also benefit from following the Automation approach 2 – Shared application registration (multitenant) with multiple service principals.