Enterprise Identity & Access Management Platform  ·  View 01 of 27  ·  Context and scope

System Context

Who this platform issues identity to, what it governs access to, and what it deliberately never holds.

Editable source SVG draw.io All views
External identities
External identities
Partner workforce
34 partner tenants
Partner workforce...
Customers
1.2M CIAM
Customers...
Human identities
Human identities
Employees
45,000
Employees...
Contractors
8,000 · sponsored
Contractors...
Privileged administrators
190 role holders
Privileged administrators...
Break-glass accounts
2 · standing
Break-glass accounts...
Systems of record
Systems of record
Workday HCM
Workday HCM
On-premises AD DS
On-premises AD DS
SaaS applications
900 apps
SaaS applications...
ServiceNow
ServiceNow
Enterprise Identity & Access Platform
Zero-trust · multi-tenant · Azure
Enterprise Identity & Access Platform...
Workloads and resources under control
Workloads and resources under control
Azure resource estate
22 subscriptions
Azure resource estate...
AKS & app workloads
3,400 workload IDs
AKS & app workloads...
CI/CD pipelines
GitHub · Azure DevOps
CI/CD pipelines...
Security operations
Sentinel · Defender
Security operations...
SSO + passwordless
SSO + passwordless
time-bound package
time-bound package
JIT elevation
JIT elevation
emergency only
emergency only
B2B cross-tenant
B2B cross-tenant
sign-up / sign-in
sign-up / sign-in
worker records, hourly
worker records, hourly
hybrid sync
hybrid sync
SSO + SCIM
SSO + SCIM
approvals, tickets
approvals, tickets
Azure RBAC
Azure RBAC
workload identity
workload identity
OIDC federation
OIDC federation
identity signals
identity signals
Enterprise Identity & Access Platform — System Context
Enterprise Identity & Access Platform — System Context
External / third party
External / third party
Person or role
Person or role
Risk / gap
Risk / gap
synchronous
synchronous
batch
batch
two-way
two-way
event / async
event / async
Every arrow is an identity relationship. Business data flows between these systems are deliberately absent: this platform decides who may move that data, it never carries it.
Every arrow is an identity relationship. Business data flows between these systems are deliberately absent: this platform decides who may move that data, it never carries it.
v 1.0 · owner Data & AI Global Practice · date 2026-08
v 1.0 · owner Data & AI Global Practice · date 2026-08
Text is not SVG - cannot display

Decisions

  • Microsoft Entra ID is the single identity authority. Every other authentication surface in the estate is a relying party, and any system that keeps its own username and password list is a migration item rather than an integration.
  • The platform issues and governs identity; it never carries business data. That separation is what lets it be a shared tenant-wide service without becoming a data-protection problem of its own.
  • Break-glass accounts are drawn in red on the first page rather than hidden in an appendix. Two permanently privileged accounts are an accepted, monitored exception to the zero-standing-access rule, not an oversight.

Scale assumed

  • 45,000 employees, 8,000 contractors, 6,500 B2B guests, 1.2M customer identities, 3,400 workload identities across 900 applications and 22 subscriptions.
  • 2.6M sign-ins per day, peaking near 420 per second at 09:00 CET. Identity is a control-plane service: this volume shapes logging cost far more than it shapes latency.
  • Every figure here is a stated exercise assumption. They drive log retention cost, review campaign size and the group model, so they are the first thing to confirm with the client.

Out of scope

  • Endpoint management and device compliance policy itself. The platform consumes Intune's compliance signal (view 12) but does not define it.
  • Physical access, HR process design, and the application-level roles each product team defines inside its own domain.
  • Customer consent and privacy preference management, which belongs with the customer data platform rather than with the identity provider.