# Using Parallels Client with Azure Virtual Desktop

After you deployed Azure Virtual Desktop in Parallels RAS and published resources from it, you can use Parallels Client to access applications and/or desktops that you published. This topic describes Parallels Client requirements and provides additional information about accessing published resources.

### **Requirements**

Parallels Client requirements for opening Azure Virtual Desktop apps and desktops are as follows:

* Parallels Client for Windows:
  * Parallels Client for Windows version 18 or newer (Basic or Full versions).
  * Supported Windows versions: Windows 10 and Windows 11. Note that Windows Server operating systems are not supported.
  * Windows updates: Update for Universal C Runtime for Windows (KB2999226). Microsoft Windows 10 incorporates this by default.
  * Microsoft .NET Framework 4.6.0 or later is required. Microsoft Windows 10 incorporates .NET Framework 4 and has it enabled by default.
  * In case the Parallels RAS policy is configured to use the Azure Virtual Desktop Client, the Microsoft Windows Desktop client, also known as Remote Desktop (MSRDC) client, must be installed. The client is downloaded and installed automatically upon launching an Azure Virtual Desktop resource from Parallels Client (if not already installed on a supported Windows client device). You may also download the client using the following link: <https://go.microsoft.com/fwlink/?linkid=2068602>.
  * In case the Parallels RAS policy is configured to use Microsoft Windows App, the Windows App is automatically downloaded and extracted upon launching an Azure Virtual Desktop resource from Parallels Client. A manually installed version of Microsoft Windows App will not be used by the Parallels RAS Client for Windows.

{% hint style="info" %}
**Note:** If you are using the [**Standard**](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/azure-virtual-desktop/deploy-azure-virtual-desktop/enable-azure-virtual-desktop-and-add-a-provider) client feature set option and Windows 10 and Windows 11 Enterprise Virtual Desktop as desktop OS where the Parallels Client is running (nested), the administrator needs to have the Windows Desktop client preinstalled using the per-device installation as highlighted by Microsoft in the following article: <https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/windowsdesktop-admin>.
{% endhint %}

{% hint style="info" %}
**Note**: Starting March 27, 2026, the Remote Desktop client for Windows (MSI) will no longer be supported by Microsoft. Use Parallels RAS policies to configure using the Microsoft Windows App for launching Azure Virtual Desktop resources.
{% endhint %}

* Microsoft Teams support: Starting with Parallels RAS 19, you can redirect audio and video from an Azure Virtual Desktop host running Windows 10 or 11 Multi-session, Windows 10, or 11 Enterprise to Parallels Client for Windows. For information on how to install Microsoft Teams on a Azure Virtual Desktop host, see <https://docs.microsoft.com/en-us/azure/virtual-desktop/teams-on-avd>.

{% hint style="info" %}
**Note:** Video feed is not available if Microsoft Teams is accessed as a published application using the Advanced client feature set.
{% endhint %}

{% hint style="info" %}
**Note**: At the time of this writing, it is not yet possible to use other platform-specific Parallels Clients to launch Azure Virtual Desktop resources. However, you can use Parallels Web Client to do that on certain operating systems (see below).
{% endhint %}

* Parallels Web Client:
  * Windows, Mac, or Linux operating system installed on the user's machine.
  * System requirements as listed in [**Parallels Web Client and User Portal**](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/parallels-web-client-and-user-portal).

### **Accessing Azure Virtual Desktop resources in Parallels Client for Windows**

When you connect to Parallels RAS from Parallels Client for Windows, all published resources, including Azure Virtual Desktop resources, are listed and made available for a user to access. Note that Azure Virtual Desktop resources are only shown in Parallels Client running on supported versions of Windows (see above).

The **Client feature set** options **Advanced** and **Advanced with feedback** are deprecated and should no longer be used. Use **Standard** mode for all new and existing deployments to ensure compatibility and long-term support. Standard mode contains most features that were previously only available in Advanced mode, such as RAS Universal Printing and Scanning and accelerated file redirection. Standard mode currently does not support session prelaunch and drag and drop.

To view and modify this setting, navigate to **Farm** > **Site** > **Settings**, select the **Features** tab, and select a desired setting in the **Client feature set** drop-down list.

Parallels RAS policies can be configured to use the **Microsoft Windows App** for launching Azure Virtual Desktop resources. Using the Microsoft Windows App requires the Client feature set to be set to Standard.

{% hint style="info" %}
**Note**: Starting March 27, 2026, the Remote Desktop client for Windows (MSI) will no longer be supported by Microsoft. Use Parallels RAS policies to configure using the Microsoft Windows App for launching Azure Virtual Desktop resources.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/azure-virtual-desktop/using-parallels-client-with-azure-virtual-desktop.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
