If your organization delivers Microsoft Teams through Windows 365 CloudApps or Azure Virtual Desktop RemoteApps, this week’s announcement directly changes what’s architecturally possible — and what’s no longer a reasonable excuse for a poor experience.
SlimCore-based Teams optimization for RemoteApps and CloudApps in the Windows App is now generally available. This closes the gap that has existed since the early days of per-application remoting: Teams delivered as a RemoteApp or CloudApp can now receive the same media engine treatment as Teams in a full desktop session.
For IT decision-makers evaluating Cloud PC architecture, this is worth understanding carefully.
What Changed
Until this week’s announcement, Slimcore-based Teams optimization — Microsoft’s modern media engine for virtual desktops — was available only when Teams ran inside a full desktop session (a complete Windows 365 Cloud PC desktop or an Azure Virtual Desktop desktop pool).
When Teams was published as a RemoteApp (an individual application streamed from an Azure Virtual Desktop host pool) or a CloudApp (an application published from a Windows 365 Cloud PC without exposing the full desktop), the optimization story was significantly weaker. Admins faced a choice between accepting degraded Teams performance or routing users back to a full desktop session just for Teams.
That constraint is now lifted. The announcement from the Week of May 25, 2026 What’s New page:
SlimCore-based Teams optimization is now supported for RemoteApps and CloudApps in the Windows App. This update enables Teams features beyond desktop sessions, with SlimCore-based optimization for improved performance. Support is limited to Windows App; non-Windows clients are not included.
Generally available. Production-supported. No preview caveats.
Why SlimCore Matters
Microsoft Teams in virtual environments has always been a media performance challenge. In a traditional (non-optimized) remote desktop deployment, every audio and video frame — every pixel of your camera feed, every millisecond of your voice — is processed inside the remote session in the data center, compressed, and streamed to your endpoint. For real-time collaboration, that extra round-trip shows up as latency, choppy video, and degraded call quality.
Media optimization inverts that model. With SlimCore optimization, the Teams user interface runs inside the Cloud PC or remote session, but the actual audio and video processing happens on the local endpoint. Media flows directly between endpoints and Microsoft’s Teams relay infrastructure — not through the data center. The result is call quality comparable to running Teams natively, with the management benefits of centralized delivery.
Microsoft describes SlimCore as “the most up to date mode with the broadest set of features” for Teams in virtual desktop environments, replacing the older “AVD media optimization” model. SlimCore aligns the virtual desktop Teams experience more closely with the modern Teams client architecture — the same media engine, with the same feature surface.
The practical significance: this is not a workaround. SlimCore is the strategic, long-term model for Teams in Cloud PC environments.
What RemoteApps and CloudApps Enable
RemoteApps (Azure Virtual Desktop) and CloudApps (Windows 365) are per-application delivery mechanisms — a user connects to a specific application that appears as if it’s running on their local device, without exposing the underlying Windows desktop.
For shift workers, contractors, or employees with narrow application sets, this model is often preferable to a full Cloud PC desktop. It reduces attack surface, simplifies the user experience, and in some cases lowers costs — a CloudApp delivery model doesn’t require the same level of Cloud PC SKU that a full desktop experience demands.
The problem has always been Teams. Organizations that wanted to deliver Teams as a CloudApp or RemoteApp were essentially publishing an application that would deliver suboptimal call quality — undermining one of the core productivity reasons for remote work in the first place. The common workaround was either:
- Full desktop session requirement: Force users into a full Cloud PC desktop just to get a good Teams experience
- Local Teams install: Have users run Teams natively on the endpoint, separate from the managed CloudApp environment
- Accept degraded quality: Publish Teams as a RemoteApp and live with the complaints
None of these are great answers. The first defeats the purpose of per-app delivery. The second creates a management and security split. The third means a poor user experience.
GA SlimCore for RemoteApp and CloudApp removes this architectural compromise.
What Organizations Should Do
If you currently deliver Teams as a CloudApp or RemoteApp: Update your Windows App client deployments to ensure users are on a current version that supports SlimCore optimization. Verify that the SlimCore mode is active for Teams sessions (the Teams VDI diagnostic overlay should report “SlimCore” as the optimization mode, not “Legacy AVD” or “Not Optimized”).
If you forced users into full desktop sessions for Teams quality reasons: Reassess whether a CloudApp delivery model now meets your needs. For users who primarily need Teams plus a narrow set of other applications, the CloudApp pattern may now deliver the experience that previously required a full desktop.
If you’re designing a new Windows 365 or AVD deployment: Model Teams delivery into your architecture from day one using SlimCore CloudApps or RemoteApps for appropriate user segments, rather than defaulting all users to full desktop sessions.
Operational checklist:
- Confirm Windows App is current across endpoints (SlimCore requires a sufficiently recent Windows App version)
- Verify Teams is deployed correctly on the Cloud PC or session host (Microsoft-distributed Teams package, not arbitrary MSI installs that may break optimization)
- Test call quality using Teams real-time analytics before rolling out to production users
- Review firewall and network rules — SlimCore media optimization relies on direct media paths to Microsoft’s relay infrastructure; existing Teams network configuration rules apply
- Communicate to users: the Teams experience in CloudApp/RemoteApp has improved; encourage them to update and test
What Has NOT Changed
Non-Windows clients are excluded. The SlimCore optimization for RemoteApp and CloudApp is limited to the Windows App on Windows endpoints. Users connecting from macOS, iOS, Android, or Linux will not receive the same optimization. This is consistent with the historical pattern — most advanced Windows App features ship on Windows first, with other platforms following over time.
Full desktop sessions are unchanged. Existing Cloud PC desktop deployments with SlimCore already enabled continue to work exactly as before. This GA adds RemoteApp/CloudApp coverage; it does not alter the full desktop optimization path.
Licensing is unchanged. No new licensing tiers or add-ons are required for SlimCore RemoteApp/CloudApp optimization. It’s a client and server-side capability update, not a commercial change.
The Teams application itself is unchanged. Teams version management on Cloud PCs — using the Microsoft-distributed optimization-compatible client — remains the same. If you already had SlimCore working in full desktop mode, the Teams application version requirements for RemoteApp/CloudApp are consistent.
The Bigger Picture: Teams as a Cloud-Delivered Application
Microsoft’s trajectory is clear: the Windows App is intended to be the authoritative, optimized front end for all cloud-hosted Windows and application delivery scenarios. Each GA announcement — SlimCore for full desktops, SlimCore for RemoteApps, the recent Azure Compute Gallery custom image GA, Admin Insights, Cloud PC Monitoring — is filling in the capability map that makes Windows 365 and AVD viable replacements for on-premises VDI.
The per-application delivery model specifically is worth watching. Organizations that have historically thought of Windows 365 as “a Cloud PC for everyone” may find that a hybrid architecture — full Cloud PCs for power users, CloudApps for task workers — becomes more attractive as the CloudApp experience reaches parity with local application delivery.
Teams reaching SlimCore GA for RemoteApps is a prerequisite for that architecture to be credible. A collaboration platform that can’t deliver high-quality video calls through a per-app model isn’t a full Cloud PC replacement — it’s a partial one. That partial nature is now resolved.
The Citrix DaaS documentation also references Microsoft SlimCore optimization alongside classic Teams optimization support, signaling that SlimCore is a Microsoft-defined protocol being adopted across the VDI ecosystem — not just a Windows-App-specific capability. The ecosystem convergence around SlimCore as the standard makes it a safe long-term investment for enterprise Teams optimization strategy.
Ready to Optimize Your Windows 365 Environment?
Big Hat Group helps organizations design, deploy, and manage Windows 365 environments — from architecture through day-to-day operations. Whether you’re evaluating CloudApp delivery for task workers, optimizing Teams performance in your Cloud PC environment, or planning a migration from on-premises VDI, we bring hands-on expertise to every engagement.
Contact Big Hat Group to discuss your Windows 365 strategy.
Looking for more Windows 365 coverage? Read about the Azure Compute Gallery custom images GA, the Frontline to Flex rebrand and Admin Insights, and the Autopilot and RDP Multipath updates.
Big Hat Group is a Microsoft partner specializing in modern endpoint management, Windows 365, and Microsoft 365 deployments. This post is part of our ongoing Windows 365 coverage.