How to Run an Access Review That Actually Removes Things
A quarterly access review you can run without governance tooling: build the inventory, send managers a decision list, apply removals, and prove it happened.

Most access reviews fail at the same point. Someone exports a list of three hundred group memberships, emails it to six managers, and gets back two replies saying "looks fine" and four no replies at all. Nothing is removed. The review is recorded as complete, and the organization has spent a day confirming that nobody wanted to read a spreadsheet.
A review that removes things is built differently. It is small, it asks for a decision rather than an opinion, it has a default for silence, and the removals actually get applied. Here is the version that works without governance tooling, which matters because the automated features in Microsoft Entra ID require ID Governance or Entra Suite licensing that most smaller organizations do not hold.
Step 1: Decide the scope before you export anything
The instinct is to review everything. Resist it, because a review of everything gets no responses. Pick the things where stale access actually causes harm, and leave the rest for the annual pass.
A good quarterly scope for an organization under two hundred people:
- Administrative roles in your identity provider, your email platform, and every cloud service you pay for.
- Anything that can move money or change where money goes: banking, payroll, the payment gateway, the accounting package, and supplier records.
- Shared accounts and their current credential holders.
- Accounts belonging to people who changed role in the last twelve months, because moves are where access accumulates without anybody deciding to grant it.
- Guests and external collaborators, which decay faster than anything else on the list.
- Service accounts and integrations, including API keys and connected applications.
That is six lists, not three hundred rows. Write the scope down, because the first question anyone asks about a review is what it covered.
Step 2: Build the inventory
Pull each list from the system rather than from memory, and put them in one spreadsheet with a consistent shape: system, account or group, who holds it, what it permits, who the business owner is, and a blank decision column.
Where to get the lists:
- Microsoft 365 and Entra ID: role assignments from the Entra admin center under Roles and administrators, group membership exports, and the enterprise applications list for consented apps. Check Entra ID > Users for accounts that have not signed in recently.
- Google Workspace: Menu > Account > Admin roles lists every prebuilt and custom role and who holds it. Assign the Role Assignment Reader Admin role to whoever runs the review so they can read this without being able to change it. Group membership comes from Directory > Groups, and third-party app grants from Security > Access and data control > API controls.
- Everything outside single sign-on: log in and export the user list by hand. This is tedious and it is where the real findings are, because these systems have no joiner-mover-leaver process attached to them at all.
While you are in each system, note two extra things: whether the account has MFA enabled, and the last sign-in date. Those two columns turn a membership list into a risk-ordered list.
Step 3: Convert the list into a decision, not a question
This is the step that determines whether you get responses. Do not send a manager a tab of raw data. Send them a short list of rows about their own people, with a pre-filled recommendation and a deadline.
The format that gets answers looks like this, one line per row:
Amara Boateng, Finance Reporting group, grants read access to the payroll export. Last signed in 94 days ago. Recommendation: remove. Reply KEEP by Friday 5pm if this is still needed, with one line saying why.
Four things are doing work there. The access is described in terms of what it permits rather than its technical name. There is evidence attached. There is a recommendation, so the easy answer is the safe one. And there is a default for silence, which is the single most important design decision in the whole process.
Set that default deliberately. For low-impact access, no response means remove. For anything where removal would stop someone working mid-week, no response means escalate to the manager's manager rather than remove, because a review that causes an outage will be the last review you are allowed to run. Microsoft's own tooling makes you make the same choice: the If reviewers don't respond setting offers No change, Remove access, Approve access or Take recommendations, and Microsoft warns that combining Remove access with auto-apply can revoke all access to a resource if reviewers stay silent.
Keep each manager's list under fifteen rows. If someone owns more than that, split it across two quarters.
Step 4: Chase properly, once
Send the lists on a Monday with a Friday deadline. Send one reminder on Wednesday to the people who have not replied, naming them individually rather than to the group. Then close the review on Friday and apply the default to anything outstanding.
Do not extend the deadline. An access review that slips becomes an access review that is still open when the next one is due, and two open reviews means no reviews.
Step 5: Apply the removals, and watch what breaks
Removals are the only part of this process that produces security value, and they are the part most often deferred. Do them on a Monday morning, not a Friday afternoon, and do them in a deliberate order:
- Administrative roles first. In Google Workspace, removing a role does not end an active session, so pair the removal with resetting the person's sign-in cookies from their Security page if the removal was unplanned. In Entra ID, revoke sessions as well as removing the assignment.
- Then money-moving access, and tell the finance team what changed before they discover it.
- Then group memberships and application access, which are the ones most likely to generate a ticket.
- Then shared account credentials, which means rotating the password and re-sharing it only with the people who survived the review. A shared account where one holder was removed but the password did not change has not actually been reviewed.
- Then guests and external collaborators, and the connected applications nobody claimed.
Keep a restore path for 48 hours. Note exactly what you removed so that putting it back is a two-minute job rather than an investigation. If you get fewer than two or three tickets from a first review, your scope was too timid.
Step 6: Record it in a way that counts as evidence
Save the spreadsheet with the decisions filled in, the date, who reviewed each section, and a column confirming the removal was applied. That one file is what you hand to an auditor, an insurer or a client's security questionnaire, and producing it costs nothing if you planned for it at the start.
Also record the three numbers that tell you whether the process is working: rows reviewed, access removed, and response rate per reviewer. Response rate is the one to watch, because a manager who never replies is a manager whose team's access is being decided by your default setting. Our note on security metrics covers which numbers are worth tracking and which are theatre.
Got an email asking you to "confirm your access" with a link? Paste the message or link into CyberWatch AI Scan for a free check.
If you do have the tooling
If your licensing includes Microsoft Entra ID Governance, the same process runs from ID Governance > Access Reviews > New access review, and it is worth using because it chases people for you. A few settings that decide whether it helps or hurts:
- Scope. Choose Teams + Groups or Applications, then Guest users only or Everyone. Selecting five groups creates five separate reviews, so keep the selection small. You can also scope a group review to Inactive users (on tenant level) and specify Days inactive, which is the fastest way to a review with a high removal rate.
- Reviewers. Group owner(s), Selected user(s) or groups(s), Users review their own access or Managers of users. Self-review is weaker than manager review and is better than no review. Always set a fallback reviewer when you choose managers or group owners.
- Upon completion settings. Auto apply results to resource is what turns decisions into removals; leave it off and you are back to applying changes by hand. Pair it with a deliberate If reviewers don't respond choice.
- Enable review decision helpers. No sign-in within 30 days gives reviewers a recommendation based on recent activity, which is the same evidence you would have pasted in manually.
- Advanced settings. Turn on Justification required so a KEEP decision comes with a reason, Reminders so the system chases at the halfway point, and use Additional content for reviewer email to explain in two sentences what you are asking for.
Note that Microsoft Entra roles themselves are reviewed through Privileged Identity Management rather than through the access reviews blade, which is a common source of confusion when you cannot find your administrators in the list.
What a good review changes
The point is not the spreadsheet. A first review on a tenant that has never had one typically removes a handful of administrative roles nobody needed, two or three leavers who were never fully deprovisioned, a dozen stale group memberships, and at least one connected application that could read everyone's mail. That is a materially smaller blast radius for the next phished password.
It also tells you where your processes leak. Leavers appearing in a review means your deprovisioning is incomplete. Accumulated access on people who changed role means your joiners, movers and leavers process adds but never subtracts. Fix those and the next review gets shorter, which is the only sustainable outcome. For the principle underneath all of it, see least privilege in practice, and for where this sits in a wider programme, our small business cybersecurity guide.
Frequently asked questions
Do I need special licensing to run an access review?
No. Microsoft Entra access reviews require Microsoft Entra ID Governance or Microsoft Entra Suite licensing, and some capabilities work with Entra ID P2. Without those you run the same process manually from exported lists, which for an organization under a couple of hundred people takes a few hours a quarter.
How often should we do this?
Quarterly for administrative roles, group memberships and anything outside single sign-on. Annually for everything else. Plus an unscheduled review immediately after any compromise, because an attacker's first move is usually to grant themselves something.
Who should make the decisions?
The person who knows what the access is for, which is almost never IT. Line managers for their own people, system owners for applications. IT's job is to produce the list, chase the responses and apply the result, not to guess whether the finance team still needs the reporting tool.
What do I do about access nobody will claim?
Remove it, with a note of what you removed and when, and a way to restore it quickly. Unclaimed access that turns out to be needed generates one support ticket. Unclaimed access that stays in place generates an incident eventually.
What should go in scope first if I only have an afternoon?
Administrative roles, then anything that can move money or change payment details, then shared accounts, then accounts belonging to people who changed role in the last year. That ordering catches most of the real risk in the first hour.
How do I review access to systems that are not in our identity provider?
By exporting the user list from each one and treating it as its own review. The bank, the payroll portal, the domain registrar and the payment gateway are usually outside single sign-on and are usually the accounts that matter most, so they belong on the list even though there is no automated way to produce them.
What evidence should we keep?
The list that was reviewed, who reviewed it, the date, each decision, and confirmation that removals were applied. One spreadsheet per review, stored where a future auditor or insurer can find it. Reviews with no record are indistinguishable from reviews that never happened.
How do I stop the same stale access reappearing?
Fix the process that created it. If leavers keep showing up, your deprovisioning is the problem. If people accumulate access when they change role, you are adding on moves but never removing. A review that finds the same thing twice is telling you about a process, not about a person.
Sources
- What are access reviews?, Microsoft Learn
- Create an access review of groups and applications, Microsoft Learn
- Best practices for Microsoft Entra roles, Microsoft Learn
- Prebuilt administrator roles, Google Workspace Admin Help
- Admin log events, Google Workspace Admin Help
- SP 800-53 Rev. 5: Security and Privacy Controls for Information Systems and Organizations, NIST
- CIS Critical Security Controls, Center for Internet Security
- 10 Steps to Cyber Security, NCSC


