Multiple firewall deployments (Premium and Standard) failing in Central US

We did suspect this was an undocumented or hard-to-find resource constraint issue, since we had previously experienced similar problems with virtual machine deployments. After testing showed normal response times and successful resource creation in West US 3, we proceeded with migrating the entire project to that region.

A few clarifications:

1. Region discrepancy: My resources were in Central US, not South Central US as referenced in the response.
2. The AI response: The earlier AI-generated response seems to have been removed — I marked it as incomplete but didn't expect it to disappear. I've included a copy at the end of this post for reference. That response suggested I did not "plan accordingly" for existing deployments in Central US and referenced this document: https://learn.microsoft.com/en-us/azure/firewall/firewall-known-issues#current-capacity-constraints which I did review before proceeding. However, I did not see any Central US-specific capacity issue listed — only South Central US and East US.
3. Health status: The Azure health status boards indicated (and still indicate) that Central US is "healthy." Resource constraints severe enough to cause multi-hour deployment failures certainly seem like a health issue to me.

I need to inform our IT Governance board about regional capacity risks and update our processes accordingly. Any documentation Microsoft provides on planning for these scenarios would be helpful — ideally a source that is kept current and updated regularly so we can reference it before deploying resources. Once I have that, I'll consider this matter resolved.

Copy of the earlier Microsoft AI response that was in this thread:

It seems that you are experiencing deployment failures for Azure Firewalls in the Central US region. This could be due to current capacity constraints in that region. As per the information available, there are known issues with deploying Azure Firewalls in certain zones within various regions, including the Central US.

Here are some options you might consider:

1. Deploy to Another Region: Since you successfully created a firewall in the North Central region, you might want to continue using that region for your deployments if it meets your requirements.
2. Check Availability Zones: If you want to stay in the Central US region, ensure that you are deploying in available zones. Sometimes, specific zones may have capacity issues, and deploying in a different zone might help.
3. Monitor Capacity Updates: Keep an eye on updates regarding capacity issues in the Central US region. Microsoft often provides updates on when capacity issues are resolved.
4. Contact Support: If the issue persists, consider reaching out to Azure support for assistance. They may provide insights specific to your subscription or deployment scenario.

It's important to plan accordingly, especially if you have existing deployments in the Central US region, as stopping them may lead to difficulties in restarting due to ongoing capacity limitations.

References: Azure Firewall known issues and limitations