# Add Microsoft Azure as a Provider

To add Microsoft Azure as a Provider:

1. In the RAS Console, navigate to **Farm > Site > Providers**.
2. On the **Providers** tab, click **Tasks > Add > Microsoft Azure**.
3. The **Add Cloud Computing** wizard opens.
4. In the wizard, specify the following:
   * **Name:** Name of the provider.
   * **Description:** Description of the provider.
   * **Manage credentials:** the administrative accounts that will be used to deploy Parallels Agents.
   * **Authentication URL:** Prepopulated with the Microsoft authentication site URL. Unless otherwise required or indicated, keep the default value provided.
   * **Management URL:** Prepopulated with the Microsoft Azure management site URL. Unless otherwise required or indicated, keep the default value provided.
   * **Resource URI**: Prepopulated with the Microsoft Azure resource URI. Unless otherwise required or indicated, keep the default value provided.
   * **Tenant ID:** The "Directory (tenant) ID" value of the Microsoft Entra ID app that you created earlier.
   * **Subscription ID:** Your Microsoft subscription ID.
   * **Application ID:** The "App (client) ID" value of the Microsoft Entra ID app that you [created earlier](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/virtual-desktop-infrastructure-vdi/add-a-provider/add-a-cloud-provider/microsoft-azure/create-microsoft-entra-id-application.md).
   * **Application key:** The "Client secret" value of the Microsoft Entra ID app that you c[reated earlier](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/virtual-desktop-infrastructure-vdi/add-a-provider/add-a-cloud-provider/microsoft-azure/create-microsoft-entra-id-application.md).
5. Click the **Advanced Settings** link to open a dialog where you can configure the following optional settings:
   * **Use dedicated Provider Agent:** When this option is cleared (default), the built-in RAS Provider Agent will be used. If you want to use a dedicated RAS Provider Agent, select this option and specify the host FQDN or IP address.
   * **Agent address:** This option becomes enabled if you select the option above it. Specify the FQDN or IP address of the host where the RAS Provider Agent is (or will be) installed. This can be either a physical box or virtual machine.
   * **Preferred Connection Broker:** Select a RAS Connection Broker to be the preferred agent for this Provider. For more info, see [**Enabling high availability for VDI**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/virtual-desktop-infrastructure-vdi/enabling-high-availability-for-vdi.md).
6. Click **Next.** The wizard will display the new Provider information and will indicate the RAS Provider Agent status. If everything is OK, click **Finish** to exit the wizard. If something is not as expected, click **Back** and correct any mistakes if necessary.

The new Provider will now appear on the **Providers** tab in the RAS Console. Complete the Provider addition as follows:

1. Click **Apply** to apply the changes.
2. Verify the value of the **Status** column. If it's anything other than **OK**, right-click the Provider and choose **Troubleshooting** > **Check agent**. Verify the agent status and install it if necessary, then click **OK**. The **Status** column on the **Providers** tab should now say **OK**.

## **Modifying the Provider configuration**

To view and modify the Provider configuration, right-click it and choose **Properties**. In the dialog that opens, view and modify the Provider properties.


---

# 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/virtual-desktop-infrastructure-vdi/add-a-provider/add-a-cloud-provider/microsoft-azure/add-microsoft-azure-as-a-provider.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.