Merge pull request #276502 from Blackmist/255250-ipv6

adding note

Author: prmerger-automator[bot]

articles/machine-learning/how-to-configure-private-link.md

@@ -305,6 +305,7 @@ You can use IP network rules to allow access to your workspace and endpoint from
 > [!WARNING]
 > * Enable your endpoint's [public network access flag](concept-secure-online-endpoint.md#secure-inbound-scoring-requests) if you want to allow access to your endpoint from specific public internet IP address ranges.
 > * When you enable this feature, this has an impact to all existing public endpoints associated with your workspace. This may limit access to new or existing endpoints. If you access any endpoints from a non-allowed IP, you get a 403 error.
+> * You can only use IPv4 addresses.
 > * To use this feature with Azure Machine Learning managed virtual network, see [Azure Machine Learning managed virtual network](how-to-managed-network.md#scenario-enable-access-from-selected-ip-addresses).
 
 # [Azure CLI](#tab/cli)

articles/machine-learning/how-to-managed-network.md

@@ -1055,6 +1055,9 @@ If you want to enable access from specific IP addresses, use the following actio
 1. Enable public network access to the workspace. For more information, see [public network access enabled](how-to-configure-private-link.md#enable-public-access).
 1. Add your IP addresses to the firewall for Azure Machine Learning. For more information, see [enable access only from IP ranges](how-to-configure-private-link.md#enable-public-access-only-from-internet-ip-ranges-preview).
 
+    > [!NOTE]
+    > Only IPv4 addresses are supported.
+
 ## Private endpoints
 
 Private endpoints are currently supported for the following Azure services: