Resolved -
      	Microsoft has now cleared the incident from its widespread status page, and we are awaiting the Post-Incident Review from them.
We're not currently seeing any unusual or unexpected issues with the Exclaimer Add-in. Our engineers will continue to monitor and advise customers if anything is detected.
If you are continuing to experience issues applying your signatures to emails through the Add-in, please don't hesitate to reach out to our support team, who will be happy to help!
        
        
            Oct 30, 00:42 UTC
        
      
      
        Update -
      	Exclaimer Engineers are not observing any ongoing issues with the Exclaimer Add-in right now, indicating the service is working as expected for both client-side and server-side signatures.
Microsoft has advised that they are operating at 98% availability, suggesting a very low chance of any issues occurring, but continues to work towards full resolution.
Microsoft has updated the completion time to be 00:40 UTC on 30 October 2025, and we will continue to monitor at this time.
If you are experiencing issues applying a signature to your emails through our Add-in, or you have any outstanding questions, please don't hesitate to reach out to our support team.
        
        
            Oct 29, 23:55 UTC
        
      
      
        Update -
      	Microsoft advised earlier today that the deployment of their 'last known good' configuration to Microsoft Azure is showing signs of successful recovery at this time; however, due to the extent of the issue, they are estimating full recovery to happen by 23:20 UTC on 29 October 2025. 
Exclaimer Engineers are continuing to monitor at this time for any changes, but are seeing signs of this recovery occurring. Earlier work that was undertaken to reduce the impact remains in place and is still seeing our mail flow processes working without signs of being impacted. 
If you are having issues sending messages at this time or you have any outstanding questions, please don't hesitate to reach out to our support team.
        
        
            Oct 29, 20:20 UTC
        
      
      
        Update -
      	
Monitoring of our mitigation looks to have restored close to half of the Add-in performance of being able to apply a signature to messages within Outlook, with indicators that some attempts are failing due to errors from Microsoft services.  
Microsoft is currently rolling back recent changes to Azure Front Door to restore service at this time. We are continuing to monitor for any further issues.
You can find updates on Microsoft's public status page for widespread incidents - https://status.cloud.microsoft/. We have recorded that this page also looks to be impacted, and may occasionally not load.
        
        
            Oct 29, 17:34 UTC
        
       
      
        Monitoring -
      	
Exclaimer Engineers have applied a routing workaround to bypass the Azure Front Door Service, which looks to have been the cause of the outage. Customers should find that the signature is applying as expected from the Add-in shortly once the new routing path has been obtained by the users Outlook client
Updates from can continue to be monitored on the following page:- https://status.cloud.microsoft/
        
        
            Oct 29, 17:10 UTC
        
       
      
        Update -
      	
Microsoft has confirmed that as of 16:00 GMT, they have been experiencing DNS issues resulting in the service impact.
They have taken action to try to mitigate the issue and expect their portal to be loading shortly.
Direct updates can be found on Microsoft's public status page for widespread incidents - https://status.cloud.microsoft/
Exclaimer Engineers have reviewed our internal systems and confirmed that our Server-side system is applying signatures as expected at this time.
        
        
            Oct 29, 16:42 UTC
        
       
      
        Investigating -
      	We are currently aware of an issue that is impacting the Exclaimer Add-in from being able to apply a signature to messages. This looks to be caused by a problem within Microsoft Azure at this time, which Microsoft is now investigating.
More updates will be provided once we have further information.
        
        
            Oct 29, 16:24 UTC