Skip to content

Commit 73af3f2

Browse files
authored
Merge pull request #110928 from JackStromberg/patch-38
Notation Hub-to-Hub is in Public Preview
2 parents c56275d + 9775c25 commit 73af3f2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-wan/virtual-wan-global-transit-network-architecture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ In the Azure Virtual WAN architecture, virtual WAN hubs are provisioned in Azure
4444

4545
You can establish a virtual WAN by creating a single virtual WAN hub in the region that has the largest number of spokes (branches, VNets, users), and then connecting the spokes that are in other regions to the hub. This is a good option when an enterprise footprint is mostly in one region with a few remote spokes.
4646

47-
## <a name="hubtohub"></a>Hub-to-hub connectivity
47+
## <a name="hubtohub"></a>Hub-to-hub connectivity (Preview)
4848

4949
An Enterprise cloud footprint can span multiple cloud regions and it is optimal (latency-wise) to access the cloud from a region closest to their physical site and users. One of the key principles of global transit network architecture is to enable cross-region connectivity between all cloud and on-premises network endpoints. This means that traffic from a branch that is connected to the cloud in one region can reach another branch or a VNet in a different region using hub-to-hub connectivity enabled by [Azure Global Network](https://azure.microsoft.com/global-infrastructure/global-network/).
5050

0 commit comments

Comments
 (0)