Skip to main content
Change User Details updates a user’s job title, department and mobile phone. Use it when someone changes role, moves team or gets a new number. Fill in only what’s changing: a field left blank keeps its current value. It 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.

Change User Details in 49 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 Details: sets the job title, department and mobile phone you filled in on the user in the client’s Microsoft Entra ID. Blank fields aren’t changed.
For an AD-synced account on a client that syncs on-premises Active Directory, Set On-Prem Attributes runs instead: the desktop agent sets the same details on the user in Active Directory, then starts a delta sync if it runs on the Microsoft Entra Connect server. Cloud-only accounts on that client take Update Details. If the Active Directory change fails, the run stops with the error. 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 Change User Details.

Configure Change User Details: every option, step by step (1:24).

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.
This ticket note means the desktop agent couldn’t update the user in Active Directory. The note includes the error. Make the change in Active Directory, or fix the cause and run it again.
For an AD-synced account, Microsoft 365 picks up the change at the next Microsoft Entra Connect sync.