Global VNET peering inbound and outbound transmission rates

刘系儒 1 Reputation point
2021-09-28T09:21:22.513+00:00

全局 VNET 对等互连的定价以区域结构为基础。例如,如果数据从区域 1 中的 VNET 传输到区域 2 中的 VNET,区域 1 会产生出站数据传输费率,区域 2 则会产生入站数据传输费率。

1可在此文档中找到与区域 1、区域 2、区域 3 和政府区域对应的区域。

Edited and changed title:
Translated in English:

The pricing of global VNET peering is based on the regional structure. For example, if data is transferred from a VNET in area 1 to a VNET in area 2, area 1 will generate outbound data transmission rates, and area 2 will generate inbound data transmission rates.

1The areas corresponding to Area 1, Area 2, Area 3 and the government area can be found in this document.

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,959 questions
{count} votes

1 answer

Sort by: Most helpful
  1. ajkuma 22,521 Reputation points Microsoft Employee
    2021-11-30T12:30:07.017+00:00

    Apologies for the delayed response. Following-up from our comments.

    Which regions correspond to Zone 1, Zone 2, Zone 3 and US Gov?

    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, Zone 2, and Zone 3:

    Zone 1—Australia Central, Australia Central 2, Canada Central, Canada East, Central US, East US, East US 2, France Central, France South, Germany North, Germany West Central, North Central US, North Europe, Norway East, Norway West, South Central US, Switzerland North, Switzerland West, UK South, UK West, West Central US, West Europe, West US, West US 2

    Zone 2—Australia East, Australia Southeast, Central India, East Asia, Japan East, Japan West, Korea Central, Korea South, Southeast Asia, South India, West India

    Zone 3—Brazil South, South Africa North, South Africa West, UAE Central, UAE North

    US Gov—US Gov Arizona, US Gov Texas, US Gov Virginia

    Copied the FAQ from the same pricing doc . I have reported about the incorrect URL internally, and as soon as it is fixed, I'll update here.

    Thanks again for your feedback and patience!

    0 comments No comments