10-14-2019 08:18 PM
Just found out that do not send a response doesn't update organizer's list in addition to not sending email. I would suggest changing the wording - because if people previously figured out how it worked they would need a cue that the behavior changed. Personally wouldn't want to choose the 'same' option again from being burned in the past.
10-29-2019 03:48 PM
Someone brought up the topic of when you would want to accept but not have your attendance registered, and that is something I used to think of when I would accept and not send the response. The idea was that I would be adding it to my calendar for awareness but would not want to be considered as acknowledging that I would be there to represent my team. (On a change control, for example). Now I just use Tentative for that. I think if the invitee's response is always going to be registered with the organizer, then Accept/Tentative/Decline is all that anyone would need and the default should be to not send an email reply.
10-29-2019 05:17 PM
@Julia Foran it's nearly been 9 months since you said "We do plan to make this change in Outlook 2016 for Windows" and still not ETA on when it will be delivered to Office 365 members.
Why is it taking so long?
I would have thought Outlook for Windows would be the first client you updated as it has been around the longest...
11-07-2019 01:50 PM
Any news on this? Last update was 2018 and this would be a great change for us. We do a lot of lunch and learns and email 400 people in the office. I don't want 400 emails coming my way but I'd really like to know who's actually coming by checking the scheduling assistant.
11-19-2019 04:18 PM
11-20-2019 01:43 AM
From my point of view is the approach suggestion a topic which has to be redesigned in the way as proposed. To accept an invitation without an sending a response is necessary but without an acceptance in the tracking tool is a no-go and creates confusion on invitation organizer side. Best regards, JPH
11-20-2019 12:02 PM
The difference in behavior for users who are on Office 365 and not is maddening. This seems to address that change. I like it.
Right now, if group calendar at Org 1 sends a meeting to someone at Org2 (also on O365) and the person responds Accepts, the Org 1 meeting organizer recieves no notification at all. I'm under the impression this is by desgin. But that means a portion of the extenal invites send mail responses and those on Office 365 do not.
11-20-2019 03:53 PM
11-20-2019 03:54 PM
11-20-2019 04:19 PM
@Julia Foran saying you are still in progress is not an update, especially when it shouldn't even take 2 months to implement let alone over a year. Like I have been saying all along the Windows update should be first as that was the first email platform.
So roughly when will this massive issue for thousands of people be fixed? I know it's not going to be this year but I would hope that it is VERY early 2020.
12-03-2019 11:29 AM
12-03-2019 04:41 PM
@Julia Foran clearly people only come to this thread when they find out the hard way (myself included) that the meeting invite is not updated when you select "Accept & Do Not Send a Response". It has had 62.7k visits with 163 replies which are the people that take the time to setup an account or login. This should have been fixed for Office 365 customers on a PC many months ago, especially considering we are coming up to 2 years since the issue was first identified.
12-04-2019 02:19 AM
@Lucien Riviere Clearly, Everyone, MS are stalling. They could have fixed this, probably overnight. Its a tweak: One has the option of sending a reply that is tracked with an accompanying email or sending a reply that is (contrary to advice) not tracked with no accompanying email. We want a combination of the two: MS if you are reading.... a reply that tracks that doesnt send an email. But I suspect you are holding out for Windows 11 or whatever, when you can charge us loads more for 'fixing' something that never made sense in the first place. Please lets not be here next month cos that will be 2years!!! How about a seasonal gift to your loyal users...??
12-04-2019 04:29 PM
@Lucien Riviere well said, that sums up exactly what is happening. There are no other logical reasons as to why they are dragging their feet. Windows should have been the first platform as that is where it all began. Unless they are fixing the hardest last as it has been around so long and does not adapt well in the rapidly changing IT world. I learnt a long time ago to start with the hardest issues first as your customers will be happy for it. @Julia Foran does read the messages but strangely this issue is not a high priority so she takes a few weeks to reply. I used to joke about it at work that it will be fixed by Xmas but sadly that is not going to happen.
12-05-2019 06:55 AM
@Julia Foran I cannot believe that this how Outlook works. Expected behavior is that when a recipient clicks "do not send a response" it still records the response on the sender's Outlook, it just doesn't send an email. I just found out that Outlook does not do this and cannot believe this is how it works. It's a big miss in my opinion.
As for the second question, here I think if the Sender does not request responses, it means they do not care whether you are coming or not, so it's OK for the response not to be recorded.
12-05-2019 07:14 AM
@Julia Foran I was shocked to find out that this how Outlook works. I echo the statements of others above that the expected behavior is that when a recipient clicks "do not send a response" it still records the response on the sender's Outlook, it just doesn't send an email.
Please fix this ASAP and provide an ETA, so I don't have to educate all of my staff to do something different to address this "flaw" only to have it corrected within a month.
12-05-2019 08:19 AM
1. Yes, and I was using that option always expecting it was recorded my response without sending an email.
Just today after years I found that it was marked as 'None' and was searching why. So I like that change, I talked with others and 50% thought that it was recording the response as accepted.
2. Yes, the intention is to avoid email responses, but expected that it will mark the response.
12-05-2019 08:24 AM
1) Yes - this change would be valuable because many people think they are being courteous to the organizer by accepting, but not clogging up the organizer's Inbox.
2) As an Organizer, I only do not ask for resposnes when it's an OOO invite.
01-08-2020 01:54 PM
I'm relatively new to this community, but I discovered this myself independent of the Tech Community. I wrote an article about this explaining this to my Blog followers and Linked In followers and the overwhelming response has been that when people accept a meeting response, they then assume the organiser is then aware they are attending, but choose "Do not send a response" so as to avoid another email being sent. I notice this is still happening, so not sure where this is at, but hopefully it will change soon. Here is the article I wrote btw...it was very popular on Linked In among my followers! https://www.lingfordconsulting.com.au/ms-outlook/accepting-outlook-meeting-correctly
01-12-2020 11:16 AM
Thank you for all your responses and your passion around what the expected behavior is. The Outlook team also agrees with you that "do not send a response" should still update the organizer and just not send an email.
As I'd posted previously, we have fixed this behavior for all Outlook clients except for Outlook for Windows. We know that Windows is our predominant client, and we certainly don't consider ourselves "done" until it's released on Outlook for Windows.
Unfortunately, it's not a simple fix that can be made quickly in the Windows client.
First, I'll explain what we changed that fixed this for the other clients (Mac, Mobile, Web). These clients call modern APIs that go through the Outlook Calendar service before the response status is saved into the attendee's copy of the event on the Exchange store. That service layer contains business logic to handle behaviors like this flow. For any Accept, Tentatively Accept, or Decline commands where the service sees that no response was sent, a server-to-server call is made to the organizer's mailbox to update their tracking list. This S2S call is why the "do not send a response still updates organizer" functionality is only supported when the attendee and the organizer are both in Office 365.
However, the Outlook for Windows client uses a legacy api (MAPI) that saves the response directly into the Exchange store (and does not go through the Outlook Calendar service today). When this happens, the S2S call is not made, so the response status is only saved for the attendee and does not make its way to the organizers tracking list.
The good news is that Outlook for Windows has been working on modernizing the way that they make calendar calls such that they will use the modern Graph APIs to create, update, respond to, and generally manage calendar events. This is not simply changing the call URL path from MAPI to REST. The two APIs are massively different in the ways that they are executed, and requires re-writing the calendar almost from scratch. When Outlook for Windows moves to the Graph APIs, the "do not send a response" behavior will automatically start happening for its users, because now all calendar calls will go through the Outlook Calendar service (and the S2S call will be executed).
The "do not send a response" is not the only benefit users will see with this update. For example, when you change the end date of a recurring series, all the past exceptional instances will be preserved (already supported in the other Outlook clients). Today, with MAPI, the entire series is reset if you just want to shorten or extend it by changing the end date.
I wish I could provide a date for when these changes will be released, but we do not have one. We are actively working on it as our very highest priority for the Outlook Calendar team. As soon as it is released, I will post to this forum.
Please keep comments positive, as well. We all want the same thing here :-). I'm also available on private messages if you want to chat.
01-12-2020 09:37 PM
@Julia Foran thanks for the detailed explanation. The frustration is that Microsoft has not admitted that there is a massive design flaw that should have been fixed years ago. This issue was raised nearly 2 years ago and has not been fixed. So rather than work on the complex fix to Windows you focussed on the easier changes and hence why we are still waiting. This is probably why you are not getting positive responses as it has not been handled well. Where are your Change Managers?
01-12-2020 10:04 PM
Thank you @Julia Foran ,
Appreciate the detailed reply. It helps me understand some of the complexity behind this... also why sometimes it tended to work and other times not.
I'll be able to update my clients now. Good luck with the update...hope to see it soon enough!
@Julia Foran First, I want to thank you for your detailed response and transparency of this matter. To know that this behavior is being worked on by your Windows team as recently as two weeks ago is good enough for me.
Secondly, I would like to add, as a Systems Engineer for a nationwide MSP, end users don't necessarily want to understand why the feature works as they assume/believe it should on the mobile app or web, but not in the desktop application/Windows version. The desktop/legacy version of Office is the end users' primary source and features are expected to act the same across platforms. Now as a tech, it's easy to understand and explain the reasoning behind the behavior, but it leaves me questioning why no education has been distributed to users like a pop-up when they are opening or creating invites?!