How to Use the Remote Desktop Web Client: URLs and Login

What Is the Remote Desktop Web Client?

The Remote Desktop web client is Microsoft's browser-based client for the Remote Desktop Protocol (RDP). You open a URL, sign in, and pick a desktop or app your administrator published, and the session runs in a browser tab with nothing installed on the computer in front of you.

Microsoft's Windows App overview lists Azure Virtual Desktop, Windows 365, and Microsoft Dev Box as reachable from a web browser, and Remote Desktop Services and remote PCs as not reachable there.

Which browser client you use therefore depends on where your organization hosts its desktops:

Windows App sign-in needs a work or school account from your administrator. The same overview states that a personal Microsoft account can't sign in.

Remote Desktop Web Client URLs

Use the exact address your administrator sends you. Each deployment type follows one of these patterns, taken from Microsoft's Azure Virtual Desktop client guide and its RDS web client setup guide.

A bookmark to the retired Azure address still lands in the right place. In a check run for this guide in October 2026 on TestMu AI's cloud, Chrome 154 on Windows 11 and Chrome 149 on a real Pixel 6 from the real device cloud both followed it to Windows App before reaching Microsoft's sign-in page. This is the console output of that run:

[Chrome 154, Windows 11]
client.wvd.microsoft.com/arm/webclient/
  -> client.wvd.microsoft.com/arm/webclient/index.html
  -> windows.cloud.microsoft/?navFrom=avdweb&navType=auto
  -> login.microsoftonline.com/common/oauth2/v2.0/authorize
  title: "Sign in to your account"
windows.cloud.microsoft/
  -> login.microsoftonline.com/common/oauth2/v2.0/authorize
  title: "Sign in to your account"
[Chrome 149, real Pixel 6]
client.wvd.microsoft.com/arm/webclient/
  -> client.wvd.microsoft.com/arm/webclient/index.html
  -> windows.cloud.microsoft/?navFrom=avdweb&navType=auto
  -> login.microsoftonline.com/common/oauth2/v2.0/authorize
  title: "Sign in to your account"
windows.cloud.microsoft/
  -> login.microsoftonline.com/common/oauth2/v2.0/authorize
  title: "Sign in to your account"

The old index page does the forwarding in the browser, with navFrom=avdweb in the query string, so an HTTP check that follows redirects stops at a 200 response for that index page and misses the move. The phone reached the same sign-in page with no warning, even though Microsoft's documentation lists mobile browsers as unsupported.

How to Use the Remote Desktop Web Client

The steps below follow Microsoft's RDS web client guide. Windows App in a browser runs the same flow, per the Azure Virtual Desktop client guide, with a Microsoft Entra work account in place of a domain user name.

Requirements and Limitations

Microsoft's Azure Virtual Desktop client guide lists these browsers for the web client, and the Windows App documentation repeats the same table. The RDS web client guide names the same four browsers, with Firefox supported from version 55.

• Recent browsers only - since June 15, 2025, Microsoft supports browser versions no more than 12 months old, with the AVC video codec and WebGL enabled. A what is my browser check shows the version you are running.
• Computers only - mobile browsers and Internet Explorer are unsupported, so phones and tablets need the Windows App mobile app.

Remote Desktop Web Client vs the Desktop App

The installed client is now Windows App. The Microsoft Store version of the older Remote Desktop app reached end of support in September 2025, per the Azure Virtual Desktop client guide.

Microsoft's Windows App feature comparison shows what the browser gives up:

Use the browser for occasional access from a computer you don't control, and the installed Windows App for daily work, multi-monitor setups, Teams calls, or smart card sign-in.

Austin Siewert

Co-Founder, Steadfast Systems

Discovered @TestMu AI yesterday. Best browser testing tool I've found for my use case. Great pricing model for the limited testing I do 👏

3M+ Devs and QAs rely on TestMu AI

Deliver immersive digital experiences with Next-Generation Mobile Apps and Cross Browser Testing Cloud

Sign up with googleSign up with Email

How to Set Up the Remote Desktop Web Client on RDS

An administrator publishes the RDS web client from the RD Web Access server with Microsoft's RDWebClientManagement PowerShell module. The RDS web client setup guide lists these prerequisites:

• An RD Gateway, an RD Connection Broker, and RD Web Access running on Windows Server 2016 or 2019.
• Per-user client access licenses (CALs) rather than per-device CALs; with per-device CALs, all licenses are consumed.
• Publicly trusted certificates on the RD Gateway and RD Web Access roles.
• The KB4025334 update on the RD Gateway, which later cumulative updates might already include.
• Session hosts running Windows 10 or later, or Windows Server 2016 or later.

Then run Microsoft's documented sequence in an elevated PowerShell prompt on the RD Web Access server. These commands are quoted from that guide and were not run for this article, because they need a live RDS deployment:

# Windows Server 2016 only: update PowerShellGet, then restart PowerShell
Install-Module -Name PowerShellGet -Force

Install-Module -Name RDWebClientManagement
Install-RDWebClientPackage
Import-RDWebClientBrokerCert <.cer file path>
Publish-RDWebClientPackage -Type Production -Latest

Import-RDWebClientBrokerCert takes the RD Connection Broker certificate, exported as a .cer file and copied to the RD Web Access server. Rerun it whenever that certificate is renewed, or users get an "unexpected server authentication certificate was received" error. To trial a new client version first, publish it with -Type Test, which serves it at /RDWeb/webclient-test/index.html.

How to Fix Remote Desktop Web Client Connection Errors

Match the symptom to its cause before calling IT. The causes and fixes come from the RDS web client setup guide and the Azure Virtual Desktop client guide:

For anything else on RDS, the web client can record its own console log: open the ellipsis menu, go to About, select Start recording under Capture support information, reproduce the problem, and select Stop recording. The browser downloads RD Console Logs.txt for your administrator.

Remote Desktops for Cross-Browser Testing

If you open a remote desktop only to check a site in a browser you don't have locally, such as Safari on a Mac from a Windows laptop, a testing cloud saves you the VM upkeep. TestMu AI's Real-Time Testing launches real desktop browsers on cloud Windows and macOS virtual machines from a web dashboard, across 3,000+ browser and OS combinations, with Chrome or Firefox DevTools, screenshots, session recording, and Mark as Bug to trackers such as Jira.

Its LT Tunnel routes the cloud browser to a staging build that only exists on your network, and the local website testing tutorial walks through that setup with Selenium. For Safari specifically, see Safari browser for Windows, and the cross-browser testing guide covers choosing the browser matrix. Real-Time Testing tests websites and apps; it does not open your organization's published desktops.

Note: Need Safari on a Mac from a Windows laptop? Start a Real-Time Testing session on a cloud macOS machine and log bugs to Jira from the same tab. Try TestMu AI free

Can AI Agents Use the Remote Desktop Web Client?

Yes, but only by looking at the screen. The web client needs WebGL and the AVC video codec, per Microsoft's Azure Virtual Desktop client guide, so a computer-use agent sees the remote desktop as pixels and has to screenshot, locate, click, and type the way a person does.

• No accessibility tree inside the session - WebGL draws inside an HTML canvas element, per MDN's WebGL reference, so the agent can't query the remote app's buttons and fields by role or name and has to find them in each screenshot.
• Sign-in needs a person - Windows App sign-in runs through Microsoft Entra ID with your organization's MFA and Conditional Access rules, so an agent usually drives a session that a person already opened.
• Clicks move with the window size - Microsoft's feature comparison describes dynamic resolution, where the remote desktop resizes to fit the browser window, so a coordinate recorded before a resize can land on a different element afterward.
• Each step waits on the network - the browser client can't use RDP Shortpath's UDP transport, so on a slow link, have the agent act only after a fresh screenshot confirms the previous step took effect.

When the app an agent needs is a web app, skip the remote desktop and give the agent a browser it can read. TestMu AI's Browser Cloud runs real Chrome sessions that agents drive through Playwright, Puppeteer, or Selenium, and its testmu-browser-agent CLI works from the page's accessibility tree with stable element references instead of screen coordinates. Every session records video plus console and network logs, and the guide to browser infrastructure for AI agents covers the setup.

Conclusion

Open the Remote Desktop web client URL that matches your deployment from the table above, in a desktop browser no more than 12 months old, and sign in with the account your administrator issued. If you only needed a remote desktop to check a site in another browser, start a Real-Time Testing session on TestMu AI with the desktop browser real-time testing guide.

Testing web or mobile apps without writing code? KaneAI by TestMu AI turns plain-English instructions into tests.

To run your first test, start free, or

book a demo

for a full walkthrough of the product.