capabilities.work

Provision a Region-Specific Deployment

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

Recipe · 4 steps

Provision a Region-Specific Deployment

with Microsoft Azure · IT Infrastructure Management

Confirm a subscription, create a region-tagged group, deploy, and poll to completion.

  1. Get the subscription and branch: only provision when it reports Enabled, otherwise end the flow.
  2. Create the resource group in the requested region and tag it with that region.
  3. Start an incremental template deployment into the region-tagged group.
  4. Poll the deployment, ending on Succeeded, ending on Failed or Canceled, and looping otherwise.
What you'll need to have ready
  • accessToken: An Azure Resource Manager OAuth2 bearer access token.
  • subscriptionId: The ID of the target subscription.
  • resourceGroupName: The name of the resource group to create.
  • location: The Azure region for the resource group and its region tag (e.g. eastus).
  • deploymentName: The name of the deployment.
  • template: The inline ARM template content to deploy.
  • parameters: Name/value pairs that define the deployment parameters.
  • apiVersion: The Azure Resource Manager API version.
For your developer

Arazzo workflow microsoft-azure:provision-region-deployment, 4 operations: Subscriptions_Get → ResourceGroups_CreateOrUpdate → putSubscriptionsBySubscriptionIdResourcegroupsByResourceGroupNameDeploymentsByDeploymentName → getSubscriptionsBySubscriptionIdResourcegroupsByResourceGroupNameDeploymentsByDeploymentName. Specs on APIs.io.

More recipes with Microsoft Azure

Audit Subscription ResourcesCreate Resource Group and Deploy From Template LinkCreate Resource Group and VerifyDeploy Template to a New Resource GroupDeploy Then Tear Down a Resource GroupDeployment Status and Resulting ResourcesFind Resources by Type and Inspect Their GroupList Providers and ResourcesList Resource Groups and Inventory ResourcesRedeploy Into an Existing Resource Group