Skip to content

Commit e603e76

Browse files
author
Michael Bender
committed
initial commit - moved BYOIP
1 parent a26db79 commit e603e76

6 files changed

+320
-87
lines changed

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

Lines changed: 164 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -12,15 +12,11 @@ maims.date: 07/25/2024
1212

1313
# Create a custom IPv4 address prefix using the Azure portal
1414

15-
A custom IPv4 address prefix enables you to bring your own IPv4 ranges to Microsoft and associate it to your Azure subscription. You maintain ownership of the range while Microsoft would be permitted to advertise it to the Internet. A custom IP address prefix functions as a regional resource that represents a contiguous block of customer owned IP addresses.
15+
In this article, you learn how to create a custom IPv4 address prefix using the Azure portal. You prepare a range to provision, provision the range for IP allocation, and enable the range to be advertised by Microsoft.
1616

17-
The steps in this article detail the process to:
17+
A custom IPv4 address prefix enables you to bring your own IPv4 ranges to Microsoft and associate it to your Azure subscription. You maintain ownership of the range while Microsoft would be permitted to advertise it to the Internet. A custom IP address prefix functions as a regional resource that represents a contiguous block of customer owned IP addresses.
1818

19-
* Prepare a range to provision
20-
21-
* Provision the range for IP allocation
22-
23-
* Enable the range to be advertised by Microsoft
19+
[!INCLUDE [ip-services-custom-ip-global-regional-unified-model](../../../includes/ip-services-custom-ip-global-regional-unified-model.md)]
2420

2521
## Prerequisites
2622

@@ -67,10 +63,13 @@ If you choose to install and use PowerShell locally, this article requires the A
6763

6864
[!INCLUDE [ip-services-pre-provisioning-steps](../../../includes/ip-services-pre-provisioning-steps.md)]
6965

70-
## Provisioning steps
66+
67+
## Provisioning and Commissioning a Custom IPv4 Prefix
7168

7269
# [Azure portal](#tab/azureportal)
7370

71+
# [**Provisioning/Commissioning steps (Unified Model)**](#tab/create-custom-ip-prefix-portal-unified)
72+
7473
The following steps display the procedure for provisioning a sample customer range (1.2.3.0/24) to the US West 2 region.
7574

7675
> [!NOTE]
@@ -80,7 +79,7 @@ The following steps display the procedure for provisioning a sample customer ran
8079

8180
Sign in to the [Azure portal](https://portal.azure.com).
8281

83-
## Create and provision a custom IP address prefix
82+
## Create and provision a unified custom IP address prefix
8483

8584
1. In the search box at the top of the portal, enter **Custom IP**.
8685

@@ -118,7 +117,7 @@ The range is pushed to the Azure IP Deployment Pipeline. The deployment process
118117
> [!IMPORTANT]
119118
> After the custom IP prefix is in a "Provisioned" state, a child public IP prefix can be created. These public IP prefixes and any public IP addresses can be attached to networking resources. For example, virtual machine network interfaces or load balancer front ends. The IPs won't be advertised and therefore won't be reachable. For more information on a migration of an active prefix, see [Manage a custom IP prefix](manage-custom-ip-address-prefix.md).
120119
121-
## Create a public IP prefix from custom IP prefix
120+
## Create a public IP prefix from unified custom IP prefix
122121

123122
When you create a prefix, you must create static IP addresses from the prefix. In this section, you create a static IP address from the prefix you created earlier.
124123

@@ -147,9 +146,9 @@ When you create a prefix, you must create static IP addresses from the prefix. I
147146

148147
6. Select **Review + create**, and then **Create** on the following page.
149148

150-
10. Repeat steps 1-5 to return to the **Overview** page for **myCustomIPPrefix**. You see **myPublicIPPrefix** listed under the **Associated public IP prefixes** section. You can now allocate standard SKU public IP addresses from this prefix. For more information, see [Create a static public IP address from a prefix](manage-public-ip-address-prefix.md#create-a-static-public-ip-address-from-a-prefix).
149+
7. Repeat steps 1-3 to return to the **Overview** page for **myCustomIPPrefix**. You see **myPublicIPPrefix** listed under the **Associated public IP prefixes** section. You can now allocate standard SKU public IP addresses from this prefix. For more information, see [Create a static public IP address from a prefix](manage-public-ip-address-prefix.md#create-a-static-public-ip-address-from-a-prefix).
151150

152-
## Commission the custom IP address prefix
151+
## Commission the unified custom IP address prefix
153152

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

@@ -163,6 +162,159 @@ When the custom IP prefix is in **Provisioned** state, update the prefix to begi
163162

164163
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 **Commissioning**, followed in the future by **Commissioned**. The advertisement rollout isn't binary and the range will be partially advertised while still in the **Commissioning** status.
165164

165+
> [!NOTE]
166+
> The estimated time to fully complete the commissioning process is 3-4 hours.
167+
168+
> [!IMPORTANT]
169+
> As the custom IP prefix transitions to a **Commissioned** state, the range is being advertised with Microsoft from the local Azure region and globally to the Internet by Microsoft's wide area network under Autonomous System Number (ASN) 8075. Advertising this same range to the Internet from a location other than Microsoft at the same time could potentially create BGP routing instability or traffic loss. For example, a customer on-premises building. Plan any migration of an active range during a maintenance period to avoid impact. To prevent these issues during initial deployment, you can choose the regional only commissioning option where your custom IP prefix will only be advertised within the Azure region it is deployed in. For more information, see [Manage a custom IP address prefix (BYOIP)](manage-custom-ip-address-prefix.md).
170+
171+
# [**Provisioning/Commissioning steps (Global/Regional Model)**](#tab/create-custom-ip-prefix-portal-globalregional)
172+
173+
The following steps display the modified steps for provisioning a sample global (parent) IP range (1.2.3.0/4) and regional (child) IP ranges to the US West 2 and US East 2 Regions.
174+
175+
> [!NOTE]
176+
> Clean up or delete steps aren't shown on this page given the nature of the resource. For information on removing a provisioned custom IP prefix, see [Manage custom IP prefix](manage-custom-ip-address-prefix.md).
177+
178+
### Provision a global custom IP address prefix
179+
180+
Sign in to the [Azure portal](https://portal.azure.com).
181+
182+
## Create and provision a global custom IP address prefix
183+
184+
1. In the search box at the top of the portal, enter **Custom IP**.
185+
186+
2. In the search results, select **Custom IP Prefixes**.
187+
188+
3. Select **+ Create**.
189+
190+
4. In **Create a custom IP prefix**, enter or select the following information:
191+
192+
| Setting | Value |
193+
| ------- | ----- |
194+
| **Project details** | |
195+
| Subscription | Select your subscription |
196+
| Resource group | Select **Create new**.</br> Enter **myResourceGroup**.</br> Select **OK**. |
197+
| **Instance details** | |
198+
| Name | Enter **myCustomIPGlobalPrefix**. |
199+
| Region | Select **West US 2**. |
200+
| IP Version | Select IPv4. |
201+
| IP prefix range | Select Global. |
202+
| Global IPv4 Prefix (CIDR) | Enter **1.2.3.0/24**. |
203+
| ROA expiration date | Enter your ROA expiration date in the **yyyymmdd** format. |
204+
| Signed message | Paste in the output of **$byoipauthsigned** from the pre-provisioning section. |
205+
206+
5. Select the **Review + create** tab or the blue **Review + create** button at the bottom of the page.
207+
208+
6. Select **Create**.
209+
The range is pushed to the Azure IP Deployment Pipeline. The deployment process is asynchronous. You can check the status by reviewing the **Commissioned state** field for the custom IP prefix.
210+
211+
> [!NOTE]
212+
> The estimated time to complete the provisioning process is 30 minutes.
213+
214+
### Provision regional custom IP address prefixes
215+
216+
After the global custom IP prefix is in a **Provisioned** state, regional custom IP prefixes can be created. These ranges must always be of size /64 to be considered valid. The ranges can be created in any region (it doesn't need to be the same as the global custom IP prefix), keeping in mind any geolocation restrictions associated with the original global range. The "children" custom IP prefixes advertise from the region they're created in. Because the validation is only done for global custom IP prefix provision, no Authorization or Signed message is required (but availability zones can be utilized).
217+
218+
In the same **Create a custom IP prefix** page as before, enter or select the following information:
219+
220+
| Setting | Value |
221+
| ------- | ----- |
222+
| **Project details** | |
223+
| Subscription | Select your subscription |
224+
| Resource group | Select **Create new**.</br> Enter **myResourceGroup**.</br> Select **OK**. |
225+
| **Instance details** | |
226+
| Name | Enter **myCustomIPRegionalPrefix1**. |
227+
| Region | Select **West US 2**. |
228+
| IP Version | Select IPv4. |
229+
| IP prefix range | Select Regional. |
230+
| Custom IP prefix parent | Select myCustomIPGlobalPrefix (1.2.3.0/24) from the drop-down menu. |
231+
| Regional IPv4 Prefix (CIDR) | Enter **1.2.3.0/25**. |
232+
| ROA expiration date | Enter your ROA expiration date in the **yyyymmdd** format. |
233+
| Signed message | Paste in the output of **$byoipauthsigned** from the pre-provisioning section. |
234+
| Availability Zones | Select **Zone-redundant**. |
235+
236+
After creation, go through the flow a second time for another regional prefix in a new region.
237+
238+
| Setting | Value |
239+
| ------- | ----- |
240+
| **Project details** | |
241+
| Subscription | Select your subscription |
242+
| Resource group | Select **Create new**.</br> Enter **myResourceGroup**.</br> Select **OK**. |
243+
| **Instance details** | |
244+
| Name | Enter **myCustomIPRegionalPrefix2**. |
245+
| Region | Select **East US 2**. |
246+
| IP Version | Select IPv4. |
247+
| IP prefix range | Select Regional. |
248+
| Custom IP prefix parent | Select myCustomIPGlobalPrefix (1.2.3.0/24) from the drop-down menu. |
249+
| Regional IPv4 Prefix (CIDR) | Enter **1.2.3.128/25**. |
250+
| ROA expiration date | Enter your ROA expiration date in the **yyyymmdd** format. |
251+
| Signed message | Paste in the output of **$byoipauthsigned** from the pre-provisioning section. |
252+
| Availability Zones | Select Zone **3**. |
253+
254+
> [!IMPORTANT]
255+
> After the regional custom IP prefix is in a "Provisioned" state, a child public IP prefix can be created. These public IP prefixes and any public IP addresses can be attached to networking resources. For example, virtual machine network interfaces or load balancer front ends. The IPs won't be advertised and therefore won't be reachable. For more information on a migration of an active prefix, see [Manage a custom IP prefix](manage-custom-ip-address-prefix.md).
256+
257+
## Create a public IP prefix from regional custom IP prefix
258+
259+
When you create a prefix, you must create static IP addresses from the prefix. In this section, you create a static IP address from the prefix you created earlier.
260+
261+
1. In the search box at the top of the portal, enter **Custom IP**.
262+
263+
2. In the search results, select **Custom IP Prefixes**.
264+
265+
3. In **Custom IP Prefixes**, select **myCustomIPPrefix**.
266+
267+
4. In **Overview** of **myCustomIPPrefix**, select **+ Add a public IP prefix**.
268+
269+
5. Enter or select the following information in the **Basics** tab of **Create a public IP prefix**.
270+
271+
| Setting | Value |
272+
| ------- | ----- |
273+
| **Project details** | |
274+
| Subscription | Select your subscription. |
275+
| Resource group | Select **myResourceGroup**. |
276+
| **Instance details** | |
277+
| Name | Enter **myPublicIPPrefix**. |
278+
| Region | Select **West US 2**. The region of the public IP prefix must match the region of the regional custom IP prefix. |
279+
| IP version | Select **IPv4**. |
280+
| Prefix ownership | Select **Custom prefix**. |
281+
| Custom IP prefix | Select **myCustomIPRegionalPrefix1**. |
282+
| Prefix size | Select a prefix size. The size can be as large as the regional custom IP prefix. |
283+
284+
6. Select **Review + create**, and then **Create** on the following page.
285+
286+
7. Repeat steps 1-3 to return to the **Overview** page for **myCustomIPPrefix**. You see **myPublicIPPrefix** listed under the **Associated public IP prefixes** section. You can now allocate standard SKU public IP addresses from this prefix. For more information, see [Create a static public IP address from a prefix](manage-public-ip-address-prefix.md#create-a-static-public-ip-address-from-a-prefix).
287+
288+
### Commission the custom IP address prefixes
289+
290+
When commissioning custom IP prefixes using this model, the global and regional prefixes are treated separately. In other words, commissioning a regional custom IP prefix isn't connected to commissioning the global custom IP prefix.
291+
292+
:::image type="content" source="./media/create-custom-ip-address-prefix-portal/any-region-prefix-v4.png" alt-text="Diagram of custom IPv4 prefix showing parent prefix and child prefixes across multiple regions.":::
293+
294+
The safest strategy for range migrations is as follows:
295+
1. Provision all required regional custom IP prefixes in their respective regions. Create public IP prefixes and public IP addresses and attach to resources.
296+
2. Commission each regional custom IP prefix and test connectivity to the IPs within the region. Repeat for each regional custom IP prefix.
297+
3. After all regional custom IP prefixes (and derived prefixes/IPs) are verified to work as expected, commission the global custom IP prefix, which will advertise the larger range to the Internet.
298+
299+
To commission a custom IP prefix (regional or global) using the portal:
300+
301+
1. In the search box at the top of the portal, enter **Custom IP** and select **Custom IP Prefixes**.
302+
303+
2. Verify the custom IP prefix is in a **Provisioned** state.
304+
305+
3. In **Custom IP Prefixes**, select the desired custom IP prefix.
306+
307+
4. In **Overview** page of the custom IP prefix, select the **Commission** button near the top of the screen. If the range is global, it begins advertising from the Microsoft WAN. If the range is regional, it advertises only from the specific region.
308+
309+
> [!NOTE]
310+
> The estimated time to fully complete the commissioning process for a custom IP global prefix is 3-4 hours. The estimated time to fully complete the commissioning process for a custom IP regional prefix is 30 minutes.
311+
312+
It's possible to commission the global custom IP prefix prior to the regional custom IP prefixes. Doing this advertises the global range to the Internet before the regional prefixes are ready so it's not recommended for migrations of active ranges. You can decommission a global custom IP prefix while there are still active (commissioned) regional custom IP prefixes. Also, you can decommission a regional custom IP prefix while the global prefix is still active (commissioned).
313+
314+
> [!IMPORTANT]
315+
> As the global custom IP prefix transitions to a **Commissioned** state, the range is being advertised with Microsoft from the local Azure region and globally to the Internet by Microsoft's wide area network under Autonomous System Number (ASN) 8075. Advertising this same range to the Internet from a location other than Microsoft at the same time could potentially create BGP routing instability or traffic loss. For example, a customer on-premises building. Plan any migration of an active range during a maintenance period to avoid impact.
316+
317+
166318
[!INCLUDE [ip-services-provisioning-note-1](../../../includes/ip-services-provisioning-note-1.md)]
167319

168320
# [Azure CLI](#tab/azurecli/)

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

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@ description: Learn about what an Azure custom IP address prefix is and how it en
55
services: virtual-network
66
author: mbender-ms
77
ms.author: mbender
8-
ms.service: azure-virtual-network
8+
ms.service: virtual-network
99
ms.subservice: ip-services
1010
ms.topic: conceptual
11-
ms.date: 08/24/2023
11+
ms.date: 08/05/2024
1212
---
1313

1414
# Custom IP address prefix (BYOIP)
@@ -47,26 +47,27 @@ When ready, you can issue the command to have your range advertised from Azure a
4747

4848
## Limitations
4949

50-
* A custom IPv4 prefix must be associated with a single Azure region.
50+
* By default, you can bring a maximum of five custom IP prefixes per region to Azure. This limit can be increased upon request.
5151

52-
* You can bring a maximum of five prefixes per region to Azure.
53-
54-
* A custom IPv4 Prefix must be between /21 and /24; a global (parent) custom IPv6 prefix must be /48.
52+
* By default
53+
- a unified custom IPv4 Prefix must be between /21 and /24
54+
- a global (parent) custom IPv4 prefix must be between /21 and /24, a regional (child) custom IPv4 prefix must be between /22 and /26 (dependent on the size of their respective parent range, which they must be at least one level smaller than)
55+
- a global (parent) custom IPv6 prefix must be /48, a regional (child) custom IPv6 prefix must be /64
5556

5657
* Custom IP prefixes don't currently support derivation of IPs with Internet Routing Preference or that use Global Tier (for cross-region load-balancing).
5758

5859
* In regions with [availability zones](../../availability-zones/az-overview.md), a custom IPv4 prefix (or a regional custom prefix) must be specified as either zone-redundant or assigned to a specific zone. It can't be created with no zone specified in these regions. All IPs from the prefix must have the same zonal properties.
5960

6061
* The advertisements of IPs from a custom IP prefix over an Azure ExpressRoute Microsoft peering isn't currently supported.
6162

62-
* Custom IP prefixes don't support Reverse DNS lookup using Azure-owned zones; customers must onboard their own Reverse Zones to Azure DNS
63+
* Custom IP prefixes don't support Reverse DNS lookup using Azure-owned zones; customers must onboard their own Reverse Zones to Azure DNS.
6364

6465
* Once provisioned, custom IP prefix ranges can't be moved to another subscription. Custom IP address prefix ranges can't be moved within resource groups in a single subscription. It's possible to derive a public IP prefix from a custom IP prefix in another subscription with the proper permissions as described [here](manage-custom-ip-address-prefix.md#permissions).
6566

6667
* IPs brought to Azure may have a delay of up to a week before they can be used for Windows Server Activation.
6768

6869
> [!IMPORTANT]
69-
> 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).
70+
> 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).
7071
7172
## Pricing
7273

@@ -80,4 +81,4 @@ When ready, you can issue the command to have your range advertised from Azure a
8081

8182
- To create a custom IPv4 address prefix using PowerShell, see [Create a custom IPv4 address prefix using Azure PowerShell](create-custom-ip-address-prefix-powershell.md).
8283

83-
- For more information about the management of a custom IP address prefix, see [Manage a custom IP address prefix](create-custom-ip-address-prefix-powershell.md).
84+
- For more information about the management of a custom IP address prefix, see [Manage a custom IP address prefix](create-custom-ip-address-prefix-powershell.md).

0 commit comments

Comments
 (0)