Unable to get support for issue related to forwarded e-mails from Exchange Online to Teams Channel

%3CLINGO-SUB%20id%3D%22lingo-sub-2233227%22%20slang%3D%22en-US%22%3EUnable%20to%20get%20support%20for%20issue%20related%20to%20forwarded%20e-mails%20from%20Exchange%20Online%20to%20Teams%20Channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2233227%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20nine%20months%2C%20I%20had%20a%20workflow%20issue%20I%20solved%20by%20having%20a%20rule%20in%20Exchange%20Online%20for%20an%20e-mail%20account%20that%20forwards%20to%20a%20Teams%20channel%20that%20has%20e-mail%20enabled%20(xxxxxxxx%40amer.teams.ms).%26nbsp%3B%20In%20January%20it%20stopped%20processing%20some%20e-mails%20directed%20and%20broke%20my%20process.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20was%20an%20Exchange%20Online%20to%20Teams.ms%20issue%20and%20message%20traced%20and%20saw%20the%20messages%20being%20accepted%20by%26nbsp%3B%40amer.teams.ms%20and%20that%20was%20it.%26nbsp%3B%20I%20reviewed%20our%20security%20rules%20and%20determined%20the%20only%20e-mails%20that%20weren't%20being%20processed%20originated%20from%20systems%20with%20e-mail%20addresses%20ending%20with%20.local.%26nbsp%3B%20I%20opened%20a%20case%20with%20someone%20who%20had%20me%20go%20in%20circles%20making%20new%20SMTP%20addresses%2C%20new%20channels%2C%20new%20rules%2C%20etc...%20it%20went%20on%20for%20weeks%2C%20then%20she%20should%20me%20it%20has%20been%20escalated%20and%20they%20could%20reproduce%20my%20problem%20internally%2C%20then%20I%20didn't%20hear%20anything%20for%20a%20month%2C%20I%20told%20her%20it%20was%20still%20a%20problem%2C%20and%20the%20issue%20closed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20issue%20certainly%20has%20to%20do%20with%20something%20on%20the%20Teams%20side%20that%20doesn't%20like%20processing%20e-mails%20that%20end%20with%20.local%20on%20the%20domain%2C%20which%20was%20working%20fine%20up%20until%20January.%26nbsp%3B%20Something%20changed%20and%20if%20someone%20just%20could%20authoritatively%20tell%20me%20that%20Teams%20won't%20process%20an%20e-mail%20address%20forwarded%20from%20a%20legit%20Exchange%20Online%20address%20because%20it%20references%20an%20internal%20system%20ending%20with%20.local%2C%20that's%20fine.%26nbsp%3B%20It%20just%20is%20frustrating%20I%20can't%20find%20any%20publication%20indicating%20this%20change%20nor%20find%20someone%20technical%20to%20acknowledge%20and%2For%20suggest%20a%20workaround.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20any%20insights.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2233227%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMessaging%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

For nine months, I had a workflow issue I solved by having a rule in Exchange Online for an e-mail account that forwards to a Teams channel that has e-mail enabled (xxxxxxxx@amer.teams.ms).  In January it stopped processing some e-mails directed and broke my process. 

 

It was an Exchange Online to Teams.ms issue and message traced and saw the messages being accepted by @amer.teams.ms and that was it.  I reviewed our security rules and determined the only e-mails that weren't being processed originated from systems with e-mail addresses ending with .local.  I opened a case with someone who had me go in circles making new SMTP addresses, new channels, new rules, etc... it went on for weeks, then she should me it has been escalated and they could reproduce my problem internally, then I didn't hear anything for a month, I told her it was still a problem, and the issue closed.

 

The issue certainly has to do with something on the Teams side that doesn't like processing e-mails that end with .local on the domain, which was working fine up until January.  Something changed and if someone just could authoritatively tell me that Teams won't process an e-mail address forwarded from a legit Exchange Online address because it references an internal system ending with .local, that's fine.  It just is frustrating I can't find any publication indicating this change nor find someone technical to acknowledge and/or suggest a workaround.

 

Thanks for any insights.

2 Replies
.local isn't a legit email address. Does that help?

@Ed Woodrick  Thanks.  I understand that @*****.local isn't a valid address, but we'd been forwarding the e-mails from a valid Exchange Online address (@*****.com) for the better part of a year into a Teams Channel and no problems.  In January it just stopped.  Can't find any documentation, change notices, or anyone on support who'd say that's the case.  When I open support cases, they just go in circles, I'm told they can replicate it, and then a month later they close the ticket without explanation.