Critical Issue: Forwarding Rules disabled and Support is unreachable

Edhar Petrosian 0 Reputation points
2026-04-20T14:15:03.3766667+00:00

Hello Outlook Support Team,

I am writing to report a serious technical issue that is affecting my business operations. My email forwarding rules are being automatically disabled by the system every time I try to enable them.

I previously tried to resolve this using your automated guide and support tools as suggested, but I cannot even reach the technical support form or chat — the system keeps looping or blocking my access. I have attached a screenshot to prove that your standard support path is inaccessible to me.

The issue:

  1. My rule "Forward to Gmail" (forwarding emails from Eldorado/TalkJS to Gmail) is being turned off by Outlook automatically.
  2. I have already performed the "Sign in and verify" step multiple times, but it doesn't help.
  3. POP/IMAP are enabled, and senders are in the "Safe list", but the rule still gets disabled.

I am a digital entrepreneur and missing these notifications costs me money. Please manually review my account security flags and stop the system from disabling my forwarding rules.

Thank you.

Outlook
Outlook

A Microsoft application for managing email, calendars, contacts, and tasks across devices and platforms.


1 answer

Sort by: Oldest
  1. AI answer

    2026-04-20T14:15:28.7766667+00:00

    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:

    1. 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.
      To allow forwarding to Gmail, an admin must configure the outbound spam policy to permit automatic external 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.
    2. 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-RemoteDomain with -AutoForwardEnabled $True to allow automatic forwarding for that remote domain.
    3. 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.
      Internal-to-internal forwarding (within the same organization) is not affected by this setting, but forwarding to Gmail is considered external and will be blocked when this protection is turned off.
    4. 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 DeliverToMailboxAndForward set to True, 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.

    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:

    1. Review and, if appropriate, change the outbound spam filter policy so that automatic external forwarding is allowed.
    2. Confirm that the relevant remote domain configuration does not have AutoForwardEnabled set to False for the destination domain.
    3. 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:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.