Service principal

The Lifecycle

The diagram summarizes the observed transition rows; declared edges without an observed writer remain outside the operational graph.

Transitions Explained

Principal status governs machine callers independently of human membership. Suspension takes effect through the receiving service’s registry-aware cache; it is not a cloud-role revocation.

Deployment preserves a deliberate suspension. The state model makes no claim of a supported deletion path.

What Cannot Happen

Deployment inserts missing principals but never resumes a suspended existing principal.

An unknown principal is returned as not found and the refused change is audited.

Concurrency and Timing

Status changes lock the principal row and append history in the same transaction. Repeating the existing status writes no change event. The observed administration API offers no principal-deletion operation.