Azure Virtual Network Study

[RongTsai4Git]

reference

• azure-virtual-network

[RongTsai4Git]

• By default, all VNet resources can communicate outbound to the Internet.
• To allow inbound communication from the Internet, can create rules to allow Internet traffic or add a public IP or Load Balancer.

Address Space

• VNet need to specify a private IP address space in the RFC 1918 range, such as 10.0.0.0, 192.168.0.0, and 172.16.0.0
  • Address spaces cannot overlap with each other.
  • Should not use overlapping network spaces with your on-premises data center if you intended on creating a hybrid network.

Network Security Groups

• use Network Security Groups (NSG) to filter traffic in and out of a virtual network that automatically secure resources by blocking Internet traffic but allowing traffic from other virtual networks.

Routing and Peering

• Azure automatically connects subnets in the same virtual network together, routing between different virtual networks requires network peering.
  • Virtual network peering connects multiple VNets together, and traffic between the virtual networks traverses the Microsoft backbone infrastructure, not the Internet.

Pricing

• Creating virtual networks is free of charge.
• Can create up to 50 virtual networks per subscription.
• Create a peering connection between different virtual networks, Azure charges for the inbound and outbound data transfers.
  • For example, peering between two virtual networks in the East US region charges $0.01 per GB for inbound and outbound data transfers.
• Creating a peering connection between networks in different regions incurs an extra charge.