> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/automation/connectors/microsoft-entra-id-connector/managing-groups.md). # Managing Groups Groups carry access in most organisations, which makes these components the backbone of provisioning flows. #### List Groups, Get Group, Update Group, Delete Group The standard read, update and delete operations. **List Groups** accepts an OData filter and the usual Output Type setting. #### Add Group Creates a group, including dynamic ones. **Membership Rule** is what makes a group dynamic. Supplying a rule such as `user.department -eq "Sales"` switches on rule processing, and membership is then maintained by Entra rather than by your flow. **Visibility** sets the group to private, public or hidden membership. **Owner IDs** assigns owners during creation as a comma-separated list. #### List Group Members Returns the members of a group. #### Add Group Members Adds several members at once, given as comma-separated IDs. {% hint style="info" %} Microsoft accepts at most 20 members per request when adding in bulk. Keep this in mind when a flow feeds in a large list, and test with a realistic number before relying on it. {% endhint %} #### Remove Group Member Removes a single member from a group. #### List Group Owners, Add Group Owner, Remove Group Owner Manage who owns a group. This matters more than it looks: a group without an owner has nobody responsible for reviewing its membership, which is why ownerless groups are a standard governance finding. #### Check Group Membership Checks whether a user belongs to one or several groups, including nested memberships through other groups. The response tells you whether the user is a member, which of the groups matched, and how many. Nested resolution is the useful part here — a direct membership check would miss access granted through a parent group. #### Trigger: New Group Member and Removed Group Member Webhook triggers that react as soon as someone is added to or removed from a specific group. Together they are the basis for group-driven provisioning: joining the group grants access in the target system, leaving it takes the access away. Building only the first half is a common mistake, and the second half is the one auditors ask about. --- # 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://hub.equipme.io/documentation/automation/connectors/microsoft-entra-id-connector/managing-groups.md?ask=&goal= ``` `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.