Skip to main content
Bulk Add / Remove Users to Group adds several people to one group, or removes them from it, in one run. It works with security, Microsoft 365, distribution and mail-enabled security groups. To change one person’s membership, use Group Membership instead. It needs Microsoft 365 connected, Exchange access for distribution and mail-enabled security groups, and the desktop agent for groups synced from on-premises Active Directory. Under GDAP, the client’s relationship needs Groups Administrator, or another role that can change group members (see Recommended roles).

Bulk Add / Remove Users to Group in 50 seconds: what it asks, what it does and what you get.

​
What the form asks

​
What it does

  1. Creates one PSA ticket for the run, if Ticketing is on.
  2. Waits for approval, if Approval is Internal or External, or a conditional override matches.
  3. Add To Group or Remove From Group, for each user in turn, in the client’s Microsoft 365:
    • Security and Microsoft 365 groups change in Microsoft Entra ID.
    • Distribution and mail-enabled security groups change in Exchange Online.
It’s one run for everyone. If the change fails for a user, the run stops there: the users before them are already changed, the users after them aren’t, and Executions shows where it stopped. Adding someone who’s already a member, or removing someone who isn’t, completes without an error. On a client set to Cloud + On-Prem (synced), a group synced from Active Directory takes Set On-Prem Group Membership instead: the desktop agent adds or removes all the users in Active Directory in one go, then starts a delta sync if it runs on the Microsoft Entra Connect server. Every user must be synced from Active Directory too. If the change fails for any of them, the others are still changed, the run ends Failed, and with Ticketing on the ticket gets a note saying how many failed, to update in AD by hand. Cloud groups on that client change in Microsoft 365. With Log actions to the ticket on, the ticket also gets a note when the run starts, after each Add To Group or Remove From Group (for example “Added jane.doe@acme.com to ‘Sales Team’ (security)”) and when the run completes.

​
Configure it

Go to Config, choose Groups and click Bulk Add / Remove Users to Group.

Configure Bulk Add / Remove Users to Group: every option, step by step (1:26).

Approval, Ticketing and User directory filters 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

Check User directory filters. Licensed users only hides people with no licence, and Active users only hides accounts whose sign-in is blocked; untick them on Base config or for that client.
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.
The group comes from on-premises Active Directory, so only users synced from Active Directory can join it. Nothing was submitted. Leave those users out, or use a cloud group for them.
Distribution and mail-enabled security groups change in Exchange Online, and the client has no Exchange connection in Triggr yet. See Exchange Online.