--- title: "Deploying virtual Network Security appliances in Azure in inline mode" slug: "deploying-virtual-network-security-appliances-in-azure-in-inline-mode" tags: ["Endpoint Security (HX)", "Product Usage"] updated: 2026-09-09T22:45:38Z published: 2026-09-09T22:45:38Z canonical: "docs.trellix.com/deploying-virtual-network-security-appliances-in-azure-in-inline-mode" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Deploying virtual Network Security appliances in Azure in inline mode This topic describes how to deploy a virtual Network Security appliance in inline mode. ### Note This procedure assumes that the interface pair is configured in inline mode on the Network Security appliance. IP forwarding must be enabled on each monitoring interface from the Azure portal. This disables source and destination checks and ensures that all network traffic reaches the appliance. To enable IP forwarding: 1. Select **Home** > **Virtual Machines**. 2. Select the Network Security virtual machine. 3. Select **Networking** under **Settings** and then select an interface. 4. Select **IP configurations**. 5. Select **Enabled** under **IP forwarding settings**. 6. Repeat these steps for each interface. ### Configuring IP routing In a typical Network Security inline deployment, port pair A is the inline port pair. The pether3 monitoring interface is connected to the subnet that hosts the on-premises enterprise clients (the client subnet) and the pether4 monitoring interface is connected to a subnet that hosts the Network Security appliance (the server subnet). The following example addresses are used in this section: - Client subnet—**10.100.1.64/27** - Network Security pether3 interface—**10.100.1.69** - Server subnet—**10.100.1.96/27** - Network Security pether4 interface—**10.100.1.100** Azure routes traffic from one subnet to another based on a route in each subnet's route table. You must add a table and route for each subnet. ### Note The following procedures describe how to configure IP routing for the subnets connected to the interfaces in port pair A. Repeat the procedures for each applicable port pair. ###### Adding a route table and route for the client subnet This procedure shows how to add a route that sends traffic from the client subnet to the Network Security appliance. To add the route table and route: 1. Select **All services**, and then select **Route tables** under **Networking**. ![Azure_add_route_table.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-e45a6d7d-153f-36ec-ed3a-1b7af27af706.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A16%3A38Z&se=2026-11-20T11%3A16%3A38Z&sr=c&sp=r&sig=Hhd5MfyFjMMrOIpxnaFwEXlYeR8mDzKEQKTyptmu4S8%3D) 2. Click **Add**. 3. Enter a meaningful **Name** for the route table. 4. Make sure the correct **Subscription**, **Resource group**, and **Location** are selected. 5. Click **Create**. 6. Click the new route table. 7. Select **Routes** under **Settings**. The **Routes** page opens. ![Azure_add_route.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-6a610187-7af8-1107-4a01-9b655b555453.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A16%3A38Z&se=2026-11-20T11%3A16%3A38Z&sr=c&sp=r&sig=Hhd5MfyFjMMrOIpxnaFwEXlYeR8mDzKEQKTyptmu4S8%3D) 8. Click **Add**. 9. On the **Add route** page: 1. Enter a meaningful **Route name**. 2. For **Address prefix**, enter the IP address and network prefix for the destination subnet (the Network Security appliance subnet). 3. Select **Virtual appliance** as the **Next hop type**. 4. Enter the IP address of the Network Security pether3 interface as the **Next hop address**. 5. Click **OK**. ###### Example The following example shows the route table for the client subnet. ![Azure_s3_route_table.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-cdec4347-6c8f-0fa4-dc87-d41b7e063e52.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A16%3A38Z&se=2026-11-20T11%3A16%3A38Z&sr=c&sp=r&sig=Hhd5MfyFjMMrOIpxnaFwEXlYeR8mDzKEQKTyptmu4S8%3D) ###### Adding a route table and route for the server subnet This procedure shows how to add a route that sends traffic from the Network Security appliance to the client subnet. To add the route table and route: 1. Select **All services**, and then select **Route tables** under **Networking**. 2. Click **Add**. 3. Enter a meaningful **Name** for the route table. 4. Make sure the correct **Subscription**, **Resource group**, and **Location** are selected. 5. Click **Create**. 6. Click the new route table. 7. Select **Routes** under **Settings**. 8. Click **Add**. 9. On the **Add route** page: 1. Enter a meaningful **Route name**. 2. For **Address prefix**, enter the IP address and network prefix for the destination subnet (the client subnet). 3. Select **Virtual appliance** as the **Next hop type**. 4. Enter the IP address of the Network Security pether4 interface as the **Next hop address**. 5. Click **OK**. ###### Example The following example shows the route table for the server subnet. ![Azure_s4_route_table.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-4f572cc2-a0c9-8e6c-aa37-81c2345c6dcc.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A16%3A38Z&se=2026-11-20T11%3A16%3A38Z&sr=c&sp=r&sig=Hhd5MfyFjMMrOIpxnaFwEXlYeR8mDzKEQKTyptmu4S8%3D):