Microsoft 365 Security Audit Checklist for Businesses

Get a practical Microsoft 365 security audit checklist covering MFA, admin accounts, sharing and audit logs, built for UK businesses in East Anglia.

Quick Summary

A security audit checklist for Microsoft 365 is a structured review of what is switched on, who has access to what, and where the gaps are. Work through admin accounts, multifactor authentication, Conditional Access, sharing settings, audit logs and backups, and repeat the review at least once a year.

  • Remove accounts belonging to former staff and limit global administrators to no more than two named people.
  • Confirm multifactor authentication is enforced for every user, with administrator accounts covered without exception.
  • Block legacy authentication, which older email protocols can use to bypass MFA.
  • Review external sharing and guest accounts every few months, since forgotten links are a common source of exposure.
  • Keep an independent copy of critical logs, because an attacker with admin access can turn off logging or delete evidence.

Table of Contents

Microsoft 365 is the backbone of how many small businesses communicate, store files and share work, which makes its security settings worth a careful look. This guide from Ibertech Solutions walks through a practical Microsoft 365 security audit checklist for businesses, written in plain English so that owners and operations managers can work through it themselves or hand it to their IT provider. Ibertech Solutions is an IT support and web agency, and the steps below reflect the kind of checks our team runs when reviewing Microsoft 365 tenants.

A security audit checklist is simply a structured look at what is switched on, who has access to what, and where the gaps are. The National Cyber Security Centre, the UK government’s cyber security agency, publishes guidance on protecting email, accounts and devices that is a useful reference point for each step below NCSC guidance on cyber security for small businesses. Common issues in Microsoft 365 tenants are accounts without multifactor authentication, old administrator accounts nobody uses, and sharing settings that were left open during a project and never closed.

Why a Microsoft 365 Security Audit Matters for UK Businesses

A Microsoft 365 security audit matters because the tenant is often the single door into your email, files and collaboration tools. If one account is compromised, an attacker can read mail, reset passwords and send convincing invoices to your customers. For a firm with a handful of staff, that can mean a day or more of disruption while the damage is untangled.

Compliance adds another reason. Under UK GDPR, businesses are expected to take appropriate technical measures to protect personal data, and the Information Commissioner’s Office explains what that means in practice ICO guidance on security of personal data. A documented audit shows that you have looked at access controls and acted on what you found.

Run an audit at least once a year, and again after any staff change, new software or office move. Keep a dated record of what you checked, what you changed and what you decided to accept as a risk.

Reviewing Your Microsoft 365 Tenant and Admin Accounts

Start with the tenant itself. Sign in to the Microsoft 365 admin centre and list every user, including former staff, shared mailboxes, and any accounts with administrative roles. Compare that list against your current payroll or staff records. Accounts that belong to people who have left are a common issue in small firms, and they should be disabled or removed.

Next, review who holds administrative roles. Small firms can end up with more global administrators than they need, for example when a former supplier was given access and never removed. Aim for no more than two global administrators, and make sure each of them is a named person with a separate account for day-to-day work.

Privileged access and least-privilege permissions

Privileged access means any role that can change settings, reset passwords or read across the whole tenant. Apply the principle of least privilege: each person should hold only the permissions their job needs. Use the more specific admin roles, such as Exchange Administrator or Helpdesk Administrator, rather than the global role, wherever the task allows it.

A common mistake is giving an office manager global administrator rights simply to make a problem go away. Instead, grant the narrower role for that task, record why it was granted, and review it at the next audit.

Checking Identity, MFA and Conditional Access

Identity is a common route into Microsoft 365 accounts, so this is an important part of the checklist. Work through it in a fixed order so nothing is missed, and record what you find at each step.

Small business owner reviewing sign-in settings on a laptop for a security audit checklist in a bright office.
Small business owner reviewing sign-in settings on a laptop for a security audit checklist in a bright office.

Step 1: Confirm MFA is enforced for every user. In the Microsoft 365 admin centre, go to Active users and check the multifactor authentication status for each account. Every user should show as enabled or enforced.

Step 2: Review Conditional Access policies in Entra ID. Conditional Access is included in some Microsoft 365 and Entra ID plans, so check your licence. You can also read how to keep your business IT compliant in Diss to confirm your wider setup meets compliance requirements. If your licence does not include it, security defaults are your fallback. Where Conditional Access is available, check that you have policies to:

  • Block legacy authentication, which older email protocols can use to bypass MFA.
  • Require MFA for all users, with a separate stricter policy for administrators.
  • Require compliant or hybrid-joined devices for access to sensitive SharePoint sites and finance data.
  • Block sign-ins from countries where you do not operate, if that fits your business.

Name each policy clearly, document what it does and who owns it, and review the list at every audit.

Step 4: Review self-service password reset and guest access. Confirm that self-service password reset is configured with MFA, and that guest invitations are restricted to approved staff. Guest accounts are a common route for external sharing that nobody tracks.

Watch out: enforcing MFA without first checking that every user has a registered authentication method can lock staff out on a Monday morning.

Record the date you checked each item, the policy names, and any exceptions you granted with a reason.

Microsoft 365 Security Best Practices for Email, Devices and Sharing

Email is the most frequent route into a business account, so check your anti-spam and anti-phishing policies in the Microsoft Defender portal. Confirm that impersonation protection covers your key executives and suppliers, and that suspicious attachments are quarantined rather than delivered. Mailbox auditing should be on, so that you can see who accessed a mailbox and when. Mailbox auditing can reveal suspicious access, while strong, unique passwords and multifactor authentication help protect your online accounts from being compromised in the first place.

For devices, use Microsoft Intune or a similar endpoint management tool to require encryption, a screen lock and up-to-date operating systems on any phone or laptop that accesses company data. Staff using personal phones should be covered by app protection policies that stop corporate data being copied into personal apps.

Sharing settings deserve a close look. Review external sharing for SharePoint and OneDrive, and decide whether guest users are allowed at all. Set a default link type that is restricted to people in your organisation, and review guest accounts every few months. Many accidental data exposures come from a link shared “anyone with the link” for a one-off project and never revoked.

Microsoft 365 Audit Log Review: What to Check and How Often

Audit logs record what happened in your tenant, such as sign-ins, mailbox access, file sharing and changes to admin settings. This section gives you that workflow.

Turn on unified audit logging and set retention. In the Microsoft 365 compliance centre, confirm that unified audit logging is active.

Build a fixed review schedule with named owners. A practical routine for a small business is:

  • Weekly: a 15-minute check of sign-in failures, new administrator role assignments, and mailbox forwarding rules created in the last seven days.
  • Monthly: a review of external sharing activity, guest account creation, and large file downloads outside normal hours.
  • Quarterly: a fuller review covering all of the above plus changes to Conditional Access policies and admin role membership.
  • Annually: a complete audit that ties the log review to the rest of this checklist.

Assign each review to a named person and record the date, what was reviewed, what was found, and what was done. A simple spreadsheet with columns for date, reviewer, area checked, findings, action taken and evidence location is enough.

Connect findings to your incident response. If a review uncovers suspicious activity, you need a clear next step: who isolates the account, who contacts your IT provider, and how you record the decision.

Watch out: audit logs are not a backup. If an attacker gains admin access, they can turn off logging or delete evidence.

Record every review, even when you find nothing. A dated record of a clean review is still evidence that you checked.

The table below summarises the recommended review schedule, so you can see at a glance what to check and how often.

Frequency What to check Owner
Weekly Sign-in failures, new admin roles, mailbox forwarding rules (last 7 days) Named reviewer
Monthly External sharing, guest account creation, large downloads outside hours Named reviewer
Quarterly All weekly and monthly items, plus Conditional Access and admin membership changes Named reviewer
Annually Complete audit tied to the full checklist Business owner

Microsoft 365 Backup and Recovery: Testing Your Safety Net

Microsoft 365 keeps data, but it is not a complete backup. Deleted items and ransomware-encrypted files can be difficult to recover without a separate backup, and retention periods are limited. Check whether you have a third-party backup covering Exchange mail, SharePoint, OneDrive and Teams, and confirm where that backup is stored.

A backup you have never restored is only a hope. Schedule a test restore of a few files and a mailbox at least twice a year, and record how long it took and whether the data was intact. This step is often skipped, and it is the one that tells you whether recovery will work when you need it.

Turning Your Audit Into an Action Plan With Ibertech Solutions

Once you have completed the checks above, sort every finding into three groups: fix this week, fix this quarter, and accept with a reason. Give each action an owner and a date. Prioritise anything touching administrator accounts, MFA gaps and external sharing, because these carry the greatest risk.

Some findings depend on your Microsoft 365 licence. Features such as Conditional Access, Defender for Office 365 and Intune are included only in certain plans, so check what you already own before buying anything new.

If you would rather not work through this alone, Ibertech Solutions can review your Microsoft 365 tenant, prioritise the findings and carry out the changes, with flexible virtual or on-site support. We also offer 24/7 support for businesses that want suspicious activity caught outside office hours. Get in touch with us to book a security review and turn this checklist into a plan your team can actually follow.

Frequently Asked Questions

What should a Microsoft 365 security audit include?

A Microsoft 365 security audit should cover your tenant configuration, administrator accounts, multi-factor authentication coverage, user permissions, external sharing in SharePoint and OneDrive, email protection, device security, audit log settings and backup arrangements. Record what you checked, what you found and who owns each fix. Writing this down gives you an evidence trail you can revisit at the next review and share with auditors or insurers if required.

How do I check the security settings in Microsoft 365?

Start in the Microsoft 365 admin centre and the Entra ID portal. Review security defaults or Conditional Access policies, confirm which administrator roles exist and who holds them, and check the Microsoft Defender and Exchange Online protection settings. Use the Microsoft Secure Score page as a starting point, but treat it as a guide rather than a complete audit, since it does not cover every risk in your organisation.

How often should a business audit Microsoft 365 security?

Most small and medium-sized businesses benefit from a full review at least once a year, with lighter checks each quarter. Review administrator accounts and sign-in logs more often, particularly after staff leave or change roles. Any significant change to the tenant, such as a new application or a change of IT supplier, is a sensible trigger for an additional review.

Can a small business carry out a Microsoft 365 security audit itself?

Yes, a business with a named owner and some administrative knowledge can work through a checklist covering identity, email, devices, sharing and logging. However, reviewing audit logs and interpreting Conditional Access policies takes time and experience. Many firms combine an internal checklist with an external review by a managed IT provider such as Ibertech Solutions.

Secret Link