Hands-On Cloud Solutions with Azure

VNet

When you have an internal network, you usually care about the network you plug your resources into. In Azure, that piece is abstracted out of your view in most scenarios. However, you might need to control how your resources interact or you may need to connect your own network to Azure.

I like to use VNet for the following reasons:

• Isolation and segmentation
• Communication between Azure resources

• Communication with o-premise resources
• Filtering network traffic
• Routing network traffic, using routing tables to move traffic between subnets and networks on-premise or via the internet
• Connecting virtual networks in different regions

Let’s take a quick look at a simplified VNet implementation that has a public frontend and a private backend: ...