> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/manage/settings/users/using-entra-id-security-groups/remove-entra-id-security-group.md).
# Remove an Entra ID Security Group in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
{% hint style="danger" %}
**Important**
When you remove an Entra ID Security Group, you are only removing that group’s access to your Patch My PC (PMPC) Cloud Company. You are not deleting the group from Entra ID.
{% endhint %}
To remove an Entra ID Security Group from PMPC Cloud:
1. In the PMPC Cloud portal, navigate to **Settings | Users**.
2. Click the **Entra ID Groups** tab.
3. Click the trashcan beside the relevant Entra ID Security Group you want to remove.
{% hint style="warning" %}
**Important**
You need to have at least one user or Entra ID Security Group assigned the **Full Admin with Access Management** user role at all times. You will be unable to delete an Entra ID Security Group assigned this role unless you have either one other user or Entra ID Security Group assigned this role.
{% endhint %}
4. On the **Are you sure you want to remove <*****group\_name*****>** dialog box, click **Yes** to confirm the removal.
The portal auto-refreshes to show the group has been removed and the **Success – Group deleted** notification is shown.
When you remove an Entra ID Security Group, the **Group Role Removed** event is written to the **Events** node.
---
# 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.patchmypc.com/patch-my-pc-cloud/manage/settings/users/using-entra-id-security-groups/remove-entra-id-security-group.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.
