Install Teams for Virtualized Desktop Infrastructure (VDI)

This article describes the requirements and limitations of using the Microsoft Teams client in a virtualized environment.

Requirements

For the Teams client to be successfully installed, you need version 23306.3314.2555.9628 or higher. In addition, virtual machines must meet the minimum requirements listed here:

Virtualization provider requirements

Currently, Teams on VDI with audio/video (AV) optimization is certified with Azure Virtual Desktops, Windows 365, Citrix, Omnissa and Amazon. Review the information in this article to ensure that you meet all requirements for proper functionality.

For RDS scenarios, please refer to this section.

Azure Virtual Desktop

Azure Virtual Desktop provides AV optimization for Teams on VDI. To learn more on requirements and installation, see Use Teams on Azure Virtual Desktop.

The following minimum versions are necessary to support the Teams client:

• Remote Desktop Client for Windows 1.2.5405

• Windows app for Windows 2.0.360.0

• Remote Desktop Client for Mac 10.9.7

• Windows app for Mac 11.1.4 (2557)

• Windows app for iOS 11.1.7 (5679) [In public preview for WebRTC based optimization only]

• Windows app for Android (11.0.0.40) [In public preview for WebRTC based optimization only]

• Web browsers don't support Microsoft Teams optimization

• Linux Thin Clients - only Partners listed on this page support Microsoft Teams optimization (WebRTC based)

• WebRTC Redirector Service 1.54.2408.19001

Microsoft recommends using the latest available versions.

In addition, you must deploy the following registry key on the virtual desktop for the Teams client to be optimized:

HKLM\SOFTWARE\Microsoft\Teams:

• Name: IsWVDEnvironment
• Type: DWORD
• Value: 1

RemoteApp

You can publish Teams using the Windows shell:appsFolder location in the format: shell:appsFolder\MSTeams_8wekyb3d8bbwe!MSTeams.

For more information on RemoteApp, see this article.

Windows 365

Windows 365 uses the same Audio/Video optimization provided by Azure Virtual Desktop to ensure optimal Teams experiences from Cloud PCs. To learn more on requirements and installation, see Use Teams on Cloud PC.

The Windows 10/11 images in the gallery are preconfigured with required optimization components. When you install and use Microsoft Teams in your Cloud PC, you get an optimized experience.

If you want to create custom images that include optimizations for Microsoft Teams, you need to perform the steps described in Create a custom Cloud PC image to support Microsoft Teams.

The same minimum versions as in Azure Virtual Desktops are necessary to support the Teams client on Windows 365. See section above.

In addition, you must deploy the following registry key on the virtual desktop for the Teams client to be optimized:

HKLM\SOFTWARE\Microsoft\Teams:

• Name: IsWVDEnvironment
• Type: DWORD
• Value: 1

Citrix Virtual Apps and Desktops and Citrix DaaS requirements

The following minimum versions are necessary to support the Teams client:

Citrix Workspace app:

• Windows 2402 LTSR (and any CU)
• Windows 2405 CR
• Linux 2408
• Mac 2405
• HTML5 2404.1
• ChromeOS - latest Citrix Workspace app for ChromeOS published in Chrome Web Store. The previous (N minus 1) version is supported on the compatible ChromeOS version and maintained until the next release.

Citrix Virtual Delivery Agent (VDA):

• 2507 LTSR (and any CU)
• 2402 LTSR (and any CU)
• 2203 LTSR (and any CU)
• 2407 CR
• 1912 LTSR is not supported

In addition, you must deploy the following registry key on the VDA for the Teams client to be optimized:

• Location:  HKLM\SOFTWARE\WOW6432Node\Citrix\WebSocketService
• Key (REG_Multi_SZ): ProcessWhitelist
• Value: msedgewebview2.exe

If this registry key is missing, the Teams client operates in nonoptimized mode (server-side rendering). This regkey isn't needed anymore if you're using VDA 2402 (check here for more details).

For additional information, learn more at Optimization for Microsoft Teams.

Omnissa Horizon and Workspace ONE requirements

The following minimum versions are necessary to support the Teams client:

• Horizon 8 2111 ESB (8.4)

To learn more about the latest requirements and instructions, including how to configure media optimization for Teams, see Microsoft Teams Optimization with Horizon | Omnissa.

Amazon WorkSpaces requirements

Please refer to the new VDI optimization page (SlimCore-based) for more details. AppStream is not supported.

Deploy the Microsoft Teams client

To deploy the Microsoft Teams client to your organization, select one of the following options.

Install the Teams client

Recommended way to deploy Teams in VDI. The direct or 'bulk deployment' method is used for this option. Learn more at Bulk deploy the Microsoft Teams desktop client.

Using the teamsbootstrapper.exe -p command always guarantees the latest Teams client is installed.

A phased and controlled rollout can then be achieved by selectively expanding the new computer catalogue/delivery group assignments to more users.

Admins can also use a local teams MSIX to provision Teams. This option minimizes the amount of bandwidth used for the initial installation. The MSIX can exist in a local path or UNC.

1. Download the .exe installer.

2. Download the MSIX:
   - MSIX x86
   - MSIX x64
   - ARM64.

3. Open the Command Prompt as an Admin.

4. Depending on where your MSIX is located, do the following steps:

   For local path, enter: .\teamsbootstrapper.exe -p -o "c:\path\to\teams.msix"

   Example:

   

   For UNC, enter: .\teamsbootstrapper.exe -p -o "\unc\path\to\teams.msix"

   Example:

   

If IT administrators set restrictions for MSIX or deploy GPOs, it could prevent users from downloading and installing the app. If restrictions are in place, the user could see errors like this one:

Teams installers in VDI environments

You should have an awareness of the install location for the Teams client.

Troubleshooting Teams deployment errors

Administrators can rely on the teamsbootstrapper.exe error code that describes the problem. If the error code doesn't provide enough information, more diagnostic information can be found in the detailed event logs.

1. Go the Event Viewer (Local) > Applications and Services Logs > Microsoft > Windows.

2. Check for available logs under these categories:

   • AppxPackagingOM > Microsoft-Windows-AppxPackaging/Operational
   • AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational

3. Review logs under AppXDeployment-Server.

   Learn more here: Common error codes

   Teamsbootstrapper.exe common error codes	Further information
   0x80070057	The bootstrapper command doesn't have the full path (avoid URIs using .). Try the full path instead (for example, c:\temp\MSTeams-x64.msix).
   0x80070032	A probable error on the UNC path. Try copying the MSIX to a local folder instead.
   0x80004004	There might be a regkey 'maglevInstallationSource' left behind in regkey HKLM\Software\WoW6432Node\Microsoft\Office\Teams. Try deleting it and reattempting the install.

Installation instructions for Windows Server 2019

For Windows Server 2019, the only supported installation method is:

Dism /Online /Add-ProvisionedAppxPackage /PackagePath:<MSIX package path> /SkipLicense

Make sure sideloading is enabled, and that WebView2 is installed. See the Requirements section.

The /SkipLicense command is needed because the MSIX package isn't considered a "Store Package" (since it wasn't downloaded from the store). Therefore, for the Dism installation command to succeed, you need to enable this policy as well during installation time: Computer Configuration > Administrative Templates > Windows Components > App Package Deployment > Allow all trusted apps to install.

Known limitations:

• If you're using FSLogix as the Profile Manager solution, Teams on Windows Server 2019 needs FSLogix 2210 HotFix 4 or higher (Microsoft recommends the latest available version).

Outlook presence integration with Teams in Windows Server 2019

For Outlook to properly display presence status, the following steps are required on the golden image:

1. Install machine-wide (ALLUSERS=1) the 'Windows 10 1809 and Windows Server 2019 KB5035849 240209_02051 Feature Preview.msi'.

2. Open your Group Policy Editor. Navigate to Computer Configuration\Administrative Templates\KB5035849 240209_02051 Feature Preview\Windows 10, version 1809 and Windows Server 2019. Change the value of that Setting to Enabled.

3. Install KB5035849 March 2024 cumulative update from the Microsoft Update Catalog or WSUS for Enterprises.

4. Install machine-wide (ALLUSERS=1) the 'MSTeamsNativeUtility.msi'.

5. Reboot the virtual machine.

6. Install Teams 24033.811.2738.2546 or higher, using Dism as described previously.

   Note

   Steps 1, 2, 3, 4, and 5 are only required once. These steps aren't required in subsequent golden image maintenance.

   Important

   Outlook must be started after Teams is launched for presence to be shown correctly.

Remove Teams for all users

To uninstall and deprovision Teams for all users, use the following command:

./teamsbootstrapper -x

This command unregisters and deprovisions Teams for all users. Teams user profile/cache is deleted.

Disable Teams autoupdate in non-persistent VDI

To prevent Teams from autoupdating, use the following registry key on the virtual machine. Only Teams builds higher than 23306.3314.2555.9628 in VDI can process this registry key.

Location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams
Name: disableAutoUpdate
Type: DWORD
Value: 1

Teams autostart

Three components control the autostart behavior of Teams:

1. By default, MSIX-based applications don't autostart until there's a first launch, because the Windows OS doesn't autostart packages in a provisioned state. An AppX registration is needed with user consent. After the first launch, users can go to Settings > General and fill the Autostart Teams checkbox, or enable autostart from the Windows Setting menu.

2. If the "Autostart Teams" checkbox is greyed out, it means a system-wide GPO is disabling this option for UWP apps:

   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] 
   "EnableFullTrustStartupTasks"=dword:00000000
   "EnableUwpStartupTasks"=dword:00000000
   "SupportFullTrustStartupTasks"=dword:00000000
   "SupportUwpStartupTasks"=dword:00000000
   

   This registry setting causes the option to be unavailable in the operating systems under Settings > Apps > Installed Apps. In order to change this setting, create the regkeys with the values as shown in this example:

   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
   "EnableFullTrustStartupTasks"=dword:00000002
   "EnableUwpStartupTasks"=dword:00000002
   "SupportFullTrustStartupTasks"=dword:00000001
   "SupportUwpStartupTasks"=dword:00000001
   

   Restart the virtual machine to see the startup options active in the operative system's settings menu.

3. This registry key controls the Teams autostart behavior, so you can enable or disable it programmatically.

   [HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\MSTeams_8wekyb3d8bbwe\TeamsTfwStartupTask]
   "State"=dword:00000002
   "UserEnabledStartupOnce"=dword:00000001
   

   State	Number	Information
   Disabled	0	The task is disabled.
   DisabledByUser	1	The user disabled the task. Only the user can re-enable the task.
   EnabledByUser	2	The task is enabled.
   DisabledByPolicy	3	The administrator or group policy disabled the task. Platforms that don't support startup tasks also report DisabledByPolicy.
   EnabledByPolicy	4	The administrator or group policy enabled the task.

   You can learn more at this link.

Profile and cache location for the Teams Client

All the user settings and configurations are now stored in:

• C:\Users<username>\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\
• C:\Users<username>\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\Settings\settings.dat
• C:\Users<username>\AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\app_switcher_settings.json
• C:\Users<username>\AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\tma_settings.json

Make sure these folders and files are persisted for proper Teams functioning.

The folder "meeting-addin" under TeamsSharedConfig shouldn't be persisted, as persisting could cause issues with the default meeting coordinates in the meeting templates inserted into Outlook.

Folder exclusions

Disk storage usage

To make it easier to distribute our client to Windows devices, support is added for MSIX, which improves the dependability of installations and app updates, as well as reduces network bandwidth and disk space consumption. This packaging technology also shows the accurate disk space usage.

Disk Footprint - Key folders and location

• App installer: C:\Program Files\WindowsApps\MSTeams_[version]_[arch]__8wekyb3d8bbwe Includes the installation package, supports the ability to reset the app, and allows single instancing.
• User and app data: C:\Users<alias>\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe Includes code (JavaScript bundles), code cache, browser caches, databases for user data (like conversations, which scale based on usage), and web storage (from domains hosted within Teams, such as Sharepoint, Viva Learning, Apps, and so on).

For non-persistent setups where storage footprint is a consideration, the following guidance applies:

Recommended for exclusion

Review tradeoff considerations, requiring evaluation and testing for these environments

Other than the folders in this section, we don't recommend excluding additional directories.

Teams and Outlook integration

The selection of the "Register the new Teams as the chat app for Microsoft 365" checkbox under Settings > General > System lets the Teams client integrate with all the Microsoft 365 apps that have instant message capabilities (presence, chat, VOIP, and so on).

For example, Outlook goes through the discovery process outlined here to integrate with the default IM client application: Integrating IM applications with Office

Teams Meeting add-in

Additionally, the Teams MSIX package bundles the Teams Meeting add-in (or TMA) MSI ("MicrosoftTeamsMeetingAddinInstaller.msi"). TMA lets you schedule a Teams meeting from Outlook.

For Security articles related to TMA integration with the Outlook client, learn more at Teams meeting add-in security when using your Outlook client.

All Teams files installed on the computer are signed, so IT admins can use AppLocker/Code Integrity/Windows Defender Application Guard policies configured to for enforcement.

• For Teams per-user installations of TMA, the install folder is in AppData\Local\Microsoft\TeamsMeetingAdd-in
• Installation logs for TMA MSI are stored here: AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs \tma_addin_msi.txt

This error is caused by GPOs affecting Windows Installer, and includes DisableUserInstalls, DisableMSI, or AppLocker policies based on Publisher rule conditions, or a RuleCollection for MSI installs. In this case, you must create an exception such as:

• FilePathCondition Path="%PROGRAMFILES%\WINDOWSAPPS*\MICROSOFTTEAMSMEETINGADDININSTALLER.MSI"

Deployment method for non-persistent environments where Teams autoupdate is disabled

If Administrators don't want to use the new --installTMA flag, they can still install the TMA MSI located in the Teams installation directory from an Admin Command prompt using:

msiexec.exe /i "C:\Program Files\WindowsApps\MSTeams_X.X.X.X_x64__8wekyb3d8bbwe\MicrosoftTeamsMeetingAddinInstaller.msi" ALLUSERS=1 /qn /norestart TARGETDIR="C:\Program Files (x86)\Microsoft\TeamsMeetingAdd-in\<version>\"

• TARGETDIR must be kept consistent across installs so that the Teams Meeting Add-in MSI can detect and clean up older versions. If multiple directories are used, then the installation may not behave as expected.

• X.X.X.X needs to be replaced by the Teams version. Make sure there's a double underscore between the CPU architecture (x64) and the PublisherID (8wekyb3d8bbwe). The exact version number can be extracted by running this command in PowerShell:

  
  Get-AppXPackage -Name "*msteams*" | Select-Object -ExpandProperty Version
  
  

• version must be replaced with the MSI file version, for example, 1.24.2203.0. The exact version number can be extracted by running this command in PowerShell:

PS C:\WINDOWS\system32> Get-AppLockerFileInformation -Path "C:\PROGRAM FILES\WINDOWSAPPS\MSTEAMS_24026.1000.2656.1710_X64__8WEKYB3D8BBWE\MICROSOFTTEAMSMEETINGADDININSTALLER.MSI" | Select -ExpandProperty Publisher | select BinaryVersion

BinaryVersion

1.24.2203.0

Example: The following are examples of the final command:

msiexec.exe /i "C:\Program Files\WindowsApps\MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe\MicrosoftTeamsMeetingAddinInstaller.msi" ALLUSERS=1 /qn /norestart TARGETDIR="C:\Program Files (x86)\Microsoft\TeamsMeetingAdd-in\1.24.2203.0\"

The following PowerShell script can be used as a reference for deployment. Customers should validate in their QA/TEST environments:

If (-not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] 'Administrator') ){
    Write-Error "Need to run as administrator. Exiting.."
    exit 1
}

# Get Version of currently installed Teams Package
if (-not ($NewTeamsPackageVersion = (Get-AppxPackage -Name MSTeams).Version)) {
    Write-Host "Teams Package not found. Please install Teams from https://aka.ms/GetTeams ."
    exit 1
}
Write-Host "Found Teams Version: $NewTeamsPackageVersion"

# Get Teams Meeting Addin Version
$TMAPath = "{0}\WINDOWSAPPS\MSTEAMS_{1}_X64__8WEKYB3D8BBWE\MICROSOFTTEAMSMEETINGADDININSTALLER.MSI" -f $env:programfiles,$NewTeamsPackageVersion
if (-not ($TMAVersion = (Get-AppLockerFileInformation -Path $TMAPath | Select-Object -ExpandProperty Publisher).BinaryVersion))
{
    Write-Host "Teams Meeting Addin not found in $TMAPath."
    exit 1
}
Write-Host "Found Teams Meeting Addin Version: $TMAVersion"

# Install parameters
$TargetDir = "{0}\Microsoft\TeamsMeetingAdd-in\{1}\" -f ${env:ProgramFiles(x86)},$TMAVersion
$params = '/i "{0}" TARGETDIR="{1}" /qn ALLUSERS=1' -f $TMAPath, $TargetDir

# Start the install process
write-host "executing msiexec.exe $params"
Start-Process msiexec.exe -ArgumentList $params
write-host "Please confirm install result in Windows Eventlog"

After installation, restart Outlook and verify TMA is loading. Logs are located on %localappdata%\Temp\Microsoft\Teams\meeting-addin.

For Teams Meeting add-in troubleshooting articles, learn more at: Resolve issues with Teams Meeting add-in for Outlook.

Troubleshooting Teams and Outlook integration

Symptoms

You see any of the following issues when you check the presence status for a user in Outlook:

• The presence indicator isn't visible.
• The displayed presence is incorrect.
• The presence status is Status unknown.

Troubleshooting steps

1. Make sure Teams is running. Then launch Outlook.

2. Check the registry settings on your computer to verify that Teams is registered as the default instant messaging (IM) app.

   1. Start Registry Editor.
   2. Locate the following subkey: HKEY_CURRENT_USER\Software\IM Providers
   3. Verify the following values:

    - **Name:** DefaultIMApp
    - **Type:** REG_SZ
    - **Data:** MsTeams
    ```
   
   

3. Locate the following subkey:

   • HKEY_CURRENT_USER\Software\IM Providers\MsTeams (Outlook monitors this registry key for value changes)

4. Verify the following values:

   -Name: UpAndRunning -Type: REG_DWORD -Data: 2 (0—Not running, 1—Starting, 2—Running)

5. If the issues persist, contact Microsoft Support.

Control fallback mode in Teams

When users connect from an unsupported endpoint, the users are in fallback mode, in which Audio/Video isn't optimized. You can disable or enable fallback mode by setting one of the following registry DWORD values:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams\DisableFallback HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Teams\DisableFallback

• This registry key can only be processed by Teams 24257.x.x.x or higher.
• To disable fallback mode, set the value to 1.
• To enable audio only, set the value to 2.
• If the value isn't present or is set to 0 (zero), fallback mode is enabled.
• On Fallback, screen sharing functionality is supported with a different screen picker UI (similar to the experience a user would see on Teams for Web).

Multitenant and Multi-account in VDI

Teams in VDI allows you to sign in quickly and easily, and allowing you to switch between multiple accounts and organizations from the same Microsoft 365 cloud environment.

If any of your accounts have guest access to other organizations, you don’t need to add them--they appear automatically. A guest is someone from outside an organization that a team owner invites to join the team, such as a partner or consultant. Guests have fewer capabilities than team members or team owners.

Learn more: Manage accounts and organizations in Microsoft Teams

Features currently not available and known issues in VDI with Teams

• In some scenarios, Citrix RemotePC users might experience a Teams crash and restart loop when using VDA 2411 and accessing Teams locally (not via HDX). Check CTX585013 for more details.
• Teams doesn't on-demand register during FSLogix profile creation (even with HotFix 4), and doesn't register during future sign-ins, despite being installed. A race condition between Process Lifetime Manager (PLM) service and AppxSvc causes this issue. causing a transient failure when updating the package with error 0x80004001 (E_NOTIMPL). If the PLM service isn't running, Teams registration fails.
  • (In MSIX, Registration occurs on a per-user basis and begins when a user logs on. The OS then loads the preinstalled packaged app, creating user-specific app data, FTAs, and app tiles in the Start menu. This action is done by the AppReadiness Service, which is aware of all preinstalled apps and requests the Appx Deployment Service (AppxSvc) deploy those packages.)
  • Customers hitting this error, even with FSLogix Hotfix 4, must deploy these fixes:
    • Windows 11 21H2 KB5043067
    • Windows Server 2022 KB5042881
    • Windows Server 2019 KB5043050
  • This bug is addressed with KB5037849 for Windows 10 (May 2024). The issue isn't present on Windows 11 22H2 or higher.
• Teams fails to launch for users logging into single-user non-persistent Windows 10 virtual desktops, or the app isn't visible in the Start menu. But the app might become visible and launches successfully 15 minutes after logging in.
  • This issue is addressed in KB5041582/KB5041587 for Windows 10/11, and Teams 24215.1007.3082.1590 (or higher) - both components are needed.
  • You might also need to exclude the following location from your roaming profile solution (for FSLogix customers, as an example, via redirections.xml): AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState.
  • NOTE - The issue isn't seen in multi-user Windows 10 or 11. For Windows 2019. A fix to resolve this issue is available: KB5044227.
• Customers installing Teams on a golden image, which later undergoes a sysprep to generalize it, are failing to launch the app. This circumstance includes templates from Azure Image Gallery.
  • Users logging in to the provisioned virtual machines see the Teams icon greyed out in the start menu and clicking on it has no effect.
  • The AppX log in the Event Viewer has the error 0x80073CF1.
  • Running Get-AppxPackage -name MsTeams -allusers from an elevated PowerShell window shows that PackageUserInformation is in a Paused state for SID S-1-15-18 (LocalSystem). This error isn't seen on W11 22H2 or higher. Install KB5039299 for Windows 10 KB5040437 for WS2022, and KB5040431 for W11 21H2.
• Screen sharing from chat for Azure Virtual Desktops/Windows 365 (This issue is now fixed on RD Client 1.2.5105 and Redirector Service 1.50.2402.29001).
• Screen sharing from chat for Citrix when using Workspace app 2311 only.
• msteams_autostart.exe "The parameter is incorrect": In non-persistent environments that use FSLogix (any version before 2210 HotFix 4) or Citrix Profile Manager profile containers, when Teams attempts to autostart or a user tries to launch Teams from the Start menu, it throws the error: "The parameter is incorrect." The frequency and reproducibility of the error varies depending on the environment and especially the antivirus software being used (SentinelOne, Palo Alto, Trend Micro, Bitdefender, CrowdStrike, and so on.) and exclusions in place. This issue is now fixed on FSLogix 2210 HotFix 4. Customers facing this issue with Citrix Profile Manager are must upgrade to CPM 2402 or 2203 CU5.
  • "The parameter is incorrect" error can be caused by other file system drivers. Running fltmc from an elevated command window lists the drivers. Two Citrix drivers (UPMAction and upmjit) can cause the error, even if you're only using FSLogix HotFix 4 and don't have Citrix Profile Manager. This error happens because Citrix VDA installers typically install profilemgt_x64.msi by default for Citrix Director monitoring of logon time counters. Removing that MSI can fix "the parameter is incorrect" error.
• Teams fails to launch for users logging into non-persistent virtual desktops, or the app is not visible in the Start menu.
  • Admins don't experience this issue - after installing Teams on the golden image they can launch it successfully.
  • After you seal the golden image and deploying it at scale (with provisioning tools like Citrix MCS/PVS or Omnissa Instant-Clones), users log in to the virtual machines and click on the Teams icon, but aren't able to launch the app. The issue is caused by a failed registration of the MSIX package at the user level with different profile management software (FSLogix before 2210 HotFix 4, Citrix CPM 2308 or 2311 but not on 2402, Ivanti UEM, and so on), even though the staging of the package was successful (the OS stored the package’s contents on the disk in the %ProgramFiles%\WindowsApps directory). This issue can be confirmed by running Get-AppxPackage -name MsTeams for the affected users. Running this code returns an empty output.
  • If Get-AppxPackage -name MsTeams -allusers is run from an elevated PowerShell command window, the output shows that Teams is registered (see line PackageFullName) and the Status is OK.
  • This issue is fixed in FSLogix 2210 HotFix 4.
• When you use Azure Virtual Desktops or Windows 365, and the MAC Remote Desktop Client or Windows app, Microsoft Teams UI doesn't enumerate all the peripherals connected to the device. Instead, only the device selected at the macOS-level is shown in the Devices' drop-down menu of Microsoft Teams. The peripheral is labeled. "MAC device name" + "Speakers" is an example of this labeling.
• Teams meetings can't be launched when selecting a link from Outlook. There's an authentication prompt (Access to '{tenant}' tenant is denied) when users attempt to join an external meeting. This issue is fixed in Teams 24091.214.2846.1452.
• The PowerShell window shows after Teams is provisioned. If the virtual machine's OS has the right fixes (see Deploy the new Microsoft Teams client, the second bullet in the Notes section), then admins can delete this registry key and the PowerShell window doesn't show anymore:

Location: "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run"
Name: TeamsProvisionRunKey

The teamsbootstrapper.exe version 1.0.2407104 added this regkey as a workaround for environments lacking those fixes.

Enhancements in Teams

Teams for web in VDI

Teams for Web isn't supported in VDI environments, so performance and reliability may be negatively impacted if used in VDI.

Features not supported in VDI

The following features aren't supported in Teams when using the WebRTC-based optimization. Most of these limitations are addressed with the new SlimCore-based optimization. Check out the Feature list with the new optimization section of our VDI 2.0 article for more information.

• QoS.

• 1080p.

• Custom Backgrounds uploaded by users.

• Teams Premium features (End to End Encryption, Watermark, Premium Events aren't optimized, Custom meeting backgrounds for organizations).

• Avatars.

• Gallery View 3x3 and 7x7.

• Noise Suppression (except for Azure Virtual Desktop/W365, where noise suppression is on by default, but confirmation isn't shown in Teams client UI. This behavior is by design).

• Zoom In / Out.

• Location Based Routing.

• Media Bypass.

• HID (Citrix only).

• Share System Audio (Omnissa only).

• Broadcast and live event producer and presenter roles.

• Cross cloud in Government Clouds (GCC, GCC High, and DoD) and Sovereign Clouds operated by 21Vianet

• Record video clip doesn't capture screen share.

• The call monitor (the small floating window after you minimize the main Teams window) doesn't display video or screen share.

• Teams calls drop on a local machine that has an HID peripheral connected if a user launches a virtual desktop from that local machine and logs into Teams (Azure Virtual Desktop/W365 and Omnissa with both WebRTC and SlimCore, Citrix with SlimCore only).

• Organizers and presenters can't join town halls.