Skip to content
Slipwaydocs

Microsoft Azure

Deploy to AKS, App Service and Container Apps; read Azure Monitor; use federated credentials.

At a glance

Section titled “At a glance”
Category Cloud & Kubernetes
Authentication Federated credential on an app registration or managed identity
Provider id azure

What it does

Section titled “What it does”
  • App Service slot swaps
  • Container Apps revisions and traffic weights
  • AKS via Kubernetes integration
  • Azure Monitor metrics for verification

Set up

Section titled “Set up”
  1. Create the trust relationship on the cloud side (see the matching OIDC guide).
  2. In Settings, Integrations, add the connection and choose the runner pool that can reach it.
  3. Create an Infrastructure on an environment that references the connection.
  4. Use Test infrastructure to confirm connectivity before the first deployment.

Configuration

Section titled “Configuration”

Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.

provider: azure
config:
  tenant_id: 00000000-0000-0000-0000-000000000000
  client_id: 11111111-1111-1111-1111-111111111111
  subscription_id: 22222222-2222-2222-2222-222222222222

Notes

Section titled “Notes”

See OIDC with Azure.

Section titled “Related”