Target Audience
- Independent software vendors (ISVs), service providers (SPs), small to medium enterprises (SMEs) and large enterprises
- Microsoft Azure administrators and Parallels RAS administrators familiar with virtual desktop infrastructure (VDI) environments
Requirements
- Access and subscription on the Azure portal
- Experience with Azure Active Directory and related modules.
Configuring Azure Application for virtual machines (VMs) listed in single Resource Group
1. Go to the Azure portal and open Azure Active Directory.
![](https://kb.parallels.com/Attachments/kcs-172499/image-20191120204010-1.jpeg)
2. Register a new app, which will then be used to establish communication between Azure and Parallels® Remote Application Server (RAS).
![](https://kb.parallels.com/Attachments/kcs-172499/2_new_registration.jpg)
3. Complete registration.
![](https://kb.parallels.com/Attachments/kcs-172499/3_register_app.jpg)
The following message indicates a successful registration:
Successfully created application Test VDI App (kb).
![](https://kb.parallels.com/Attachments/kcs-172499/4_success.jpg)
4. Tenant and Client IDs will be required for the Parallels RAS Console so it's better to save them to the server hosting the Parallels RAS Console. Once done, proceed to Certificates & secrets.
![](https://kb.parallels.com/Attachments/kcs-172499/5_copy_IDs.jpg)
5. Configure New Client Secret.
![](https://kb.parallels.com/Attachments/kcs-172499/6_new_client_secret.jpg)
6. Set expiration and click Add.
![](https://kb.parallels.com/Attachments/kcs-172499/6_new_client_secret_0.jpg)
7. Copy the secret as it will not be available after this page will be refreshed or reopened.
![](https://kb.parallels.com/Attachments/kcs-172499/6_new_client_secret_1.jpg)
8. Open Resource groups.
![](https://kb.parallels.com/Attachments/kcs-172499/7_resource_groups.jpg)
9. Create a new resource group or select the existing one and scroll down.
![](https://kb.parallels.com/Attachments/kcs-172499/8_create_group.jpg)
10. Specify Group parameters and click Preview & create.
![](https://kb.parallels.com/Attachments/kcs-172499/8_create_group_0.jpg)
11. Click Create.
![](https://kb.parallels.com/Attachments/kcs-172499/8_create_group_1.jpg)
The resource group should now be available.
![](https://kb.parallels.com/Attachments/kcs-172499/8_create_group_2.jpg)
Note: You might need to refresh this page in order to see the newly created resource group.
12. Click on the group name and then select Access Control (IAM).
![](https://kb.parallels.com/Attachments/kcs-172499/9_access_control.jpg)
13. Add Reader role to the application.
![](https://kb.parallels.com/Attachments/kcs-172499/12_add_role_assignment_reader.jpg)
14. Once the application is selected, click Save.
![](https://kb.parallels.com/Attachments/kcs-172499/13_save.jpg)
15. Add Contributor role to the application using the same approach.
![](https://kb.parallels.com/Attachments/kcs-172499/10_add_role_assignment_contributor.jpg)
16. The following message indicates success:
Test VDI App (kb) was added as Contributor for Test_VDI_Group.
![](https://kb.parallels.com/Attachments/kcs-172499/11_success.jpg)
Listing all resource groups under specific subscription
1. Open subscriptions from the Menu pane > All Services > Subscriptions or simply find it in search:
![](https://kb.parallels.com/Attachments/kcs-172499/14_subscriptions.jpg)
2. Choose the subscription that is currently active.
![](https://kb.parallels.com/Attachments/kcs-172499/15_choose_subscription.jpg)
3. Copy the Subscription ID to the server hosting the Parallels RAS Console and open IAM afterward.
![](https://kb.parallels.com/Attachments/kcs-172499/16_copy_subscription_ID.jpg)
4. Add Reader role to this subscription:
![](https://kb.parallels.com/Attachments/kcs-172499/17_add_role_assignment_reader_to_subscription.jpg)
Adding Azure VDI provider in the Parallels RAS Console
1. From Parallels RAS Console > Farm > Providers > click + or Tasks > Add. (click on the image to enlarge)
2. Select Microsoft Azure from the list of available providers.
![](https://kb.parallels.com/Attachments/kcs-172499/Azure.jpg)
3. Input Name, Tenant ID, Subscription ID, Application ID, and Application Key (Client Secret) and click Next.
Note: Advanced Settings in this window allow setting up Dedicated VDI Agent and Preferred Publishing Agent right away.
4. On the next window, verify that VDI Agent is installed and the agent status is OK. Then click Finish.
The VDI host is now added. Some time is needed for agents to synchronize settings.
![](https://kb.parallels.com/Attachments/kcs-172499/5_sync.jpg)
Depending on the environmental conditions, this may take about a few minutes. Once complete, you will see the status OK (green).
![](https://kb.parallels.com/Attachments/kcs-172499/6_OK.jpg)
Was this article helpful?
Tell us how we can improve it.