Skip to main content
Bulk Update User Details sets one detail, the department, job title or office, to the same value for several users in one run. Use it when a team moves department or office, or takes on a new job title. Change User Details is the single-user version: it changes one person’s job title, department and mobile phone together. Bulk Update User Details needs Microsoft 365 connected. Under GDAP, the client’s relationship needs User Administrator (see Recommended roles). For a client that syncs on-premises Active Directory, it also needs the desktop agent.

Bulk Update User Details in 50 seconds: what it asks, what it does and what you get.

​
What the form asks

​
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. Update users: Update Details sets the field you chose to the new value on each user in turn, in the client’s Microsoft Entra ID. Office sets the user’s office location.
For a client that syncs on-premises Active Directory, Set On-Prem Attributes runs first: the desktop agent sets the field on every AD-synced user in the list in Active Directory, in one go, then starts a delta sync if it runs on the Microsoft Entra Connect server. Cloud-only accounts in the list then take Update Details. If the Active Directory change fails for any account, the run stops with the error before the cloud-only accounts are updated. It’s one run for everyone, one user at a time. If an update fails, the run stops there: the users before it keep the new value and the rest aren’t changed. Executions shows where it stopped. With Log actions to the ticket on, the ticket also gets a note when the run starts and when it completes.

​
Configure it

Go to Config and click Bulk Update User Details, under Accounts & Access.

Configure Bulk Update User Details: every option, step by step (1:27).

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

The run form shows this when the client’s GDAP relationship doesn’t give Triggr a role that can edit users. Assign User Administrator to Triggr’s security group in that relationship. See Recommended roles.
Check User directory filters. By default the list leaves out unlicensed users, accounts whose sign-in is blocked and guests, as well as anyone in an Entra role you’ve excluded.
An update failed for one user, so the run stopped there. Open the run in Executions to see the error. The users before it already have the new value; fix the cause and run it again for the rest.
This ticket note means the desktop agent couldn’t update one or more AD-synced users in Active Directory. The note says how many failed and why. Make the change in Active Directory, or fix the cause and run it again.
A synced user has no on-premises user principal name in Microsoft 365, so nothing was submitted. Check the account’s UPN in Active Directory and that it has synced, then submit again.