1. Hybrid Cloud Kickoff Meeting
4/27/ :04 AM
Hybrid Cloud Kickoff Meeting
[Name of speaker]
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Agenda Introductions Engagement objectives and approach Azure Overview
Azure Hybrid Cloud Foundations Offering
Introductions
Engagement objectives and approach
Azure Overview
Process and Organization
Deliverables
Roles and Resources
Next Steps and Action Items
Questions

3. Introductions <Update team member names>
Azure Hybrid Cloud Foundations Team
Engagement Team Members
Customer Team Members
[Role 1] – [Name]
One sentence profile
One sentence on role responsibilities
<Update team member names>
[Role ] – [Name]
One sentence profile
One sentence on role responsibilities

4. Engagement Objectives
Provide a deep dive workshop on Azure infrastructure services
Topics include Subscriptions, Identity, Compute, Storage, Network, Management and Operations
Educate
Plan your organization’s subscription, administrative, naming convention, information security, and billing models
Detailed design and implementation of a base networking, storage, identity and compute infrastructure in your Azure subscription model using Azure Resource Manager
Design and Build your Azure Subscription
Determine which workload will be migrated to Azure for the production pilot
Provide informal knowledge transfer to your staff to prepare them to operate the Solution and to expand Microsoft Azure usage into other scenarios
Extend the Datacenter to Azure

5. Engagement Approach Azure Hybrid Cloud Foundations Envision Plan Build
Stabilize
Deploy
Describe the Solution concept and define the project team necessary to deliver it.
Assemble detailed plans and designs necessary to deliver the Solution.
Construct a Solution that includes all aspects of the project needs.
Polish and verify that the Solution meets customer and user needs and expectations.
[OPTIONAL] Deploy and integrate the Solution to its intended production environments.
Summary
Kick-off meeting
Requirements gathering
Current state assessment
Operational impact review
Vision and scope approved
Azure Technical and Operations Solution alignment workshops
Architectural Design Session for target application
Planning of subscription, administrative, naming convention, information security, and billing models
Establish Azure subscriptions
Extend the datacenter network to Azure
Configuration of subscription, administrative, naming convention, information security, and billing
ARM template creation for network, storage and compute
Test the Azure environment (connectivity, storage, virtual machines)
Validate ARM template creation
[OPTIONAL] Migrate the selected workload to the production Azure subscription
Key Activities
N/A
Solution Alignment Workshop results reports
High Level Design diagram
Azure Subscription Design
Sample ARM Templates
Deliverables

6. Azure Reference Architecture
Rulebook
The Azure Reference Architecture (AZRA) evolves as we capture learnings from customer deployments and support incidents to continuously improve the architecture and our deployment design patterns.
The potential benefits of using the AZRA include:
Tested deployment model
Deployed right the first time
Reduced time to deployment
Predictable and achievable service-level agreements
World-class user experience
More workload capabilities realized
The Azure Reference Architecture delivers customer-tested deployment patterns and practices by following design principles to facilitate:
Performance
Scalability
Interoperability
Resilience
Manageability
Quality
Supportability
Disaster Recovery
Portability

7. Solution Alignment Workshop
TechReady 16
4/27/2018
Solution Alignment Workshop
Education on the Azure platform – its constructs, its capabilities and its building blocks
Review of the Azure Reference Architecture (AZRA) patterns and models which have been gathered from numerous deployments
Review the AZRA models and identify any gaps or deployment blockers for your organization
Develop an action plan to include specific activities, resources, and timelines.
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

8. Transforming the Datacenter with Microsoft Azure
Integration
Platform Agnostic
Security

9. Huge infrastructure scale is the enabler
19 Regions ONLINE…huge datacenter capacity around the world…and we’re growing
North Europe
Ireland
West Europe
Netherlands
Central US
Iowa
North Central US
Illinois
China North *
Beijing
US Gov
Iowa
East US
Virginia
Japan East
Saitama
China South *
Shanghai
West US
California
East US 2
Virginia
Japan West
Osaka
India East
TBD
India West
TBD
US Gov
Virginia
South Central US
Texas
East Asia
Hong Kong
SE Asia
Singapore
Australia East
Sydney
Brazil South
Sao Paulo
Australia West
Melbourne
100+ datacenters
One of the top 3 networks in the world (coverage, speed, connections)
2 x AWS and 6x Google number of offered regions
G Series – Largest VM available in the market – 32 cores, 448GB Ram, SSD…
Operational
Announced
* Operated by 21Vianet

10. Azure is Open Microsoft Integrated Ecosystem Provided
Languages, Dev Tools and App Containers
Bring your own
CMS and Apps
Dozens of .NET and PHP CMS and Web applications
Devices
Via HTMl/JS, cross-platform and native
Databases
DocDB
Management
libcloud
jclouds
Operating systems
Ubuntu, SUSE, OpenSUSE,
OpenLogic CentOS-based
Oracle Linux, CoreOS
Bring
your own

11. Process and Organization
<This section of the presentation describes the engagement process. There are examples for the following slides:>
Communication Plan
Change Management
Risk and Issue Management
Project Timeline
Deliverables
Roles and Resources

12. Communication Plan Who Schedule Format
Weekly status meeting
<Stakeholders>
Weekly
<Face to face, online, or >
Project management tracking documents
Client checkpoint meetings
Internal customer communication
<Outline a communication plan, including date, medium, and attendees.>

13. Change Management
<Define how changes to the process will be managed.>
The activities below will be superseded by the statement of work (SOW) or work order (WO) for the engagement.
Change Management Activity Flow P
Delivery Management
Define Processes
Change Management Process
Review Deliverables Against Statement of Work (SOW) and Agreed Changes
Change Management
Initiate Change Requests
Manage Project Changes
Manage Work Order (WO) and Contract Changes
Change Manage-ment Process
Project Change Request Form
Change Request Log
Updates to the WO and SOW
Deliverables

14. Risk Management Delivery Management Risk Management Activity Flow P
The activities below will be superseded by the SOW or WO for the engagement.
Risk Management Activity Flow
<Define and discuss key risks and address how they will be managed.> P
Delivery Management
Risk Management Process
Hand Over Outstanding Risks
Establish Risk Management Process
Identify Risks
Manage Risks
Own Risk Actions
Master Project Plan
Risk Management Plan
Risk List
Risk Status on Internal Status Report
Risk Status on External Status Report
Deliverables

15. Issue Management
<Define how issues arising during the project will be managed.>
The activities below will be superseded by the SOW or WO for the engagement.
Issue Management Activity Flow P
Delivery Management
Establish Project Management Processes
Manage Project Issues
Hand Over Outstanding
Issues
Manage Solution Issues
Establish Project Issue Management Process
Build Stabilize Deploy
Solution Delivery
Establish Solution Issue Management Process
Transition To Operations
Resolve Solution Issues (and Bugs)
Issue Management Processes
Issue List
Solution Issue Database
Test Results And Reports
Support Knowledge Base

16. Key Events Timeline
<Update to fit an appropriate timeline for the engagement.>
Engagement Kickoff
Test Azure Resource Manager Templates
Solution handover to operations
Stabilize
Plan / Build
Envision
Solution Alignment Workshop (Technical and Operations), Architecture Design Session, Configure Azure Environment
Test Templates
[Optional] Deploy Workload, Application or Service to Production Azure Subscription
Solution handover
Day One
Deploy
Closeout
Solution Alignment Workshop
Azure Deep Dive
Design Decisions
Build reusable templates
Production deployment

17. Deliverables
Phase
Deliverable
Description
Date
Plan
Solution alignment workshop results reports
The results report produced during the Solution alignment workshops are used as input for the architecture and design of the in-scope technologies.
High-Level Design
Covers the design patterns and models selected as they align to the Azure Reference Architecture
Note: The Hybrid Cloud Foundation does not include any formal deliverables requiring acceptance as the objective is to establish an initial Azure environment and migrate one workload to it.

18. Roles and Resources
<Distinguish between partner, and customer roles. Below are sample roles.>
Roles
Name
Responsibilities
Contact information
Project Sponsor
Makes key project decisions, assists in escalating unresolved issues to the executive steering committee, and clears project roadblocks.
Project Manager
Primary point of contact for <Partner> team:
Responsible for managing and coordinating the overall project delivery.
Responsible for resource allocation, risk management, project priorities, and communication to executive management.
Manages day-to-day activities of the project (customer resources).
<Partner>Architect
Primary technical point of contact for the team that is responsible for technical architecture.
<Partner> Consultants
Primary technical point of contact for the team that is responsible for technical design and implementation.

19. Next Steps and Action Items
<Highlight any action items identified in the meeting.>
Person Responsible
Completion Date
Action