Updated January 2026 version
This guide provides a practical overview of the Azure Virtual Desktop (AVD) user experience across macOS and Windows devices. It also explains key architectural and operational differences between Azure Virtual Desktop, Windows 365, and traditional Remote Desktop Services (RDS).
Azure Virtual Desktop is Microsoft’s fully managed enterprise Virtual Desktop Infrastructure (VDI) platform hosted on Azure. It allows organizations to deliver secure, scalable virtual desktops and applications to users on virtually any device.
Contents
- User Experience
- macOS AVD User Experience
- Windows AVD User Experience
- Microsoft Teams on Azure Virtual Desktop
- Connectivity
- Comparison Sections
- Azure Virtual Desktop vs Windows 365
- Azure Virtual Desktop vs Self-Managed RDS
- Automatic Scaling
- Cost Overview
- Additional Resources and References
User Experience
Users can connect to Azure Virtual Desktop using:
- Web browser
- Remote Desktop application (Windows or macOS)
- Remote Desktop mobile apps (iOS and Android)
- Thin client devices
macOS AVD User Experience
On macOS, access Azure Virtual Desktop using the Microsoft Remote Desktop client available from the macOS App Store:
https://apps.apple.com/ca/app/microsoft-remote-desktop/id1295203466
After installing the app, users add their workspace by entering their corporate email address or workspace URL. The client automatically discovers the subscription and completes the setup process.
Detailed guidance on email discovery:
https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-email-discovery
Connecting on macOS
The initial login process typically completes within 30 seconds on a stable network connection. Authentication behavior may vary based on organizational policies such as MFA or conditional access.
Windows AVD User Experience
On Windows devices, users configure their subscription, authenticate, and connect using the Remote Desktop client. Once authenticated, session establishment is typically completed within approximately 30 seconds on high-speed networks.
Microsoft Teams on Azure Virtual Desktop
Microsoft Teams is fully supported on Azure Virtual Desktop, including chat, meetings, calling, and collaboration. Media optimization improves audio and video quality for both Windows and macOS clients.
More details:
https://learn.microsoft.com/en-us/azure/virtual-desktop/teams-on-avd
Connectivity
Azure Virtual Desktop does not require traditional VPN connectivity for end-user access. Users connect securely over the public internet using Microsoft-managed reverse connect infrastructure, though organizations may still integrate VPNs for hybrid or compliance scenarios.
Organizations can integrate multi-factor authentication and single sign-on using Microsoft Entra ID.
Comparison Sections
Azure Virtual Desktop vs Windows 365
Windows 365 is Microsoft’s Cloud PC service that delivers dedicated desktops through a per-user licensing model where Microsoft manages the underlying Azure compute and infrastructure. Azure Virtual Desktop provides a more flexible consumption-based architecture using pooled or personal session hosts that the customer designs and controls.
| Feature | Windows 365 | Azure Virtual Desktop |
|---|---|---|
| Management | Microsoft-managed | Customer-managed |
| Desktop types | Dedicated Cloud PC | Pooled or personal |
| Remote App support | Not available | Supported |
| Compute flexibility | Fixed | Fully flexible |
| Licensing model | Per-user license | Azure consumption + eligible license |
| User profile management | Limited | FSLogix supported |
| Integration options | Limited | Extensive |
Azure Virtual Desktop vs Self-Managed RDS
Azure Virtual Desktop abstracts and automates core infrastructure components traditionally managed in RDS environments, including brokers, gateways, load balancers, and client connectivity.
Product comparison:
https://azure.microsoft.com/en-us/products/virtual-desktop/#features
Automatic Scaling
Azure Virtual Desktop supports automated scaling using scaling plans. Administrators can define ramp-up, peak, ramp-down, and off-peak schedules for each host pool, optimizing both performance and cost.
Cost Overview
AVD costs consist of:
- User access rights — covered by eligible Microsoft 365, Windows 11 Enterprise, or RDS licenses associated with Microsoft Entra ID identities
- Azure infrastructure — compute, storage, networking, backups, monitoring, and supporting services
Organizations typically present combined cost on a per-user basis for budgeting and optimization.
Additional Resources
Cloud Adoption Framework for AVD
- https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/wvd/
- https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/wvd/strategy
- https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/wvd/plan
- https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/wvd/migrate-assess
- https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/wvd/manage
- https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/wvd/govern
Microsoft Learn Paths
- https://learn.microsoft.com/en-us/training/paths/plan-azure-virtual-desktop-implementation/
- https://learn.microsoft.com/en-us/training/paths/m365-wvd/
AVD Prerequisites
https://learn.microsoft.com/en-us/azure/virtual-desktop/prerequisites
Identity Limitations (Current AVD Behavior)
Based on current Azure Virtual Desktop identity capabilities:
https://learn.microsoft.com/en-us/azure/virtual-desktop/deploy-azure-ad-joined-vm
- Azure AD-joined session hosts do not support external identities such as Azure AD B2B or B2C
- Azure AD-joined session hosts can access Azure Files only using Azure AD Kerberos authentication
- The Microsoft Store Remote Desktop client does not currently support Azure AD-joined session hosts
Photo by Windows
https://unsplash.com/@windows
https://unsplash.com/photos/lhDjusLtpP4