> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/getting-started/deploying-to-microsoft-azure.md).
# Deploying to Microsoft Azure
### Before you begin
You need to have sufficient administrative privileges and Quota available in Microsoft Azure to complete this task. Upon completion of these steps you'll be able to offer desktops and applications to you users.
{% hint style="info" %}
**Note:** You can connect one Microsoft Azure subscription to one Parallels DaaS environment.
{% endhint %}
{% hint style="success" %}
**We are here to help!**
If you experience issues while connecting the subscription, return to the **Introduction** page and click **Contact**. You will be redirected to Parallels My Account, where you can request support.
{% endhint %}
| Action | Screenshot |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------- |
| Start the wizard. Note the customer ID in the bottom when you reach out to support. |  |
| The wizard will outline the steps that need to be executed in the Microsoft Azure portal to set the pre-requisites.
Go to and sign in with administrative credentials.
|  |
| Go to **Entra ID** |  |
| Go to **App registrations** |  |
| Click **New registration** |  |
| Enter a name for the new registration, e.g., Parallels DaaS.
Select Single tenant as supported account type. Click Register.
|  |
| Note the Application and Directory (**Tenant ID**) you need them later. |  |
| Go to **API Permissions** |  |
| Click **Add a Permission** |  |
| On the right fold out choose **Microsoft Graph** |  |
| Select **Application permissions**. Search for and select **Application.ReadWrite.All**. Click **Add**. |  |
| Click **Grant admin consent to the Default Directory** |  |
| Go to **Certificates and Secrets** & Click **New Client secret**. In the right fold out, give the Secret a name, e.g., `Parallels DaaS`, and an expiry date, e.g., the default `180 days` for a proof of concept. |  |
| Note the **Client secret** value, you will need it later. |  |
| Go back to the Parallels DaaS > Onboarding wizard. Enter the information you noted in previous steps:
- Tenant ID
- Application ID
- Client Secret
Click Continue to validate and continue.
|  |
| Click **Grant Admin consent in Azure**, a new tab will open in your browser. |  |
| **Accept** the permissions request. |  |
| Go back to the Parallels DaaS Onboarding wizard & click **Continue**. |  |
| Copy the Service principal to your clipboard and click **Deploy to Azure**. |  |
| Paste the Service principal from the previous step in the **Service Principal ID** field and click **Deploy**. |  |
| Wait for the deployment to complete (typically less than 1 minute). |  |
| Go back to the Parallels DaaS onboarding wizard and select the Azure subscription to use. |  |
| Select the resource groups to use in Microsoft Azure to deploy the required resources. Default names are:
- Infrastructure:
daas-infrastructure-rg - Virtual machines:
daas-vms-rg
|  |
| Select a region close to you to deploy the virtual machines. |  |
| Select the default gateway size unless you run into quota issues. |  |
| Select a machine size that fits your user needs. Your options are:
- Light: Ideal for budget-conscious needs, this plan is streamlined for simplicity and savings, and perfect for tasks like data entry and running simple applications. Deliver essential functionality without the extras.
- Medium: Designed for a typical knowledge worker, this plan supports everyday tasks like document creation, email management, and video conferencing. Get the perfect balance of performance and value for your team.
- Heavy: Prioritize performance with this plan, tailored for resource-intensive workloads like data analysis, or development. Best for power users who need exceptional CPU and memory capabilities.
|  |
| Select an operating system version and optionally whether to install the Microsoft 365 apps. Make sure you are licensed for both the operating system of choice as well as additional applications. |  |
| Settings will be validated one more time, hit **Deploy** to initialize the environment. This process will take approximately 45 minutes. |  |
{% hint style="warning" %}
Please Note: Multi-user requires users to have any of the below license types from Microsoft:
* Microsoft 365 E3, E5, A3, A5, F3, Business Premium, Student Use Benefit
* Windows Enterprise E3, E5
* Windows Education A3, A5
* Windows VDA per user
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/getting-started/deploying-to-microsoft-azure.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.