Ms Cloud Adoption Framework for Azure

Data transferred out of Azure data centers

Bandwidth refers to data moving in and out of Azure data centers, as well as

Data transferFirst 100GB / MonthPrice
Data Transfer InFree
Data transfer between Availability Zones(Egress and Ingress)$0.01 per GB
Between regions within Europe$0.02 per GB
Data transferFirst 100GB / MonthNext 10TB / Month
Internet Egress (routed via Microsoft Premium Global Network)
Europe to any destination
Free$0.087 per GB
Internet Egress (Routed via Routing preference transit ISP network)
Europe to any destination
Free$0.08 per GB

Pricing – Bandwidth | Microsoft Azure

Microsoft Cloud Adoption Framework for Azure

The Cloud Adoption Framework for Azure is a collection of documentation, technical guidance, best practices, and tools that aid in aligning business, organizational readiness, and technology strategies.

 It can help guide your decisions throughout cloud adoption to accelerate a specific business objective.

The Cloud Adoption Framework helps customers undertake a simplified cloud journey in three main stages:

Define strategy



The first application an organization deploys to the cloud is often done so in an experimental environment with no operational or governance capacity. It’s important to select an application that doesn’t interact with secure data. Carefully consider which application is a good candidate. As you plan subsequent releases and additional applications are deployed to the cloud, you create the first prioritized migration application and the first prioritized release backlog. Over time, you create and continue to shape the optimal environment for future deployments.

Establish clear business outcomes

The most successful cloud adoption journeys start with a business outcome in mind, backed up by financial reasoning and support. A business outcome is a concise, defined, and observable result or change in business performance that’s captured by a specific measure.

Here are some tools to support you in your financial planning:

Define business justification

1 Plan

In this stage, you focus on two main actions

Rationalize your digital estate

During this process, we recommend that you proceed incrementally, application by application. Don’t make decisions too broadly or too early across the entire application portfolio.

There are five options for cloud rationalization, sometimes referred to as the Five Rs:

Create your cloud adoption plan

Key steps to build this plan are to:

2 Ready

Now, let’s talk about how to get your organization ready for this journey:

Create your landing zone

Before you begin to build and deploy solutions with Azure services, make sure your environment is ready. The term landing zone is used to describe an environment that’s provisioned and prepared to host workloads in a cloud environment, such as Azure.

Each landing zone is part of a broader solution for organizing resources across a cloud environment. These resources include management groups, resource groups, and subscriptions.

Blueprints are a declarative way to orchestrate the deployment of various resource templates and other artifacts such as:

Standards-based Azure Blueprints samples are available and ready to use. Visit the list of available samples that are ready to use or modify for your needs linked in the Summary and resources section

3 Adopt

At this point, you’ve established your business justification and defined your business outcomes. You’ve prepared your organization. Your people and your Azure environment are ready to deploy your prioritized applications. You’re ready to adopt cloud technologies following the selected digital estate rationalization path.

Cloud migration

Cloud innovation

Govern and manage

Cloud governance

To determine where you should start to implement your own cloud governance, use the Microsoft assessment tools linked in the Summary and resources section

Cloud management

Summary and resources

All useful links are stored here

Summary and resources – Training | Microsoft Learn

AZ-305 Microsoft Azure Architect Design Prerequisites – Training | Microsoft Learn

This article provides a list of resources that you can use to make informed decisions about the technologies that you choose for your Azure solutions. Explore comparison matrices, flowcharts, and decision trees to ensure that you find the best matches for your scenario.

Azure choose solution – e-lo (

Togaf vs Azure Well-Architected Framework

TOGAF is a comprehensive framework for enterprise architecture that provides a common language, methodology, and tools for designing and managing IT architecture. In short, it’s a set of best practices for creating and implementing technology solutions that meet business needs. TOGAF is intended to help organizations reduce costs, improve efficiency, and increase the agility of their IT infrastructure.

So you want to build great things in Azure.

Azure Well-Architected Framework

The Azure Well-Architected Framework is a set of guiding tenets to build high-quality solutions on Azure. There’s no one-size-fits-all approach to designing an architecture, but there are some universal concepts that apply regardless of the architecture, technology, or cloud provider.

These concepts aren’t all-inclusive, but focusing on them can help you build a reliable, secure, and flexible foundation for your application.

The Azure Well-Architected Framework consists of five pillars:

Introduction to the Microsoft Azure Well-Architected Framework – Training | Microsoft Learn