Virtual network resource limitations

Azure Networking Components

Virtual Networks

Implementing Virtual Networks

 Create new virtual networks at any time  Add virtual networks when you create a virtual machine  Need to define the address space, and at least one subnet Be careful with overlapping address spaces

Demonstration – Create VMs with Multiple NICs (CLI)
 Create a VNet, subnet, and NSG
 Create and configure multiple NICs
 Create a VM and attach the NICs

Public IP Addresses

Public IP addresses
	NIC	Yes
			Yes
VPN Gateway
	Front-end configuration	Yes

 Endpoints limit network access to specific subnets and IP addresses
 Improved security for your Azure service resources
 Optimal routing for Azure service traffic from your virtual network
 Endpoints use the Microsoft Azure backbone network

Service Endpoint Services

 Must configure both sides of the endpoints. For example, the virtual network side and the storage account side.  Each service endpoint has its own Azure documentation page

Demonstration – Service Endpoints

network gateway, virtual
network, internet, or virtual

Associate the Route

VNet-to-VNet Connections

Rely on VPN connectivity:
 Require VPN gateways for each VNet
 Equivalent to Site-to-Site VPN in hybrid scenarios

 The Azure portal:  For VNets in the same subscription

 Connect VNets with a VNet-to-VNet VPN connection  Requires a VPN gateway in each virtual network
 A secure IPsec/IKE tunnel provides the communication Use when VNet peering is not an option

Create the Gateway Subnet

Create the VPN Gateway

 Use the VPN Gateway type  Most VPN types are Route-based Your choice of gateway SKU affects the number of tunnels you can have and the aggregate throughput benchmark  Associate a virtual network that includes the gateway subnet  The gateway needs a public IP address

	P2S SSTP Connection s
	Max. 128	Not Supported
		Max. 250	650 Mbps
			1 Gbps
VpnGw3

✔ The Basic SKU is considered a legacy SKU

Create the Local Network Gateway

 Consult the list of supported VPN devices (Cisco, Juniper, Ubiquiti, Barracuda Networks)
 A VPN device configuration script may be available
 Remember the shared key for the Azure connection (next step)
 Specify the public IP address (previous step)

Create the VPN Connection

Verify the VPN Connection

Demonstration – VNet-to-VNet Connections

 Explore the Gateway subnet blade
 Explore the Connections blade
 Explore adding a virtual network gateway
 Explore adding a connection between the virtual networks

 VNet peering connects two Azure virtual networks (not transient)
 Two types of peering: Regional and Global
 Peered networks use the Azure backbone for privacy and isolation
 Easy to setup, seamless data transfer, and great

Configure VNet Peering

Gateway Transit

Service Chaining

 Leverage user-defined routes
and service chaining to