Microsoft has published official information about this incident on the Service Health Dashboard (SHD) under ID: EX1183800. Please refer to the SHD for more details.
Since this officially confirms that the issue was not related to CodeTwo, we are resolving this incident on our end. If you have any questions, please raise a service request with Microsoft. You are also welcome to contact our Support Team at: https://www.codetwo.com/company/contact.
All CodeTwo services have been operational during the incident. Thank you for your understanding and cooperation.
Posted Nov 07, 2025 - 22:20 UTC
Identified
We have an update from Microsoft Product Group about this issue: "We suspect the latency issue is caused by high CPU usage regression. That could cause latency issues in uploading image. We already have the reverts done and the fix will deploy via a fast track soon. We need to monitor saturation over the next 24-48 hours."
As a reminder: This issue is not related to add-ins. It concerns inline images in general within the New Outlook and OWA and affects a subset of customers globally, regardless of whether they use any signature add-in solution.
Posted Nov 07, 2025 - 06:31 UTC
Update
Microsoft is still investigating this issue. So far, we know the problem is related to loading images in OWA and New Outlook and is not specific to add-ins - it affects any type of images in Outlook. Fortunately, the issue is not widespread.
If you have any questions, please feel free to reach out to our Support Team (which is available around the clock) while we await Microsoft’s resolution.
A subset of customers using OWA and the New Outlook are experiencing issues when adding/loading pictures in email signatures via email signature add-ins (such as CodeTwo). Some images load slowly, while others fail to load entirely.
We have reproduced the issue in our own CodeTwo production environment for certain users. We are currently in direct contact with the Microsoft product group, and they have confirmed that they are seeing the same problem. The issue is under active, high-priority investigation by Microsoft.
Further details are pending, but early findings indicate that the problem is not limited to Add-ins - it also affects OWA and New Outlook clients in general. Initial analysis suggests latency in OAuth as the potential root cause.
Please wait for more information. In the meantime, you can:
* Choose signatures without pictures for your end-users, or * Use server-side mode, where signatures are added by CodeTwo in the cloud (not via Microsoft add-ins).
Posted Nov 06, 2025 - 09:26 UTC
This incident affected: Australia East (Outlook add-in), Canada East (Outlook add-in), North Central US (Outlook add-in), North Europe (Outlook add-in), West Europe (Outlook add-in), West US (Outlook add-in), UK South (Outlook add-in), Germany West Central (Outlook add-in), and UAE North (Outlook add-in).