Send email to private channel

%3CLINGO-SUB%20id%3D%22lingo-sub-1083316%22%20slang%3D%22en-US%22%3ERe%3A%20Send%20email%20to%20private%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1083316%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F501887%22%20target%3D%22_blank%22%3E%40Wim_Vanhove%3C%2FA%3E%26nbsp%3B%20Check%20these%20settings%20in%20teams%20admin%20console%2C%20they%20must%20be%20enabled%20for%20this%20to%20work.%3C%2FP%3E%3CP%3Eorg-Wid%20Settings%20--%26gt%3B%26nbsp%3B%20teams%20Settings%20-%26gt%3B%20Email%20integration%26nbsp%3B%20-%26gt%3B%26gt%3B%20%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3E%3CSPAN%3EAllow%20users%20to%20send%20emails%20to%20a%20channel%20email%20address%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FOL%3E%3CDIV%20class%3D%22settings-grid__cell___32ofo%20settings-grid__control___IfaDJ%22%3E%3CDIV%20class%3D%22styles__root___2dDCK%22%3E%3CDIV%20class%3D%22styles__container___bu6XU%22%3E%3COL%3E%3CLI%3E%3CSPAN%3EAccept%20channel%20email%20from%20these%20SMTP%20domains%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1083408%22%20slang%3D%22en-US%22%3ERe%3A%20Send%20email%20to%20private%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1083408%22%20slang%3D%22en-US%22%3EI%20think%20that's%20not%20the%20issue...by%20default%20we%20can%20send%20e-mails%20to%20any%20channel%20in%20Microsoft%20Teams%20so%20something%20IMHO%20is%20not%20right%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1083445%22%20slang%3D%22en-US%22%3ERe%3A%20Send%20email%20to%20private%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1083445%22%20slang%3D%22en-US%22%3EI%20can%20reproduce%20this%20as%20well.%20Seems%20to%20be%20a%20bug.%20You%20can%20send%20to%20the%20e-mail%20from%20outside%20the%20org%20with%20external%20e-mail%20fine%2C%20just%20seems%20to%20be%20something%20checking%20e-mails%20with%20your%20domain%20and%20not%20sending%20them%20through.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1084152%22%20slang%3D%22en-US%22%3ERe%3A%20Send%20email%20to%20private%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1084152%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F133392%22%20target%3D%22_blank%22%3E%40Safeer%20khan%3C%2FA%3E%26nbsp%3Bthanks%20for%20your%20reply%3C%2FP%3E%3CP%3EWe%20checked%20all%20settings%20and%20everything%20is%20as%20it%20should%20be.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1084153%22%20slang%3D%22en-US%22%3ERe%3A%20Send%20email%20to%20private%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1084153%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3Bgood%20to%20hear%20that%20we%20are%20not%20the%20only%20ones%20with%20this%20problem.%3C%2FP%3E%3CP%3EI%20can%20also%20send%20emails%20to%20the%20private%20channel%20from%20another%20domain%20without%20a%20problem.%3C%2FP%3E%3CP%3EI%20will%20ask%20our%20users%20to%20do%20this%20as%20a%20work%20around.%3C%2FP%3E%3CP%3EWe%20will%20open%20a%20ticket%20at%20Microsoft%20support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1122606%22%20slang%3D%22en-US%22%3ERe%3A%20Send%20email%20to%20private%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1122606%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F501887%22%20target%3D%22_blank%22%3E%40Wim_Vanhove%3C%2FA%3E%26nbsp%3BHave%20you%20received%20any%20solution%20to%20this%20from%20Microsoft%3F%20We%20have%20the%20same%20issue%20with%20only%20members%20being%20able%20to%20email%20private%20channels.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1083280%22%20slang%3D%22en-US%22%3ESend%20email%20to%20private%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1083280%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20created%20a%20private%20channel.%3C%2FP%3E%3CP%3EI%20go%20to%20%22more%20options%22%20-%20%22Get%20email%20address%22%20and%20then%20%22advanced%20settings%22.%3C%2FP%3E%3CP%3EI%20then%20see%20the%20following%20three%20options%20which%20are%20the%20same%20as%20for%20a%20standard%20channel.%3C%2FP%3E%3CUL%3E%3CLI%3E%26nbsp%3BAnyone%20can%20send%20emails%20to%20this%20address.%3C%2FLI%3E%3CLI%3E%26nbsp%3BOnly%20members%20of%20this%20team.%3C%2FLI%3E%3CLI%3E%26nbsp%3BOnly%20email%20sent%20from%20these%20domains.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EAlthough%20the%20first%20option%20is%20selected%20only%20people%20who%20have%20access%20to%20this%20channel%20can%20send%20emails.%20People%20who%20do%20have%20access%20to%20the%20team%20but%20not%20to%20the%20private%20channel%20cannot%20send%20emails%20to%20this%20private%20channel.%20As%20a%20result%20it%20is%20not%20%22Anyone%22.%3C%2FP%3E%3CP%3EIs%20this%20a%20bug%20or%20is%20this%20works%20as%20designed%3F%3C%2FP%3E%3CP%3EIf%20it%20works%20as%20designed%20then%20why%20does%20is%20say%20%22Anyone%22%3F%20And%20is%20there%20a%20workaround%20so%20that%20people%20who%20do%20not%20have%20access%20to%20the%20private%20channel%20can%20send%20emails%20to%20this%20channel%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpdate%20%3A%3C%2FP%3E%3CP%3EWe%20added%20our%20domain%20name%20in%20the%20%22Email%20integration%22%20at%20%22Accept%20channel%20email%20from%20these%20SMTP%20domains%22.%3C%2FP%3E%3CP%3EThis%20solves%20the%20problem%20for%20private%20channels%20in%20new%20Teams%20that%20are%20created%20after%20we%20added%20our%20domain.%3C%2FP%3E%3CP%3EBut%20this%20doesn't%20solve%20the%20problem%20for%20an%20existing%20private%20Channel%20in%20an%20existing%20Team.%20Also%20the%20problem%20remains%20for%20a%20new%20private%20Channel%20created%20in%20an%20existing%20Team%20(Team%20created%20before%20we%20added%20the%20domain).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1083280%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

I have created a private channel.

I go to "more options" - "Get email address" and then "advanced settings".

I then see the following three options which are the same as for a standard channel.

  •  Anyone can send emails to this address.
  •  Only members of this team.
  •  Only email sent from these domains.

Although the first option is selected only people who have access to this channel can send emails. People who do have access to the team but not to the private channel cannot send emails to this private channel. As a result it is not "Anyone".

Is this a bug or is this works as designed?

If it works as designed then why does is say "Anyone"? And is there a workaround so that people who do not have access to the private channel can send emails to this channel?

 

Update :

We added our domain name in the "Email integration" at "Accept channel email from these SMTP domains".

This solves the problem for private channels in new Teams that are created after we added our domain.

But this doesn't solve the problem for an existing private Channel in an existing Team. Also the problem remains for a new private Channel created in an existing Team (Team created before we added the domain).

24 Replies
Highlighted

@Wim_Vanhove  Check these settings in teams admin console, they must be enabled for this to work.

org-Wid Settings -->  teams Settings -> Email integration  ->>  

  1. Allow users to send emails to a channel email address
  1. Accept channel email from these SMTP domains
 
Highlighted
I think that's not the issue...by default we can send e-mails to any channel in Microsoft Teams so something IMHO is not right
Highlighted
I can reproduce this as well. Seems to be a bug. You can send to the e-mail from outside the org with external e-mail fine, just seems to be something checking e-mails with your domain and not sending them through.
Highlighted

@Safeer khan thanks for your reply

We checked all settings and everything is as it should be.

Highlighted

@Chris Webb good to hear that we are not the only ones with this problem.

I can also send emails to the private channel from another domain without a problem.

I will ask our users to do this as a work around.

We will open a ticket at Microsoft support.

Highlighted

@Wim_Vanhove Have you received any solution to this from Microsoft? We have the same issue with only members being able to email private channels.

Highlighted
Hi Par, no at the end we didn't open a support ticket. We will implement a work around.
Highlighted

@Wim_Vanhove Ok, we will open a ticket then. If we get some info I will share it here.

Highlighted

@Par Linderoth 
any updates from the ticket you opened?

 

Thanks!

Kat

Highlighted

@Kathryn Whiteley They are working on it but so far they haven't found anything explaining the problem.

Highlighted

We have the some problem, do you have any updates from the ticket? @Par Linderoth 

Highlighted

@Sindre95 Unfortunately not, I am still working with Microsoft on this.

Highlighted

Now it seems like we can't email any private channel that we are not a member of, no matter if the team is "old" or "new". Can anyone confirm in another tenant?

Highlighted

Finally got an answer from Microsoft:

 

Thank you for your patience as I worked through this with the senior technicians to confirm my findings in several tests reproducing the issue as well as reach out the development team for information. I am now able to confirm that this is functioning correctly and why it changed in mid-april for all tenants. 

     Previously Teams was not fully governed by the Exchange and Office 365 group rules, and the private Teams channels were still being modified as they were rolled out since their release last November, 2019. The original private channels for a few months were able to receive external to the private channel members emails. But with the changes rolling out since February 2020 Teams groups are now fully in line with Exchange and Office 365 groups. This means that private channels work the same way as private groups. If you are not a member of the private group, even if you have the email address for the channel, you will not be able to send messages to it. This is bound with the same rules that govern private Exchange and Office 365 groups. The changes to Teams was fully saturated as of mid April 2020 and this is why I have been able to reproduce in all of the different set ups of Teams. If a channel is public then you are able to message the group using the email, but not if it is private. 

 

I have already updated the team as to the findings as well as management and they will work to update the documents to explicitly state the connections and work to introduce the changes in a future update.

Highlighted
Glad we have an answer. But I actually still have a private channel that is receiving the occassional email from non-members (last one received was just overnight last night.)

Also, while I understand the philosophy, that answer is a bit disappointing. Our use-case was to use a private channel to manage (non IT) service requests via Teams. With a private channel we could keep the requests private from the rest of the organization, but able to assign to private channel members for resolution. Without this, we'll have to abandon Teams for this use-case.

Kat Whiteley
PATH
Highlighted
Yeah that makes no sense. You literally have an advanced option setting on private Team channels to specify that you want to allow e-mail from anyone......
Highlighted
Wait nevermind slept since this came up.... it's you can't send from people inside the org not in the channel that is the issue.
Highlighted
Well that works too, so I dunno, maybe newer private channels work? I just sent from external and internal user not in the Team to Private channel and it's working.
Highlighted

Microsoft's statements certainly seem to make no sense -- since we are still seeing email from non-team members being received within the private channels:
"...with the changes rolling out since February 2020 Teams groups are now fully in line with Exchange and Office 365 groups. <...snip...> The changes to Teams was fully saturated as of mid April 2020 and this is why I have been able to reproduce in all of the different set ups of Teams. If a channel is public then you are able to message the group using the email, but not if it is private."