English

Creating a Connector from the Azure Marketplace

Contributors netapp-bcammett Download PDF of this page

It’s best to create a Connector directly from Cloud Manager, but you can launch a Connector from the Azure Marketplace, if you prefer. After you create and set up the Connector, Cloud Manager will automatically use it when you create new working environments.

Creating a Connector in Azure

Deploy the Connector in Azure using the image in the Azure Marketplace and then log in to the Connector to specify your Cloud Central account.

Steps
  1. Go to the Azure Marketplace page for Cloud Manager.

  2. Click Get it now and then click Continue.

  3. From the Azure portal, click Create and follow the steps to configure the virtual machine.

    Note the following as you configure the VM:

  4. On the Review + create page, review your selections and click Create to start the deployment.

    Azure deploys the virtual machine with the specified settings. The virtual machine and Connector software should be running in approximately five minutes.

  5. Open a web browser from a host that has a connection to the Connector virtual machine and enter the following URL:

    http://ipaddress:80

  6. After you log in, set up the Connector:

    1. Specify the Cloud Central account to associate with the Connector.

    2. Enter a name for the system.

      A screenshot that shows the set up Cloud Manager screen that enables you to select a Cloud Central account and name the system.

Result

The Connector is now installed and set up. You must grant Azure permissions before users can deploy Cloud Volumes ONTAP in Azure.

Granting Azure permissions

When you deployed the Connector in Azure, you should have enabled a system-assigned managed identity. You must now grant the required Azure permissions by creating a custom role and then by assigning the role to the Connector virtual machine for one or more subscriptions.

Steps
  1. Create a custom role using the Cloud Manager policy:

    1. Download the Cloud Manager Azure policy.

    2. Modify the JSON file by adding Azure subscription IDs to the assignable scope.

      You should add the ID for each Azure subscription from which users will create Cloud Volumes ONTAP systems.

      Example

      "AssignableScopes": [
      "/subscriptions/d333af45-0d07-4154-943d-c25fbzzzzzzz",
      "/subscriptions/54b91999-b3e6-4599-908e-416e0zzzzzzz",
      "/subscriptions/398e471c-3b42-4ae7-9b59-ce5bbzzzzzzz"

    3. Use the JSON file to create a custom role in Azure.

      The following example shows how to create a custom role using the Azure CLI 2.0:

      az role definition create --role-definition C:\Policy_for_cloud_Manager_Azure_3.8.7.json

      You should now have a custom role called Cloud Manager Operator that you can assign to the Connector virtual machine.

  2. Assign the role to the Connector virtual machine for one or more subscriptions:

    1. Open the Subscriptions service and then select the subscription in which you want to deploy Cloud Volumes ONTAP systems.

    2. Click Access control (IAM).

    3. Click Add > Add role assignment and then add the permissions:

      • Select the Cloud Manager Operator role.

        Cloud Manager Operator is the default name provided in the Cloud Manager policy. If you chose a different name for the role, then select that name instead.
      • Assign access to a Virtual Machine.

      • Select the subscription in which the Connector virtual machine was created.

      • Select the Connector virtual machine.

      • Click Save.

    4. If you want to deploy Cloud Volumes ONTAP from additional subscriptions, switch to that subscription and then repeat these steps.

Result

The Connector now has the permissions that it needs to manage resources and processes within your public cloud environment. Cloud Manager will automatically use this Connector when you create new working environments. But if you have more than one Connector, you’ll need to switch between them.