> 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/cipp/custom-data/directory-extensions.md).

# Directory Extensions

[Directory extensions](https://learn.microsoft.com/en-us/graph/extensibility-overview?tabs=http#directory-microsoft-entra-id-extensions) allow you to add custom properties to Microsoft Entra directory objects. Each extension is a single standalone property registered against the CIPP application registration, which makes it available in every tenant CIPP is consented to.

* Directory extensions must have unique names.
* There is a limit of 100 extension values per resource instance.
* [Considerations for using directory extensions](https://learn.microsoft.com/en-us/graph/extensibility-overview?tabs=http#considerations-for-using-directory-extensions)

## Action Buttons

{% content-ref url="/pages/Y1u8bCEpqZ39WQN4bXZ8" %}
[Add Directory Extension](/user-documentation/cipp/custom-data/directory-extensions/add.md)
{% endcontent-ref %}

## Table Details

| Column          | Description                                                                                                                                                             |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name            | The fully qualified extension name, in the form `extension_<applicationId>_<yourName>`. This is the property name used when reading or writing the value through Graph. |
| Data Type       | The type of value the extension stores.                                                                                                                                 |
| Is Multi Valued | Whether the extension holds a collection of values rather than a single value.                                                                                          |
| Target Objects  | The directory object types the extension can be set on.                                                                                                                 |

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Delete Directory Extension</td><td>Removes the extension from the CIPP application registration after confirmation. Values already written to directory objects are no longer readable through the extension.</td><td>true</td></tr></tbody></table>

{% hint style="danger" %}
Deleting a directory extension is permanent and affects every tenant, not just the one you are currently viewing. Check for mappings that reference the extension before removing it.
{% 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 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://docs.cipp.app/user-documentation/cipp/custom-data/directory-extensions.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.