KB4169: Exchange backup fails after upgrading to Veeam ...
https://www.veeam.com/kb416921.05.2021 · Solution. To add the "full_access_as_app" permission to your Azure AD app registration, do the following: Sign in to the Azure portal. Go to Azure Active Directory > App registrations, and select your application. Select API permissions > Add a permission > APIs my organization uses. Select Office 365 Exchange Online API in the list, go to the ...
KB2969: Veeam Backup for Office 365 Complete Permissions
www.veeam.com › kb2969Jun 26, 2019 · Veeam service account permissions. 1.a. Exchange Role. Configuring permissions for Exchange Online. Create a role group in the Exchange Admin Center as explained here. Add Roles specified in the User Guide. Add the Veeam Service account to role group members and save the role group. Connect to Exchange Online PowerShell module and run the " Get ...
KB2969: Veeam Backup for Office 365 Complete Permissions
https://www.veeam.com/kb296926.06.2019 · 2969. Product: Veeam Backup for Microsoft Office 365 5.0, Veeam Backup for Microsoft Office 365 4.0. Published: 2019-06-26. Last Modified: 2021-08-12. Starting with Veeam Backup for Microsoft Office version 4c, two different modern authentication methods and a basic authentication method for working with Office 365 organizations are supported.
Issues authenticating - Veeam R&D Forums
forums.veeam.com › veeam-backup-for-office-365-f47Sep 02, 2014 · When trying to use this account to connect VBO to our tenant I cannot get past the Connect to EWS and Microsoft Graph actions. EWS fails with HTTP status 401: Unauthorized and Microsoft Graph with Failed to get Microsoft Graph resource ID. As far as I can tell this new account is not set up to use MFA. We do have MFA turned on for the accounts ...
EWS Connect Error 401 Unauthorized – InfoBridge
kb.infobridge.com › hc › en-usOct 12, 2017 · Note Verify if you indeed are not authorized to connect to EWS. Something you can also check is the password of the SyncUser with which you are trying to connect to EWS. Office 365 doesn’t like passwords with special characters: This password for instance didn’t work anymore: d2h*praWrAW6. When changed to this the connection to EWS worked ...