MicrosoftHi I am experiencing the same issue using Outlook 365 exchange personal subscription.
The EX212460 incident resolution above did not resolve my issue which started about 3 weeks ago - same as you guys.
I hope that Microsoft is aware of the issue and working on it - a bit disappointed there hasn't been any comms / public acknowledgement of the issue which seems to impact a high number and diverse customers.
Travis_78 I want to be proactive and notify Microsoft about the issue like you - in the absence of any comms I just don't know if they're aware of the issue and acting on it - so I went to Microsoft support via the inbuilt Outlook support function however it was a negative experience. I spent 45 mins obliging the support person with remote control and basic troubleshooting process which led to an outcome of "waiting for next version". No incident ID or assurance that they will notify the relevant tech team.
I don't recommend spending your time on the support. In the absence of an effective support function there is just no recourse left or way to know if Microsoft is actually doing something about this.
Other less tech competent / minded people are flailing in other forums / discussions - I am grateful that I discovered this community which has shed light on the issue and confirmed that it's a Microsoft issue. Some clarity from Microsoft would be good.
