AVD Clients: Choose and Deploy
Users connect to Azure Virtual Desktop through client applications. The new Windows App is replacing legacy clients and works on every platform. Learn how to choose, deploy, and troubleshoot AVD clients across Windows, macOS, iOS, Android, and web browsers.
How users connect to AVD
Think of AVD clients as remote controls for your cloud desktop.
Your desktop runs in Azure, but you need something on your device to see it and interact with it — like a TV remote control. The Windows App is Microsoft’s latest universal remote. It works on your laptop, phone, tablet, or even just a web browser. You open it, sign in, and your cloud desktop appears on your screen.
Client options — what is available
| Client | Platforms | Key Features | Status |
|---|---|---|---|
| Windows App | Windows, macOS, iOS, Android | Unified client, multi-monitor, device redirection, RDP Shortpath | Current — recommended |
| Web client | Any modern browser | No install needed, works anywhere | Current — always available |
| Remote Desktop client (MSRDC) | Windows, macOS | Legacy client, full feature set | Being replaced by Windows App |
| Remote Desktop app (Store) | Windows | Store version of legacy client | Deprecated — use Windows App |
Windows App — the recommended client
Windows App is the primary client going forward. Key capabilities:
- Multi-monitor support: Span your remote desktop across multiple monitors
- Dynamic display resolution: Adapts to window size and DPI changes
- Device redirection: Cameras, microphones, USB devices, printers, clipboard
- RDP Shortpath and Multipath support: UDP transport for better performance
- Multiple service support: One app for AVD, Windows 365, Dev Box, and RDS
- Workspace feed subscription: Subscribe by URL or email-based discovery
- Teams media optimisation: Offloads audio/video processing to the client
Web client — zero install
The AVD web client at client.wvd.microsoft.com provides browser-based access:
- Works in Edge, Chrome, Safari, and Firefox
- No installation or admin rights required on the device
- Good fallback for locked-down devices or BYOD scenarios
- Limitations: no multi-monitor, limited device redirection, no RDP Shortpath
🌐 Priya’s BYOD solution: “Half our NomadTech contractors use personal devices we don’t manage. We can’t ask them to install software. The web client is perfect — they open a browser, sign in with their credentials, and they’re in. For our full-time staff with company devices, we deploy Windows App through Intune.”
Exam tip: Web client limitations
The web client is convenient but has feature gaps compared to native clients. If an exam question asks about multi-monitor support, USB redirection, or RDP Shortpath — the web client does NOT support these. You need a native client (Windows App) for full functionality.
However, the web client does support clipboard redirection, audio playback, and basic file transfer.
Subscribing to a workspace feed
Before users can see their desktops and apps, they must subscribe to a workspace feed:
| Method | How It Works |
|---|---|
| URL subscription | User enters https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery |
| Email discovery | User enters their email address — the client discovers the feed automatically |
| Auto-subscription | Configure via Intune or Group Policy to subscribe automatically on sign-in |
Auto-subscription is recommended for managed environments — users open Windows App and their desktops appear without manual configuration.
Deploying AVD clients
Deployment methods
| Method | Best For | Details |
|---|---|---|
| Microsoft Store | BYOD, self-service | Users install Windows App from the Store |
| Microsoft Intune | Managed corporate devices | Push Windows App as a required or available app |
| SCCM/MECM | On-premises managed devices | Deploy MSI package through task sequences |
| Direct download (MSI) | Manual deployment, testing | Download from Microsoft and install manually |
| Group Policy (MSI) | AD-joined devices at scale | Deploy MSI via software installation GPO |
| Winget | Developer/IT pro self-service | winget install Microsoft.WindowsApp |
🌐 Priya’s deployment matrix: “We have staff in 12 countries on every platform. Windows and macOS devices get Windows App pushed through Intune. iOS and Android devices get it through the App Store and Google Play. Contractors use the web client. Ben’s creative team on Macs needed the native client for multi-monitor support with their external displays.”
Client auto-update
Windows App updates automatically by default. For enterprise environments, you can control updates:
- Microsoft Store: Updates managed through Store policies
- Intune: Deploy new MSI versions as app updates
- Update ring: Windows App supports update channels (Public, Insider)
| Feature | Windows App (Native) | Web Client (Browser) |
|---|---|---|
| Installation required | Yes — native app install | No — browser only |
| Multi-monitor | Yes — full multi-monitor support | No — single browser window |
| RDP Shortpath / Multipath | Yes — UDP transport | No — TCP only |
| Device redirection (USB, cameras) | Yes — full device redirection | Limited — clipboard and audio only |
| Teams media optimisation | Yes — offloads to client | No — runs in session host |
| Dynamic resolution | Yes — adapts to window/display changes | Limited |
| Offline workspace caching | Yes — remembers subscriptions | No — requires connection |
| Best for | Primary daily use on managed devices | BYOD, fallback, locked-down devices |
Troubleshooting client connections
Common issues and solutions
| Symptom | Likely Cause | Solution |
|---|---|---|
| ”We couldn’t find any resources” | User not assigned to an application group | Verify app group assignment in AVD portal |
| Black screen after connecting | Session host GPU issue or profile failure | Check FSLogix logs, GPU driver compatibility |
| ”Connection attempt failed” | Network connectivity or gateway issue | Run msrdcw://connect?diagnostics in Windows App |
| Slow connection / high latency | Using TCP instead of UDP | Enable RDP Shortpath, check UDP connectivity |
| Frequent disconnections | Network instability | Enable RDP Multipath for automatic failover |
| ”Access denied” | Conditional Access policy blocking | Check CA policies for device compliance |
Client log locations
| Client | Log Location |
|---|---|
| Windows App (Windows) | %localappdata%\Packages\Microsoft.WindowsApp_*\LocalState\DiagOutputDir |
| Web client | Browser developer tools (F12) console |
| macOS client | ~/Library/Containers/com.microsoft.rdc.macos/Data/Library/Logs |
Deep dive: Connection diagnostics URL
Windows App supports a special diagnostics URL that tests connectivity to the AVD service:
msrdcw://connect?diagnostics
Opening this URL launches a connectivity diagnostic that checks:
- DNS resolution for AVD endpoints
- TCP connectivity to the gateway
- UDP connectivity for RDP Shortpath
- WebSocket connectivity
- Certificate validation
This is invaluable for troubleshooting — run it before escalating any connection issue.
Priya has contractors in 5 countries using personal devices that NomadTech does not manage. The contractors need access to AVD desktops but cannot install software on their devices. What client should Priya recommend?
Mia's radiology team reports that Teams video calls are choppy and laggy when working through AVD. They use the web client. What should Mia do?
🎬 Video coming soon
AVD Clients: Choose and Deploy
Next up: User Experience and Session Settings — configure device redirection, multimedia settings, printing, session timeouts, and manage user settings through Intune and Group Policy.