ExpressRoute Circuit should use Premium SKU tier
Medium
Azure
General
expressroutecircuits-expressroute-circuit-premium
Applies to
Microsoft.Network/expressRouteCircuits
What CGPulse checks
A resource passes this rule when sku.tier must equal Premium. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Upgrade to Premium tier for global connectivity and enhanced route limits. In Azure Portal: ExpressRoute Circuit > Configuration > change SKU to Premium. See: https://learn.microsoft.com/en-us/azure/expressroute/expressroute-faqs#expressroute-premium
CLI
az network express-route update --ids "{id}" --sku-tier PremiumTerraform
resource "azurerm_express_route_circuit" "{name}" {
name = "{name}"
resource_group_name = "{rg}"
location = var.location
service_provider_name = "Equinix"
peering_location = "Silicon Valley"
bandwidth_in_mbps = 50
sku {
tier = "Premium"
family = "MeteredData"
}
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Azure rules
- Action Group should be enabled
- Activity Log Alert should be enabled
- AKS cluster logs should be sent to Log Analytics
- AKS cluster must enable RBAC
- AKS cluster must enable RBAC
- AKS cluster should be a private cluster
- AKS cluster should disable local accounts
- AKS cluster should enable Azure RBAC for Kubernetes