--- title: "Requirements to deploy Trellix Virtual IPS in Azure environment" slug: "requirements-to-deploy-trellix-virtual-ips-in-azure-environment-3" tags: ["Product Usage"] updated: 2026-11-19T12:29:31Z published: 2026-11-19T12:29:31Z canonical: "docs.trellix.com/requirements-to-deploy-trellix-virtual-ips-in-azure-environment-3" --- > ## 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. # Requirements to deploy Trellix Virtual IPS in Azure environment The following table lists the requirements to deploy vIPS in the Azure environment. | Requirement | Purpose | Role | | --- | --- | --- | | Azure GUI access | To launch Trellix vIPS and configure setup | Privilege: Contributor | | External Controller | To install External Controller | Privilege: Contributor | | Virtual IPS Sensor | To install Virtual IPS Sensor | Privilege: Contributor | | Web server (or) Virtual Machines to be protected | To install Virtual Probes | Privilege: OS Administrator | | IAM Role | To assign role permissions | Privilege: Owner | The following table lists the requirements of vIPS solution components for the deployment of Trellix vIPS in the Azure environment. | Component | Azure Virtual Machine Type | Software Requirements | Network Requirements | | --- | --- | --- | --- | | Trellix IPS Manager | D2s_v4 | Trellix IPS Manager image | 1 Network Interface (management subnet) | | External Controller | F4s_v2 | External Controller image | 1 Network Interface (management subnet) | | Virtual IPS Sensor | F4s_v2 | Virtual IPS Sensor image | 1 Network Interface for both management and data subnet | | Protected virtual machines | Any | Customer Supplied | 1 or more (see deployment) | The following table lists the ports for network security group settings required to deploy Trellix vIPS in the Azure environment. > [!WARNING] > Important > > For more information about ports and traffic destinations used by Trellix IPS, see [KB59342](https://support.trellix.com/s/article/KB59342). | | | Ports | Purpose | Source/Destination | | --- | --- | --- | --- | --- | | Manager | Inbound rules | 8501–8504, 8506–8510 | TCP ports used to install the Sensor, send alerts and packet captures to the Manager, and transfer files between them. | Sensor | | 9798 | TCP port used to communicate Probe state and configuration. This is applicable only when the local Controller is used. | Probe, Sensor | | 443 | TCP port used for: - Controllers to register with the Manager - Sensors and Probes to discover registered Controllers - Web UI access on the Manager | Sensor, Controller, Probe | | 22 | TCP port used for Manager CLI access (via SSH). | --- | | 3306 | TCP port used for database access by External Controllers to store and retrieve Probe data. This is applicable only when an External Controller is used. | Controller | | Outbound Rules | 443 | TCP port used: - To connect the Manager to the External Controller using private IP address - By the Local Controller to connect to the Azure portal | EC2 Endpoint | | 8500 | UDP port used by the Manager to make real-time configuration changes on the Sensor. | Sensor | | Local/External Controller | Inbound rules | 9798 | TCP port used to communicate Probe state and configuration. | Sensor, Probe | | 22 | TCP port used for Controller CLI access. | --- | | Outbound Rules | 443 | TCP port used for: - Connecting to the Azure portal | Manager, EC2 Endpoint | | 3306 | TCP port used for database access by External Controllers to store and retrieve Probe data. This is applicable only when an external Controller is used. | Manager | | Sensor | Inbound rules | 8500 | UDP port used by the Manager to make real-time configuration changes on the Sensor. | Manager | | 9797 | UDP port used by Probes to forward traffic to the Sensor for inspection. | Probe | | 22 | TCP port used for Sensor CLI access. | --- | | Outbound Rules | 8501-8504, 8506-8510 | TCP ports used to install the Sensor, send alerts and packet captures to the Manager, and transfer files between them. | Manager | | 443 | TCP port used to discover registered Controllers. | Manager | | 9798 | TCP port used to communicate Probe state and configuration. | Controller | | Probe | Inbound rules | No ports required for inbound. | --- | --- | | Outbound Rules | 9797 | UDP port used by the Probe to forward traffic to Sensors for inspection. | Sensor | | 443 | TCP port used to discover registered Controllers and Sensors. | Manager | | 9798 | TCP port used to communicate Probe state and configuration. | Controller | ![GUID-232831BE-B114-449B-A8F7-E37F2F24ED86-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a4291623-8cb6-1cb5-e6a6-cf8fc404f3cb(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A48Z&se=2026-11-20T16%3A24%3A48Z&sr=c&sp=r&sig=g5yDDAq9o5%2FUQZKDYTaL1%2Bm4UHvIp1EB727W0pM2o9k%3D)