Skip to content

Commit da8fe50

Browse files
author
Michael Bender
committed
updated tabs
1 parent d08c129 commit da8fe50

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/virtual-network/ip-services/create-custom-ip-address-prefix-portal.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ If you choose to install and use PowerShell locally, this article requires the A
6868

6969
# [Azure portal](#tab/azureportal)
7070

71-
# [Unified Model)](#tab/azureportal/unified)
71+
# [Unified Model](#tab/azureportal/unified)
7272

7373
The following steps display the procedure for provisioning a sample customer range (1.2.3.0/24) to the US West 2 region.
7474

@@ -495,8 +495,6 @@ It's possible to commission the global custom IP prefix prior to the regional cu
495495

496496
# [Unified Model](#tab/azurepowershell/unified)
497497

498-
# [Unified Model](#tab/azurepowershell/unified)
499-
500498
The following steps display the procedure for provisioning a sample customer range (1.2.3.0/24) to the US West 2 region.
501499

502500
> [!NOTE]
@@ -660,7 +658,7 @@ It's possible to commission the global custom IP prefix prior to the regional cu
660658

661659
> [!IMPORTANT]
662660
> As the global custom IP prefix transitions to a **Commissioned** state, the range is being advertised with Microsoft from the local Azure region and globally to the Internet by Microsoft's wide area network under Autonomous System Number (ASN) 8075. Advertising this same range to the Internet from a location other than Microsoft at the same time could potentially create BGP routing instability or traffic loss. For example, a customer on-premises building. Plan any migration of an active range during a maintenance period to avoid impact.
663-
661+
---
664662

665663
---
666664
## Next steps

0 commit comments

Comments
 (0)