Skip to main content

Tools, templates and assessments for the Adopt phase of CAF (Microsoft Cloud Adoption Framework)

Microsoft is offering an excellent framework to support cloud migration and adoption process –Microsoft Cloud Adoption Framework (CAF) 

The framework defined an iterative process with the following phases:

  1. Define Strategy
  2. Plan
  3. Ready
  4. Adopt
  5. Govern
  6. Manage

For each of them, Cloud Adoption Framework (CAF) provides us a list of templates, tools, and assessment mechanisms that can help us to improve the adoption and migration process. Let's take a look at the ones for Adopt.   

Strategic Migration Assessment and Readiness Tool

Location: https://docs.microsoft.com/ro-ro/assessments/?mode=pre-assessment&session=1e9bea1e-6e2a-46f0-bf60-897e0424b5e2 

When you want to adopt cloud you need to be aware of all the dimensions that are impacted by the migration. This tool allows you to do an assessment of where you are in under 10 minutes and identify the dimensions that need to be improved to be able to achieve the adoption in a SMART way.

The covered dimensions are:

  1. Business strategy
  2. Partner support
  3. Discovery & Assessment
  4. Business case
  5. Migration Plan
  6. Technical Skilling
  7. Landing Zone
  8. Migration Execution
  9. Governance
  10. Management
For each dimension, you get a score and where needed a list of resources that can be used to do the improvements. 

Azure migration guide overview

Location: https://ms.portal.azure.com/#blade/Microsoft_Azure_Resources/QuickstartPlaybookBlade/guideId/migration-setup

This guide is used during the Adopt phase to ensure that we cover all the steps from the process. For each step, we have the full list of steps, tools, and best practices that need to be taken into account, covering:

  • Assess
  • Deploy
  • Cost control
  • Release

Azure innovation guide overview

Location: https://ms.portal.azure.com/#blade/Microsoft_Azure_Resources/QuickstartPlaybookBlade/guideId/innovation-setup

The last tool that we have available for the Adopt phase is Azure Innovation Guide Overview. The guide supports us to improve the way how we drive adoption, build solutions, and engage with customers. 

A list of services and tools are provided that helps us to:

  • Manage customer feedback: Set up tools and processes to manage the build-measure-learn feedback loop by using GitHub and Azure DevOps.
  • Democratize data: Data alone might be enough to drive innovative solutions to your customers. Deploy common data options in Azure.
  • Engage via applications: Some innovation requires an engaging experience. Use cloud-native application platforms to create engaging experiences.
  • Empower adoption: Invention is great, but a plan to reduce friction is needed to empower and scale adoption. Deploy a foundation for CI/CD, DevOps, and other adoption enablers.
  • Interact through devices: Create ambient experiences to bring your applications and data closer to the customers' point of need. IoT, mixed reality, and mobile experiences are easier with Azure.
  • Predict and influence: Find patterns in data. Put those patterns to work to predict and influence customer behaviors by using Azure-based predictive analytics tools.


Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...