Reviewing Azure Virtual Networks

Lab Steps

lock
Logging in to the Microsoft Azure Portal
lock
Reviewing Azure Virtual Networks
lock
Reviewing Azure Load Balancers
lock
Reviewing Azure Application Gateways
lock
Reviewing Azure VPN Gateways
lock
Starting an Azure Cloud Shell
lock
Reviewing Azure Content Delivery Network
Need help? Contact our support team

Here you can find the instructions for this specific Lab Step.

If you are ready for a real environment experience please start the Lab. Keep in mind that you'll need to start from the first step.

Introduction

Azure Virtual Networks (VNets) is the basic building block for logically isolating resources using networks in Azure. VNets enable many different Azure services, such as load balancers, virtual machines and more, to communicate securely with one another. In combination with other Azure services like network security groups they also provide layers of protection from different segments of the Internet to your Azure resources. In this Lab Step, you will navigate to a VNet in the Azure Portal and learn about Azure Virtual Networks.

 

Instructions

1. On the dashboard of the Azure Portal, click the portal menu > All resources:

alt

You can proceed even if the deployment didn't reach 100%. It will take about 20 mins.

 

2. On the All Resources page, click calabs-vnet:

alt

 

3. On the Overview blade, notice the information near the top of the page:

alt

There are a few things to be aware of in this section:

  • Like other resources in Azure, the virtual network has a Resource group ID and a Subscription ID. This means that the virtual network belongs to a specific resource group and Azure subscription. To quickly summarize, resource groups and subscriptions are two tools Microsoft uses to organize, track and bill for its resources.
  • The network also has a Location, which is the geographical region that holds the servers your network is hosted on.
  • Finally, the network has an Address space of 10.0.0.0/16, meaning any resource that is deployed under this virtual network and which is capable of having an IP address will have an address inside this address space. Also, note that because 10.0.0.0/16 is a private address range, this network currently only hosts private resources.

 

4. In the Menu to the left, click Connected Devices:

alt

Note that there are currently two are Network Interfaces connected to this VNet. Notice a couple of things about each connected resource:

  • Each resource has an IP Address that falls within the address range you saw earlier.
  • Each resource also belongs to a subnet, which you will review next.

 

5. In the Menu to the left, click Subnets:

alt

subnet is a way to further separate a VNet into smaller segmented networks. Subnets are used to increase the amount of organization and trackability of resources. Because you can apply different network security groups to different subnets, using subnets also potentially increases the security of your infrastructure.

Notice that there are two subnets on the Subnets blade and that each one has an Address range that falls within the address range of the VNet. Click here for a refresher on how CIDR ranges work and an explanation of how the Address ranges of the subnets on this blade fall within the address range of the VNet.

 

6. Return to the Connected devices blade and click nic0:

alt

 

7. On the following blade, click caLabsVM0:

alt

You are brought to the Overview blade of the caLabsVM0 Virtual Machine (VM). This is because the network interface deployed to the VNet was attached to this VM. Network interfaces allow resources including VMs to communicate with other resources in Azure and on the Internet. Because this VM has a network interface attached and that network interface belongs to the VNet, this VM will be able to communicate with other resources in the VNet.

 

Summary

In this Lab Step, you navigated to a VNet in the Azure Portal and learned about the fundamentals of VNets.