reworked sub tabs

Author: Michael Bender

includes/ip-services-provision-ipv4-cli.md

@@ -11,7 +11,7 @@
  ms.custom: include file
 ---
 
-# [Unified model](#tab/azurecli/unified)
+# [Unified model](#tab/unified/azurecli)
 
 The following steps display the procedure for provisioning a sample customer range (1.2.3.0/24) to the US West 2 region.
 
@@ -89,7 +89,7 @@ As before, the operation is asynchronous. Use [az network custom-ip prefix show]
 > [!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--see [Manage a custom IP address prefix (BYOIP)](manage-custom-ip-address-prefix.md) for more information.
 
-# [Global/Regional Model)](#tab/azurecli/globalregional)
+# [Global/Regional Model)](#tab/globalregional/azurecli)
 
 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.
 

includes/ip-services-provision-ipv4-portal.md

@@ -11,7 +11,7 @@
  ms.custom: include file
 ---
 
-# [Unified Model](#tab/azureportal/unified)
+# [Unified Model](#tab/unified/azureportal)
 
 The following steps display the procedure for provisioning a sample customer range (1.2.3.0/24) to the US West 2 region.
 
@@ -111,7 +111,7 @@ The operation is asynchronous. You can check the status by reviewing the **Commi
 > [!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. To prevent these issues during initial deployment, you can choose the regional only commissioning option where your custom IP prefix will only be advertised within the Azure region it is deployed in. For more information, see [Manage a custom IP address prefix (BYOIP)](manage-custom-ip-address-prefix.md).
 
-# [Global/Regional Model](#tab/azure-portal/globalregional)
+# [Global/Regional Model](#tab/globalregional/azureportal)
 
 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.
 

includes/ip-services-provision-ipv4-powershell.md

@@ -11,7 +11,7 @@
  ms.custom: include file
 ---
 
-# [Unified Model](#tab/azurepowershell/unified)
+# [Unified Model](#tab/unified/azurepowershell)
 
 The following steps display the procedure for provisioning a sample customer range (1.2.3.0/24) to the US West 2 region.
 
@@ -88,7 +88,7 @@ As before, the operation is asynchronous. Use [Get-AzCustomIpPrefix](/powershell
 > [!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).
 
-# [Global/Regional Model](#tab/azurepowershell/globalregional)
+# [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.