# Cross-tenant access: 3 incidents in the ledger

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

Cross-tenant access is a flaw in a provider's service, or a setting in a customer's application or account, that let one customer's tenant reach resources belonging to another customer, so the boundary the provider draws around each customer did not hold for that request or token.

## How it works

A tenant is the boundary a provider draws around one customer. Microsoft's documentation says its identity service organizes users and apps into tenants, and that a multitenant app can be used by accounts from any directory, so the app has to decide whose sign-ins it accepts. Providers run shared infrastructure behind these boundaries, so a flaw in the provider's own service can cross them without any mistake by the customer.

The ledger records this path only where the provider or the customer's own statement describes the crossing. Typical cases are an application that accepts a valid token from the wrong tenant, a provider-side service that handled another customer's credentials, or a setting that allowed data to be copied between tenants. Fixes come from the provider when the flaw is theirs and from the app owner when the check is theirs.

## The incidents

| Disclosed | Organization | Cloud | How access was gained |
| --- | --- | --- | --- |
| 2023-07-12 | [JumpCloud](/incidents/jumpcloud-orchestration-2023/) | JumpCloud | The company stated it traced anomalous activity on an internal orchestration system to a spear-phishing campaign on June 22, which gave unauthorized access to a specific area of its infrastructure. It later found unusual activity in the commands framework for a small set of customers, and stated the attack vector was data injection into its commands framework. |
| 2023-07-11 | [Microsoft](/incidents/microsoft-storm-0558-2023/) | Microsoft 365 | Microsoft stated the actor used an acquired Microsoft account consumer signing key to forge tokens, and exploited a token validation issue so that enterprise mail accepted them. The post-mortem says the most probable mechanism for the key acquisition was a compromised engineer corporate account with access to a debugging environment holding a crash dump that contained the key. |
| 2021-08-27 | [Microsoft (Azure Cosmos DB)](/incidents/azure-cosmosdb-chaosdb-2021/) | Microsoft Azure | The post-mortem says a vulnerability in the Azure Cosmos DB Jupyter Notebook feature could allow a user to gain access to another customer's resources by using the account's primary read-write key. |

## The kind of control that addresses it

validate the tenant and issuer on every token an application accepts, and turn off cross-tenant features that are not in use

## Related pages

- [Third-party access: cloud breaches by access path](/access-paths/third-party-access/)
- [Exposed network services and request paths: cloud breaches](/access-paths/exposed-network-service/)
- [Retained access after departure or change: cloud breaches ](/access-paths/retained-access/)

## Sources

- Microsoft Learn: single and multitenant apps in Microsoft Entra ID: https://learn.microsoft.com/en-us/entra/identity-platform/single-and-multi-tenant-apps (read 16 Nov 2026)
- AWS IAM User Guide: the confused deputy problem: https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/access-paths/cross-tenant/
