> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/automation/connectors/microsoft-entra-id-connector/managing-licenses.md).

# Managing Licenses

License components cover both sides of license work: seeing what you have, and moving it between people.

#### List Licenses

Returns every license SKU your organisation subscribes to, with the consumed, enabled and available unit counts.

Those counts are the reason this component is more useful than it first looks. They are what you need for cost control and for reordering before you run out — and they are the input for any flow that assigns licenses, because you need the SKU ID from here.

#### Assign License

Assigns one or more licenses to a user. SKU IDs are given as a comma-separated list, and individual service plans within a SKU can be switched off if you do not want the whole bundle.

{% hint style="warning" %}
The user needs a **usage location** before any license can be assigned. Without it, Microsoft rejects the request.

Set it when the account is created rather than fixing it afterwards — otherwise an onboarding flow fails halfway through, with the account already made.
{% endhint %}

#### Remove License

Removes licenses from a user.

This belongs in every offboarding flow. A disabled account keeps consuming its licenses until someone takes them away, and that is the most common place where spend quietly continues after people leave.


---

# 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://hub.equipme.io/documentation/automation/connectors/microsoft-entra-id-connector/managing-licenses.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.