This is the first in the series of utilizing the Cloud Adoption Framework to move to the cloud. These are the actual slides I use when I work with customers on planning their migration.
Typically, the process starts with an assessment of their on-premise infrastructure using one of many tools to get an inventory of their datacenter as well as the services/software running, ports used, and connections between servers. This allows us to determine and build “move groups” so that we do not impact services during the migration. This subject is covered in more depth in the series. Because this process takes about two weeks to complete, that is the opportune time to complete the cloud adoption framework series of decks.
The download link is to the github repository and will contain the latest versions of the slides.
The Microsoft Cloud Adoption Framework for Azure guides customers through their cloud journey, to use and adopt cloud services with confidence and in control. In this episode, Scott Bockheim explores the guidance and documentation of the framework with Lara Rubbelke to provide an overview of all the components and elements included.
The Microsoft Cloud Adoption Framework for Azure guides customers through their cloud journey, to use and adopt cloud services with confidence and in control.
The most common comments I hear regarding the cloud adoption framework is:
it is too massive (hundreds of pages)
too complex
and the steps are confusing
In the next few posts, I will share the decks and corresponding collateral that I use with customers when I am hired to help them migrate to the cloud. The decks are a mix of information from the cloud adoption framework (CAF), my own process to supplement the CAF, and feedback from customers I have migrated. I have worked on countless projects over the years and I have refined my process and distilled it down to what I feel is useful for customers and not overwhelming.
Full disclosure, I do follow the Azure CAF instead of the AWS CAF because Microsoft has invested a considerable amount of effort into building theirs while AWS is lacking IMO. GCP has one too if you would like to check it out. I do take some bits from AWS and I include links to GCP and AWS tools if you are adopting one of them for your cloud. But overall Microsoft has done a better job IMO and provides the most comprehensive CAF, and even goes out of their way to agnostic in lots of areas of their documentation.
