Internal Developer Platform  ·  View 09 of 21  ·  Structure

Integration Surface

One API behind every surface, and the four systems the platform actually drives.

Editable source SVG draw.io All views
Consumers Developer Portal Platform CLI Team Pipelines Risk and Audit Platform API Platform API versioned · deprecated on notice Platform Event Bus Service Bus Webhook Receiver Git and cloud events Systems the platform drives GitHub Enterprise Azure Resource Manager AKS Fleet Microsoft Entra ID REST REST OIDC evidence repos provision apply tokens Internal Developer Platform — Integration Surface Application we own External / third party Interface / broker Queue / topic Security / platform synchronous batch two-way Every human surface is a client of the same API. Key Vault, Azure Monitor and Cost Management are omitted: the platform grants and exports to them rather than driving them. v 1.0 · owner Platform Architecture · date 2026-09

Decisions

  • The API is primary; the portal and the CLI are clients of it. A capability reachable only through the portal cannot be scripted, audited or replaced, so it is defined as a defect (ADR-12).
  • The platform API is versioned with a published deprecation window, because its consumers include 140 teams' pipelines.
  • Git is the only integration the platform both drives and is driven by, which is a direct consequence of intent living in the repository (ADR-01).

Assumptions

  • Team pipelines authenticate by OIDC federation with no static credential (ADR-15).
  • Audit evidence is exported rather than queried live by the risk function.

Omitted

  • Key Vault, Azure Monitor and Cost Management: the platform grants to or exports from them rather than driving them.
  • Two edge labels on this view sit close enough to touch. That is the hub layout's fan geometry, not a routing error; the alternative was a shorter label that said less.