Control-M for Azure Functions

Azure Function job enables you to develop, test, and run applications in the cloud.

Control-M for Azure Functions enables you to do the following:

  • Connect to any Azure Functions endpoint from a single computer with secure login, which eliminates the need to provide authentication.
  • Integrate Azure Functions jobs with other Control-M jobs into a single scheduling environment.
  • Execute Activity, HTTP, and Orchestrator Azure Function Apps.
  • Monitor the status, results, and output of Azure Functions jobs in the Monitoring domain.
  • Attach an SLA job to your Azure Functions jobs.
  • Introduce all Control-M capabilities to Control-M for Azure Functions including advanced scheduling criteria, complex dependencies, Resource Pools, Lock Resources, and variables.
  • Run 50 Azure Functions jobs simultaneously per Agent.

Setting up Control-M for Azure Functions

This procedure describes how to install the Azure Functions plug-in, create a connection profile, and define an Azure Functions job in Helix Control-M and Automation API.

Before you Begin

  • Verify that Automation API is installed, as described in Setting up the API.
  • Verify that Agent version or later is installed.


  1. On the Agent host, set the Java environment variable by running one of the following commands through a command line:
    • Linux:
      • Bourne shell/bash: export BMC_INST_JAVA_HOME=<java_11_directory>
      • csh/tcsh: setenv BMC_INST_JAVA_HOME <java_11_directory>
    • Windows: set BMC_INST_JAVA_HOME="<java_11_directory>"
  2. Run one of the following API commands:
    • For a fresh installation, use the provision image command:
      • Linux: ctm provision image ZFA_plugin.Linux
      • Windows: ctm provision image ZFA_plugin.Windows
    • For an upgrade, use the following command:
      ctm provision agent::update
  3. Create an Azure Functions connection profile in Helix Control-M or Automation API, as follows:
  4. Define an Azure Functions job in Helix Control-M or Automation API, as follows:


To remove this plug-in from an Agent, follow the instructions in Removing a Plug-in. The plug-in ID is ZFN032022.

Was this page helpful? Yes No Submitting... Thank you