Yes, I think it’s now an established fact that Exchange servers no longer interest MS at all. It seems to me that Octave even mentioned it on the ML.
The future at MS is 365 and Copilot (all the Copilot, there are 30 
)
Anyway, good reflex for Thunderbird @VeroniqueB23 there’s just left to migrate everything to Zimbra and that’s it 
Hello,
We have the same issue, does anyone have a solution? Should we change email boxes?
As a temporary solution, one option that has worked for other users with the same issue is to use Mozilla Thunderbird as an email client. Being an alternative client that doesn’t rely on Outlook’s infrastructure, it usually avoids these compatibility and authentication problems.
You can also force manual server configuration in Outlook instead of using automatic detection. In the advanced options when adding the account, select “Let me set up my account manually” and enter the Exchange server details provided by OVH.
Best regards,
Sergio Turpín
Hello Sergio,
I don't think this solution addresses the issue reported by several people, namely that images embedded in an email are not displayed.
Are you using an AI to generate your responses?
Hi @fritz2cat
No, I mentioned it because it is an OVH‑documented alternative, and it really helps confirm that the problem is not a configuration issue (a situation that can happen to some users), so it is used to rule it out.
When Outlook experiences connection or synchronization problems (such as those described in the thread, with images not showing), automatic detection sometimes fails or takes time to respond, especially in Exchange environments that are not Microsoft 365. Forcing manual configuration allows you to quickly verify that the server details are correct and that the account connects without relying on automatic detection. This helps rule out that the failure is in the Outlook client and confirms that the source of the problem is the Microsoft patch, as has ultimately been verified.
I mentioned it as a step to isolate the issue, not as a magic solution for the image failure. The real cause of this failure, as you correctly point out, is a problem confirmed by Microsoft that affects classic Outlook after the May 2026 updates.
It may turn out that the translation of my posts is not entirely accurate, since I respond in Spanish. I’m sorry if something is unclear; this is how I try to express it 
Sergio Turpín
It’s July 9th, still no word on the fix?
Monday 13/07 today, still no fixes or information on the issue?
Since mid‑May, we’ve been pretty much stuck here 
Microsoft will not fix it within a reasonable time, that’s clear.