Veeam Backup for Microsoft Office 365 Complete Permissions
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.
Depending on the Office 365 tenant configuration and the restrictions on using legacy authentication protocols, one of the following authentication methods may be used:
- Modern authentication
- Modern authentication with legacy authentication protocols
- Basic authentication
These authentication types require different sets of permissions to be configured.
For organizations with Modern Authentication
Veeam service account permissions
Veeam service account you are going to use should have a Global Administrator role.
Azure AD Application Permissions
There are two options:
- Have Veeam Backup for Office 365 automatically create the Azure AD application and all the required application permissions will be granted automatically.
or
- You can create an Azure AD application manually, then configure the permissions in accordance with "Requirements for Modern App-Only Authentication" section of the User Guide.
For more information about permission types please visit:
https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-permissions-and-consent
For organizations with modern authentication and legacy authentication protocols
Before configuring permissions, please check the following things:
- Security Defaults are disabled in your Office 365 tenant.
- Conditional Access policies are not blocking legacy authentication protocols for the Veeam service account.
The following sections are laid out as follows:
- Configure Veeam service account permissions
- Configure the App password
- Configure Azure AD Application permissions
1. 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-AuthenticationPolicy" command.
- If there is a blank return then there is no policy in place and you need to configure one.
- If the current policy does not have "true" for AllowBasicAuthPowershell and AllowBasicAuthWebService contact the Domain admins to update the policy withthis Microsoft document.
Below is an example of PowerShell cmdlets that could be used to configure a new authentication policy with AllowBasicAuthPowershell and AllowBasicAuthWebService enabled for the Veeam service account.
To create a new authentication policy named "Allow Basic Auth":
New-AuthenticationPolicy -Name "Allow Basic Auth"Set-AuthenticationPolicy -Identity "Allow Basic Auth" -AllowBasicAuthPowershell
Set-AuthenticationPolicy -Identity "Allow Basic Auth" -AllowBasicAuthWebServiceWhere <UserIdentity> is the Veeam service account.
Set-User -Identity <UserIdentity> -AuthenticationPolicy "Allow Basic Auth"1.b. Sharepoint Permissions
Configuring Permissions for SharePoint Online.
- Grant Veeam service account with the SharePoint Administrator Role in Azure Admin Center.
- In the SharePoint Admin Center open [Policies] > [Access control] and set "Apps that don't use modern authentication" to "Allow Access".
2. Configure the App password
- Set up Veeam service account user to leverage Multi-Factor Authentication.
- Make sure users are allowed to create app passwords.
- Sign-in to https://portal.office.com using Veeam service account credentials and create app password.
3. Azure AD Application permissions
Configuring Azure AD Application.
- Register a new application in Azure AD
- Go to API permissions and click [Add a permission].
- Configure the permissions in accordance with "Requirements for Modern App-Only Authentication" section of this User Guide page.
All permissions must have Application type.
For more information about permission types please visit https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-permissions-and-consent
- After all API permissions have been added you will need to grant admin consent.
- Select [Certificates & secrets] and [+New client secret].
- Add a Description> Choose Expiration> Add.
- Copy the Client's secret value.
- Go to Overview and copy the Application (client) ID.
Permissions required for organizations with basic authentication
Exchange
Exchange permissions should be configured the same way as in the Exchange section of this article.
SharePoint
SharePoint permissions should be configured the same way as in SharePoint section of this article.
Couldn't find what you were looking for?
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Do you have an issue or need post-sales technical assistance?
*if you need help choosing the right product, please select "Sales" chat
Do you need guidance on the website, upgrade hints or help with your licenses/accounts?
Questions regarding your Veeam contract renewal? Contact us and learn how you can maximize your savings
Do you need additional license, pricing details, product information or have any other sales-related question?
Would you like to become our partner or do you need assistance as our existing partner?
We apologize, but this chat is not available at the moment
We apologize, but this chat is not available at the moment
We apologize, but this chat is not available at the moment
We apologize, but this chat is not available at the moment
Veeam representative will get back to you shortly.
