Reading Time: 3 minutes

As you may know, accessing the Azure Virtual Desktop HTML5 client using its non-memorable public endpoint address ( can be a hassle. However, were you aware that there exists a method to utilize your personal custom domain name for accessing the service?

Back in 2020, Tom Hickling, Senior PM for Azure Virtual Desktop at Microsoft, blogged about a complex method that involves using a combination of Azure tools and services, such as Azure Front Door, to achieve this. While this approach offers the benefit of a memorable and custom domain name, it can be time-consuming and comes with additional costs.

Here are some pros and cons:


  • Resolve Azure Virtual Desktop service using a memorable and custom domain name.


  • Too complex to implement.
  • Somehow time-consuming.
  • Involves additional cost, in case Azure Front Door is preferred.

But what if I told you there’s an easier and more cost-effective solution?

Introducing Azure Static Apps

With this service, you can quickly and easily deploy a static website that redirects to another website, in our case that would be the Azure Virtual Desktop HTML5 client. In general, Azure Static Web Apps is a service that automatically builds and deploys full-stack web apps to Azure from a code repository.

Here’s how the AVD HTTP redirection works:

  • The client queries the custom domain name
  • The DNS request is resolved and the CNAME record is returned to the client.
  • The client connects to the Azure Static Website.
  • Azure Static Web App redirects the client to AVD public endpoint address.

The following HTTP code does the trick. A very simple HTTP redirection is configured

<!DOCTYPE html>
  <meta http-equiv="refresh" content="0; url=''">
  <p> You are being transferred to Azure Virtual Desktop Service<a href=""></a>.</p>


Before deploying the Azure Static Web App, make sure you complete the following steps:

  1. Create a GitHub account (if you don’t have one already).
  2. Import/clone the public GitHub repository george-markou/avdurlredirect into a new one GitHub Repo. Attention, do not fork, I repeat, do not fork 😀
  3. Optional, create a Personal Access Token (PAT) to automate the provisioning of the Azure Static Web App.

Deploy Azure Static Web App

Once you’ve completed the prerequisites, it’s time to deploy the Azure Static Website:

  1. Navigate to Azure Marketplace, search for Static Web App, and create a new one.
  2. Fill in the required parameters, such as name, plan type, region, and source (GitHub).
  3. Authenticate using your GitHub account.
  4. Choose the newly imported repository from the drop-down menu.
  5. After the deployment is complete, navigate to the newly created Static Web App.
  6. On the overview blade, choose “Edit workflow”.
  7. Click on the edit button to edit the workflow yaml file within your repository.
  8. Change the parameter in line 30 to “/src” instead of “/”.
  9. Hit “Start commit”. After a few seconds, a GitHub Action will be triggered, pushing the code to the newly created Static Web App.
  10. Return to the Azure Portal, choose “Custom domain” from the resource menu, and click on “Add” to configure your custom domain.
  11. Add the required CNAME record on your public dns zone, pointing to the hostname of the newly deployed Azure Static Web App.
  12. Verify that the DNS record has been configured correctly.

Verify that the DNS record has been configured properly.

In conclusion, this solution offers a streamlined and cost-effective way to enhance your experience when accessing Azure Virtual Desktop using a custom domain name. While the traditional method involving Azure Front Door can be complex, time-consuming, and incur additional costs, the introduction of Azure Static Apps presents a more straightforward alternative.

Forgot to mention, give it a whirl 👉

Let me know what you think or how can this module can become better in the comments down below.

Thanks for reading my blog!