# Third-party integration

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

A third-party integration is an outside application connected to a company's cloud or software-as-a-service account by a token, key or role. Its access lasts as long as the grant does, whatever happens in the vendor's own systems. The ledger records incidents that began in an integration as third-party access, not as the customer's own compromise.

## An example, sourced

Microsoft's Entra documentation covers managing application permissions, including the consent granted to applications in a tenant (read 16 Nov 2026).

## Why it matters here

On Cloud Security Breaches the term appears in the rubric and on the platform pages; the example above was read on 16 Nov 2026 from the page under Sources.

## Related pages

- [Form 8-K Item 1.05: meaning and an example](/glossary/form-8-k-item-1-05/)
- [Consent order: meaning and an example](/glossary/consent-order/)
- [Provider post-mortem: meaning and an example](/glossary/provider-post-mortem/)
- [All of them](/glossary/)

## Sources

- https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-application-permissions (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/glossary/third-party-integration/
