Introduction
In cloud networking, routing plays a vital role in ensuring that traffic between subnets, virtual networks, and external networks is directed efficiently and securely. Within Microsoft Azure, custom route tables allow administrators to control how traffic flows in and out of subnets, providing flexibility beyond the default system routing. This project focuses on configuring network routing in Azure by creating and associating a custom route table with subnets, and defining specific routes for traffic management. By completing this project, you will gain practical knowledge of how routing works in Azure and how to customize it to meet application or organizational requirements.
Tasks to Cover
- Create a Route Table – Set up a custom route table that will manage routing rules within the virtual network.
- Add the Route Table – Ensure the route table is properly integrated into the Azure environment.
- Associate the Route Table to the Subnets – Link the created route table to one or more subnets so that its rules apply to traffic within those subnets.
- Create a Route in the Route Table – Define a custom route that controls how specific traffic is directed, ensuring traffic flows as intended.
Step 1 Create a Route Table
Azure automatically creates a route table for each subnet within an Azure virtual network. The route table includes the default system routes. You can create route tables and routes to override Azure’s default system routes.
Record the private IP address of app-vnet-firewall
- In the search box at the top of the portal, enter Firewall. Select Firewall in the search results.
- Select app-vnet-firewall.
- Select Overview and record the Private IP address.
Step 2 Add the route table
- In the search box, enter Route tables. When Route table appears in the search results, select it.
- In the Route table page, select + Create and create the route table.
Complete the following configuration
- Subscription: Select your subscription
- Resource group: RG1
- Region: East US
- Name: app-vnet-firewall-rt
- Select Review + create
- Select Create.
- Wait for the route table to deploy, then select Go to resource.
Step 3 Associate the route table to the subnets
- In the portal, continue working with the route table, select app-vnet-firewall-rt.
- In the Settings blade, select Subnets and then + Associate.
Configure an association to the frontend subnet, then select OK.
Virtual network: app-vnet (RG1)
Subnet: frontend
- Configure an association to the backend subnet, then select OK.
- Virtual network: app-vnet (RG1)
- Subnet: backend
- The Frontend and the Backend subnets as been associated to the route table.
Step 4 Create a route in the route table
- In the portal, continue working with the route table, select app-vnet-firewall-rt.
In the Settings blade, select Routes and then + Add.
Configure the route, then select Add.
Route name outbound-firewall
Destination type IP addresses
Destination IP addresses/CIDR range 0.0.0.0/0
Next hop type Virtual appliance
Next hop address: private IP address of the firewall (10.0.2.4)
- Route was created successfully in the route table
Conclusion
By completing this project, a custom route table has been successfully created, associated, and configured within Azure. These steps ensure greater control over traffic flow in the virtual network, enabling administrators to optimize performance, enforce security, and implement custom networking requirements. This exercise demonstrates the practical application of Azure’s routing capabilities and establishes a foundation for more advanced network designs.
Top comments (0)