Set Up Your Harness Account for Azure ARM

Updated 2 months ago by Michael Cretzman

Currently, this feature is behind a Feature Flag. Contact Harness Support to enable the feature. Feature Flags can only be removed for Harness Professional and Essentials editions. Once the feature is released to a general audience, it is available for Trial and Community Editions.

The first step in integrating your ARM templates into Harness is setting up the necessary Harness account components: Delegates, Cloud Providers, and Source Repo Providers.

This topic describes how to set up these components for ARM.

Once you set your account for ARM, you can begin integrating your ARM templates. See Add Azure ARM Templates to Harness.

In this topic:

Before You Begin

Limitations

See Azure Resource Management (ARM) How-tos.

Step 1: Install a Harness Delegate

A Harness Delegate performs the ARM provisioning in your ARM templates. When installing the Delegate for your ARM provisioning, consider the following:

  • Install the Delegate where it can connect to the target infrastructure.
    • If you are using ARM to provision the target infrastructure for an Azure Web App deployment, make sure this Delegate is in, or can connect to, the resource group for your Azure Web App.
  • The Delegate must also be able to connect to your template repo. The Delegate will pull the templates at deployment runtime.
  • All Harness Delegates types can use ARM.

To install a Delegate, follow the steps in Delegate Installation and Management. Once you install the Delegate and it registers with Harness, you'll see it on the Harness Delegates page.

Step 2: Set Up the Azure Cloud Provider

A Harness Azure Cloud Provider connects to your Azure subscription using your Client ID and Tenant ID.

Follow the steps in Add Microsoft Azure Cloud Provider to connect Harness to Azure.

The Azure service account for the Azure Cloud Provider will need the roles required for the Azure resources you are provisioning.

See Azure Resource Management (ARM) in Add Microsoft Azure Cloud Provider.

Step 3: Set Up Source Repo Provider

Harness pulls Azure ARM templates from a Git repo, such as GitHub.

Add a Harness Source Repo Provider to connect Harness to the Git repo for your templates.

You can also add your templates and parameters inline in Harness. In this case, you do not need a Source Repo Provider.

See Add Source Repo Providers.

Option: Set Up the Harness Artifact Server

If you are performing ARM provisioning as part of Azure Web App deployment, add a Harness Artifact Server to connect Harness to your Docker artifact server, such as a Docker Registry or Artifactory.

See Connect to Azure and Artifact Repo for Your Web App Deployments.

If you store the artifact Docker image in Azure Container Registry, then you can use the Azure Cloud Provider you set up and skip the Artifact Server setup.

If you simply going to provision resources without deploying anything, then you don't need to set up a Harness Artifact Server.


How did we do?