> 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/activating-a-license-key.md).

# Activating a license key

When you are invited to Parallels DaaS, you will receive an invitation email that contains a license key, a link to Parallels DaaS Management Portal sign-in page, and instructions on how to activate the license key in Parallels My Account.

To sign in:

1. Sign in to Parallels My Account (<https://my.parallels.com/login>).
2. On the **Home** page, click the **Register a License Key** button. You might be prompted to enter business information if you do not yet have a business account.
3. In the **License Key** field, specify the license key you received in the invitation email. Provide an optional description of the key in the **Display** **name** field.
4. Click **Register**.
5. Click **Dashboard** on the top of the page.
6. On the **Parallels Cloud** card, click **Switch to Management Portal.** You will be redirected to Parallels DaaS Management Portal.
7. Click **Sign in as an owner**.

{% embed url="<https://youtu.be/G0h0v7BnLD4>" %}

Next, you need to [configure prerequisites in Microsoft Azure](broken://pages/JaqVYsFno96ZamE6LFtU)[.](broken://pages/proOyVZoIJAt1bWRzMaS)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/getting-started/activating-a-license-key.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.