Required Permissions

In this article

    Make sure user accounts that you plan to use have permissions described in this section:

    Veeam Backup & Replication User Account Permissions

    The user account that you plan to use when installing and working with Veeam Backup & Replication must have permissions described in the Installing and Using Veeam Backup & Replication section in the Veeam Backup & Replication User Guide.

    If you plan to connect to a tenant using Remote Access Console, you must run the console as administrator.

    Azure User Account Permissions

    The Azure user account that you plan to use when deploying a new Veeam Backup for Microsoft Azure appliance or connecting to an existing appliance must have permissions described in the Azure Role Permissions section of the Veeam Backup for Microsoft Azure User Guide.

    Azure Storage Account Permissions

    The Azure storage account that you plan to use when connecting to an existing appliance or adding a new Blob storage must have permissions described in the Repository Account section of the Veeam Backup for Microsoft Azure User Guide.

    AWS User Account Permissions

    The AWS user account that you plan to use when restoring Azure VMs to Amazon EC2 must have permissions described in the AWS IAM User Permissions section of the Veeam Backup & Replication User Guide.

    Permissions for Virtualization Servers and Hosts

    If you plan to copy backups to on-premises repositories, to perform restore to VMware vSphere or Microsoft Hyper-V, or to perform other tasks related to virtualization servers or hosts, you must check that the user account specified for these servers and host has permissions listed in both the Using Virtualization Servers and Hosts section in the Veeam Backup & Replication User Guide for VMware vSphere and in the Using Virtualization Servers and Hosts section in the Veeam Backup & Replication User Guide for Microsoft Hyper-V.

    I want to report a typo

    There is a misspelling right here:

     

    I want to let the Veeam Documentation Team know about that.