Azure Credentials

ID: azure-credentials

Important: This plug-in is maintained by the Jenkins community and won’t be supported by Microsoft as of February 29, 2024.

Using Credentials Binding and Az CLI

Credentials Binding and Az CLI is the recommended way to integrate with Azure services.

  1. Make sure you have Az CLI installed, version 2.0.67 or higher.

  2. Create a service principal using Az CLI:

        az ad sp create-for-rbac
  3. Make sure the Credentials plugin is installed and add a credential in Jenkins Credentials page.

    Ensure that the credential kind is Username with password and enter the following items:

    • Username - The appId of the service principal created.
    • Password - The password of the service principal created.
    • ID - Credential identifier such as AzureServicePrincipal

    Sample Jenkinsfile (declarative pipeline)

    pipeline {
        agent any
        environment {
        stages {
            stage('Example') {
                steps {
                       withCredentials([usernamePassword(credentialsId: 'myAzureCredential', passwordVariable: 'AZURE_CLIENT_SECRET', usernameVariable: 'AZURE_CLIENT_ID')]) {
                                sh 'az login --service-principal -u $AZURE_CLIENT_ID -p $AZURE_CLIENT_SECRET -t $AZURE_TENANT_ID'
                                sh 'az account set -s $AZURE_SUBSCRIPTION_ID'
                                sh 'az ...'

About this plugin

Jenkins plugin to manage Azure credentials.

It supports the following Azure credential types:

  1. Azure Service Principal, with the following authentication mechanism:
    • Client secret
    • Certificate (Add the certificate to Jenkins credentials store and reference it in the Azure Service Principal configuration)
  2. Azure Managed Service Identity (MSI)
  3. Credentials In Azure Key Vault

Using Azure credentials in your own Jenkins plugin

  1. Update your project POM file to reference azure-credentials plugin and necessary dependencies:

  2. Add the credential selector in the config.jelly and Descriptor

     <f:entry title="${%azureCredentialsId_title}" field="azureCredentialsId">
         <c:select expressionAllowed="false"/>
     public ListBoxModel doFillAzureCredentialsIdItems(@AncestorInPath Item owner) {
         StandardListBoxModel model = new StandardListBoxModel();
         model.add(Messages.ACSDeploymentContext_selectAzureCredentials(), Constants.INVALID_OPTION);
         model.includeAs(ACL.SYSTEM, owner, AzureBaseCredentials.class);
         return model;
  3. Build the Azure client from the credential

    AzureBaseCredentials credential = AzureCredentialUtil.getCredential2(credentialsId);
    // Resolve the class loader incompatibility issue. Works along with maskClasses in the POM
    TokenCredentialData token = TokenCredentialData.deserialize(credential.serializeToTokenData());
    Azure azClient = AzureClientFactory.getClient(token);

Getting an iterator to all SYSTEM owned Azure Credentials

CredentialsProvider.lookupCredentials(AzureBaseCredentials.class, null, ACL.SYSTEM, Collections.<DomainRequirement>emptyList());

Using AzureCredentials in the job (freestyle / pipeline)

Custom binding for AzureCredentials to support reading Azure service principal in both freestyle and pipeline using Credentials Binding plugin.

In freestyle jobs, click Use secret text(s) or file(s) in the Build Environment in the configuration page and add a Microsoft Azure Service Principal item, which allows you add credential bindings where the Variable value will be used as the name of the environment variable that your build can use to access the value of the credential. With the default variable names you can reference the service principal as the following:

echo "My client id is $AZURE_CLIENT_ID"
echo "My client secret is $AZURE_CLIENT_SECRET"
echo "My tenant id is $AZURE_TENANT_ID"
echo "My subscription id is $AZURE_SUBSCRIPTION_ID"

In pipelines, there're two ways to construct this binding:

  1. With defaults, which will read specified service principal into four predefined environment variables: AZURE_SUBSCRIPTION_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID. Sample pipeline code:

    withCredentials([azureServicePrincipal('credentials_id')]) {
        sh 'az login --service-principal -u $AZURE_CLIENT_ID -p $AZURE_CLIENT_SECRET -t $AZURE_TENANT_ID'
  2. With custom name, where you can control the names of the variables. Sample pipeline code:

    withCredentials([azureServicePrincipal(credentialsId: 'credentials_id',
                                        subscriptionIdVariable: 'SUBS_ID',
                                        clientIdVariable: 'CLIENT_ID',
                                        clientSecretVariable: 'CLIENT_SECRET',
                                        tenantIdVariable: 'TENANT_ID')]) {
        sh 'az login --service-principal -u $CLIENT_ID -p $CLIENT_SECRET -t $TENANT_ID'

Reporting bugs and feature requests

We use Jenkins JIRA to record all bugs and feature requests. Please follow beblow steps to create your own issues.

  1. Search in Jira to see if the issue was existed already.
  2. Create a new issue with the component azure-credentials-plugin .

You can refer to Jira doc for detailed instructions about creating an issue.

ArchivesGet past versions
Version: 177.v816b81058012
Requires Jenkins 2.263.1
Installs: 5,055
xu zhang
Tim Jacomb
Help us improve this page!
To propose a change submit a pull request to the plugin page on GitHub.