> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Create Group
> Creates a new Microsoft 365, security or distribution group in your client's Microsoft 365.
Create Group makes a new group in a client's Microsoft 365: a Microsoft 365 group, a security group or a distribution group. Use it when a team or project needs a group of its own. It needs [Microsoft 365 connected](https://kb.mspprocess.com/core/get-started/connect-microsoft-365.md), and [Exchange access](https://kb.mspprocess.com/core/reference/microsoft-faq.md#exchange-online) for the client to create distribution groups. Under GDAP, the client's relationship needs Groups Administrator, or another role that can manage groups (see [Recommended roles](https://kb.mspprocess.com/integrations/microsoft-graph/recommended-roles.md)).
Create Group in 49 seconds: what it asks, what it does and what you get.
## What the form asks
| Field | |
| - | - |
| Group name | Required, always on. The group's display name, for example `Design Team` |
| Group type | Required, always on. Microsoft 365, Security or Distribution |
| Description | Required, always on. Saved on the group in Microsoft 365 |
| Reason / ticket reference | Optional by default. For your records and the approver; not sent to Microsoft |
The form doesn't ask for owners, members or an email address.
## What it does
1. Creates a ticket in your PSA, if Ticketing is on.
2. Waits for approval, if Approval is Internal or External, or a conditional override matches.
3. Create Group, in the client's Microsoft 365:
* Microsoft 365 and security groups are created in Microsoft Entra ID.
* Distribution groups are created in Exchange Online.
Microsoft 365 and distribution groups get an alias made from the group name's letters and digits in lower case (Design Team becomes `designteam`), and Microsoft builds the group's email address from it. In Executions, open the Create Group step to see the new group's name, alias and type (`Unified` is a Microsoft 365 group).
Triggr doesn't add anyone to the new group. Add people with [Group Membership](https://kb.mspprocess.com/core/workflows/group-membership.md).
The group is created in Microsoft 365 for every client, including clients set to Cloud + On-Prem (synced). Create Group doesn't create groups in on-premises Active Directory.
With Log actions to the ticket on, the ticket also gets a note when the run starts, after Create Group and when the run completes.
## Configure it
Go to **Config**, choose Groups and click Create Group.
Configure Create Group: every option, step by step (1:28).
| Setting | Where | What it does |
| - | - | - |
| Availability | Header | Internal only, Public form only, Internal + public or Disabled, set on Base config. List on homepage needs a public form |
| Group name, Group type, Description | Form config | Always on: the automation needs them |
| Reason / ticket reference | Form config | Hidden, Optional or Required. Can differ per client |
| Add field, Add section | Form config | Your own questions. They're saved with the request and can go in ticket templates, but aren't sent to Microsoft. Add client section asks one client only |
| Approval | Execution config | None runs on submit. Internal waits for a teammate or group; External waits for the client's approver, set on each client. Let the approver edit the request lets them correct it before approving. Conditional overrides use a different approval when the answers match, for example when Group type is Security |
| Ticketing | Execution config | Create a PSA ticket for each run, with its type, priority, status, subject and body. With no subject, the ticket is titled with the run's summary, for example "Create a new group called Design Team". Log actions to the ticket adds an internal or public note as each action completes |
Approval and Ticketing are set on Base config and apply to every client unless you override them for one. For how Base config and client overrides work, see [How configuration works](https://kb.mspprocess.com/core/get-started/configure-user-onboarding.md#settings-for-each-client).
## Troubleshooting
> [accordion] The run fails at Create Group for a name that's already in use
>
> Microsoft needs a unique alias for a Microsoft 365 group and a unique name for a distribution group, so it refuses a second one with the same name. Open the Create Group step in Executions to see Microsoft's error, then run it again with a different name. Security groups can share a name, so a second run creates a second group.
> [accordion] “Group changes will fail for … — needs Groups Administrator.”
>
> The run form warns you before you submit. Under GDAP, assign Groups Administrator (or User Administrator) to Triggr's security group in the client's relationship, then click **Check now** on the client's GDAP health.
> [accordion] “Microsoft Exchange integration is not configured for tenant …”
>
> Distribution groups are created in Exchange Online, and the client has no Exchange connection in Triggr yet. See [Exchange Online](https://kb.mspprocess.com/core/reference/microsoft-faq.md#exchange-online).
> [accordion] The new group isn't in Group Membership's list
>
> The Group list can come from a cached copy of the client's groups. Click the refresh icon next to the Group field to load them live from Microsoft 365.
## Related
* [Workflow catalogue](https://kb.mspprocess.com/core/reference/workflow-catalogue.md)
* [Run a workflow](https://kb.mspprocess.com/core/use/run-a-workflow.md)
* [Executions](https://kb.mspprocess.com/core/use/executions.md)
* [Group Membership](https://kb.mspprocess.com/core/workflows/group-membership.md), to add people to the new group
* [User Onboarding](https://kb.mspprocess.com/core/workflows/user-onboarding.md), which adds a new starter to groups
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.