Azure Solution Alignment Workshop

Azure Solution Alignment Workshop
9/10/2018 5:43 PM Azure Solution Alignment Workshop Azure Organizational Considerations © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Azure Impact on Organizations

Impact on Organization
Cloud Operation fundamentals differ from traditional IT (and framework) Governance of defined manual processes (Traditional) Governance on fully automated processes (Cloud) Traditional Process Maturity Improvements focus on orchestration and automation across individual silo’s but leaves the silo’s in tact…! The automation removes some of the tasks and skills level can go down. Cloud Process Maturity removes silo boundaries completely (by virtualization & resource pooling) and then orchestrates and automates the process by using runbook automation. The virtualization and resource pooling needed to remove the silo boundaries (compute, network, storage) requires consolidation of skills.

Cloud Principles & Concepts
Cloud Services and solutions are based on the following principles and concepts Principles Achieve Business Value through Measured Continual Improvement Perception of Infinite Capacity Perception of Continuous Service Availability Take a Service Provider’s Approach Optimization of Resource Usage Take a Holistic Approach to Availability Design Minimize Human Involvement Drive Predictability Incentivize Desired Behavior Create a Seamless User Experience Concepts Favor Resiliency Over Redundancy Homogenization of Physical Hardware Pool Compute Resources Virtualized Infrastructure Fabric Management Elastic Infrastructure Multitenancy Partitioning of Shared Resources Resource Decay Service Classification Cost Transparency Consumption-Based Pricing Security and Identity

Impact on IT Organization
Applying cloud principles to an IT organization has the following impact: Separation of dependencies ITSM processes Shift of Responsibilities & Accountabilities New roles & skills sets Separation of dependencies Impact on current ITSM processes Service Management processes are handled differently within a cloud organization. Because of the separation of layers each layer is an independent unit with (potentially) their own ITSM processes. Changes between layers are only possible with standard changes in the form of service requests using a self-service portal or automated API. Processes within the each layer are always pro-active instead of re-active (except for the incident process), such as the capacity management and configuration process Shift of roles and responsibilities Because human involvement is set to a minimum, human responsibilities are reducing. Also each layer is a separate in depend unit with lot of responsibilities. Next slide will explain this better. New roles & skills set There for new roles and skillsets are required to deliver and operate cloud service. This will also be explained within this workshop.

Applying cloud principles to an IT organization has the following impact: SLA(s) SaaS Service Provider Supplier Driven Guidelines & Boundaries SLA(s) Applied Concepts & Principles PaaS Service Provider Traditional Process Maturity Improvements focus on orchestration and automation across individual silo’s but leaves the silo’s in tact…! The automation removes some of the tasks and skills level can go down. Cloud Process Maturity removes silo boundaries completely (by virtualization & resource pooling) and then orchestrates and automates the process by using runbook automation. The virtualization and resource pooling needed to remove the silo boundaries (compute, network, storage) requires consolidation of skills. Guidelines / Boundaries / Lifecycle Take a Service Provider’s Approach Drive Predictability Pool Compute Resources Fabric Management SLA)(s) Multi-tenancy Pool Compute Resources Partitioning of Shared Resources Service Classification IaaS Service Provider

Applying cloud principles to an IT organization has the following impact: General ITSM processes between layers and dependencies with technology Supplier driven Change Management Communication between layers about standard changes. Changes within layers are released based. Capacity Management Focused on scale units Scaling up AND scaling down Incident Management From reactive to proactive process with planned activities, monitoring Demand / Financial Management Focus on consumption, per use and show back Automated Processes: Configuration & Asset Management Daily operations (incl. patching) Standard Changes / Service Requests Applied Concepts & Principles Title: Impact on IT organization Applying cloud principles leads to impact current ITSM processes Length: 2 minutes Instructor Notes: In public cloud only fully automated processes are surfaced through self service portals. Take a Service Provider’s Approach Perception of Infinite Capacity Perception of Continuous Service Availability Minimize Human Involvement Favor Resiliency Over Redundancy Elastic Infrastructure Service Classification Consumption-Based Pricing

Applying cloud principles to an organization has the following impact: Line Of Business Line Of Business Line Of Business Line Of Business Line Of Business Competence Centers & Shared Services Exchange SaaS OS SQL Exchange OS SQL Line Of Business Line Of Business Line Of Business Applied Concepts & Principles SQL PaaS OS OS Traditional Process Maturity Improvements focus on orchestration and automation across individual silo’s but leaves the silo’s in tact…! Automation removes some of the tasks and skill levels don’t require the same depth per component. Cloud Process Maturity removes silo boundaries (through virtualization & resource pooling) and then orchestrates and automates the process through runbook automation. The virtualization and resource pooling needed to remove the silo boundaries (compute, network, storage) requires consolidation of skills and roles. Take a Service Provider’s Approach Drive Predictability Pool Compute Resources Fabric Management IaaS Virtualization Hardware Virtualization Multi-tenancy Pool Compute Resources Partitioning of Shared Resources Service Classification Storage Compute Network Storage Network

Applying cloud principles to an organization has the following impact: Process Maturity Private Resource Skill Level Traditional IT Cloud IT # Of Resources Applied Concepts & Principles Traditional Process Maturity Improvements focus on orchestration and automation across individual silo’s but leaves the silo’s in tact…! Automation removes some of the tasks and skill levels don’t require the same depth per component. Cloud Process Maturity removes silo boundaries (through virtualization & resource pooling) and then orchestrates and automates the process through runbook automation. The virtualization and resource pooling needed to remove the silo boundaries (compute, network, storage) requires consolidation of skills and roles. Take a Service Provider’s Approach Drive Predictability Minimize Human Involvement Take a Holistic Approach to Availability Design Achieve Business Value through Measured Continual Improvement Pool Compute Resources Partitioning of Shared Resources Service Classification

Defining Cloud Organizations
Azure Operations

Recommended Practice as Starting Point
Existing customer process /organization Existing Recommended Practice New Cloud Service & Organization Operate as Bimodal IT Think Big, Start Small Title: Recommended practice as starting point Length: 2 minutes Instructor Notes: Slide contains animation!. Pause between clicks to allow the graphics to render in Lync. Verify with students that they can view the slide updates. Don't try to embrace cloud using existing organization, instead leave the current organization as it is and add a competence center/center of excellence embracing the new principles and concepts. Bimodal IT Business Model Predefined Roles & Responsibilities Required Processes Governance recommendations Health model Daily Operations Existing employees transition to new roles Training on the job for team Changing organization (governance & dependencies) Blueprint describing: Dedicated Organization Accountabilities for the new service Different organization due to: New Roles & responsibilities New delegation / dependencies

Reference Model as Starting Point
The predefined roles and processes are based on the Cloud Services Reference Model Predefined Processes Service Delivery Service Manager Reliability Manager Architect New Environment Capabilities Predefined Processes Application Management & Support Service Operations Developer Tester Operator Mgmt & Sup Administrator Operations Manager Platform Platform Administrator Author Speaker notes: The cloud service foundation reference model describing the best practices which Microsoft uses to define, build and operate an cloud solution, whether this is a IaaS, PaaS or SaaS solution. The reference model is publicly available using the link on the slide. The model consists of three parts: The cloud solution itself separated by the infrastructure / Platform and Software defining the IaaS, PaaS and SaaS layers. Management and support provide all the capabilities that are required to manage and support the cloud solution. In order to delivery and operate the cloud solution properly all processes in green need to be in place as well. The processes are divided into service delivery; what is required to deliver the different cloud service towards the consumer, and service operations; what processes are required to operate the cloud solution end-to-end. This reference model will be the starting point of the Datacenter Operations workshop. Fabric Fabric Administrator

Overview Service in Modern IT Organization
Service Consumer Existing IT Organization Cloud Workload Workloads Migration Competence Centers Drive Consumption Service Provider ‘Take a Service Provider Approach’ New Service Provider Organization. Isolated using on own ITSM processes. For public cloud (or hybrid) services integration is required. Leveraging Shared Services from existing IT organization. Leveraging Competence Centers for support, guidelines and compliance. Delivering STANDARD service towards Service Consumer. Service Consumer can be IT or Business units. Service Consumer will act as service provider for their consumers. Shared Services Integration Integration Cloud

Required Roles for each model
Microsoft Ignite 2015 9/10/2018 5:43 PM Required Roles for each model Software as a Service Platform as a Service Infrastructure as a Service Service Provider Service Manager Reliability Manager Architect Mgmt & Sup Administrator Service Consumer Service Consumer Developer Operator Author Developer Operator Application Cloud Provider Office 365 Developer Operator Service Provider Service Manager Reliability Manager Architect Mgmt & Sup Administrator Platform Administrator Author This slide show the three different levels of the cloud proposition. On top of that is the service that is actually delivered towards an end-customer and is called a business service in this slide. There is always a unit (business or IT) that is responsible for delivering this service towards the end-user. They own the budget and are functional accountable for that service. They will decide how the service is implemented and operated. If they choose for a cloud solution, using the explained concepts, they need to decide what cloud service they prefer. This depends on the level of accountability and responsibility they prefer at lower level. The slide demonstrates the high-level possibilities. Within each possibility the service consumer has different accountabilities and responsibilities in the software, platform and infrastructure layer. This also goes for the service provider obviously. If we map the different roles onto the required organization, we see that certain roles sometimes fall within the service provider and sometimes within the service consumer. All depending of the service that this being delivered (IaaS / PaaS / SaaS). Important is that when a only an IaaS is being delivered. The DevOps roles are being defined at the service consumer for delivering a true cloud solution it is crucial to perfectly align with the application life cycle processes towards the cloud. The platform role is a single role within the slide in reality has every platform a dedicated platform role (SQL platform admin / SharePoint platform admin / etc.) The service delivery roles are always within the service provider organization regardless the type of offering (IaaS / PaaS / SaaS). Platform Cloud Provider Azure Platform Administrator Platform Administrator Service Provider Service Manager Reliability Manager Architect Mgmt & Sup Administrator Fabric Azure Fabric Administrator Operations Manager Fabric Administrator Operations Manager Cloud Provider Fabric Administrator Operations Manager © 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Scenario #1: Infrastructure as a Service (On-Premises)
Service Delivery Business Relation Mgmt Policy & Compliance Service Manager Architect Reliability Manager Capacity Mgmt Financial Mgmt Continuity Mgmt Service Level Mgmt Mgmt & Support Administrator Author Service Consumer Information & Sec Mgmt WL Service Life Cycle Required Processes Required Roles Service Operations Request Fullfillment Access Mgmt Operations Manager Platform Administrator Asset & Configuration Daily Operations Change Mgmt Knowlegde Mgmt Operator Developer Tester Release & Deployment Incident & Problem Mgmt Service Delivery Business Relation Mgmt Policy & Compliance Service Manager Architect Reliability Manager Capacity Mgmt Financial Mgmt Level of detail  walkthrough detail as we go. Not necessary to read all blocks. Read scenario Explain service provider: Service Delivery Service Operations Platform Integration Roles Explain Service Consumer Existing Organization & Competence Centers Migration of workloads. Explain scenario. Look at service Provider Continuity Mgmt Service Level Mgmt Information & Sec Mgmt Cloud Service Life Cycle Service Provider Platform Integration Subscription Mgmt Service Catalog Mgmt Mgmt & Support Administrator Author Required Processes Required Roles System Mgmt Integration Service Operations Request Fullfillment Access Mgmt Operations Manager Platform Administrator Asset & Configuration Daily Operations Change Mgmt Knowlegde Mgmt Fabric Administrator Release & Deployment Incident & Problem Mgmt

Scenario #2: Infrastructure as a Service (Azure)

Scenario #3: Platform as a Service (On-Premise)

Scenario #4: Platform as a Service (Azure)

Scenario #5: SharePoint as a Service (On-Premise)

Scenario #6: SharePoint as a Service (Office365)

Scenario #7: Software as a Service (Office365)

Takeaways for defining Cloud Organization
Take the following items in mind when defining a cloud organization at a customer. Cloud is not Cloud. Cloud services differ in usage and functionality. Therefore no one-size-fits all cloud organization exists (see scenarios). Supplier Driven. To keep the services STANDARD, cloud solutions (even on- premises) are never demand driven. Relevance of Patterns. The decoupling of layers requires patterns and guidelines how to consume cloud services Think Big, Start Small. Start with a small single workload delivered by a NEW Service Provider organization – Bimodal IT Change & Engage. The impact of Cloud for the IT organizations is usually not managed or planned

Key Decisions & Next Steps
9/10/2018 5:43 PM Key Decisions & Next Steps © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Azure Solution Alignment Workshop

Similar presentations

Presentation on theme: "Azure Solution Alignment Workshop"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Azure Solution Alignment Workshop

Similar presentations

Presentation on theme: "Azure Solution Alignment Workshop"— Presentation transcript:

Similar presentations

About project

Feedback