Plan your cloud migration with Microsoft Cloud Adoption Framework and Azure DevOps
May 17, 2020 |
Microsoft Cloud Adoption Framework (CAF) for Azure is a detailed guidance of patterns and practices to create and implement business and technology strategies necessary for organisations to move to the cloud. According to Microsoft, this guidance is adopted from various customers learnings from moving to cloud and Microsoft itself.
In this post, we will see CAF’s starter template in Azure DevOps Demo generator helps customersPlan
their cloud journey.
The Cloud Adoption Frameworkdocumentation is neatly aligned to various phases (Strategy, Plan, Ready, Adopt, Govern and Organise) of customer’s journey to the cloud so that it can easily be understood by cloud architects, IT professional and even business decision makers.
Azure DevOps Demo Generator Starter template for CAF
CAF has a custom built template usingAzure DevOps Demo generator. This custom template lets you easily create the backlog which is based on the standardised guidance in the Cloud Adoption Framework. Lets see how to use the template.
So go in to Azure DevOps demo generator and sign in.
In the next step, select the organization and enter a name for the team project. The project is created automatically. Next selectChoose template
In the screen that pops up, go toAzure Community
tab and selectCloud Adoption Plan
and clickSelect Template
Click onCreate Project
Ensure the user running this wizard has at least has
Create project
permission. If not, go toOrganization Settings
and setCreate new projects
toAllow
If everything went without issues, you will see the status as below.
Click onNavigate to project
and you will be taken to the new project in the organisation you selected.
Go into theBacklog
andEpics
view and you will see set of epics. These work items help customers to plan and manage the work required to complete the adoption lifecycle.
According to docs, these work items heavily focus only on migration efforts. Tasks related to governance, innovation or operations need to be planned and populated manually.
Drill down on Epics and you will seeFeatures
,User Stories
andTasks
. These are ordered so that customers are enabled to think and capture all the necessary context/prerequisites needed for essential cloud adoption. Often times, we have seen customers realise pretty late (usually after they receive their first month bill in my experience) that cloud is not run as traditional on-premises by handing over to separate operations team.
So Microsoft CAF starter template for Azure DevOps, ensures customer do not miss key pieces and capture all that is needed to migrate to cloud.
Take first epic for example. The epic attempts to capture all the prerequisites needed from the customer. For any cloud adoption, it is necessary to have a right strategy and motivation (I am moving to cloud to save costs (or to innovate/reduce complexity etc)). TheUser Stories
aim to capture thesemotivations,business outcomes from key stakeholders. Next it is essential to capture business justification from the key stakeholders on why part of the cloud migration. Discussing and agreeing on the cloud migration outcome is essential so that there are no surprising outcomes in the end and ROI (Return on Investment) is captured in the business justification.
Each workitem has description, links to additional documentation and tags applied for easier querying.
Accessing documentation from Azure Portal
BTW, there is an even easier way to access this guidance. Go toAzure Portal
and thenQuickstart Center
.
Then click on relevant links at the bottom.
Conclusion
There you have it, just a quick summary of using starter template of CAF. You saw how you can start to capture all the key bits from various stakeholders in your customer’s cloud journey to Azure and plan better using Azure DevOps backlog.
If you are an organisation evaluating your cloud options to Azure, or a consultant helping your customer to migrate to cloud, Microsoft’s Cloud Adoption Framework guidance provides a great set of best practices and patterns. CAF provides you useful guidance on strategising, planning and so on until customer is able to manage cloud efficiently on their own. Go check it out.
Like this post? Have comments? Let me know.
- Use a single repository for multiple wikis in Azure DevOps
- Helm 3 - CI/CD with Azure DevOps using Azure Container Registry (ACR) and Azure Kubernetes Service (AKS)
- Deploying TIBCO Rendezvous on RedHat Enterprise Linux using Azure DevOps
- Troubleshooting Azure DevOps deployment stuck at 'Queued' status
- Azure DevOps workitems don't show frequently used users? Here's how to fix it.

Utkarsh Shigihalli
Utkarsh is passionate about software development and has experience in the areas of Azure, Azure DevOps, C# and TypeScript. Over the years he has worked as an architect, independent consultant and manager in many countries including India, United States, Netherlands and United Kingdom. He is a Microsoft MVP and has developed numerous extensions for Visual Studio, Visual Studio Code and Azure DevOps.
Do you like our posts? Subscribe to our newsletter!
- acr
- aks
- arm
- agile
- appveyor
- artifacts
- azure
- azure container registry
- azure devops
- azure hybrid benefit
- azure key vault
- azure kubernetes service
- azure oms
- azure pipelines
- azure static webapps
- azureappservice
- azureautomation
- azuredevtestlabs
- boards
- bug2mail
- build
- buildpipeline
- cli
- chatops
- chef
- chrome
- cloud adoption framework
- conftest
- continuous delivery
- continuousmonitoring
- dependency visualizer
- devops
- devops book
- devsecops
- exception
- extensions
- git
- githooks
- github
- governance
- helm
- iac
- jekyll
- keyvault
- kubernetes
- licensing
- machine groups
- msbuild
- netlify
- oms
- perf
- personal
- pester
- pipelines
- powershell
- releasegates
- releasemanagement
- servicenow
- sitecore
- sonarqube
- specflow
- tfs
- tfs15
- tfs2015
- teambuild
- teamfoundationserver
- tools
- training
- vscode
- vsts
- visualstudio
- wpf
- wiki
- winrm
- windows mobile
- xaml
- acr
- actions
- angularjs
- azure
- bash
- build
- burndown
- container
- cosmos
- csharp
- dependabot
- devops
- dotnet
- dotnetcore
- github
- helm
- ie
- mvc
- packages
- productivity
- quartz.net
- registry
- shell
- synology
- windows
- workitem
- wsl
- wsl2