Skip to content

Commit 141be0a

Browse files
authored
Merge pull request #124841 from stantoni-msft/patch-1
CSS-Networking: Update create-custom-ip-address-prefix-ipv6-portal.md
2 parents 180644f + 32f221b commit 141be0a

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,9 @@ If you choose to install and use PowerShell locally, this article requires the A
5656

5757
To utilize the Azure BYOIP feature, you must perform and number of steps prior to the provisioning of your IPv6 address range. Refer to the [IPv4 instructions](create-custom-ip-address-prefix-portal.md#pre-provisioning-steps) for details. All these steps should be completed for the IPv6 global (parent) range.
5858

59+
> [!NOTE]
60+
> When hexadecimal IPv6 characters (a-f) are used in an IPv6 Prefix (CIDR), the case of the Custom IP Prefix IPv6 Prefix (CIDR) used in the Custom IP Prefix object must match the case of the IPv6 prefix as generated for your Custom IP Prefix Signed message.
61+
5962
## Provisioning for IPv6
6063

6164
The following steps display the modified steps for provisioning a sample global (parent) IPv6 range (2a05:f500:2::/48) and regional (child) IPv6 ranges. Some of the steps have been abbreviated or condensed from the [IPv4 instructions](create-custom-ip-address-prefix-portal.md) to focus on the differences between IPv4 and IPv6.

0 commit comments

Comments
 (0)