Griffin31
HEBook a demo
HE
Blog

Defender for Office 365: the settings that matter, what each license includes, and common mistakes

1 November 2026 · Shlomi Fanan

Threats

Many organizations pay for Defender for Office 365, yet the protection they bought doesn’t cover every user. The problem is almost always the configuration, not the license.

What each license includes

LevelWhat it includesWhere it’s included
Built-in protection (formerly EOP)Spam, malware and basic phishing filtering, and user reportingEvery cloud mailbox
Plan 1Safe Links, Safe Attachments, impersonation protection, Real-time detections and Teams protectionsBusiness Premium, and since July 2026 Microsoft 365 E3 and Office 365 E3
Plan 2Everything in Plan 1, plus Threat Explorer, AIR, Attack simulation training, Campaigns and advanced huntingMicrosoft 365 E5, or Business Premium with Defender Suite for Business Premium

A quick way to tell what you have: if the Defender portal shows Explorer, you have Plan 2. If it shows Real-time detections, you have Plan 1.

The settings that matter

  1. Preset policies. There are three: Built-in protection, Standard and Strict. Only Built-in protection is on by default, and it’s the weakest: users can click through a warning, and internal senders aren’t covered. Standard and Strict are tighter, and Microsoft recommends applying them to all users.
  2. Safe Links. Checks links at the time of click, in email, Teams and the Office apps. There’s nothing to "turn on" for click-time checking; that’s how it works. What to check: that it applies to all users, internal senders included, and that users can’t click through the warning.
  3. Safe Attachments. The recommended action is Block. If delivery delays are a problem, Dynamic Delivery delivers the message body right away and adds the attachments after scanning. A separate setting protects files in SharePoint, OneDrive and Teams.
  4. Impersonation protection. Mailbox intelligence is on by default. But protection for specific people, such as your CEO and CFO, doesn’t work until you add them to the list, up to 350 users per policy. In a custom policy, the default action is also "don’t apply any action".
  5. Priority accounts. Tag up to 250 sensitive users as priority accounts. With Plan 2 they get extra protection, and either way their alerts and reports are easier to filter.
  6. Configuration analyzer. Compares your policies with the Standard and Strict settings and shows where yours are weaker. The tab that tracks changes over time requires auditing to be on.

Common mistakes

A KnowBe4, Hoxhunt or Cofense report button: connect it to Microsoft

If you use another vendor’s report button, you can send the messages users report to Microsoft as well. They then show up on the User reported page in the Defender portal, generate alerts and, with Plan 2, trigger AIR. Setup:

  1. A reporting mailbox. The button must send reports to an Exchange Online mailbox. Not a distribution group, and not a mailbox outside the organization.
  2. Portal settings. In Settings > Email & collaboration > User reported settings, choose Use a non-Microsoft add-in button, and under Reported item destinations choose Microsoft and my reporting mailbox.
  3. Report format. The original message is attached as an EML or MSG file, unchanged and uncompressed, one message per report. The report subject starts with 1| (Junk), 2| (Not junk) or 3| (Phishing). A report with no prefix is treated as phishing.
  4. Exclusions. Set the mailbox as a SecOps mailbox in the advanced delivery policy, and exclude it from DLP, so messages arrive as they are.

Note: simulation messages reported through another vendor’s button won’t show up in Attack simulation training reports.

Want to know what’s configured in your Defender for Office 365? Griffin31 checks your Microsoft 365 tenant’s security settings continuously, including Safe Links, Safe Attachments and preset policies, and shows you what to fix first.

Sources