Onboarding and offboarding do not fix access that becomes stale between those events. People change roles, guests finish projects and temporary permissions remain. A recurring review turns that invisible inventory into owned decisions.
Short answer
Automate inventory, reminders and evidence capture. Keep a human decision when evidence is ambiguous. For every person-resource pair, record the owner, business reason, available activity signal, deadline and decision: retain, reduce, remove or investigate.
| Evidence | Suggested outcome | Human gate |
|---|---|---|
| Current role requires access | Retain until next review | Owner confirms scope |
| Guest has an active project | Retain with a new expiry | Sponsor supplies date |
| No activity, dependency unknown | Investigate | Never remove on silence alone |
| Privileged access lacks a reason | Reduce or remove | Security validates impact |
| Reviewer misses deadline | Escalate | Use an approved default policy |
Microsoft Entra supports recurring reviews for groups, apps and roles. Its documentation also explains that each review starts from a snapshot and that submitted decisions may still need enforcement. Model “decision submitted” and “access changed” as separate states.
inventory identity + resource + access type
→ assign an accountable reviewer
→ show evidence and deadline
→ retain, reduce, remove or investigate
→ enforce only an approved decision
→ record result and next review
Pilot with a non-critical group and synthetic records. Include required access, an expired guest, an absent reviewer, a mid-review change and a failed enforcement action. Pass only when every exception has an owner and the final state can be reconstructed.
Track inventory coverage, on-time decisions, confirmed reductions and enforcement failures. “Accounts removed” is not a success metric by itself.
Connect the process to least-privilege onboarding and access offboarding. Recurring reviews govern the long interval between them.