capabilities.work

Provision an Azure Function App and Confirm It Is Running

A 3-step recipe with Microsoft Azure Functions. We can help you get access.

Recipe · 3 steps

Provision an Azure Function App and Confirm It Is Running

Create a function app, wait for it to run, and list its functions.

  1. Create or update the Microsoft.Web/sites resource as a function app. ARM returns 202 when the create is accepted as a long-running operation, or 200 when it completes synchronously.
  2. Read the function app resource and confirm it reports a Running state. Use this step in a retry loop until the state transitions out of provisioning.
  3. Enumerate the functions deployed into the now-running function app.
What you'll need to have ready
  • subscriptionId: The Azure subscription identifier (GUID).
  • resourceGroupName: The resource group that will contain the function app.
  • name: The globally unique name of the function app to create.
  • location: The Azure region for the function app (e.g. "East US").
  • serverFarmId: The resource id of the App Service plan / serverFarm to host the app.
  • apiVersion: The ARM api-version to use for all requests.
For your developer

Arazzo workflow microsoft-azure-functions:provision-function-app, 3 operations: WebApps_CreateOrUpdate → WebApps_Get → WebApps_ListFunctions. Specs on APIs.io.