> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/workflows/inventory-actions-quick-actions/entra-id-inventory-actions.md).

# Entra ID inventory actions

With inventory actions, you can mitigate the risk of data overexposure and exfiltration in Microsoft Entra ID. Manually trigger on-demand remediation actions to resolve these specific issues in Microsoft Entra ID assets:

* [Remove application](#remove-application)

{% hint style="success" %}
You can also apply inventory actions in [bulk](/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action.md) to multiple assets.
{% endhint %}

## Remove application

You can remove Microsoft Entra ID applications that were installed in the past. 

{% hint style="warning" %}
You cannot remove a DoControl app. It can only be removed by [disconnecting the integration ](/docontrol-user-guide/integrations/offboarding.md)with SharePoint and OneDrive.
{% endhint %}

1. Go to **Inventory > OAuth apps > Microsoft Entra ID.**
2. Select the Azure apps you wish to remove. You can filter by **app name** or **permissions**.
3. From the top right corner, click **Remediate > Inventory actions** > **Remove application**.  
4. Select the relevant workflow, and click **Trigger workflow**.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F4f5j5RO9HjyQN4Kr8jaV%2Fremove%20Azure%20app.png?alt=media&amp;token=2234e541-099e-4c7d-bc40-b52eb1ce0be8" alt=""><figcaption></figcaption></figure>

After confirmation, the selected apps are removed.


---

# 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.docontrol.io/docontrol-user-guide/workflows/inventory-actions-quick-actions/entra-id-inventory-actions.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.