Hi @Jason Bea
Here are the troubleshooting steps for the ExpressRoute bandwidth issue, including considerations for insufficient capacity and circuit recreation.
- Verify the ExpressRoute Circuit: Ensure that the circuit is showing 10 Gbps provisioned in Azure and that both the circuit provisioning state and service provider provisioning state are marked as provisioned.
- Confirm ExpressRoute Gateway Upgrade: Validate that the Virtual Network Gateway SKU has been successfully upgraded to ErGw3AZ and that it reflects a maximum bandwidth of 10 Gbps. If needed, restart the gateway to force reapplication.
- Check ExpressRoute Peering Configuration: Verify that both private peering and Microsoft peering settings align with the 10 Gbps upgrade and are correctly configured.
4 . Check for Azure firewall or NVA bottlenecks. If traffic passes through an Azure Firewall, ensure it is Azure Firewall Premium (Standard is limited to 2 Gbps). If using an NVA (e.g., Palo Alto, Fortinet, Cisco), confirm that it supports 10 Gbps throughput and is not limiting bandwidth.
Review Load Balancer Configurations: Ensure any Azure Load Balancer in the traffic path is Standard SKU and correctly configured for high throughput.
Validate Provider Configuration: Although the circuit provider confirms 10 Gbps provisioning, request a detailed validation to ensure that the committed bandwidth settings have been updated correctly.
Force Azure to Revalidate the Configuration: If all settings appear correct but bandwidth remains capped at 2 Gbps, escalate to Microsoft by requesting backend re-provisioning of the ExpressRoute circuit.
Reference: About upgrading ExpressRoute circuit bandwidth
I hope this helps to resolve your issue.
If the above is unclear and/or you are unsure about something, add a comment below.