Policies

1. Policies Software Assurance Planning Services

2. Agenda • Engagement Policies • Scope Policies • Voucher Policies • Resources

3. Engagement Policies

4. Delivery Qualified Onsite Interactive • Designed and advertised as onsite engagement • Up to 3 days of off-site delivery for distributed customer resources • Interactive consultative sessions • Unique deliverable • Competency-holding Partners • Registered and approved • Maintain competency status • Certified consultants

5. Engagement Length • Engagements can be 1, 3, 5, 10 or 15 days • Actual length varies by engagement • Engagements may not exceed 15 days • Vouchers should be reserved in VVR prior to the engagement start date • See guidance outlined across each program offering, and online FAQ for more information

6. Solution Planning Engagement must correspond to featured products for the offering Engagements may include a limited amount of time for secondary product if it directly supports the Deploy, Migrate, or Upgrade plan Planning Services days can be used across multiple offerings or programs only in cases where each voucher represents a complete, self-contained planning services engagement and a deliverable

7. Delivery Framework

8. Engagement Outcomes • Each engagement has two required deliverables • Planning Services Completion Report • Customer Planning Deliverable • Examples of Customer Planning Deliverable include: • Findings & Recommendations • Vision & Scope • Solution Brief • OAI Report • Custom Plan • May include other optional deliverables, such as labs & slide decks • Must align with products represented under each program (e.g. no Exchange deliveries under DDPS)

9. Scope Policies

10. The primary purpose of a Planning Service engagement is to help customers create a deployment, upgrade, or migration plan for a given product

11. Engagement High Level Scope • All Planning Services deliveries must meet the following criteria: • A Planning Services deliverable must be furnished to the customer • Planning Services days may only be applied toward the creation of the Required Deliverables and optional elective activities directly associated with creation/presentation of deliverables • Deliverables MUST reflect number of days charged to Microsoft (e.g. no 1-day deliverable for 15 days of planning effort) • For more details please refer to the FAQ

12. Scope Highly prescriptive, planning-only engagements with service levels of 1, 3, 5, 10, or 15 days DDPSWindows Office Pro PlusO365 Plan Deliverable Limited to products listed on right Limited outcome (Deploy/Upgrade/Migrate) Est. 1-3 Days (5 for larger organizations) Invoice w/ Completion Report (est. 15 min) Elective Activities Must Directly Support Primary Deliverable SDPSSharePoint SharePoint OnlineO365 L&EDPSLync Server Exchange Server Exchange OnlineO365

13. Scope (cont…) PVDPS DTDPSVisual Studio 2012 Plan Deliverable Limited to products listed on the right Limited outcome (Deploy/Upgrade/Migrate) 3-15 days, depending on engagement Invoice w/ Completion Report (est. 15 min) Elective Activities Limited training through DTDPS and AZDPS SSDPSSQL Server 2012SQL Server 2008 R2 AZDPSWindows Azure

14. Other Out of Scope Activities Configuration General Training Deployment Modification Program Documentation Remediation Optimization Detailed Design Development Implementation Recovery Compliance Staff Augmentation Support Image Creation Disaster Recovery Utilization Testing Stabilization

15. DDPS + Jumpstart • At least one DDPS component: • Deployment Planning • Jumpstart Core PoCs • Office 365 FastTrack Pilot Jumpstart Non-Core PoC’s or 5-day MAAP PoC only supported when delivered with a Deployment Planning or Jumpstart Core PoC Primary Customer Deliverable based on the DDPS Engagement Findings and Recommendations orJumpstart Core PoC templates • Not supported: • Non-Core PoCs delivered as a stand-alone engagements without prescriptive deliverable for how to deploy Windows or Office • Engagements performed during product pre-sales or pilot phase (exception for O365 pilots)

16. Voucher Policies

17. Vouchers may only be applied toward the creation of a plan that directly influences an increase of deployed server or seat counts for the products featured within each Planning Services offering

18. Distributed Organizations Vouchers from parent-level organizations can be used at subsidiaries, divisions, or organizations (and vice versa) provided each is legally connected Permission must first be obtained for each customer by the customer’s internal SA Benefit Administrator To request permission send mail to the corresponding program help alias Combining multiple, not legally-connected vouchers is prohibited

19. Voucher Stacking Custom duration engagements Multiple 15-day engagements (up to 60 days per offering) Engagements over 15 days May be performed for each customer, but only in cases where a completely different division or product deployment is involved Must be submitted through the field to the Planning Services team using an internal exception request process May be created up to a max of 15 days per offering

20. Consultant Time One consultant per engagement OK to use your own team and resources Subcontractors must comply with all guidelines and policies

21. Voucher Expiration • Vouchers must be reserved, delivered, and redeemed in VVR prior to the stated expiration date found on the voucher in VVR • Vouchers in the Assigned status have a lifespan of 180 days from the voucher creation date, regardless of the expiration date of the customers enrollment • If the enrollment is still active when a voucher expires, the days will return to the enrollment’s available pool of days • If the enrollment has expired when the voucher expires, the days are lost and cannot be restored or applied towards a new enrollment

22. Resources

23. Resources

24. Thank you