Merge pull request #271915 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/expressroute/how-to-configure-coexisting-gateway-portal.md

@@ -33,7 +33,7 @@ The steps to configure both scenarios are covered in this article. You can confi
 
 * **Only route-based VPN gateway is supported.** You must use a route-based [VPN gateway](../vpn-gateway/vpn-gateway-about-vpngateways.md). You also can use a route-based VPN gateway with a VPN connection configured for 'policy-based traffic selectors' as described in [Connect to multiple policy-based VPN devices](../vpn-gateway/vpn-gateway-connect-multiple-policybased-rm-ps.md).
 * **ExpressRoute-VPN Gateway coexist configurations are not supported on the Basic SKU**.
-* **Both the ExpressRoute and VPN gateways must be able to communicate with each other via BGP to function properly.** If using a UDR on the gateway subnet, ensure that it does not include a route for the gateway subnet rage itself as this will interfere with BGP traffic.
+* **Both the ExpressRoute and VPN gateways must be able to communicate with each other via BGP to function properly.** If using a UDR on the gateway subnet, ensure that it doesn't include a route for the gateway subnet range itself as this will interfere with BGP traffic.
 * **If you want to use transit routing between ExpressRoute and VPN, the ASN of Azure VPN Gateway must be set to 65515.** Azure VPN Gateway supports the BGP routing protocol. For ExpressRoute and Azure VPN to work together, you must keep the Autonomous System Number of your Azure VPN gateway at its default value, 65515. If you previously selected an ASN other than 65515 and you change the setting to 65515, you must reset the VPN gateway for the setting to take effect.
 * **The gateway subnet must be /27 or a shorter prefix**, such as /26, /25, or you receive an error message when you add the ExpressRoute virtual network gateway.
 * **Coexistence for IPv4 traffic only.** ExpressRoute co-existence with VPN gateway is supported, but only for IPv4 traffic. IPv6 traffic isn't supported for VPN gateways.

articles/machine-learning/how-to-package-models.md

@@ -230,21 +230,21 @@ You can create model packages in Azure Machine Learning, using the Azure CLI or
 
 ## Package a model that has dependencies in private Python feeds
 
-Model packages can resolve Python dependencies that are available in private feeds. To use this capability, you need to create a connection from your workspace to the feed and specify the credentials. The following Python code shows how you can configure the workspace where you're running the package operation.
+Model packages can resolve Python dependencies that are available in private feeds. To use this capability, you need to create a connection from your workspace to the feed and specify the PAT token configuration. The following Python code shows how you can configure the workspace where you're running the package operation.
 
 ```python
 from azure.ai.ml.entities import WorkspaceConnection
-from azure.ai.ml.entities import SasTokenConfiguration
+from azure.ai.ml.entities import PatTokenConfiguration
 
 # fetching secrets from env var to secure access, these secrets can be set outside or source code
-python_feed_sas = os.environ["PYTHON_FEED_SAS"]
+git_pat = os.environ["GIT_PAT"]
 
-credentials = SasTokenConfiguration(sas_token=python_feed_sas)
+credentials = PatTokenConfiguration(pat=git_pat)
 
 ws_connection = WorkspaceConnection(
-    name="<connection_name>",
-    target="<python_feed_url>",
-    type="python_feed",
+    name="<workspace_connection_name>",
+    target="<git_url>",
+    type="git",
     credentials=credentials,
 )
 

articles/machine-learning/how-to-secure-workspace-vnet.md

@@ -311,6 +311,12 @@ Azure Container Registry can be configured to use a private endpoint. Use the fo
 
     ---
 
+> [!TIP]
+> If you have configured your image build compute to use a compute cluster and want to reverse this decision, execute the same command but leave the image-build-compute reference empty:
+> ```azurecli
+>   az ml workspace update --name myworkspace --resource-group myresourcegroup --image-build-compute ''
+>    ```
+
 > [!TIP]
 > When ACR is behind a VNet, you can also [disable public access](../container-registry/container-registry-access-selected-networks.md#disable-public-network-access) to it.