Azure Virtual Networks, Virtual Machines & Network Security Groups

Lab Steps

lock
Logging in to the Microsoft Azure Portal
lock
Provision a Virtual Network and Subnet with default settings
lock
Change Network Settings with no connected devices
lock
Add a Virtual machine to the Network
lock
Change Network settings with a connected devices
lock
Deploy a second virtual machine into the Vnet1
lock
Provision a Network Security Group and connect it to Subnet1

Ready for the real environment experience?

DifficultyBeginner
Time Limit2h 30m
Students314
Ratings
4.8/5
starstarstarstarstar-half

Description

Introduction: 

Azure Virtual Networks (VNets) are the fundamental building block of your private network in Azure. VNets enable you to build complex virtual networks that are similar to an on-premises network, with additional benefits of Azure infrastructure such as scale, availability, and isolation. A VNet is a representation of your own network in the cloud. It is a logical isolation of the Azure cloud dedicated to your subscription. You can use VNets to provision and manage virtual private networks (VPNs) in Azure and, optionally, link the VNets with other VNets in Azure, or with your on-premises IT infrastructure to create hybrid or cross-premises solutions. Each VNet you create has its own CIDR block and can be linked to other VNets and on-premises networks as long as the CIDR blocks do not overlap. You also have control of DNS server settings for VNets, and segmentation of the VNet into subnets. 

In this Lab exercise, you will: 

  • Provision a Virtual Network with default settings  
  • Change the IP Address range of the network, while there are no devices (Virtual Machines) connected to the network
  • Add a Virtual Machine to the amended network 
  • Change the IP Address range of the network with the new connected device present, and move the connected device to a new subnet
  • Create a Second Virtual machine 
  • Create a Network Security group to allow remote desktop connectivity
  • Test Remote and internal connectivity using one of the Virtual Machines 
About the Author

David’s IT career started in 1990, when he took on the role of Database Administrator as a favor for his boss. He redirected his career into the Client Server side of Microsoft with NT4, and then progressed to Active Directory and each subsequent version of Microsoft Client/Server Operating Systems. In 2007 he joined QA as a Technical Trainer, and has delivered training in Server systems from 2003 to 2016 and Client systems from XP onwards. Currently, David is a Principal Technical Learning Specialist (Cloud), and delivers training in Azure Cloud Computing, specializing in Infrastructure Compute and Storage. David also delivers training in Microsoft PowerShell, and is qualified in the Alibaba Cloud Space.