BYOIP region and time for each deployment phrase

Question

Question 1:

From public docs, BYOIP can be only associated to one single region. We have requirement that they only have one prefix /24, but want resources in different regions consuming this prefix. It looks to me this is not possible as one prefix can be only associated to one single region. Need your help to check whether my understanding is correct and whether there's workaround to achieve cx requirement.

Question 2:

There're 3 phase process to bring IP prefix to Azure: Validation, Provision, Commission. Given everything is ready from Routing Internet Registry side. How long it will take for each single phase to complete.

Answer 1

Hello @Herman Ge ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand that you would like to know about the Azure BYOIP region limitation and the time required for each deployment phase.

It looks to me this is not possible as one prefix can be only associated to one single region. Need your help to check whether my understanding is correct and whether there's workaround to achieve cx requirement.

Your understanding is correct.

A custom IPv4 prefix must be associated with a single Azure region.

Refer: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/custom-ip-address-prefix#limitations

Even when you try to migrate a range from one region to another, it must first be deprovisioned from the previous region. So, there is no workaround for this limitation as of today.

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/manage-custom-ip-address-prefix#how-can-i-migrate-a-range-from-one-region-to-another

There are 3 phase processes to bring IP prefix to Azure: Validation, Provision, Commission. Given everything is ready from Routing Internet Registry side. How long it will take for each single phase to complete?

Validation process:

This process/phase is to make sure you own a registered (with one of the 5 major Regional Internet Registries) Public IP range which you can bring to Azure.

You then fill out a Route Origin Authorization (ROA) document that authorizes Microsoft to advertise the address range. The ROA needs to be digitally signed with the Resource Public Key Infrastructure (RPKI) of your RIR and should be filled on the appropriate Routing Internet Registry (RIR) website or via their API. After the ROA is complete and submitted, allow at least 24 hours for it to become available to Microsoft, where it will be verified to determine its authenticity and correctness as part of the provisioning process.

Post this follow the Certificate readiness step and create a certificate to authorize Microsoft to associate a prefix with your subscription.

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/create-custom-ip-address-prefix-portal#certificate-readiness

Provision process:

In this phase, you create and provision a custom IP address prefix within Azure portal. The estimated time to complete the provisioning process is 30 minutes.

Refer: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/create-custom-ip-address-prefix-portal#provisioning-steps

Commission process:

When the custom IP prefix is in Provisioned state, update the prefix to begin the process of advertising the range from Azure.

The estimated time to fully complete the commissioning process is 3-4 hours.

Refer: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/create-custom-ip-address-prefix-portal#commission-the-custom-ip-address-prefix

Kindly let us know if the above helps or you need further assistance on this issue.

---

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.