Monitoring - We are pleased to confirm that the technical issue affecting our supplier's licensing server has now been resolved. We apologise for any concern or inconvenience this may have caused.
To ensure your Veeam license reflects the correct status, please follow the steps below:
1. Open Veeam and go to the main menu. (Top left corner)
2. Select License.
3. Confirm that the Auto update license option is enabled.
4. If your license has not updated automatically, click Update Now.
If you continue to experience any issues, please do not hesitate to contact our service desk at servicedesk@virtualdcs.co.uk and a member of the team will be happy to assist.
Thank you for your patience whilst we worked to resolve this matter.
Jun 05, 2026 - 15:25 BST
To ensure your Veeam license reflects the correct status, please follow the steps below:
1. Open Veeam and go to the main menu. (Top left corner)
2. Select License.
3. Confirm that the Auto update license option is enabled.
4. If your license has not updated automatically, click Update Now.
If you continue to experience any issues, please do not hesitate to contact our service desk at servicedesk@virtualdcs.co.uk and a member of the team will be happy to assist.
Thank you for your patience whilst we worked to resolve this matter.
Jun 05, 2026 - 15:25 BST
Identified - We are aware that you may be seeing messages about your Veeam licence expiring. This is due to an issue with our suppliers licensing server. They are actively working on resolving the issue and we are treating this with the utmost urgency.
There is no risk to your licences, and they are not expiring unless your contracted date with DCS falls within the next 30 days. We expect this to be resolved within the next few days and understand the concern it may have caused. Thank you for your understanding in this matter.
May 28, 2026 - 10:53 BST
There is no risk to your licences, and they are not expiring unless your contracted date with DCS falls within the next 30 days. We expect this to be resolved within the next few days and understand the concern it may have caused. Thank you for your understanding in this matter.
May 28, 2026 - 10:53 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,
May 22, 2026 - 14:08 BST
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,
Apr 28, 2026 - 10:06 BST
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,
Apr 28, 2026 - 10:05 BST
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
Apr 24, 2026 - 17:32 BST
A further update will be provided on Monday the 27th of April
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
Apr 20, 2026 - 10:51 BST
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.
Apr 16, 2026 - 14:27 BST
We are currently looking into a resolution for this. We will share additional information once we are able. Apologies for any inconvenience caused.
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.
Apr 01, 2026 - 12:22 BST
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.
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
Mar 31, 2026 - 17:30 BST
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
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
Mar 31, 2026 - 17:30 BST
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
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.
Mar 27, 2026 - 16:29 GMT
Mar 27, 2026 - 16:29 GMT
Microsoft 365 Cloudmore Portal
Operational
CloudCover365 Portal
Operational
CloudCover365 Services
Operational
Hosting Platform
Operational
Veeam Cloud Connect Backup Service
Operational
Veeam Cloud Connect Replication Service
Operational
Object Storage Leeds
Operational
Object Storage Slough
Operational
Service Desk
Operational
Geo-Failover Replication
Operational
www.virtualdcs.co.uk
Operational
Veeam Service Provider Console
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.