---
title: Deploying Traffic Manager in Azure Portal
slug: ps/help/en_us/vtm/cloudgs/deploying-traffic-manager-in-azure-portal
docTags: 
createdAt: 2026-08-02T08:48:57.990Z
---

Use the Azure Management portal to create a cluster of virtual machine instances based on the Traffic Manager template contained in the Azure marketplace.

1. On **Azure Marketplace** portal, search for **Ivanti Virtual Traffic Manager with WAF**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/c7RrFKAFkuq5tUYfjuxJD_marketplace.png" position="flex-start" size="80" width="1431" height="518" initialPath="images/marketplace.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/marketplace.png" showCaption="false" indent="1"}

2. Below image is displayed in results, select it for deployment.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/YHe9IQ8WhJ7cNhu7_hEGi_vtmvm.png" position="flex-start" size="55" width="547" height="844" initialPath="images/vtm_vm.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/vtm_vm.png" showCaption="false" indent="1"}

3. For instance select the **BYOL Edition** (under **Plans + Pricing**), however, you can choose from the other options listed below.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/pFEd-L36oDVsrKqTLZiSq_plans.png" position="flex-start" size="80" width="1428" height="1421" initialPath="images/plans.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/plans.png" showCaption="false" indent="1"}

4. Enter the **Resource Group**, **Virtual machine name**, **Region**, **Image** etc details.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/0vBRmXkPrVDJbhYtTcBdD_basicdetails.png" position="flex-start" size="80" width="1431" height="1284" initialPath="images/basic_details.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/basic_details.png" showCaption="false" indent="1"}

5. Scroll down and select machine size, **Authentication type** should be **SSH public key**, relevant inputs for the below fields can be given to generate a new key pair.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/bdzWzVXKvbJ3PCIQP3aXI_size.png" position="flex-start" size="80" width="1396" height="814" initialPath="images/size.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/size.png" showCaption="false" indent="1"}

:::hint{type="info"}
**Username** field is not used, login to the VTM Admin-UI or through ssh is being done using Administrator (admin) account.
:::

6. Select **Disk Management** as needed.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/5N3kkZSsagKn-Izvn3j3m_disk.png" position="flex-start" size="80" width="1763" height="1756" initialPath="images/disk.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/disk.png" showCaption="false" indent="1"}

7. Provide the networking info such as **Virtual network**, **Subnet**, **NSG** etc.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/3UiLWQdQo_jXy0i8fFcq5_networking.png" position="flex-start" size="80" width="1527" height="1791" initialPath="images/networking.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/networking.png" showCaption="false" indent="1"}

8. In **Management**, **Monitoring**, **Advanced**, **Tags** default values present can be retained, else if required, can be modified appropriately based on requirement.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/OTCO36vJfOOA_YIs8gIkC_management.png" position="flex-start" size="80" width="1441" height="719" initialPath="images/management.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/management.png" showCaption="false" indent="1"}

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/ah01BDybA-l9mPs6q3Iiv_monitoring.png" position="flex-start" size="80" width="1192" height="689" initialPath="images/monitoring.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/monitoring.png" showCaption="false" indent="1"}

9. Select Create option in the final **Review + Create** page

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/B170a9ohgiVyhp9UTFoiq_createvm.png" position="flex-start" size="61" width="610" height="864" initialPath="images/create_vm.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/create_vm.png" showCaption="false" indent="1"}

10. Download the **private key** generated to performing ssh login into the newly created VTM azure instance.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/nbi0XFIgPKeSPs59R2kB4_genprikey.png" position="flex-start" size="80" width="1842" height="858" initialPath="images/gen_prikey.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/gen_prikey.png" showCaption="false" indent="1"}

:::hint{type="info"}
When creating a 2 or more vTM’s to be the same Cluster, it is recommended to select the following parameters similar to the 1st vTM (1. Resource group, 2.SSH Public Key Source, 3. Virtual Network, 4. Network Security Group).
:::

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/2kJmg5KLatkR4MGWHH6Oq_basicvadc.png" position="flex-start" size="80" width="1202" height="477" initialPath="images/basic_vadc.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/basic_vadc.png" showCaption="false" indent="1"}

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/MV4NwTd8UTATjY6QZZ89o_adminaccount.png" position="flex-start" size="80" width="1401" height="580" initialPath="images/admin_account.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/admin_account.png" showCaption="false" indent="1"}

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/OyJw83Zw3NQPiQkpWL2os_createvm.png" position="flex-start" size="80" width="1407" height="1314" initialPath="images/createvm.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/createvm.png" showCaption="false" indent="1"}

## Creating a Traffic Manager HA Cluster in the Azure Portal

Use the Azure Management portal to create a cluster of virtual machine instances based on the Traffic Manager template contained in the Azure marketplace.

To create a Traffic Manager HA cluster using the Azure Management portal

1. Deploy a multiple vTM instances following the steps provided in [Deploying Traffic Manager in Azure Portal](docId\:G-2vxBWjsmVZl9sjVicsb)
2. Create an **Azure Load Balancer**. From the Azure Home page under **Azure Services**, select **Load balancers** and then click on **create**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/W-DwrpDYk6nlbNrN0uElm_azservices.png" position="flex-start" size="80" width="1103" height="313" initialPath="images/azservices.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/azservices.png" showCaption="false" indent="1"}

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/apYyMgQ5RmhJye8vnviUm_loadbal.png" position="flex-start" size="80" width="797" height="281" initialPath="images/loadbal.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/loadbal.png" showCaption="false" indent="1"}

3. Provide the **Resource Group** info same as the vTMs.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/RK3PvOElL2_WE486O0N9u_clusterbasic.png" position="flex-start" size="80" width="1222" height="983" initialPath="images/clusterbasic.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/clusterbasic.png" showCaption="false" indent="1"}

4. Create the **Front End IP configuration** as shown below.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/IaZ7V1GBNB79kb3904UnQ_loadbalcreate.png" position="flex-start" size="80" width="1232" height="765" initialPath="images/loadbalcreate.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/loadbalcreate.png" showCaption="false" indent="1"}

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/y4o97ISmlQRjevEaT6mXL_frontend.png" position="flex-start" size="80" width="911" height="1551" initialPath="images/frontend.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/frontend.png" showCaption="false" indent="1"}

5. Create the **Backend Pools** (In this case the nodes are vTM1 and vTM2).

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/rCXFy4REMLT264cldRdFA_backend.png" position="flex-start" size="80" width="1225" height="746" initialPath="images/backend.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/backend.png" showCaption="false" indent="1"}

6. Add the resources (the vTM’s as shown below).

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/N7G6ykXKAt6HxRVGtsCzD_backendpool.png" position="flex-start" size="80" width="1210" height="562" initialPath="images/backendpool.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/backendpool.png" showCaption="false" indent="1"}

7. Add the inbound NAT Rule as shown below. For the second vTM use the Frontend Port as 9091 (as it is already mapped the 9090 to vTM1) .

:::hint{type="info"}
Ensure to add the right names (example: AdminUI\_vTM1 for 9090 and AdminUI\_vTM2 for 9091, this helps to identify the purpose of the rule by the name).
:::

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/Bi3VwP0ZK9FjEd-F63mdF_inbound.png" position="flex-start" size="80" width="922" height="2000" initialPath="images/inbound.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/inbound.png" showCaption="false" indent="1"}

8. Proceed to add the outbound rules from the Azure portal and create the Load Balancer. The vTM is now available as a High Availability pair.
9. Add more configuration to the Azure LB as needed from the below location.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/Res-QpzJlM1iE3kefLxx__settings.png" position="flex-start" size="65" width="647" height="1294" initialPath="images/settings.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/settings.png" showCaption="false" indent="1"}

## Connecting to the Admin UI

1. After cluster is created, you will see the following resources showing in the overview of your Resource Group. As you see for this Cluster, the NSG (Network Security Group), the Virtual Network and the SSH Key are common to this Cluster).

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/ndUAayE6zww0Z34V7nJgh_resources.png" position="flex-start" size="80" width="1573" height="1037" initialPath="images/resources.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/resources.png" showCaption="false" indent="1"}

2. Click on virtual machine (in this case“1vTM” as shown below).

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/IrRr2ulLqWiU_Khuts98L_virtualm.png" position="flex-start" size="80" width="1126" height="117" initialPath="images/virtualm.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/virtualm.png" showCaption="false" indent="1"}

3. Scroll down to bottom left side of the page and click **Boot Diagnostics**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/AHJ-7xPN7oDjKi_9TBV5O_bootdia.png" position="flex-start" size="64" width="638" height="522" initialPath="images/bootdia.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/bootdia.png" showCaption="false" indent="1"}

4. In the next page, click on **Serial log** and then click on **Download serial log**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/RSVyybqSOKwgruehvfpjM_log.png" position="flex-start" size="80" width="1354" height="488" initialPath="images/log.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/log.png" showCaption="false" indent="1"}

5. This takes you to a new browser, here search for **password** using ctrl + f and as show in figure below. Use this password in the UI on prompt for the first time, change the password using Initial Configuration Wizard in the next section.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/SysW7YLyMq1J1pVJBvs57_cli.png" position="flex-start" size="80" width="1499" height="245" initialPath="images/cli.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/cli.png" showCaption="false" indent="1"}

6. Click on NSG.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/5RLf-BFLIn9GmuJOkW1IK_nsg.png" position="flex-start" size="80" width="934" height="661" initialPath="images/nsg.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/nsg.png" showCaption="false" indent="1"}

7. Add an inbound rule for Port 9090 as shown below.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/v6RFYnPm26TR7GK2-OCPw_inboundrule.png" position="flex-start" size="80" width="1514" height="405" initialPath="images/inbound_rule.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/inbound_rule.png" showCaption="false" indent="1"}

8. Go back to VM (vTM) **Overview** page and use the fully qualified public DNS name or public IP address for deployment on Web browser to access the Admin UI on one of Traffic Manager instances. For example, to access the Admin UI for the first instance in your cluster using the details shown in figure, enter the following **https\://Public IP address:9090**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/7HSG4WtGRHrccJccqJPOa_vmprop.png" position="flex-start" size="80" width="1649" height="528" initialPath="images/vmprop.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/vmprop.png" showCaption="false" indent="1"}

:::hint{type="info"}
If you are trying to connect to the deployed VTM Admin-UI for the first time and if you are facing error saying the instance is inaccessible, then restart the VTM instance.
:::

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/HoJJJZGXJRyI6FIAdvc1V_restart.png" position="flex-start" size="80" width="1671" height="600" initialPath="images/restart.png" githubPath="CloudGS/ps-vtm-cloud-gsg/images/restart.png" showCaption="false" indent="1"}

:::hint{type="info"}
REST API access is initially disabled in your instances. To enable REST access, configure your Traffic Manager instances and enable REST through the Admin UI. For more details, see the Virtual Traffic Manager: User’s Guide.
:::

To learn more about resource groups, see [https://azure.microsoft.com/en-gb/documentation/articles/resource-group-overview/](https://azure.microsoft.com/en-gb/documentation/articles/resource-group-overview/).

If your Traffic Manager instance has not yet been configured, first complete the Initial Configuration wizard. This wizard allows you to specify the initial time and security settings for your Traffic Manager. For more information, see [Using the Initial Configuration Wizard](docId\:Gkmq0sCpKxYDXQ3OfrHBe).