Skip to main content
Register Azure subscriptions
Updated over a week ago

Before you begin

  • To assign roles or grant access, ensure you have Microsoft.Authorization/role assignment of Global Administrator.
    ​Steps to assign role:

    • Login to your Microsoft Azure portal.

    • Navigate to Microsoft Entra ID > Manage > Users, and select the Admin Account you are using to onboard the subscription.

    • Select Manage > Assigned Roles and verify if the account has a Global Administrator role.
      To assign the role, click Add assignments, locate and select the Global Administrator checkbox and then click Add.
      ​

  • To add a subscription to the Druva console, you must be an administrator or owner of the subscription in the Azure console.
    ​Steps to update access:

    • Login to your Microsoft Azure portal and locate the subscription you wish to onboard.

    • Under Overview verify that My role is set to Owner.
      To update access role, navigate to Access control (IAM) and click Add. Select Add role assignment and search for Owner. Select the user account you wish to use for onboarding the subscription and then click Review+Assign.

  • You must have the Azure Key Vault service registered for the subscription that you want to onboard.
    ​Steps to register Microsoft Key Vault:

    • Login to your Microsoft Azure portal.

    • Navigate to Subscriptions and select the subscription that you need to register on Druva.

    • Scroll to the Resource providers in the Subscription Settings.

    • Locate Microsoft.KeyVault from the list of resource providers and click Register.


      πŸ“ Note
      ​To register multiple subscriptions on Druva, repeat the steps above for each subscription individually.


  • To onboard or register subscriptions, ensure that you have the Users can register applications permission enabled for your user account in the Azure environment.
    ​Steps to enable permissions:

    • Login to your Microsoft Azure portal.

    • Navigate to Microsoft Entra ID > Manage > User Settings

    • Set the Users can register applications toggle to Yes. Click Save.

Add new subscription

  1. Log in to the Management Console.

  2. On the console, from the top menu, select Organization.

  3. Select Protect > Azure Workloads > Virtual Machines.

  4. Click Register.

  5. On the Microsoft Sign in page, enter the Microsoft Azure credentials and click Next.

  6. Accept the default permissions.

  7. On the subscriptions modal window that appears, do the following:

    1. Select the subscription(s) you want to protect and click Next.


      πŸ“ Note
      ​You cannot select subscriptions that are already registered or onboarded.


      SelectSubs-Updated.png
    2. On the Access & Storage tab, in the Group Access section, either select an Administrative Group or create a new Administrator Group.
      ​

      Onboarding-AssignAdmin-Updated.png
    3. In the Storage Rules section, select a default Druva storage for all regions and click Next. You can also add additional storage rules.
      ​

      AssignStorage.png

      πŸ“ Notes

      • Once you assign a default storage rule, you cannot delete it later. However, you can delete other storage rules created subsequently.

      • You can create multiple storage rules.

      • When assigning storage rules, adhere to your compliance and governance policies.

      • Once storage is assigned to a region then it gets permanently associated with that region. Consequently, all the VMs will continue to get backed up and stored in this region.


    4. On the E-Key Settings tab, select the following:

      • Select the Primary Region. This is the Azure Region which is used to create the Security Key Vault Name and Resource Group
        ​


        πŸ“ Note
        ​Define a Secondary Region as well, which will be used to create the Key vault and Resource Group, when the Primary Region is unavailable.


      • Select the Authorization check box. This authorizes creation of the encryption keys for the selected subscriptions.
        If not authorized, backups will fail for resources within these subscriptions.
        ​


        πŸ“ Note
        ​The subscriptions are onboarded successfully even if you do not authorize the creation of an access key in your Azure vault. However, resources in these subscriptions will not be backed up unless you authorize the subscriptions.


      • Click Finish​.
        The subscriptions are onboarded successfully and are listed on the Azure subscriptions listing page.
        ​

Add subsequent subscriptions

You can add subscriptions during onboarding or later at any point in time. To add subscriptions for the first time, see Register Azure subscriptions.

For adding more subscriptions at a later stage, see the following procedure:

  1. Log in to the Management Console.

  2. On the console, from the top menu, select Organization.

  3. Select Protect > Azure Workloads > Virtual Machines.

  4. On the Azure subscriptions page, click Add Subscriptions.

  5. On the Microsoft Sign in page, enter the Microsoft Azure credentials and click Next.

  6. Accept the default permissions.

  7. On the Add Subscriptions window, do the following:

    1. Select the subscription(s) you want to protect and click Next.


      πŸ“ Note
      ​You cannot select subscriptions that are already onboarded.


    2. On the Access & Storage tab, in the Group Access section, either select an Administrative Group or create a new Administrator Group and click Next.
      ​

      Onboarding-AssignAdmin-SubsequentSubs.png
    3. On the E-Key Settings tab, select the following:

      • Select the Primary Region. This is the Azure Region which is used to create the Security Key Vault Name and Resource Group.
        ​


        πŸ“ Note
        ​Define a Secondary Region as well, which will be used to create the Key vault and Resource Group, when the Primary Region is unavailable.


      • Select the Authorization check box. This authorizes creation of the encryption keys for the selected subscriptions.
        If not authorized, backups will fail for resources within these subscriptions.
        ​


        πŸ“ Note
        ​The subscriptions are onboarded successfully even if you do not authorize the creation of an access key in your Azure vault. However, resources in these subscriptions will not be backed up unless you authorize the subscriptions.


      • Click Finish​.
        The subscriptions are onboarded successfully and are listed on the Azure subscriptions listing page.

Administrative groups

An administrative group is a logical categorization of subscriptions. For example, subscriptions with resources located in one region can belong to one administrative group. An administrative group allows you to segregate subscriptions for Role-Based Access Control (RBAC) purposes, enabling more granular and organized management of resources and permissions.

While onboarding Azure subscriptions, you must assign administrative groups. You can assign one administrative group to manage multiple subscriptions. If no administrative group is available, you can create an administrative group.

Considerations

The following are some of the important points to consider for administrative groups:

  • You should be a Cloud Admin to create or edit an administrative group.

  • Administrative group is associated with an organization. If you want to create an administrative group for a specific organization, you must select that particular organization.

  • You can select an administrative group while onboarding Azure subscriptions.

  • You can select one existing administrative group for the multiple subscriptions. If no group exists, you can create an administrative group while onboarding Azure subscriptions.

  • You can delete an administrative group. However, before deleting, you must move the Hybrid resources, AWS accounts, and Azure subscriptions to a different group.

  • If you want to give granular access to the onboarded subscriptions, you can do so from DCP or Enterprise Workloads console where you can specify Azure subscriptions for specific group admins.

Create a new administrative group

  1. Log in to the Management Console.

  2. On the console, from the top menu, select Organization.

  3. Select Protect > Azure Workloads > Virtual Machines.

  4. On the Access & Storage tab, in the Group Access section, click on the Administrative Group dropdown.

  5. Click + New Administrative Group.
    ​

    CreateNewAdmin.png
  6. On the New Administrative Group window, provide name and description and click Save.

Delete an administrative group

You can delete an Administrative group. However, before deleting, you must move the Hybrid resources, AWS accounts, and Azure subscriptions to a different group.

  1. Log in to the Management Console.

  2. On the console, from the top menu, select Organization and then click Manage > Administrative Groups.
    The Manage Administrative Groups page displays a list of available administrative groups.

  3. To delete an administrative group, do either of the following:

    • Select an administrative group and click Delete.

    • Click on the administrative group that you want to delete, and on the Administrative group details page, click Delete.

  4. Click Yes on the confirmation dialog box to proceed with the deletion.

Related keywords: key vault, keyvault, azurevault, vault, azure vault, azure vault key, azurevaultkey

Did this answer your question?