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:

• Execute Activity, HTTP, and Orchestrator Azure Function Apps.
• Manage Azure Functions credentials in a secure connection profile.
• Connect to any Azure Functions endpoint.
• Integrate Azure Functions jobs with other Control-M jobs into a single scheduling environment.
• 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.

Control-M for Azure Functions Compatibility

The following table lists the prerequisites that are required to use the Azure Functions plug-in, each with its minimum required version.

Component	Version
Control-M/EM	9.0.20.200
Control-M/Agent	9.0.21.200
Control-M Application Integrator	9.0.21.200
Control-M Automation API	9.0.20.240

Control-M for Azure Functions is supported on Control-M Web and Control-M Automation API, but not on Control-M client.

To download the required installation files for each prerequisite, see Obtaining-Control-M-Installation-Files.

Setting up Control-M for Azure Functions

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

Before You Begin

Verify that Automation API is installed, as described in Automation API Installation.

Begin

1. Create a temporary directory to save the downloaded files.
2. Download the Azure Functions plug-in from the Control-M for Azure Functions download page in the EPD site.
3. Install the Azure Functions plug-in via one of the following methods:
   • (9.0.21 or higher) Use the Automation API Provision service:
     1. Log in to the Control-M/EM Server machine as an Administrator and store the downloaded zip file in the one of the following locations (within several minutes, the job type appears in Control-M Web):
        • Linux: $HOME/ctm_em/AUTO_DEPLOY
        • Windows: <EM_HOME>\AUTO_DEPLOY
     2. Log in to the Control-M/Agent machine and run the provision image command, as follows:
        • Linux: ctm provision image ZFA_plugin.Linux
        • Windows: ctm provision image ZFA_plugin.Windows
   • (9.0.20.200 or lower) Use the Automation API Deploy service, as described in deploy jobtype.
4. Create an Azure Functions connection profile in Control-M Web or Automation API, as follows:
   • Web: Creating a Centralized Connection Profile with Azure Functions Connection Profile Parameters
   • Automation API: ConnectionProfile:AzureFunctions
5. Define an Azure Functions job in Control-M Web or Automation API, as follows:
   • Web: Creating a Job with Azure Functions Job parameters
   • Automation API: Job:AzureFunctions

Change Log

The following table provides details about changes that were introduced in new versions of this plug-in:

Plug-in Version	Details
1.0.09	New Unauthenticated option for the Identity Type in the connection profile. New job attributes Azure Resource and Azure Resource Scope.
1.0.08	Added API-VERSION to the job properties.
1.0.07	Added ability to kill Durable Functions.
1.0.06	Corrected issue in the Function App ID authentication in the Connection Profile.
1.0.05	New Function APP ID authentication. New connection profile fields, Function App Web Site and Custom App Key.
1.0.03	Added ability to trigger Orchestrator functions.
1.0.02	New fields Verification Poll Interval and Failure Tolerance, and a new Durable option in the Function Type attribute.