The virtual network in Azure is free of charge. Every subscription permits building up tp 50 virtual networks across all regions.
The public IP address and retained IP address used by services in virtual networks are charged.
The network appliances including VPN gateway and Application Gateway running in the Virtual Network are also charged.
Virtual network peering
Virtual network peering links virtual networks, enabling you to route traffic between them using private IP addresses. Ingress and egress traffic is charged at both ends of the peered networks.
VNET Peering within the same region
|Inbound data transfer||￥0.06572 /GB|
|Outbound data transfer||￥0.06572 /GB|
Global VNET Peering
|ZONE 1||ZONE 2|
|Inbound data transfer||￥0.1638 /GB||￥0.1638 /GB|
|Outbound data transfer||￥0.1638 /GB||￥0.1638 /GB|
*Global VNET Peering pricing is based on a zonal structure. For instance, if data is being transferred from a VNET in zone 1 to a VNET in zone 2, customers will incur outbound data transfer rates for zone 1 and inbound data transfer rates for zone 2.
The public IP address and reserved IP address can be applied to services running in the virtual network. The Public IP Address Pricing Details page lists the standard fees of these IP addresses.
The virtual network may have one or several VPN gateways of the on-premises networks or other virtual networks connected back to Azure.
For the charging standards of VPN gateways, see the VPN Gateway Pricing Details page.
Will the pricing differ by region or zone?
For Global VNET Peering pricing will differ based on the zone your VNETs are in.
Will there be a charge for data transfer within a virtual network?
No, there is no charge for data transfer within a virtual network
Will there be any compute charges in addition to virtual network peering charges?
No, you pay for other resources as you normally would. Neither VNET Peering, nor Global VNET peering impose any compute charges.
How does billing for this service work?
VNET Peering is billed based on the ingress and egress data being transferred from one VNET to another.
Global Peering, like VNET peering, is billed based on ingress and egress data transfer. However, the pricing differs based on the zone the region is in.
Which regions correspond to Zone 1, Zone 2?
A sub-region is the lowest level geo-location that you may select to deploy your applications and associated data. For data transfers (except CDN), the following regions correspond to Zone 1 and Zone 2:
Zone 1: CN East and CN North
Zone 2: CN East 2 and CN North 2
Support & SLA
If you have any questions or need help, please visit Azure Support and select self-help service or any other method to contact us for support.
The virtual network is free of charge and doesn’t provide service level agreements. To learn more about the details of our service level agreement, please visit the Service Level Agreements page.