VNET- Customer
managed secure, isolated virtual network.
·
Services and VMs that are part of VNET can
access each other.
·
Each VNET can have as many subnets
·
All services deployed within a VNET can access
internet
Typed of VNETs
·
Cloud
only VNET
o
When a VNET created in Azure
o
VMs and services access through endpoints.
o
No configuration of VPN device required.
·
Cross
premise Virtual network(Hybrid network)
o
Connection of On-Premise network with the Cloud
VNET through site to site tunnel.
o
Requires a VPN device.
VNet Address space and Subnet
o
Specify Topology during VNET creation: address
space and subnet
o
Private address space
§
This is the range VMs and services can use
§
Non Routable(these can’t access by public
network)
§
Specified in CIDR Notation (classless inter
domain routing)
·
10.0.0.0/8: 10.0.0.0 to 10.255.255.255
·
172.16.0.0/12: 172.16.0.0 to 172.31.255.255
·
192.168.0.0/16:192.168.0.0 to 192.168.255.255
o
Subnet
§
Break up the network with more manageable
sections.
§
All services can access across subnets.
§
Network security groups can be utilized to
implement rules .