M365Con 2027 – бесплатная онлайн-конференция · 11–22 Jan 2027 · 120 sessions m365con.net

Workload identity federation

Concept

Workload identity federation lets workloads outside Azure, such as GitHub Actions pipelines, exchange a trusted external token for a short-lived Microsoft Entra access token without storing secrets.

✦ CONCEPTWorkload identityfederationM365.FM
Title graphic: Workload identity federation (Concept)

Связи

Workload identity federation относится к более широкой теме Microsoft Entra Workload ID.

Description

Workload identity federation, also called WIF or federated identity credentials, is a concept within Microsoft Entra Workload ID. It allows a workload that runs outside Azure, for example a GitHub Actions pipeline, to exchange a token issued by a trusted external identity provider for a short-lived Microsoft Entra access token. The central point is that no secret has to be stored: the workload does not hold a password, client secret or certificate that could leak, expire unnoticed or be copied.

The approach addresses a common problem with application identities. Pipelines, services and bots need to authenticate to resources protected by Microsoft Entra, and traditionally this meant creating a credential and keeping it somewhere, such as in a pipeline variable or a configuration file. Every stored credential has to be rotated, protected and eventually retired. With federation, trust is established once between the Microsoft Entra application and the external token issuer. After that, the external token serves as proof of identity, and Microsoft Entra returns a short-lived access token that the workload then uses to reach the target resource.

The M365.FM episodes mention federated identity credentials in several settings. In "Entra Workload Identities - Simply Explained", workload identity federation appears in a list of measures for securing workload identities in Microsoft Azure. The episode treats workload identities as needing governance in the same way as privileged user accounts, and it names least privilege access, Conditional Access for workload identities, certificate-based authentication, Microsoft Entra ID Protection, logging, monitoring, lifecycle management and ownership alongside federation. The host argues that every workload identity should have a clearly assigned owner, minimal permissions, continuous monitoring and regular security reviews, and that neglected application identities often leave unused service principals behind.

In "Copilot in Microsoft Entra ID - Simply Explained", Federated Identity Credentials (FIC) are listed among the key benefits discussed. The episode says they improve security by eliminating the need for persisted secrets and certificates for bot registration. The same list also mentions IT control, which lets administrators block risky agents from operating, and customer managed encryption keys.

The episode "MCP Custom Connector in Copilot Studio: The Complete Integration Guide" gives a practical recommendation. Among the lessons from organizations that integrated MCP with Copilot Studio, it advises using federated identity credentials for passwordless Power Platform authentication. This sits next to other points from the episode, such as bridging MCP to Copilot Studio through Power Platform custom connectors and letting user identity flow through the entire stack from the OAuth token to the business logic.

Typical decisions around workload identity federation concern where a secret can be removed altogether and how the trust relationship is scoped. Because federation replaces a stored credential with a trust relationship, the surrounding controls matter more: the federated application still needs an owner, narrowly scoped permissions and monitoring, as the governance discussion in the first episode emphasizes. Federation is therefore one part of a wider approach to workload identity hygiene rather than a replacement for it.

Workload identity federation sits under the broader topic Microsoft Entra Workload ID, which covers identities for applications, services and automated processes rather than for people. Within that area, federation is the option for workloads that already have a trusted identity elsewhere and need to obtain access to Microsoft Entra-protected resources without introducing a new secret to manage. Microsoft's documentation page on workload identity federation describes the mechanism in more detail.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept
Also known asFederated identity credentials, WIF
DocumentationWorkload identity federation – Microsoft Learn learn.microsoft.com

Связанные темы вкратце

Темы, связанные с Workload identity federation, с кратким пояснением:

Workload identity federation: все связи, сгруппированные по типу связи:

Broader topic

Workload identity federation — более широкие темы:

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: