Skip to content

Commit 89c94c6

Browse files
authored
Update manage-custom-ip-address-prefix.md
1 parent 63f6824 commit 89c94c6

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -142,6 +142,9 @@ Update-AzCustomIpPrefix
142142

143143
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.
144144

145+
> [!NOTE]
146+
> 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.
147+
145148
## Deprovision/Delete a custom IP prefix
146149

147150
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
269272

270273
- 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).
271274

272-
- 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).
275+
- 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).

0 commit comments

Comments
 (0)