Merge pull request #201933 from Heidilohr/work-teams-macosga

Updates for Teams for Azure Virtual Desktop macOS GA.

Author: PRMerger6

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

@@ -3,24 +3,20 @@ title: 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: 06/23/2022
+ms.date: 06/27/2022
 ms.author: helohr
 manager: femila
 ---
 # Use Microsoft Teams on Azure Virtual Desktop
 
 >[!IMPORTANT]
->Media optimization for Teams is supported for Microsoft 365 Government (GCC) and GCC-High environments. Media optimization for Teams is not supported for Microsoft 365 DoD.
+>Media optimization for Teams is supported for Microsoft 365 Government (GCC) and GCC-High environments. Media optimization for Teams isn't supported for Microsoft 365 DoD.
 
 >[!NOTE]
 >Media optimization for Microsoft Teams is only available for the following two clients:
 >
 >- Windows Desktop client for Windows 10 or 11 machines, version 1.2.1026.0 or later.
->- macOS Remote Desktop client, version 10.7.7 or later (preview)
-
-> [!IMPORTANT]
-> Teams for macOS is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+>- macOS Remote Desktop client, version 10.7.7 or later.
 
 Microsoft Teams on Azure Virtual Desktop supports chat and collaboration. With media optimizations, it also supports calling and meeting functionality. To learn more about how to use Microsoft Teams in Virtual Desktop Infrastructure (VDI) environments, see [Teams for Virtualized Desktop Infrastructure](/microsoftteams/teams-for-vdi/).
 
@@ -31,7 +27,7 @@ With media optimization for Microsoft Teams, the Remote Desktop client handles a
 Before you can use Microsoft Teams on Azure Virtual Desktop, you'll need to do these things:
 
 - [Prepare your network](/microsoftteams/prepare-network/) for Microsoft Teams.
-- Install the [Remote Desktop client](./user-documentation/connect-windows-7-10.md) on a Windows 10 or Windows 10 IoT Enterprise device that meets the Microsoft Teams [hardware requirements for Teams](/microsoftteams/hardware-requirements-for-the-teams-app#hardware-requirements-for-teams-on-a-windows-pc/).
+- Install the [Remote Desktop client](./user-documentation/connect-windows-7-10.md) on a Windows 10, Windows 10 IoT Enterprise, Windows 11, or macOS 10.14 or later device that meets the [hardware requirements for Microsoft Teams](/microsoftteams/hardware-requirements-for-the-teams-app#hardware-requirements-for-teams-on-a-windows-pc/).
 - Connect to a Windows 10 or 11 Multi-session or Windows 10 or 11 Enterprise virtual machine (VM).
 
 ## Install the Teams desktop app
@@ -123,7 +119,7 @@ You can deploy the Teams desktop app using a per-machine or per-user installatio
 
         This installs Teams to the Program Files (x86) folder on a 32-bit operating system and to the Program Files folder on a 64-bit operating system. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups.
 
-        There are two flags that may be set when installing teams, **ALLUSER=1** and **ALLUSERS=1**. It is important to understand the difference between these parameters. The **ALLUSER=1** parameter is used only in VDI environments to specify a per-machine installation. The **ALLUSERS=1** parameter can be used in non-VDI and VDI environments. When you set this parameter, **Teams Machine-Wide Installer** appears in Program and Features in Control Panel as well as Apps & features in Windows Settings. All users with admin credentials on the machine can uninstall Teams.
+        There are two flags that may be set when installing teams, **ALLUSER=1** and **ALLUSERS=1**. It's important to understand the difference between these parameters. The **ALLUSER=1** parameter is used only in VDI environments to specify a per-machine installation. The **ALLUSERS=1** parameter can be used in non-VDI and VDI environments. When you set this parameter, **Teams Machine-Wide Installer** appears in Program and Features in Control Panel as well as Apps & features in Windows Settings. All users with admin credentials on the machine can uninstall Teams.
 
         > [!NOTE]
         > Users and admins can't disable automatic launch for Teams during sign-in at this time.
@@ -158,7 +154,7 @@ After installing the WebSocket Service and the Teams desktop app, follow these s
 
       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 do not load, uninstall then reinstall Teams and check again.
+      If optimizations don't load, uninstall then reinstall Teams and check again.
 
 ## Known issues and limitations
 
@@ -168,20 +164,20 @@ Using Teams in a virtualized environment is different from using Teams in a non-
 
 - With per-machine installation, Teams on VDI isn't automatically updated the same way non-VDI Teams clients are. To update the client, you'll need to update the VM image by installing a new MSI.
 - Media optimization for Teams is only supported for the Remote Desktop client on machines running Windows 10 or later or macOS 10.14 or later.
-- Use of explicit HTTP proxies defined on the client endpoint device is not supported.
+- Use of explicit HTTP proxies defined on the client endpoint device isn't supported.
 
 ### Calls and meetings
 
 - The Teams desktop client in Azure Virtual Desktop environments doesn't support creating live events, but you can join live events. For now, we recommend you create live events from the [Teams web client](https://teams.microsoft.com) in your remote session instead. When watching a live event in the browser, [enable multimedia redirection (MMR) for Teams live events](multimedia-redirection.md#how-to-use-mmr-for-teams-live-events) for smoother playback.
 - Calls or meetings don't currently support application sharing. Desktop sessions support desktop sharing.
 - Due to WebRTC limitations, incoming and outgoing video stream resolution is limited to 720p.
 - The Teams app doesn't support HID buttons or LED controls with other devices.
-- New Meeting Experience (NME) is not currently supported in VDI environments.
+- New Meeting Experience (NME) isn't currently supported in VDI environments.
 - Teams for Azure Virtual Desktop doesn't currently support uploading custom background images.
 
 For Teams known issues that aren't related to virtualized environments, see [Support Teams in your organization](/microsoftteams/known-issues).
 
-### Known issues for Teams for macOS (preview)
+### Known issues for Teams for macOS
 
 - You can't configure audio devices from the Teams app, and the client will automatically use the default client audio device. To switch audio devices, you'll need to configure your settings from the client audio preferences instead.
 - Teams for Azure Virtual Desktop on macOS doesn't currently support background effects such as background blur and background images.
@@ -201,7 +197,7 @@ To contact Microsoft Teams support, go to the [Microsoft 365 admin center](/micr
 
 Customizing a host pool's Remote Desktop Protocol (RDP) properties, such as multi-monitor experience or enabling microphone and audio redirection, lets you deliver an optimal experience for your users based on their needs.
 
-Enabling device redirections is not required when using Teams with media optimization. If you are using Teams without media optimization, set the following RDP properties to enable microphone and camera redirection:
+Enabling device redirections isn't required when using Teams with media optimization. If you're using Teams without media optimization, set the following RDP properties to enable microphone and camera redirection:
 
 - `audiocapturemode:i:1` enables audio capture from the local device and redirects audio applications in the remote session.
 - `audiomode:i:0` plays audio on the local computer.