Merge pull request #266921 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: TimShererWithAquent

articles/ai-studio/how-to/configure-managed-network.md

@@ -241,7 +241,9 @@ To allow installation of __Python packages for training and deployment__, add ou
 | `*.tensorflow.org` | Used by some examples based on Tensorflow. |
 
 ### Scenario: Use Visual Studio Code
+Visual Studio Code relies on specific hosts and ports to establish a remote connection.
 
+#### Hosts
 If you plan to use __Visual Studio Code__ with Azure AI, add outbound _FQDN_ rules to allow traffic to the following hosts:
 
 > [!WARNING]
@@ -262,6 +264,9 @@ If you plan to use __Visual Studio Code__ with Azure AI, add outbound _FQDN_ rul
 * `pkg-containers.githubusercontent.com`
 * `github.com`
 
+#### Ports
+You must allow network traffic to ports 8704 to 8710. The VS Code server dynamically selects the first available port within this range.
+
 ### Scenario: Use HuggingFace models
 
 If you plan to use __HuggingFace models__ with Azure AI, add outbound _FQDN_ rules to allow traffic to the following hosts:
@@ -323,4 +328,4 @@ The Azure AI managed VNet feature is free. However, you're charged for the follo
 * Managed VNet uses private endpoint connection to access your private resources. You can't have a private endpoint and a service endpoint at the same time for your Azure resources, such as a storage account. We recommend using private endpoints in all scenarios.
 * The managed VNet is deleted when the Azure AI is deleted. 
 * Data exfiltration protection is automatically enabled for the only approved outbound mode. If you add other outbound rules, such as to FQDNs, Microsoft can't guarantee that you're protected from data exfiltration to those outbound destinations.
-* Using FQDN outbound rules increases the cost of the managed VNet because FQDN rules use Azure Firewall. For more information, see [Pricing](#pricing).
+* Using FQDN outbound rules increases the cost of the managed VNet because FQDN rules use Azure Firewall. For more information, see [Pricing](#pricing).

articles/aks/dapr-settings.md

@@ -65,7 +65,7 @@ az k8s-extension create --cluster-type managedClusters \
 --auto-upgrade-minor-version true \
 --configuration-settings "global.ha.enabled=true" \
 --configuration-settings "dapr_operator.replicaCount=2" \
---configuration-settings "global.nodeSelector.kubernetes\.io/zone: us-east-1c"
+--configuration-settings "global.nodeSelector.kubernetes\.io/zone=us-east-1c"
 ```
 
 For managing OS and architecture, use the [supported versions](https://github.com/dapr/dapr/blob/b8ae13bf3f0a84c25051fcdacbfd8ac8e32695df/docker/docker.mk#L50) of the `global.daprControlPlaneOs` and `global.daprControlPlaneArch` configuration:
@@ -241,7 +241,10 @@ az k8s-extension update --cluster-type managedClusters \
 
 ## Meet network requirements
 
-The Dapr extension for AKS and Arc for Kubernetes requires outbound URLs on `https://:443` to function. In addition to the `https://mcr.microsoft.com/daprio` URL for pulling Dapr artifacts, verify you've included the [outbound URLs required for AKS or Arc for Kubernetes](../azure-arc/kubernetes/network-requirements.md). 
+The Dapr extension for AKS and Arc for Kubernetes requires the following outbound URLs on `https://:443` to function:
+1. `https://mcr.microsoft.com/daprio` URL for pulling Dapr artifacts.
+2. `https://linuxgeneva-microsoft.azurecr.io/` URL for pulling some Dapr dependencies.
+3. The [outbound URLs required for AKS or Arc for Kubernetes](../azure-arc/kubernetes/network-requirements.md). 
 
 ## Next Steps
 

articles/azure-maps/about-azure-maps.md

@@ -236,6 +236,8 @@ Stay up to date on Azure Maps:
 [Get Map Tile]: /rest/api/maps/render/get-map-tile
 [Get Weather along route API]: /rest/api/maps/weather/getweatheralongroute
 [Render]: /rest/api/maps/render
+[Render v1]: /rest/api/maps/render?view=rest-maps-1.0
+[Render v2]: /rest/api/maps/render
 [REST APIs]: /rest/api/maps/
 [Route]: /rest/api/maps/route
 [Search]: /rest/api/maps/search?view=rest-maps-1.0&preserve-view=true

articles/azure-maps/indoor-map-dynamic-styling.md

@@ -151,3 +151,4 @@ Learn more by reading:
 [Create an indoor map]: tutorial-creator-indoor-maps.md
 [WFS API]: /rest/api/maps-creator/wfs
 [Creator for indoor maps]: creator-indoor-maps.md
+[What is Azure Maps Creator?]: about-creator.md

articles/azure-maps/migrate-from-bing-maps.md

@@ -173,6 +173,7 @@ Learn the details of how to migrate your Bing Maps application with these articl
 [free Azure account]: https://azure.microsoft.com/free/
 [manage authentication in Azure Maps]: how-to-manage-authentication.md
 [Microsoft Azure terms of use]: https://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=31
+[Microsoft Entra authentication]: /entra/fundamentals/whatis
 [Microsoft learning center shows]: https://aka.ms/AzureMapsVideos
 [Migrate a web app]: migrate-from-bing-maps-web-app.md
 [Route - Get Route Directions]: /rest/api/maps/route/get-route-directions

articles/azure-maps/quick-demo-map-app.md

@@ -107,6 +107,7 @@ In this quickstart, you created an Azure Maps account and a demo application. Ta
 [Find an address with Azure Maps search service]: how-to-search-for-address.md
 [free account]: https://azure.microsoft.com/free/?WT.mc_id=A261C142F
 [Interactive Search Quickstart.html]: https://github.com/Azure-Samples/AzureMapsCodeSamples/blob/master/Samples/Tutorials/Interactive%20Search/Interactive%20Search%20Quickstart.html
+[Microsoft Entra ID]: /entra/fundamentals/whatis
 [Next Steps]: #next-steps
 [open-source map controls]: open-source-projects.md#third-party-map-control-plugins
 [Search nearby points of interest with Azure Maps]: tutorial-search-location.md

articles/azure-maps/quick-ios-app.md

@@ -191,6 +191,7 @@ In this quickstart, you created your Azure Maps account and created a demo appli
 [Creating an Xcode Project for an App]: https://developer.apple.com/documentation/xcode/creating-an-xcode-project-for-an-app
 [free account]: https://azure.microsoft.com/free/
 [manage authentication in Azure Maps]: how-to-manage-authentication.md
+[Microsoft Entra ID]: /entra/fundamentals/whatis
 [Shared Key authentication]: azure-maps-authentication.md#shared-key-authentication
 [subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
 [‎Xcode]: https://apps.apple.com/cz/app/xcode/id497799835?mt=12

articles/databox-online/azure-stack-edge-gpu-connect-powershell-interface.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: how-to
-ms.date: 10/01/2023
+ms.date: 02/21/2024
 ms.author: alkohli
 ---
 # Manage an Azure Stack Edge Pro GPU device via Windows PowerShell
@@ -574,7 +574,10 @@ While changing the memory and processor usage, follow these guidelines.
 
 ## Connect to BMC
 
-Baseboard management controller (BMC) is used to remotely monitor and manage your device. This section describes the cmdlets that can be used to manage BMC configuration. Prior to running any of these cmdlets, [Connect to the PowerShell interface of the device](#connect-to-the-powershell-interface).
+> [!NOTE]
+> Baseboard management controller (BMC) is not available on Azure Stack Edge Pro 2 and Azure Stack Edge Mini R. The cmdlets described in this section only apply to Azure Stack Edge Pro GPU and Azure Stack Edge Pro R.
+
+BMC is used to remotely monitor and manage your device. This section describes the cmdlets that can be used to manage BMC configuration. Prior to running any of these cmdlets, [Connect to the PowerShell interface of the device](#connect-to-the-powershell-interface).
 
 - `Get-HcsNetBmcInterface`: Use this cmdlet to get the network configuration properties of the BMC, for example, `IPv4Address`, `IPv4Gateway`, `IPv4SubnetMask`, `DhcpEnabled`. 
     

articles/databox-online/azure-stack-edge-pro-2-deploy-install.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: tutorial
-ms.date: 10/17/2023
+ms.date: 02/21/2024
 ms.author: alkohli
 zone_pivot_groups: azure-stack-edge-device-deployment
 # Customer intent: As an IT admin, I need to understand how to install Azure Stack Edge Pro 2 in datacenter so I can use it to transfer data to Azure.  
@@ -273,8 +273,6 @@ On your device:
         - Two 10/1-Gbps interfaces, Port 1 and Port 2.
         - Two 100-Gbps interfaces, Port 3 and Port 4.
 
-    - A baseboard management controller (BMC).      
-
     - One network card corresponding to two high-speed ports and two built-in 10/1-GbE ports:
 
         - **Intel Ethernet X722 network adapter** - Port 1, Port 2.

articles/machine-learning/how-to-access-azureml-behind-firewall.md

@@ -197,7 +197,9 @@ To install the Azure Machine Learning extension on Kubernetes compute, all Azure
 
 
 ## Scenario: Visual Studio Code
+Visual Studio Code relies on specific hosts and ports to establish a remote connection.
 
+### Hosts
 The hosts in this section are used to install Visual Studio Code packages to establish a remote connection between Visual Studio Code and compute instances in your Azure Machine Learning workspace.
 
 > [!NOTE]
@@ -212,6 +214,9 @@ The hosts in this section are used to install Visual Studio Code packages to est
 | `raw.githubusercontent.com/microsoft/vscode-tools-for-ai/master/azureml_remote_websocket_server/*` | Used to retrieve websocket server bits that are installed on the compute instance. The websocket server is used to transmit requests from Visual Studio Code client (desktop application) to Visual Studio Code server running on the compute instance. |
 | `vscode.download.prss.microsoft.com` | Used for Visual Studio Code download CDN |
 
+### Ports
+You must allow network traffic to ports 8704 to 8710. The VS Code server dynamically selects the first available port within this range.
+
 ## Scenario: Third party firewall or Azure Firewall without service tags
 
 The guidance in this section is generic, as each firewall has its own terminology and specific configurations. If you have questions, check the documentation for the firewall you're using.