Account Unlock in 49 seconds: what it asks, what it does and what you get.
What the form asks
What it does
- Creates a ticket in your PSA, if Ticketing is on.
- Waits for approval, if Approval is Internal or External, or a conditional override matches.
- Re-enable Sign-in: turns sign-in back on for the account in the client’s Microsoft 365.
Configure it
Go to Config and click Account Unlock.Configure Account Unlock: every option, step by step (1:16).
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 blocked user isn't in the User list
The blocked user isn't in the User list
Check User directory filters for that client. With Active users only ticked, accounts whose sign-in is blocked are hidden. Guests and anyone in an Entra role you’ve excluded are hidden too.
The run completed but the user still can't sign in
The run completed but the user still can't sign in
Account Unlock turns sign-in back on. It doesn’t change Microsoft Entra smart lockout after repeated wrong passwords, which ends on its own. For an AD-synced account, Microsoft 365 picks up the change at the next Entra Connect sync. If they’ve forgotten their password, run Password Reset.
“Set On-Prem Account State — needs manual attention”
“Set On-Prem Account State — needs manual attention”
This ticket note means the desktop agent couldn’t enable or unlock the account in Active Directory. The note includes the error. Make the change in Active Directory, or fix the cause and run it again.
Related
- Workflow catalogue
- Run a workflow
- Executions
- Password Reset, for a forgotten password

