# Pagerless for Azure Container Apps

> Woken only when it matters, and one tap undoes a bad deploy: Pagerless moves to the previous revision.

URL: https://pagerless.dev/integrations/azure-container-apps
Updated: 2026-10-22

## Set up

Node, Go or Python SDK.

Store the key with `az containerapp update -n APP -g RG --set-env-vars PAGERLESS_KEY=pl_live_...`. Or run `npx pagerless connect` and it finds your services and places the key for you.

## Fixes on Azure Container Apps

| Fix | On Azure Container Apps |
| --- | --- |
| Undo the update | Moves to the previous revision |
| Restart | Restarts revisions |
| Add capacity | Changes min and max replicas |
| Deploy events | Yes: errors right after a deploy are tied to it |
| Access it needs | an Entra app with an RBAC role |

## Questions

### Can Pagerless roll back Azure Container Apps automatically?

Yes, if your rules set undo to alone. By default it asks first, and approving an undo needs your passkey (Face ID or Touch ID). It then moves to the previous revision.

### Does Pagerless need admin access to Azure Container Apps?

It needs an Entra app with an RBAC role. It is stored encrypted and used only for the fixes listed above. You can skip it: alerts work without it.