We're modernizing a legacy Azure environment that currently has roughly 300 resources in a single subscription managed mostly through the portal. We've deployed the Azure Landing Zones accelerator and built a working Terraform-based subscription vending process. To migrate the environment properly, we need around 50–60 subscriptions, including separate production and staging subscriptions, but our current limit was only increased from 5 to 10. Support keeps asking for a business justification even though we've explained that the request is part of an Azure best-practice migration. What information or escalation path is most likely to get the limit increased?
1 Answer
Support will probably need a concrete capacity and governance plan rather than a general reference to best practices. Explain exactly why you need 50–60 subscriptions, how many you will create initially, the expected timeline, and how Terraform, Azure Landing Zones, policies, budgets, and RBAC will control them. It may also help to request an incremental increase, such as 20 first and then 60, instead of asking for the full limit immediately. Include the subscription vending design and explain that the subscriptions are for workload isolation and separate staging and production environments, not uncontrolled growth. If the case remains stuck, ask for it to be escalated to the subscription or account management team and provide the business justification as a formal document.
That makes sense. We have the vending process working already, but we haven't presented the rollout plan and controls as a formal capacity request. I'll put together the numbers, timeline, and governance details and ask for a staged increase.