您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

ExpressRoute 路由要求ExpressRoute routing requirements

若要使用 ExpressRoute 连接到 Microsoft 云服务,需要设置并管理路由。To connect to Microsoft cloud services using ExpressRoute, you’ll need to set up and manage routing. 某些连接服务提供商以托管服务形式提供路由的设置和管理。Some connectivity providers offer setting up and managing routing as a managed service. 请咨询连接服务提供商,以确定他们是否提供此类服务。Check with your connectivity provider to see if they offer this service. 如果不提供,则必须遵守以下要求:If they don't, you must adhere to the following requirements:

有关需要在设置后才能建立连接的路由会话的说明,请参阅线路和路由域一文。Refer to the Circuits and routing domains article for a description of the routing sessions that need to be set up in to facilitate connectivity.

备注

Microsoft 不支持任何高可用性配置的路由器冗余协议(例如 HSRP 和 VRRP)。Microsoft does not support any router redundancy protocols (for example, HSRP, VRRP) for high availability configurations. 我们依赖每个对等互连的一组冗余 BGP 会话来获得高可用性。We rely on a redundant pair of BGP sessions per peering for high availability.

用于对等互连的 IP 地址IP addresses used for peerings

用户需要保留一些 IP 地址,用于配置网络与 Microsoft Enterprise Edge (MSEE) 路由器之间的路由。You need to reserve a few blocks of IP addresses to configure routing between your network and Microsoft's Enterprise edge (MSEEs) routers. 本部分提供了要求列表,并介绍有关如何获取和使用这些 IP 地址的规则。This section provides a list of requirements and describes the rules regarding how these IP addresses must be acquired and used.

用于 Azure 专用对等互连的 IP 地址IP addresses used for Azure private peering

可以使用专用 IP 地址或公共 IP 地址来配置对等互连。You can use either private IP addresses or public IP addresses to configure the peerings. 用于配置路由的地址范围不得与用于在 Azure 中创建虚拟网络的地址范围重叠。The address range used for configuring routes must not overlap with address ranges used to create virtual networks in Azure.

  • 必须为路由接口保留一个 /29 子网或两个 /30 子网。You must reserve a /29 subnet or two /30 subnets for routing interfaces.
  • 用于路由的子网可以是专用 IP 地址或公共 IP 地址。The subnets used for routing can be either private IP addresses or public IP addresses.
  • 子网不得与客户保留用于 Microsoft 云的范围冲突。The subnets must not conflict with the range reserved by the customer for use in the Microsoft cloud.
  • 如果使用 /29 子网,它将拆分成两个 /30 子网。If a /29 subnet is used, it is split into two /30 subnets.
    • 第一个 /30 子网用于主链路,第二个 /30 子网用于辅助链路。The first /30 subnet is used for the primary link and the second /30 subnet is used for the secondary link.
    • 对于每个 /30 子网,必须在路由器上使用 /30 子网的第一个 IP 地址。For each of the /30 subnets, you must use the first IP address of the /30 subnet on your router. Microsoft 使用 /30 子网的第二个 IP 地址设置 BGP 会话。Microsoft uses the second IP address of the /30 subnet to set up a BGP session.
    • 只有设置两个 BGP 会话,我们的 可用性 SLA 才有效。You must set up both BGP sessions for our availability SLA to be valid.

专用对等互连示例Example for private peering

如果选择使用 a.b.c.d/29 设置对等互连,它将拆分成两个 /30 子网。If you choose to use a.b.c.d/29 to set up the peering, it is split into two /30 subnets. 在以下示例中,请注意 a.b.c.d/29 子网的用法:In the following example, notice how the a.b.c.d/29 subnet is used:

  • a.b.c.d/29 拆分成 a.b.c.d/30 和 a.b.c.d+4/30 并通过预配 API 一路传递到 Microsoft。a.b.c.d/29 is split to a.b.c.d/30 and a.b.c.d+4/30 and passed down to Microsoft through the provisioning APIs.
    • 请使用 a.b.c.d+1 作为主要 PE 的 VRF IP,而 Microsoft 将使用 a.b.c.d+2 作为主要 MSEE 的 VRF IP。You use a.b.c.d+1 as the VRF IP for the Primary PE and Microsoft will consume a.b.c.d+2 as the VRF IP for the primary MSEE.
    • 请使用 b.c.d+5 作为辅助 PE 的 VRF IP,而 Microsoft 将使用 a.b.c.d+6 作为辅助 MSEE 的 VRF IP。You use a.b.c.d+5 as the VRF IP for the secondary PE and Microsoft will use a.b.c.d+6 as the VRF IP for the secondary MSEE.

假设选择 192.168.100.128/29 设置专用对等互连。Consider a case where you select 192.168.100.128/29 to set up private peering. 192.168.100.128/29 包括从 192.168.100.128 到 192.168.100.135 的地址,其中:192.168.100.128/29 includes addresses from 192.168.100.128 to 192.168.100.135, among which:

  • 192.168.100.128/30 将分配给 link1(提供商使用 192.168.100.129,而 Microsoft 使用 192.168.100.130)。192.168.100.128/30 will be assigned to link1, with provider using 192.168.100.129 and Microsoft using 192.168.100.130.
  • 192.168.100.132/30 将分配给 link2(提供商使用 192.168.100.133,而 Microsoft 使用 192.168.100.134)。192.168.100.132/30 will be assigned to link2, with provider using 192.168.100.133 and Microsoft using 192.168.100.134.

用于 Microsoft 对等互连的 IP 地址IP addresses used for Microsoft peering

必须使用自己的公共 IP 地址来设置 BGP 会话。You must use public IP addresses that you own for setting up the BGP sessions. Microsoft 必须能够通过路由 Internet 注册表和 Internet 路由注册表来验证 IP 地址的所有权。Microsoft must be able to verify the ownership of the IP addresses through Routing Internet Registries and Internet Routing Registries.

  • 门户中列出的与 Microsoft 对等互连的已播发公共前缀相对应的 IP 将为 Microsoft 核心路由器创建 ACL,目的是允许来自这些 IP 的入站流量。The IPs listed in the portal for Advertised Public Prefixes for Microsoft Peering will create ACLs for the Microsoft core routers to allow inbound traffic from these IPs.
  • 必须使用一个唯一的 /29 (IPv4) 或 /125 (IPv6) 子网或两个 /30 (IPv4) 或 /126 (IPv6) 子网为每条 ExpressRoute 线路(如果有多个)的每个对等互连设置 BGP 对等互连。You must use a unique /29 (IPv4) or /125 (IPv6) subnet or two /30 (IPv4) or /126 (IPv6) subnets to set up the BGP peering for each peering per ExpressRoute circuit (if you have more than one).
  • 如果使用 /29 子网,它将拆分成两个 /30 子网。If a /29 subnet is used, it is split into two /30 subnets.
  • 第一个 /30 子网用于主链路,第二个 /30 子网将用于辅助链路。The first /30 subnet is used for the primary link and the second /30 subnet will be used for the secondary link.
  • 对于每个 /30 子网,必须在路由器上使用 /30 子网的第一个 IP 地址。For each of the /30 subnets, you must use the first IP address of the /30 subnet on your router. Microsoft 使用 /30 子网的第二个 IP 地址设置 BGP 会话。Microsoft uses the second IP address of the /30 subnet to set up a BGP session.
  • 如果使用 /125 子网,它将拆分成两个 /126 子网。If a /125 subnet is used, it is split into two /126 subnets.
  • 第一个 /126 子网用于主链路,第二个 /126 子网将用于辅助链路。The first /126 subnet is used for the primary link and the second /126 subnet will be used for the secondary link.
  • 对于每个 /126 子网,必须在路由器上使用 /126 子网的第一个 IP 地址。For each of the /126 subnets, you must use the first IP address of the /126 subnet on your router. Microsoft 使用 /126 子网的第二个 IP 地址设置 BGP 会话。Microsoft uses the second IP address of the /126 subnet to set up a BGP session.
  • 只有设置两个 BGP 会话,我们的 可用性 SLA 才有效。You must set up both BGP sessions for our availability SLA to be valid.

用于 Azure 公共对等互连的 IP 地址IP addresses used for Azure public peering

备注

Azure 公共对等互连不适用于新线路。Azure public peering is not available for new circuits.

必须使用自己的公共 IP 地址来设置 BGP 会话。You must use public IP addresses that you own for setting up the BGP sessions. Microsoft 必须能够通过路由 Internet 注册表和 Internet 路由注册表来验证 IP 地址的所有权。Microsoft must be able to verify the ownership of the IP addresses through Routing Internet Registries and Internet Routing Registries.

  • 必须使用一个唯一的 /29 子网或两个 /30 子网为每条 ExpressRoute 线路(如果有多个)的每个对等互连设置 BGP 对等互连。You must use a unique /29 subnet or two /30 subnets to set up the BGP peering for each peering per ExpressRoute circuit (if you have more than one).
  • 如果使用 /29 子网,它将拆分成两个 /30 子网。If a /29 subnet is used, it is split into two /30 subnets.
    • 第一个 /30 子网用于主链路,第二个 /30 子网用于辅助链路。The first /30 subnet is used for the primary link and the second /30 subnet is used for the secondary link.
    • 对于每个 /30 子网,必须在路由器上使用 /30 子网的第一个 IP 地址。For each of the /30 subnets, you must use the first IP address of the /30 subnet on your router. Microsoft 使用 /30 子网的第二个 IP 地址设置 BGP 会话。Microsoft uses the second IP address of the /30 subnet to set up a BGP session.
    • 只有设置两个 BGP 会话,我们的 可用性 SLA 才有效。You must set up both BGP sessions for our availability SLA to be valid.

公共 IP 地址要求Public IP address requirement

专用对等互连Private peering

进行专用对等互连时,可以选择使用公共的或专用的 IPv4 地址。You can choose to use public or private IPv4 addresses for private peering. 我们会对用户的流量进行端到端隔离,因此在进行专用对等互连时,不可能出现与其他客户的地址发生重叠的情况。We provide end-to-end isolation of your traffic, so overlapping of addresses with other customers is not possible in case of private peering. 这些地址不会播发到 Internet。These addresses are not advertised to Internet.

Microsoft 对等互连Microsoft peering

可以使用 Microsoft 对等互连路径连接到 Microsoft 云服务。The Microsoft peering path lets you connect to Microsoft cloud services. 服务列表包括 Office 365 服务,例如 Exchange Online、SharePoint Online、Skype for Business 和 Microsoft 团队。The list of services includes Office 365 services, such as Exchange Online, SharePoint Online, Skype for Business, and Microsoft Teams. Microsoft 支持在 Microsoft 对等互连时进行双向连接。Microsoft supports bi-directional connectivity on the Microsoft peering. 定向到 Microsoft 云服务的流量必须使用有效的公共 IPv4 地址才能进入 Microsoft 网络。Traffic destined to Microsoft cloud services must use valid public IPv4 addresses before they enter the Microsoft network.

确保 IP 地址和 AS 号码已在下列其中一个注册表中注册:Make sure that your IP address and AS number are registered to you in one of the following registries:

如果没有在前述注册表中为你分配前缀和 AS 编号,需开立一个支持案例,以便手动验证前缀和 ASN。If your prefixes and AS number are not assigned to you in the preceding registries, you need to open a support case for manual validation of your prefixes and ASN. 支持需要文档,例如证明你有权使用相关资源的授权书。Support requires documentation, such as a Letter of Authorization, that proves you are allowed to use the resources.

专用 AS 编号可以用于 Microsoft 对等互连,但也需手动验证。A Private AS Number is allowed with Microsoft Peering, but will also require manual validation. 此外,对于收到的前缀,我们会删除 AS PATH 中的专用 AS 数字。In addition, we remove private AS numbers in the AS PATH for the received prefixes. 因此,无法在 AS PATH 中追加专用 AS 数字来影响 Microsoft 对等互连的路由As a result, you can't append private AS numbers in the AS PATH to influence routing for Microsoft Peering.

重要

不要将相同的公共 IP 路由播发到公共 Internet 和通过 ExpressRoute 播发。Do not advertise the same public IP route to the public Internet and over ExpressRoute. 为了降低错误配置导致不对称路由的风险,我们强烈建议通过 ExpressRoute 播发到 Microsoft 的 NAT IP 地址应该来自完全没有播发到 Internet 的范围。To reduce the risk of incorrect configuration causing asymmetric routing, we strongly recommend that the NAT IP addresses advertised to Microsoft over ExpressRoute be from a range that is not advertised to the internet at all. 如果无法实现这一点,则必须确保通过 ExpressRoute 播发的范围比 Internet 连接上的范围更具体。If this is not possible to achieve, it is essential to ensure you advertise a more specific range over ExpressRoute than the one on the Internet connection. 除了要进行 NAT 的公共路由外,还可以在本地网络中通过 ExpressRoute 播发与 Microsoft 中的 Office 365 终结点通信的服务器使用的公共 IP 地址。Besides the public route for NAT, you can also advertise over ExpressRoute the Public IP addresses used by the servers in your on-premises network that communicate with Office 365 endpoints within Microsoft.

公共对等互连(已弃用 - 不适用于新线路)Public peering (deprecated - not available for new circuits)

Azure 公共对等互连路径用于连接到托管于 Azure 中的所有服务的公共 IP 地址。The Azure public peering path enables you to connect to all services hosted in Azure over their public IP addresses. 其中包括 ExpessRoute 常见问题 中列出的服务以及由 Microsoft Azure 上的 ISV 托管的任何服务。These include services listed in the ExpessRoute FAQ and any services hosted by ISVs on Microsoft Azure. 始终从网络向 Microsoft 网络发起与公共对等互连中 Microsoft Azure 服务的连接。Connectivity to Microsoft Azure services on public peering is always initiated from your network into the Microsoft network. 必须使用公共 IP 地址才能将流量发往 Microsoft 网络。You must use Public IP addresses for the traffic destined to Microsoft network.

重要

所有 Azure PaaS 服务可通过 Microsoft 对等互连访问。All Azure PaaS services are accessible through Microsoft peering.

公共对等互连允许使用专用 AS 编号。A Private AS Number is allowed with public peering.

动态路由交换Dynamic route exchange

路由交换将通过 eBGP 协议进行。Routing exchange will be over eBGP protocol. EBGP 会话在 MSEE 与路由器之间建立。EBGP sessions are established between the MSEEs and your routers. 不要求对 BGP 会话进行身份验证。Authentication of BGP sessions is not a requirement. 如果需要,可以配置 MD5 哈希。If required, an MD5 hash can be configured. 有关配置 BGP 会话的信息,请参阅配置路由线路预配工作流和线路状态See the Configure routing and Circuit provisioning workflows and circuit states for information about configuring BGP sessions.

自治系统编号Autonomous System numbers

Microsoft 使用 AS 12076 进行 Azure 公共、Azure 专用和 Microsoft 对等互连。Microsoft uses AS 12076 for Azure public, Azure private and Microsoft peering. 我们保留了 ASN 65515-65520 供内部使用。We have reserved ASNs from 65515 to 65520 for internal use. 支持 16 和 32 位 AS 编号。Both 16 and 32 bit AS numbers are supported.

数据传输对称没有相关要求。There are no requirements around data transfer symmetry. 转发与返回路径可以遍历不同的路由器对。The forward and return paths may traverse different router pairs. 相同的路由必须从属于你的多个线路对的任何一端播发。Identical routes must be advertised from either sides across multiple circuit pairs belonging to you. 路由指标不需要完全相同。Route metrics are not required to be identical.

路由聚合与前缀限制Route aggregation and prefix limits

我们支持通过 Azure 专用对等互连向我们播发最多 4000 个前缀。We support up to 4000 prefixes advertised to us through the Azure private peering. 如果已启用 ExpressRoute 高级版附加组件,则可增加到 10,000 个前缀。This can be increased up to 10,000 prefixes if the ExpressRoute premium add-on is enabled. 我们接受为每个 BGP 会话最多使用 200 个前缀建立 Azure 公共和 Microsoft 对等互连。We accept up to 200 prefixes per BGP session for Azure public and Microsoft peering.

如果前缀数目超过此限制,将丢弃 BGP 会话。The BGP session is dropped if the number of prefixes exceeds the limit. 我们只接受专用对等互连链路上的默认路由。We will accept default routes on the private peering link only. 提供商必须从 Azure 公共和 Microsoft 对等互连路径中筛选出默认路由和专用 IP 地址 (RFC 1918)。Provider must filter out default route and private IP addresses (RFC 1918) from the Azure public and Microsoft peering paths.

传输路由和跨区域路由Transit routing and cross-region routing

ExpressRoute 不能配置为传输路由器。ExpressRoute cannot be configured as transit routers. 必须依赖连接服务提供商的传输路由服务。You will have to rely on your connectivity provider for transit routing services.

播发默认路由Advertising default routes

只有 Azure 专用对等互连会话允许默认路由。Default routes are permitted only on Azure private peering sessions. 在这种情况下,我们将所有流量从关联的虚拟网络路由到网络。In such a case, we will route all traffic from the associated virtual networks to your network. 在专用对等互连中播发默认路由会导致来自 Azure 的 Internet 路径遭到阻止。Advertising default routes into private peering will result in the internet path from Azure being blocked. 必须依赖企业网络边缘,为 Azure 中托管的服务往返路由 Internet 的流量。You must rely on your corporate edge to route traffic from and to the internet for services hosted in Azure.

要连接其他 Azure 服务和基础结构服务,必须确保已准备好下列其中一项:To enable connectivity to other Azure services and infrastructure services, you must make sure one of the following items is in place:

  • 已启用 Azure 公共对等互连,以将流量路由到公共终结点。Azure public peering is enabled to route traffic to public endpoints.
  • 使用用户定义的路由,为需要 Internet 连接的每个子网建立 Internet 连接。You use user-defined routing to allow internet connectivity for every subnet requiring Internet connectivity.

备注

播发默认路由会中断 Windows 和其他 VM 许可证激活。Advertising default routes will break Windows and other VM license activation. 请按照 此处 的说明来解决此问题。Follow instructions here to work around this.

BGP 社区支持Support for BGP communities

本部分概述如何配合 ExpressRoute 使用 BGP 社区。This section provides an overview of how BGP communities will be used with ExpressRoute. Microsoft 将播发公共和 Microsoft 对等互连路径中的路由并为路由标记适当的社区值。Microsoft will advertise routes in the public and Microsoft peering paths with routes tagged with appropriate community values. 下面会介绍这种方案的理由以及有关社区值的详细信息。The rationale for doing so and the details on community values are described below. 但是,Microsoft 不遵循向 Microsoft 播发的路由的任何标记社区值。Microsoft, however, will not honor any community values tagged to routes advertised to Microsoft.

如果要在某个地缘政治区域内的任何一个对等互连位置通过 ExpressRoute 连接到 Microsoft,就必须能够访问该地缘政治边界内所有区域中的所有 Microsoft 云服务。If you are connecting to Microsoft through ExpressRoute at any one peering location within a geopolitical region, you will have access to all Microsoft cloud services across all regions within the geopolitical boundary.

例如,如果在阿姆斯特丹通过 ExpressRoute 连接到 Microsoft,则就能够访问在欧洲北部和欧洲西部托管的所有 Microsoft 云服务。For example, if you connected to Microsoft in Amsterdam through ExpressRoute, you will have access to all Microsoft cloud services hosted in North Europe and West Europe.

有关地缘政治地区、关联的 Azure 区域和对应的 ExpressRoute 对等互连位置的详细列表,请参阅 ExpressRoute 合作伙伴和对等位置Refer to the ExpressRoute partners and peering locations page for a detailed list of geopolitical regions, associated Azure regions, and corresponding ExpressRoute peering locations.

可以针对每个地缘政治区域购买多个 ExpressRoute 线路。You can purchase more than one ExpressRoute circuit per geopolitical region. 如果拥有多个连接,则可以从异地冗余中获得明显的高可用性优势。Having multiple connections offers you significant benefits on high availability due to geo-redundancy. 如果具有多条 ExpressRoute 线路,将在 Microsoft 对等互连和公共对等互连路径收到 Microsoft 播发的同一组前缀。In cases where you have multiple ExpressRoute circuits, you will receive the same set of prefixes advertised from Microsoft on the Microsoft peering and public peering paths. 这意味着可以使用多个路径从网络接入 Microsoft。This means you will have multiple paths from your network into Microsoft. 这可能会导致在网络中做出欠佳的路由决策。This can potentially cause suboptimal routing decisions to be made within your network. 因此,可能会在不同的服务上遇到欠佳的连接体验。As a result, you may experience suboptimal connectivity experiences to different services. 可以依赖社区值做出适当的路由决策,向用户提供最佳路由You can rely on the community values to make appropriate routing decisions to offer optimal routing to users.

Microsoft Azure 区域Microsoft Azure region 区域 BGP 社区Regional BGP community 存储 BGP 社区Storage BGP community SQL BGP 社区SQL BGP community Cosmos DB BGP 社区Cosmos DB BGP community
北美North America
美国东部East US 12076:5100412076:51004 12076:5200412076:52004 12076:5300412076:53004 12076:5400412076:54004
美国东部 2East US 2 12076:5100512076:51005 12076:5200512076:52005 12076:5300512076:53005 12076:5400512076:54005
美国西部West US 12076:5100612076:51006 12076:5200612076:52006 12076:5300612076:53006 12076:5400612076:54006
美国西部 2West US 2 12076:5102612076:51026 12076:5202612076:52026 12076:5302612076:53026 12076:5402612076:54026
美国中西部West Central US 12076:5102712076:51027 12076:5202712076:52027 12076:5302712076:53027 12076:5402712076:54027
美国中北部North Central US 12076:5100712076:51007 12076:5200712076:52007 12076:5300712076:53007 12076:5400712076:54007
美国中南部South Central US 12076:5100812076:51008 12076:5200812076:52008 12076:5300812076:53008 12076:5400812076:54008
美国中部Central US 12076:5100912076:51009 12076:5200912076:52009 12076:5300912076:53009 12076:5400912076:54009
加拿大中部Canada Central 12076:5102012076:51020 12076:5202012076:52020 12076:5302012076:53020 12076:5402012076:54020
加拿大东部Canada East 12076:5102112076:51021 12076:5202112076:52021 12076:5302112076:53021 12076:5402112076:54021
南美洲South America
巴西南部Brazil South 12076:5101412076:51014 12076:5201412076:52014 12076:5301412076:53014 12076:5401412076:54014
欧洲Europe
北欧North Europe 12076:5100312076:51003 12076:5200312076:52003 12076:5300312076:53003 12076:5400312076:54003
西欧West Europe 12076:5100212076:51002 12076:5200212076:52002 12076:5300212076:53002 12076:5400212076:54002
英国南部UK South 12076:5102412076:51024 12076:5202412076:52024 12076:5302412076:53024 12076:5402412076:54024
英国西部UK West 12076:5102512076:51025 12076:5202512076:52025 12076:5302512076:53025 12076:5402512076:54025
法国中部France Central 12076:5103012076:51030 12076:5203012076:52030 12076:5303012076:53030 12076:5403012076:54030
法国南部France South 12076:5103112076:51031 12076:5203112076:52031 12076:5303112076:53031 12076:5403112076:54031
亚太区Asia Pacific
东亚East Asia 12076:5101012076:51010 12076:5201012076:52010 12076:5301012076:53010 12076:5401012076:54010
东南亚Southeast Asia 12076:5101112076:51011 12076:5201112076:52011 12076:5301112076:53011 12076:5401112076:54011
日本Japan
日本东部Japan East 12076:5101212076:51012 12076:5201212076:52012 12076:5301212076:53012 12076:5401212076:54012
日本西部Japan West 12076:5101312076:51013 12076:5201312076:52013 12076:5301312076:53013 12076:5401312076:54013
澳大利亚Australia
澳大利亚东部Australia East 12076:5101512076:51015 12076:5201512076:52015 12076:5301512076:53015 12076:5401512076:54015
澳大利亚东南部Australia Southeast 12076:5101612076:51016 12076:5201612076:52016 12076:5301612076:53016 12076:5401612076:54016
澳大利亚政府Australia Government
澳大利亚中部Australia Central 12076:5103212076:51032 12076:5203212076:52032 12076:5303212076:53032 12076:5403212076:54032
澳大利亚中部 2Australia Central 2 12076:5103312076:51033 12076:5203312076:52033 12076:5303312076:53033 12076:5403312076:54033
印度India
印度南部India South 12076:5101912076:51019 12076:5201912076:52019 12076:5301912076:53019 12076:5401912076:54019
印度西部India West 12076:5101812076:51018 12076:5201812076:52018 12076:5301812076:53018 12076:5401812076:54018
印度中部India Central 12076:5101712076:51017 12076:5201712076:52017 12076:5301712076:53017 12076:5401712076:54017
韩国Korea
韩国南部Korea South 12076:5102812076:51028 12076:5202812076:52028 12076:5302812076:53028 12076:5402812076:54028
韩国中部Korea Central 12076:5102912076:51029 12076:5202912076:52029 12076:5302912076:53029 12076:5402912076:54029
南非South Africa
南非北部South Africa North 12076:5103412076:51034 12076:5203412076:52034 12076:5303412076:53034 12076:5403412076:54034
南非西部South Africa West 12076:5103512076:51035 12076:5203512076:52035 12076:5303512076:53035 12076:5403512076:54035
阿拉伯联合酋长国UAE
阿联酋北部UAE North 12076:5103612076:51036 12076:5203612076:52036 12076:5303612076:53036 12076:5403612076:54036
阿拉伯联合酋长国中部UAE Central 12076:5103712076:51037 12076:5203712076:52037 12076:5303712076:53037 12076:5403712076:54037

所有 Microsoft 播发的路由都标有适当的社区值。All routes advertised from Microsoft will be tagged with the appropriate community value.

重要

全局前缀将使用相应的社区值进行标记。Global prefixes are tagged with an appropriate community value.

服务到 BGP 团体值Service to BGP community value

除了上述各项,Microsoft 还会根据其所属的服务加上标记及前缀。In addition to the above, Microsoft will also tag prefixes based on the service they belong to. 这只适用于 Microsoft 对等互连。This applies only to the Microsoft peering. 下表提供了服务与 BGP 社区值之间的映射。The table below provides a mapping of service to BGP community value. 若要获取最新值的完整列表,可以运行 "AzBgpServiceCommunity" cmdlet。You can run the 'Get-AzBgpServiceCommunity' cmdlet for a full list of the latest values.

服务Service BGP 社区值BGP community value
Exchange Online * *Exchange Online** 12076:501012076:5010
SharePoint Online * *SharePoint Online** 12076:502012076:5020
Skype For Business Online * *Skype For Business Online** 12076:503012076:5030
CRM OnlineCRM Online 12076:504012076:5040
Azure 全球服务*Azure Global Services* 12076:505012076:5050
Azure Active DirectoryAzure Active Directory 12076:506012076:5060
其他 Office 365 联机服务 * *Other Office 365 Online services** 12076:510012076:5100

*本次 Azure 全球服务仅包括 Azure DevOps。*Azure Global Services includes only Azure DevOps at this time. * * Microsoft 要求的授权,请参阅为 microsoft 对等互连配置路由筛选器** Authorization required from Microsoft, refer Configure route filters for Microsoft Peering

备注

Microsoft 不遵循你在播发到 Microsoft 的路由上设置的任何 BGP 社区值。Microsoft does not honor any BGP community values that you set on the routes advertised to Microsoft.

区域云中的 BGP 社区支持BGP Community support in National Clouds

国家/地区云 Azure 区域National Clouds Azure Region BGP 社区值BGP community value
美国政府US Government
美国亚利桑那州政府US Gov Arizona 12076:5110612076:51106
US Gov 爱荷华州US Gov Iowa 12076:5110912076:51109
美国政府弗吉尼亚州US Gov Virginia 12076:5110512076:51105
美国德克萨斯州政府US Gov Texas 12076:5110812076:51108
美国 DoD 中部US DoD Central 12076:5120912076:51209
美国 DoD 东部US DoD East 12076:5120512076:51205
国家/地区云中的服务Service in National Clouds BGP 社区值BGP community value
美国政府US Government
Exchange OnlineExchange Online 12076:511012076:5110
SharePoint OnlineSharePoint Online 12076:512012076:5120
Skype For Business OnlineSkype For Business Online 12076:513012076:5130
其他 Office 365 Online 服务Other Office 365 Online services 12076:520012076:5200

后续步骤Next steps