Skip to content

Commit d37ce90

Browse files
Merge pull request #303457 from MekaylaMoore/HOBO
Hobo
2 parents b277335 + a9a4b64 commit d37ce90

File tree

3 files changed

+5
-1
lines changed

3 files changed

+5
-1
lines changed

articles/expressroute/expressroute-about-virtual-network-gateways.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,10 @@ When you create an ExpressRoute gateway, Microsoft automatically provisions and
9999

100100
**Availability:**
101101
Auto-Assigned Public IP is not available for Virtual WAN (vWAN) or Extended Zone deployments.
102+
103+
#### Create a new ExpressRoute gateway with Auto-Assigned Public IP
102104

105+
:::image type="content" source="media/expressroute-introduction/hobo-ip.png" alt-text="Screenshot of the create for virtual gateway." lightbox="media/gateway-migration/gateway-prepare-stage.png":::
103106

104107
## Connectivity from VNet to VNet and from VNet to virtual WAN
105108

articles/expressroute/expressroute-howto-gateway-migration-portal.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@ Follow these steps to migrate to a new gateway using the Azure portal:
3636
:::image type="content" source="media/gateway-migration/validate-step.png" alt-text="Screenshot of the validate step for migrating a virtual network gateway." lightbox="media/gateway-migration/validate-step.png":::
3737

3838
1. After successful validation, move to the **Prepare** stage. At this point, a new virtual network gateway will be created, and its Public IP address will be provisioned and managed by Microsoft. In the **Virtual Network Gateway Details** section, enter the following information:
39+
1.
3940
:::image type="content" source="media/gateway-migration/gateway-prepare-update.png" alt-text="Screenshot of the Prepare stage for migrating a virtual network gateway." lightbox="media/gateway-migration/gateway-prepare-stage.png":::
4041

4142
| Setting | value |
@@ -65,4 +66,4 @@ Follow these steps to migrate to a new gateway using the Azure portal:
6566
## Next steps
6667

6768
* Learn more about [designing for high availability](designing-for-high-availability-with-expressroute.md).
68-
* Plan for [disaster recovery](designing-for-disaster-recovery-with-expressroute-privatepeering.md) and [using VPN as a backup](use-s2s-vpn-as-backup-for-expressroute-privatepeering.md).
69+
* Plan for [disaster recovery](designing-for-disaster-recovery-with-expressroute-privatepeering.md) and [using VPN as a backup](use-s2s-vpn-as-backup-for-expressroute-privatepeering.md).
161 KB
Loading

0 commit comments

Comments
 (0)