Microsoft 365 comes with an impressive set of security features. The problem is that many of them are optional, need the right licence, or depend on a setting nobody ever touched after the tenant was created. When we assess a small business tenant, we find the same gaps again and again.
Here are five of the most common, and what to do about each.
1. MFA that isn't really enforced everywhere
Most businesses think they have multi-factor authentication. In practice we often find a mix: some users enrolled, some not, a few "temporary" exclusions that became permanent, and service accounts with no MFA at all.
Microsoft has made MFA mandatory for its admin portals, including the Microsoft 365 admin centre, and for changes to Azure resources made through the Azure command line and PowerShell. That protects administrators, but not the rest of your users' mailboxes and files.
What to do:
- Smaller tenants without Business Premium: make sure security defaults are enabled. They require MFA registration for everyone and block legacy authentication at no extra cost.
- With Business Premium: use Conditional Access instead, which is included through Entra ID P1. It lets you require MFA for all users, block sign-ins from countries you don't operate in, and require compliant devices for sensitive data.
- Move administrators and finance staff towards phishing-resistant methods such as passkeys, which can't be intercepted by modern phishing kits.
2. Too many Global Administrators
The Global Administrator role can do everything: read every mailbox, delete every file, disable every security control. Yet in small businesses it is often handed out to the owner, the office manager, the previous IT provider and "the person who set it up".
Microsoft recommends fewer than five Global Admins. Every extra one is another account an attacker can phish to take over your whole organisation.
What to do:
- Give people the least-privileged role that does the job: User Administrator for password resets, Exchange Administrator for mailbox changes, and so on.
- Use separate admin accounts, not people's everyday mailbox accounts, for administrative work.
- Create two emergency ("break-glass") accounts, protected by strong, phishing-resistant authentication and monitored for any use.
- Remove admin access for former employees and previous providers. This one is surprisingly common.
3. Audit logging switched off
If something goes wrong, the audit log is how you find out what happened: who signed in from where, which mailbox rules were created, which files were downloaded. Without it, an incident investigation is guesswork, and meeting obligations like NIS2's 24-hour early warning becomes very difficult.
Here's the catch: while Microsoft enables auditing by default for most organisations, it states that it is not enabled by default for Microsoft 365 Business Basic, Standard and Premium, which are exactly the plans small businesses use.
What to do:
- Check it in the Microsoft Purview portal under Audit. If you see a banner offering to start recording, it's off.
- Turn it on, and confirm it with PowerShell:
Get-AdminAuditLogConfig | Format-List UnifiedAuditLogIngestionEnabledshould returnTrue. - Remember the standard retention is 180 days. Decide whether that's enough for your needs.
4. Automatic forwarding to external addresses
When attackers compromise a mailbox, one of the first things they do is set up a rule that forwards email to an address they control. They then read your conversations silently, waiting for an invoice to intercept.
Microsoft's default outbound policy now blocks automatic external forwarding. But older tenants can behave inconsistently, and exceptions added once for a single user tend to stay forever.
What to do:
- In the Microsoft Defender portal, set automatic forwarding in your outbound spam policy explicitly to Off, rather than relying on the default.
- If someone genuinely needs forwarding, allow it only for that mailbox and document why.
- Set up an alert for new forwarding and inbox rules. It's one of the best early warnings of a compromised account.
5. Email protection left on the basics
Every Microsoft 365 tenant gets baseline spam and malware filtering. But the protections that stop targeted attacks, Safe Links (checking links at the moment of clicking), Safe Attachments (detonating attachments in a sandbox) and impersonation protection, require Microsoft Defender for Office 365. Business Premium includes Plan 1, yet we regularly find those features licensed and paid for, but never configured.
What to do:
- Apply Microsoft's preset security policies: Standard for everyone, and consider Strict for high-value targets like management and finance.
- Add your directors and key suppliers to impersonation protection.
- Publish SPF, DKIM and DMARC records for every domain you send email from, so criminals can't send email that appears to come from your exact domain.
Bonus: check your Secure Score
Microsoft Secure Score, in the Defender portal, rates your tenant's configuration and lists concrete improvement actions, ranked by impact. It's not a perfect measure, but it is a useful to-do list, and it's free. Track it monthly. If it's not trending upwards, nobody is actively managing your tenant's security.
What steady work on that list achieves: one of our clients doubled their Secure Score from 38% to 76% while bringing every device under healthy, reporting protection. Read the Bimvest Holding case study.
Good to know: sending email from devices and apps
Many businesses still have printers, scanners or line-of-business applications that send email using a simple username and password, known as SMTP AUTH basic authentication. Microsoft has postponed its planned removal, but from the end of December 2026 it will be switched off by default for existing tenants. Admins can still turn it back on for now, and Microsoft will announce a final removal date in the second half of 2027. Take stock now of which devices and apps depend on it, so a scanner that suddenly stops emailing doesn't catch you by surprise.
The takeaway
None of these fixes requires new software. They are configuration changes to tools most businesses already pay for. The challenge is knowing where to look, getting them right without disrupting users, and keeping them right as Microsoft keeps changing the platform.