Running BAU across onshore and offshore teams
One queue, written handovers, tested runbooks and a clear map of who owns what between service providers.
Guides and short notes written from real migrations, upgrades and clean-ups.
One queue, written handovers, tested runbooks and a clear map of who owns what between service providers.
Five habits that keep runbooks and designs short, current and useful.
Deadlines by severity, patch rings, written exceptions and saved evidence: the parts of a patching process that satisfy an auditor.
How an on-premises background maps to the AZ-305 exam, and how to study the design decisions.