Merge pull request #295245 from brianlehr/patch-80

Update manage-custom-ip-address-prefix.md

Author: prmerger-automator[bot]

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

@@ -142,6 +142,9 @@ Update-AzCustomIpPrefix
 
 The operation is asynchronous. You can check the status by reviewing the **Commissioned state** field for the custom IP prefix. Initially, the status will show the prefix as **InternetDecommissioningInProgress**, followed in the future by **CommissionedNoInternetAdvertise**. The advertisement to the Internet isn't binary and the range is partially advertised while still in the **InternetDecommissioningInProgress** status.
 
+> [!NOTE]
+> There is no need to regionally commission regional ("child") prefixes when using the glboal/regional model, as their inherent nature means that they will only advertise from within the region, and the commissioning of the global ("parent") prefix is what will advertise the range to the Internet and other Azure regions.
+
 ## Deprovision/Delete a custom IP prefix
 
 To fully remove a custom IP prefix, it must be deprovisioned and then deleted. 
@@ -269,4 +272,4 @@ When you onboard or remove a custom IP prefix from Azure, the system updates the
 
 - To create a custom IP address prefix using the Azure portal, see [Create custom IP address prefix using the Azure portal](create-custom-ip-address-prefix-portal.md).
 
-- To create a custom IP address prefix using PowerShell, see [Create a custom IP address prefix using Azure PowerShell](create-custom-ip-address-prefix-powershell.md).
+- To create a custom IP address prefix using PowerShell, see [Create a custom IP address prefix using Azure PowerShell](create-custom-ip-address-prefix-powershell.md).