# Azurescape: cross-account container takeover in a container service: the technique as Palo Alto Networks Unit 42 published it

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Palo Alto Networks Unit 42 published "Azurescape: cross-account container takeover in a container service" on 9 Sep 2021. The ledger files it under cross-tenant access. It is a disclosed research technique, not an incident. The source is the publisher's own write-up.

- **Published:** 9 Sep 2021
- **Publisher:** Palo Alto Networks Unit 42
- **Access path:** [Cross-tenant access](/access-paths/cross-tenant/)
- **Source:** [the publisher's write-up](https://unit42.paloaltonetworks.com/azure-container-instances/)

Unit 42 reported a chain that let a container escape its sandbox in Azure Container Instances and reach other customers' containers on the same platform. The post says Microsoft patched the service after the report and that Unit 42 has no knowledge of exploitation in the wild.

## Related pages

- [OMIGOD: unauthenticated remote code execution in a VM mana](/techniques/omigod/)
- [ChaosDB: Cosmos DB keys obtained from a notebook feature](/techniques/chaosdb/)
- [AutoWarp: another customer's tokens reachable from an auto](/techniques/autowarp/)

## Sources

- Azurescape: cross-account container takeover in a container service: https://unit42.paloaltonetworks.com/azure-container-instances/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/techniques/azurescape/
