Deployment Gates and Rollback

MS Learn path: Design and implement a release strategy — module 4.

Overview

Covers the control mechanisms that make releases safe: deployment gates and approvals that pause releases until conditions are met, and rollback strategies that bring a bad release back to a known-good state.

Units

• Deployment gates & approvals
• Pre-deployment vs post-deployment gates
• Monitor/query-based gates
• Rollback strategies & forward fix

Concepts introduced

• Deployment gates
• Rollback strategy
• Release pipeline stage config
• Feature flags as kill switch

Key terms & commands

• Approval gate — human sign-off.
• Azure Monitor gate — metric/log query must pass.
• Pre/post-deployment gates per stage.
• Rollback — flip traffic (blue/green), stop canary, or kill-switch the flag.

Hands-on

⚠ verify — add an exercise adding an approval + monitor gate and a rollback.

Exam focus

• Gates: pre- vs post-deployment, approval/Monitor/work-item types, retries & timeouts.
• Rollback: match mechanism to pattern; feature-flag kill switch = fastest, blue/green = instant.
• Stateful/schema changes may need forward-fix over rollback.

Related

deployment-gate · rollback-strategy · release-definition · feature-flags · Path MOC