- Article
- 02/17/2022
- 2 minutes to read
Important
This content applies to Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects. If you're using Azure Virtual Desktop [classic] without Azure Resource Manager objects, see this article.
The web client lets you access your Azure Virtual Desktop resources from a web browser without the lengthy installation process.
Note
The web client doesn't currently have mobile OS support.
Supported operating systems and browsers
Important
As of September 30, 2021, the Azure Virtual Desktop web client no longer supports Internet Explorer. We recommend that you use Microsoft Edge to connect to the web client instead. For more information, see our blog post.
While any HTML5-capable browser should work, we officially support the following operating systems and browsers:
| Microsoft Edge | Windows, macOS, Linux, Chrome OS | Version 79 or later |
| Apple Safari | macOS | Version 11 or later |
| Mozilla Firefox | Windows, macOS, Linux | Version 55 or later |
| Google Chrome | Windows, macOS, Linux, Chrome OS | Version 57 or later |
Access remote resources feed
In a browser, navigate to the Azure Resource Manager-integrated version of the Azure Virtual Desktop web client at //rdweb.wvd.microsoft.com/arm/webclient and sign in with your user account.
Note
If you've already signed in with a different Azure Active Directory account than the one you want to use for Azure Virtual Desktop, you should either sign out or use a private browser window.
After signing in, you should now see a list of resources. You can launch resources by selecting them like you would a normal app in the All Resources tab.
Next steps
To learn more about how to use the web client, check out Get started with the Web client.
- Article
- 11/30/2021
- 2 minutes to read
Applies to: Windows 10.
You can access Azure Virtual Desktop resources on devices with Windows 10.
Install the Microsoft Store client
You can install the client for the current user, which doesn't require admin rights. Alternatively, your admin can install and configure the client so that all users on the device can access it.
Once installed, the client can be launched from the Start menu by searching for Remote Desktop.
To get started, download and install the client from the Microsoft Store.
Subscribe to the workspace provided by your admin to get the list of managed resources you can access on your PC.
To subscribe to a workspace:
In the Connection Center screen, tap +Add, then tap Workspaces.
Enter the Workspace URL into the Workspace URL field provided by your admin. The workspace URL can be either a URL or an email address.
- If you're using a Workspace URL, use the URL your admin gave you.
- If you're connecting from Azure Virtual Desktop, use one of the following URLs depending on which version of the service you're using:
- Azure Virtual Desktop [classic]: //rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx.
- Azure Virtual Desktop: //rdweb.wvd.microsoft.com/api/arm/feeddiscovery.
Tap Subscribe.
Provide your credentials when prompted.
After subscribing, the workspaces should be displayed in the Connection Center.
Workspaces may be added, changed, or removed based on changes made by your administrator.
Next steps
To learn more about how to use the Microsoft Store client, check out Get started with the Microsoft Store client.
- Article
- 12/23/2021
- 3 minutes to read
Applies to: Windows Server 2022, Windows Server 2019, Windows 11, Windows 10, and Windows 7
This topic has additional information about the Windows Desktop client that admins will find useful. For basic usage information, see Get started with the Windows Desktop client.
Installation options
Although your users can install the client directly after downloading it, if you're deploying to multiple devices, you may want to also deploy the client to them through other means. Deploying using group policies or the Microsoft Endpoint Configuration Manager lets you run the installer silently using a command line. Run the following commands to deploy the client per-device or per-user.
Per-device installation
msiexec.exe /I /qn ALLUSERS=1Per-user installation
msiexec.exe /i `` /qn ALLUSERS=2 MSIINSTALLPERUSER=1Configuration options
This section describes the new configuration options for this client.
Microsoft releases new versions of the client on a regular basis. You should always use the latest supported version of the client, so it's important that you configure your update policies to tell you when updates are ready. This section will show you how to configure your policies to enable or disable update notifications.
The update behavior of the client depends on two factors:
Whether the app is installed for only the current user or for all users on the machine
The value of the following registry key:
- Key: HKLM\Software\Microsoft\MSRDC\Policies
- Type: REG_DWORD
- Name: AutomaticUpdates
The Windows Desktop client offers three ways to update:
- Notification-based updates, where a the client shows the user a notification in the client UI or a pop-up message in the taskbar. The user can choose to update the client by selecting the notification.
- Silent on-close updates, where the client automatically updates after the user has closed the UI of the Microsoft Remote Desktop Connection Center.
- Silent background updates, where a background process checks for updates a few times a day and will update the client if a new update is available.
To avoid interrupting your work, silent updates won't happen while you have the client open, have a remote connection active, or if you've disabled the feature. If the client is running while a silent background update occurs, the client will show a notification to let you know an update is available.
You can set your update policy to one of the following values:
| 0 | Disable notifications and turn off auto-update. | Disable notifications and turn off auto-update. |
| 1 | Notification-based updates. | Notification-based updates. |
| 2 [default] | Notification-based updates when the app is running. Otherwise, silent on-close and background updates. | Notification-based updates. No support for silent update mechanisms, as users may not have administrator access rights on the client device. |
Configure user groups
You can configure the client for one of the following types of user groups, which determines when the client receives updates.
The Insider group is for early validation, and consists of admins and their selected users. The Insider group serves as a test run to detect any issues in the update that can impact performance before it's released to the Public group.
Note
We recommend each organization have some users in the Insider group to test updates and catch issues early.
In the Insider group, a new version of the client is released to the users on the second Tuesday of each month for early validation. If the update doesn't have issues, it gets released to the Public group two weeks later. Users in the Insider group will receive update notifications automatically whenever updates are ready. You can find more detailed information about changes to the client at What's new with the Windows Desktop client.
To configure the client for the Insider group, set the following registry information:
- Key: HKLM\Software\Microsoft\MSRDC\Policies
- Type: REG_SZ
- Name: ReleaseRing
- Data: insider
Public group
This group is for all users and is the most stable version. You don't need to do anything to configure this group.
The Public group receives the version of the client that was tested by the Insider group every fourth Tuesday of each month. All users in the Public group will receive an update notification if that setting is enabled.