Mail Flow Rollback
Restore inbound/outbound mail during connector failures, transport rule issues, or throttling.
Includes testing, monitoring, and escalation criteria.
Rollback Runbooks: Restore service in 5–30 minutes, prevent escalation
Safe, step‑by‑step procedures to restore service fast and prevent extended downtime. Each runbook includes quick checks, rollback actions, validation steps, and business impact assessment. Pre-tested for P1 incidents.
Runbooks
CA Policy Rollback
Safely disable or modify Conditional Access policy during authentication outages.
Emergency access procedures and policy adjustment techniques.
Hybrid Configuration Rollback
Restore on-premises to cloud migration and coexistence during hybrid failures.
Free-busy, migration, and HCW recovery procedures.
When to Use
Active incident. Recent change caused impact. Need fast, safe restore.
Common Scenarios
- Mail flow stopped after rule, connector, or domain changes
- Users locked out by Conditional Access policy
- Mailbox migration stuck or failed; batch restart needed
- Free‑busy or hybrid sync broken after HCW or namespace changes
- Throttling issues causing delays; adjust policy
- Revert to known‑good after unauthorized or risky changes
What’s Inside
Each runbook includes:
- Pre‑reqs: Permissions, tools, and quick validation
- Decision trees: Flowcharts to pick the right path
- Rollback steps: PowerShell and portal actions
- Validation: Confirm restore and success criteria
- Escalation: When to involve Microsoft or senior engineers
- Post‑incident: Docs and lessons learned
Before You Start
⚠️ Important: Document the current state before you change anything. Take screenshots, export configs, and note exact times. This creates an audit trail and enables forward‑fixes if rollback causes unexpected issues.
For diagnostic procedures before rollback, see our diagnostics guides. For preventive guidance, review our Exchange Online services covering change-control best practices.
Related Guides
Diagnostic procedures before running runbooks.