If you are experiencing the “Cannot complete login due to an incorrect username or password” error in your Veeam Backup jobs, there are several things you can check to fix this issue: If the error persists, please reach out to Managecast and we can assist in troubleshooting and resolving the issue.
Veeam Backup for Microsoft 365 provides support for backing up SharePoint Online sites, but currently does not support Microsoft Loop SharePoint sites. If you are attempting to backup a Microsoft Loop SharePoint site, you may receive the “(401) Unauthorized” error. In this case, your best course of action is to exclude the Microsoft Loop site from your backup job. You can do this by modifying your backup job settings and excluding the site in question. Veeam has provided a knowledge base article with more information on this issue, which you can find at https://www.veeam.com/kb4440. In that KB article you will also find a hotfix available for Veeam Backup for Microsoft 365 v7 that will silently ignore and exclude these sites. Veeam is planning to add support for these Microsoft Loop SharePoint sites once the product becomes generally available.
The error message “Cannot change WebPart ExportMode to ‘All’. WebPart will be skipped” indicates that a WebPart cannot be backed up due to an issue with custom scripting when using Veeam backup for Microsoft 365. To resolve this issue, you must enable the “Allow custom script” option in SharePoint, as detailed in KB article from Veeam: https://www.veeam.com/kb4091. Once enabled, you should be able to successfully back up the affected SharePoint sites. Alternatively, if you do not need to backup custom Web Parts content, edit the Organization and uncheck the option for Allow this application to enable export mode for SharePoint Web Parts.
You may run into the following error when trying to perform restores from Veeam for Microsoft 365: The specified Azure AD application is missing required delegated permissions (Microsoft API: Microsoft Graph, permissions: Sites.Read.All) This issue seems to be caused by upgrading from previous versions of Veeam for Microsoft 365, specifically version 5 to version 6. The quick fix for this is simply to edit the organization in the Veeam for Microsoft 365 console, and run through the steps to Automatically register a new Azure AD application.
