About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Use the browser-based Remote Desktop web client when staff mainly need to open published desktops or apps from everyday PCs without installing software, and when your pilot proves the workflow works on the browsers you actually allow. Use the native Remote Desktop client (Windows, macOS, iOS, Android per vendor text) when you depend on client-side features, tighter integration with the local device, or behaviour that the web channel does not expose in your tests.
Microsoft states that users reach session-based apps and desktops on an RD Session Host through Remote Desktop clients or “through a supported browser by using the web client.” Remote Desktop Web Access can present a portal and launch resources through the device’s native Microsoft Remote Desktop client application—which means your delivery path can mix browser discovery with native launch unless you standardise on one channel.
Why it matters
The client channel shapes help-desk load, update policy, and what staff assume “remote access” can do. Browser access reduces friction for contractors and locked-down PCs; native clients matter when power users expect multi-monitor layout, predictable keyboard shortcuts, or peripherals that web sessions handle differently. Choosing the wrong default produces tickets that look like application faults but are really access-shape mismatches.
How it works
At a high level, the RD Session Host runs the application; the client only presents the session. The Connection Broker “handles connections to both collections of full desktops and collections of remote apps” and, if a session disconnects, “will reconnect the user to the correct RD Session Host server and their interrupted session.” The web client still terminates on a session host—the difference is which protocol stack and device integration you get at the edge.
RD Web Access sits behind HTTPS (TCP 443 when deployed, per Microsoft’s port guidance). RD Gateway can encrypt internet paths without a VPN. Those roles affect how users reach the client choice, not which client wins for a given workflow.
Microsoft’s Remote Desktop web client documentation (page dated 2025-05-06) states that you need a PC running Windows, macOS, ChromeOS, or Linux; mobile devices aren’t supported at this time. Supported browsers include Microsoft Edge, Google Chrome, Apple Safari, and Mozilla Firefox (v55.0 and later). Plan phone and tablet staff on the native clients for those platforms, not the web client.
Labelled example — accounts payable clerk: Starts in the web client from a shared office PC to post invoices. Labelled example — production planner: Uses the native Windows client on a dual-monitor desktop with heavy copy/paste between Excel and the hosted ERP tile.
What to choose and why
| Situation | Lean towards |
|---|---|
| Casual access, no install rights, short tasks | Web client after browser pilot on an allowed desktop browser |
| Daily power use, multiple monitors, local shortcuts | Native client |
| Mix of RemoteApp and full desktop in one day | Native client unless web pilot passes every task |
| Personal BYOD phone or tablet | Native client from the vendor store; web client is not for mobile devices |
Run a single-workflow pilot on both channels: same user, same LOB tasks, same printer and file-save paths you expect in production. Record which steps fail only in the browser. Microsoft’s role text does not certify parity for every peripheral; treat gaps as design facts, not surprises in go-live week.
Read next
Related articles you may want next.
- HostingWhat "works in a browser" really means for Windows line-of-business softwareUnderstand what browser access means for Windows business software, then check supported devices, clipboard limits and the workflows your staff need.Read article
- HostingMultiple monitors and display scaling for remote business softwareChoose remote display settings using the correct client support table, then test monitor layouts, scaling and everyday application tasks on your staff’s devices.Read article
- HostingPrinting from hosted applications: staff expectations and design choicesPlan printing from hosted applications by matching each critical process to a supported printer path and testing the output staff actually need.Read article
Risks and limits
The web client documentation describes clipboard, printing, and file-transfer behaviour that differs from native clients; treat peripheral-heavy workflows as pilot items. No steps in this article were executed in a lab; collection or client deployment guidance is untested here.
A hosting provider may offer both channels; confirm in contract and design review which client paths and features are in scope for your environment.
Sources
- Remote Desktop Services roles — accessed 2026-11-16; ms.date 2024-07-03. Web and native client paths; Broker reconnect; Web Access native launch.
- Deploy the Remote Desktop Gateway role — accessed 2026-11-16; ms.date 2025-06-24. Internet access without VPN framing.
- Ports used by RDS — accessed 2026-11-16. HTTPS port context for RD Web.
- Get started with the web client for Remote Desktop Services — accessed 2026-11-16; ms.date 2025-05-06. Mobile exclusion and supported browsers.
Related reading
- Printing from hosted applications: staff expectations and design choices
- What “works in a browser” really means for Windows line-of-business software
- Multiple monitors and display scaling for remote business software
- Business solutions (NetLeverage service context)
Learning notes
- Browser and native are presentation channels to the same session host workloads, not different products.
- RD Web Access may hand off to a native client even when staff “start in the browser.”
- Broker reconnect applies to disconnected sessions regardless of client type—if the session still exists on the farm.
- Pilot one real workflow, not only “can I see the login screen?”
- The web client excludes mobile devices; unsupported browser claims are a procurement risk—test the browsers you allow.
This article was originally published on .