Skip to main content

Tools, templates and assessments for the Ready 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 Ready. 

Azure Setup Guide

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

The first thing you need to do when you start a project is to configure the environments. Ensuring that you have the right governance, security, monitoring in place. 

The guide is providing best practice, with direct links to Azure Portal from where you can configure the recommendations. There are 5 different areas that are covered:

  1. Organize resources
  2. Manage access
  3. Manage costs and billing
  4. Plan governance, security and compliance
  5. Establish monitoring and reporting
Plus a section that provides different resources from where you can find the current status of your services, any updates related to Azure that are available and news related to Azure services and features. 

Naming and Tagging Conventions Tracking Template

The main purpose of this document is to help us to define the conventions that we shall follow at the moment in time when we define tags or create new instances of Azure services. You have the freedom to change the conversions, but keep in mind to take into account all the dimensions that are covered inside the template. In this way to will be able to manage more easily your cloud resources. 

Azure Landing Zone

Complex cloud solutions require more than one Azure Subscription. Concerns like security, networking, scaling are forcing organizations to use multiple subscriptions. Managing them requires extra effort. For this situation, Azure Landing Zone is offering us design areas that cover topics like Identity, Networking topology, Connectivity, Resource organization, enrollment, governance, BCDR, deployment and operation. 
For each design area, we have a list of principles that we need to follow and deployment instructions that can build our initial blueprint (e.g. CAF migrate landing zone).

Ready checklist

A simple list of items that we shall follow at the moment in time where we are preparing to adopt the cloud. The covered areas are Readiness Guide, Landing zone, Blueprint, and Best practices. Very useful if it your first cloud adoption project or program.

CAF Foundation blueprint

Often we forget to define and implement cloud governance. Azure is offering us a lightweight implementation of the core governance principles that we shall have inside our project. Items like:
  1. Azure Policy,
  2. Azure Resource Groups for Apps, Identity, Shared resources and network
  3. Azure Templates
, are created by the framework. Easy to extend, we can use this framework as a starting point for our Azure Governance layout. 

CAF Migration landing zone blueprint

The reality is that most of the time, migrations are similar between each others and there are a set of core principles that are applicable in most of the cases. The landing zone defines a blueprint that can be used with success to define the landing zone for our workloads that we plan to migrate to Azure. 

Terraform modules

We don't build environments and landing zone using the only ARM. Terraform is one of the 3rd parties that it is used to build and manage environemtns. To support teams that already know and use Terraform, especially for multi-cloud scenarios, Microsoft is offering guidance and out of the box modules for Terraform, that can be used to create our landing zone. 

Terraform registry

The modules from the previous item are available inside the Terraform Registry website. In this way, we have one central location from where we can fetch Terraform modules provided by Microsoft. 



Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

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...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...