What is our primary use case?
In Azure Virtual Desktop, we are designing infrastructure for the team. With my previous experience, I was managing Azure Virtual Desktop where I was handling all operations such as working on host pools and giving access to users.
It is mainly for giving access to users who are not part of the company, such as consultants or contractors who would be onboarded for a short period of time. We can design and develop a machine for them, and they can connect with Microsoft Authenticator from anywhere in the world. For example, if there are customers from India, we can easily assign a virtual desktop to them and they can login to the network and perform all activities. This really helps in remote working capabilities, and the data remains secure.
With Multi-session, we can have multiple users on the same machine. It's a non-persistent machine where if proper RAM and CPU are assigned for a workstation, up to 20 users can connect to the same session and access applications. This is useful when there are many users and the team is looking for a cost-effective solution. All users can login to the same workstation and applications can be deployed to them. It will be seamless and can be accessed from anywhere.
What is most valuable?
The best feature is scalability, as it can be used from anywhere.
For example, if a laptop needs to be shipped to users, it requires purchasing, procurement, adding it to the domain, and completing all tasks before handover, plus shipping costs. With Azure Virtual Desktop or any scalable solution, users only need a device, which can be their personal device. They can login to the cloud, use their authentication, and connect to the secure network. This reduces manual effort of procuring devices and shipping costs. When onboarding a team of 100 users for a project, we can assign virtual machines quickly, and resources can be allocated immediately for users to login and perform their tasks.
What needs improvement?
We can integrate anything with Azure Virtual Desktop from an application perspective. The App-V has evolved into MSIX. To deliver an application to Azure Virtual Desktop, MSIX can be used by expanding it as a virtual hard disk and attaching it to the virtual machine. When this is done, users who need the application will have immediate access through Active Directory group assignment.
One challenge with Virtual Desktop infrastructure is application delivery. From an infrastructure perspective, it's beneficial as we can have a fallback point - if one machine is down, we can have a disaster recovery site for redirection. The delivery of applications is a tedious process. Microsoft is working on building new products for efficient application installation. This feature might be included in upcoming releases. Currently, it's burdensome for IT administrators to create applications compatible with Virtual Desktop infrastructure, unlike traditional machines where direct installation is possible.
For how long have I used the solution?
I have been using this solution for 5 years.
What was my experience with deployment of the solution?
Regarding deployment processes, most companies using Microsoft utilize either Microsoft Intune or Microsoft SCCM. SCCM is primarily for on-premise computers while Intune is for cloud-based devices. For Azure Virtual Desktop and non-persistent machines, an additional step is required to create applications compatible for deployments. SCCM capability cannot be used to deploy applications on a non-persistent machine. IT administrators must create an App-V or MSIX and deploy that application to Azure resources for user access. This additional step impacts the time required for application deployment to end users.
What do I think about the stability of the solution?
Since these are cloud-related services for Azure Virtual Desktop, different licenses are available. When a company manages it themselves, it's simpler than existing solutions. You can identify errors in the environment through Azure, which clearly indicates if services aren't working. You can investigate the service and initiate troubleshooting. If issues aren't dependent on your environment, they require Microsoft's intervention. Once setup is complete, it's easy to manage with regular operations. The initial setup is complex, but maintenance is straightforward.
What do I think about the scalability of the solution?
With a persistent machine, assigning workstations to 100 users costs approximately $30,000. In a non-persistent machine with multi-session operating system, users can login to workstations on demand. Sometimes 50 users might login simultaneously, other times only 10. Resource allocation is based on active users. This saves costs as maintenance mode can be set for machines during weekends, allowing them to enter sleep mode and restart automatically on Monday at 7:00 a.m. When resources aren't utilized, there's no payment in Azure as it follows a pay-as-you-go model.
How are customer service and support?
Microsoft support is efficient. For priority incidents affecting 400-500 users, the turnaround time is quick with responses within 3 hours. They help identify root causes and implement fixes. The support agents are capable of narrowing down issues, providing temporary solutions when needed, and working with vendors or engineering teams to implement permanent solutions.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I worked with Citrix and VMware. Citrix was the first solution with a multi-session operating system supporting 20 users. Citrix can easily integrate with Microsoft App-V, which is advantageous, whereas VMware ThinApp lacks this integration capability.
Each solution has its advantages. With Citrix and VMware, monthly imaging work is required as OS images cannot be updated automatically. They must be taken to a centralized location and deployed for everyone in the image. With Azure Virtual Desktop, since applications are attached, the process is simpler and images can be delivered faster compared to Citrix and VMware.
How was the initial setup?
The initial setup complexity varies based on the environment. For financial institutions, there are numerous restrictions, whereas utilities companies might have limited restrictions due to different data sensitivity levels. The setup depends on requirements and industry type. For secure connections, requests should first reach Active Directory before returning to users. Financial industries typically have more complex setups compared to other industries.
What's my experience with pricing, setup cost, and licensing?
The cost depends on user numbers. For Azure Virtual Desktop with 100 VMs with vCPU for four, supporting 800 machines simultaneously, the cost is approximately $30,000. Costs vary based on user requirements. Developers might need machines with higher specifications and 16 GB RAM, while call center staff require less powerful machines. By classifying users into multiple groups, significant cost savings can be achieved.
What other advice do I have?
Configuration is simple since all components are in the same product family. Office 365 configurations connect to Active Directory and AD tenants, enabling immediate application access upon user verification. This applies to Teams as well.
Some organizations use different tools for data management, such as Forcepoint data loss protection (DLP). These applications allow policy configuration to prevent data from leaving the company. Microsoft Defender can also be used to classify documents as private, confidential, restricted, or public, with corresponding rules. When Azure Virtual Desktop and Defender are applied, data is highly secured.
The latest release includes all necessary features. Previous challenges with host pool management, such as renaming and removing devices, have been resolved, making the process much simpler.
It's advantageous to purchase from Microsoft rather than AWS because application compatibility and integration are simpler with Microsoft.
I would rate this solution 8.5 out of 10.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure