> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/tenant/reports/list-licenses.md).

# Licence Report

This report lists every licence SKU present in the selected tenant, showing how many of each are owned, how many are in use, and who holds them. It is the quickest way to spot over-provisioning across a client base, or to find which users and groups are consuming a particular SKU.

This page covers the **Licences** tab. The report also has an [Optimization](/user-documentation/tenant/reports/list-licenses/optimization.md) tab, which suggests licence removals, plan changes and term changes with their estimated savings and can produce a client-ready PDF, and a [Pricing](/user-documentation/tenant/reports/list-licenses/pricing.md) tab, which holds the monthly per-seat prices those figures are calculated from.

The report supports the All Tenants view. Because gathering licence data from every tenant takes time, the first request queues a background job and shows a message asking you to check back once it completes. Results are cached for an hour, so subsequent loads return immediately.

## Table Details

| Column          | Description                                                                                            |
| --------------- | ------------------------------------------------------------------------------------------------------ |
| Tenant          | The tenant the licences belong to. Most useful in the All Tenants view.                                |
| License         | The friendly name of the SKU, resolved from Microsoft's published product names.                       |
| Count Used      | The number of licences currently assigned.                                                             |
| Count Available | The number of licences owned but not yet assigned.                                                     |
| Total Licenses  | The total number of licences owned.                                                                    |
| Assigned Users  | The users holding this licence, including whether each assignment is direct or inherited from a group. |
| Assigned Groups | The groups this licence is assigned to, for group-based licensing.                                     |
| Term Info       | Subscription detail for the SKU. See below.                                                            |

{% hint style="info" %}
SKUs configured as excluded in CIPP's licence settings are omitted from the report.
{% endhint %}

### Term Info

A SKU can be backed by more than one subscription, so Term Info holds an entry per subscription.

{% hint style="warning" %}
This report tries to make an estimate of the NCE term by calculating the dates. As this is an estimate, these dates might not be accurate and require manual checking in your CSP's own environment.
{% endhint %}

| Property            | Description                                                                                                      |
| ------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Status              | The subscription's current status, for example enabled or warning.                                               |
| Total Licenses      | The number of licences on this subscription.                                                                     |
| Days Until Renew    | How many days remain before the next lifecycle date.                                                             |
| Next Lifecycle      | The date the subscription next renews or expires, as reported by the tenant's directory rather than by your CSP. |
| Created Date Time   | When the subscription was created.                                                                               |
| Is Trial            | Whether the subscription is a trial.                                                                             |
| Subscription Id     | The Graph subscription identifier.                                                                               |
| CSP Subscription Id | The commerce subscription identifier, for matching against your CSP portal.                                      |
| OCP Subscription Id | The partner centre subscription identifier.                                                                      |

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Assign License to User</td><td>Assigns the selected licence to a user in that row's tenant. The user list is drawn from the tenant the row belongs to.</td><td>true</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout with the full details for the selected row.</td><td>false</td></tr></tbody></table>

{% hint style="info" %}
This page accepts filters passed in the URL, so links from dashboards and other reports can open it pre-filtered to a particular SKU or tenant.
{% endhint %}

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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.cipp.app/user-documentation/tenant/reports/list-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 `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.