Quantcast
Channel: Veeam Support Knowledge Base
Viewing all articles
Browse latest Browse all 4425

Veeam Office 365 Complete Permissions

$
0
0

Challenge

Configuring the required granular permissions for Veeam Backup for Microsoft Office 365.

Cause

Veeam Backup for Microsoft Office version 4c supports two different modern authentication methods and a basic authentication method for working with Office 365 organizations.

Depending on your Office 365 tenant configuration and the restrictions on using legacy authentication protocols, you can use one of the following authentication methods: 

These authentication types require different sets of permissions to be configured.

Solution

Configure permissions required 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

You can either allow Veeam Backup for Office 365 to create the Azure AD application and all the required application permissions will be granted automatically:

https://helpcenter.veeam.com/docs/vbo365/guide/register_ad_application.html?ver=40#cna

Or you can create an Azure AD application manually: https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app

And then configure the permissions in accordance with "Veeam Backup for Microsoft Office 365 Version 4c" section of this User Guide page: https://helpcenter.veeam.com/docs/vbo365/guide/azure_ad_applications.html?ver=40 

Both Application permissions and Delegated permissions should be configured in the Azure AD application.
For more information about permission types please visit https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-permissions-and-consent



Configure permissions required for organizations with modern authentication and legacy authentication protocols

Before configuring permissions below, make sure that Security Defaults are disabled in your Office 365 tenant:

https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/concept-fundamentals-security-defaults

And Conditional Access policies are not blocking legacy authentication protocols for the Veeam service account:

https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/


Veeam service account permissions


Exchange

 Configuring permissions for Exchange Online.

Below you may see the example of PowerShell cmdlets you could use to configure a new authentication policy with enabled AllowBasicAuthPowershell and AllowBasicAuthWebService for the Veeam service account.

To create a new authentication policy named "Allow Basic Auth":

New-AuthenticationPolicy -Name "Allow Basic Auth"

To enable AllowBasicAuthPowershell and AllowBasicAuthWebService in the new authentication policy:

Set-AuthenticationPolicy -Identity "Allow Basic Auth" -AllowBasicAuthPowershell
Set-AuthenticationPolicy -Identity "Allow Basic Auth" -AllowBasicAuthWebService

To assign this policy to the Veeam service account:

Set-User -Identity <UserIdentity> -AuthenticationPolicy "Allow Basic Auth"

Where <UserIdentity> is the Veeam service account.



SharePoint

Configuring Permissions for SharePoint Online.

  • Grant Veeam service account with the SharePoint Administrator Role in Azure Admin Center: https://admin.microsoft.com/
  • In the SharePoint Admin Center open [Policies] > [Access control]  and set "Apps that don't use modern authentication" to "Allow Access".

    User-added image
    User-added image


App password

Configuring user App password.


Azure AD Application permissions

Configuring Azure AD Application.


 

Configure 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.


Viewing all articles
Browse latest Browse all 4425

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>