Introduction to Azure Virtual Network (VNET)
Introduction to Azure Virtual Network (VNET)
A network or environment called an Azure Virtual Network (VNet) can be used to run virtual machines (VMs) and applications in the cloud.
Once Azure services and virtual machines are built, they communicate securely.
The size, availability, and isolation that come with Azure's infrastructure are similar to those of a network you might run in your own data center.
Companies can build efficient cloud applications by using Azure networking components, which provide a wide range of functionalities.
 |
| Fig 1.1- Introduction to Azure VNET |
Benefits of Using Azure Virtual Network
- The network has a high level of security
- You can run your applications in an isolated environment
- Default access to the public internet is available to a subnet in a VNet
- Traffic can easily be directed from resources
- Simple yet sophisticated network topologies can be built with it
The components of Azure Networking are listed below:
Subnets, routing and Network Security Groups
Subnets
In subnets, users can segment the virtual network into one or more subnetworks. Each subnet consists of a server, and there are also private and public subnets.
NAT (Network Address Translation) gateways present in the public subnet can be used by private instances to access the Internet, while public instances can access it directly.
Routing
In virtual networks, traffic is automatically routed and routing tables are created for each subnet. Routing delivers data by choosing a suitable path from source to destination.
Network Security Groups
Depending on the destination IP addresses, ports, and protocols, the Network Security Groups restrict inbound and outbound network traffic for the virtual machine.
In other words, you can say that In the Network Security Group, a firewall protects the virtual machine by limiting network traffic and restricting traffic depending on the IP address, port, and protocol of the destination.
