Microsoft Teams on Azure Virtual Desktop: Getting Calls and Video Right

By David, 2026-09-14

Microsoft Teams is the app that tells you, within a week, whether an Azure Virtual Desktop (AVD) rollout went well. Chat and files work out of the box. Calls and video are different: set up wrong, every call runs inside the session host, eats its CPU, and sounds like a bad phone line. Set up right, the user's own device does the media work and calls feel local.

This guide covers how to get Teams on Azure Virtual Desktop right in 2026: how media optimization works, the setup checklist for the new Teams app on multi-session hosts, which clients support it, why RDP Shortpath still matters, and how to troubleshoot the usual complaints. It's vendor-neutral until the section on where Atlas AVD helps.

The short version: install new Teams per machine, set the IsWVDEnvironment registry key, install the WebRTC Redirector Service, run FSLogix 2210 hotfix 4 or later, and have users connect with Windows App. Then check that Teams reports AVD SlimCore Media Optimized.

Microsoft changes Teams-on-VDI guidance often. Everything below reflects Microsoft Learn as of October 2026, with links to each source so you can check what has changed since.

How Teams media optimization works on AVD

Without optimization, Teams on a virtual desktop behaves like any other app. The camera and microphone are redirected from the user's device into the session, the session host encodes and decodes every audio and video stream, and the result travels back to the user as part of the remote display. That works, but it's expensive. Video calls are among the heaviest things a multi-session host does, and quality drops as soon as the host or the connection is under load.

Media optimization moves that work to the user's device. Teams still runs on the session host, so chat, files, presence and the meeting window all live in the virtual desktop. But when a call starts, the audio and video are processed on the local device, and the media flows directly between the user's device and Microsoft Teams, not through the session host (Microsoft Learn).

There are two optimization architectures:

SlimCore is Microsoft's newer architecture, and most of the old VDI limitations go away with it (New VDI solution for Teams). It's enabled by default through the Teams VDI policy (the VDI2Optimization setting of CsTeamsVdiPolicy). Microsoft still recommends installing the WebRTC Redirector Service alongside new Teams, so users fall back to WebRTC optimization rather than none when they connect from a device that can't run SlimCore. Teams picks the right stack per connection, so a user who roams from a Windows laptop to an older thin client keeps an optimized call either way.

Optimized Teams keeps the meeting window in the virtual desktop and moves the call itself to the user's device. That's what saves host CPU and makes calls sound local.

Setup checklist: new Teams on multi-session hosts

The classic Teams app is done on VDI. Microsoft's support for classic Teams in VDI environments ended on 1 October 2026, and it reaches end of availability on 1 April 2027 (Microsoft Learn). Everything below is for the new Teams app.

On the image or session host

1. Use a supported OS. Microsoft's AVD guidance covers Windows 10 and 11 Enterprise and Enterprise multi-session. N and KN editions aren't supported. Windows 11 Enterprise multi-session is the usual choice for pooled hosts.
2. Install the prerequisites. The latest Microsoft Visual C++ Redistributable and the WebView2 runtime, which new Teams needs on multi-session Windows (Teams for VDI).
3. Set the media optimization registry key. Under HKLM\SOFTWARE\Microsoft\Teams, create the DWORD IsWVDEnvironment with the value 1.
4. Install the Remote Desktop WebRTC Redirector Service. It's an MSI from Microsoft. Keep it current: Microsoft's minimum for new Teams is version 1.54.2408.19001.
5. Install new Teams per machine. On pooled host pools Teams must be installed per machine, not per user. Microsoft's recommended method is the bootstrapper, teamsbootstrapper.exe -p, which provisions the Teams MSIX for every user on the host. Point it at a downloaded MSIX with -o to save bandwidth on image builds. Add --installTMA to install the Teams Meeting add-in for Outlook machine-wide too.
6. Decide how Teams updates. New Teams updates itself. On a non-persistent image, you can set the DWORD disableAutoUpdate to 1 under HKLM\SOFTWARE\Microsoft\Teams and update Teams with each image instead. If you do, rebuild the image regularly: Teams shows warnings on versions older than 60 days and blocks versions older than 90 days.

Profiles

7. Run FSLogix 2210 hotfix 4 or later. The AVD guidance sets 2210 hotfix 3 as the minimum for new Teams, and the Teams VDI guidance recommends hotfix 4 (2.9.8884.27471), which fixed the "Teams won't start" and missing-icon problems that came from MSIX registration in profile containers. Use the latest release.
8. Exclude only what Microsoft says is safe. For non-persistent hosts, Microsoft lists the Teams logs, the GPU cache and the WebStorage cache as safe to keep out of the profile. Excluding the IndexedDB or the service worker cache makes every Teams launch slower, so test before you do it. Microsoft doesn't recommend excluding anything else.

Delivery

9. Desktop or RemoteApp. Teams works in a full desktop or as a published RemoteApp. To publish new Teams as a RemoteApp, use the path shell:appsFolder\MSTeams_8wekyb3d8bbwe!MSTeams, because the MSIX install folder changes with every update.
10. Don't rely on device redirection for calls. Optimized Teams doesn't need camera and microphone redirection in the host pool's RDP properties. Those settings only matter for the unoptimized fallback.

In the Teams admin center

11. Leave the VDI policy on its defaults unless you have a reason to change them. SlimCore is on by default. If you need to hold a group back, assign them a CsTeamsVdiPolicy with VDI2Optimization set to Disabled.

Client requirements

Media optimization depends on the device the user connects from, not just on the session host. Microsoft's current list (Microsoft Learn):

Three things on the client side catch teams out:

• SlimCore is an MSIX package on the user's device. Windows App's plugin downloads it from Microsoft's CDN and installs it for the user, without admin rights. Group Policy, AppLocker or Intune policies that block non-admin MSIX installs (such as BlockNonAdminUserInstall) stop it. Allow-list the SlimCore package family names, Microsoft.Teams.SlimCoreVdiHost.win-x64_8wekyb3d8bbwe and Microsoft.Teams.SlimCoreVdiFwk.*_8wekyb3d8bbwe, or the device falls back to WebRTC.
• The user's device now makes the media connection. It needs direct UDP access to Microsoft's Teams media ranges on ports 3478 to 3481, the same as a native Teams client. VPNs and packet-inspection proxies on the client side hurt call quality.
• Conditional Access sees the user's device. With SlimCore, Teams authenticates from the endpoint's IP address, not the session host's. Strict location-based policies with Continuous Access Evaluation can cause repeated sign-in prompts for users working from home.

RDP Shortpath: what it is and why it matters for calls

Every AVD connection starts on TCP through the AVD gateway. RDP Shortpath then tries to move the session onto a direct UDP transport between the client and the session host, and drops back to TCP if UDP can't get through (Microsoft Learn). UDP gives lower and steadier latency and better throughput.

There are two flavors:

• Public networks. The client and session host find each other with STUN and connect directly over UDP. If a firewall or symmetric NAT blocks that, they connect through a TURN relay instead. In the Azure commercial cloud this is generally available and works with no extra configuration, as long as UDP isn't blocked.
• Managed networks. Over ExpressRoute or a site-to-site VPN, the client connects straight to a UDP listener on the session host (port 3390 by default). You enable the listener yourself.

Why it matters when calls are already optimized. With optimization on, the call's audio and video don't travel over RDP at all. But everything around the call still does: the meeting window, the content of a screen share, typing into the chat, and every other app in the desktop. A user on a TCP connection with high latency sees a laggy meeting window while the audio sounds fine. And when a user connects from a device that can't optimize, all of the call's audio and video do go through RDP, where Shortpath makes the difference between usable and not.

Check what you're getting. In Windows App, the connection information panel shows whether the session is using UDP. Across the estate, AVD Insights reports the transport and round-trip time for each connection. To give Shortpath a fair chance:

• Allow outbound UDP from the session host subnet. In Azure commercial, that includes UDP 3478 to the TURN relay range 51.5.0.0/16.
• Avoid forced tunneling, double NAT, TCP-based VPNs and cloud packet inspection on the path.
• Pick a region close to your users. Shortpath shortens the path; it can't remove the distance. Wrong region selection is one of the top 10 AVD mistakes.

Troubleshooting: no video, echo and "not optimized"

Start every investigation in the same place. In Teams, select Settings and more (...), then Settings, then About Teams, and read the banner. Newer Teams builds also show a VDI status indicator at the top left; hover over Optimized to see which stack is in use.

"Not optimized" or "AVD Media not connected"

• Confirm IsWVDEnvironment is set on the host, and that Teams was installed per machine.
• Confirm the WebRTC Redirector Service is installed and running, and up to date.
• Check the client: Windows App, or a supported platform, at a supported version. Browsers never optimize.
• If the user had Teams open when they reconnected from a different device, have them quit and restart Teams. Users can also choose Optimize virtual desktop and restart from the status indicator's menu.
• If it should be SlimCore but shows WebRTC, look at the user's device: an MSIX install block, an outdated Windows App, or the Mac App Store client.

No video, or other people's video and screen shares are black

• Check camera permissions on the user's device. Windows privacy settings must let apps use the camera and microphone, and on macOS Windows App needs camera access in System Settings.
• If the device list in Teams shows Remote audio rather than the user's real devices, optimization didn't load. Restart Teams, then work through the list above.
• Microsoft lists a known issue where users on WebRTC optimization can't see incoming video or screen shares on Windows 11 24H2 or 25H2 hosts with User Account Control disabled. The workaround is to turn UAC back on.
• Teams optimization doesn't work in a "double hop", where a user opens a second remote desktop from inside the first.

Echo and poor audio

• Echo usually means two audio paths. Make sure only one device is active in the Teams device settings, and that users aren't joining the same meeting from their phone or local Teams as well.
• Robotic or choppy audio in an optimized call is a network problem on the user's side, because the media runs from their device. Check their UDP access to the Teams media ranges, and any VPN in the path.
• Choppy audio in an unoptimized call points at the session host or the RDP transport. Check host CPU at the time of the call and whether the session was on UDP or TCP.

Teams won't start, or the icon is missing

• Update FSLogix to 2210 hotfix 4 or later. Most of the "Teams installed but won't launch" reports trace back to MSIX registration with older profile container versions.
• Make sure Teams is up to date. Versions older than 90 days are blocked.
• If you disabled auto-update on a non-persistent image, Teams only gets newer when the image does.

Where Atlas AVD helps

Most of the checklist above is the same few steps on every session host, and the risk is the host that missed one. Atlas AVD handles the host-side steps for you and helps you check the network side. Here's exactly what it does, and what it leaves to you.

Teams settings on every host Atlas builds. In a host pool's settings, under Compute & Deployment → Deployment Behavior, two switches cover the host-side Teams steps:

• WebRTC Redirector Service downloads Microsoft's current Remote Desktop WebRTC Redirector Service and installs it while the session host is provisioned.
• Optimize Teams sets the IsWVDEnvironment registry key, so Teams knows it's on AVD and offloads calls.

Both are on by default. They inherit from your global and tenant defaults, which you set once in the setup wizard's VM Defaults step, and any host pool can override them. They apply whenever Atlas builds a session host: when you add hosts, and when you re-image or replace them, including a Rolling Replace (Zero Downtime) onto a new image. Changing the switch doesn't reach into hosts that are already running, so roll the pool onto fresh hosts after you change it.

Teams itself goes in your image. Atlas doesn't install the Teams app. Install new Teams per machine with the bootstrapper on your golden image, then capture it from Imaging into an Azure Compute Gallery version, and every host built from it has Teams. The prerequisites are easier: the Application Catalog installs any WinGet package per host pool at deploy time, such as the Visual C++ Redistributable or the WebView2 runtime. The WinGet integration post shows how that works.

FSLogix from the current release. When Atlas installs FSLogix on a host or bakes it into an image, it installs Microsoft's current release rather than a pinned old build, so the hotfix 4 requirement takes care of itself. Atlas doesn't add Teams cache exclusions to the profile, so add Microsoft's recommended ones yourself if you want them.

See whether sessions are on UDP. Atlas doesn't change your RDP Shortpath configuration, but it shows you whether Shortpath is working. With AVD Insights connected, the Network Transport card on the Analytics Experience tab shows UDP adoption across your sessions, adoption by host pool, and recent sessions that fell back to TCP. The Connection Quality dashboard widget breaks round-trip time into good, fair and poor, so you can see whether a user's "Teams is bad" ticket is really a network problem.

Hear about changes before users do. The Atlas Feed tracks Microsoft's release notes for Microsoft Teams and the WebRTC Redirector Service, alongside the other products your session hosts run.

What Atlas doesn't do: it doesn't read the Teams status banner on each session. Your pilot still needs someone to open About Teams on a few real devices and see AVD SlimCore Media Optimized.

New to AVD? Start with What Is Azure Virtual Desktop? for how the pieces fit together, and App delivery on AVD for where Teams and your other apps should live. Moving from VMware Horizon? Teams is one of the migration traps to plan for.

FAQ

Does Microsoft Teams work on Azure Virtual Desktop?

Yes. Chat and collaboration work on every client. Calls and meetings are optimized, with the audio and video processed on the user's device, when users connect with Windows App on Windows, macOS, iOS, iPadOS or Android, or from a supported Linux thin client.

What is SlimCore in Teams for AVD?

SlimCore is the media engine behind Microsoft's newer Teams VDI optimization. Windows App downloads it to the user's device, where it handles the call's audio and video. It supports more Teams features than the older WebRTC-based optimization, including 1080p video, larger gallery views and QoS.

Do I still need the WebRTC Redirector Service with new Teams?

Microsoft recommends installing it. SlimCore doesn't need it, but it lets users fall back to WebRTC optimization when they connect from a device that can't run SlimCore, such as an iPad, an Android device or a Linux thin client.

Can I still use classic Teams on AVD?

Not with support. Classic Teams in VDI environments reached end of support on 1 October 2026 and reaches end of availability on 1 April 2027. Move to the new Teams app.

Does Teams work in a web browser session to AVD?

Teams runs, but calls and meetings aren't optimized in a browser session. Audio and video are processed on the session host, so call quality depends on the host and the connection. Use Windows App for anyone who joins calls from their virtual desktop.

Do I need RDP Shortpath for Teams?

It isn't required, but it helps. Optimized call media doesn't travel over RDP, but the meeting window, screen-share content and the rest of the desktop do, and unoptimized calls send everything over RDP. Shortpath for public networks works automatically in Azure commercial as long as UDP isn't blocked.

How do I check whether Teams is optimized?

In Teams, open Settings and more (...), then Settings, then About Teams. The banner shows AVD SlimCore Media Optimized, AVD Media Optimized or AVD Media not connected.

Should Teams be installed per user or per machine on AVD?

Per machine on pooled host pools. Microsoft's recommended method is teamsbootstrapper.exe -p, which provisions new Teams for every user on the host.

Microsoft product details in this article are taken from Microsoft Learn as of October 2026: Use Microsoft Teams on Azure Virtual Desktop, Teams for VDI, New VDI solution for Teams and RDP Shortpath. Teams-on-VDI guidance changes often, so check those pages before you change production.