Adding a Cosmos DB for MongoDB Instance Using a New Azure Account

When you add a Cosmos DB for MongoDB instance, you can do that while also creating a new Azure account for the instance.

Before You Begin

• For Azure Resource Manager, the cloud account represents an application, and there are two methods of deployment:

  • The traditional method with Azure Active Directory where you must set up the application and tenant. With this option, when you configure the cloud account, you must provide the following information:

    • Subscription ID

    • Tenant ID

    • Application ID and password

    To complete this type of deployment, refer to Configuring Access to Azure Resources.

  • Managed identity authentication with Azure Active Directory. This is a more secure method of deployment. Using this method ensures that your Azure subscription is accessed only from authorized managed identity-enabled virtual machines. In addition, the process of adding an Azure cloud account is more simplified, because you need only the Subscription ID, not the Tenant ID, Application ID, or Application Password.

    To complete this type of deployment, refer to Setting Up Managed Identity Authentication for Azure Resource Manager.

• Verify that the Cosmos DB for MongoDB application or the managed identity of the access node VM has the contributor role enabled on the Azure Cosmos DB account.

• For restricted access, create a custom role using the AzureDBBackupRole.json file at the resource group level of the Cosmos DB account and assign it to the Cosmos DB for MongoDB application or the managed identity of the access node VM.

Procedure

1. From the Command Center navigation pane, go to Protect > Databases.

   The database overview page appears.

2. Click Add instance, and then select Cloud database service.

   The Add Cloud DB Instance page appears.

3. From the Vendor list, select Microsoft Azure, and then click NEXT.

   The Select A Database Service page appears.

4. Select Cosmos DB, and then click NEXT.

   The Select A Plan page appears.

5. From the Plan list, select the backup plan to use for the instance, and then click NEXT.

   The Cloud Account page appears.

6. From the API list, select MongoDB API.

7. Beside the Cloud account list, click +.

   The Add cloud account dialog box appears.

8. In the Name box, type the name for the account.

9. Enter information about the subscription:

   • For the traditional authentication method of deployment, enter the following information:

     • Subscription ID: Enter the subscription ID for the Azure account.

     • Credential: If you have already configured the credentials entity, select the credentials from the list. To define a new credential, click + beside the list. For more information, see Adding Credentials.

     • Access node: Select the access nodes for this cloud account.

   • For the managed identity authentication method of deployment, configure the following settings:

     • Connect using managed identities for Azure resources: Move the toggle key to the right.

     • Subscription ID: Enter the subscription ID for the Azure account.

     • Access node: Select access nodes that have both the Virtual Server and Cloud Apps packages installed.

       Note

       If you configure this cloud account to use managed identity authentication, select only Azure access nodes that use managed identity authentication so that backups and restores will be successful. The access node must be an Azure virtual machine in the same subscription that contains the Cosmos DB account that you want to back up.

10. Click SAVE.

11. Click NEXT.

    The instance details page appears.

12. From the Region list, select the region for the instance.

13. In the Instance box, enter a name for the instance.

14. In the Collection group box, enter a name for the table group, and then click NEXT.

    The Backup Content page appears.

15. To filter the content that is backed up, click EDIT, select or clear the tables that you want to include or exclude, and then click SAVE.

16. Click NEXT to create the instance.

    A summary page is displayed that shows the instance details.

17. Review the summary, and then click FINISH.

What to Do Next

A collection group is created for the instance. You can create more collection groups to meet different backup requirements.