- 100 GB capacity
- general availability
- VNET Peering Regional Ingress
A virtual network is a network overlay that you can configure in Azure. VMs and services that are part of the same virtual network can access each other. However, services outside the virtual network have no way to identify or connect to services hosted within virtual networks unless you decide to configure that specific type of connection, as in the case of VNet to VNet configurations. This provides an added layer of isolation to your services. Azure Virtual Network also lets you extend your network into Azure and treat deployments as a natural extension to your on-premises network. Whether you need a virtual network depends entirely on what you are trying to do. There are no one-size-fits-all virtual network designs. However, you'll find that every solution falls into one of 3 basic configuration categories: No VNet, Cloud-Only VNet, or Cross-Premises VNet (which includes Hybrid solutions). Once you know which basic category your project falls under, you can then build on it to create a network design that supports the solution that you want to create. It's best to know if you need a virtual network before you deploy your VMs and cloud services. VMs and cloud services acquire their network settings during deployment. This means you can't simply move something into a VNet if it is already deployed. However, you can redeploy your VMs and cloud services. It's a relatively straight forward process, but can result in some minor downtime for the VMs or services while you redeploy.