Azure Virtual Desktop Call redirection for Dialpad

Question

As we are currently working on the support of Call redirection for Azure Virtual Desktop for Dialpad, we would like to get our domain whitelisted so it's easier for our common customers to deploy Dialpad on Azure Virtual Desktop, and they experience the best media quality.

Answer 1

Hello Arnaud Budkiewicz,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

Problem

Sequel to your questions, I understand that you would like to integrate Dialpad with Azure Virtual Desktop and aims to streamline the deployment process for common customers. Also seek to have your domain whitelisted to ensure optimal media quality during calls. The challenge lies in navigating the process of getting the domain whitelisted and ensuring a smooth integration between Dialpad and Azure Virtual Desktop.

Scenario

Arnaud Budkiewicz was tasked with integrating Dialpad with Azure Virtual Desktop to enhance the communication experience for their customers. As part of this integration, He needs to ensure that Dialpad functions seamlessly within the Azure Virtual Desktop environment, including support for Call redirection. Additionally, he wants to simplify the deployment process for common customers by having Dialpad's domain whitelisted on Azure Virtual Desktop.

Solution

This prescribed solution was based on the scenario given and your questions, while focusing on the problem statement. I will break down the answer into three categories.

1. Enable SAML in your Dialpad and Configure SAML in Azure Portal. Use the links to be able to see full detailed configurations you will need to do at first stage: https://help.dialpad.com/docs/integrating-azure-saml-with-dialpad
2. Whitelist Required FQDNs and Endpoints. Use the links to be able to see full detailed configurations you will need to do at second stage: https://learn.microsoft.com/en-us/azure/virtual-desktop/required-fqdn-endpoint If you will use firewall use this link: https://learn.microsoft.com/en-us/azure/firewall/protect-azure-virtual-desktop and if you would preferred to use proxy use this link for more details: https://learn.microsoft.com/en-us/azure/virtual-desktop/proxy-server-support
3. Validate, Update and Sync your configurations. Use Azure Virtual Desktop Agent URL Tool to validate whether your session hosts can access each required FQDN and endpoint, If any are inaccessible, the tool will list them so you can unblock them. For more details on how to do this follow this link: https://learn.microsoft.com/en-us/azure/virtual-desktop/check-access-validate-required-fqdn-endpoint. Also, If you're using Azure-provided DNS, the appropriate DNS suffix will be automatically applied to your virtual machines. For other DNS options, ensure to use FQDNs or manually apply the appropriate DNS suffix or use this link for more details: https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.

Finally

To Sync Azure AD with Dialpad. With Azure integration, Microsoft admins can configure their AD to automatically provision or de-provision users to and from Dialpad. This can be set up directly from the AD marketplace, you can use this link for more configuration details:

https://dialpad.com/app-marketplace/azure/

References

All the links above.

Accept Answer

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

** Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful ** so that others in the community facing similar issues can easily find the solution.

Best Regards,

Sina Salam NR