Access Control

Limit and Review Administrator Access

List who can administer your systems, check why they need that access, and remove unnecessary permissions while keeping a tested recovery route.

Content review: 2026-09-22 · Estimated effort: Medium

Priority and effort are suggestions, not risk scores or deadlines. Check business impact, vendor instructions, licenses and obligations before making changes. Test before wider rollout.

Before you start

Before starting: name an access owner and protect a tested emergency administrator route. Record current assignments and an approved recovery process. Do not remove the last usable administrator or change a service identity without its owner's involvement.

Put it into practice

  1. List privileged users, groups, application identities, and external IT-provider access across email, cloud services, devices, and backups. Include inherited group membership and delegated access. Record purpose, approver, owner, and last review in a restricted spreadsheet; never include passwords or recovery codes.
  2. Match each task to the narrowest supported role and scope. In Microsoft Entra, use Roles & admins > All roles and the linked role guidance. Check separate service roles and local device administrators too; an Entra role review is not a complete inventory of privileges.
  3. Use separate named administrator identities for privileged work and ordinary accounts for daily email and browsing. Require MFA, preferably phishing-resistant where supported. Avoid shared routine admin accounts; protect and monitor emergency accounts rather than using them for daily work.
  4. Pilot reduced access with one owner and test their necessary tasks before expanding. Review application consent and delegated permissions as well as human roles; remove unused grants only after checking dependencies. Document narrowly scoped exceptions instead of retaining broad access for convenience.
  5. Schedule owner reviews and revoke access promptly when responsibilities or employment change. Built-in role lists and a manual review are a low-cost start. Just-in-time privileges and automated access reviews can help, but licensing varies; do not assume Entra PIM is included in a basic subscription.
  6. Verify: using a safe test account, confirm an approved task succeeds and an out-of-scope task is denied. Check group-derived privileges, application access, and audit records after changes. Record approvals and exceptions. If a required task breaks, restore only the documented necessary permission with approval, then refine the role.

Use what you have

Tools and templates

“Included” tools require an eligible product or subscription. Options reviewed 2026-09-22; check current vendor terms.

Start without another software subscription

Use existing role listings and the Excel access review worksheet to approve removals and schedule repeat reviews without PIM.

What to account for: A manual review does not provide just-in-time access, automated expiry or PIM approval workflows. Those capabilities require a suitable licensed system.

Allow for equipment, storage and staff time. Eligibility details are linked below.

Entra Roles & admins and assignment export

Start with built-in role listing; PIM requires eligible premium licensing

Open Roles & admins > All roles and Download assignments. Review the exported assignments against responsibilities and approved scope.

Limits: Include local administrators, service roles, apps and external providers separately. PIM requires Entra ID P2 or Governance licensing; a manual review provides no just-in-time enforcement.

Your information: The export contains identity and privilege information. Restrict the downloaded file and remove unneeded copies.

Official instructions: Entra Roles & admins and assignment export ↗

Download a working template

Open the Excel or Word file using your existing Microsoft Office license. Replace fictional entries, fill in the blanks and save your own copy. These manual worksheets have no macros, scoring or automatic verification.

  • Administrator access review (Excel (.xlsx)) ↓

    Record roles, scope, justification, approval and the outcome of each review. Use identifiers appropriate for a restricted internal record.

    Fictional worksheet preview: Administrator access review
    Account or group referenceRole and scopeDecision
    EXAMPLE-ADMIN-GROUPAdministrator: tenant scopePending review

    Three columns shown. The full worksheet also records justification, approval and verification. Record the owner’s approval before changing access.

Fictional worked example

Use these invented entries as a guide when filling in your worksheet. They are not a customer story or lab result. Record what you observe in your own checks.

An employee who moved to a non-IT role still appears in an administrator review.

Use the Administrator access review template.

What to enter before testing

Account or group reference
EXAMPLE-USER-01
Role and scope
Record actual role and scope from the authorized export
Business justification
Role change: current need not confirmed
Decision
Pending owner approval

How to verify

Check direct and inherited assignments and obtain an authorized decision. After an approved removal, check effective access again and confirm ordinary work still succeeds. Protect the remaining authorized administrator and recovery routes.

If the result is unexpected

If privileges remain, investigate group membership and other assignments rather than declaring success. If required work breaks, have the approver identify the minimum justified access; do not automatically restore broad administrator privileges.

Keep completed worksheets private. Leave out passwords, recovery keys and confidential messages. This site does not receive your edits, but a cloud editor or synced folder may send them to its provider.

Sources and review approach

These guides use selected NIST CSF 2.0 alignments. They are not official crosswalks or complete framework implementations. We have not tested these steps in your environment.

  • NIST CSF 2.0: PR.AA-05: least privilege and reviewed permissions
How this guidance is prepared