Internal Developer Platform · View 01 of 21 · Context and scope
Decisions
- The platform is a tenant of the landing zone, not its owner: it provisions inside subscriptions handed to it, under an Azure Policy floor it does not set.
- GitHub is the only bidirectional edge on the diagram, because the team's repository holds intent and the platform must both write to it and read from it.
- Entra ID is the sole source of identity and entitlement; the platform maintains no user or access list of its own.
Assumptions
- 900 engineers, 140 teams, 1,400 deployable components, 5,200 deploys per week (stated assumptions throughout the set).
- An existing landing zone with management groups and a subscription vending process already in place.
- A current baseline of 19 working days from request to first production deploy, which is the number the platform is built to destroy.
Out of scope
- Product code, product architecture and product on-call. The platform paves the road; teams drive on it.
- Network topology, subscription vending and the organisation's policy floor — the landing zone owns all three.
- Being an approval workflow. A request the platform accepts and then queues for a human has already failed.
