- Basic authentication is retired for most Exchange Online protocols, but SMTP AUTH, policy exceptions and older integrations can still accept a password alone.
- A Defender for Office 365 licence does not prove protection: check which policies are on, who they cover and who investigates detections.
- OneDrive and the organisation-level sharing setting start at "Anyone", so review both the site settings and the default link type.
- Audit logging is not on by default for Business Basic, Business Standard or Business Premium, and it cannot record events retrospectively.
- Resetting the password only starts the recovery of a compromised account: revoke sessions, remove unfamiliar MFA methods, and check inbox rules, app consents and role changes.
This page covers legacy authentication, email security, applications and consent, external sharing, audit logging, compromised-account recovery and Secure Score. For security defaults, MFA, Conditional Access, admin accounts and the order to roll everything out, see our Microsoft 365 security hardening guide.
Blocking legacy authentication
The real risk is Basic authentication, where an application sends a username and password with each request and cannot complete an MFA challenge. The protocols themselves are a separate question. Microsoft has supported OAuth 2.0 for POP, IMAP and SMTP AUTH in Exchange Online since 2020, so a client that supports modern authentication can use them safely. Microsoft's own analysis found that more than 99% of password spray attacks and more than 97% of credential stuffing attacks it observed used legacy authentication.
With Basic authentication already retired for most Exchange Online protocols, the remaining exposure usually sits in a few places:
- SMTP AUTH. Basic authentication for SMTP AUTH client submission still works until the end of December 2026, when Microsoft plans to disable it by default for existing tenants. Administrators will still be able to re-enable it, and Microsoft has said it will announce a final removal date in the second half of 2027. Printers, scanners and line-of-business applications that send email often rely on it.
- Exceptions. Accounts or groups excluded from security defaults or Conditional Access to keep an older system working.
- Older clients and integrations, including applications outside Exchange Online that still authenticate with a password alone.
Review the Entra sign-in logs, filtered by client app, to see which legacy clients still sign in. Check whether SMTP AUTH is enabled at organisation and mailbox level in Exchange Online. Migrate legitimate applications to OAuth or another supported sending method, and test business-critical workflows before you switch anything off. If you use Conditional Access, run the legacy authentication block in report-only mode first and keep a rollback procedure. In some organisations this is a handful of devices; in others with many older systems, it is a project in its own right. Before you enforce the block, assess every dependent integration, document each exception with an owner, a reason and an end date, keep your break-glass accounts working, and monitor the sign-in logs afterwards for blocked or new legacy attempts.
Email security: Defender for Office 365
All Exchange Online plans include Exchange Online Protection (EOP), which filters spam and malware and includes basic anti-phishing and anti-spoofing protection. Defender for Office 365 Plan 1, included in Business Premium and available as an add-on for other plans, adds:
- Safe Links, which checks URLs at the time of click rather than only at delivery. In email, Safe Links can rewrite URLs so the check happens when the user clicks. In Microsoft Teams, it checks the URL when the user clicks, without rewriting the link shown in the message. Safe Links also covers supported Office apps.
- Safe Attachments, which opens attachments in a sandbox before delivery and blocks files that behave maliciously.
- Additional anti-phishing settings, including impersonation protection for named users and domains and mailbox intelligence.
A licence does not prove protection. Check which policies are enabled, which users, groups and domains they cover, and who investigates detections. Microsoft's Standard and Strict preset security policies are a reasonable starting point for most organisations. No filtering service stops every phishing email, so reporting and response still matter.
SPF, DKIM and DMARC
Configure SPF, DKIM and DMARC for every domain you send from, including third-party services that send email on your behalf. These records help receiving servers decide whether a message using your domain is authorised. Start DMARC in monitoring mode, read the reports until you have identified every legitimate sender, then move step by step to quarantine or reject. Domain authentication does not stop lookalike domains, so it complements the anti-phishing controls above rather than replacing them.
Applications, consent and service identities
Not every Microsoft 365 compromise starts with a stolen password. An attacker can persuade a user to grant a malicious application access to their mailbox or files, and that access continues after a password reset. Applications and service principals with broad permissions or forgotten credentials create similar risks. MFA for users does not cover any of this.
- Review the enterprise applications and app registrations in Entra ID, and the permissions each one holds.
- Restrict user consent, for example to verified publishers and low-risk permissions, and set up an admin consent workflow for everything else.
- Review consent grants periodically, and remove applications and permissions with no business owner, purpose or recent use.
- Monitor new consent grants, new application credentials and changes to service principals.
This matters most for organisations that connect Microsoft 365 to CRM, HR and finance systems, Power Automate flows and third-party SaaS tools.
External sharing settings
SharePoint and OneDrive sharing works at two levels. The organisation-level setting sets the most permissive option any site can use, and it starts at "Anyone", which allows links that work without sign-in. Each site then has its own setting, which can be the same or more restrictive. Microsoft's defaults by site type are:
- OneDrive: Anyone.
- Sites connected to Microsoft 365 groups, including Teams: New and existing guests, if group owners may add people from outside the organisation; otherwise existing guests only.
- Communication sites, classic sites and modern sites without a group: only people in your organisation. The root communication site is the exception and defaults to Anyone.
A separate setting controls which link type is selected by default when a user clicks Share. Review the organisation-level setting, the setting on sensitive sites, the default link type, link expiry, any allowed or blocked domain lists, and the Entra ID external collaboration settings. In Teams, review external access and guest access, and who can bypass the meeting lobby.
Changing the policy does not clean up what is already shared. Review existing external sharing on sensitive sites as well. If you have Entra ID P2 or Entra ID Governance, access reviews can ask owners to confirm whether guests still need access.
Audit logging and alerting
The audit log records user and admin activity across Microsoft 365 services. It is the main source of evidence when you investigate a compromised account. Without it, you cannot reconstruct what an attacker did.
Microsoft turns auditing on by default for most Microsoft 365 organisations. Business Basic, Business Standard and Business Premium are the exception: auditing is not on by default for these licences, and the same applies to unmanaged tenants on free enterprise trials. Check the status in Microsoft Purview, or run Get-AdminAuditLogConfig | Format-List UnifiedAuditLogIngestionEnabled in Exchange Online PowerShell. Enabling it today does not recover events from before it was switched on.
Audit (Standard) keeps records for 180 days. Audit (Premium), included in E5, keeps Exchange, SharePoint and Entra records for one year by default, and longer with an add-on licence. Export to a SIEM if you need a longer history.
Logs alone do not detect anything. Decide which events need an alert, such as admin role changes, new mailbox forwarding or inbox rules, bulk file downloads, Conditional Access changes and new application consents. Then decide who receives each alert and what they do with it. Microsoft's built-in alert policies cover some of these. Defender XDR, Microsoft Sentinel or another SIEM can correlate events across sources. Test critical alerts periodically: generate the event, confirm the alert arrives, and confirm someone acts on it.
Recovering a compromised account
Resetting the password is the start of a recovery. An attacker who has had access to a Microsoft 365 account may have left other ways back in. Your recovery procedure should cover:
- Revoking active sessions and refresh tokens, and resetting the password.
- Reviewing registered MFA methods and removing any the user did not add.
- Checking mailbox forwarding and inbox rules that hide, delete or redirect messages.
- Reviewing OAuth consents the account has granted, and new application credentials.
- Checking for role changes, new accounts and changes to Conditional Access policies.
- Searching the audit log for what the account accessed, sent or shared.
Build these steps into your incident response plan so your team does not have to work them out during an incident.
Microsoft Secure Score
Microsoft Secure Score, in the Microsoft Defender portal, measures how many of Microsoft's recommended security actions your tenant has adopted, with a prioritised list of improvements. It is a useful starting point for a small IT team and a simple way to track progress over time.
It is not a measure of how likely you are to be breached. The score depends on which products you license and which recommendations apply to you, and some recommendations will not fit your organisation. Prioritise actions by risk and operational impact, record the reasons for any recommendation you choose not to follow, and review progress every quarter.