Connect to Azure and Artifact Repo for Your Web App Deployments
You connect Harness to your Azure account to deploy Azure Web Apps. You make the connection using a Harness Cloud Provider.
You deploy your Web App using a Docker image. You connect to your image's repo using a Harness Artifact Server. If your Docker image is stored in Azure Container Registry, then you can use this Azure Cloud Provider you set up and skip the next step.
In this topic:
- Before You Begin
- Supported Platforms and Technologies
- Review: Azure Connection Options
- Step 1: Install a Harness Delegate
- Step 2: Set Up the Azure Cloud Provider
- Step 3: Set Up the Harness Artifact Server
- Next Steps
- See Also
Before You Begin
Supported Platforms and Technologies
Review: Azure Connection Options
As covered in Harness Key Concepts, you need to install a Harness Delegate in your infrastructure before setting up your Harness deployment.
There are several types of Delegates you can use for an Azure App Service deployment, described in Delegate Installation Overview.
Shell Script, Docker, Kubernetes, and Helm Delegates are all options.
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.
Make sure this Delegate is in, or can connect to, the resource group for your Azure Web App.
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.
That's all the setup you need to connect Harness to your account and start your deployment.
Step 3: Set Up the Harness Artifact Server
A Harness Azure Web App deployment uses a Docker image. You connect Harness to the same Docker repo you use in your Web App in Azure. You made this connection using a Harness Artifact Server.
The Harness Azure Web Application Service type supports the following repos:
- Docker Registry: see Add Docker Registry Artifact Servers.
- Artifactory: see Add Artifactory Servers.
- Azure Container Registry: you can use the Azure Cloud Provider you set up in the previous step.
For example, here are the Docker Hub settings in an Azure Web App:
Here's the Harness Docker Registry Artifact Server:
The above example uses a public repo, and it requires no username or password.
Later, in the Harness Service, you'll add an Artifact Source that uses this Artifact Server and points to the Docker Image Name:
- Run a custom container in Azure from Azure.