Email Security
Control External Email Forwarding
Check where Exchange Online mail is being forwarded outside your organization. Block unapproved forwarding and document any business exceptions.
Content review: 2026-09-22 · Estimated effort: Medium
Priority and effort are suggestions, not risk scores or deadlines. Check business impact, vendor instructions, licenses and obligations before making changes. Test before wider rollout.
Before you start
Before starting: identify the Exchange administrator, mail-flow owner, and business approver. Record current policies and forwarding settings in a protected location. Ask about ticketing, finance, and outsourced support workflows before changing them.
Put it into practice
- Review mailbox-level forwarding and user inbox rules, including shared mailboxes. Also inspect mail-flow rules and connectors separately: one forwarding control does not cover every route mail can take. Record each external destination, business purpose, data sensitivity, owner, and approval; investigate unexpected rules as possible compromise.
- Prefer access to a controlled shared mailbox or an approved collaboration workflow over forwarding business mail to personal inboxes. Obtain data-owner approval before retaining an external destination. Preserve relevant evidence before removing suspicious rules and follow your incident response process if compromise is suspected.
- In Microsoft Defender, review the applicable outbound anti-spam policy's Automatic forwarding rules setting and explicitly disable unapproved external automatic forwarding. Check policy scope and precedence. This control is available with built-in cloud-mailbox protection; it is not a blanket requirement to buy Defender for Office 365.
- If an exception is necessary, restrict it to approved senders and destinations using the applicable policy and remote-domain controls. Record an expiry and reviewer. Other blocking controls can override an allow setting; test the effective combination rather than assuming the exception works. This does not prevent a user manually sending mail externally.
- Verify: with synthetic messages and test mailboxes you control, confirm unapproved forwarding is blocked, approved workflows function, and ordinary mail delivery continues. Inspect message trace or non-delivery reports and check the destination inbox. Keep an evidence summary, not real customer email.
- If a business workflow fails: contact its owner and restore only an approved, narrow route while correcting the dependency. Avoid enabling unrestricted forwarding for the entire organization. Repeat the review after mailbox ownership changes and investigate newly created unexpected forwarding rules.
Use what you have
Tools and templates
“Included” tools require an eligible product or subscription. Options reviewed 2026-09-22; check current vendor terms.
Start without another software subscription
Use the outbound forwarding controls included with an eligible Microsoft cloud mailbox service and the free change worksheet.
What to account for: Basic desktop Office alone does not include Exchange Online. If mail is hosted elsewhere, use that provider’s controls; no free desktop app can enforce forwarding policy for a hosted mailbox.
Allow for equipment, storage and staff time. Eligibility details are linked below.
Microsoft Defender outbound anti-spam policies
Included cloud-mailbox protection; no Defender for Office 365 upgrade needed for this control
Review Automatic forwarding rules in the applicable outbound anti-spam policy, alongside inbox rules and mailbox forwarding.
Limits: Requires administrative permissions and an applicable Microsoft cloud mailbox service. Other mail-flow controls can override exceptions; this does not block manual external sending.
Your information: Policies and message trace are in your existing Microsoft service. Record test summaries rather than customer messages.
Official instructions: Microsoft Defender outbound anti-spam policies ↗Download a working template
Open the Excel or Word file using your existing Microsoft Office license. Replace fictional entries, fill in the blanks and save your own copy. These manual worksheets have no macros, scoring or automatic verification.
- Security change and verification record (Excel (.xlsx)) ↓
Plan one scoped change per row, including prerequisites, recovery, test expectations and actual results. An untested change is not a verified success.
Fictional worksheet preview: Security change and verification record Change ID Proposed change Actual test results EXAMPLE-CHANGE-01 Test an approved MFA policy in a limited scope Not tested Three columns shown. The full worksheet also records prerequisites, expected behavior and recovery steps. Confirm permissions and recovery access before making changes.
Fictional worked example
Use these invented entries as a guide when filling in your worksheet. They are not a customer story or lab result. Record what you observe in your own checks.
A team wants to prevent a mailbox automatically forwarding customer messages externally.
Use the Security change and verification record template.
What to enter before testing
- Change ID
- EXAMPLE-FORWARD-01
- Service and scoped recipients
- Authorized test mailbox and controlled external destination
- Expected allowed and blocked behavior
- Normal mail works; unapproved automatic external forwarding is blocked
- Actual test results
- Not tested
How to verify
With approval, use harmless mail and controlled accounts to test applicable forwarding rules, mailbox forwarding and policy behavior. Inspect trace or failure evidence and confirm normal mail delivery. Clean up temporary test rules afterward.
If the result is unexpected
If forwarding succeeds, check which policy applies and other mail-flow controls. If legitimate workflows fail, review a narrowly scoped approved exception. Automatic-forwarding controls do not prevent a person manually sending mail externally.
Keep completed worksheets private. Leave out passwords, recovery keys and confidential messages. This site does not receive your edits, but a cloud editor or synced folder may send them to its provider.
Sources and review approach
These guides use selected NIST CSF 2.0 alignments. They are not official crosswalks or complete framework implementations. We have not tested these steps in your environment.
- NIST CSF 2.0: PR.DS-02: protecting confidentiality of data in transit by controlling forwarding
- NIST CSF 2.0: PR.PS-01: managed mail configuration
- https://www.nist.gov/publications/nist-cybersecurity-framework-csf-20 ↗
- https://learn.microsoft.com/en-us/defender-office-365/outbound-spam-policies-external-email-forwarding ↗