I don't think many orgs are using "new Outlook" to connect to on-prem Exchange because you miss a lot if you're only doing it via IMAP and "new" still doesn't support on-prem Exchange any other way. So all my clients are using classic Outlook with their on-prem Exchange servers (and really if they have EXO too because new Outlook isn't very good).
replyIt's been gone-as-a-default for a few months now, but for a long time, "Classic Outlook" aggressively offered a one-toggle upgrade path to "New Outlook", and it got used.
replySure, "New Outlook" on Windows is still entirely broken (including stuff like, oh, re-ordering mailboxes), but on Mac it's actually quite usable, and even allows you to switch off the IMAP proxying.
Do e-mail messages that self-hosted Exchange receives always get proxied through the outlook.com cloud?
replyThanks for this LMAO. It made my day off worth taking. Now I don't feel the need to log in and check who-knows-what mail.
replyExchange has been a circus for years. I think that's why everyone went O365 in the first place. Managing to have a paid up configuration where you go down when a cloud provider goes down but you're hosting it locally is absolutely stupid and I am laughing my ass off here.
replyAlso laughing at our ops guys who are now absolutely helpless and have people phoning them. I warned about this on our risk call and it was seen as low probability low risk. I hope it's down for a few hours :)