> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/identity/administration/groups/group.md). # View Group This page brings together everything CIPP knows about a single group: its properties, who is in it, who owns it, and what it belongs to. The header shows the group's display name along with its email address, object ID and creation date, each of which can be copied, and a **View in Entra** button that opens the same group in the Microsoft Entra admin center. {% hint style="info" %} Opening a group in Entra uses your own account rather than the CIPP service account, so you need rights in that tenant to see it: direct assignment in the partner tenant, or a GDAP relationship for a client tenant. {% endhint %} ## Actions The **Actions** menu acts on this group. Entries are greyed out rather than hidden when they do not apply. | Action | Description | | -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Edit Group | Opens the [Edit Group](/user-documentation/identity/administration/groups/edit.md) page, where properties, membership and group settings can be changed. | | Set Global Address List Visibility | Hides the group from the Global Address List, or shows it again. Has no effect on a group synchronised from on-premises Active Directory. | | Only allow messages from people inside the organisation | Requires sender authentication, so the group only accepts mail from within the tenant. | | Allow messages from people inside and outside the organisation | Drops the sender authentication requirement, so the group accepts mail from external senders as well. | | Set Source of Authority | Switches the group between Cloud Managed and On-Premises Managed. Greyed out for cloud-native groups that have never been synchronised, and a move back to on-premises takes until the next sync cycle to appear. | | Create template based on group | Creates a reusable group template from this group, copying its name, description, type, membership rule, alias and external sender setting. | | Create Team from Group | Turns the group into a Microsoft Teams team, with the member, messaging and fun settings set in the dialog. Greyed out for anything other than a Microsoft 365 group. | | Delete Group | Deletes the group. | {% hint style="info" %} A group has to be at least fifteen minutes old before **Create Team from Group** will work, as Microsoft needs the group to have finished provisioning first. {% endhint %} ## Group Details The card on the left summarises the group, opening with its display name and type. | Field | Description | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | Display Name | The name of the group as it appears to users. | | Group ID | The group's object ID in Entra ID. | | Email Address | The group's email address. Shown only when the group has one. | | Description | The group's description. Shown only when one is set. | | Group Type | The kind of group, worked out from the group's underlying flags: Microsoft 365, Security, Mail-Enabled Security or Distribution List. | | Mail Enabled | Whether the group can receive email. | | Security Enabled | Whether the group can be used to grant access to resources. | | Created Date | When the group was created. | | Synced from AD | Shown only when the group is synchronised from on-premises Active Directory. | {% hint style="info" %} Group Type is composed rather than returned by Graph, which spreads the same information across the `groupTypes`, `mailEnabled` and `securityEnabled` properties. A group is Microsoft 365 when its `groupTypes` include `Unified`, Mail-Enabled Security when it is both mail and security enabled, Security when it is security enabled alone, and a Distribution List when it is mail enabled alone. {% endhint %} ## Members The group's members, listed with their display name, sign-in name, email address and object type. The row action opens the [View Individual User](/user-documentation/identity/administration/users/user.md) page, and is available for members that are users, since the same table also lists nested groups, devices and contacts. ## Owners The group's owners listed the same way, with the same row action through to the user's own page. ## Memberships The groups this group belongs to, listed with the group name, its types, and whether it is security enabled and mail enabled. Row actions open the group's own page or its edit page. *** ## Feature Requests / Ideas We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub. --- # 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.cipp.app/user-documentation/identity/administration/groups/group.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.