Prepare for your first infrastructure conversation.
Bring the facts that make a cloud proposal specific to your business.
Read the guideNotes for the
next deployment.
Practical reading for the decisions between an application requirement and a working environment.
Write an infrastructure change plan people can use.
Connect impact, approval, validation, communication, and rollback.
Read the guideReview cloud cost through the workload.
Connect capacity, storage growth, management scope, and migration effort.
Read the guideAsk better questions about cloud network boundaries.
Define permitted traffic and administrative access before drawing network zones.
Read the guideMap application dependencies before a migration.
Find the connections that a server inventory leaves out.
Read the guideStorage, snapshots, and backups serve different jobs.
Ask the questions that connect a data copy to an actual recovery need.
Read the guideSet recovery objectives your team can test.
Turn downtime and data-loss tolerance into a practical recovery exercise.
Read the guideManaged hosting starts with a responsibility map.
Set clear ownership for patches, backups, changes, applications, and escalation.
Read the guideWhat belongs in a virtual data center plan?
Connect the resource inventory to networks, access boundaries, and operating responsibilities.
Read the guideRight-size a cloud workload before you move it.
Build a useful capacity baseline from demand, dependencies, and headroom.
Read the guide