Microsoft Azure Cloud Networking & Automation Fundamental

Create an Azure virtual network with address space 10.1.0.0/16 in Central India under the lab resource group, then add private 10.1.1.0/24 and public 10.1.2.0/24 subnets and verify.

Compare virtual networks to traditional networks, provision and configure Azure vnets with multiple subnets, and enforce isolation between vnets while understanding public and private IP ranges and vnet limitations.

Azure virtual network peering enables private traffic between virtual networks across regions, supporting regional and global peering, hub-and-spoke topology, gateway transit, and cross-subscription connectivity.

Learn to set up Azure virtual network peering between VNet instances in the same region (regional pairing) and across regions (global pairing), verify subnets, and confirm peering status is connected.

Verify connectivity across Azure vnet peering in three networks, confirming vnet1 connects to vnet2 and vnet3, while vnet2 and vnet3 do not connect due to non-transitive peering.

Test bandwidth across Azure virtual network peering with iperf3 on Linux VMs, establishing a server and running clients, and compare same-region versus global peering performance.

Explore Azure virtual machines built on the Azure hypervisor, an on-demand infrastructure as a service offering with full operating system, application, and data control and scalable deployment options.

Create a Windows Azure virtual machine in VNet one with a public subnet, configure a public IP and RDP access on port 3389, and verify connectivity in the Azure portal.

Learn how Azure virtual machine networking uses NICs within a VNet, with public and private IPs, NAT gateway, and NSG rules to manage inbound and outbound traffic.

Explore how Azure routes traffic between subnets and to the internet using system routes, default routes, and user defined routes, with virtual networks, peering, gateways, and service endpoints.

Demonstrate how virtual machines route traffic, how routing tables and VNet peering shape connectivity, and how public IPs and NAT gateways influence internet access within a VNet.

Azure NAT gateway provides fully managed, high-availability outbound internet connectivity for virtual networks, with static, dynamic, and port address translation options and public IP pools.

Create a nat gateway and attach it to a subnet in Central India, then test outbound ip detection from a vm to confirm the gateway's public ip.

Override system routes with Azure user defined routes to direct traffic to a virtual network gateway or virtual appliances, and drop or route traffic by address prefixes to internet.

Create and attach a user defined route table to a subnet, then add routes to block specific IP addresses and verify the effective routes on a Windows VM.

Explore a hub-spoke Azure network with a VPN gateway to route traffic between spokes, using a gateway subnet and gateway type to enable site-to-site, point-to-site, and VNet-to-VNet connections.

Build a hub-and-spoke Azure network using a VPN gateway to connect VNet one with VNet two and VNet three, enabling spoke-to-spoke connectivity without VNet peering and testing with pings.

Discover how Azure ExpressRoute provides private, high-throughput connectivity from on-prem or co-located facilities to Azure, offering secure, predictable bandwidth without the public internet.

Learn how Azure Network Security Groups filter traffic within a VNet by defining stateful inbound and outbound rules, using priorities, service tags, and application security groups for scalable control.

Explore how Azure network security groups filter traffic between resources in a virtual network and control ssh and http access using application security groups.

Explore Azure DNS introduction: host domains in Azure, manage DNS records with the same credentials and billing, understand name servers, anycast proximity, and DNS query flow from root to TLD.

Set up a public Azure DNS zone, connect it to GoDaddy via name servers, and create an A record to a Linux VM hosting Apache.

Explore Terraform introduction for Azure automation, install Terraform on Windows, set environment variables, and connect Terraform Cloud to Azure using a service principal with RBAC.

Provision an azure resource group with a vnet named terraform network via a cli-driven terraform cloud workflow, in east us, with address space 30.0.0.0/16 using init, plan, and apply.

Leverage Terraform automation with a GitHub repository to enable CI/CD via Terraform Cloud, automating Azure resource provisioning of a resource group and a virtual network using a version-control workflow.

Use Terraform to provision Azure resources via the Azure Resource Manager, defining a resource group, a virtual network with two subnets, and environment tags.

Learn to provision Azure resources with Terraform: create multiple VNets in the same region, set up VNet peering, and deploy a Windows VM with a dynamic public IP and NIC.

Azure VPN gateway essentials for site-to-site and point-to-site connections, including ExpressRoute and VNet-to-VNet options, encryption, redundancy, and scaling for secure, high-availability cloud-to-on-prem links.

Orchestrate a site-to-site azure vpn with terraform, creating a vnet with gateway subnet and test subnet, provisioning a route-based ipsec vpn and local gateways, and validating connectivity to a vm.

Demonstrates turning on BGP for an Azure site-to-site VPN to replace static routes, configure BGP peers on the Azure gateway and local gateway, and verify reachability and BGP table updates.

Enable active-active mode on the Azure VPN gateway by provisioning a second public IP and a second tunnel, then configure BGP to advertise networks and validate connectivity.

Explore Azure’s IPv6 introduction, enabling dual-stack virtual networks with IPv4 and IPv6, IPv6 subnets (slash 64), and internet connectivity via NAT gateways or load balancers, addressing IPv4 depletion.

Azure IPv6 lab walks through provisioning a virtual network, enabling IPv6, allocating v6 ranges, and testing dual-stack connectivity with IPv4 primary addresses and instance level public IPs.

Move the IPv6 public IP from the instance to a standard public load balancer. Configure the load balancer with a front-end IP, backend pool, and outbound rule to enable access.