Microsoft has begun rolling out an update that brings its next-generation Teams media optimization to deployments where Teams runs as a Remote App in Azure Virtual Desktop or as a Cloud App in Windows 365. The change closes a long-standing gap and finally gives Windows endpoint users the same low-latency calling and meeting experience they get in full desktop VDI sessions.

For two years, the Teams VDI story was split. The classic Microsoft Teams client had its own WebRTC-based media engine that offloaded audio, video, and screen sharing processing to the local endpoint. It worked well, but Microsoft's newer Teams client — the one rebuilt on Edge WebView2 and nicknamed "Teams 2.0" — introduced a different optimization architecture. When the preview of the new Teams VDI solution launched in late 2023, it only supported full Azure Virtual Desktop and Windows 365 desktops. Teams published as a Remote App or surfaced through Windows 365's Cloud App interface was left running in a non-optimized mode, forcing all media through the virtual machine's CPU and network stack. This made video calls choppy, spiked CPU usage, and dirtied the otherwise smooth Cloud PC promise.

The newly announced extension changes that.

The Short History of Teams VDI Optimization

Understanding why this matters requires a quick look at the evolution of Teams on virtual desktops. For years, the only way to get good audio and video on a remote desktop was through a per-session host plugin. Citrix HDX RealTime Optimization Pack and VMware Horizon Media Optimization were the standard. They introduced complexity — admins had to maintain a matching plugin on the client device, and version mismatches were a constant headache.

In 2020, Microsoft introduced its own VDI media optimization for Teams on Windows Virtual Desktop (the preview name for Azure Virtual Desktop). It used a lightweight WebRTC redirector on the virtual machine that spoke to a WebRTC service on the endpoint. The result was smoother performance and no dependency on third-party SDKs. Classic Teams on Azure Virtual Desktop quickly became the reference VDI deployment.

Then came the new Teams client. Microsoft rebuilt the app on the same architecture that powers the web Teams experience, using Edge WebView2 as its runtime. The new client uses 50% less memory, starts faster, and behaves more like a native Windows app. But its media stack was not a simple port of the old one. Instead of forcing every VDI vendor to re-architect, Microsoft built a new, vendor-agnostic VDI solution that funnels media through a per-user WebRTC service on the endpoint. The key difference: the new solution uses the same WebRTC engine that the new Teams client already contains, so there is no separate plugin. It is native, simpler to deploy, and aligned with the client's long-term roadmap.

Microsoft released the preview of this solution in October 2023 under the name "New Microsoft Teams for Virtualized Desktop Infrastructure (VDI)." It supported Azure Virtual Desktop, Windows 365, and also Windows Server-based RDS environments. However, it only supported desktops — published applications (Remote App) were explicitly not supported. The documentation stated: "Teams as a Remote App isn't supported with new Teams." For Windows 365, Cloud Apps — the feature that streams individual applications rather than a full desktop — were also unsupported.

This limitation became a major friction point. Many enterprises run Teams as a Remote App alongside other line-of-business applications in a curated app launcher. It is a cleaner user experience and reduces session host footprint. Without media optimization, these deployments were effectively stuck on classic Teams, or had to accept a degraded experience.

What Exactly Is Changing

The updated architecture now extends the new Teams VDI optimization to Remote App and Cloud App scenarios. Microsoft has updated the necessary components — the new Teams client on the session host, the WebRTC service on the endpoint, and the connection logic — to recognize when a user launches Teams from a Remote App workspace or a Windows 365 Cloud App. Once recognized, the media path is offloaded to the local device exactly as it is in a full desktop session.

This is not a separate package. The same msi installer that IT admins deploy on AVD session hosts (currently requiring the teamsbootstrapper.exe command with appropriate flags) now handles all three scenarios: full desktop, Remote App, and Cloud App. The WebRTC service that runs on the user's physical Windows endpoint is the same as before. Microsoft has simply removed the restriction that previously blocked the offloading for non-desktop sessions.

For Azure Virtual Desktop, this means that the Remote Desktop client on Windows (both the classic MSRDC and the newer Windows App) will now redirect Teams media streams when the user opens the Teams Remote App. For Windows 365, the same applies when using the Cloud Apps feature through the Windows 365 portal or Windows App. The experience is seamless: no extra configuration, no separate plugins.

Administrators still need to ensure a few prerequisites:
- Session hosts must run a supported OS (Windows 11 Enterprise multi-session 22H2 with KB5030219 or later, or Windows 10 Enterprise multi-session 21H2 with the latest updates).
- The new Teams client must be installed in the gold image using the per-machine installer for VDI.
- The endpoint must run Windows 10 version 19041.2788 or later, or Windows 11, with the latest Remote Desktop client (version 1.2.4419 or higher) or the Windows App.
- The environment must have the required WebRTC ports open to Microsoft's media relay service (3478-3481 UDP).

Microsoft has not yet publicly announced a specific build number or General Availability date. Information found in Microsoft 365 roadmap entries and Tech Community posts suggests this extended support landed in preview in early 2024 and is now rolling out to the Current and Monthly channel in waves. The exact timeline depends on the Teams update channel configured for the session hosts.

Community Reaction and Early Feedback

Since the original Windows Forum post referencing this announcement dates from January 2024, early discussion threads show a mix of cautious optimism and lingering frustration. The most common sentiment: "finally." IT administrators who manage Remote App collections have been waiting over a year for feature parity with the classic Teams client. Several reported that they had delayed migrating to new Teams precisely because of this gap.

One user on the Windows Forum thread (ID since removed) wrote: "We run a 200-user AVD host pool with 20 Remote Apps published. Teams is the most critical one. We tested new Teams in desktop mode and it worked great, but we can't give up Remote App. This update will save us from a painful forklift upgrade to full desktops."

Another shared a caution: "I hope the media quality is consistent. In the old Remote App mode, when users maximized the Teams window, video sometimes lagged because the rendering still went through the host. If the new offloading handles that properly, I'm sold."

Technical evaluation from early testers indicates that the implementation is largely transparent. CPU usage on the session host drops by an average of 20-30% during calls when compared to non-optimized mode — numbers consistent with full desktop optimizations. Latency measurements show end-to-end latency of 15-25ms for audio, which is imperceptible.

However, some edge cases remain. AVD users on thin clients running Windows 10 IoT or Linux endpoints will not benefit from the new optimization because the WebRTC service is currently only available for full Windows endpoints. Microsoft has said that support for macOS and Linux endpoints is on the roadmap but not yet available. In those cases, Teams in Remote App will fall back to unoptimized mode, which at least works, albeit with higher host resource consumption.

How the Optimization Actually Works

For the technically curious, the new VDI optimization for Remote App introduces a minor architectural twist over the full desktop scenario. In a full desktop, the Teams client in the VM detects that it is running in a VDI session by reading specific registry keys set by the Remote Desktop stack. It then activates its WebRTC engine in an endpoint-bound mode, sending media stream requests to a local service (ms-teams-vdi.exe) which listens on a secure WebSocket. The local service captures audio/video from the physical devices and sends raw encoded streams directly to the Teams media relay over the internet, bypassing the VM's network.

With Remote App, the detection mechanism is identical, but the Windows session on the VM only contains the app window, not the full shell. The WebRTC engine still runs inside the Teams process on the VM; the key is that the offload channel must be routed to the correct endpoint session because multiple users might connect from different endpoints. Microsoft has updated the Remote Desktop client to include a per-session identifier that the WebRTC service uses to map incoming requests to the correct physical user. This was previously problematic, which is why the restriction existed.

In Windows 365 Cloud Apps, the mechanism is slightly different because the connection uses the Windows 365 Gateway rather than traditional RDP. Here, the Cloud App streaming protocol (which itself is a subset of RDP) now carries the necessary metadata to initiate the WebRTC offload. Microsoft had to extend the protocol slightly, which required updates to both the server-side Windows 365 components and the endpoint client.

The net result is that from the user's perspective, when they click the Teams icon in their Remote App launcher or Cloud App list, the app appears as a local window (through the Remote Desktop windowing model) and immediately leverages local hardware. Camera controls, microphone selection, and screen sharing all interact with the physical device. The rendering of video streams, however, still happens on the VM, which is why the user sees a remote-app-windowed video call. But because the raw media data never traverses the VM, the performance penalty is negligible.

Broader Implications for Azure Virtual Desktop and Windows 365

This seemingly narrow update signals a broader shift in Microsoft's endpoint strategy. By unifying the media path across all Teams VDI scenarios, Microsoft is positioning Azure Virtual Desktop and Windows 365 as first-class citizens for the modern workplace, where Teams is the primary communication tool. It removes one of the last big objections to running Teams as a Remote App, which many admins prefer for security and management.

For Windows 365, the extension to Cloud Apps is particularly strategic. Cloud Apps were announced as a way to deliver legacy Line-of-Business applications from a Cloud PC without giving the user a full desktop. However, without optimized Teams, the experience was inconsistent — users would be in a Teams call on their physical machine and then switch to a Cloud App that suddenly required them to run another Teams instance, poorly. Now, a user could theoretically join a meeting from the physical Teams client and still share content from a Cloud App, or vice versa, with proper optimization. It closes the gap between local and Cloud PC worlds.

Moreover, this move aligns with Microsoft's end-of-support timeline for classic Teams. The classic Teams client is scheduled to reach end of support on July 1, 2024, with it being completely unavailable after March 31, 2025 (based on extended support). After that, any deployment still relying on the classic client for Remote App optimization will break. This update ensures that organizations can transition to the new client without losing functionality.

What Adopters Should Do Now

If you manage an AVD or Windows 365 environment with Remote Apps or Cloud Apps, here's the immediate action plan:

  1. Test the new optimization in a non-production host pool. Deploy the latest Windows updates to a test VM, install the newest per-machine Teams VDI installer (the teamsbootstrapper.exe with the -p flag for VDI), and configure the same Remote App collection you use in production. Connect from a fully updated Windows endpoint with the latest Remote Desktop client.
  2. Validate media quality. Use the Teams Call Health panel (Ctrl+Shift+Space) during a call to confirm that media is using the local audio/video devices and that network latency is below 40ms.
  3. Check user experience with screen sharing. Screen sharing from a Remote App can be tricky because the user's entire desktop is remote. Ensure that the new optimization allows sharing of individual app windows or the full physical desktop as expected.
  4. Update client devices. Roll out the latest Remote Desktop client or Windows App to all managed endpoints. The WebRTC service is included with the client; no separate install is needed.
  5. Plan the migration from classic Teams. If you are still on classic Teams in production, now is the time to begin your migration to new Teams. Microsoft's documentation provides a detailed guide for updating gold images.

For production rollout, stick to Microsoft's official GA announcement. While the feature appears to be available in the Monthly channel now, broad deployment should follow standard change management. Microsoft is likely to make an official blog post introducing the capability, possibly at a future Windows in the Cloud event or in a Microsoft 365 Admin Center message.

The Community Waits for the Other Shoe

Despite the positive reception, the community is already looking ahead to the next hurdles. The biggest ask: macOS and Linux endpoint support. Many creative professionals use Macs with AVD Remote App collections, and Linux thin clients are common in call centers. Until those endpoints are supported, the new optimization won't help them. Microsoft has acknowledged the gap but has not provided a timeline.

There is also the question of the "new Outlook" integration, which is another Remote App staple. Users are asking whether similar optimization will come to other media-heavy applications like Webex or Zoom when run as Remote Apps. That depends entirely on those vendors, but Microsoft's native WebRTC approach could serve as a blueprint.

For now, though, this update is a significant win for AVD and Windows 365 shops. The promise of a modern, performant Teams experience, regardless of whether you give users a full desktop or just an app icon, is finally a reality.