A Microsoft application for managing email, calendars, contacts, and tasks across devices and platforms.
Automatic disabling of forwarding rules is typically caused by security or anti-spam protections in the service configuration rather than a problem with POP/IMAP, safe senders, or the rule definition itself.
Based on the documented behavior, the following conditions can cause forwarding rules to be disabled or ignored:
- Outbound spam policy blocking automatic forwarding
In Microsoft 365/Exchange Online, if the outbound spam filter policy is configured with:- Off – Forwarding is disabled, then:
- Any Inbox rules or mailbox-level forwarding that send mail to external addresses (such as Gmail) are blocked.
- The sender receives a non-delivery report (NDR/bounce) when forwarding is attempted.
- This setting affects both user-created Inbox rules and admin-configured mailbox forwarding.
- Set the automatic forwarding option to On – Forwarding is enabled (or an allowed/controlled mode if available in the tenant) in the outbound spam filter policy.
Details are in the article on controlling automatic external email forwarding.
- Off – Forwarding is disabled, then:
- Remote domain configuration blocking auto-forwarding
If the target domain (for example, gmail.com) is configured as a remote domain with automatic forwarding disabled, Inbox rules that forward or redirect to that domain will not work. This is by design. An admin can check and adjust this in Exchange Online PowerShell:- List remote domains where automatic forwarding is disabled:
Get-RemoteDomain | Where {$_.AutoForwardEnabled -eq $False} - If the mailbox domain or the destination domain is listed there, use
Set-RemoteDomainwith-AutoForwardEnabled $Trueto allow automatic forwarding for that remote domain.
- List remote domains where automatic forwarding is disabled:
- Tenant-wide security design: automatic external forwarding disabled
The documentation notes that disabling automatic forwarding in outbound spam policies disables:- Inbox rules that redirect/forward to external addresses.
- Mailbox-level forwarding configured by admins.
- Other rule-related design behaviors (for completeness):
These may not match the described scenario exactly but can affect forwarding rules:- If mailbox-level forwarding is enabled with
DeliverToMailboxAndForwardset toTrue, redirect-type Inbox rules may not work as expected. Disabling mailbox forwarding (Set-Mailbox -DeliverToMailboxAndForward $False) is required if redirect rules are used. - If the rule forwards/redirects to more than 10 individual recipients, it exceeds the Exchange Online Inbox rule limit and must be changed to use a distribution group or Microsoft 365 group instead.
- If mailbox-level forwarding is enabled with
Because the problem involves forwarding to Gmail (an external domain) and rules being effectively blocked, the most likely cause is a tenant or service-level policy that disables automatic external forwarding. Resolution requires an administrator to:
- Review and, if appropriate, change the outbound spam filter policy so that automatic external forwarding is allowed.
- Confirm that the relevant remote domain configuration does not have
AutoForwardEnabledset toFalsefor the destination domain. - Ensure no conflicting mailbox-level forwarding is configured if redirect-style rules are being used.
If direct support channels and forms are not accessible, the documented path is to use the in-product Help/Support entry points (for Outlook.com or Microsoft 365) or the community/tech forums referenced in the documentation to escalate, since only service administrators can change outbound spam policies and remote domain settings.
References: