• In this Section
• Enterprise-scale FAQ
• How long does enterprise-scale architecture take to deploy?
• Why are there custom policy definitions as part of enterprise-scale reference implementation?
• Where can I see the policy definitions used by the enterprise-scale landing zones reference implementation?
• Why does the enterprise-scale reference implementation require permission at tenant root '/' scope?
• The enterprise-scale (also known as the Azure landing zone accelerator) portal-based deployment doesn't display all subscriptions in the drop-down lists?
• Can we use and customize the ARM templates for enterprise-scale architecture and check them into our repository and deploy it from there?
• What if we can't deploy by using the Azure landing zone accelerator portal-based experience, but can deploy via infrastructure-as-code?
• If we already deployed enterprise-scale architecture without using infrastructure-as-code, do we have to delete everything and start again to use infrastructure-as-code?
• ARM Templates
• Bicep
• Terraform
• The AzureDiagnostics table in my Log Analytics Workspace has hit the 500 column limit, what should I do?
• Next steps
• What happens if I have existing Management Groups that have the same Name/IDs as ones that will be deployed in the ALZ Portal Accelerator?
• What are the ALZ Portal Accelerator Management Group Name/IDs that are created?
• Why hasn't Azure landing zones migrated to the Azure Monitor Agent yet?
• What if we are not ready to make the switch and migrate, right now?
• Where do I find more information about the Azure Monitor Baseline Alerts initiative included in the Azure landing zones Portal Accelerator?
• What is the impact of GitHub Releases and ALZ?
• What if I always want the latest release of ALZ?
• How does this impact me if I am using the ALZ Portal Accelerator?
• How do I browse a specific release of ALZ in GitHub?
• Why some managed services will potentially fail to deploy to ALZ and how to work around this issue?