Skip to main content
A virtual network gateway is billed for every hour it is deployed, whether or not any VPN or ExpressRoute connection uses it. Azure Advisor flags gateways that have no connections, and nOps shows those that are still on your bill, with the gateway’s full monthly cost as the saving.

Why it matters

Gateways are among the more expensive networking resources and are often left behind after a site-to-site link or migration project ends.

How nOps finds it

This recommendation comes from Azure Advisor, which nOps imports daily. nOps keeps only gateways billed on at least 6 of the last 7 days, including one of the last 3. Advisor gives no saving for unconnected gateways, so the saving shown is what the gateway actually cost over the last 7 days, net of discounts and scaled to a month.

Before you start

Permission to delete the gateway (for example Network Contributor), and confirmation from the network owner.

How to implement

  1. In the Azure portal, open Virtual network gateways, select the gateway and check Connections and Point-to-site configuration to confirm nothing is using it.
  2. Check with the network team that no new connection is planned soon.
  3. Delete the gateway, or run az network vnet-gateway delete --resource-group MY_RG --name MY_GATEWAY.
  4. Delete its public IP address and the GatewaySubnet if they are no longer needed.
  5. If the gateway is defined in Terraform, Bicep or ARM templates, remove it there as well.

Risks and considerations

  • A gateway kept as a standby for disaster recovery or a planned link has no connections but is still needed. Check first.
  • Recreating a gateway takes a long time to deploy and usually gets a new public IP, so remote VPN devices need updating.
  • Point-to-site VPN users connect without a site connection object, so check the point-to-site configuration too.

FAQs

Advisor does not estimate a saving for unconnected gateways. Deleting one removes all of its charges, so nOps shows what it cost you.