An Azure Virtual Network (VNet) allows creation of an isolated virtual network in the cloud. A VNet contains subnets that can segment resources logically. Subnets can be private, requiring a NAT gateway for internet access, or public with direct internet access. VNets can be connected across regions using virtual network gateways and peering to allow communication between virtual networks in a secure and cost-effective manner.

2. Azure Virtual Network
• An Azure Virtual Network (VNet) is a network or
environment that can be used to run VMs and applications
in the cloud.
• When it is created, the services and Virtual Machines
within the Azure network interact securely with each other.

3. Components of Azure
VNet
• Subnets
• Routing
• Network Security Groups

4. Subnets
• Subnets let users segment the virtual network into one or
more sub-networks.
• These sub-networks can be separated logically, and each
subnet consists of a server.

5. Subnets
We can further divide a subnet into two types:
1. Private
2. Public
• Private - Instances can access the Internet with NAT
(Network Address Translation) gateway that is present in
the public subnet.
• Public - Instances can directly access the internet.

6. Routing
• It delivers the data by choosing a suitable path from source
to destination.
• For each subnet, the virtual network automatically routes
traffic and creates a routing table.

7. Network Security
Groups
• It is a firewall that protects the virtual machine by limiting
network traffic.
• It restricts inbound and outbound network traffic
depending upon the destination IP addresses, port, and
protocol.

8. Advantages of Using
Azure Virtual Network
• It provides an isolated environment for your applications
• A subnet in a VNet can access the public internet by
default
• We can easily direct traffic from resources
• It is a highly secure network
• It has high network connectivity
• It builds sophisticated network topologies in a simple
manner

9. How to Launch an Instance
using Azure VNet?
• First, create a virtual network in the Azure cloud
• Next, create subnets into each virtual network
• Now, assign each subnet with the respective instance or
Virtual Machine
• After which you can connect the instance to a relevant
Network Security Group
• Finally, configure the properties in the network security
and set policies
• As a result, you will be able to launch your instance on
Azure

10. Virtual network gateway
• A virtual network gateway is composed of two or more
VMs that are automatically configured and deployed to a
specific subnet you create called the gateway subnet.
• The gateway VMs contain routing tables and run specific
gateway services.

11. Configuring a VPN
Gateway
• Site-to-Site VPN connections
• Point-to-Site VPN connections
• VNet-to-VNet VPN connections

12. Site-to-Site VPN
connections
• S2S connections can be used for cross-premises and hybrid
configurations.
• A S2S connection requires a VPN device located on-
premises that has a public IP address assigned to it. For
information about selecting a VPN device

13. Point-to-Site VPN
• A Point-to-Site (P2S) VPN gateway connection lets you
create a secure connection to your virtual network from an
individual client computer.
• A P2S connection is established by starting it from the
client computer.

14. Point-to-Site VPN
• This solution is useful for telecommuters who want to
connect to Azure VNets from a remote location, such as
from home or a conference.
• P2S VPN is also a useful solution to use instead of S2S
VPN when you have only a few clients that need to
connect to a VNet.

15. Point-to-Site VPN

16. VNet-to-VNet connections
• Connecting a virtual network to another virtual network
(VNet-to-VNet) is similar to connecting a VNet to an on-
premises site location.
• The VNets you connect can be:
• in the same or different regions
• in the same or different subscriptions
• in the same or different deployment models

17. VNet-to-VNet connections
•

18. Virtual Network peering
• VNet Peering in Azure allows the traffic of one virtual
network to communicate to another virtual network.
• This is basically used for database failover, disaster
recovery, or cross-region data replication.
• VPN gateways are used in an encrypted connection in the
region but VNet Peering provides connection sharing in
different regions.

19. Virtual Network peering

20. Importance Of VNet
Peering
• • VNet peering is similar to an inter-VLAN Routing in
VLAN of On-premise networks so it works similarly to
inter-VLAN connect to one VLAN to another VLAN for
communication.
• • In Azure infrastructure, need to connect to virtual
networks to each other for sharing traffic which can be
applications, backup, replication, recovery, or information
sharing.

21. Importance Of VNet
Peering
• • The virtual machines of virtual network connections to
other virtual machines of different Virtual network via
connection of VNet Peering in the same region or across
the region

22. Types Of VNet Peering
1. Default VNet Peering: it empowers the connectivity
between various VNets within the same Azure region.
2. Global VNet Peering: it allows Virtual networks to
connect across different Azure regions. It provides private
peering with low latency and high bandwidth in Azure
backbone infrastructure.

23. Pre-checks Of VNet Peering
• VNet Peering only establishes between Two virtual networks, it’s
not transitive. for example, VNet P and VNet Q having VNet peering,
VNet Q and VNet R having peering than VNet P and VNet R are not
having VNet peering.
• Before Peering at virtual networks check for the non-overlapping IP
addresses.

24. Pre-checks Of VNet Peering
• The virtual network’s resource cannot set connections with the
front-end IP address’s basic load balancer in Global VNet Peering in
Azure.
• Once a virtual network peered with another virtual network then
adding or deleting the address range is auto-disabled.

25. Benefits
• Network traffic of peered Virtual networks become private.
• Virtual network peering in Azure allows transferring data across
Azure deployment models, subscriptions, and other regions.
• No downtime issues in global Azure virtual network peering.
• It configures the connection with high bandwidth Low latency in the
VNet region.

26. Benefits
• Global VNet peering has erased the need for VNet to VNet peering
Azure configuration. It disabled the use of VPN encryption, public
internet, or any gateways.
• This is a very cost-effective and Time-saving process that
controlling the backup, traffic, sharing from different regions

27. ExpressRoute
• Azure ExpressRoute is a service that, with the help of a connectivity
provider, helps us in establishing a private connection to extend your
on-premises networks to the Microsoft cloud.
• So, Azure ExpressRoute works like a VPN setup between you and the
Microsoft cloud. The connection types include point-to-point ethernet
network, any-to-any (IPVPN) network, and virtual cross-connection
through a co-location facility.