We continue to look into this with our development team. We are currently preparing / creating a fix that should resolve these errors for impacted jobs,
Posted May 22, 2026 - 14:08 BST
Update
We continue to look into this with our development team. We are currently preparing / creating a fix that should resolve these errors for impacted jobs,
Posted Apr 28, 2026 - 10:06 BST
Update
We continue to look into this with our development team. We are currently preparing / creating a fix that should resolve these errors for impacted jobs,
Posted Apr 28, 2026 - 10:05 BST
Update
We continue to look into this with our development team. We are currently preparing / creating a fix that should resolve these errors for impacted jobs,
A further update will be provided on Monday the 27th of April
Posted Apr 24, 2026 - 17:32 BST
Update
We continue to look into this with our development team. We are currently looking into a resolution for this, identified as a change from Microsoft. We will share additional information once we are able. Apologies for any inconvenience caused and thank you for your patience here
Posted Apr 20, 2026 - 10:51 BST
Update
We continue to look into this with our development team. This is identified as a patch that Microsoft released 27th March for Exchange Web Service access, which now requires explicit access at organization and mailbox levels. We are currently looking into a resolution for this. We will share additional information once we are able. Apologies for any inconvenience caused.
Posted Apr 16, 2026 - 14:27 BST
Update
We are continuing to monitor Microsoft Incident EX1256020, which is causing intermittent access issues for some users connecting to Exchange Online mailboxes via certain connection methods.
We are still actively reviewing potential workarounds and will contact affected customers directly if an interim solution becomes available.
A further update will be provided on 2nd April if not before.
Posted Apr 01, 2026 - 12:22 BST
Monitoring
We have confirmed that the issue is related to Microsoft Incident EX1256020, which is causing intermittent access problems for some users connecting to their Exchange Online mailboxes via certain connection methods.
We are actively reviewing potential workarounds and will contact affected customers directly where an interim solution is possible.
A further update will be provided on the morning of the 1st of April
Posted Mar 31, 2026 - 17:30 BST
Update
We have confirmed that the issue is related to Microsoft Incident EX1256020, which is causing intermittent access problems for some users connecting to their Exchange Online mailboxes via certain connection methods.
We are actively reviewing potential workarounds and will contact affected customers directly where an interim solution is possible.
A further update will be provided on the morning of the 1st of April
Posted Mar 31, 2026 - 17:30 BST
Identified
We are currently investigating some Exchange Mailbox backups providing the error “The HTTP request was forbidden with client authentication scheme ‘Anonymous’". This is believed to stem from a change to Microsoft's authentication requirements. We will share additional information once we are able.