- Detected by Pingoru
- Apr 20, 2026, 09:56 PM UTC
- Resolved
- Apr 20, 2026, 09:56 PM UTC
- Duration
- —
Affected: M365 - Asia PacificM365 - Europe, Middle East & AfricaM365 - Americas
Timeline · 4 updates
-
investigating Mar 27, 2026, 04:00 PM UTC
Status: Investigating We are currently investigating an uptick in errors backing up Exchange Online mailboxes with the message “The HTTP request was forbidden with client authentication scheme ‘Anonymous’" with Microsoft. We will share additional information once we are able. More specific information is at https://www.veeam.com/kb4796. Affected components M365 - Asia Pacific (Partial outage) M365 - Europe, Middle East & Africa (Partial outage) M365 - Americas (Partial outage)
-
identified Mar 30, 2026, 07:21 PM UTC
Status: Identified We have identified a mitigation for the Exchange Online backup authentication errors related to Exchange Web Services (EWS) access. Backups are succeeding for customers who enable EWS at both the organization and mailbox levels and allow time for Microsoft 365 replication to complete. We continue to work with Microsoft to investigate a small number of edge cases where issues may persist, and we will provide further updates as more information becomes available. More information on the workaround can be found here: https://www.veeam.com/kb479 "https://www.veeam.com/kb4796": https://www.veeam.com/kb4796 Affected components M365 - Europe, Middle East & Africa (Partial outage) M365 - Americas (Partial outage) M365 - Asia Pacific (Partial outage)
-
monitoring Apr 01, 2026, 09:38 PM UTC
Status: Monitoring We continue to see successful backups for customers who have applied the configuration changes outlined in our knowledge base article. Customers who have not yet made these updates should follow the guidance in the article to restore normal backup operation. Please note, due to Microsoft 365 replication timing, it may take up to 24 hours after making these changes for backups to fully return to normal. We are not observing new widespread impact at this time. Knowledge base article: https://www.veeam.com/kb4796 Affected components M365 - Asia Pacific (Operational) M365 - Europe, Middle East & Africa (Operational) M365 - Americas (Operational)
-
resolved Apr 20, 2026, 09:56 PM UTC
Status: Resolved We continue to see successful backups for customers who have applied the configuration changes outlined in our knowledge base article below. We have not observed any new recurrence of this issue. For remaining impacted customers, please refer to our Knowledge base article: https://www.veeam.com/kb4796 Affected components M365 - Asia Pacific (Operational) M365 - Europe, Middle East & Africa (Operational) M365 - Americas (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 04:07 PM UTC
- Resolved
- Apr 20, 2026, 04:07 PM UTC
- Duration
- —
Affected: M365 - Asia PacificM365 - Europe, Middle East & AfricaM365 - Americas
Timeline · 5 updates
-
identified Mar 20, 2026, 04:09 PM UTC
Status: Identified We have identified an issue with the Microsoft Sharepoint & OneDrive API resulting in some restored files to cause errors when opened with Microsoft office. We are currently working on mitigating this issue and are doing a joint investigation with Microsoft. Affected components M365 - Asia Pacific (Partial outage) M365 - Europe, Middle East & Africa (Partial outage) M365 - Americas (Partial outage)
-
monitoring Mar 22, 2026, 05:02 PM UTC
Status: Monitoring As of 12:30 UTC, our engineering team has deployed a fix for the issue impacting the Microsoft SharePoint & OneDrive API. We are no longer observing new errors. However, some customer files that were backed up in recent weeks may continue to exhibit issues during restore until remediation is completed. Our Veeam Data Cloud engineering team is now working to identify and reprocess any files that were impacted during this period. Affected components M365 - Asia Pacific (Partial outage) M365 - Europe, Middle East & Africa (Partial outage) M365 - Americas (Partial outage)
-
monitoring Mar 25, 2026, 06:01 PM UTC
Status: Monitoring As of March 25, we have deployed an update globally and are seeing stable operation. While no new instances of the error are being observed, we are continuing follow-up work to ensure all previously impacted scenarios are fully resolved. An update on this work will be provided as soon as possible. Affected components M365 - Asia Pacific (Partial outage) M365 - Europe, Middle East & Africa (Partial outage) M365 - Americas (Partial outage)
-
monitoring Apr 03, 2026, 02:57 PM UTC
Status: Monitoring As of March 25, we deployed an update globally and continue to see stable service operation. At this time, we are not observing any new instances of this issue. Our engineering team continues follow-up work with Microsoft and internal engineering efforts to ensure all previously impacted scenarios are fully addressed and to drive a permanent resolution. We expect to have additional updates in the next few days and will share another update as soon as we have more information. Affected components M365 - Americas (Partial outage) M365 - Asia Pacific (Partial outage) M365 - Europe, Middle East & Africa (Partial outage)
-
resolved Apr 20, 2026, 04:07 PM UTC
Status: Resolved We have not observed any recurrence of this issue since the March 25 update. We are closing this incident and will continue working with Microsoft on any remaining items. Affected components M365 - Americas (Operational) M365 - Asia Pacific (Operational) M365 - Europe, Middle East & Africa (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 10:44 PM UTC
- Resolved
- Mar 26, 2026, 10:44 PM UTC
- Duration
- —
Affected: Azure - Asia PacificAzure - AmericasAzure - Europe, Middle East & Africa
Timeline · 2 updates
-
investigating Mar 26, 2026, 05:11 PM UTC
Status: Investigating Starting around 16:00 UTC on March 25, Veeam Data Cloud began experiencing an issue with VDC Azure tenant management for all Azure customers. During this time, customers may experience issues with loading tenant data after selecting a tenant to manage (blank page), which may require multiple refreshes to recover. Veeam engineers are actively working to resolve this issue. Affected components Azure - Americas (Degraded performance) Azure - Europe, Middle East & Africa (Degraded performance) Azure - Asia Pacific (Degraded performance)
-
resolved Mar 26, 2026, 10:44 PM UTC
Status: Resolved Between 16:00 UTC on March 25 and 17:30 UTC on March 26, Veeam Data Cloud experienced an issue with VDC Azure tenant management. During this time, customers may have experienced issues with loading tenant data after selecting a tenant to manage in OneUI (blank page), which may have required multiple refreshes to recover. Veeam engineers have mitigated the issue and confirmed that services are fully functional. Please reach out to support if you experience any further issues. Affected components Azure - Americas (Operational) Azure - Europe, Middle East & Africa (Operational) Azure - Asia Pacific (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 04:50 PM UTC
- Resolved
- Mar 18, 2026, 04:50 PM UTC
- Duration
- —
Affected: M365 - Asia Pacific
Timeline · 2 updates
-
investigating Mar 18, 2026, 03:36 AM UTC
Status: Investigating Starting at 17:00 UTC on March 17th, Veeam Data Cloud began experiencing an issue with M365 backups failing for some customers in the APJ region. Our engineers have opened a technical support ticket with Microsoft and are actively working alongside their team to resolve the underlying cause as quickly as possible. Further information will be provided as soon as more details are obtained from Microsoft. Affected components M365 - Asia Pacific (Partial outage)
-
resolved Mar 18, 2026, 04:50 PM UTC
Status: Resolved Between 17:00 UTC on March 17th and 08:00 UTC on March 18th, Veeam Data Cloud experienced an issue where M365 backups failed for some customers in the APJ region. Our engineers worked closely with Microsoft to identify and resolve the underlying infrastructure issue, and we can now confirm that backup functionality has been fully restored. All systems are operating normally. If you experience any further issues, please reach out to our support team for assistance. Affected components M365 - Asia Pacific (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 11:31 PM UTC
- Resolved
- Mar 02, 2026, 11:31 PM UTC
- Duration
- —
Affected: M365 - Americas
Timeline · 2 updates
-
investigating Mar 02, 2026, 10:50 PM UTC
Status: Investigating Starting around 21:00 UTC, Veeam Data Cloud began experiencing degraded performance for some AMER customers using M365. During this time, some customers may experience issues performing backups or restores. Our engineer team is actively engaged and working to resolve this issue. Affected components M365 - Americas (Degraded performance)
-
resolved Mar 02, 2026, 11:31 PM UTC
Status: Resolved Between 21:00 UTC and 23:20 UTC, Veeam Data Cloud experienced an issue with M365 impacting some AMER customers. During this time, some customers may have experienced issues performing restores and backups. Our engineers mitigated this issue and confirmed services are fully functional. If you experience any further issues, please reach out to support for further assistance. Affected components M365 - Americas (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 11:29 PM UTC
- Resolved
- Mar 01, 2026, 11:20 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 03:10 PM UTC
- Resolved
- Feb 25, 2026, 03:10 PM UTC
- Duration
- —
Affected: M365 - Europe, Middle East & Africa
Timeline · 2 updates
-
investigating Feb 25, 2026, 05:18 AM UTC
Status: Investigating Starting around 02:57 UTC on February 25, some EMEA-hosted customers may experience service disruptions affecting dashboard access and restore operations. While backup jobs should continue to run as expected, Microsoft has confirmed that a database issue following scheduled maintenance is causing this impact. Our engineering teams are working closely with Microsoft Support to resolve the issue, and we will provide updates as they become available. Affected components M365 - Europe, Middle East & Africa (Degraded performance)
-
resolved Feb 25, 2026, 03:10 PM UTC
Status: Resolved As of 10:53 UTC, service functionality has been fully restored. Following Microsoft's scheduled maintenance, our teams worked closely with their support engineers to resolve the underlying database issues that were affecting dashboard access and restore operations. We have monitored the environment and confirmed that all services are now stable and healthy. If you continue to experience any issues, please reach out to our Support team for assistance. Affected components M365 - Europe, Middle East & Africa (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 04:53 PM UTC
- Resolved
- Feb 19, 2026, 04:52 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Feb 17, 2026, 03:35 PM UTC
- Resolved
- Feb 17, 2026, 03:35 PM UTC
- Duration
- —
Affected: M365 - Asia PacificM365 - Europe, Middle East & AfricaM365 - Americas
Timeline · 4 updates
-
identified Feb 12, 2026, 06:38 PM UTC
Status: Identified Starting around 06:00 UTC on February 09, Veeam Data Cloud began experiencing service performance issues for backups on M365. Our engineering teams are engaged and actively working to restore functionality. We appreciate your patience and will provide updates as soon as more information is available. Affected components M365 - Asia Pacific (Degraded performance) M365 - Europe, Middle East & Africa (Degraded performance) M365 - Americas (Degraded performance)
-
monitoring Feb 12, 2026, 09:19 PM UTC
Status: Monitoring Our engineers implemented a fix as of 21:09 UTC. Previously impacted backup service functionality has been restored for all M365 customers. We will continue to monitor service health overnight to ensure stability and confirm that no further issues arise. Affected components M365 - Asia Pacific (Operational) M365 - Europe, Middle East & Africa (Operational) M365 - Americas (Operational)
-
monitoring Feb 13, 2026, 11:19 PM UTC
Status: Monitoring Since our initial fix at 21:09 UTC on February 12th, the majority of our services have remained stable and healthy. However, because we have observed a small number of intermittent errors, we are continuing to monitor over the weekend to ensure stability. Affected components M365 - Asia Pacific (Operational) M365 - Europe, Middle East & Africa (Operational) M365 - Americas (Operational)
-
resolved Feb 17, 2026, 03:35 PM UTC
Status: Resolved We have confirmed that all services, including backup functionality, have remained stable and fully operational since February 12 at 21:09 UTC. Our engineering team has closely monitored the environment and no further errors have been observed. Affected components M365 - Asia Pacific (Operational) M365 - Europe, Middle East & Africa (Operational) M365 - Americas (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 03:32 PM UTC
- Resolved
- Feb 16, 2026, 03:32 PM UTC
- Duration
- —
Affected: Entra - Europe, Middle East & AfricaEntra - AmericasEntra - Asia Pacific
Timeline · 3 updates
-
investigating Feb 15, 2026, 07:31 PM UTC
Status: Investigating Starting on Sunday, February 15, Veeam Data Cloud experienced a service disruption impacting Entra ID customers across all regions. During this window, affected users may have encountered intermittent or total backup failures within their environments. Our engineering team identified the root cause and successfully implemented a mitigation to restore functionality as of 17:30 UTC. We are currently monitoring the service closely to ensure stability and prevent any recurrence. Affected components Entra - Americas (Partial outage) Entra - Asia Pacific (Partial outage) Entra - Europe, Middle East & Africa (Partial outage)
-
monitoring Feb 15, 2026, 07:33 PM UTC
Status: Monitoring Starting on Sunday, February 15, Veeam Data Cloud experienced a service disruption impacting Entra ID customers across all regions. During this window, affected users may have encountered intermittent or total backup failures within their environments. Our engineering team identified the root cause and successfully implemented a mitigation to restore functionality as of 17:30 UTC. We are currently monitoring the service closely to ensure stability and prevent any recurrence. Affected components Entra - Americas (Operational) Entra - Asia Pacific (Operational) Entra - Europe, Middle East & Africa (Operational)
-
resolved Feb 16, 2026, 03:32 PM UTC
Status: Resolved Between 20:03 UTC on February 14th and 17:23 UTC on February 15th, Veeam Data Cloud experienced a service disruption impacting Entra ID customers. During this period, some customers may have experienced failed backup jobs. Our engineering team has mitigated the issue and confirmed through overnight monitoring that service stability has returned to normal levels. Please reach out to support if you experience any further issues. Affected components Entra - Europe, Middle East & Africa (Operational) Entra - Americas (Operational) Entra - Asia Pacific (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 03:43 PM UTC
- Resolved
- Feb 10, 2026, 03:43 PM UTC
- Duration
- —
Affected: M365 - Asia PacificM365 - Europe, Middle East & AfricaM365 - Americas
Timeline · 4 updates
-
investigating Feb 06, 2026, 04:20 PM UTC
Status: Investigating We are currently investigating an issue where some customers may experience failures or delays when exporting data to PST. At this time, restore functionality remains fully operational and is not impacted. Our engineering teams are actively debugging the issue, which appears to be related to a recent Microsoft update affecting PST background processing. We are working to mitigate the impact and will provide further updates as more information becomes available. Affected components M365 - Asia Pacific (Partial outage) M365 - Europe, Middle East & Africa (Partial outage) M365 - Americas (Partial outage)
-
monitoring Feb 06, 2026, 09:49 PM UTC
Status: Monitoring Targeted changes were applied to mitigate the current PST export failures. The system and associated changes will continue to be monitored and we will provide additional updates as the situation evolves. Affected components M365 - Asia Pacific (Operational) M365 - Europe, Middle East & Africa (Operational) M365 - Americas (Operational)
-
monitoring Feb 10, 2026, 02:14 AM UTC
Status: Monitoring Our engineers have applied a fix as of 12:00 UTC to address the recent service interruptions. We have confirmed that systems are currently performing as expected and will continue to monitor service health overnight to ensure ongoing stability. The next update will be provided around 16:00 UTC after further observation. Affected components M365 - Asia Pacific (Operational) M365 - Europe, Middle East & Africa (Operational) M365 - Americas (Operational)
-
resolved Feb 10, 2026, 03:43 PM UTC
Status: Resolved Our engineers have monitored system health overnight and confirmed that platform stability has returned to normal. The previous failures and delays encountered when exporting data to PST have been fully resolved. Affected components M365 - Europe, Middle East & Africa (Operational) M365 - Americas (Operational) M365 - Asia Pacific (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 02:11 AM UTC
- Resolved
- Feb 10, 2026, 02:11 AM UTC
- Duration
- —
Affected: M365 - Americas
Timeline · 2 updates
-
investigating Feb 08, 2026, 08:36 PM UTC
Status: Investigating Some backups may be experiencing degraded performance. We are actively investigating the issue. Affected components M365 - Americas (Degraded performance)
-
resolved Feb 10, 2026, 02:11 AM UTC
Status: Resolved As of 00:45 UTC on February 09, full functionality has been restored for all backups previously impacted by service interruptions. The issue originated from a widespread Microsoft outage that affected our underlying infrastructure, but all systems are now performing as expected. Please reach out to support if you experience any further issues. Affected components M365 - Americas (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 08, 2026, 04:45 AM UTC
- Resolved
- Feb 08, 2026, 04:45 AM UTC
- Duration
- —
Affected: M365 - Americas
Timeline · 2 updates
-
investigating Feb 07, 2026, 07:05 PM UTC
Status: Investigating Starting at 08:00 UTC, Veeam Data Cloud began experiencing issues due to a widespread outage in Microsoft Azure impacting customers in the US West region. Customers in the West US region may see some failed backups. More information regarding this outage can be found on Microsoft’s status page here: https://azure.status.microsoft/en-us/status Further updates will be provided when more information is obtained from Microsoft. Affected components M365 - Americas (Degraded performance)
-
resolved Feb 08, 2026, 04:45 AM UTC
Status: Resolved Between 08:00 UTC on February 06 and 02:15 UTC on February 07, Veeam Data Cloud experienced issues due to a widespread outage with Microsoft Azure that impacted customers in the US West region. Microsoft has confirmed that all Azure services are now healthy. Veeam Data Cloud engineers have also confirmed service restoration. For more information on the Microsoft Azure outage, please refer to Microsoft's status page: https://azure.status.microsoft/en-us/status Affected components M365 - Americas (Operational)
Read the full incident report →
