1. About this Template
Datacenter Infrastructure and Management Offering
The engagement kick-off presentation should introduce the project team and summarize the project plan, which includes the communications plan, deliverables, Services Delivery Methodology, and other relevant project information.
This is a customer-facing deliverable targeted to engagement managers.

2. About this Template Datacenter Infrastructure and Management Offering
What you need to do as a presenter:
Fill in your name and customer name.
Translate, if necessary.
Delete or hide any instruction slides and text. <Instructional text is red.>
View and present on full presentation mode because of build and animation effects.
Confirm that any and all web references are working and that you have them filled in.
Read the presentation notes sections and use when prompted.
If you send this presentation file to a customer, please first delete all instructional slides, notes, and any other content not normally seen in presentation mode.

3. Engagement Kickoff [Presenter’s Name/Title] [Date of Presentation]
Azure Dev Test Solution in a Box
[Presenter’s Name/Title]
[Date of Presentation]

4. Agenda Introductions Engagement objectives and approach
Datacenter Infrastructure and Management – Hybrid Cloud Scenario
Introductions
Engagement objectives and approach
What is a Product Line Architecture?
Architecture
Process and Organization
Work Products
Roles and Resources
Next Steps and Action Items
Questions

5. Introductions [Project Name] Team
<Introduce team members from <Partner Name>, customer, and partners.>
<Partner Name> Team Members
Customer Team Members
[Role 1] – [Name]
One sentence profile
One sentence on role responsibilities
Project Manager – John or Jane Doe
15 years project management experience integrating enterprise infrastructure with focus on private cloud and virtualization.
Responsible for day-to-day running of project, and for managing the plan and resources end-to-end.
[Role ] – [Name]
One sentence profile
One sentence on role responsibilities
[Customer name] team members

6. Introductions (Partner Version)
[Project Name] Team
<Introduce team members from <Partner Name>, customer, and partners.>
<Partner Name>Team Members
[Partner Name] team members
[Role 1] – [Name]
One sentence profile
One sentence on role responsibilities
Project Manager – John or Jane Doe
15 years project management experience integrating enterprise infrastructure with focus on private cloud and virtualization.
Responsible for day-to-day running of project, and for managing the plan and resources end-to-end.
[Role ] – [Name]
One sentence profile
One sentence on role responsibilities
[Customer name] team members

7. Engagement Objectives
<Outline the objectives of the engagement that includes the current business and technical challenges as well as the scope. Below is some sample wording.>
Assess the app workload that we’ll be building lab capabilities for in Azure
Assessment
Conduct the solution alignment workshop to provide an overview and deep dives on Microsoft Azure, the Microsoft Azure SDK, and our library of PowerShell lab automation
Drive discussions with application owners, service owners, and others to gather data about lab usage, self-service, and automation needs
Analysis
Identify lab scenarios and map requirements to capabilities.
Create architecture and design guidance for:
Building foundational infrastructure capability in Microsoft Azure
Connecting Microsoft Azure to existing networks
Importing and configuring Microsoft’s library of lab automation code
Develop Design
Build and test the deployment in Microsoft Azure
Assist you in configuring your app’s labs with the solution
Conduct a solution walk through with your staff
Deployment

8. Engagement Approach
<Outline the engagement approach and activities.>
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.
Deploy and integrate the Solution to its intended environments.
Summary
Project preparation
Kick-off meeting
Requirements gathering
Current state assessment
Operational impact review
Solution alignment workshop
Architecture and design guidance Microsoft Azure specifically for dev and test scenarios
Configure Microsoft Azure storage, networking, and VMs to support the solution
Optionally, connect to your existing network
Import and configure Microsoft’s library of automation IP
Validate the solution based on the scenarios identified in the test plan
Lead a solution walk through with your staff
Assist in transitioning solution to production
Key Activities
High level architecture diagram
Test plan
Work Products

9. Product Line Architectures Office 365 and Microsoft Azure
Deployment Models
Unsupported Design
Custom Design
Recommended
Practices
Product Line Architectures
Office 365 and Microsoft Azure
(Public Cloud)
Supported
Recommended
Cost
Complexity
Structured
Standardized
Key Concepts:
The circles can represent a number of scales: features, complexity, standardization, and so forth.
Supported: The most flexible, anything within the product support guidelines.
Recommended: More flexible on design options, but there are not recommendations to cover all aspects of the product.
Cloud: Cloud restricts the features that are available, but removes operations work.
A Good Example, Storage Design
Supported: Can be any type of storage except network-area storage, which is not supported.
Recommended: Recommendation is to not share storage (drives) with other applications.
Product-line architecture: Must be deployed on direct-attached storage, with just a bunch of drives (JBOD).
Standardized: Black box; you have no idea what the storage is other than a quota.

10. What is a Product-Line Architecture?
TechReady 16
5/27/2018
What is a Product-Line Architecture?
A product-line architecture (PLA) is a set of rules and architectural patterns that provide a method for predictable and supportable deployments.
The Infrastructure as a Service (IaaS) PLA fabric architecture includes the concepts of compute, storage, and network fabric layers.
© 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.

11. Who is the PLA for?
Organizations which fit in defined scale points as defined by each product
New deployments and upgrades from legacy solutions
Customers looking for reliability, stability, and supportability
For customer less than 5,000, we highly recommend Office 365.
For customers more than 300,000, PLA may work, but generally this scale should be closely evaluated to make sure they fit. In fact, generally speaking, the PLA is meant to scale for really large customers.
The second item means that all the intellectual property we’ve built is around legacy Exchange work. If they have a foreign platform, like Dominio, then we can still use the PLA for planning the Exchange infrastructure, but there are gaps in intellectual property that will require custom additions to the engagement.

12. PLA Attributes Rulebook
<Partner Name> evolves the PLA as we capture learnings from customer deployments and support incidents to continuously improve the architecture and our deployment practices.
The potential benefits of using the PLA 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 PLA delivers high quality deployment by following design principles to facilitate:
Performance
Scalability
Interoperability
Resilience
Manageability
Quality
Supportability
Disaster Recovery
Portability
Key Concepts:
These are the attributes the define the PLA. You could say that in order to deliver the bottom things (quality, performance, and so forth) the PLA is standardized design that incorporates the Microsoft Services Framework methodology.

13. Solution Alignment Workshop
TechReady 16
5/27/2018
Solution Alignment Workshop
Review the IaaS PLA Hybrid Cloud Addendum service description and service-levels objectives which should address this question: Does the PLA provide what I need?
Review the PLA Rulesets and identify any gaps or deployment blockers.
Develop a remediation plan to include specific activities, resources, and timelines.
Decide if the PLA is right for your organization.
Solution alignment workshop (SAW) in Exchange, Lync and SharePoint
© 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.

14. Hybrid Cloud Overview Available to Partners Workload Mobility
Common User Experience
Cloud Optimized Services
Consistent
APIs
Common Toolsets
Available to Partners
Workload Mobility
Public
Private
Hosted

15. Architecture Overview
Fabric
Fabric Management
IaaS Services
Platform as a Service (PaaS) Services
Software as a Service (SaaS) Services
Azure VPN
Service
Provider
Foundation (
Service Provider Foundation (SPF) )
Enterprise Datacenter
Computer
Storage
Network
Microsoft Azure
PaaS Services
SaaS Services
Office
365
Microsoft Hosting Partner
App
Controller
Customer Hybrid Infrastructure

16. Discussion: Your Requirements and Constraints
<This section of the presentation describes the potential Hybrid Cloud project scope options. Be sure to indicate that the Solution alignment workshop will explore these in detail to help with decision making.>
Discussion: Your Requirements and Constraints
Microsoft Azure Fabric
Compute
Storage
Network
Identity
Your specific scenario
What app workload?
What environments?
Developer managed or IT managed?
Solution components
Self-Service
Management
Automation

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

18. 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
Steering committee meetings
Internal customer communication

19. Change Management
<Define how changes to the process will be managed.>
The activities below shall 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

20. Risk Management
<Define and discuss key risks and address how they will be managed.>
The activities below shall 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

21. Issue Management
<Define how issues arising during the project will be managed.>
The activities below shall 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

22. Key Events Timeline
<Update to fit an appropriate timeline for the engagement.>
Engagement Kickoff
Solution training for IT staff and handover to operations
Phase 3
Phase 2
Phase 1
Solution Alignment Workshop
2-3 days
Build
Validation and solution walk through
Assist in transition to operations
One day
Solution Alignment Workshop
IaaS fabric architectural patterns
Infrastructure management
Service delivery
Phase 4
Available for developer usage
Phase 5

23. Delete this row for Basic SKU
Work Products
<List all key deliverables. These are sample deliverables. Edit as needed.>
Phase
Work Product
Description
Date
Plan
High level architectural design
The high level architecture is typically documented in 1 Visio drawing, comprised of 1-4 pages illustrating network connectivity, Azure design, and the app’s lab deployment model
Test plan
The test plan is typically comprised of an Excel workbook listing <=5 test cases, expected results, and observed results
Deploy
Lab operations guide
The lab operations guide is typically provided as a Word document containing 5-10 sections. Each section represents a common lab task and includes a series of screenshots illustrating recommended practices for the task and <=125 words of explanatory text.
Delete this row for Basic SKU

24. Roles and Resources
<Distinguish between <Partner Name>, 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.
<Partner Name> Project Manager
Primary point of contact for <Partner Name> 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 Name> Architect
Primary technical point of contact for the team that is responsible for technical architecture.
<Partner Name> Subject Matter Expert
Primary technical point of contact for the team that is responsible for technical design and implementation.

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

26. Questions?

27. Contact
Name
Title
Phone
<Partner Name> website link