capabilities.work

Provision a Staging Deployment Slot

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

Recipe · 3 steps

Provision a Staging Deployment Slot

with Microsoft Azure Functions

Create a deployment slot, wait for it to run, and start it.

  1. Create or update the deployment slot. ARM returns 202 when the create is accepted as a long-running operation.
  2. Read the slot resource and confirm it reports a Running state. Use this step in a retry loop until the slot finishes provisioning.
  3. Explicitly start the slot to guarantee it is live before any swap.
What you'll need to have ready
  • subscriptionId: The Azure subscription identifier (GUID).
  • resourceGroupName: The resource group that contains the function app.
  • name: The name of the parent function app.
  • slot: The name of the deployment slot to create (e.g. "staging").
  • location: The Azure region for the slot (matches the parent app region).
  • serverFarmId: The resource id of the App Service plan / serverFarm hosting the slot.
  • apiVersion: The ARM api-version to use for all requests.
For your developer

Arazzo workflow microsoft-azure-functions:provision-staging-slot, 3 operations: WebApps_CreateOrUpdateSlot → WebApps_GetSlot → WebApps_StartSlot. Specs on APIs.io.

More recipes with Microsoft Azure Functions

Create a Function in a Function App and Verify ItDeploy a Function and Sync Its TriggersInspect a Function App and Issue an Admin TokenProvision an Azure Function App and Confirm It Is RunningRecord a Deployment and Verify the Deployment LogRotate a Function Key and Confirm ItRotate a Host-Level Key and List All Host KeysPreview and Swap a Slot Into ProductionUpdate Function App Settings and Confirm ThemUpdate Function App Site Configuration and Restart