Azure Function

Use the Azure Function integration to let a workbench call one of your HTTP-triggered Azure Functions as an action. You describe what the function does and the input it accepts, and the workbench agent decides when to call it, builds the input, and reads the function's response. Typical uses include running a runbook step, querying an internal system, or triggering automation you already host on Azure Functions.

The Azure Function tool reuses a Plural cloud connection for Azure credentials. This guide uses the Plural Console UI. For the complete list of integrations and general tool behavior, see Workbench tools.

Prerequisites

Before you begin, make sure you have:

• A deployed Azure Function with an HTTP trigger that accepts POST requests with a JSON body.
• The function's Azure resource ID. See Find the function identifier.
• An Azure cloud connection for the function's subscription, whose service principal can read the function's keys. See Grant access.
• Permission in Plural Console to create a configured tool and edit the target workbench.
• An existing workbench, or permission to create one. See Setting up a workbench.

Find the function identifier

The tool identifies the function by its full resource ID:

/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.Web/sites/{function-app}/functions/{function-name}

The subscription in the ID must match the Subscription ID of the cloud connection. You can find the ID in the Azure portal on the function's Overview page, or with the Azure CLI:

az functionapp function show \
  --resource-group my-rg \
  --name my-function-app \
  --function-name restart-service \
  --query id -o tsv