Forum Discussion
Solved
Remote Domains, Automatic Forwarding, and ForwardingAddress VS ForwardingSMTPAddress
The many ways to block automatic email forwarding in Exchange Online Reducing or increasing information flow to another company Forward email from Office 365 to another email account Configure ...
- I had the realization of the explanation for the 'why' - ForwardingAddress takes only existing recipients (RecipientId) and so if the specified recipient happens to be a MailContact / MailUser with an ExternalEmailAddress, well that is no longer 'automatic forwarding' to the remote domain, the forwarding was to the internally existing recipient, so the external email address of that recipient is not part of the AutoForwardEnabled evaluation.
ForwardingSMTPAddress takes an SMTP (email) address, not a RecipientId, so suddenly this address is part of the evaluation.
The main thing that isn't documented is just that even if an administrator sets ForwardingSMTPAddress, it's still subject to Remote Domain AutoForwardEnabled.
I'll see if I can get this into the docs I linked earlier via GitHub issues (where possible).
I had the realization of the explanation for the 'why' - ForwardingAddress takes only existing recipients (RecipientId) and so if the specified recipient happens to be a MailContact / MailUser with an ExternalEmailAddress, well that is no longer 'automatic forwarding' to the remote domain, the forwarding was to the internally existing recipient, so the external email address of that recipient is not part of the AutoForwardEnabled evaluation.
ForwardingSMTPAddress takes an SMTP (email) address, not a RecipientId, so suddenly this address is part of the evaluation.
The main thing that isn't documented is just that even if an administrator sets ForwardingSMTPAddress, it's still subject to Remote Domain AutoForwardEnabled.
I'll see if I can get this into the docs I linked earlier via GitHub issues (where possible).
ForwardingSMTPAddress takes an SMTP (email) address, not a RecipientId, so suddenly this address is part of the evaluation.
The main thing that isn't documented is just that even if an administrator sets ForwardingSMTPAddress, it's still subject to Remote Domain AutoForwardEnabled.
I'll see if I can get this into the docs I linked earlier via GitHub issues (where possible).
That, and the fact that only admins can set the ForwardingAddress property on a mailbox.
- Thanks and good point. I think they do mention that in one of those articles I linked, but in its own context, not quite in relation to Remote Domain, and possibly not quite as concisely.
I'll make sure to point it out when suggesting edits.