Provision Container App
A 3-step recipe with Azure Container Apps. We can help you get access.
Recipe · 3 steps
Provision Container App
with Azure Container Apps · IT Infrastructure Management
Create a container app in a ready environment and wait until it is provisioned.
- Read the managed environment and confirm it has finished provisioning before binding a new app to it.
- Submit the create-or-update for the container app, binding it to the resolved environment id and defining a single container with external ingress in the ARM properties envelope.
- Read the container app and check its provisioningState, looping while it is still in progress and branching once it settles.
What you'll need to have ready
- subscriptionId: The Azure subscription ID.
- resourceGroupName: The name of the resource group.
- environmentName: The managed environment that hosts the app.
- containerAppName: The name of the container app to create.
- location: The Azure region for the app (e.g. eastus).
- image: The container image to run (e.g. mcr.microsoft.com/k8se/quickstart:latest).
- targetPort: The port the container listens on for ingress traffic.
- apiVersion: Client API version.
For your developer
Arazzo workflow azure-container-apps:provision-container-app, 3 operations: ManagedEnvironments_Get → ContainerApps_CreateOrUpdate → ContainerApps_Get. Specs on APIs.io.