> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-3.x/cortex-xdr-3.x-documentation/readme/understand-cortex-xdr-license-plans/license-allocation.md).

# License allocation

Cortex XDR regulates licenses according to the available license quota and revocation policy.

**Enforcement of Cortex XDR Pro Licenses**

For the Cortex XDR Pro license, Cortex XDR limits the number of Pro agents and associated Pro capabilities to the number of agents allocated by the license. You can further refine the endpoints on which you enable Pro features in your agent settings profiles.

After utilizing all available Pro per Endpoint and Cloud per Host licenses, Cortex XDR falls back to a Cortex XDR Prevent policy that protects the endpoint but does not include Pro-specific capabilities. When you exceed the permitted number of Pro and Cloud agents, Cortex XDR displays a notification in the notification area. Cortex XDR permits a small grace period over the permitted number but begins enforcing the number of agents after 14 days. If additional Pro or Cloud agents are required, increase your Cortex XDR Pro per Endpoint or your Cloud per Host license capacity.

**License revocation**

Cortex XDR manages licensing for all endpoints in your organization. Each time you install a new Cortex XDR agent on an endpoint, the Cortex XDR agent registers with Cortex XDR to obtain a license. In the case of non-persistent VDI, the Cortex XDR agent registers with Cortex XDR as soon as the user logs in to the endpoint.

Cortex XDR issues licenses until you exhaust the number of license seats available. Cortex XDR also enforces a license cleanup policy to automatically return unused licenses to the pool of available licenses. The time at which a license returns to the license pool depends on the type of endpoint:

| Endpoint Type                              | License Return                                                | Agent Removal from Cortex XDR Console | Agent Removal from Cortex XDR Database |
| ------------------------------------------ | ------------------------------------------------------------- | ------------------------------------- | -------------------------------------- |
| Standard and mobile devices                | After 30 days                                                 | After 186 days                        | After 186 days                         |
| (Non-Persistent) VDI and Temporary Session | Immediately after log-off for VDI, otherwise after 90 minutes | After 6 hours                         | After 7 days                           |

After a license is revoked, if the agent connects to Cortex XDR, reconnection of a specific endpoint will succeed as long as the agent has not been deleted, otherwise, the endpoint is registered as a new endpoint.

If a deleted agent tries to connect to Cortex XDR during the 186 days period, the agent can resume connection and maintain its agent ID. After the 186 days period, the agent ID is deleted alongside all the associated data. In order to reconnect the agent, you must use Cytool to reconnect it or reinstall it on the endpoint, and the agent will be assigned a new ID and a fresh start.

{% hint style="info" %}

### Note

It can take up to an hour for Cortex XDR to display revived endpoints.
{% 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://cortex-docs.paloaltonetworks.com/cortex-xdr-3.x/cortex-xdr-3.x-documentation/readme/understand-cortex-xdr-license-plans/license-allocation.md?ask=<question>&goal=<endgoal>
```

`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.