Forum Discussion
You no longer receive messages sent to Office 365 'Groups' that you are a member of
- Jul 25, 2018
Update (7/25/2018):
Thanks for all your feedback and sharing your concerns. Our mission is to help you be more productive at your work, and some users complained about their workflows being affected with this change.
Based on the feedback we've seen from our users on this post, we are working on making this option configurable for our users. We are adding a switch which can be toggled by the user to start receiving their sent emails to Groups back in their inbox.
The exact details on how this setting can be used and the timeline for this change will be communicated soon. Thanks for your patience.
Bruce Wilson - totally understand your concern. But, to clarify, this behavior *only* affects O365 Groups in Outlook and NOT distribution lists (DLs).
For DLs, the email sending behavior continues to behave the same way it has always been. If a sender emails a DL, the sender would receive that email back in his/her inbox. The item would also be present in the sender's sent email folder.
One big advantage of O365 groups in Outlook vs. DLs is that the former has an archive & history of all the conversations that have taken place in that group. This conversation archive is equally visible to each member of the group at any time. Hence, the additional email that sender receives back in their inbox becomes superfluous. This conversation history/archive is not available for DLs. We had received a lot of user feedback around this superfluous email sending behavior and we have corrected it for Groups in Outlook.
You speak about workflows that get triggered once the sender receive their email back in their inbox. Though this won't break the behavior for DLs but for Groups, have you explored using Flow Automation to trigger some of these workflows? (https://flow.microsoft.com/)
This really should have been implemented as an option, not something forced.
It doesnt really seem consistent to have the new o365 groups NOT work like on prem DLs do.
This behavior is\was expected, and a mix of people want\dont want it, so really should have been optional not some random global change.