Skip to content
Octiga Docs
Copy as Markdown

Dormant Users

ScopeGroupRoleL1 Read to view · L1 Read/Write to actLicenceEntra ID P1 or P2

Define when users are considered dormant.

Adding a baselineAdd, configure or remove a single baseline on a tenant, a user or a group, without deploying a whole scheme.

Configure it

This baseline applies per user, through a user-level scheme or an Azure group rather than to the tenant as a whole. It evaluates only users with no administrator role; admin accounts are covered by the dormant-admin baseline instead.

  1. Add it directly to a user or an Azure group (Adding a baseline), or bundle it into a user-level scheme and deploy that to the groups covering your users (Deploying a scheme). See Groups and priority for how Octiga resolves which value a user gets when a Direct value, a scheme and a group all supply one.

  2. Set how many months without a sign-in counts as dormant. It’s the only setting on this baseline, and the longest you can set is three months, in line with common guidance to act on an inactive account well within 90 days.

  3. Save. This baseline only reports what it finds and writes nothing back to Microsoft 365, so there’s no Auto-remediation switch.

Check it worked

Passing means the user has signed in within the window you set; Deviated means they haven’t. To check the last sign-in yourself, go to Identity → Users in the Microsoft Entra admin centre, select the user and open Sign-in activity. On the user roster or a group’s member list, Passing shows as a green dot for this baseline; Deviated (red) means the account has gone quiet; Excluded (grey) means the user or tenant isn’t licensed for Entra ID P1 or P2.

Doing this for every tenant?

Step through the deploy wizard to apply a scheme to a tenant, groups or users, and see what Managed and Direct do at deploy time.

Deploying a scheme