In the previous topics, we mostly handled VNets and their features. Of course, each VNet in Azure can be divided into separate subnets that leverage the address space of the whole network. Whether you use subnets is completely up to you; it is perfectly fine to use a network that does not use them to isolate the different components of your system.
However, in most cases, you will want to create an extra separation so that you can clearly know which subsystem a particular component belongs to. These scenarios often involve several web applications that have to be segmented inside the same VNet so that they can connect to each other while remaining in isolated parts of the network. Such subnets may include additional resources so that you have an architecture of a network inside a network. We will now learn how you can use subnetworks in Azure VNets for your needs.
To get started, you will need a VNet that can be divided into subnets.
