Forum Discussion
Better start with Virtual Machines on the same subnet
Yes you can assign them to the same subnet but not for all services. VMs can be created in the same VNet and they can connect to each other using private IP addresses. They can connect even if they are in different subnets without the need to configure a gateway or use public IP addresses. If you deploy multiple VMs into a VNet or subnet, they are assigned IP addresses as they boot up.
If you plan to deploy some Azure service resources into a virtual network, they may require, or create, their own subnet, so there must be enough unallocated space for them to do so. To determine whether an Azure service creates its own subnet, see information for each Azure service that can be deployed into a virtual network. For example, if you connect a virtual network to an on-premises network using an Azure VPN Gateway, the virtual network must have a dedicated subnet for the gateway but that is not the case for VM's :-)
Thank you
Dav,
