Buyer guide

A Microsoft 365 security baseline for small and mid-sized organisations

A sound Microsoft 365 baseline starts with identity: multi-factor authentication for everyone, legacy sign-in blocked, administrator access tightly controlled. Then email protection, managed devices, a backup outside normal retention and someone watching alerts.

The short answer

A baseline covers six areas. Your licences decide the tools: check your plan first.

Identity

MFA for every user; legacy authentication blocked.

Administrator access

Separate admin accounts, few Global Administrators, two emergency accounts.

Email

Preset protection policies plus sender authentication.

Devices

Managed, encrypted and protected endpoints.

Data and backup

Sensible sharing; a backup that restores after deletion or ransomware.

Monitoring

Someone watching sign-in risk, alerts and configuration drift.

1. Identity: MFA and blocking legacy sign-in

Security defaultsConditional Access
CostFreeNeeds at least Microsoft Entra ID P1
ControlOn or off as a wholePolicies by user, device, location, application and risk
Best forOrganisations without Entra ID P1P1 or P2 organisations, per Microsoft; turn security defaults off when policies replace them
More detail

Security defaults require all users to register for MFA, require MFA for administrators, prompt users for MFA when needed, block legacy authentication protocols, block device code flow and protect access to Azure management tools (Microsoft Learn).

Legacy authentication (IMAP, POP3 and other older protocols) does not support MFA, so attackers use it to bypass MFA. Before blocking it, check printers, scanners and business applications that still sign in or send mail the old way.

Choose MFA methods that work here. Mobile networks in some locations are unreliable, so SMS codes may arrive late or not at all, and SMS is weaker against SIM-swap fraud. An authenticator app (which generates codes offline) or a security key is more dependable for staff who travel or work from branch offices.

A typical Conditional Access starting set:

  • MFA for all users
  • Phishing-resistant MFA (passkeys, security keys) for administrators
  • Block legacy authentication
  • Compliant or managed devices for sensitive data
  • Block countries where you have no staff, if that fits

2. Administrator access

Microsoft's guidance for Entra roles (Microsoft Learn):

  • Least privilege: roles such as User Administrator or Exchange Administrator, not Global Administrator, for everyday work.
  • Global Administrator for fewer than five people; MFA on every administrator account.
  • Cloud-only admin accounts, separate from everyday accounts so mail and browsing are not privileged.
More detail
  • Privileged Identity Management for just-in-time elevation where licensed (Entra ID P2 or Entra ID Governance).
  • Recurring access reviews to remove roles people no longer need.
  • Cloud-only means not synchronised from on-premises Active Directory.
Two or more emergency access ("break glass") accounts. Cloud-only, on the onmicrosoft.com domain, protected with a phishing-resistant method (such as a FIDO2 passkey) different from your normal admin method, excluded from Conditional Access policies that could block them, alerting on every sign-in, and tested at least every 90 days (Microsoft Learn).

3. Email protection

Email is the most common route for phishing and malware. Microsoft's preset security policies (Standard, Strict) apply its recommended anti-spam, anti-malware and anti-phishing settings, plus Safe Links and Safe Attachments with Defender for Office 365, and stay aligned as recommendations change, unlike unreviewed custom policies (Microsoft Learn).

SPF, DKIM, DMARC

Every sending domain; DMARC to enforcement once legitimate mail passes. Deters payment-fraud impersonation of your domain.

Tag external mail

Staff see when a message comes from outside.

Block auto-forwarding

To external addresses, unless there is an approved business reason.

Easy reporting

A simple way for users to report suspicious messages.

4. Devices

Enrol in Intune

Or equivalent, with compliance: supported OS, encryption, screen lock, security software running.

Endpoint protection with EDR

Defender for Business or Defender for Endpoint, by licence. See EDR vs antivirus.

Automatic patching

Windows, macOS, Office apps, browsers; check devices offline through power or network outages catch up.

Personal phones

App protection policies keep work data in managed apps without taking over the device.

5. Data sharing and backup

  • Review SharePoint and OneDrive external sharing: limit "anyone" links, set link expiry, restrict sharing on sensitive sites.
  • Use sensitivity labels and data loss prevention where licensed and where you have clear rules to enforce.
Retention is not backup. Retention policies preserve content for compliance; they are not designed to roll a whole mailbox or site back to a point in time after ransomware or mass deletion.

Options: pay-as-you-go Microsoft 365 Backup for SharePoint, OneDrive and Exchange, with restore points and configurable recovery windows (Microsoft Learn), or third-party products storing copies outside Microsoft's service. Either way, test restores; see why a backup is not the same as a recovery plan.

6. Monitoring and review

  • Secure Score reviewed; decisions on skipped items recorded
  • Audit logging on and retained (it helps assess a breach under the Nigeria Data Protection Act 2023)
  • Alerts: risky sign-ins, new forwarding rules, new admin roles, emergency account use
  • A named alert owner, after hours if needed
  • Re-check after licence changes, mergers, major Microsoft changes

Baseline checklist

Identity

  • MFA enforced for all users (security defaults or Conditional Access)
  • Legacy authentication blocked; exceptions identified and fixed
  • Phishing-resistant MFA for administrators

Administration

  • Fewer than five Global Administrators
  • Separate, cloud-only admin accounts
  • Two emergency access accounts, monitored and tested at least every 90 days
  • Access reviews scheduled

Email

  • Standard or Strict preset security policy applied
  • SPF, DKIM and DMARC published for every sending domain
  • External auto-forwarding blocked or controlled

Devices

  • Devices enrolled with compliance policies
  • Endpoint protection with EDR deployed
  • Automatic patching in place

Data

  • External sharing settings reviewed
  • Backup covering Exchange, OneDrive and SharePoint, with a tested restore

Monitoring

  • Secure Score reviewed on a schedule
  • Alerts assigned to a named owner

Limitations

Microsoft changes features, names and licence contents often: confirm against current documentation and pilot changes first. A baseline is a starting point, not a full security programme; it does not replace training, incident response planning or backups outside Microsoft 365. General information, not legal advice. To have it assessed or implemented, see our Microsoft 365 and modern workplace service.

Sources and further reading

Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.

  1. Security defaults in Microsoft Entra ID, Microsoft Learn
  2. Best practices for Microsoft Entra roles, Microsoft Learn
  3. Manage emergency access admin accounts, Microsoft Learn
  4. Preset security policies, Microsoft Learn
  5. Overview of Microsoft 365 Backup, Microsoft Learn

This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.

Talk to Promatics

Get a straight answer for your situation

General advice only goes so far. Tell us about your environment and we will tell you what we would do, what it would cost and what to watch out for.

  • A named specialist who owns the outcome, not a chat window
  • Advice checked against your actual systems, contracts and risks
  • Written scope and costs in NGN before any work starts