1. Azure Stack Foundation
5/10/2018 5:43 PM
[Partner Logo]
Azure Stack Foundation
Kickoff Meeting
© Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Agenda Introductions Azure Stack Overview
5/10/2018 5:43 PM
Agenda
Introductions
Azure Stack Overview
Engagement objectives and approach
Process and Organization
Deliverables
Roles and Resources
Next Steps and Action Items
Questions
© Microsoft Corporation. All rights reserved.

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

4. Cloud is a new way to think about your datacenter
5/10/2018 5:43 PM
Cloud is a new way to think about your datacenter
Optimize
Transform
Traditional model
Dedicated infrastructure for each application
Custom hardware
Distinct infrastructure and operations teams
Customized processes and configurations
Servers
Cloud model
Loosely coupled apps and micro-services
Industry-standard hardware
Service-focused DevOps teams
Standardized processes and configurations
Services
2 modes or models of IT – and they coexist simultaneously in almost every datacenter.
Traditional model and the cloud model. Both have their own unique attributes.
One is kinda well known…other is new and the conversation is sparked by what everyone is talking about.
Cloud.
But what’s interesting is the business value that your customers are asking different things out of these.
Perform and transform.
On the left. ..think physical or virtual environments - the question they are probably asking are
– how can I keep evolving the stuff that I’ve built over the years running smoothly….more efficiently…how can I save more $s for my org?
The stuff on the right is new…so they’re asking – how can I use this to cloud thing deliver innovation and speed to my business?
Translated – this means how can I quickly build apps that can help my business move faster?
So cloud is a model, not just a place. Yes, you will choose public cloud for some apps and choose private for the others.
We want to provide the same cloud model regardless of where your customers want to run their apps.
© 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.

5. Hybrid Cloud requires consistency
5/10/2018 5:43 PM
Hybrid Cloud requires consistency
Azure Active Directory
Azure management and security
Azure
data services
Azure services
Clouds
Common Identity
Integrated Management and Security
Consistent Data Platform
Unified Development and DevOps
Microsoft is the only cloud provider that offers hybrid cloud consistency, and we’ve do it across a broad range of products and services.
Let me share some examples.
<click>
Azure Active Directory extends Active Directory to enable single sign on and protect access to data used by cloud and on-premises applications.
Azure management and security services allows you to gain visibility and control across your cloud and on- premises infrastructure with simplified operations management and security
Both SQL Server and Azure SQL Database use a common T-SQL query language across cloud and on- premises. This means you can seamlessly distribute data between on-premises and cloud. SQL Server Stretch Database allows on-premises data to be archived on lower cost Azure storage with no application changes required.
Azure Stack provides Azure services in on-premises datacenters, enabling a single set of APIs and tools to deploy applications anywhere. Developers gain a common approach to building applications, and full flexibility to choose where they run.
No other vendor has built hybrid consistency across such a broad portfolio of products and services.
SQL Server
Active
Directory
On-premises
infrastructure
Azure Stack
© Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

6. Azure and Azure Stack Truly consistent hybrid cloud platform
Consistency
Why are we here today?
Azure Stack is an extension of Azure. It brings the agility and innovation of cloud computing to on-premises environments. Organizations can now build modern applications across hybrid cloud environments with the right flexibility and control.
The consistency is key. Developers can build applications using a consistent set of Azure services and DevOps processes and tools, then collaborate with operations to deploy to the location that best meets the business, technical, and regulatory requirements. Developers can speed up new cloud application development by using pre-built solutions from the Azure Marketplace, including open source tools and technologies.

7. Azure services in your datacenter Unified app development
Azure and Azure Stack
Truly consistent Hybrid Cloud platform
Cloud-inspired infrastructure
Azure IaaS | Azure PaaS Compute | Network | Storage
App Service | Service Fabric*
Azure Resource Manager
Portal | PowerShell | DevOps tools
Microsoft Azure Stack
Private | Hosted
Cloud-inspired infrastructure
Azure IaaS | Azure PaaS Compute | Network | Storage
App Service | Service Fabric*
Azure Resource Manager
Portal | PowerShell | DevOps tools
Microsoft Azure Stack
Private | Hosted
Cloud infrastructure
IaaS | PaaS
Azure Resource Manager
Portal | PowerShell | DevOps tools
Microsoft Azure
Public
Azure services in your datacenter
Unified app development
One Azure ecosystem
Developers IT
© Microsoft Corporation. All rights reserved.

8. Azure services everywhere
5/10/2018 5:43 PM
Azure services everywhere
We have 38 Azure hyper-scale regions operational today.
(Click) And then we expect 100s of service providers to join in with their own Azure Stack datacenters offering differentiated services to their customers.
(Click) And then 1000s of enterprises who will want to adopt the Azure model to serve the speed and innovation needs of their business.
All coming together. One big ‘family’ – “mi casa es tu casa”, as my Spanish friends would say.
We’re committed to delivering Azure innovation everywhere.
38 Azure regions
100s of service providers
1,000s of enterprises
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9. Developing a hybrid cloud strategy
5/10/2018 5:43 PM
Developing a hybrid cloud strategy
Physical Servers and Virtual Machines
On-premises, non-cloud
Legacy IT
New IT reality
Hybrid cloud
Replace
Modernize
Migrate
Retire/Keep/
Platform Upgrade Only
Agility
Implementation Options
Public cloud/ Private cloud Azure Stack
Private cloud
Enterprise Virtualization
Windows Server 2016
System Center 2016
SQL Server 2016
SaaS: Microsoft Dynamics, Office 365
PaaS: Microsoft Azure and
Azure Stack
IaaS: Microsoft Azure and
Target Cloud Platform
© Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10. Engagement Objectives
Educate
Plan
Build
Workshop that addresses core Windows Server 2016 software defined networking and storage capabilities along with Virtualization improvements along with ARM and Azure Stack Technical Preview capabilities.
Plan the hosting, monitoring and managing customer workloads in Azure Stack and the changes required your Operations teams. Plan and prioritize workload migration, offers, subscriptions and plans in Azure Stack.
ARM Template planning and development in Azure or Azure Stack workshop materials followed by hands-on development of ARM templates based on your envisioned Azure Stack workload.

11. Engagement Approach Envision Plan Build Closure Summary Key Activities
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.
Close the project
Summary
Kick-off meeting
Requirements gathering
Current state assessment
Operational impact review
Vision and scope approved
Project Plan reviewed
Azure Stack Technical and Operations Solution alignment workshops
Deployment integration of Azure Stack into the datacenter environment
Tenant model
Security model
Billing integration
Network integration
Identity integration
Backup integration
Deployment of the single-node Azure Stack Development Kit [or use of approved OEM SKU]
Modeling of subscription, offer/plan, RBAC, network, and billing
Initial workload planning
ARM template creation for infrastructure areas
Close out meeting
Review what’s been accomplished.
Discuss next steps.
Key Activities
Vision scope document
High level functional specification
Next steps report (AZOP Intro)
Azure Stack workload and integration design
Sample ARM Templates
Deliverables

12. Solution Alignment Workshop
TechReady 16
5/10/2018
Solution Alignment Workshop
Education on the Azure Stack platform – its constructs, its capabilities and its building blocks
Review of the patterns and models which have been gathered from numerous deployments
Review the integration 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.

13. 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

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

15. 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

16. Risk Management
<Define and discuss key risks and address how they will be managed.>
The activities below will be superseded by the SOW or WO for the engagement.
Risk Management Activity Flow 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

17. 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

18. Build and Test Infrastructure Templates, Design initial workload
Key Events Timeline
<Update to fit an appropriate timeline for the engagement.>
Engagement Kickoff
Azure Resource Manager Templates
Workload Planning
Build
Plan
Envision
Solution Alignment Workshop (Technical and Operations), Deployment integration planning
Build and Test Infrastructure Templates, Design initial workload
Closeout meeting
Day One
Deploy
Solution Alignment Workshop
Azure Stack Workshop
Design Decisions
Plan integration points

19. 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 Functional Specification
This is a high-level documentation of the areas covered in the SAWs.
Next Steps Report
This is a Microsoft Word document that outlines the gaps that are identified in Azure Operations processes that are to be used for adopting Azure Stack.
Build
High-Level Offer, Plan, Quota Strategy 
This Visio or Microsoft PowerPoint diagram provides a high-level visual representation of the results of the design session.
High-Level Architectural Diagram
ADS Results Report
This Word document summarizes the results of the design session that was conducted
Note: The Azure Stack Foundation engagement does not include any formal deliverables requiring acceptance.

20. Roles and Resources Refer to the Statement of Work
<Distinguish between Microsoft, partner, and customer roles. Below are sample roles>
Refer to the Statement of Work
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.
Microsoft Project Manager
Primary point of contact for Microsoft 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).
Microsoft Architect
Primary technical point of contact for the team that is responsible for technical architecture.
Microsoft Consultants
Primary technical point of contact for the team that is responsible for technical design and implementation.

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

22. 5/10/2018 5:43 PM
Questions?
© Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

23. 5/10/2018 5:43 PM
[Partner Logo]
© Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.