> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/soc-analyst-guide/everyday-tasks/ms365-user-isolation.md).

# MS365 User Isolation

ThreatDefence offers active defence capabilities for Microsoft 365 environments, enabling you to swiftly respond to compromised accounts by revoking user sessions and disabling accounts. This guide provides the steps required to configure Microsoft Graph API permissions for the user isolation functionality.

You can manually isolate or release users at any time via your [ThreatDefence portal](https://portal.threatdefence.io).

***

## Prerequisites

* Onboarding Microsoft Graph API in ThreatDefence. Refer to the [Microsoft Graph API Guide](/microsoft-365/ms-graph.md) for details.

***

#### Usage

* Access your [ThreatDefence portal](https://portal.threatdefence.io).
* Navigate to **Assets** > **M365 Users**.
* Select your tenant, and review the list of users.
* Use the **Isolate** or **Release** buttons to manage user accounts.

**Notes**

* All Disabled accounts will be marked as "Isolated" in the portal.
* External accounts can be isolated, but their active sessions cannot be revoked because external users sign in through their home tenant.


---

# 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.threatdefence.com/soc-analyst-guide/everyday-tasks/ms365-user-isolation.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.