Skip to content

Commit 7e9d56a

Browse files
KumudDSyntaxC4
authored andcommitted
fixed link
Signed-off-by: Cory Fowler <[email protected]>
1 parent 3a1a62c commit 7e9d56a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/networking/azure-network.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ You want a fast, reliable response when you use Microsoft services. Data travels
2828

2929
Customer traffic enters our global network through strategically placed Microsoft Edge nodes, our points of presence. These edge nodes are directly interconnected to more than 3500 unique Internet partners through thousands of connections in more than 145 locations. Our rich interconnection strategy optimizes the paths that data travels on our global network. Customers get a better network experience with less latency, jitter, and packet loss with more throughput. Direct interconnections give customers better quality of service compared to transit links, because there are fewer hops, fewer parties, and better networking paths.
3030

31-
Say you’re in London and the service is in Tokyo: Internet traffic enters one of our edges in London, goes over Microsoft WAN through France, our Trans-Arabia paths between Europe and India and then to Japan where the service is hosted. Response traffic is symmetric. This is sometimes referred to as [cold-potato routing, which means that traffic stays on Microsoft network as long as possible before we hand it off.
31+
Say you’re in London and the service is in Tokyo: Internet traffic enters one of our edges in London, goes over Microsoft WAN through France, our Trans-Arabia paths between Europe and India and then to Japan where the service is hosted. Response traffic is symmetric. This is sometimes referred to as [cold-potato routing](https://en.wikipedia.org/wiki/Hot-potato_and_cold-potato_routing), which means that traffic stays on Microsoft network as long as possible before we hand it off.
3232

3333
Azure traffic between our datacenters stays on our network and does not flow over the Internet. This includes all traffic between Microsoft services anywhere in the world. For example, within Azure, traffic between virtual machines, storage, and SQL communication traverses only the Microsoft network, regardless of the source and destination region. [Intra-region VNet-to-VNet traffic](../virtual-network/virtual-network-peering-overview.md), as well as [cross-region VNet-to-VNet traffic](../vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal.md), stays on our secure Microsoft network.
3434

0 commit comments

Comments
 (0)