Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Azure Function on the plugin site for more information.

A Jenkins plugin to deploy an Azure Function.


To use this plugin to deploy to Azure Function, first you need to have an Azure Service Principal in your Jenkins instance.

  1. Create an Azure Service Principal through Azure CLI or Azure portal.
  2. Open Jenkins dashboard, go to Credentials, add a new Microsoft Azure Service Principal with the credential information you just created.

Then create a Function in Azure portal or through Azure CLI.


You can deploy your project to Azure Function by uploading your build artifacts using GIT or ZIP.

  1. Create a new freestyle project in Jenkins, add necessary build steps to build your code.
  2. Add a post-build action 'Publish an Azure Function'.
  3. Select your Azure credential in Azure Profile Configuration section.
  4. In App Configuration section, choose the resource group and function app in your subscription, and also fill in the files you want to deploy (for example, a jar package if you're using Java).
  5. There are two optional parameters Source Directory and Target Directory that allows you to specify source and target folders when uploading files.
  6. Save the project and build it, your function app will be deployed to Azure when build is completed.

Deploy using Pipeline

You can also use this plugin in pipeline (Jenkinsfile). Here are some samples to use the plugin in pipeline script:

To deploy a NodeJS function app:

azureFunctionAppPublish azureCredentialsId: '<credential_id>',
                        resourceGroup: '<resource_group_name>', appName: '<app_name>',
                        filePath: '**/*.js,**/*.json'

For advanced options, you can use Jenkins Pipeline Syntax tool to generate a sample script.


Azure Function Plugin collects usage data and sends it to Microsoft to help improve our products and services. Read our privacy statement to learn more.

You can turn off usage data collection in Manage Jenkins -> Configure System -> Azure -> Help make Azure Jenkins plugins better by sending anonymous usage statistics to Azure Application Insights.


Version 0.3.0, 2019-01-07

  • Deploy Java function with zip deployment instead of ftp deployment

Version 0.2.1, 2018-04-03

  • Support for credentials lookup in Folders

Version 0.2.0, 2018-01-09

  • Support MSI

Version 0.1.2, 2017-11-07

  • Specify refspec explicitly when doing git push
  • Add Third Party Notice

Version 0.1.1, 2017-10-18

  • Remove runtime licenses

Version 0.1.0, 2017-10-04

  • Initial release
  • No labels


  1. Unknown User (hemanth132)

    We have used the plugin but its not getting deployed..do we need to set up additional maven parameters in freestyle as i have i currently set up maven package as default ....


    Deploy repository is up-to-date. Nothing to commit.
    Done Azure Function App deployment.

    1. Unknown User (arieshout)

      The plugin will compare your local files (as defined in the "Files") with the remote ones. If they are not changed, nothing will be updated.

      If you have already updated your source, make sure they are included in the "Files" list.

  2. Unknown User (mitchellmaler)

    Hello, we currently are using this plugin but found out it only allows SYSTEM ACL service principals. We have multiple nested jobs in GitHub Orgs and Folders with specific permissions and want to be able to add the credential there. Would it be possible to use lower level ACL credentials instead of global ones?

    If you look here 'https://github.com/jenkinsci/azure-credentials-plugin/blob/dev/src/main/java/com/microsoft/azure/util/AzureCredentialUtil.java' all the functions are expected system level credentials. 


    1. Unknown User (arieshout)

      This is now fixed in release 0.2.1. The plugin will lookup credentials in the enclosing folder first.