fshy

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
email?placeholder, not evidence; card unknown, phone unknown
Binding limit
write-gatedcreating or managing a sandbox requires the Container Apps SandboxGroup Data Owner role assignment
Evidence
documented2 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
Free tierno 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
Pricenone 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
Identityemail (placeholder) not published
Egressnot stated
Per-object capnot stated
Retentionnot stated
Interfaceunknown
Reliabilityno reliability event recorded
Evidence notedocumented 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
Evidence 2
datesourcewhat it proved
2026-10-02learn.microsoft.com/en-us/azure/container-apps/sandboxes-ovenot published
2026-10-22learn.microsoft.com/en-us/azure/container-apps/sandboxes-ove'Sandboxes are provisioned from prewarmed pools for near-instant availability' and 'You pay no CPU or memory fees when sandboxes are stopped' and 'Suspend and resume: Snapshot full state including memory and disk, and resume later with sub-second restore times', quoted
More fields 13
{
 "keep_rate": 1.0,
 "keep_rate_basis": null,
 "billing_model": "unclassified",
 "shape": null,
 "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"
 },
 "persistent_storage": null,
 "network_out": null,
 "price_note": null,
 "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