Home / Microsoft
Azure Container Apps Sandboxes
learn.microsoft.com/en-us/azure/container-apps/sandboxes-oveCloud VMcompute/azure-container-apps-sandboxesJSONcomparereport an errorprovider JSON
- Free allowance
- No sandbox-specific free allowance is published; sandbox compute bills through the same per-second Container Apps meters, whose first 180,000 vCPU-seconds and 360,000 GiB-seconds a month are free
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- cardcard required, phone required
- Binding limit
- write-gatedcreating or managing a sandbox requires the Container Apps SandboxGroup Data Owner role assignment
- Evidence
- documented4 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-03checked 2026-11-02 (live); stale on 2026-12-03
| Free tier | no sandbox-specific free allowance is published; sandbox compute bills through the same per-second Container Apps meters, whose first 180,000 vCPU-seconds and 360,000 GiB-seconds a month are free unit seconds; metered on wall-clock |
|---|
| Price | none stated |
|---|
| Limits | - request-rate sandbox compute bills per second through the Container Apps meters source
- retention-clamped a stopped sandbox incurs no CPU or memory fee; a snapshot preserves memory and disk source
- write-gated (binding) creating or managing a sandbox requires the Container Apps SandboxGroup Data Owner role assignment source
not stated |
|---|
| Identity | card A card and a phone number, because a sandbox bills through an Azure subscription. Azure's signup FAQ: 'All you need is a phone number, a credit card or a debit card (non-prepaid), and a Microsoft account or a GitHub account.' A second gate on the card: 'Only credit cards are accepted in Hong Kong and Brazil.' On top of the subscription, creating a sandbox needs a role assignment: 'To manage and create sandboxes, you need the Azure role Container Apps SandboxGroup Data Owner.' Country limit, quoted: 'If your country is not listed, the offer is not available in your region.' |
|---|
| Egress | not stated |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | unknown |
|---|
| Reliability | no reliability event recorded |
|---|
| Evidence note | documented the sandboxes overview was read on 2026-10-22. It establishes the lifecycle and the stop-billing behaviour and does not publish a free allowance, so the requirement below is the Container Apps consumption allowance the same vendor prices on its pricing page, not a sandbox-specific grant |
|---|
| Parsed numbers | |
|---|
Evidence 4
More fields 8
| keep rate | 1.0 |
|---|
| billing model | unclassified |
|---|
| session cap | {"wall_clock_min": null,"idle_reap_s": null,"restart_required": false,"note": "no automatic reap is described: you manage create, suspend, resume and delete, and a stopped sandbox is free of compute charges"} |
|---|
| free tier kind | allowance |
|---|
| granularity | {"min_billed_s": 0,"rounding_s": null} |
|---|
| burst x | 1.0 |
|---|
| ps | {"gib": null,"price": "volumes are a separate resource","durability": "snapshot of memory and disk; persistent volumes","on_stop": true,"on_destroy": false,"retention": "until the sandbox is deleted"} |
|---|
| net | {"out": true,"in": true,"ports": "networking policies govern egress and ingress","static_ip": null,"ipv6": null,"allowance": null} |
|---|
Unknown values 10
- chaining: a source was read and is silent on this field
- egress metered: egress metering was not published
- egress terms: a source was read and is silent on this field
- interface: the access interface was not established
- limits note: a source was read and is silent on this field
- per object cap stated: a source was read and is silent on this field
- reliability note: nothing of this kind was observed
- retention notes: the field may be stated in a source that was not read
- retention stated: a source was read and is silent on this field
- tooling: a source was read and is silent on this field