Forum Discussion
Receiving email to teams channel
I have been trying to develop a solution which uses the Teams email address to deliver email content to teams channels. I have had mixed results with differing implementations.
Because the teams email addresses are not memorable, I have been adding a Mail Contact which references the Teams channel email address.
And then I create a Share Mailbox and forward mail for that Shared Mailbox to the Mail Contact.
This setup allows me to see when mail has successfully been delivered (in the Shared Mailbox) and whether or not the same content arrives in the teams channel.
It also allows me to add the Shared Mailbox user stub as a member of the Team which contains the teams channel - still not sure how relevant this is to my problem.
With this setup, I have had some mail come through to the Teams channel, and some mail not come through. And I can't tell what the difference is between mail that makes it and mail that doesn't.
It seems like anytime mail is sent from an internal member it goes to the Teams channel.
But if the sender is external, it might go in, and it might not go in, but it always makes it to the Shared Mailbox, so it isn't an email problem, it is a problem with the Teams channel not receiving some emails.
Can anyone advise on how to setup a memorable email address (like one on your own domain name) which forwards mail (reliably like 100% of the time) to a teams channel email address from external contacts?
I have already reviewed this article before anyone mentions it: https://support.microsoft.com/en-us/office/send-an-email-to-a-channel-in-microsoft-teams-d91db004-d9d7-4a47-82e6-fb1b16dfd51
I also have the email settings for the Team set to allow emails from outside, as well as having the most permissive and inclusive Teams and SharePoint settings.
If this Teams channel email address is meant to be a production feature, I must be doing something wrong, as it is completely unreliable.
- Messages send to a Teams channel address are routed through and processed in a "managed" Microsoft tenant, and we have zero visibility as to what happens therein. I'd avoid using this functionality for any critical processes.
As you are effectively forwarding external messages, it's likely that some protection feature is triggered, but you don't really have a way of knowing this. Best you can do is run a message trace, but even that will follow the message up to the point it was sent of the mail contact address.- I understand that fact, but it doesn't help with my problem at all.
I assume that since this is a documented seemingly production feature, it should work reliably.
I am wondering if my described experience is in fact a widespread bug and not due to some misconfiguration I have.
