Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into view-csp-res

Author: bandersmsft

articles/aks/use-node-taints.md

@@ -250,6 +250,7 @@ This article assumes you have an existing AKS cluster. If you need an AKS cluste
     az aks nodepool update \
     --cluster-name $CLUSTER_NAME \
     --name $NODE_POOL_NAME \
+    --resource-group $RESOURCE_GROUP_NAME \
     --node-taints "sku=gpu:NoSchedule"
     ```
 
@@ -260,6 +261,7 @@ This article assumes you have an existing AKS cluster. If you need an AKS cluste
     ```azurecli-interactive
     az aks nodepool update \
     --cluster-name $CLUSTER_NAME \
+    --resource-group $RESOURCE_GROUP_NAME \
     --name $NODE_POOL_NAME \
     --node-taints ""
     ```
@@ -295,7 +297,7 @@ When you remove all initialization taint occurrences from node pool replicas, th
     az aks update \
     --resource-group $RESOURCE_GROUP_NAME \
     --name $CLUSTER_NAME \
-    --node-init-taints "sku=gpu:NoSchedule"
+    --node-init-taints ""
     ```
 
 ## Check that the taint has been removed from the node

articles/azure-monitor/agents/azure-monitor-agent-migration.md

@@ -19,10 +19,10 @@ Migration is a complex task. Start planning your migration to Azure Monitor Agen
 
 > [!IMPORTANT]
 > The Log Analytics agent will be [retired on **August 31, 2024**](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). You can expect the following when you use the MMA or OMS agent after this date.
-> - **Data upload:** Cloud ingestion services will gradually reduce support for MMA agents, which may result in decreased support and potential compatibility issues for MMA agents over time.  Ingestion for MMA will be unchanged until Febuary 1 2025.
-> - **Installation:** The ability to install the legacy agents will be removed from the Azure Portal and installation policies for legacy agents will be removed. You can still install the MMA agents extension as well as perfrom offline installations.
+> - **Data upload:** Cloud ingestion services will gradually reduce support for MMA agents, which may result in decreased support and potential compatibility issues for MMA agents over time.  Ingestion for MMA will be unchanged until February 1 2025.
+> - **Installation:** The ability to install the legacy agents will be removed from the Azure Portal and installation policies for legacy agents will be removed. You can still install the MMA agents extension as well as perform offline installations.
 > - **Customer Support:** You will not be able to get support for legacy agent issues.
-> - **OS Support:** Support for new Linux or Windows distros, incluing service packs won't be added after the deprecation of the legacy agents.
+> - **OS Support:** Support for new Linux or Windows distros, including service packs, won't be added after the deprecation of the legacy agents.
 
 ## Before you begin
 

articles/machine-learning/how-to-connect-models-serverless.md

@@ -179,7 +179,7 @@ Follow these steps to create a connection:
     # [Python SDK](#tab/python)
 
     ```python
-    client.connections.create(ServerlessConnection(
+    client.connections.create_or_update(ServerlessConnection(
         name="meta-llama3-8b-connection",
         endpoint="https://meta-llama3-8b-qwerty-serverless.inference.ai.azure.com",
         api_key="1234567890qwertyuiop"
@@ -209,4 +209,4 @@ Follow these steps to create a connection:
 ## Related content
 
 - [Model Catalog and Collections](concept-model-catalog.md)
-- [Deploy models as serverless API endpoints](how-to-deploy-models-serverless.md)
+- [Deploy models as serverless API endpoints](how-to-deploy-models-serverless.md)

articles/operator-nexus/howto-install-cli-extensions.md

@@ -6,7 +6,7 @@ ms.author: travisneely
 ms.service: azure-operator-nexus
 ms.custom: devx-track-azurecli
 ms.topic: include
-ms.date: 02/08/2024
+ms.date: 06/28/2024
 # ms.custom: template-include
 ---
 
@@ -74,15 +74,15 @@ Example output:
 ```output
 Name                     Version
 -----------------------  -------------
-monitor-control-service  0.2.0
+monitor-control-service  0.4.1
 connectedmachine         0.7.0
-connectedk8s             1.6.5
+connectedk8s             1.7.3
 k8s-extension            1.4.3
 networkcloud             1.1.0
-k8s-configuration        1.7.0
-managednetworkfabric     4.2.0
+k8s-configuration        2.0.0
+managednetworkfabric     6.2.0
 customlocation           0.1.3
-ssh                      2.0.2
+ssh                      2.0.4
 ```
 
 <!-- LINKS - External -->

articles/virtual-desktop/teams-on-avd.md

@@ -3,29 +3,40 @@ title: Use Microsoft Teams on Azure Virtual Desktop - Azure
 description: How to use Microsoft Teams on Azure Virtual Desktop.
 author: Heidilohr
 ms.topic: how-to
-ms.date: 12/06/2023
+ms.date: 06/27/2024
 ms.author: helohr
 ---
 # Use Microsoft Teams on Azure Virtual Desktop
 
-Microsoft Teams on Azure Virtual Desktop supports chat and collaboration. With media optimizations, it also supports calling and meeting functionality by redirecting it to the local device when using a supported Remote Desktop client. You can still use Microsoft Teams on Azure Virtual Desktop with other clients without optimized calling and meetings. Teams chat and collaboration features are supported on all platforms.
+Microsoft Teams on Azure Virtual Desktop supports chat and collaboration. With media optimizations, it also supports calling and meeting functionality by redirecting it to the local device when using Windows App or the Remote Desktop client on a supported platform. You can still use Microsoft Teams on Azure Virtual Desktop with other clients without optimized calling and meetings. Teams chat and collaboration features are supported on all platforms.
+
+There are two versions of Teams, *Classic Teams* and *[New Teams](/microsoftteams/new-teams-desktop-admin)*, and you can use either with Azure Virtual Desktop. New Teams has with feature parity with Classic Teams, but improves performance, reliability, and security.
+
+To redirect calling and meeting functionality to the local device, Azure Virtual Desktop uses an extra component. This component is either *SlimCore* or the *WebRTC Redirector Service*. The option you use depends on the following:
+
+- New Teams can use either SlimCore or the WebRTC Redirector Service. SlimCore is available in preview and you need [to opt in to the preview](/microsoftteams/public-preview-doc-updates?tabs=new-teams-client) to use it. If you use SlimCore, you should also install the WebRTC Redirector Service. This allows a user to fall back to WebRTC, such as if they roam between different devices that don't support the new optimization architecture. For more information about SlimCore and how to opt into the preview, see [New VDI solution for Teams](/microsoftteams/vdi-2).
+
+- Classic Teams uses the WebRTC Redirector Service.
 
 > [!TIP]
-> The new Microsoft Teams app is now generally available to use with Azure Virtual Desktop, with feature parity with the classic Teams app and improved performance, reliability, and security.
->
 > If you're using the [classic Teams app with Virtual Desktop Infrastructure (VDI) environments](/microsoftteams/teams-for-vdi), such as as Azure Virtual Desktop, end of support is **October 1, 2024** and end of availability is **July 1, 2025**, after which you'll need to use the new Microsoft Teams app. For more information, see [End of availability for classic Teams app](/microsoftteams/teams-classic-client-end-of-availability).
 
 ## Prerequisites
 
-Before you can use Microsoft Teams on Azure Virtual Desktop, you'll need to do these things:
+Before you can use Microsoft Teams on Azure Virtual Desktop, you need:
 
 - [Prepare your network](/microsoftteams/prepare-network/) for Microsoft Teams.
 
 - Connect to a session host running Windows 10 or 11 multi-session or Windows 10 or 11 Enterprise. Session hosts running an N or KN SKU of Windows aren't supported.
 
 - For Windows, you also need to install the latest version of the [Microsoft Visual C++ Redistributable](https://support.microsoft.com/help/2977003/the-latest-supported-visual-c-downloads) on your client device and session hosts. The C++ Redistributable is required to use media optimization for Teams on Azure Virtual Desktop.
 
-- Install the latest [Remote Desktop client](./users/connect-windows.md) on a client device running Windows 10, Windows 10 IoT Enterprise, Windows 11, or macOS 10.14 or later that meets the [hardware requirements for Microsoft Teams](/microsoftteams/hardware-requirements-for-the-teams-app#hardware-requirements-for-teams-on-a-windows-pc/).
+- Install the latest version of [Windows App](/windows-app/get-started-connect-devices-desktops-apps) or the [Remote Desktop client](./users/connect-windows.md) on Windows or macOS that meets the [hardware requirements for Microsoft Teams](/microsoftteams/hardware-requirements-for-the-teams-app#hardware-requirements-for-teams-on-a-windows-pc/).
+
+   SlimCore is available on Windows with the following apps and versions:
+   
+   - Windows App for Windows, version 1.3.252 or later
+   - Remote Desktop client for Windows, version 1.2.5405.0 or later
 
 - If you use FSLogix for profile management and want to use the new Microsoft Teams app, you need to install FSLogix 2210 hotfix 3 (2.9.8716.30241) or later.
 
@@ -41,11 +52,11 @@ For more information about which features Teams on Azure Virtual Desktop support
 
 ## Prepare to install the Teams desktop app
 
-This section will show you how to install the Teams desktop app on your Windows 10 or 11 Enterprise multi-session or Windows 10 or 11 Enterprise VM image.
+This section shows you how to install the Teams desktop app on your Windows 10 or 11 Enterprise multi-session or Windows 10 or 11 Enterprise VM image.
 
 ### Enable media optimization for Teams
 
-To enable media optimization for Teams, set the following registry key on the host VM:
+To enable media optimization for Teams, set the following registry key on each session host:
 
 1. From the start menu, run **Registry Editor** as an administrator. Go to `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams`. Create the Teams key if it doesn't already exist. 
 
@@ -64,7 +75,9 @@ New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Teams" -Name IsWVDEnvironment -
 
 ### Install the Remote Desktop WebRTC Redirector Service
 
-The Remote Desktop WebRTC Redirector Service is required to run Teams on Azure Virtual Desktop. To install the service:
+You need to install the WebRTC Redirector Service on each session host. You can install the [MSI file](https://aka.ms/msrdcwebrtcsvc/msi) using a management tool such [Configuration Manager](/mem/configmgr/apps/get-started/create-and-deploy-an-application), or manually. 
+
+To install the WebRTC Redirector Service manually:
 
 1. Sign in to a session host as a local administrator.
 
@@ -76,9 +89,12 @@ The Remote Desktop WebRTC Redirector Service is required to run Teams on Azure V
 
 You can find more information about the latest version of the WebRTC Redirector Service at [What's new in the Remote Desktop WebRTC Redirector Service](whats-new-webrtc.md).
 
+> [!TIP]
+> If you want to use SlimCore, all of its required components come bundled with new Teams and Windows App or the Remote Desktop client.
+
 ## Install Teams on session hosts
 
-You can deploy the Teams desktop app per-machine or per-user. For session hosts in a pooled host pool, you'll need to install Teams per-machine. To install Teams on your session hosts follow the steps in the relevant article:
+You can deploy the Teams desktop app per-machine or per-user. For session hosts in a pooled host pool, you need to install Teams per-machine. To install Teams on your session hosts follow the steps in the relevant article:
 
 - [Install the classic Teams app](/microsoftteams/teams-for-vdi#deploy-the-teams-desktop-app-to-the-vm).
 - [Install the new Teams app](/microsoftteams/new-teams-vdi-requirements-deploy).
@@ -87,27 +103,29 @@ You can deploy the Teams desktop app per-machine or per-user. For session hosts
 
 After installing the WebRTC Redirector Service and the Teams desktop app, follow these steps to verify that Teams media optimizations loaded:
 
+1. Connect to a remote session.
+
 1. Quit and restart the Teams application.
 
 1. Select your user profile image, then select **About**.
 
 1. Select **Version**.
 
-      If media optimizations loaded, the banner will show you **Azure Virtual Desktop Media optimized**. If the banner shows you **Azure Virtual Desktop Media not connected**, quit the Teams app and try again.
+      If media optimizations loaded, the banner shows you  **AVD SlimCore Media Optimized** or **AVD Media Optimized**. If the banner shows you **AVD Media not connected**, quit the Teams app and try again.
 
 1. Select your user profile image, then select **Settings**.
 
-      If media optimizations loaded, the audio devices and cameras available locally will be enumerated in the device menu. If the menu shows **Remote audio**, quit the Teams app and try again. If the devices still don't appear in the menu, check the Privacy settings on your local PC. Ensure the under **Settings** > **Privacy** > **App permissions - Microphone** the setting **"Allow apps to access your microphone"** is toggled **On**. Disconnect from the remote session, then reconnect and check the audio and video devices again. To join calls and meetings with video, you must also grant permission for apps to access your camera.
+   If media optimizations loaded, the audio devices and cameras available locally will be enumerated in the device menu. If the menu shows **Remote audio**, quit the Teams app and try again. If the devices still don't appear in the menu, check the Privacy settings on your local PC. Ensure the under **Settings** > **Privacy** > **App permissions - Microphone** the setting **"Allow apps to access your microphone"** is toggled **On**. Disconnect from the remote session, then reconnect and check the audio and video devices again. To join calls and meetings with video, you must also grant permission for apps to access your camera.
 
-      If optimizations don't load, uninstall then reinstall Teams and check again.
+   If media optimizations don't load, uninstall then reinstall Teams and check again.
 
 ## Enable registry keys for optional features
 
-If you want to use certain optional features for Teams on Azure Virtual Desktop, you'll need to enable certain registry keys. The following instructions only apply to Windows client devices and session host VMs.
+If you want to use certain optional features for Teams on Azure Virtual Desktop, you need to enable certain registry keys. The following instructions only apply to Windows client devices and session host VMs.
 
 ### Enable hardware encode for Teams on Azure Virtual Desktop
 
-Hardware encode lets you increase video quality for the outgoing camera during Teams calls. In order to enable this feature, your client will need to be running version 1.2.3213 or later of the [Windows Desktop client](whats-new-client-windows.md). You'll need to repeat the following instructions for every client device. 
+Hardware encode lets you increase video quality for the outgoing camera during Teams calls. In order to enable this feature, your client needs to be running version 1.2.3213 or later of the [Windows Desktop client](whats-new-client-windows.md). You need to repeat the following instructions for every client device. 
 
 To enable hardware encode: