Workload identity federation
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
A way for software running outside a cloud, or in another system, to trade a token from its own identity provider for short-lived cloud credentials. The cloud trusts the provider, so the workload holds no stored key. Google Cloud, Microsoft Entra and AWS each offer a version.
An example, sourced
Microsoft documents workload identity federation as configuring a user-assigned managed identity or app registration in Microsoft Entra ID to trust tokens from an external identity provider, such as GitHub or Google. Once the trust relationship exists, the external software workload exchanges trusted tokens from that provider for access tokens from the Microsoft identity platform. Microsoft lists GitHub Actions and Kubernetes workloads as scenarios.
Why it matters here
Federation is the usual way to remove keys from agents that run outside the cloud they call. A reviewer should check which external subject is trusted, because a broad trust lets any workload from that provider in. Ask also how long the exchanged credentials last.
Related pages
Sources
Last reviewed 16 Nov 2026.