Table of contents
In this hands-on lab, we are going to implement and configure an Azure Virtual Network NAT
NAT
Network Address Translation (NAT) is a process that enables one unique IP address to represent an entire group of computers. In network address translation, a network device, often a router or NAT firewall, assigns a computer or computers inside a private network a public address. In this way, network address translation allows the single device to act as an intermediary or agent between the local, private network and the public network that is the internet. NAT’s main purpose is to conserve the number of public IP addresses in use, for both security and economic goals. https://avinetworks.com/glossary/network-address-translation/
Azure NAT Gateway
Azure NAT Gateway is a fully managed service that provides Network Address Translation for an Azure Virtual Network, which simplifies the process of providing outbound internet connectivity to virtual machines without a public IP address. The NAT gateway provides outbound internet connectivity for resources in a subnet within a virtual network without needing a public IP address assigned to each resource.
Configuring Azure NAT Gateway
Confirm the private virtual machine with no public IP
Search for NAT Gateway in the Azure portal and click it.
Create the NAT gateway. The NAT gateway needs to be in the same region as the Virtual Network that contains the subnet you want to associate it with.
Configure the public IP address the NAT gateway should use. This is the outbound IP address that our private VM is going to be associated with for internet connectivity.
Choose the subnet to be associated with the NAT gateway. All virtual machines in the subnet will be automatically given outbound internet connectivity through the NAT gateway
Verify all the details are correct before proceeding with the creation of the NAT gateway.
Deploying the NAT gateway resources.
confirm the Outbound IP configured for the NAT gateway which will be associated any VM in the subnet.
confirm the outbound IP associated with the private VM. The VM was logged into using Azure Bastion
Voila! QED !