Fixed Redirects

Author: Michael Bender

.openpublishing.redirection.json

@@ -4971,13 +4971,13 @@
             "redirect_document_id": false
         },
         {
-            "source_path": "azure/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6-powershell.md",
-            "redirect_url": "azure/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6--portal.md",
+            "source_path": "/articles/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6-powershell.md",
+            "redirect_url": "/azure/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6--portal.md",
             "redirect_document_id": false
         },
         {
-            "source_path": "azure/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6-cli.md",
-            "redirect_url": "azure/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6--portal.md",
+            "source_path": "/articles/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6-cli.md",
+            "redirect_url": "/azure/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6--portal.md",
             "redirect_document_id": false
         }  
 

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

@@ -24,6 +24,8 @@ The steps in this article detail the process to:
 
 For this article, choose between the Azure portal, Azure CLI, or PowerShell to create a custom IPv6 address prefix.
 
+## Differences between using BYOIPv4 and BYOIPv6
+
 [!INCLUDE [ip-services-ipv4-ipv6-differences](../../../includes/ip-services-ipv4-ipv6-differences.md)]
 
 ## Prerequisites

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

@@ -66,7 +66,7 @@ When ready, you can issue the command to have your range advertised from Azure a
 * IPs brought to Azure may have a delay of up to a week before they can be used for Windows Server Activation.
 
 > [!IMPORTANT]
-> There are several differences between how custom IPv4 and IPv6 prefixes are onboarded and utilized. For more information, see [Differences between using BYOIPv4 and BYOIPv6](create-custom-ip-address-prefix-ipv6-powershell.md#differences-between-using-byoipv4-and-byoipv6).
+> There are several differences between how custom IPv4 and IPv6 prefixes are onboarded and utilized. For more information, see [Differences between using BYOIPv4 and BYOIPv6](create-custom-ip-address-prefix-ipv6-portal.md#differences-between-using-byoipv4-and-byoipv6).
 
 ## Pricing
 

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

@@ -204,7 +204,7 @@ To migrate a custom IP prefix, it must first be deprovisioned from one region. A
 
 ### Are there any special considerations when using IPv6
 
-Yes - there are multiple differences for provisioning and commissioning when using BYOIPv6.  For more information, see [Create a custom IPv6 address prefix - PowerShell](create-custom-ip-address-prefix-ipv6-powershell.md).
+Yes - there are multiple differences for provisioning and commissioning when using BYOIPv6.  For more information, see [Create a custom IPv6 address prefix - PowerShell](create-custom-ip-address-prefix-ipv6-portal.md).
 
 ### Status messages
 

includes/ip-services-ipv4-ipv6-differences.md

@@ -11,13 +11,11 @@
  ms.custom: include file
 ---
 
-## Differences between using BYOIPv4 and BYOIPv6
-
 > [!IMPORTANT]
 > Onboarded custom IPv6 address prefixes have several unique attributes which make them different than custom IPv4 address prefixes.
 
 * Custom IPv6 prefixes use a *parent*/*child* model. In this model, the Microsoft Wide Area Network (WAN) advertises the global (parent) range, and the respective Azure regions advertise the regional (child) ranges.  Global ranges must be /48 in size, while regional ranges must always be /64 size.  You can have multiple /64 ranges per region.
 
-* Only the global range needs to be validated using the steps detailed in the [Create Custom IP Address Prefix](create-custom-ip-address-prefix-portal.md) articles.  The regional ranges are derived from the global range in a similar manner to the way public IP prefixes are derived from custom IP prefixes.
+* Only the global range needs to be validated using the steps detailed in the [Create Custom IP Address Prefix](../articles/virtual-network/ip-services/create-custom-ip-address-prefix-portal.md) articles.  The regional ranges are derived from the global range in a similar manner to the way public IP prefixes are derived from custom IP prefixes.
 
 * Public IPv6 prefixes must be derived from the regional ranges.  Only the first 2048 IPv6 addresses of each regional /64 custom IP prefix can be utilized as valid IPv6 space.  Attempting to create public IPv6 prefixes that span beyond this will result in an error.