Problem statement
When users access video playback and WebRTC calling apps through a web browser (Edge/Chrome) in AVD, Multimedia Redirection may or may not successfully redirect the media to the local device. Today, administrators have no centralized way to see which sessions/sites are being optimized (redirected) versus falling back to server-side rendering. The only visibility is per-session and manual — the browser extension icon per tab, or a user-reported "not optimized" state — which does not scale for enterprise support teams.
Requested enhancement
Provide native, admin-facing visibility into MMR optimization status, ideally exposing:
- Per-user / per-session redirection state (redirected vs. not redirected / server-side fallback)
- The site or media element being redirected, and the reason redirection failed where applicable
- Video playback redirection and WebRTC call redirection status separately
- Queryable data via Azure Monitor / Log Analytics (Insights workbook) and an exportable report/API
Business value
- Let's support teams proactively identify optimization failures before users raise tickets
- Reduces troubleshooting effort (no per-machine log collection or Process Explorer DLL checks)
- Enables capacity/cost validation, since un-redirected media consumes session host CPU
Current workaround Manual per-session checks via the browser extension icon / Teams banner, and per-VM log collection — not viable at enterprise scale.
Example use case A large enterprise AVD deployment supporting browser-based collaboration and video needs to confirm, across thousands of sessions, whether MMR is functioning per user — without touching each endpoint.