You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/expressroute/expressroute-about-virtual-network-gateways.md
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.custom: references_regions
12
12
13
13
# About ExpressRoute virtual network gateways
14
14
15
-
To connect your Azure virtual network (VNet) and your on-premises network by using Azure ExpressRoute, you must first create a virtual network gateway. A virtual network gateway serves two purposes: to exchange IP routes between networks, and to route network traffic.
15
+
To connect your Azure virtual network (virtual network) and your on-premises network by using Azure ExpressRoute, you must first create a virtual network gateway. A virtual network gateway serves two purposes: to exchange IP routes between networks, and to route network traffic.
16
16
17
17
This article explains different gateway types, gateway SKUs, and estimated performance by SKU. This article also explains ExpressRoute [FastPath](#fastpath), a feature that enables the network traffic from your on-premises network to bypass the virtual network gateway to improve performance.
18
18
@@ -83,6 +83,23 @@ The following table shows the features that each gateway type supports and the m
The Hosted-On-Behalf-Of (HOBO) Public IP feature simplifies ExpressRoute gateway deployment by allowing Microsoft to manage the required public IP address on your behalf. With HOBO, you no longer need to create or maintain a separate public IP resource for your gateway.
89
+
90
+
**Key benefits:**
91
+
92
+
-**Improved security:** The public IP is managed internally by Microsoft and isn't exposed to customers, reducing risks associated with open management ports.
93
+
-**Reduced complexity:** Customers aren't required to provision or manage a public IP resource.
94
+
-**Streamlined deployment:** The Azure portal and CLI no longer prompt for a public IP during gateway creation.
95
+
96
+
**How it works:**
97
+
When you create an ExpressRoute gateway, Microsoft automatically provisions and manages the public IP address in a secure, backend subscription. This IP is encapsulated within the gateway resource, enabling Microsoft to enforce policies such as data rate limits and enhance auditability.
98
+
99
+
**Availability:**
100
+
HOBO Public IP is currently in preview for ExpressRoute Virtual Network Gateways. It isn't available for Virtual WAN (vWAN) or Extended Zone deployments.
101
+
102
+
86
103
### <aname="zrgw"></a>Zone-redundant gateway SKUs
87
104
88
105
You can also deploy ExpressRoute gateways in Azure availability zones. Physically and logically separating the gateways into availability zones helps protect your on-premises network connectivity to Azure from zone-level failures.
0 commit comments