fixed URLs

Author: Michael Bender

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

@@ -7,7 +7,7 @@ ms.author: mbender
 ms.service: azure-virtual-network
 ms.subservice: ip-services
 ms.topic: how-to
-maims.date: 08/05/2024
+maims.date: 08/06/2024
 ---
 
 # Create a custom IPv4 address prefix using the Azure portal
@@ -66,12 +66,20 @@ If you choose to install and use PowerShell locally, this article requires the A
 
 ## Provisioning and Commissioning a Custom IPv4 Prefix
 
+The following steps display the procedure for provisioning and commissioning a custom IPv4 address prefix with a choice of two models:  Unified and Global/Regional. The steps can be performed with the Azure portal, Azure CLI, or Azure PowerShell.
+
 # [Azure portal](#tab/azureportal)
 
+Use the Azure portal to provision and commission a custom IPv4 address prefix with the Azure portal.
+
 # [Azure CLI](#tab/azurecli)
 
+Use the Azure CLI to provision and commission a custom IPv4 address prefix with the Azure CLI.
+
 # [Azure PowerShell](#tab/azurepowershell/)
 
+Use Azure PowerShell to provision and commission a custom IPv4 address prefix with Azure PowerShell.
+
 ---
 
 # [Unified Model](#tab/unified/azureportal)
@@ -324,7 +332,7 @@ It's possible to commission the global custom IP prefix before the regional cust
 The following steps display the procedure for provisioning a sample customer range (1.2.3.0/24) to the US West 2 region.
 
 > [!NOTE]
-> Clean up or delete steps aren't shown on this page given the nature of the resource. For information on removing a provisioned custom IP prefix, see [Manage custom IP prefix](../articles/virtual-network/ip-services/manage-public-ip-address-prefix.md).
+> Clean up or delete steps aren't shown on this page given the nature of the resource. For information on removing a provisioned custom IP prefix, see [Manage custom IP prefix](manage-public-ip-address-prefix.md).
 
 ### Create a resource group and specify the prefix and authorization messages
 
@@ -376,7 +384,7 @@ The **CommissionedState** field should show the range as **Provisioning** initia
 > The estimated time to complete the provisioning process is 30 minutes.
 
 > [!IMPORTANT]
-> After the custom IP prefix is in a **Provisioned** state, a child public IP prefix can be created. These public IP prefixes and any public IP addresses can be attached to networking resources. For example, virtual machine network interfaces or load balancer front ends. The IPs won't be advertised and therefore won't be reachable. For more information on a migration of an active prefix, see [Manage a custom IP prefix](../articles/virtual-network/ip-services/manage-public-ip-address-prefix.md).
+> After the custom IP prefix is in a **Provisioned** state, a child public IP prefix can be created. These public IP prefixes and any public IP addresses can be attached to networking resources. For example, virtual machine network interfaces or load balancer front ends. The IPs won't be advertised and therefore won't be reachable. For more information on a migration of an active prefix, see [Manage a custom IP prefix](manage-public-ip-address-prefix.md).
 
 ### Commission the unified custom IP address prefix
 
@@ -402,7 +410,7 @@ As before, the operation is asynchronous. Use [az network custom-ip prefix show]
 The following steps display the modified steps for provisioning a sample global (parent) IP range (1.2.3.0/4) and regional (child) IP ranges to the US West 2 and US East 2 Regions.
 
 > [!NOTE]
-> Clean up or delete steps aren't shown on this page given the nature of the resource. For information on removing a provisioned custom IP prefix, see [Manage custom IP prefix](../articles/virtual-network/ip-services/manage-public-ip-address-prefix.md).
+> Clean up or delete steps aren't shown on this page given the nature of the resource. For information on removing a provisioned custom IP prefix, see [Manage custom IP prefix](manage-public-ip-address-prefix.md).
 
 ### Create a resource group and specify the prefix and authorization messages
 
@@ -501,7 +509,7 @@ It's possible to commission the global custom IP prefix before the regional cust
 The following steps display the procedure for provisioning a sample customer range (1.2.3.0/24) to the US West 2 region.
 
 > [!NOTE]
-> Clean up or delete steps aren't shown on this page given the nature of the resource. For information on removing a provisioned custom IP prefix, see [Manage custom IP prefix](../articles/virtual-network/ip-services/manage-public-ip-address-prefix.md).
+> Clean up or delete steps aren't shown on this page given the nature of the resource. For information on removing a provisioned custom IP prefix, see [Manage custom IP prefix](manage-public-ip-address-prefix.md).
 
 ### Create a resource group and specify the prefix and authorization messages
 
@@ -555,7 +563,7 @@ The **CommissionedState** field should show the range as **Provisioning** initia
 > The estimated time to complete the provisioning process is 30 minutes.
 
 > [!IMPORTANT]
-> After the custom IP prefix is in a **Provisioned** state, a child public IP prefix can be created. These public IP prefixes and any public IP addresses can be attached to networking resources. For example, virtual machine network interfaces or load balancer front ends. The IPs won't be advertised and therefore won't be reachable. For more information on a migration of an active prefix, see [Manage a custom IP prefix](../articles/virtual-network/ip-services/manage-public-ip-address-prefix.md).
+> After the custom IP prefix is in a **Provisioned** state, a child public IP prefix can be created. These public IP prefixes and any public IP addresses can be attached to networking resources. For example, virtual machine network interfaces or load balancer front ends. The IPs won't be advertised and therefore won't be reachable. For more information on a migration of an active prefix, see [Manage a custom IP prefix](manage-public-ip-address-prefix.md).
 
 ### Commission the unified custom IP address prefix
 
@@ -571,14 +579,14 @@ As before, the operation is asynchronous. Use [Get-AzCustomIpPrefix](/powershell
 > The estimated time to fully complete the commissioning process is 3-4 hours.
 
 > [!IMPORTANT]
-> As the 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. Additionally, you could take advantage of the regional commissioning feature to put a custom IP prefix into a state where it is only advertised within the Azure region it is deployed in. For more information, see [Manage a custom IP address prefix (BYOIP)](../articles/virtual-network/ip-services/manage-public-ip-address-prefix.md).
+> As the 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. Additionally, you could take advantage of the regional commissioning feature to put a custom IP prefix into a state where it is only advertised within the Azure region it is deployed in. For more information, see [Manage a custom IP address prefix (BYOIP)](manage-public-ip-address-prefix.md).
 
 # [Global/Regional Model](#tab/globalregional/azurepowershell)
 
 The following steps display the modified steps for provisioning a sample global (parent) IP range (1.2.3.0/4) and regional (child) IP ranges to the US West 2 and US East 2 Regions.
 
 > [!NOTE]
-> Clean up or delete steps aren't shown on this page given the nature of the resource. For information on removing a provisioned custom IP prefix, see [Manage custom IP prefix](../articles/virtual-network/ip-services/manage-public-ip-address-prefix.md).
+> Clean up or delete steps aren't shown on this page given the nature of the resource. For information on removing a provisioned custom IP prefix, see [Manage custom IP prefix](manage-public-ip-address-prefix.md).
 
 ### Create a resource group and specify the prefix and authorization messages