Skip to main content
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, and Exchange access 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).

Create Group in 49 seconds: what it asks, what it does and what you get.

​
What the form asks

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. 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).

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.

​
Troubleshooting

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.
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.
Distribution groups are created in Exchange Online, and the client has no Exchange connection in Triggr yet. See Exchange Online.
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.