CAF presentation 09 16-2020
•Télécharger en tant que PPTX, PDF•
0 j'aime•1,985 vues
Omaha Azure User Group presentation slides: Pitfalls to Avoid on you Cloud Adoption Journey
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à CAF presentation 09 16-2020
Similaire à CAF presentation 09 16-2020 (20)
Dernier
Dernier (20)
CAF presentation 09 16-2020
- 1. Cloud AdoptionFrameworkfor Azure Pitfalls to avoid on your Cloud Migration Journey Presented by Michael Nichols
- 2. What is Cloud Adoption Framework for Azure? • It’s a collection of documentation, technical guidance, best practices, and tools that aid in aligning business, organizational readiness, and technology strategies. • It accelerates meeting business objectives and guides decision making 2
- 3. The Cloud Adoption Framework approaches cloud adoption as a self-service activity. The objective is to empower each of the teams supporting adoption through standardized approaches Azure solution providers (partners): Get connected with Azure expert managed services providers (MSP) and other Microsoft partners who have service offerings aligned to the Cloud Adoption Framework methodologies. FastTrack for Azure: Use the Microsoft FastTrack for Azure program to accelerate migration. Azure Migration Program (AMP): The AMP program aligns a mixture of partners and Microsoft employees to accelerate and support your migration. Framework Intent Strategy for partner alignment Pitfall Avoidance - Don’t do it alone Foundational Alignment Every member of the team should have a basic understanding of how azure works Every technical team member should have a basic understanding of fundamental Azure concepts
- 4. https://aka.ms/adopt/overview Phases of Cloud Adoption Lifecycle
- 5. 5 Define Strategy ● Understand motivations ● Business outcomes ● Business justification ● Prioritize project Plan ● Rationalize digital assets ● Initial organization alignment ● Skills readiness plan ● Cloud adoption plan Ready ● Azure setup guide ● First landing zone ● Expand the landing zone ● Best practice Validation Define strategy Plan Adopt Ready ManageGovern Adopt Migrate ● Migration Guide ● First workload migration ● Expanded scenarios ● Best practice validation ● Process improvements Innovate ● Innovation guide ● Expanded scenarios ● Best practice validation ● Process improvements Govern ● Methodology ● Benchmark initial best practice ● Governance maturity Manage ● Business commitments ● Operations baseline ● Operations maturity https://aka.ms/adopt/overview Cloud Adoption Framework
- 6. Defineanddocumentyour motivations Meet with key stakeholders and executives to document the motivations behind cloud adoption Documentbusiness outcomes Engage motivated stakeholders and executives to document specific business outcomes 1 2 Develop a business case Develop a business case to validate the financial model that supports your motivations and outcomes Choosethe right first project This first project will help align motivations with technical effort and must be chosen wisely 3 4 Defineyour strategy
- 7. Critical business events Migration Innovation Datacenter exit Merger, acquisition, or divestiture Reduction in capital expenses End of support for mission-critical technologies Response to regulatory compliance changes New data sovereignty requirements Reduction of disruptions and improvement of IT stability Cost savings 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 Integration of a complex IT portfolio 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 Democratization and/or self-service environments Strategy – Define document your motivations
- 8. Pitfall Avoidance –Involve all stakeholders in these motivation discussions to ensure alignment
- 9. XYZ Life Sciences Co. - Drug & Device Division Stakeholder: Therapeutic Product Owner Business Outcome: Decrease Time to Market for drug/device Business Drivers KPI Capabilities Study Design $3M opportunity cost per day per drug Data-Driven protocol authoring Study Conduct Trial Simulation Structured collaboration for trial approval Strategy - Document your business outcomes Types of Business Outcomes Fiscal Outcomes Agility Outcomes Reach Outcomes Customer Engagement Outcomes
- 10. Pitfall Avoidance –Identify meaningful KPIs including hard/soft costs in business outcomes KPIs support measurable successful outcomes and can reduce anxiety and resistance to cloud adoption
- 11. Tools you can use: • 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. • Azure Cost Management: Use and manage Azure and other cloud resources through a multiple-cloud cost management solution. Cloud Accounting Models versus Traditional (cost center model, profit center models) ROI = (Gain from Initial Investment – Initial Investment) / Initial Investments Gain from investment = revenue deltas + cost deltas Strategy – Business Justification
- 12. Pitfall Avoidance– Dispel cloud migrationmyths Thecloud is always cheaper Everything should go into the cloud Mirroringmy on-premises environmentwill help me savemoneyin the cloud Servercosts drive businesscasesfor cloud migration An operating expense model is better than a capital expense model Moving tothe cloud is like flipping a switch Myths
- 13. Your first adoption project should align with your motivations for cloudadoption. Whenever possible, your first project should also demonstrate progress toward a defined business outcome Your team's first adoption project is likelyto result in a production deployment of some kind. But this isn't always the case. Establish proper expectations early. Hereare afew wise expectations toset: 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 Strategy – Choosethe first cloud adoption project
- 14. Develop your plan 1 2 3 4 DIGITAL ESTATE INITIAL ORGANIZATIONAL ALIGNMENT SKILLS READINESS PLAN CLOUD ADOPTION PLAN Inventory and rationalize your digital estate based on assumptions that align with motivations and business outcomes Establish a plan for initial organizational alignment to support the adoption plan Create a plan for addressing skills readiness gaps Develop a cloud adoption plan to manage change across the digital estate, skills, and organization
- 15. Pitfall Avoidance –Don’t miss steps 2 and 3 in your plan These steps are often overlooked
- 16. Plan -Rationalize your digital estate Rehost Refactor Rearchitect Rebuild/New Replace Also known as a lift-and-shift migration, a rehost effort moves a current state asset to the chosen cloud provider, with minimal change to overall architecture Also refers to the application development process of refactoring code to allow an application to deliver on new business opportunities When aging applications aren't compatible with the cloud, they might need to be rearchitected to produce cost and operational efficiencies in the cloud Unsupported, misaligned, or out-of-date on-premises applications might be too expensive to carry forward. A new code base with a cloud-native design might be the most appropriate and efficient path Sometimes the best approach is to replace the current application with a hosted application that meets all functionality required in the cloud
- 17. Pitfall Avoidance –Keep it simple and makeit quick Avoid analysis paralysis on common goals
- 18. Plan -Initial organization alignment https://docs.microsoft.com/en-us/azure/cloud-adoption- framework/organize/raci-alignment
- 19. Plan -Skill Readiness Capture concerns Identify gaps Partner Across Teams
- 20. • Prerequisites: Confirm that all prerequisite steps have been completed before you create your plan. • Define and prioritize workloads: Prioritize your first 10 workloads to establish an initial adoption backlog. • Align assets to workloads: Identify which assets (proposed or existing) are required to support the prioritized workloads. • Review rationalization decisions: Review rationalization decisions to refine adoption path decisions: migrate or innovate. • Establish iterations and release plans: Iterations are the time blocks allocated to do work. Releases are the definition of the work to be done before triggering a change to production processes. • Estimate timelines: Establish rough timelines for release planning purposes, based on initial estimates. Azure DevOps Demo Generator Plan - Cloud adoption plan
- 21. Azure setup guide Azure landing zones Expand the landing zone Best practices 1 2 3 4 Review the Azure setup guide to become familiar with the tools and approaches you need to use to create a landing zone Choose the most appropriate landing zone option, to establish a code-based starting point for your environment Meet the platform requirements of your cloud adoption plan by expanding the first landing zone Validate landing zone modifications against best practices to ensure the proper configuration of your current and future landing zones Ready
- 22. Organize resources Manage access Manage costs and billing Plan for governance , security, and compliance Use monitoring and reporting Stay current with Azure Track product updates to enable a proactive approach to change management Enforce and automate policies and security settings that help you follow applicable legal requirements Get visibility across resources to find and fix problems, optimize performance, and gain insight into customer behavior Identify your subscription type, understand how billing works, and learn how to control costs Use role-based access control to make sure that users have only the permissions they really need Set up a management hierarchy to consistently apply access control, policy, and compliance to groups of resources and use tagging to track related resources Ready – Azure setup guide You'll learn how to:
- 23. Azurelanding zones are the output of a multi- subscription Azureenvironment that accounts for scale, security, governance, networking, and identity. All Azurelanding zones providea scalable, modular approach to building out your environment based on a common set of design areas. Ready – Azure landing zones CAF Foundation blueprint in Azure
- 24. Demo – CAF Blueprint - Landing Zone Ready – Expand the landing zones Implementation Options Blueprints Menu Blade Get Started
- 25. Decision Guides Ready – Best practices Best Practices
- 26. Pitfall Avoidance –Make sure Ready is ready Otherwise, Governance & Management are impossible and require large efforts to enable Security standards non-compliance Riskbreaches anddataloss Lackof operationalefficiencies andinability toalign future efforts BillShockrelated to costinefficiencies andlackof limits Performance andlatencyissue causebeinappropriate regions Naminginconsistency Lackof RBAC Agilityconstrained bythematurityof individual/teambrings craftingdeployment Laterefforts to mitigateintroduce technicalcomplexityrisk ofdown-time
- 27. Adopt -Migrate
- 28. Adopt -Innovate
- 29. Govern
- 30. Manage
- 31. Define strategy Plan Ready Adopt Govern Manage Cloud journey tracker Business outcome template Cloud adoption plan generator Azure DevOps demo generator Cloud adoption plan template Azure setup guide Readiness checklist Naming and tagging tracking template Landing zone blueprints Strategic migration assessment and readiness tool (SMART) Azure migration guide Azure innovation guide Governance benchmark Governance process template Cost Management process template Deployment acceleration process template Identity process template Resource consistency process template Security baseline process template Azure architecture review Best practices source code Operations management workbook aka.ms/adopt/tools-templates Tools, templates, and assessments
- 32. Q&A Open Discussion Thank You! Michael Nichols LinkedIn Profile
Notes de l'éditeur
- Material referenced from Microsoft Cloud Adoption Framework Documentation available at https://aka.ms/adopt/overview Let’s first identify what the CAF is: The Cloud Adoption Framework brings together cloud adoption best practices from thousands of Microsoft employees, partners, and customers. It provides a set of tools, guidance, and narratives that help shape technology, business, and people strategies for driving desired business outcomes during your adoption effort. It follows agile principles and a requires a growth mindset. This guidance aligns to the phases of the cloud adoption lifecycle, giving you easy access to the right guidance at the right time. So, now hearing this glowing description of the CAF, let discuss the first potential pitfall to avoid aka.ms/adopt.plan
- While CAF Framework has the intent of providing a self-service approach to cloud adoption it is important to consider strategic partnership alignment. Few corporations have the diversity of skills required to support the strategy, planning, readiness, adoption, governance, and management. Partners and other support models are often necessary to fill in the gaps in the team's skills and responsibilities.
- The phases of the cloud adoption lifecycle consist of three main phases that are completed iteratively: Plan, Ready, & Adopt These three main stages are preceded by a business strategy phase and surrounded by an operations phase (that included Governance and Management) that expands through the cloud adoption journey. Strategy - Define You Business Objects Plan - Prepare you organization for the cloud Ready - Prepare you environment to move work loads to the cloud Adopt – Is when the rubber hits the road. The CAF offer guidance whether your intent is to Migrate current workload to the cloud of Innovate by taking advantage of what the cloud has to offer. Govern & Manage - Establish well managed cloud environment by implementing governance and ensure alignment with you existing IT infrastructure as security best practices
- Preferred view with Strategy at the core, surround by iterative plan, ready, and adopt phases, all within the bounds of Governance and Management The phases of the cloud adoption lifecycle consist of three main phases that are completed iteratively: Plan, Ready, & Adopt These three main stages are preceded by a business strategy phase and surrounded by an operations phase (that included Governance and Management) that expands through the cloud adoption journey. Strategy - Define You Business Objects Plan - Prepare you organization for the cloud Ready - Prepare you environment to move work loads to the cloud Adopt – Is when the rubber hits the road. The CAF offer guidance whether your intent is to Migrate current workload to the cloud of Innovate by taking advantage of what the cloud has to offer. Govern & Manage - Establish well managed cloud environment by implementing governance and ensure alignment with you existing IT infrastructure as security best practices
- https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/strategy/ So let dig deeper into the first phase of you journey – Defining you strategy
- Defining and documenting your motivation requires all clear understanding of all stakeholder’s motivation. Motivation vary greatly between the business and technical side. Motivations often include: Organization is preparing for new technical capabilities Gaining scale to meet market or geographic demands Cost savings Reduction in vendor or technical complexity Optimization of internal operations Increased business agility Improvements to customer experiences or engagements Disruption of the market with new products or services
- https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/strategy/motivations Critical pitfall to avoid during the motivation step of the strategy phase is to not have all stakeholders involved. Discussion around your organization’s motivation with result in important decision further down you cloud journey path. Without coming to agreement regarding motivations, you are sure to underdeliver or overdeliver on the wrong goals of your organization. Migration or Innovation 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.
- Business Outcomes step of your Strategy phase is where you document your agreed upon business outcomes. The CAF provide business outcome templates to help drive these conversations. https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/strategy/business-outcomes/ Which focus around: Fiscal Outcomes Agility Outcomes Reach Outcomes - Growth Customer Engagement Outcome
- Common pitfall during the business outcome step of the Stagey phase are frequently related to not defining meaningful KPIs. To help drive the development of good KPIs. It is helpful to view this as a discovery process. Stakeholders: Who in the organization is likely to see the greatest value in a specific business outcome? Who is most likely to support this transformation, especially when things get tough or time consuming? Who has the greatest stake in the success of this transformation? This person is a potential stakeholder. Business outcomes: A business outcome is a concise, defined, and observable supported by a specific measure. Business drivers: Business drivers capture the current challenge that's preventing the company from achieving desired outcomes. KPIs: How will this change be measured? How does the business know if they are successful? How frequently will this KPI be observed? Capabilities: What applications must be included in the transformation to achieve business objectives? How do various applications or workloads get prioritized to deliver on capabilities?
- The third step in the Strategy phase is Business Justifications. Cloud Accounting models are quite different from traditional cost models. Understanding how to determine ROI can be complicated. One common finical model recommend by the CAF is mentions: Revenue deltas Revenue deltas should be forecast in partnership with business stakeholders. After the business stakeholders agree on a revenue impact, it can be used to improve the earning position. Cost deltas Cost deltas are the amount of increase or decrease that will be caused by the transformation. Independent variables can affect cost deltas. Earnings are largely based on hard costs like capital expense reductions, cost avoidance, operational cost reductions, and depreciation reductions. The following sections describe some cost deltas to consider. Cost Deltas Physical asset recovery Operational cost reductions Software licensing. Hosting expenses. Electric bills. Real estate rentals. Cooling expenses. Temporary staff required for operations. Equipment rentals. Replacement parts. Maintenance contracts. Repair services. Business continuity and disaster recovery (BCDR) services. Other expenses that don't require capital expense approvals that often provide the highest earning deltas. When you're considering a cloud migration, time invested in making this list exhaustive is rarely wasted. Cost avoidance Soft-cost reductions Headcount reductions Capital expense avoidance due to removal refresh cycles
- Common pitfalls to avoided during the business justification phase of the Strategy Phase are often tied to myths about the cloud. Dispel these common myths. Myth: The cloud is always cheaper It's commonly believed that operating a datacenter in the cloud is always cheaper than operating one on-premises. While this assumption might generally be true, it's not always the case. Sometimes cloud operating costs are higher. These higher costs are often caused by poor cost governance, misaligned system architectures, process duplication, atypical system configurations, or greater staffing costs. Fortunately, you can mitigate many of these problems to create early ROI. Following the guidance in Build the business justification can help you detect and avoid these misalignments. Dispelling the other myths described here can help too. Myth: Everything should go into the cloud In fact, some business drivers might lead you to choose a hybrid solution. Before you finalize a business model, it's smart to complete a first-round quantitative analysis, as described in the digital estate articles. For more information about the individual quantitative drivers involved in rationalization, see the five Rs of rationalization. Either approach will use easily obtained inventory data and a brief quantitative analysis to identify workloads or applications that could result in higher costs in the cloud. These approaches could also identify dependencies or traffic patterns that would necessitate a hybrid solution. Myth: Mirroring my on-premises environment will help me save money in the cloud During digital estate planning, it's not unheard of for businesses to detect unused capacity of more than 50% of the provisioned environment. If assets are provisioned in the cloud to match current provisioning, cost savings are hard to realize. Consider reducing the size of the deployed assets to align with usage patterns rather than provisioning patterns. Myth: Server costs drive business cases for cloud migration Sometimes this assumption is true for other companies can five-year to eight-year hardware refresh cycle are unlikely to see returns on their cloud migration. Myth: An operating expense model is better than a capital expense model As explained in the fiscal outcomes article, an operating expense model can be a good thing. But some industries view operating expenditures negatively. Myth: Moving to the cloud is like flipping a switch Migrations are a manually intense technical transformation. You must consider Bandwidth limitations: The amount of bandwidth between the current datacenter and the cloud provider will drive timelines during migration. Testing timelines: Testing applications with the business to ensure readiness and performance can be time consuming. Aligning power users and testing processes is critical. Migration timelines: The amount of time and effort required to implement the migration can increase costs and cause delays. Technical and cultural impediments can slow cloud adoption. Migration-specific initial investment
- Final step in the Strategy phase -choosing your first cloud adoption project. The CAF provides a few example project that can help guide you You may be choosing your first project as a result of: A Critical business events: Where a tool like Azure Site Recovery might be a good first project. The CAF allow highlights how the Azure Migrate tools can help you quickly migrate datacenter assets. Migration motivations: When migration is the primary motivation, it's wise to start with the migration of a noncritical workload. The Azure setup guide and the Azure migration guide can provide guidance for the migration of your first workload. Innovation motivations: Creation of a targeted dev/test environment can be a great first project. Starting a first project adoption process in parallel with the development of the next phase – the plan phase may provide some benefits such as: Establish a growth mindset to encourage learning and exploration. Provide an opportunity for the team to develop necessary skills. Create situations that encourage new approaches to collaboration. Identify skill gaps and potential partnership needs. Provide tangible inputs to the plan.
- https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/plan/ Most organization tend to focus the energy on Rationalize your Digital Estate and creating of the Cloud Adoption Plan as these are the more technically focused steps in this phase. 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.
- Pitfall avoidance – don’t skip steps 2 and 3 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. Throwing your organization into the cloud without a skills readiness plan can have devasting effect. In addition to having lost cycles it can destroy a team’s morale
- Rehost - Also known as a lift-and-shift migration, a rehost effort moves a current state asset to the chosen cloud provider, with minimal change to overall architecture. Reduce capital expense. Free up datacenter space. Achieve rapid return on investment in the cloud. Refactor - also refers to the application development process of refactoring code to allow an application to deliver on new business opportunities. Experience faster and shorter updates. Benefit from code portability. Achieve greater cloud efficiency in the areas of resources, speed, cost. Rearchitect - When aging applications aren't compatible with the cloud, they might need to be rearchitected to produce cost and operational efficiencies in the cloud. Gain application scale and agility. Adopt new cloud capabilities more easily. Use a mix of technology stacks. Rebuild/New - Unsupported, misaligned, or out-of-date on-premises applications might be too expensive to carry forward. A new code base with a cloud-native design might be the most appropriate and efficient path. Accelerate innovation. Build apps faster. Reduce operational cost. Replace -Sometimes the best approach is to replace the current application with a hosted application that meets all functionality required in the cloud. Standardize around industry best practices. Accelerate adoption of business process-driven approaches. Reallocate development investments into applications that create competitive differentiation or advantages.
- To create a balance between speed and control, at a minimum, you must have people accountable for the cloud adoption and cloud governance Adoption Only is anti-pattern! To align your origination you must understand Structure types and Define the type of organizational structure that best fits your operating model. You must also understand Cloud functions and what is required to adopt and operate the cloud. And you must account for mature team structures to Define the teams that can provide various cloud functions. RACI matrix help to Clearly defined roles are an important aspect of any operating model. The CAF provides RACI matrix that help guide your efforts when aligning your organization:
- Cloud adoption plans convert the aspirational goals of a cloud adoption strategy into an actionable plan. It is an iterative project plan that helps a company transition from traditional IT approaches to modern, agile approaches. The CAF provide an Azure DevOps template the generate a project for you, that is extremely helpful
- The CAF provides a lot of tools and automation to get quickly on your path in the Ready phase. Click links
- Click links
- https://github.com/Azure?q=caf&type=&language= https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/implementation-options
- CAF provides a wealth of best practices that decision guides to help you Click links
- For an interactive experience, view this guide in the Azure portal. Go to the Azure Quickstart Center in the Azure portal, select Azure migration guide, and then follow the step-by-step instructions. Assess each workload's technical fit. Validate the technical readiness and suitability for migration. Migrate your services. Perform the actual migration, by replicating on-premises resources to Azure. Manage costs and billing. Understand the tools required to control costs in Azure. Optimize and promote. Optimize for cost and performance balance before promoting your workload to production. Get assistance. Get help and support during your migration or post-migration activities. It is assumed that a landing zone has already been deployed, in alignment with the best practices in the
- For an interactive experience, view this guide in the Azure portal. Go to the Azure Quickstart Center in the Azure portal, select Azure migration guide, and then follow the step-by-step instructions. https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/innovate/
- https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/govern/methodology Cloud governance creates guardrails that keep the organization on a safe path throughout the journey. Easiest if you define corporate policy up front 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). An MVP allows the governance team to quickly incorporate governance into implementations throughout the adoption lifecycle. After this MVP is deployed, additional layers of governance can be quickly incorporated into the environment. Cloud governance is an iterative process. For organizations with existing policies that govern on-premises IT environments, cloud governance should complement those policies. The level of corporate policy integration between on-premises and the cloud varies depending on cloud governance maturity and a digital estate in the cloud. As the cloud estate changes over time, so do cloud governance processes and policies. The following exercises help you start building your initial governance foundation.
- The historical IT operating model was sufficient for over 20 years. But that model is now outdated and is less desirable than cloud-first alternatives. When IT management teams move to the cloud, they have an opportunity to rethink this model and drive greater value for the business. It is necessary to modernized model of IT management. Operations management workbook https://raw.githubusercontent.com/Microsoft/CloudAdoptionFramework/master/manage/opsmanagementworkbook.xlsx