02-24-2017 04:49 PM - edited 04-07-2017 10:27 AM
02-24-2017 04:49 PM - edited 04-07-2017 10:27 AM
We have recently fixed the email sending behavior to a group, where senders had complained about receiving the emails they send to a group, back in their personal inbox. With this fix, senders will no longer receive the emails they send to a group, back in their personal inbox.
The primary complaints we heard were about reading the same message users sent to a group multiple times - in their sent messages, and their inbox.
We believe sending an email to a person or to a group should be consistent, and this circling back of an email from a group was just leading to confusion, unnecessary triage, and inconvenience for a lot of our users.
We understand that some users had started using this inconsistent behavior as a way to confirm if their emails were delivered to a group. An email sent to a group is already available in the group's conversation archive as well as in the sender's sent email.
Thanks for all your valuable feedback. Though a good majority of our users have embraced this change for Groups, there's also a section of our users who complained about this change affecting their workflows. We value all the feedback from our users and hence we are considering enhancing this feature to address the negative feedback. Please watch this space for further updates on this feature in the coming weeks.
02-25-2017 12:06 AM
02-25-2017 08:13 AM
In general that will be nice to have the notification about such updates in Admin Message Center. Another recently introduced change is updating default mailbox size from 50MB to 100MB - also there was no notification (except appearing it in Roadmap Rolling Out section). Or i missed something?
Another point is "More info" in Roadmap sometimes forwards us on outdated articles.
Anyway, perhaps above is for separate discussion in another thread. As for this feature have nothing against it except no notification was sent.
02-25-2017 08:18 AM
02-25-2017 08:34 AM
Found it, was published yesterday. When i missed the notification, sorry. Will try to find one about the change of mailbox size.
By the way, i guess that's not for you, but could you within Microsoft to unify the form for the message subject. Some starts from "Updated feature(s):..", some from "Feature(s) update:...". Not a big deal, just easier to check.
02-25-2017 08:38 AM
Perhaps I need to change my mobile on one with bigger screen... Or check the notifications more often, when i pay more attention to each of it.
03-10-2017 08:47 AM
I don't understand this upgrade - we have users complain that they don't get messages sent to groups in their inbox - so are we taking away the subscribe button too? I don't want to see this go away. Users want the group messages in their inbox.
03-10-2017 09:04 AM
Is there any way to reverse this change? I've got users who want the emails to keep coming to their own inbox
03-10-2017 09:32 AM
If the Office365 group is nested in a distribution list is the behavior the same? Seems inconsistent in what I have seen so far.
03-10-2017 11:14 AM - edited 03-10-2017 11:40 AMSolution
@Nicholas Williams - No, there is no effect to group subscription options with this change. Subscribed users will continue to receive all group conversations, messages and events in their inbox as usual.
The only effect of this change will be on the sender of the messages to groups as below.
I send a message to a group, or reply back to a message from a group. Message is delivered to the group and is available in the group's conversation archive. I would also receive my message in back my inbox.
I send a message to a group, or reply back to a message from a group. Message is delivered to the group and is available in the group's conversation archive. I would NOT receive my message in back my inbox.
Would be great if you can help us understand why your users are complaining with this change? What additional benefit does it provide to users when they receive their sent email back again in their inbox? Is it just a confirmation that the message was delivered to the group?
03-10-2017 11:17 AM
Hi @Joe Savage - Would be great if you can help us understand why you'd like to reverse this change? What additional benefit does it provide to users when they receive their sent email back again in their inbox? Is it just a confirmation that the message was delivered to the group?
We believe that sending messages to a group of people should behave the same way as sending messages to individuals. This change is made to achieve parity in email sending behavior to a person or to a group. When I send an email to a person, I do not receive that email back in my inbox. So why would i expect otherwise if I send that message to a group?
03-10-2017 11:36 AM
@Michelle Proper - can you help me understand the issue in detail - You're saying that you have a DL which has a Group as a member. When you send an email to that DL, you get that email back in your inbox? Is my understanding is correct?
We have not changed email sending behavior for DLs. If you send an email to a DL, you will receive this email back in your inbox. This behavior is only changed for Groups.
03-10-2017 11:58 AM
Yes, we have a DL that has an Office365 group as a member. One member of that Office 365 group sent an email to the DL yesterday and he didn't get a copy. I was curious if the new group functionality overrides the DL functionality and if someone wants a copy of the message they send to the DL they need to cc themselves.
03-10-2017 12:02 PM - edited 03-10-2017 12:03 PM
The post that you provided wasn't 100% clear - I completely understand now.
I would like to be able to "Force" Subscriptions to group converstations to users inboxes and not let them unsubscribe from the group conversations.
03-10-2017 01:19 PM
Yes, they would like to receive it as a confirmation it was delivered. I understand why this might be seen as unnecessary, but I still deal with a lot of users who frequently CC/BCC themselves on all emails as well which is similar. It's a bit redundant, but if it makes them more comfortable/ confident their message was received, I don't have a problem with it.
I agree that the new behavior makes sense for most people and should be the default, but I don't think it's unreasonable to ask that we be given the option to return to the previous behaviour if that's what is preferred by the user, especially since that's the way it's been configured for a while now.
03-10-2017 04:32 PM
03-13-2017 01:17 AM - edited 03-13-2017 01:18 AM
We were using Office Groups (and advertising them to users) as a direct replacement of distribution lists with extended capabilities. It was the only possibility to keep communication in desktop Outlook 2010 we still had on some PCs. For us it's not a confirmation of sending, but the message we can filter to a folder like a normal distribution list and reply to it. As we are upgrading from the last Office 2010 copies I try to convince users to the new Groups interface, but starting from "Microsoft broke something again" is not making my life easier.
In short - configuration option would be great. Getting this option FAST would be even better.
03-13-2017 10:50 AM
03-13-2017 01:16 PM
Is the recommendation the same for Office365 groups nested within the DLs? Were you able to confirm that the feature that doesn't cc the sender on an email to an Office365 group won't cc members of the Office365 group inside the DL and they need to cc themselves if they want the email?
03-13-2017 10:55 PM
At least in our company's case, O365 groups were considered an upgrade of simple distribution groups, with all the added features, something that we absolutely loved and therefore upgraded all distribution groups to O365 groups. So it would make sense for an upgraded distribution group to function/behave as its simple version does, but with the added benefit (as its supposed to be an upgrade) of being able to change this behaviour. Your argument about keeping sending to a person vs a group consistent I believe does not stand if you compare sending to a person, vs a distribution group the sender is a member of, vs an O365 group the sender is a member of. It is not consistent across the board there.
So please make this configurable as people are used to this way of this working as it did for ages now. It is clear and logical.
Also, please dont think you know whats best for how people work. When making such a change in your code that is not a fix to something that is broken, dont force it down to people's throats. Set it as default if that is what your telemetry tells you that people want, but also make it configurable so that people have a choice. Thank you for your hard work.
03-14-2017 10:55 AM
03-14-2017 11:38 AM
Dimitris, thanks for your feedback. I understand your inconvenience and apologize if this change does not help you be more productive. Rest assured, from the tens of millions of customers that we serve, we've received a bunch of positive feedback on this change and some negative feedback as well. I hope you understand that serving millions of customers and catering to each one of their needs is not the easiest things to do, but we're trying our best :)
You have provided very valid feedback and I assure you that we will consider it as we plan engineering work for the immidiate future. Please watch this space for more updates on this.
03-14-2017 05:51 PM
Sorry it doesn't. I see the behavior for the DLs and Groups as you have explained but when my co-worker sent an email to a DL that had an Office 365 group as a member he did not receive a copy of the email so it seems that the new feature will not copy the sender even if it is inside a DL. The DL (with the O365 group as one of the members) was the TO address for the email. I just wanted to confirm that is the expected behavior and not a bug or unintended consequence.
03-15-2017 03:57 PM
If I send an email to a group, it should go to everyone in the group. That's what groups are for. If I am a member of that group, I should get it as well. If I don't want to send something to everyone in the group, I won't send it to the group. This change makes no sense at all.
03-29-2017 02:29 PM
We began researching changes when our documents shared to a group no longer showed in the group conversation or any of the member's of that group's emails. It now only goes to the group's files. Everyone in the group is subscribed so they are alerted when changes are made to the group. They are no longer alerted. We can get it to show up if we attach a document and email the group, but not if it is shared directly with the group. It makes it confusing as to what will and what will not work. On another note, I liked receiving my own emails with the rest of the group.
03-30-2017 10:58 AM
This is a major change that our users were not expecting at. As a group collaborating together they were using the O365 groups in a certain way and working primarily out of their Inbox and all of a sudden they found that they are not receiving copies for the emails and have to communicate back and force between Inbox,, Sent Items.
At least 10 complaints so far from our users.
04-07-2017 08:44 AM
Does this apply to traditional distribution lists as well? I am still seeing the behavior when I email a distribution list I am a member of I also receive the email in my inbox.
04-07-2017 10:21 AM
04-07-2017 11:59 AM
Sending to a group should still go to all of the group, regardless of whether it's a traditional distribution list or not.
04-07-2017 12:05 PM
04-10-2017 10:34 AM
The behavior we are experiencing is if the O365 group is nested in the DL, the sender will not recieve the message either. In order for the sender to get the message they must be listed individually in the DL or cc themselves on the message.
04-10-2017 11:54 AM
04-10-2017 12:35 PM
The sender is not a part of the DL individually but a member of the group nested in the DL. It seemed easier to add the group instead of everyone one by one but sounds like we should add them one by one since the group behavior is different than the DL. Thank you for confirming.
04-11-2017 01:35 AM
As a teacher I set up each one of my class sets as a group. I do not like this change as when I used to send a message to a group the email that was sent to my inbox was a quick way to know that a email notification has been sent to each student in the group. Now, I am uncertain if they have recieved a notification, not handy for me but a good get out clause for the students. I can no longer say 'I got the email so you must have as well!'
On another note, I have spent quite a few hours trying to findout what had been changed when I noticed, last week, that group email notifications were not being sent back to me as the sender. I did not find any notice about this change and only came across this thread today.
Please confirm, will all members of the group, excluding the sender, recieve an email to alert them to a new/reply to a conversation. And is there a way to reverse the change for the reasons stated above.
04-11-2017 10:41 AM
04-20-2017 09:41 PM
Is this change world wide yet? I have some tenants where the change has not taken place.
04-21-2017 11:11 AM
04-24-2017 05:25 PM
04-24-2017 05:29 PM
05-29-2017 02:26 AM
Still not fixed. We've been testing the behavior of the Group Conversations, and still any message within a conversation goes to the Group but also the the personal Inbox of any of the gorup members. When I hit the "message" button, the Recipients automatically include both the group email and also each group member email address.
The groups we tested are all created without the option of subscribing new members. We've tried Subscribe (afterwards) and Unsubscribe, but there is not difference. Each message in the group conversation goes to he personal Inboxes as well.
We have recently started working with Office 365, and this group conversation feature seemed very useful and attractive, but now it is simply annoyong the way it behaves.
Is there any solution forseen for this?
07-18-2017 06:07 AM
Any news on the ability to configure Office 365 groups so that the sender receives the email? I have users that really, really want that ability.
07-27-2017 09:03 AM
I'm having this problem with a newly created distribution group. Members of the group are recieving emails which they sent out. I've seen no settings in the Admin panel to control this behaviour.
07-27-2017 03:04 PM
07-27-2017 03:06 PM
07-28-2017 05:54 AM
The use case is the very typical use case of every email user for the last twenty years or longer.
You define a group. In that group is user firstname.lastname@example.org email@example.com and firstname.lastname@example.org
User email@example.com sends an email to the group. User firstname.lastname@example.org expects, since their email is in the group, to recieve the email they just sent to the group. Again - as has always happened for many decades. Why is this difficult to understand and why does it cause consternation among Microsoft developers?
07-28-2017 11:28 AM
Thanks for the explanation, @Matt Verner.
I partially understand the need, and I would like to clarify that this change was deliberate from Microsoft. It was difficult with distribution lists to track the mesaages sent to a DL, but with Groups, we have made that very easy by visiting the Group and looking at the conversations list. Any message sent to the Group will be available instantly to view in the group's conversation archive. This obviates the need of a bounce-back email to the sender if the purpose is purely to confirm whether the mail was delivered to the group.
Please do let us know if you are using the bounce-back email for triggering some workflows in your org, or is it just a means to confirm delivery?
07-28-2017 11:36 AM
07-30-2017 03:34 AM
Does it matter why is @Matt Verner asking for that functionality back? He and his users (as well as the rest of us) had it before and were "robbed" of it, just because. Again, make this behaviour CONFIGURABLE, this is the secret to keeping not just the majority but ALL of your clients happy, unless you like these confrontations for some reason.