Azure Classroom Series – 22/Aug/2021

Networking in Azure

  • In Azure, we can create virtual networks with subnets using a service called as Azure VNET.

  • To understand networking in Azure we need to know about Regions in Azure Preview

  • When ever we need to create any resource in Azure, it has to be part of a group (Resource Group).

  • Resource Group has resources which can be from same or different regions

  • In Azure when we create a Network, the Network is created at a Region level

  • Lets create a first vnet Preview Preview Preview Preview Preview Preview Preview Preview

  • Exercise: Create a virtual network with 4 subnets, which are capable of 500 devices each. Preview

  • In any network, We cannot use 2 IP addresses

    • All 0 will be Network Id
    • All 1 (255) will be broadcast id
  • In the case of Azure we cannot 5 IP Addresses

    • All 0 will be Network Id (x.x.x.0)
    • ALL 1 will be broadcast id (x.x.x.255)
    • x.x.x.1 Reserved by Azure for the default gateway
    • x.x.x.2 and x.x.x.3 Reserved by Azure to Map the Azure DNS IPs to VNET Space
  • In Azure the Smallest subnet possible is /29 Preview

  • Azure Network will have default routing which enables all the communication within vnet. Preview

  • When we want to create vm’s, Every VM has to be part of some subnet. Networking is connected to VM using NIC (Network interface card), This is virtual NIC and this receives the private ip address from the configured address space (cidr range) Preview

  • While creating vm, we can choose a public ip address for this NIC so that we can access the VM from internet.

  • Now lets create the following network in Azure Preview Preview

  • Now lets try to create a ubuntu vm with public ip in subnet1 Preview Preview Preview Preview Preview Preview Preview

  • Lets look at network interface Preview

  • Lets ssh into this machine

ssh <username>@<publicip>


  • Now lets try to create one more ubuntu vm in subnet2 without publicip Preview Preview
  • We cannot directly login into vm created in subnet2, but we can login into vm1 and from there login into vm2 Preview Preview
  • Observations made:
    • VM with public ip is able to access internet
    • VM without public ip is not able to access internet.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

About learningthoughtsadmin