Internal Developer Platform  ·  View 21 of 21  ·  Assurance

Identity and Access

From a person's group claim to a workload's short-lived token, with no static credential anywhere.

Editable source SVG draw.io All views
Engineer Microsoft Entra ID Platform API Catalog Infra Reconciler Key Vault Workload Pod 1. sign in · device policy 2. token with group claims 3. provision a database 4. who owns this component? 5. owning group 6. group claim vs owner 7. not your component 8. reconcile declared intent 9. federated credential 10. create path · grant identity 11. workload identity token 12. short-lived token 13. read own secret 14. secret value 15. audit event Identity and Access — From a Person to a Workload Credential Message 7 is the whole access model: entitlement is derived from catalog ownership, so there is no separate access list to fall out of date when a team reorganises. v 1.0 · owner Platform Architecture · date 2026-09

The message that matters

  • Message 7 — "not your component" — is the whole access model: entitlement is derived from catalog ownership, so there is no separate access list to fall out of date when a team reorganises (ADR-10).
  • Workload identity is federated to Entra with no secret to rotate, distribute or leak (ADR-15).
  • Every privileged action writes an audit event as a matter of course, not as an option a deployment can disable.

Consequences

  • A wrong owner in the catalog is now an access-control fault, not a metadata fault — which is why an empty owning group is treated as an incident.
  • Bulk re-attribution on a reorganisation moves entitlements with it, and the history of who owned what is retained.

Assumptions

  • Entra groups are already the organisation's team structure, and are kept current by joiner-mover-leaver processes outside this platform (stated assumption).
  • Token lifetimes short enough that revocation through group membership is effective within the hour.