In our ongoing commitment to enhance the security and control mechanisms of Exchange Web Services (EWS), we are announcing a significant change in the behavior of the EWSEnabled tenant-wide switch in...
Updated Feb 26, 2025
Version 2.0
Blog Post
It is insane to NOT include this in the Exchange/M365 Admin. Writing a blogpost to announce a change that will have drastic impact on potentially a lot of customers is not sufficient - judging from the other comments here.
Why in the world would you NOT make this a notification somewhere in the Exchange/M365 Admin. At least implement a check that checks the Organization Level settings and give you an alert via mail/notification in case you are affected.
Utterly insane. What is even more insane is NO support team knew about this change. 3 Days of pushing around tickets with no meaningful help when it could have been solved in literally 1 Minute if they just linked us this article.
What a sh*tty day to work as a microsoft Sysadmin. Thanks for nothing.
- Greg Taylor - EXCHANGE
Microsoft
I am disappointed too that some support agents didn't know about this - but we did post this to the Message Center. That's the official place we publish changes to.
I'll echo this Greg on the support system. I had a ticket too and it was 4-5 days of idle useless level 1 workstation-oriented troubleshooting. Level 1 support had a huge failure on this and I want to again make that public from another MS customer (i.e. me). They had NO idea, could not communicate and were having me jump through hoops of zero relevance and importance.
This is and was a systems issue from support. I am not happy to think of the next time I might have to put in a ticket.
- Greg Taylor - EXCHANGE
Again, sorry to hear that was your experience. For what it's worth, I'm sorry you had to go through that. It's not easy to get every agent to know of every change that might affect you, but we'll keep seeing what we can do to improve it I promise.
