In the License Overview report, a user display name is displayed instead of a UPN.OneDrive and SharePoint items restore with modern auth with allowed legacy protocols may fail with an authentication error.After moving existing OneDrive and SharePoint backups to an object storage repository, a new backup job targeted at this repository may fail to create restore points.A user may not have a valid Microsoft Office 365 license with a SharePoint plan enabled" error. SharePoint personal site backup may fail with "Failed to resolve personal site owner.Microsoft Teams backup may fail with "400 – Bad request – Value cannot be null.In on-premises Exchange organizations, public folder backup fails with "Value cannot be null.Exchange mailbox backup fails with "Arithmetic operation results in an overflow" error.The part may not have been uploaded, or the specified entity tag may not match the part's entity tag" error. Under certain conditions, Exchange mailbox backup fails with "One or more of the specified parts could not be found.Exchange mailbox backup fails with "Mailbox is already processed by another job" error.Exchange mailbox backup fails with "The specified object was not found in the store" error.SharePoint backup fails with "An item with the same key has already been added" error.In the backup job wizard, some users may not be displayed and available for selection.Backup job session processing rate may be displayed with a negative value of -1.Adding Office 365 organization with modern app-only authentication fails with "Invalid Exchange Web Services response" error.In addition, the following issues in the Veeam product have been fixed by the cumulative update: Optimized operations with local cache to improve the performance of SharePoint backup to an object store repository.
The cumulative update KB4124 for Veeam Backup for Office 365 5b includes the following improvements and bug fixes: (), that a cumulative update KB4124 for Veeam Backup for Office 365 is available since March 12, 2021. have pointed out in comments and mails in connection with the blog post Azure-Problem beeinträchtigt Teams, Exchange Online, Office 365 etc. German time.īoth Michel Py, and blog reader Robert G. Blog reader Michel Py pointed out in this comment that in his environment, Veeam backup jobs failed around 21:00 p.m. The global disruption in Microsoft's Azure Active Directory on March 15, 2021, has arguably affected backup solutions that rely on Microsoft services provided by Azure AD for authentication, among other things. Backup fails due to Azure service disruption Microsoft technicians are working to fix this glitch. The next update will be provided in 60 minutes or as events warrant. As the deployment continues to the impacted regions, some customers may begin to see signs of recovery. A subset of customers may experience 403 error notifications when attempting to make storage calls.Ĭurrent Status: We currently have a deployment in progress, in line with safe deployment practices, to mitigate residual impact to Azure Storage. We have completed rollout of a fix to mitigate impact to Azure Active Directory and the Azure Portal.Īdditional impact to other Azure services/offerings that rely on the Azure Storage service may continue to see further impact. Starting at approximately 19:15 UTC on 15 Mar, a subset of customers may have experienced issues authenticating into Microsoft services, including Microsoft Teams, Office and/or Dynamics, Xbox Live, and the Azure Portal. On the status page, regarding Azure storage accesses, a message says that they trigger a 403 error when the storage is accessed:Īzure Storage – 403 error notifications when attempting to make storage calls – Applying Mitigation But the status page of Azure still shows some disruptions in the data storage area on at 11:28 a.m.
It seems the issues have been fixed internally by an update SINCE Microsoft. The Azure outage affects Teams, Exchange Online, Office 365 etc. The worldwide disruption in Microsoft's Azure Active Directory as of Mahas affected many services (I had covered it only within my German blog post Azure-Problem beeinträchtigt Teams, Exchange Online, Office 365 etc. Worldwide Azure service disruption persists