Azure Virtual Network design
Azure services often need to communicate on a private network, which is where virtual networks (VNets) come in. You can think of VNets as facilitating communication just like physical networks do, and they are very similar in concept. VNets, however, are implemented as software-defined networks on top of Azure’s robust physical infrastructure.
VNets are integral to infrastructure as a service (IaaS) solutions since virtual machines cannot be provisioned without them. A virtual machine will need access to an underlying network to not only access the internet but also be discovered by other virtual machines or resources on the same VNet. The device is assigned an internal IP address on the VNet. While VNets are a foundation for IaaS implementations, platform as a service (PaaS) services can also be provisioned to communicate via VNets. For example, Azure App Service with a minimum Basic pricing tier supports TCP and UDP communication. It can communicate...