Merge pull request #205601 from asudbring/byoip-portal-message

Added table for portal messages to custom IP prefix manage article

Author: JamesJBarnett

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

@@ -153,6 +153,62 @@ Before you decommission a custom IP prefix, ensure it has no public IP prefixes
 
 To migrate a custom IP prefix, it must first be deprovisioned from one region. A new custom IP prefix with the same CIDR can then be created in another region.
 
+### Status messages
+
+When onboarding or removing a custom IP prefix from Azure, the **FailedReason** attribute of the resource will be updated. If the Azure portal is used, the message will be shown as a top-level banner. The following tables list the status messages when onboarding or removing a custom IP prefix.
+
+#### Validation failures
+
+| Failure message | Explanation |
+| --------------- | ----------- |
+| CustomerSignatureNotVerified | The signed message cannot be verified against the authentication message using the Whois/RDAP record for the prefix. |
+| NotAuthorizedToAdvertiseThisPrefix </br> or </br> ASN8075NotAllowedToAdvertise | ASN8075 is not authorized to advertise this prefix. Make sure your route origin authorization (ROA) is submitted correctly. Verify ROA. |
+| PrefixRegisteredInAfricaAndSouthAmericaNotAllowedInOtherRegion | IP prefix is registered with AFRINIC or LACNIC. This prefix is not allowed to be used outside Africa/South America. |
+| NotFindRoutingRegistryToGetCertificate | Cannot find the public key for the IP prefix using the registration data access protocol (RDAP) of the regional internet registry (RIR). |
+| CIDRInAuthorizationMessageNotMatchCustomerIP | The CIDR in the authorization message does not match the submitted IP address. |
+| ExpiryDateFormatInvalidOrNotInThefuture | The expiration date provided in the authorization message is in the wrong format or expired. Expected format is yyyymmdd. |
+| AuthMessageFormatInvalid | Authorization message format is not valid. Expected format is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx1.2.3.0/24yyyymmdd. |
+| CannotParseValidCertificateFromRIRPage | Cannot parse the public key for the IP prefix using the registration data access protocol (RDAP) of the regional internet registry (RIR). |
+| ROANotFound | Unable to find route origin authorization (ROA) for validation. |
+| CertFromRIRPageExpired | The public key provided by the registration data access protocol (RDAP) of the regional internet registry (RIR) is expired. |
+| InvalidPrefixLengthInROA | The prefix length provided does not match the prefix in the route origin authorization (ROA). |
+| RIRNotSupport | Only prefixes registered at ARIN, RIPE, APNIC, AFRINIC, and LACNIC are supported. |
+| InvalidCIDRFormat | The CIDR format is not valid. Expected format is 10.10.10.0/16. |
+| InvalidCIDRFormatInAuthorizationMessage | The format of the CIDR in the authorization message is not valid. Expected format is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx1.2.3.0/24yyyymmdd. |
+| OperationFailedPleaseRetryLaterOrContactSupport | Unknown error. Contact support. |
+
+> [!NOTE]
+> Not all the messages shown during the commissioning or decommissioning process indicate failure-- some simply provide more granular status.
+
+#### Commission status
+
+| Status message | Explanation |
+| --------------- | ----------- |
+| RegionalCommissioningInProgress | The range is being commissioned to advertise regionally within Azure. |
+| InternetCommissioningInProgress | The range is now advertising regionally within Azure and is being commissioned to advertise to the internet. |
+
+#### Decommission status
+
+| Status message | Explanation |
+| -------------- | ----------- |
+| InternetDecommissioningInProgress | The range is currently being decommissioned. The range will no longer be advertised to the internet. |
+| RegionalDecommissioningInProgress | The range is no longer advertised to the internet and is currently being decommissioned. The range will no longer be advertised regionally within Azure. |
+
+#### Commission failures
+
+| Failure message | Explanation |
+| --------------- | ----------- |
+| CommissionFailedRangeNotAdvertised | The range was unable to be advertised regionally within Azure or to the internet. |
+| CommissionFailedRangeRegionallyAdvertised | The range was unable to be advertised to the internet but is being advertised within Azure. |
+| CommissionFailedRangeInternetAdvertised | The range was unable to be advertised optimally but is being advertised to the internet and within Azure. |
+
+#### Decommission failures
+
+| Failure message | Explanation |
+| --------------- | ----------- |
+| DecommissionFailedRangeInternetAdvertised | The range was unable to be decommissioned and is still advertised to the internet and within Azure. |
+| DecommissionFailedRangeRegionallyAdvertised | The range was unable to be decommissioned and is still advertised within Azure but is no longer advertised to the internet. |
+
 ## Next steps
 
 - To learn about scenarios and benefits of using a custom IP prefix, see [Custom IP address prefix (BYOIP)](custom-ip-address-prefix.md).