Subtenant Account

In this article

    To work with the cloud repository, a subtenant uses the subtenant account. Veeam Backup & Replication offers two types of subtenant accounts:

    Subtenant AccountNote

    In the scenario where the SP and tenant belong to the same organization that has Microsoft Active Directory deployed, the SP can allow AD users to create Veeam Agent backups in a cloud repository. To do this, the SP must configure Active Directory tenant accounts instead of subtenant accounts. Veeam Agent users will be able to connect to the SP using credentials of their accounts in AD without the need to remember additional credentials.

    To learn more, see Active Directory Tenant Account.

    Standalone Subtenant Account

    In the scenario where users on the tenant side back up data to the cloud repository with Veeam Agent operating in the standalone mode, the tenant or SP must create subtenant accounts. The number of subtenant accounts created per tenant is not limited in Veeam Backup & Replication.

    Typically, the tenant is the party responsible for creating and managing subtenant accounts. However, the SP can perform the same operations with subtenant accounts as the tenant. This allows the SP to create, edit or delete subtenant accounts upon tenant requests, for example, if the tenant has no access to the Veeam Backup & Replication console.

    Veeam Backup & Replication saves information about subtenant accounts in the Veeam Backup & Replication database. Every time the tenant or SP performs an operation with the subtenant account, Veeam Backup & Replication updates the subtenant data and replicates this data between the tenant side and SP side.

    Subtenant AccountNote

    Mind the following:

    • End users on the tenant side can use subtenant accounts only to connect to the SP in Veeam Agent for Microsoft Windows and Veeam Agent for Linux. The tenant cannot use credentials of a subtenant account to add a SP in the Veeam backup console.
    • Veeam Agent users on the tenant side can connect to the SP and create backups on the cloud repository under the tenant account. However, it is recommended to provide every user with a separate subtenant account. In this case, the tenant or SP can allocate storage resources on the cloud repository individually for every subtenant so that subtenants’ data is stored in the cloud in an isolated and segregated way.

     

    Managed Subtenant Account

    In the Veeam Agent management scenario where Veeam Agent is deployed and managed remotely from Veeam Backup & Replication, the tenant or SP does not need to create subtenant accounts to back up Veeam Agent machines to the cloud repository. In this scenario, Veeam Backup & Replication creates subtenant accounts automatically. Such accounts are considered as managed subtenant accounts.

    Veeam Backup & Replication creates a managed subtenant account for each machine added to a backup policy. A machine uses this account to connect to the SP during the backup process.

    Veeam Backup & Replication automatically generates names, passwords and descriptions for managed subtenant accounts. In contrast to standalone subtenant accounts, passwords for managed subtenant accounts are saved in the Veeam backup database on the tenant backup server only. Passwords for managed subtenant accounts are not passed to the SP side.

    The tenant or SP can manually edit a managed subtenant account, if necessary. The following operations are available:

    To learn more about Veeam Cloud Connect support for Veeam Agent managed by Veeam Backup & Replication, see the Backup to Veeam Cloud Connect Repository section in the Veeam Agent Management Guide.

    I want to report a typo

    There is a misspelling right here:

     

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