dev
Isolated workspace. Main merge deploys automatically; smoke tests accept the change.
No prod secrets or data; dedicated nonprod resources and deployment identity.
Independent concept for discussion.
No live execution or connected systems.
Dev proves the change runs. Staging proves the release behaves. Production admits only an approved, verified artifact. Environment status and digests below read directly from the shared release.
Isolated workspace. Main merge deploys automatically; smoke tests accept the change.
No prod secrets or data; dedicated nonprod resources and deployment identity.
Production-like configuration, test data. Integration, e2e and smoke evidence required.
Separate config, secrets and identity. Match production behavior, not production data.
Restricted identity and data. Named approval, change window and health verification.
Jordan · synthetic release approver. No agent production writes; least privilege.
An environment is a security and delivery boundary: its identity, data, configuration and approval policy. An Azure App Service slot is another deployment within an app. Slots can share an App Service plan and downstream data; they do not automatically provide full isolation.
A production app’s staging slot can validate a version before a controlled swap. Configure slot-specific settings and data access, understand swap behavior and validate recovery. A slot does not replace an isolated Dev environment or a separately governed Staging system.
Microsoft: deployment slots ↗Same digest in each deployed environment. Last-known-good Production remains separate until promotion.
ENG-104 opened. Synthetic release; no live execution.