Colour theme
Book a consultation

Seven checks for Defender email protection

Review Microsoft Defender email protection by licence, policy coverage, spam handling, links, attachments, mail routing and staff reporting.

A white padlock icon in a green circle, over rows of green characters on a black background

The Defender name covers several Microsoft security products. Email protection in Microsoft 365 involves the mail service’s built-in controls and, where licensed, Microsoft Defender for Office 365.

Check which features you have and how the policies reach your users. Having a product in your subscription doesn’t mean every mailbox is covered the way you expect.

1. Identify the licence and service

Record the mailboxes and collaboration services you’re protecting. Compare the purchased plan with Microsoft’s Defender for Office 365 service description.

Every Microsoft 365 business plan with Exchange Online mailboxes includes Exchange Online Protection. Microsoft 365 Business Premium adds Defender for Office 365 Plan 1, which other plans can buy as an add-on. Microsoft 365 Defender, the name in older articles, is now Microsoft Defender XDR, the suite that brings the Defender products together in the Microsoft Defender portal, including Defender for Endpoint for devices.

Name who reviews alerts and who maintains the configuration.

2. Verify policy coverage

Review the recipients included in preset or custom protection policies. Check priority, exclusions and any users outside the intended scope.

Microsoft’s preset-policy guide explains the available policy groups. Check which policies apply to a few real accounts, including someone who joined recently.

3. Check spam and impersonation handling

Review where suspicious messages are delivered or quarantined and who can release them. Include legitimate mail staff need, such as supplier invoices that keep landing in quarantine.

Test the release process with harmless examples. A message that reached the inbox from a familiar name still needs checking by phone or another known route if it asks for a payment change or a password.

If licensed, check the Safe Links policy and the applications where you expect it to apply. Microsoft’s overview describes the supported behaviour.

Confirm that staff understand a warning and can report a false positive. Don’t tell them every link is checked everywhere, or that a page that opens without a warning is safe.

5. Check attachment handling and release

Review the Safe Attachments configuration and how it interacts with the mail service’s malware checks. Microsoft describes attachment analysis in an isolated environment.

That covers attachments arriving by email. It doesn’t check every file staff download from the web, so keep endpoint protection in place. Decide who can release a quarantined attachment.

6. Account for an upstream mail service

If another service receives inbound mail first, document the routing and connector configuration. Have the mail administrator review authentication signals and bypass rules.

Enhanced Filtering for Connectors lets Microsoft see where a message came from before the upstream service handled it. Without it, Microsoft treats that service as the sender, and its spoofing and phishing checks are less accurate.

7. Practise staff reporting and follow-up

Give staff the built-in Report button in Outlook, and set where reports go in the Defender portal’s user reported settings. Check who receives a report and who investigates it, including when the usual person is away.

Run a harmless reporting exercise and record the result. Make sure the incident process also covers someone who followed a link or entered account information.

Repeat these checks after a licence, mail-routing or staffing change. Keep a note of what’s covered and any open exceptions with the person who looks after mail security.


Featured Image Credit