Microsoft 365 mailbox forwarding and inbox rule audit
Automatic forwarding is useful when a mailbox has a documented successor. It is also a common way a compromised account quietly sends copies of mail to an outside address. A regular audit looks at three places: mailbox (SMTP) forwarding, inbox rules, and the tenant policy that allows or blocks external automatic forwarding.
The three controls you are reviewing
| Control | What it does | Where it lives |
|---|---|---|
| Mailbox forwarding (SMTP forwarding) | An admin (or, in some cases, a user) sets the mailbox to forward to another address, with or without keeping a copy in the original mailbox. | Microsoft 365 admin center or Exchange. Official steps: Configure email forwarding and Exchange Online mailbox forwarding. |
| Inbox rules | Rules in the mailbox can forward, redirect or attach and send messages, or hide them by moving or deleting them. Users can create these in Outlook on the web, the Outlook desktop client, or an admin can create them in Exchange Online PowerShell. | Each mailbox. Microsoft documents how to list current rules and who changed them in Identify who modified mailbox rules. |
| Outbound spam policy (automatic forwarding) | This tenant (or policy) setting allows or blocks automatic forwarding to external recipients. It applies to both inbox rules and mailbox forwarding. Internal forwarding is not affected. | Defender / Exchange outbound spam filter policies. Official article: Control external email forwarding. |
Remote domains and Exchange mail-flow rules can also allow or block forwarded mail. If one control allows external forwarding and another blocks it, you will see confusing non-delivery reports (including 5.7.520). Read the "how these settings work together" section of the outbound-spam article before you change more than one control at a time.
1. Set the tenant default, then document exceptions
For most small tenants, the outbound spam policy should be set to Off - Forwarding is disabled, so automatic external forwarding is blocked and the sender gets an NDR. Microsoft advises against leaving the value on Automatic - System-controlled, because that default has meant different things in different organizations over time. Set On or Off explicitly.
If a business process truly needs external forwarding, put it in a documented exception (a more specific outbound spam policy, or a carefully scoped remote-domain or mail-flow exception), with an owner and a review date. Do not "temporarily" re-open forwarding for the whole tenant.
2. Inventory mailbox forwarding
In Exchange Online PowerShell, list mailboxes with a forwarding address or forwarding SMTP address set. The properties to look at are ForwardingAddress (usually another recipient in the tenant), ForwardingSmtpAddress (often an external address), and DeliverToMailboxAndForward (whether a copy stays in the mailbox). Microsoft's audit-log guidance for this scenario is in Search the audit log to investigate common support issues, which also shows how to clear unwanted SMTP forwarding with Set-Mailbox <mailbox> -ForwardingSmtpAddress $null.
Review every external target. Keep only entries you can match to a written request (for example, a leaver whose mail is being forwarded as part of user offboarding). Microsoft warns that if you rely on mailbox forwarding, you must not remove the license from that account, or forwarding stops and the mailbox is deactivated. A shared mailbox is often the cleaner option; see the offboarding guide.
3. Inventory inbox rules that send or hide mail
Microsoft's mailbox-rules article shows how to list rules on a mailbox:
Get-InboxRule -Mailbox <mailbox> | FL Name,Description,DeleteMessage,MoveToFolder,Enabled
When you audit for data leaving the tenant or for a hidden copy of mail, also look at actions that forward, redirect, or forward as an attachment, not only delete and move. Pay extra attention to rules that target external addresses, rules that delete or move mail after forwarding, and rules with odd names or that were created unexpectedly.
You do not have to inspect every mailbox by hand on the first pass. Start with privileged accounts, shared mailboxes, and recently risky sign-ins, then expand. On a tenant you just inherited, treat this as part of the previous-MSP handover.
4. Confirm who created or changed the setting
Current rules and forwarding tell you the state today. The unified audit log tells you who changed it and when, which is what you need if you think an account was compromised.
- For mailbox forwarding, search for
Set-Mailboxactivity and inspect the parameters forForwardingSmtpAddressandDeliverToMailboxAndForward, as Microsoft describes in the troubleshooting article above. - For inbox rules, search for
New-InboxRule,Set-InboxRuleandRemove-InboxRule(Outlook on the web and PowerShell). Changes from the Outlook desktop client appear asUpdateInboxRules. See Identify who modified mailbox rules and Manage mailbox auditing.
Audit (Standard) retains records for a limited period (commonly 180 days). If your investigation is older than that, you may not have the events unless Audit (Premium) or an export was already in place. Confirm the unified audit log is actually ingesting events as part of your regular tenant review.
Make it a repeatable control
Run this audit when you take over a tenant, after any suspected account compromise, and on a quarterly schedule with the rest of your identity and email checks. Record each exception, the owner, and the date you will look at it again. The forwarding and inbox-rule items sit in the email section of our quarterly Microsoft 365 security audit checklist. The Tenant Security Audit Kit includes them with where-to-verify paths and scoring so the review is not a one-off spreadsheet.