Fix redirection limit for mails within Office 365
I manage two different Office 365 tenants for two different companies.
Several years ago I created a forwarding rule that behaved in the following way:
- incoming email to email@example.com
- inbox rule within firstname.lastname@example.org forwards all incoming mails to email@example.com
- inbox rule within firstname.lastname@example.org forwards all incoming mails to email@example.com, firstname.lastname@example.org
This worked fine until recently: sometimes rules work as expected, but most of the time mails get into email@example.com and get forwarded to firstname.lastname@example.org. Afterwards the email is not forwarded to user1 and user2 anymore.
After investigation by Microsoft Support I was informed that the limitation for redirecting mails (https://technet.microsoft.com/en-us/library/exchange-online-limits.aspx#TransportRuleLimits) is not limited to a single tenant - instead it is measured across all Office 365 tenants.
My understanding is now, that an email entering an Office 365 tenant can only be forwarded once within Office 365 - even if the mail is forwarded to a completely different organization/tenant (also on Office 365) and this target organization want's to forward an email internally as well. The target tenant organization is unable to automatically forward an email once again when it has already been forwarded by the originating office 365 tenant.
As more and more organizations move to Office 365 it is not acceptable that an organization/tenant is unable to forward an email within it's organization using an automatic inbox rule IF the mail was forwarded before within another organization/tenant on Office 365. The organization/tenant unable to forward the email will be unable to find out why the inbox rule does not work - so there is no clear indication visible wether or not the email has been forwarded already within an Office 365 tenant.
Case 616050394743908 provides some insight on this bug. Microsoft support recommended to put this in as a feature request.
A functionality that worked fine for the past years until a few months ago has been disabled without notice and now we need to vote that such a bug get's fixed.
Is this for real?
Has anyone found a work around yet?
How is this still not fixed. Why should what another company does effect my ability to structure my email system in the manner I want. The most dangerous thing here is there is no errors so if an email comes in or a client changes to O365 things get lost
**** mailbox so it doesn't float
Todd Overbay commented
Is there any updates on this? We need at least a 3 redirect limit !!!!