The history of Microsoft VDI part 4: WVD to AVD
By now I hope you have enjoyed part one (Terminal Services), part two (RDS), and part three (RDS in Azure) in our series on the history and evolution of Microsoft VDI (virtual desktop infrastructure.) But I’m excited to say – we’ve gotten to the good stuff!
Let’s get into the introduction of Windows Virtual Desktop and take you through the modern, secure, and scalable capabilities in Azure Virtual Desktop, Microsoft’s cloud VDI service that is widely used across industries and companies of all sizes.
Traditional virtual desktops in Microsoft Azure
Prior to the invention of Windows Virtual Desktop and Azure Virtual Desktop, Microsoft primarily offered virtual desktops via traditional RDS. RDS in Azure allowed users to access virtual machines (VMs) hosted in Azure but lacked the advanced features, scalability, and integrated management capabilities that modern virtual desktop solutions like AVD provide.
One of the biggest limitations to widespread adoption of desktop virtualization prior to WVD/AVD, was that the customer had to own and manage all infrastructure. This is partly what made troubleshooting RDS in Azure so complex, there wasn’t an easy way to manage everything at scale.
The birth of Windows Virtual Desktop
Windows Virtual Desktop was introduced to the market in Fall 2019. You can read about the launch of WVD/AVD in Nerdio’s CEO’s blog post written at the time.
WVD marked a significant evolution from previous Microsoft technologies. It offered a cloud-native, scalable, and fully managed virtual desktop solution, leveraging the power of Azure. Unlike RDS, WVD allowed for multi-session Windows 10 experiences, simplified management, and integrated security features, making it a more flexible and user-friendly choice for organizations looking to facilitate remote, hybrid, or flexible work.
Windows Virtual Desktop’s evolution to Azure Virtual Desktop
Azure Virtual Desktop classic
What came to be called AVD classic was an implementation of AVD that ran on dedicated app services and was not part of the Azure Resource Manager (ARM). Not being part of ARM pretty much meant that AVD had no real integration with Azure.
In September 2023, Microsoft announced that AVD Classic will be retired/reach end-of-life on September 30, 2026.
Azure Virtual Desktop (current, ARM version)
The ARM version of AVD is fully backed into the ARM model. From there, a portal integration could be done. Things like ARM templates can now natively talk to AVD. All the benefits of Azure were now reachable (PS core support, API endpoints, etc.)
Again, in keeping in lockstep with Microsoft’s VDI evolution, our CEO wrote about the ARM version launch (at the time called ‘Spring Update’) back in 2020. You can check out the blog here.
Azure Virtual Desktop features and capabilities
Windows 10/11 Multi-Session
Leveraging Windows 10 or Windows 11 with AVD, organizations can support multiple active user sessions at the same time. Multi-session-based virtual desktops help IT teams to maximize resources and optimize costs.
Security and compliance
Because Microsoft is responsible for the infrastructure, there are no servers to harden or physical security to worry about. Microsoft also enacts Zero Trust principles by default. And additionally, AVD does not use RDP ports, which are an extremely common attack vector. Rather, it uses Reverse Connect, and webs sockets secured with SSL to ensure Azure environments are secure.
App services/application management
With Azure, Microsoft is providing applications that are smart and can act as clients to AVD. And there’s a version for Apple, there’s a version for Android, and there’s an HTML5 version that you can run technically on any device that has a browser compatible with HTML5. And obviously, there’s a Windows version.
As the enterprise administrator, you get to figure out how to get those applications on your users’ physical devices. Once the user opens their device or AVD client, they should get everything they need. This is facilitated by App Services which uses Reverse Connect to allocate VMs and users.
FSLogix + user profiles
FSLogix user profiles allow us to load the user state from a file share. This is important because it allows for the user state to be segregated away from the operating system state. When Microsoft acquired FSLogix, they were able to solve the issues with Outlook, OneDrive, and Teams. And the profiles make the VMs stateless, meaning they can come and go. As long as your profile is intact, you will be able to get whatever you need. Your configurations, your applications, and your settings for your applications will all “follow” you.
Conclusion + real-world success stories
Azure Virtual Desktop is a versatile and scalable solution that benefits organizations of all sizes and industries due to its ability to provide secure, cloud-based virtual desktops. It enables cost-effective remote work, easy management of virtualized environments, and seamless integration with other Azure services, accommodating the diverse needs and requirements of businesses while enhancing productivity and security.
Check out some of our customer and partner success stories for real-world examples of how Azure Virtual Desktop can improve your business.
