Software Assurance Planning Services

1. Software Assurance Planning Services Partner Training Module 2: Voucher Life Cycle Steps, Conducting the Planning Services Engagement, and Getting Paid July, 2013

2. The purpose of this partner training The purpose of this 2-part partner training series is to provide Microsoft partners who are enrolled in the Software Assurance Planning Services program, or who are considering enrolling, with important program value and execution guidance, as well as clarify the voucher life cycle and the various process steps associated with Microsoft customer’s use of their Software Assurance Planning Services benefits.

3. Training Agenda for Module 2 • Customer eligibility and access to their PS benefit • Voucher creation • Reserving a voucher • Conducting the engagement and scope • Required deliverables • Redeeming a voucher • Getting paid: creating payment requests in SAVB • Review & resources • Appendix

4. Customer eligibilityand access to their PS Benefits Volume Licensing Service Center (VLSC) How to Manage Software Assurance Benefits - Video Instruction for Customers Point system determines PS days Watch Steps 1 & 2 of the Voucher Life Cycle Videos located here!

5. Watch Steps 1-2: Voucher Life Cycle Videos Voucher creation (Customer) in VLSC

6. 5 important facts about Vouchers • A voucher’s lifespan is 180 days from the date of creation in VLSC. • If a Customer’s enrollment expires before the voucher’s expiration date, the voucher is still valid up to it’s own expiration date. • If the enrollment is still active when a voucher expires (the voucher has not been used), the days will return to the enrollment’s available pool of days (Planning Services remaining days). If the enrollment has already expired when the voucher expires, the days are lost. • Assigned Vouchers should be reserved in VVR as soon as possible to ensure that it is not reserved by another partner. (Note that you can change the engagement start and end dates after a voucher is reserved.) • Partners must reserve the voucher, deliver the engagement, and redeem the voucher in VVR prior to the stated expiration date of the voucher.

7. Reserve the voucher (Partner) in VVR Access to VVR and User Authentication Align text to upper left corner User is associated to Location in MPN • User has 1 of the 6 MPN Program Contact Roles: • Primary Program Contact • Executive Contact • Sales & Marketing Contact • 1st Technical Contact • 2nd Technical Contact • 3rd Technical Contact If both of these criteria are met, a User may log into http://vvr.microsoft.com using their Microsoft Account (formerly known as “WLID”)

8. Watch Step 3: Voucher Life Cycle Videos Reserve the voucher (Partner) in VVR https://vvr.microsoftcom

9. Server & Tools Business (STB) Conduct the engagement PVDPS Visit each of the Planning Services site to enhance and streamline your engagement process. SA Planning Services Partner Portal SSDPS AZDPS Microsoft Office Division (MOD) DTDPS DDPS L&EDPS SDPS • Customer Program Overview/ Presentation • Pre-Engagement Questionnaire • Customer Fact Sheets • Sample WO/SOW’s • Agendas & Labs • Delivery Guides • Required Deliverables

10. Conducting the engagement Look for options within each PS offering Example: DDPS Options • Office 365 FastTrack Pilot (3-days) • Windows 8 & Office 2013 deployment planning workshops (1, 3 or 5 days) • Windows 8 Core Jumpstart Proof of Concept (5, 10 or 15 days) • Windows 7 & Office 2010 deployment planning workshops (1 – 15 days) • Windows 7 & Office 2010 Core Jumpstart Proof of Concept (3, 5 or 10 days) SA Planning Services Partner Portal

11. Scope limitations In Scope: The Plan for a deployment, upgrade or migration • Out of Scope: • Support of existing systems • Implementation of recommendations • Industry regulatory compliance requirements • Deployment of any products into the production environment • Review of current operational process • Customer development • Modification or stabilization of a current environment • Application packaging/sequencing • Formal training • Disaster recovery and business continuity planning • Providing economic justification for the new solution • Custom image creation

12. After delivery of the engagement Redeem Prepare Customer Deliverable Navigate to the VVR tool Upload deliverables and REDEEM vouchers within 60 days following the engagement Completion Report Review your Required Deliverables Completion Report Infopath Form https://vvr.microsoft.com

13. The Completion Report Infopath form https://msftxdps.com/SitePages/template.aspx

14. Watch Step 4: Voucher Life Cycle Videos Redeem the voucher (Partner) in VVR 1 2 • https://vvr.microsoft.com/ 3 4

15. Redeem the voucher (Partner) in VVR 5 6

16. Getting paid Four Important Facts about the SAVB tool Global Admins register each PS offering once at https://channelincentives.microsoft.com/home.mvc/savb You must have at least one voucher already in REDEEMED status in VVR to register in SAVB for the 1st time. SAVB only displays REDEEMED vouchers. It does not display vouchers that are still in Reserved status in VVR. Partners create Payment Requests in the SAVB toolto get paid. SAVB is not the same as VVR.

17. Getting ready to use SAVB Assign your Vendor ID to your Location (in SAVB) Obtain a New Vendor ID from Microsoft (NVA process) Register your Planning Services Program (in SAVB) SA Planning Services Partner Quick Start Guide SAVB Partner User Guide

18. Watch Step 5: Voucher Life Cycle Videos Create a Payment Request in SAVB https://channelincentives.microsoft.com

19. Create a Payment Request in SAVB The information in your Company invoice must match what is in the Payment Request!

20. Your homepage in SAVB

21. Module 2 - In Review • Planning Services is on-site planning support for a deployment, upgrade or migration. It does not cover actual deployment work. • Customers create PS vouchers in 1, 3, 5, 10 or 15 day increments in VLSC. A voucher is “assigned” to a customer employee. Vouchers live for 180 days. • Customers find partners in the PS Provider Directory. • There are multiple engagement options under each Planning Services offering. Explore them! • PS Partners reserve and redeem vouchers in VVR. • Vouchers must be reserved before the engagement start date. • An engagement must be complete and customer deliverables delivered prior to redemption of a voucher. • When redeeming, partners must upload the two required deliverables. • PS Partners submit Payment Requests through the SAVB tool.

22. Resources

23. Resources

24. Thank you

25. Appendix

26. Step 7a: First-time Registration in SAVB This step is only required if the voucher that you redeemed was your organization’s first redeemed voucher for a Planning Services Program SAVB is a unique system, separate from VVR, with a one-time requirement to “register” your organization and each of your voucher programs in SAVB. The registration cannot occur for a program until an Org has at least one voucher redeemed for that program in VVR SAVB only displays vouchers that have been redeemed in VVR. SAVB does not display vouchers that are still in “reserved” status in VVR. Please refer to the SAVB Partner User Guide for these steps as well as screenshots of this process.

27. Step 7b: Obtain a New Vendor ID This step is only required if you don’t have a vendor ID setup and mapped for your location ID for another Planning Services Program in SAVB Microsoft will automatically initiate a New Vendor ID Request for each new country that registers in SAVB You can use the same bank account for locations in different countries as long as those countries are located in the same Microsoft Company Code If you don’t want to create a new vendor ID for a new location, please let us know and we will cancel the NVA

28. Step 7c: Assign Vendor ID This step is only required if this is your first time invoicing this location ID under this program in SAVB. If you have never invoiced the location under any program in SAVB, then you will need to complete step 7b to create a new vendor ID before assigning your voucher If you have invoiced the location under a different program in SAVB, that vendor ID will be mapped and then you can assign your vendor ID to your location ID