Create a VM

Each VM that will host a Verint MS Teams Recording Bot Adapter needs to have a public IP address in Azure (ILPIP) and a CNAME record. The CNAME record belongs to the domain of your Microsoft tenant that is pointing to this public IP address. When a virtual machine is created, one Network Security Group (firewall) is automatically created and attached to the VM. You need to open the required ports on this Network Security Group.

Before you begin 

• Create a virtual network with subnets

• Minimum Azure role: Virtual Machine Contributor

Procedure 

1. Open the Azure management portal at https://portal.azure.com.

2. Go to Home > Virtual Machines,

3. Select Add.

4. On the Basics tab, enter the Project Details. The starred items are required.

   • Select the Subscription.

   • Select a Resource Group.

   

5. On the Basics tab, enter the Instance Details. The starred items are required.

   1. Enter the Virtual Machine name.

   2. Select a Region. Use the nearest region to the location of the Microsoft Teams tenant.

   3. For Image, select a Windows Server image, 2012 R2 or above.

   4. Select the Size. Follow our sizing guide:

      • Standard_DS3_v2 - 150 channels

      • Standard_DS4_v2 - 300 channels

      • Standard_DS5_v2 - 600 channels

6. On the Basics tab, enter the details for the Administrator account.

   1. Enter the Username.

   2. Enter the Password.

   3. To Confirm password, reenter the password.

7. On the Basics tab, under Inbound port rules, allow the ports that are listed in Firewall ports.

   

8. On the Basics tab, under Save money, select a suitable Server license option.

9. On the Disks tab, configure disks as needed, according to the disk requirements in the Recorder Configuration and Administration Guide.

10. On the Networking tab, complete the settings as required:

    1. Create a new Virtual network or use an existing resource group VNet.

       If you are using an Application Gateway, make sure you select the Virtual Network and Subnet you have already created.

    2. Select a Subnet as needed.

    3. If no public load balancers are created for the deployment, make sure that a static Public IP is created for the instance.

       

11. Select Review + create.

12. Select Create.

    It takes a couple of minutes for Azure to prepare the new VM.

13. When the VM is deployed, select Go to resource.

    

14. Configure the DNS name for the VM.

15. Add a DNS name label and select Save.

What to do next 

Configure the VM network interface

Related topics 

Firewall ports