If your EWS applications stopped working and you are looking for a quick relief, please see Exchange Online EWS application stopped working? Do this. | Microsoft Community Hub. Re-enabling EWS is pos...
Updated Oct 27, 2026
Version 21.0
Blog Post
I have to disagree with some of Greg's statements, yes people should and have started to migrate when the announcement came out and if they have waited to the lat minute then that's on them. However Microsoft haven't addressed all their 1st party services and haven't provided the expected level of detail to easily identify client versions affected. Microsoft also added external calendar sharing to the impacted scope very late in the day, the new cross site policy method wasn't released globally until just over a week ago and people are still reporting it isn't fully working.
We were in a position where all our applications had been migrated months ago and were fully expecting Microsoft to be managing there 1st part apps and clients, then the new in-scope announces came and we had to kick off a load more unexpected work.
To try and frame this as just customers not being prepared is disingenuous, I fully except that this is the case for some but others will have taken this seriously only to have additional requirements added late in the day.
My opinion is that a lot of us are trying to do the right thing within serve financial and resource constraints and this is far from the only Microsoft, and other vendor, changes in flight.
I'm not trying to start an argument, only trying to put another perspective forward whilst recognising some of what has been said is also true.
It's an 11th hour scramble, no-matter what anyone says. We just need to accept it for what it is and hope they do better next time..
