Dealing with subscription limitations and regional resource shortages

[kevball2]

Hi All,
Was wondering how others are dealing with resource quota issues in regions while trying to follow best practices in the Cloud Adoption Framework

Working with a customer deploying resources into Central US. We have run into an issue with new subscriptions not being able to deploy App Service Plans (any SKU) Microsoft support says this is due to capacity issues in the region and we should use the sister region instead (East US 2). If we would like more capacity for new subscriptions, then we will need to contact support for each subscription and request the capacity we need. This capacity issue is expected for at least 6 months.

• With issues like this occuring, how are we supposed to follow practices in CAF and Enterprise Scale deployments?
• With the potential of creating hundreds of subscriptions, it is not feasible to have to contact Microsoft each time to allow a new subscription to deploy App Services?

We plan on eventually setting up a Hub in East US 2, though this will still cause issues with applications that would like to deploy across regions. Curious how other groups were handling new subscription onboarding and if they were also seeing these kinds of issues.