In this section, we are going to discuss how to connect between virtual networks.
Its important to understand that how Azure implements security across virtual networks. By default, a machine which is one virtual network cannot communicate with a machine or any other resource on the other virtual network.
Any storage resource can be communicated via public end points and associated keys. But, if you have associated your storage account to a private end point, on a virtual network, then you will find that virtual machine on another network cannot communicate with it.
But, that doesn’t stop networking. We can actually setup peering relationship between the two networks.
In this section, we will continue from the last blog and discuss more about application security groups.
Application security groups are the enhancements of network security groups. It allows you to reduce the number of network security groups (NSGs) you require or the number of security rules that you require.
The way it does that by grouping resources based on the same rules. So, instead of creating network security groups for the every subnet which you have and then separate rules for each resource; you can put all of your SQL Server dbs, all of your app servers, web servers into the same security group.
Let’s create a one. Search for application security groups in all services.
In this section, we will continue from the last section and see how to get started with route table.
Next, we are going to create a route table. A route table is basically a list of IP address ranges. And, this will tell Microsoft azure how to send traffic which is coming over your network. Hence, let’s search for the same in all services.