What it observes

Whether mail can leave this organisation automatically, and which of the three controls that govern it are in which position.

FactWhat it carries
outbound_policiesEvery outbound spam filter policy, its name and its AutoForwardingMode
outbound_policies_ambiguousHow many of them sit on Automatic - System-controlled
remote_domainsEvery remote domain and its AutoForwardEnabled
remote_domains_allowing_forwardingHow many permit automatic forwarding
remote_domain_block_reachesWhat a block on a remote domain governs
mail_flow_rulesnot-supported: the third route, named and not read

Three gates, and no screen shows them together

Microsoft documents that these interact rather than override: "When one setting allows external forwarding, but another setting blocks external forwarding, the block typically wins."

ControlWhat it decides
The outbound spam filter policyWhether a user may forward externally at all
A remote domainWhere forwarded mail may go
A mail flow ruleCan forward regardless of either

A reader who has checked one has checked a third of the question.

One value does not carry its own meaning

AutoForwardingMode: Automatic was equivalent to On when it was introduced. In 2021 it became Off for new organisations and for existing organisations that were not actively using it, and stayed On for those that were.

Two tenants showing the same word have opposite behaviour, decided by the organisation's history rather than by anything readable today. Microsoft does not ask anybody to reason about it -- it says to stop using it: *"Because the behavior can differ by organization, configure On - Forwarding is enabled or Off

  • Forwarding is disabled instead of Automatic - System-controlled."*

That is read by EXO-FORWARD-001.

A block on a remote domain reaches half of it

AutoForwardEnabled: false overrides forwarding a user configured, through an Inbox rule or Outlook on the web. Microsoft states what it does not reach: "When admins use other methods to configure automatic forwarding for users, the forwarded messages aren't affected by the remote domain settings."

Mailbox forwarding an administrator configured, and mail flow rules, go anyway. So a tenant that blocked every remote domain and reported automatic forwarding is disabled described one of the two ways mail leaves. That is read by EXO-FORWARD-002.

What it does not read

  • Mail flow rules. Whether any of them forwards externally is a question about rule actions rather than about a forwarding setting, and it is a separate reading. Their absence is recorded as not-supported, not as none.
  • Per-mailbox forwarding. ForwardingSmtpAddress on a mailbox is what an administrator set, and enumerating it is a per-recipient reading.
  • Whether forwarding should be permitted. Many organisations forward deliberately, and Microsoft publishes no rule that it must be off.

A second surface exists and has not been compared

Microsoft Graph exposes hostedOutboundSpamFilterPolicy through Tenant Configuration Management, carrying the same AutoForwardingMode. The same setting is readable two ways, under different permissions, through a different endpoint. Whether they agree is a measurement nobody has made, and it is recorded as named rather than left unstated.

Sources

What the Engine publishes

Generated from the Engine's capability manifest at 1.0.0b8@c2aecc628b21. No value on this panel is maintained by this site.

Answers
whether mail can leave this organisation automatically, and which of the three controls that govern it are in which position
Collector
PnP PowerShell · mode Forwarding
Reads
  • Get-HostedOutboundSpamFilterPolicy
  • Get-RemoteDomain
Least privilege
  • Exchange.ManageAsApp
Produces
exchange ·tenant
Proven against a tenant
not live-validated

Rules that decide from it

  • EXO-FORWARD-001Automatic forwarding is set to a value whose behaviour is not in the valuedocumented-guidance
  • EXO-FORWARD-002A remote domain permits automatic forwardingdocumented-guidance

Contracts it produces

Every collection writes evidence and an account of itself. The manifest publishes no narrower per-capability list, so this states what it does establish rather than guessing at more.