You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-network/ip-services/custom-ip-address-prefix.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,10 +49,10 @@ When ready, you can issue the command to have your range advertised from Azure a
49
49
50
50
* By default, you can bring a maximum of five custom IP prefixes per region to Azure. This limit can be increased upon request.
51
51
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
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
56
56
57
57
* Custom IP prefixes don't currently support derivation of IPs with Internet Routing Preference or that use Global Tier (for cross-region load-balancing).
Copy file name to clipboardExpand all lines: includes/ip-services-custom-ip-prefix-certificate-creation.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ The following steps show the steps required to prepare sample customer range (1.
40
40
41
41
After the public comments are filled out, the Whois/RDAP record should look like the following example. When copying, ensure there aren't spaces, or carriage returns and include all dashes:
42
42
43
-
:::image type="content" source="./media/ip-services-pre-provisioning-steps/certificate-example.png" alt-text="Screenshot of example certificate comment":::
43
+
:::image type="content" source="./media/ip-services-pre-provisioning-steps/certificate-example.png" alt-text="Screenshot of example certificate comment.":::
44
44
45
45
3. To create the message passed to Microsoft, create a string that contains relevant information about your prefix and subscription. Sign this message with the key pair generated previously. Use the following format, substituting your subscription ID, prefix to be provisioned, and expiration date matching the Validity Date on the ROA. Ensure the format is in that order.
46
46
@@ -92,7 +92,7 @@ The following steps show the steps required to prepare sample customer range (1.
92
92
93
93
After the public comments are filled out, the Whois/RDAP record should look like the following example. Ensure there aren't spaces or carriage returns and include all dashes:
94
94
95
-
:::image type="content" source="./media/ip-services-pre-provisioning-steps/certificate-example.png" alt-text="Screenshot of example certificate comment":::
95
+
:::image type="content" source="./media/ip-services-pre-provisioning-steps/certificate-example.png" alt-text="Screenshot of example certificate comment.":::
96
96
97
97
3. To create the message passed to Microsoft, create a string that contains relevant information about your prefix and subscription. Sign this message with the key pair generated previously. Use the following format, substituting your subscription ID, prefix to be provisioned, and expiration date matching the Validity Date on the ROA. Ensure the format is in that order.
98
98
@@ -110,6 +110,9 @@ The following steps show the steps required to prepare sample customer range (1.
0 commit comments