Azure Virtual Desktop Networking Planning
Azure Virtual Desktop Implementation
The course is part of this learning path
The most fundamental component of any cloud solution is the network. It is networking that will provide connectivity and security to your applications and solutions. This is most critical with an internet-accessible solution like Azure Virtual Desktop, so we need to properly build it and secure it.
In this course, we will help you design your Azure Virtual Desktop network components so you can not only gain insight into those Azure services but also understand how they integrate and relate to the Azure Virtual Desktop service and help you to pass the Azure Virtual Desktop Specialty exam.
- Understand Azure virtual desktop networking requirements
- Recommend the correct solution for network connectivity
- Implement your Azure Virtual Desktop networking solution
- Manage connectivity to the internet and on-premises networks
- Implement and manage network security
- Manage Azure Virtual Desktop session hosts using the Azure bastion service
- Monitor and troubleshoot network connectivity
- Azure administrators with subject matter expertise in planning, delivering, and managing virtual desktop experiences and remote apps, for any device, on Azure
- Anyone looking to learn more about Azure Virtual Desktop
To get the most out of this course, you should have knowledge of the following:
- Azure networking
- Network security
- Network monitoring and troubleshooting
Now that we've created our virtual network, we need to do some configuration. Select VNET-AVD, on the left blade, select DNS Servers. The default option is to use Azure provided DNS. This is referring to the default DNS IP for Azure of 188.8.131.52. For many workloads this would be just fine, and if you're planning on only using Azure AD Join VMs, you can stick with the default. However, since AVD relies on Active Directory DNS today, you will need to change this to custom and enter the IP addresses of your Active Directory DNS servers. I will have two of these located in Azure in the identity sub-net that we created earlier. So their IP addresses would be 10.0.3.4 and 10.0.3.5 respectively. I will also add the Azure default as my last DNS address. This way if my DNS servers can't resolve something, it'll be forwarded to Azure DNS. If your DNS servers are on premise, you can add those here as well. But before there'll be able to work, you'll need hybrid connectivity.
Dean Cefola is a Principal Azure Engineer at Microsoft and has worked in the IT industry for over 20 years. Dean has been supporting Azure Virtual Desktop from the beginning and is the Microsoft FastTrack Global Leader for AVD.