Connect to Azure for VMSS Deployments

Updated 1 month ago by Michael Cretzman

Currently, this feature is in Beta and 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.

You connect Harness to your Azure Azure to deploy virtual machine scale sets using a Harness Azure Cloud Provider.

In this topic:

Before You Begin

Supported Platforms and Technologies

See  Supported Platforms and Technologies.

Review: Azure Connection Options

As covered in Harness Key Concepts, you need to install a Harness Delegate in your target infrastructure before setting up your Harness deployment.

There are several types of Delegates you can use for a virtual machine scale set deployment, described in Delegate Installation Overview.

Shell Script, Docker, Kubernetes, and Helm Delegates are all options.

The simplest option for most users is to install the Harness Shell Script Delegate on a VM in the same resource group, virtual network, and subnet where your virtual machine scale set will be deployed.

Step 1: Install a Harness Delegate

Follow the installation steps for the Harness Delegate you want to install. See Delegate Installation Overview for the available options.

Ensure this Delegate is in or can connect to the resource group, virtual network, and subnet where your virtual machine scale set will be deployed.

Step 2: Set Up the Azure Cloud Provider

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

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

That's all the setup you need to connect Harness to your account and start your virtual machine scale set deployment.

A virtual machine scale set deployment uses an Azure Shared Image Gallery and image. Access to those resources use the same Azure Cloud Provider.

Next Steps

See Also

See the following docs from Azure:


How did we do?