Creating a user-defined route is not a complicated process, all you need to do is perform the following steps:
- Search for route tables, and open its blade.
- Click on Add to create your customized route, as shown in the following screenshot:
Figure 4.38: Route tables blade
- A new blade will pop up, wherein you have to fill in the following:
- Name: A name for the route
- Subscription: Specify the subscription that will be charged for using this service
- Resource group: The resource group within which the route table will exist
- Location: The location where this service will be built:
Figure 4.39: Create a new route table
- Once you have clicked on Create, the route table will be created.
- Navigate to the created route table, as shown in the following screenshot:
Figure 4.40: Route table overview
- Navigate to Routes, under SETTINGS, as shown in the following screenshot:
Figure 4.41: Routes
- Click on Add, and a new blade will be opened, asking you to specify the following:
- Route name: A name for the route.
- Address prefix: The destination IP address range in CIDR notation that this route applies to. If the destination address of a packet falls in this range, it matches this route.
- Next hop type: The next hop handles the matching packets for this route. It can be one of the following:
- Virtual Network: Traffic between different address ranges within an address spaces in a virtual network can be routed by selecting this type.
- Virtual Network Gateway: This type would be used when you have a site-to-site VPN connection and you want to customize the routes between your on-premises and Azure.
- Internet: This type of hops can be used when you want to customize the routes to the internet.
- Virtual Appliance: In case you have a virtual appliance which you are using to route traffic, you can select it as the next hop type and once the traffic get to the virtual appliance, it would take care of the routing process.
- None: This type would drop the traffic whenever it goes out from the subnet this route will be attached to.
- Next hop address: The IP address of the next hop. This can only be set when the next hop type is Virtual appliance:
Figure 4.42: Create a new route
- Once, the route is created, navigate to Subnets, which is located after Routes, as shown in the following screenshot:
Figure 4.43: The subnets to which the route is assigned blade
- Click on Associate to specify the subnet that will use this customized route to reach the virtual network specified during the route creation.
- First off, specify the Virtual network within which the subnet exists, as shown in the following screenshot:
Figure 4.44: Specify the virtual network within which the subnet exists
- Then, specify the Subnet, as shown in the following screenshot:
Figure 4.45: Specify the subnet that will be associated to the route
- Then, click on OK and the subnet will be associated. As a result, any VM with an IP address in the range of this subnet can reach out to any VM with an IP address in the virtual network specified in the route.