> 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/modify-entra-id-security-group.md).
# Modify an Entra ID Security Group in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Once an Entra ID Security Group has been added to Patch My PC (PMPC) Cloud, you can change the role assigned to that group.
{% hint style="info" %}
**Note**
You cannot change the membership of an Entra ID Security Group from within the PMPC Cloud portal.
{% endhint %}
To change the role assigned to an Entra ID Security Group:
1. In the PMPC Cloud portal, navigate to **Settings | Users**.
2. Click **Entra ID Groups**.
3. Click the dropdown arrow in the **Group Role** column beside the group whose role you want to modify and select the new role.
{% hint style="warning" %}
**Important**
You will be unable to change the group’s role from **Full Admin with Access Management** to another role if this is the only group assigned that role and no users under the **Active Users** tab have been assigned the **Full Admin with Access Management** role.
{% endhint %}
The portal auto-refreshes to show the new role assigned to the group and the **Success – Role changed** notification is shown.
When you change the role of an Entra ID Security Group, the **Group role with name <*****group\_name*****> and id <*****entra\_id\_security\_group\_id*****> was changed to role <*****new\_user\_role*****>** 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/modify-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.
