3. 76% of CEOs consider DT their #1 priority
Source: PWC CEO Survey
Technological
advances
76%
Demographic
shifts
69%
Shift in global
economic power
58%
Resource scarcity
& climate change
39%
Urbanization
28%
Trends that will transform business over the next five years
4. A modernization strategy drives innovation + growth
1The Total Economic Impact™ Of Microsoft Azure Platform-As-A Service, Forrester Consulting, June 2016
3Source: Keystone Strategy interviews Oct 2015 - Mar 2016
80%Administration
Remove patching, network
setup, firewall configuration
Enable application innovation
—Forrester TEI of Azure1
With cloud, we collect data we
couldn’t before
Make personal connections that
standout in sea of information
—Anheuser-Busch InBev
Websites running in
minutes
Remove the need to wait for servers2
Improve app delivery time by 50%1
Organizations that harness data, the cloud, and AI outperform their peers3
operating
margin2x~
additional
operating income$100M
Data
analysis
5. …but change is difficult.
We understand this
impacts people, culture,
and can feel risky.
It requires new and
disruptive thinking
It requires leaders to adapt,
take risks, and learn quickly
It requires a culture shift
from within the organization
6. Modern business in the
cloud is the new normal
6
Today’s world reflects a new reality:
Technology is ever-present through
the cloud, offering easy access to
digital services…
Capitalizing on this shift is
key for the organization’s
innovation and growth
8. Microsoft Cloud Adoption Framework for Azure
Align business, people and technology strategy to achieve business goals with actionable,
efficient, and comprehensive guidance to deliver fast results with control and stability.
Achieve balance
9. Modular approach, meeting the customer in their journey
Building the framework
ReadyPlan AdoptStrategy
ManageGovern
10. Motivations
• Executive mandate
• Data Center Exit
• Merger and acquisitions
• Cost savings
• Optimization
• Agility
• Tech capabilities
• Market demands
• Geo expansion
• Migration
• Innovation
Define strategy
Business outcomes
• Fiscal: revenue, cost, profit
• Agility: timer to market,
provisioning,
• Reach: global access,
sovereignty
• Customer engagement:
cycle time, from request
to release
• Performance: SLAs,
Downtime, operations,
reliability
Business justification
• Business case: the cloud
is not always cheaper,
mirroring is not cloud,
servers drive cost analysis
• Financial model: Capex/
Opex, ROI, gain, cost
avoidance/reduction
• Cloud accounting:
cost center, procurement,
profit center, revenue
generating, chargeback
First project
• Business criteria:
workload supported by a
BDM
• Technical criteria:
minimum dependencies
and test path, no
governance
• Qualitative analysis:
Current Team analysis
Documenting the cloud strategy will help business stakeholders
and technicians understand the benefits the organization is
pursuing by adopting the cloud.
ReadyPlan Adopt
Define
strategy
ManageGovern
11. Plan
Cloud adoption plans convert the aspirational goals of the
cloud adoption strategy into actions. It will help guide
technical efforts, in alignment with the business strategy.
ReadyPlan Adopt
Define
strategy
ManageGovern
Digital estate
• Rationalization: inventory
• Quantitative analysis:
asset optimized and
sized properly
• Qualitative analysis:
operational process
Initial organization
alignment
• Cloud Strategy Team
• Business IT: requirements
and needs
• IT management operations:
traditional IT
• Governance: executive
sponsor, finance, business
leadership, legal,
security, HR
• Cloud platform vendor:
account success team
• Cost management
• IT-business alignment
• Governance MVP
Skill readiness plan
• Organizational readiness
• Governance and security
alignment
• Initial organization
alignment
• Building technical skills:
business/technical,
and certifications
• Change management
guidance
Cloud adoption plan
• 5R strategy: rehost,
refactor, rearchitect,
rebuild, replace
• Infrastructure migration:
VM, server,
database focus
• Application innovation:
born in the cloud
applications, APIs
• Data-driven innovation:
Focus on data
consolidation and analysis
12. Azure
readiness guide
• Resource
management:
management
groups,
subscriptions,
resource groups,
resources tree
hierarchy
• Naming Standards
• Resource tags
Landing zone
infrastructure
• Network design:
Vnet, hybrid, firewall,
hub, front door,
endpoints
• Storage design: disk,
file, blobs, CDN
• Compute design:
VMs, containers,
apps, serverless
• Data design:
Structured/
unstructured
Landing
zone ID
• Identity and access
• Role-based access
control RBAC
• Manage to least
privilege
Landing
zone cost
• Costs and billing
• Analyze Cloud Costs
• Monitor with
budgets
• Optimize with
recommendations
• Manage invoices
and payments
Blueprints
• AI
• BigData
• Hybrid networks
• Identity
management
• IoT
• Serverless
• SAP
• VMs
• WebApps
• DevOps
Ready
Ready establishes a cloud foundation or Adoption Target that can
provide hosting for any adoption efforts. This should consist of
common denominators across 80–90% of cloud adoption.
ReadyPlan Adopt
Define
strategy
ManageGovern
13. Adopt: Migrate
Cloud adoption will include workloads which do not warrant
significant investments in the creation of new business logic.
These workloads are candidates for migration to the cloud.
ReadyPlan Adopt
Define
strategy
ManageGovern
Assess
• Evaluate assets and
establish a plan
• Validate pre-requisites:
landing zone, skilling
• Drivers: reducing capex,
freeing up DC
• Quantitative factors: VMs,
networking, compatibility
• Qualitative factors:
process dependencies,
critical business events
Migrate: rehost
• Replicate (lift and shift)
on-prem functionality
using cloud native
technology
• Leverage Azure
Migration Guide
Optimize
• Balance performance
and price
• Deliver the right
experience within budget
• Resize VM size, resize
storage, resize database
Secure and manage
• Prepare the migrated
asset for ongoing
operations: security,
monitoring,
configuration
14. Adopt: Innovate
Older apps can take advantage of many of the same cloud-native
benefits by modernizing the solution or components of the solution.
Modern DevOps invites into the process to create shorter feedback
loops and better customer experiences.
ReadyPlan Adopt
Define
strategy
ManageGovern
Infrastructure
abstraction
• Cloud native
applications built
from the ground up
optimized for cloud:
• Resiliency
• Global scale
• Agility
• Security
• Autoscaling
Innovate:
refactor
• Refactoring an
application to fit a
PaaS/Serverless-
based model or
refactoring code to
deliver on new
business
opportunities.
• Drivers: faster and
shorter updates,
code portability,
greater cloud
efficiency (resources,
speed, cost)
Innovate:
rearchitect
• Modify existing
applications into
managed containers
to take advantage of
cloud native benefits
• Drivers: application
scale and agility,
easier adoption of
new cloud
capabilities, mix of
technology stacks
Innovate:
rebuild
• A new code base is
created to align with
a cloud-native
approach. App Data
and AI Services
• Drivers: accelerate
innovation, build
apps faster, reduce
operational cost
DevOps
• Culture
• Development
• Testing
• Release
• Monitoring
• Management
15. Govern
Policy definition ensures consistency across adoption efforts.
Alignment to governance/compliance requirements is key to
maintain a well-managed cross-cloud environment.
ReadyPlan Adopt
Define
strategy
ManageGovern
Cost management
• Evaluate and
monitor cost
• Limit IT spend
• Scale based on
business demand
• Create cost
accountability
Security baseline
• Compliance with
IT Security
requirements
• Apply security
baseline to all
adoption efforts
Resource
consistency
• Consistency
in resource
configuration
• Enforce on boarding,
recovery and
discoverability
practices
Identity baseline
• Enforce identity
and access baseline
• Apply role
definitions and
assignments
Deployment
acceleration
• Centralize templates
• Drive consistency
and standardization
Business risk
• Document evolving
business risk
• Document risk tolerance
based on data
classification, and
application criticality
Policy & compliance
• Convert risk decisions into
policy statements
• Establish cloud adoption
boundaries
Processes
• Establish processes to
monitor violations
• Adhere to
corporate policies
• Cloud Center
of Excellence
16. Management
• Identify critical
operations for
business operations
• Map operations
to services
• Analyze services
dependencies
• Create high level view
service dashboards
Monitoring
• Enable data collection
• Identify operations
baseline
• Generate alerts
• Measure Service
Metrics and generate
SLAs
Resiliency
• Enable a resilient
platform
• Recover from failures
with minimal
downtime and
minimum data
loss before
• Evolve to a highly
available platform
Manage and operations
Manage and operations enumerates, implements, and
iteratively reviews related to the expected operational
behavior of the service.
ReadyPlan Adopt
Define
strategy
ManageGovern
17. Microsoft Cloud Adoption Framework for Azure
Ready
• Azure readiness guide
• First landing zone
• Expand the blueprint
• Best practice Validation
Plan
• Digital estate
• Initial organization alignment
• Skills readiness plan
• Cloud adoption plan
Adopt
Define Strategy
• Understand motivations
• Business outcomes
• Business justification
• Prioritize project
Manage
Business commitments
operations baseline •
Ops maturity
Govern
Methodology • Benchmark
initial best practice •
Governance maturity
Migrate
• First workload migration
• Expanded scenarios
• Best practice validation
• Process improvements
Innovate
• Innovation guide
• Expanded scenarios
• Best practice validation
• Process improvements
19. The major drivers for
IT Governance
Keep risk at acceptable levels
Maintain availability to systems
and services
Consistently apply policy and
audit compliance
Protect customer data
20. Objective of this model: Create balance
Control &
Stability
Speed &
Results
21. Cloud Adoption Framework Governance ModelGovernance End State that fosters trust and builds confidence
Corporate Policy
Cloud Governance
Disciplines
Cloud Governance Team
24. Release
Predict, don’t guess
We could make educated guesses about future, milestone risks. We can accurately predict those risks per release.
Release Release Release Release Milestone
Release composition
Each release represents a continuum of activities from
planning to completion. Releases often span multiple
iterations of effort or sprints.
During planning, the team should be able articulate a
fairly accurate description of the assets involved, workload
criticality, data classification, deployment approach, and
budget. These may change in the release; but are close
enough for a safe governance prediction.
Release
Risk-Driven EvolutionKeep the big picture in mind, but align tasks based on immediate tangible risks
25. Governance Evolution
The Cloud Governance Team then asks deeper questions to establish a governance release
plan.
Governance Integration
During release planning, the Cloud Governance Team
seeks to understand the release plan, so they can better
integration.
The following high-level questions can help:
• When will this release be completed?
• What risks are introduced by this plan?
• What needs to change to mitigate the new risks? Release
Plan
Will application criticality in this release impact
policies regarding IT Operations or Cloud
Operations?
Will data classifications in this release impact
policies regarding IT Security?
Will the suggested deployment impact pricing,
planned spend, or cloud budget?
Will the application requirements impact identity
policies or implementation?
Will any of these answers impact configuration
management implementations or require the
implementation of new corporate policies?
Execution of Incremental Governance
Integrating into release cycles
26. Resources
MS Learn Learning module
Azure
Architecture
Center
Examples, reference architectures,
microservices design, data architectures, app
innovation design guides
MCS
Microsoft Consulting Services offering: Azure
Cloud Foundation
MS Docs Cloud Adoption Framework for Azure
Azure Expert
MSP
Partners already trained and/or with offerings
aligned to Cloud Adoption Framework for Azure
Governance
Benchmark tool
Q&A based tool to assess current and desired
state on cloud governance
Digital transformation:
Technology is omnipresent.
It’s shaping how businesses plan for innovation and growth within their markets.
The importance of digital transformation is urgent; Since 2000, 52% of Fortune 500 companies are gone due to digital disruption.
We see companies responding by creating digital strategies across four core areas: engaging their customers, empowering their employees, optimizing their operations, and transforming their products.
Everyone is aware of how important this is. Look at a company like Uber for example. They’ve created a digital model for the taxi industry that has allowed them to surpass every other taxi company by double or more, recently valued at $62.5 Billion. They’ve created a significant shift in an industry that has been largely untouched for decades
Why is this transformation important? Let’s take a look at the next few years before us…
There are huge demographic shifts , changes in economic power, impact of climate changes and rampant urbanizations happening across the globe. This calls for highly resilient computing requirements that can adapt to every market change with minimal lag, Cloud provides a scalable, highly available resilient architecture that helps companies to adapt the changing demands of the global transformation,.
Key Business Drivers for Transformation
Modernization - Improving customer and employee experiences
Transformation - Evolving how businesses operate and interact with the market
Growth - Scaling products and services to meet ever growing business needs
Business Returns - IT must rapidly produce measurable business returns to stay relevant
Cloud platforms are growing and evolving at tremendous pace with market driven demand, Starting the traditional lift and shift migration, companies are adopting modernization approaches, harnessing the platform features provided by cloud. Infrastructure services provides economies of scale and adaptation of an Opex model on long term optimization of total cost of ownership. However, modern cloud provides easy to use platform as a service capabilities that allows customers to worry about the application and not the infrastructure., This greatly reduces the maintenance efforts such as patching and extensive security configuration and frees up the customer to work on the important problems that are pertinent to a successful business.
A modern cloud also provides analytical and cognitive tools that help create intelligent apps that delight with data-driven experiences. Go quickly from concept to release with Azure data services and artificial intelligence, from image recognition to bot services. This enhances personal connection of users and help applications to stand out in the vast sea of information and tools available in the market.
Changes are challenging, Moving from a traditional on-premise to cloud is not simple. It is a marriage of people, culture, processes etc. and it can be overwhelming and can feel risky. The goal of the Cloud Adoption Framework to is make this change as smooth as possible. The CAF provides an established blueprint to drive cloud adoption using tested practices. We will discuss more in the upcoming slides.
The cloud fundamentally changes how enterprises procure and use technology resources. Traditionally, enterprises assumed ownership of and responsibility for all aspects of technology, from infrastructure to software. By moving to the cloud, enterprises can provision and consume resources only when they're needed. Although the cloud offers tremendous flexibility in design choices, enterprises need a proven and consistent methodology for adopting cloud technologies. The Microsoft Cloud Adoption Framework for Azure meets that need, helping guide decisions throughout cloud adoption.
However, cloud adoption is only a means to an end. Successful cloud adoption starts well before a cloud platform vendor is selected. It begins when business and IT decision makers realize that the cloud can accelerate a specific business transformation objective. The Cloud Adoption Framework can help them align strategies for business, culture, and technical change to achieve their desired business outcomes.
The Cloud Adoption Framework provides technical guidance for Microsoft Azure. Because enterprise customers might still be in the process of choosing a cloud vendor, the framework provides cloud-agnostic guidance for strategic decisions whenever possible.
To recap,
Cloud Computing is the new normal
Technology is ever-present thru the cloud and companies are moving to this model rapidly
Capitalizing on this shift is essential for organization’s innovation and growth,
What we have heard from customers is that we help drive a structured approach to transform their business leveraging the cloud.
In July 2018, we released the Cloud Operating Model (COM). The COM was a guide which helped customers understand the WHAT and the WHY of digital transformation, we released 2 versions of the COM, a 10-page executive summary and the full 100-page version. This helped customer get a sense of all the areas which needed to be addressed, business strategy, culture strategy and technology strategy. What was not included in the COM was the specific HOW TO’s, this left customer’s asking the question, “Where to from here”. With this gap many of our field teams began building their own models and engagement. Whilst directionally accurate, each team was saying something slightly different which ultimately led to broader customer confusion.
In October 2018, we began to take stock of all the models which had proliferated across our org, we found roughly 60 different cloud adoption models. At this time, a cross-Microsoft team was established to build on all of that success by aligning all of that great guidance. This culminated in the creation of a single model, Microsoft Cloud Adoption Framework for Azure (CAF), with the intention of helping customers understand the WHAT, WHY and provide unified guidance on the HOW from Microsoft to help them accelerate their cloud journey.
Our framework is the best one - The reason why our CAF is better is it encompasses people process and technology. We evolved our strategy continuously and published recently. So, our framework is the most advanced and relevant.
The Cloud Adoption Framework helps customers undertake a simplified cloud journey, in three main stages (Plan, Ready and Adopt) preceded by a business strategy phase, and surrounded by an ubiquitous Operate phase expanding through the cloud adoption journey.
To be successful in adopting the cloud, organizations must prepare its people, technology and processes to be ready for this digital transformation. The framework coves end-to-end guidance covering each of these aspects broken down into the adoption journey phases:
Strategy: Define business justification and expected outcomes. The three key steps in Strategy phase include: 1) understanding your motivations to move to cloud, 2) documenting desired business outcomes and 3) creating your business justificationPlan: Align business outcomes to actionable technology backlogs. Planning consists of three areas of early stage planning activities: 1) understanding your current state of digital assets 2)
identifying workloads to move/create in the cloud, 3) creating cloud adoption plan based on current digital estate.Ready: Prepare the people, culture and environment forchange. There are 2 key components in Ready: 1) creating a skills readiness plan across roles and functions, 3) setting up the cloud environment.
Adopt: Implement the desired changes across IT and business process helping customers realize their business, technology and people strategies. It includes several areas of work that will depend on what the organization is actually implementing. This will include 4 main areas: 1) workloads and assets migration, 2) apps and data modernization, 3) cloud governance, 4) assets and workloads management and operation in the cloud.
Operate: Govern and manage resources, people and business process. This phaseentails 2 steps: 1) defining governance solutions for your cloud environment and 2) managing your cloud environment allowing it to grow and adapt to your changing business needs
Understand motivations
There are many reasons and motivations for cloud adoption and understanding them is key to developing an effective cloud adoption strategy.
Classify your motivations: Your motivations for cloud adoption will likely fall into multiple categories. As you're building the list of motivations, trends will likely emerge. Motivations tend to be associated more with one classification than with others. Use the predominant classification to help guide the development of your cloud adoption strategy.
Motivation Driven Strategies – Migration and Innovation
Migration: Reduction in vendor or technical complexity, Optimization of internal operations, Increase in business agility, Preparation for new technical capabilities, Scaling to meet market demands, Scaling to meet geographic demands
Innovation: Preparation for new technical capabilities, Building new technical capabilities, Scaling to meet market demands, Scaling to meet geographic demands, Improved customer experiences and engagements, Transformation of products or services, Market disruption with new products or services
Identify desired business outcomes
Establish clear business outcomes that align with your motivations. Use this template to align stakeholders and decision makers on deciding which outcomes to prioritize. The most successful transformation journeys start with a business outcome in mind. Cloud adoption can be a costly and time-consuming effort. Fostering the right level of support from IT and other areas of the business is crucial to success. The Microsoft business outcome framework is designed to help customers identify business outcomes that are concise, defined, and drive observable results or change in business performance, supported by a specific measure.
Associate Outcomes by Strategy – Fiscal, Reach, Customer Engagement, Performance etc.
Prepare for conversations with different personas
The following are a few business outcomes that tend to trigger conversations with various personas:
Finance leadership: Increase profitability while driving compliance.
Marketing: Acquire and retain customers, build reputation.
Sales: Accelerate sales, improve customer lifetime value.
Human Resources: Retain, recruit, and empower employees.
Define your business justification
Define your business case and create a financial model to project the business impact of your cloud adoption strategy. Cloud migrations can generate early return on investment (ROI) from cloud transformation efforts. But developing a clear business justification with tangible, relevant costs and returns can be a complex process..
Dispel cloud migration myths such as
Cloud is always cheaper, Everything should go to cloud, Mirroring my on-premise environment will save money, Opex is always better than Capex, Mo ving to cloud is like flipping a switch
Estimate Migration specific initial investment
Estimate Migration specific deltas
Estimate ROI
First Project
There's a learning curve and a time commitment associated with cloud adoption planning. Even for experienced teams, proper planning takes time: time to align stakeholders, time to collect and analyze data, time to validate long-term decisions, and time to align people, processes, and technology. In the most productive adoption efforts, planning grows in parallel with adoption, improving with each release and with each workload migration to the cloud. It's important to understand the difference between a cloud adoption plan and a cloud adoption strategy. You need a well-defined strategy to facilitate and guide the implementation of a cloud adoption plan.
First project criteria
Your first adoption project should align with your motivations for cloud adoption. Whenever possible, your first project should also demonstrate progress toward a defined business outcome.
Expectations
This project is a source of learning.
This project might result in production deployments, but it will probably require additional effort first.
The output of this project is a set of clear requirements to provide a longer-term production solution.
Examples
Critical Business Events – use tools like ASR would be a good pilot project
Projects that satisfy and exemplify migration motivations, Innovation motivations
The following exercises will help you document your technology strategy. This approach captures prioritized tasks to drive adoption efforts. The cloud adoption plan then maps to the metrics and motivations defined in the cloud adoption strategy.
Digital estate
Rationalize Digital Estate: Cloud rationalization is the process of evaluating assets to determine the best approach to hosting them in the cloud. After you've determined an approach and aggregated an inventory, cloud rationalization can begin. Cloud rationalization discusses the most common rationalization options. A thorough inventory of assets, including applications, software, hardware, operating systems, and system performance metrics, is required for completing a full rationalization by using traditional models. The five Rs of rationalization: Rehost, Refactor, Rearchitect, Rebuild and Replace.
Quantitative analysis: In the decision tree, quantitative questions drive the first layer of decisions. Common questions include the following: Is the asset in use today? If so, is it optimized and sized properly? What dependencies exist between assets? These questions are vital to the classification of the inventory.
Qualitative analysis: The next set of decisions requires human intelligence in the form of qualitative analysis. Often, the questions that come up here are unique to the solution and can be answered only by business stakeholders and power users. These decisions typically delay the process, slowing things down considerably. This analysis generally consumes 40 to 80 FTE hours per application.
Initial organization alignment
The most important aspect of any cloud adoption plan is the alignment of people who will make the plan a reality. No plan is complete until you understand its people-related aspects.
True organizational alignment takes time. It will become important to establish long-term organizational alignment, especially as cloud adoption scales across the business and IT culture.
Full organization alignment is not a required component of the cloud adoption plan. However, some initial organization alignment is needed.
To create a balance between speed and control, we recommend that during cloud adoption, at a minimum, you have people accountable for cloud adoption and cloud governance. This might be a team of people sharing responsibilities for each of these areas, or capabilities. It might also be individual people who are both accountable for the outcomes and responsible for the work. In either scenario, cloud adoption and cloud governance are two capabilities that involve natural friction between moving quickly and reducing risks. Here's how the two teams fit together:
Skill Readiness Plan
The Cloud Adoption Framework guides customers through the full adoption lifecycle.
Throughout this framework, customers are provided opportunities to build necessary skills.
Strategy and Plan- Develop the skills needed to prepare an actionable migration plan. Develop Business Justification and Business Planning Skills
Ready - Develop skills to prepare the business, culture, people and environment for the upcoming changes
Adopt - Develop the technical skills to implement cloud migration plan i.e., migrate and innovate
Operate – Develop the skills for governance and operations
Available tools - Microsoft Learn, Enterprise Skills Initiative, Cloud Skills Challenge
Cloud Adoption Plan
Align plan for each of the identified workloads – in terms of the 5 Rs of cloud rationalization exercise
At each phase of the IT industry's history, the most notable changes have often been marked by changes in staff roles.
Capture concerns, Identify gaps and partner across teams
Ensuring proper support for the translated roles is a team effort. To act on this guidance, review the organizational readiness introduction to identify the right team structures and participants.
Inventory and rationalize your digital estate based on assumptions that align with motivations and business outcomes.
Initial organizational alignment
Establish a plan for initial organizational alignment to support the adoption plan.
Skills readiness plan
Create a plan for addressing skills readiness gaps.
Cloud adoption plan
Develop a cloud adoption plan to manage change across the digital estate, skills, and organization.
Azure Readiness Guide
Ensure that the environment is prepared for readiness
Sketch your playground
Create an organizational hierarchy and subscription management
Create naming standards and organize into resource groups
Plan for resource tagging– start using the tagging as a metadata for every resource for searchability and cost breakdown view
Landing Zone Infrastructure
Migration landing zone is a term used to describe an environment that has been provisioned and prepared to host workloads being migrated from an on-premises environment into Azure.
A migration landing zone is the final deliverable of the Azure setup guide. This article ties together all of the readiness subjects discussed in this guide and applies the decisions made to the deployment of your first migration landing zone.
Landing Zone Considerations
Migration tools
Logging and Monitoring
Networking
Policies
Subscription Design
Management Groups
Resource Group
Data
Storage
Naming Standards
Compute Resources
Landing Zone Id
Identity and RBAC
Landing Zone Id
Cost Management
Budgeting
Cost Analysis and Reporting
Invoices and Payment
Enterprise Agreements
Blueprints
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
Resource Groups
Assess
In an ideal migration, every asset (infrastructure, app, or data) would be compatible with a cloud platform and ready for migration.
In reality, not everything should be migrated to the cloud. Furthermore, not every asset is compatible with cloud platforms.
Before migrating a workload to the cloud, it is important to assess the workload and each related asset (infrastructure, apps, and data)
Use Azure Migrate or third-party Assessment tools such as Cloudamize, Zerto, Carbonite, Movere, Cosmos DB Partners…
Use Project planner tools such as Microsoft Planner, Project, Teams and Azure DevOps
Rehost
Once the assessment is done, use lift and shift tools
Azure Migrate
Azure Site Recovery (ASR)
Azure Database Migration Service
Data Migration Assistant
SQL Server Migration Assistant
Database Experimentation Assistant
Cosmos DB Migration tool
Optimize Migrated Assets
Use Azure Monitor to review performance
Balance and resize virtual machines
Use Reserved Instances
Resize Storage and SQL Databases
Secure and Manage
Use Azure Monitor, set up logging, alerts and notifications
Use Azure Security Center
Use Service Health for overviews
Use Azure Advisor for best practices and actionable insights
Innovate with Azure Tool Chain. Some of the Digital Invention articles in Azure Tool Chain includes:
Democratize data: Tools for sharing data to solve information-related customer needs
Engage via apps: Tools to create apps that engage customers beyond raw data
Empower adoption: Tools to accelerate customer adoption through digital support for your build-measure-learn cycles
Interact with devices: Tools to create different levels of ambient experiences for your customers
Predict and influence: Tools for predictive analysis and integration of their output into applications
Use Azure Architecture Reference Guide to drive innovation https://docs.microsoft.com/en-us/azure/architecture/architectures/?
Embrace DevOps practices early
Corporate policies: Corporate policies drive cloud governance. The governance guide focuses on specific aspects of corporate policy:
Business risks: Identifying and understanding corporate risks.
Policy and compliance: Converting risks into policy statements that support any compliance requirements.
Processes: Ensuring adherence to the stated policies.
Five Disciplines of Cloud Governance: These disciplines support the corporate policies. Each discipline protects the company from potential pitfalls:
Cost Management
Security Baseline
Resource Consistency
Identity Baseline
Deployment Acceleration – Time to market
Management Considerations:
Business alignment
Define criticality
Understand business impact
Establish business commitments
Management disciplines – Monitoring and Resiliency
Inventory and visibility
Operational compliance
Scalability and Availability
Protect and recovery
Platform operations
Workload operations
Summary of the CAF journey from the previous slides captured…
For recap
Governance is about meeting strategic objectives (performance) while meeting legal and regulatory, contractual and other obligatory requirements often supported by policies (conformance). The goal is to achieve both in a balanced way.
Started with notion that the value of cloud services (speed, agility, innovation, cost, security) is often negatively impacted by existing/legacy enterprise IT processes and practices (Legacy doesn’t work)
The cloud provides unprecedented agility and scale. Since it is now way easier to deploy resources by different people across the organization, it becomes more difficult to have control over environments and applications. Today, governance is done through manual processes, often written documentation, and a lot of approval processes. This means that if you implement governance then development speed and agility go down. They are sort of opposing forces. Azure provides you a set of governance capabilities that are fully embedded on the Azure platform to provide control without losing speed.
The Cloud Adoption Framework governance model identifies key areas of importance during the journey. Each area relates to different types of risks the company must address as it adopts more cloud services. Within this framework, the governance guide identifies required actions for the cloud governance team. Along the way, each principle of the Cloud Adoption Framework governance model is described further. Broadly, these include:
Business risks: Identifying and understanding corporate risks.
Policy and compliance: Converting risks into policy statements that support any compliance requirements.
Processes: Ensuring adherence to the stated policies.
Five Disciplines of Cloud Governance: These disciplines support the corporate policies. Each discipline protects the company from potential pitfalls:
Cost Management
Security Baseline
Resource Consistency
Identity Baseline
Deployment Acceleration
Essentially, corporate policies serve as the early warning system to detect potential problems. The disciplines help the company manage risks and create guardrails.
What native Azure features can we use to build the Governance Model?
What third parties can be used to accomplish similar goals?
The Governance Framework is evolved based on risk identification and actively bridging the risks. The Minimum Viable Product for Governance will be evolved thru the releases.
Every Release will strengthen the Governance Model and incrementally develop on top of the previous governance model. A MVP is evolved and that is identified as the baseline governance model. Depending on identification on additional risks new governance practices will be added to MVP and adopted by the enterprise.
The ability to respond rapidly to changing risks empowers the cloud governance team to engage in new ways. The cloud governance team can join the cloud strategy team as scouts, moving ahead of the cloud adoption teams, plotting routes, and quickly establishing guardrails to manage risks associated with the adoption plans. These just-in-time governance layers are known as governance iterations. With this approach, governance strategy grows one step ahead of the cloud adoption teams.