![]() Of course, if you're planning on using only Azure AD Join you won't be needing domain controllers so you might skip the Identity subnet in the future. This one will be called Identity, and it's going to be for your active directory domain controllers that you'll build later. For the subnet address range, we'll use the next available range, which is 10.0.1.0/24. Click to add a new subnet and we'll call this one AzureFirewallSubnet. Rename this subnet to GatewaySubnet and you can leave the other settings alone and click save at the bottom. The first subnet has been created for you with a 10.0/24 which makes up 256 addresses. AzureBastionSubnet, this service will allow you to connect to your Azure virtual machine resources and manage them. AzureFirewallSubnet, this is required for you to set up an Azure firewall for security. The GatewaySubnet, this will contain the Azure Virtual Network gateway resources, which are required for setting up a VPN or express route connection. Now, there are three special subnets in Azure that need specific names. A subnet is where we divide those 65,000 addresses into different blocks and we will need a few of those. ![]() All of these 65,000 IP addresses become usable in the bottom section where you create subnets. So, if we have a 10.0/16 network in Azure, you cannot have a 10.0/16 network on-premise that connects to Azure. Once this virtual network is connected to any other network, they must all have unique addresses. Things are different when connecting this virtual network to another virtual network in your subscription or to your on-premise networks. Even though we have the exact same address spaces we don't overlap and the networks can't communicate together because we're two different users in two different environments of Azure. You and I can both create a 10.0/16 network. Now, one of the beauties of how Azure does this, is called software defined networking. By default, you've been given a /16 network, which means that you have over 65,000 IP addresses. This is the number of total IP addresses in your network. This is where you set up your address space. Azure resources need to reside in an Azure region and since we need to keep all of our resources as close together as possible, I suggest that you build this network in a region located closest to you, and I'll pick the East US. So, sticking with our naming convention, we'll call this VNET-AVD. Now we need a name for our virtual network. This way, when you're looking at your resources, you'll know that this is a resource group for Azure Virtual Desktop that contains network resources. Now, there are several strategies for how to name and locate your resources in Azure, but to keep things simple today, we're going to build one resource group for our networks and we'll call it RG-AVD-Network. So, select your subscription and let's click to create a new resource group. Select the first option of virtual network and click create.Įvery resource in Azure needs to be in a subscription and a resource group. In the Azure portal, click the plus to create a resource and in the search box type network. And then we'll set up security to allow connectivity to Azure Virtual Desktop. Then we'll set up our supporting services like our gateway and DNS. Now that you've got the basic concepts, let's build our network in Azure. To get the most out of this course, you should have knowledge of the following: Anyone looking to learn more about Azure Virtual Desktop.Azure administrators with subject matter expertise in planning, delivering, and managing virtual desktop experiences and remote apps, for any device, on Azure.Monitor and troubleshoot network connectivity.Manage Azure Virtual Desktop session hosts using the Azure bastion service.Manage connectivity to the internet and on-premises networks.Implement your Azure Virtual Desktop networking solution.Recommend the correct solution for network connectivity.Understand Azure virtual desktop networking requirements.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. This is most critical with an internet-accessible solution like Azure Virtual Desktop, so we need to properly build it and secure it. It is networking that will provide connectivity and security to your applications and solutions. The most fundamental component of any cloud solution is the network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |