> 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.threatdefence.com/soc-analyst-guide/everyday-tasks/ms365-user-isolation.md?ask=&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.