Update Azure Firewall capacity constraints table

- Added four new regions with capacity constraints:
  - Spain Central (zone 2) - Available December 31, 2026
  - South Central US (zone 3) - Available March 31, 2026
  - West US 2 (zone 1)
  - East US 2 EUAP (zones 1 and 4)
- Reorganized table alphabetically by region for better readability
- All new constraints apply to Basic, Standard, and Premium SKUs

Author: duongau

articles/firewall/firewall-known-issues.md

@@ -24,9 +24,13 @@ The following zones are currently experiencing capacity constraints:
 
 | Region/Zones | SKU | Restrictions | Recommendation |
 |--|--|--|--|
+| **Physical zone 1 and zone 4** in **_East US 2 EUAP_** | Basic, Standard, and Premium | - You can't deploy a new Azure Firewall in zone 1 and zone 4. | We recommend you deploy a new Azure Firewall to the remaining availability zones or use a different region. To configure an existing firewall, see [How can I configure availability zones after deployment?](firewall-faq.yml#how-can-i-configure-availability-zones-after-deployment) |
 |- **Physical zone 2** in **_North Europe_** </br>- **Physical zone 3** in **_South East Asia_**  | Standard and Premium | - You can't deploy a new Azure Firewall to zone 3 in South East Asia or zone 2 in North Europe. </br></br>- If you stop an existing Azure Firewall that is deployed in these zone, it can't be restarted. </br></br>For more information, see [Physical and logical availability zones](../reliability/availability-zones-overview.md#physical-and-logical-availability-zones). | We recommend you deploy a new Azure Firewall to the remaining availability zones or use a different region. To configure an existing firewall, see [How can I configure availability zones after deployment?](firewall-faq.yml#how-can-i-configure-availability-zones-after-deployment) |
+| **Physical zone 3** in **_South Central US_** | Basic, Standard, and Premium | - You can't deploy a new Azure Firewall in zone 3. </br></br>Estimated date available: March 31, 2026 | We recommend you deploy a new Azure Firewall to the remaining availability zones or use a different region. To configure an existing firewall, see [How can I configure availability zones after deployment?](firewall-faq.yml#how-can-i-configure-availability-zones-after-deployment) |
+| **Physical zone 2** in **_Spain Central_** | Basic, Standard, and Premium | - You can't deploy a new Azure Firewall in zone 2. </br></br>Estimated date available: December 31, 2026 | We recommend you deploy a new Azure Firewall to the remaining availability zones or use a different region. To configure an existing firewall, see [How can I configure availability zones after deployment?](firewall-faq.yml#how-can-i-configure-availability-zones-after-deployment) |
 | **_US Gov Virginia_** | Premium | - There's zero capacity for Azure Firewall Premium SKU in US Gov Virginia, both zonal and nonzonal deployments are blocked. | Deploy Azure Firewall Standard SKU or deploy Premium SKU to a different region. |
 | **Physical zone 3** in **_US Gov Virginia_** | Basic and Standard | - Zonal deployments are blocked in physical zone 3 in US Gov Virginia. </br></br>- You must manually select available zones for successful deployment, creating a suboptimal deployment experience. | Select zones 1 and 2 for zonal deployments or use a different region. |
+| **Physical zone 1** in **_West US 2_** | Basic, Standard, and Premium | - You can't deploy a new Azure Firewall in zone 1. | We recommend you deploy a new Azure Firewall to the remaining availability zones or use a different region. To configure an existing firewall, see [How can I configure availability zones after deployment?](firewall-faq.yml#how-can-i-configure-availability-zones-after-deployment) |
 
 > [!WARNING]
 > If you stop an existing Azure Firewall deployment in any of these capacity-restricted regions, you might not be able to start it again due to ongoing capacity limitations. Plan accordingly before stopping firewall instances in these regions.