Last updated on September 22, 2023
Data transferred out of Azure data centers
Bandwidth refers to data moving in and out of Azure data centers, as well as
- Data moving between Azure data centers
- Other transfers are explicitly covered by the Content Delivery Network, ExpressRoute pricing, or Peering.
|Data transfer||First 100GB / Month||Price|
|Data Transfer In||Free|
|Data transfer between Availability Zones(Egress and Ingress)||$0.01 per GB|
|Between regions within Europe||$0.02 per GB|
|Data transfer||First 100GB / Month||Next 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|
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:
- Some triggers drive the organization to migrate current applications.
- Other triggers require creation of new capabilities, products, and experiences.
- Establish clear business outcomes: Drive transparency and engagement for your journey across the organization.
- Define business justification: Identify business value opportunities to then select the right technology.
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:
- Azure Total Cost of Ownership (TCO) Calculator: Use the TCO calculator to estimate the cost savings you can realize by migrating your application workloads to Azure.
- Azure pricing calculator: Estimate your expected monthly bill by using the pricing calculator.
- Microsoft Cost Management + Billing: Use and manage Azure and other cloud resources through a multiple-cloud cost management solution.
Define business justification
- Cost: Eliminates capital expense.
- Scale: Ability to scale elastically, delivering the right amount of IT resources
- Productivity: Removes the need for many IT management chores
- Reliability: Eases the burden of data backup, disaster recovery, and business continuity
In this stage, you focus on two main actions
- Rationalize your digital estate: Understand the organization’s current digital estate to maximize return and minimize risks by running a workload assessment.
- Create your cloud adoption plan: Develop a plan where prioritized workloads are defined and aligned with business outcomes.
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:
- Review sample business outcomes.
- Identify the leading metrics that best represent progress toward the identified business outcomes.
- Establish a financial model that aligns with the outcomes and learning metrics.
Now, let’s talk about how to get your organization ready for this journey:
- Define skills and support readiness: Create and implement a skills-readiness plan to:
- Address current gaps.
- Ensure that IT and business people are ready for the change and the new technologies.
- Define support needs.
- Create your landing zone: Set up a migration target in the cloud to handle prioritized applications.
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:
- Role Assignments
- Policy Assignments
- Azure Resource Manager templates (ARM templates)
- Resource Groups
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
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 is the process of moving existing digital assets to a cloud platform.
- Cloud-native applications and data accelerate development and experimentation cycles.
Govern and manage
- Define governance solutions for your cloud environment that meet your organization’s business needs, provide agility, and control risks.
- Manage your cloud environment based on the governance solutions to allow it to evolve, grow, and adapt to your organization’s changing business needs.
- Cloud governance creates guardrails that keep the organization on a safe path throughout the journey.
- Because governance requirements will evolve throughout the cloud adoption journey, a flexible approach to governance is required.
- Incremental governance relies on a small set of corporate policies, processes, and tools to establish a foundation for adoption and governance. That foundation is called a minimum viable product (MVP)
To determine where you should start to implement your own cloud governance, use the Microsoft assessment tools linked in the Summary and resources section
- The goal of the Manage methodology is to maximize ongoing business returns by creating balance between stability and operational costs.
Summary and resources
All useful links are stored here
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.
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: