Merge pull request #194129 from andreamichaelmsft/patch-8

UDR Service Tags GA Update

Author: PRMerger10

articles/virtual-network/virtual-networks-udr-overview.md

@@ -95,7 +95,7 @@ You cannot specify **VNet peering** or **VirtualNetworkServiceEndpoint** as the
 
 ### Service Tags for user-defined routes
 
-You can now specify a [Service Tag](service-tags-overview.md) as the address prefix for a user-defined route instead of an explicit IP range. A Service Tag represents a group of IP address prefixes from a given Azure service. Microsoft manages the address prefixes encompassed by the service tag and automatically updates the service tag as addresses change, minimizing the complexity of frequent updates to user-defined routes and reducing the number of routes you need to create. You can currently create 25 or less routes with Service Tags in each route table. </br>
+You can now specify a [service tag](service-tags-overview.md) as the address prefix for a user-defined route instead of an explicit IP range. A service tag represents a group of IP address prefixes from a given Azure service. Microsoft manages the address prefixes encompassed by the service tag and automatically updates the service tag as addresses change, minimizing the complexity of frequent updates to user-defined routes and reducing the number of routes you need to create. You can currently create 25 or less routes with service tags in each route table. With this release, using service tags in routing scenarios for containers is also supported. </br>
 
 #### Exact Match
 When there is an exact prefix match between a route with an explicit IP prefix and a route with a Service Tag, preference is given to the route with the explicit prefix. When multiple routes with Service Tags have matching IP prefixes, routes will be evaluated in the following order: 

includes/machine-learning-compute-user-defined-routes.md

@@ -8,6 +8,10 @@ ms.author: larryfr
 
 When using Azure Machine Learning __compute instance__ (with a public IP) or __compute cluster__, allow inbound traffic from Azure Batch management and Azure Machine Learning services. Compute instance with no public IP (preview) does not require this inbound communication. A Network Security Group allowing this traffic is dynamically created for you, however you may need to also create user-defined routes (UDR) if you have a firewall. When creating a UDR for this traffic, you can use either **IP Addresses** or **service tags** to route the traffic.
 
+> [!IMPORTANT]
+> Using service tags with user-defined routes is now GA. For more information, see [Virtual Network routing](../articles/virtual-network/virtual-networks-udr-overview.md#service-tags-for-user-defined-routes).
+
+
 > [!TIP]
 > While a compute instance without a public IP (a preview feature) does not need a UDR for this inbound traffic, you will still need these UDRs if you also use a compute cluster or a compute instance with a public IP.
 
@@ -25,7 +29,7 @@ When creating the UDR, set the __Next hop type__ to __Internet__. The following
 
 :::image type="content" source="./media/machine-learning-compute-user-defined-routes/user-defined-route.png" alt-text="Image of a user-defined route configuration":::
 
-# [Service tag (preview) routes](#tab/servicetag)
+# [Service tag routes](#tab/servicetag)
 
 Create user-defined routes for the following service tags:
 
@@ -41,4 +45,4 @@ az network route-table route create -g MyResourceGroup --route-table-name MyRout
 
 ---
 
-For information on configuring UDR, see [Route network traffic with a routing table](../articles/virtual-network/tutorial-create-route-table-portal.md).
+For information on configuring UDR, see [Route network traffic with a routing table](../articles/virtual-network/tutorial-create-route-table-portal.md).