Closed sergio-re closed 3 weeks ago
When deploying MLZ in multiple subscriptions, Tier0 is getting deployed in Tier2, causing errors and conflicts with the deployment.
Directly from the main aka.ms/mlz site, deploy Landing Zone and select multiple subscriptions, a separate one for each Tier.
Steps to reproduce the behavior:
Each Tier gets deployed in their own LZ
Identity tier is getting deployed in whatever subscription was selected for SharedServices (Tier2) subscription.
Operating System: Deployed from Win 11 Client Terraform Version: N/A Cloud (public, Azure Government, etc.): US Gov't
Thank you for reporting this issue, @sergio-re! I have the fix added to my current feature branch and should be merged hopefully this week.
@sergio-re this should be fixed now.
Description
When deploying MLZ in multiple subscriptions, Tier0 is getting deployed in Tier2, causing errors and conflicts with the deployment.
Steps to Reproduce
Directly from the main aka.ms/mlz site, deploy Landing Zone and select multiple subscriptions, a separate one for each Tier.
Steps to reproduce the behavior:
Expected behavior
Each Tier gets deployed in their own LZ
Actual behavior
Identity tier is getting deployed in whatever subscription was selected for SharedServices (Tier2) subscription.
Screenshots
Additional context
Operating System: Deployed from Win 11 Client Terraform Version: N/A Cloud (public, Azure Government, etc.): US Gov't