> 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/pd-ag/parallels-desktop-licensing-guide/signing-up-and-registering-a-subscription/renewing-and-updating-licenses.md).

# Renewing and Updating Licenses

A Parallels Desktop Business Edition license purchased online is renewed automatically for as long as the payment method on file remains valid, and until such time that the customer chooses to unsubscribe.

For Parallels Desktop Business Edition or Enterprise Edition licenses purchased via our sales channels there is a grace period of 30 days after the current license expires, during which the system will prompt the administrators to renew the lincese, but the setup will continue to remain activated.

When Parallels Desktop is running on a Mac, it sends a license renewal request to the Parallels Licensing Server at random intervals. Once a license update is available, it is automatically downloaded and installed. Please note that if the license key expires, Parallels Desktop will continue to run on a Mac until it checks in with the Parallels Licensing Server. This could be anywhere from a few minutes to seven days.

Parallels Desktop uses port 443 (the standard SSL port) to communicate with the Parallels Licensing Server from which it obtains license updates.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/pd-ag/parallels-desktop-licensing-guide/signing-up-and-registering-a-subscription/renewing-and-updating-licenses.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 `build a script that syncs our docs to a CMS` 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.