1 / 23

License Mobility Process Hosting Services Provider team

License Mobility Process Hosting Services Provider team. 12/4/2012. Deck Scope. The purpose of this deck is to educate the MSFT Hosting community (MSFT Internal and Hosting Partners) about License Mobility and SALs for SA, using Lync examples, describing: What it is How it works

zahi
Download Presentation

License Mobility Process Hosting Services Provider team

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. License Mobility Process Hosting Services Provider team 12/4/2012

  2. Deck Scope • The purpose of this deck is to educate the MSFT Hosting community (MSFT Internal and Hosting Partners) about License Mobility and SALs for SA, using Lync examples, describing: • What it is • How it works • What resources are available • For License Mobility questions, please email LMobASK@microsoft.com(or “LM ASK”)

  3. License Mobility Defined With License Mobility through Software Assurance, customers can deploy certain server application licenses purchased under their Volume Licensing agreement in an Authorized Mobility Partner’s datacenter. License Mobility applies to single tenant deployments, SALs for SA must be acquired for multi-tenant deployments. In each case, Customer must maintain Server and CALs under SA. “License Mobility” Single-Tenant Hosted Deployment (i.e. Lync Server 2013) Move servers to Hosting Service Provider’s data center at no additional cost. “SAL for SA” Multi-Tenant Hosted Deployment (e.g., Lync Hoster Pack) Hosting Service Provider purchases SALs for SA on behalf of the customer.

  4. License Mobility - Customer Obligations • Must have Active Software Assurance - All licenses used to run and access licensed software, such as server licenses, processors licenses, CALs, External Connector (EC) licenses, and server management licenses require active Software Assurance coverage. • Must use Approved Partner - Customers can exercise License Mobility through Software Assurance rights only with Authorized Mobility Partners. • Customers need to contain instance(s) of software within a single cloud server farm at the Authorized Mobility Partner’s data center. • Customers need to maintain eligible licenses on the Authorized Mobility Partner’s shared servers for a minimum period of 90 days. After the 90-day period, a customer can move the licensed software back to their premise or to another Authorized Mobility Partner’s server farm.

  5. License Mobility Process Responsibilities Hosting PartnerResponsibility Customer Responsibility Microsoft Responsibility • Sign Mobility Addendum to SPLA Agreement • Determine eligibility and license position • Certifies partner to offer License Mobility through Software Assurance • Provide link to mobility form for customer to complete • Choose eligible License Mobility partner • Confirms customer eligibility to Service Provider customer and partner • Assist Microsoft in good faith to investigate non-compliance • Submit License Mobility verification form to Microsoft • Provide explanation of denial within 10 days of application receipt

  6. License Mobility Verification Form Mythbuster #1: LM Verification form does not track CALs North America form: http://www.microsoftvolumelicensing.com/Downloader.aspx?DocumentId=5900 Mythbuster #2: LM compliance is an Account team (VL) responsibility – Not HSP’s

  7. Customer Verification Data Tracker • 52 Approvals, 15 rejections (as of 12/2/12) • 7 Customers with Lync submissions • For updated list of all customer LM Mobility submissions, please see: HSP Answerbank http://sharepoint/sites/wwoc/licensing/Lists/SPLA%20Answer%20Bank/DispForm.aspx?ID=242&ContentTypeId=0x0100FC15AFB66E5A404185372602C2877DB1

  8. PUR language detailing License Mobility For list of product eligibility (Oct 2012), see appendix A

  9. Questions and Answers • Does Hosting Partner enroll as an authorized LM partner, or the LAR? • The partner who signs the SPLA agreement, typically the Hosting Partner. The LAR is not required to enroll as an authorized License Mobility partner. • Who is eligible to use License Mobility through Software Assurance? • Any Microsoft Volume Licensing customer who has eligible application server licenses covered with active Software Assurance may elect to use License Mobility through Software Assurance. • These include Microsoft Enterprise Agreement (EA) and Microsoft Open Value Agreement, where Software Assurance is included, and other Volume Licensing programs where Software Assurance is an option such as the Microsoft Select Plus Agreement. • More information is available on the Microsoft Partner Network Software Assurance page at https://partner.microsoft.com/licensing/. Customers can find information on the Microsoft Volume Licensing Software Assurance page at http://www.microsoft.com/licensing/software-assurance/license-mobility.aspx

  10. Questions and Answers, II • Is there a validation process for customers to use License Mobility through Software Assurance? • Yes. A simple customer license validation process began in late 2011. • Customers will need to choose an authorized partner for License Mobility through Software Assurance. • Once they select an Authorized Mobility Partner, the customer fills out a license validation form available on the Microsoft Volume Licensing page at www.microsoftvolumelicensing.com. • Does End User Customer have to show License Mobility approval before the Hosting Partner begins service? • No. The End User Customer may deploy in Service Provider’s Cloud immediately. • The End User Customer has 10 days to submit a license Mobility Verification form. • Microsoft will verify eligibility for License Mobility within 10 days of receiving the form. • If rejection occurs, what is language around next steps? Timeline? • Microsoft will inform the customer and the Authorized Mobility Partner and channel partner of record of the validation results, including why the verification was not granted. The customer can make the necessary revisions and resubmit the form as many times as required.

  11. Questionsand Answers, III • Is the Hosting Partner notified of the quantity of CALs the end user customer is approved to move? • No. The quantity of servers is communicated, but not the quantity of CALs. This information is not captured on the License Mobility Verification form. • When does a customer need to submit an updated License Mobility Verification form? • Reapplication is required when the End User Customer wants to move from one Authorized Mobility Partner/Hoster to another, or when they renew their VL or SA. • Where do customers get the Validation Form and do they send it to the Regional Operations Centers (ROCs) when they complete it? • The form is available on the Microsoft Volume Licensing page at www.microsoftvolumelicensing.com or on the Partner’s website. • The customer will complete the form and submit it to their channel partner or Microsoft account manager. • The partner or account manager will submit the form to the Microsoft Regional Operations Center.

  12. Questions and Answers, IV • How is the shared infrastructure platform licensed? • The Windows Server component is licensed through the service provider via SPLA. • Does License Mobility through Software Assurance apply to multi-tenant applications delivered as a service? • No. A Hosting partner must acquire Subscriber Access Licenses (SALs) for SA. • SALs for SA provide a way for customers to recognize license investment if they want to have licenses delivered as a multi-tenant service. • A customer does not need to submit a License Mobility Verification form in this scenario. • Can a customer mix VL and SPLA? • Yes, but they cannot mix for one product SKU. • (Example: Lync Standard can be VL and Lync Enterprise Plus can be SPLA)

  13. Use Case #1: Improperly Licensed End User Customer applies for License Mobility approval, but is denied. • Customer and SPLA Hosting Partner receive rejection and explanation from MSFT Regional Operating Center within 10 days of receipt. • Customer has three options: • Amend VL and reapply • Discontinue Hosted Service • Purchase licenses from SPLA partner, if product is not licensed via VL

  14. Use Case #2: Growing Customer End User Customer is approved for 500 users, but grows to 800 users within the first year. This is a sales opportunity, but not a License Mobility issue, since CAL quantity is not included in the LM verification form. If Open/VL: • Must acquire additional licenses before providing service on additional users. If EA: • At VL anniversary, End User Customer trues up VL to cover 800.

  15. Use Case #3: Declining Customer End User Customer is approved for 800 users, but declines to 500 users within the first year. Not applicable. Adjusting CAL license quantities falls outside the scope of License Mobility.

  16. Use Case #4: Additional SKU Customer is properly licensed with Core Cal (covering IM/P Lync), but wants conferencing and enterprise voice. Two options: • Customer can acquire additional licenses under VL (Plus CAL). • SPLA partner can acquire Lync Enterprise Plus SAL per user under SPLA for the benefit of the customer.

  17. Use Case #5: Multi-Tenant Lync Customer maintains Lync CALs and wants to deploy with Hosting Partner’s Multi-tenant environment via Lync Hoster pack. Service provider purchases appropriate SALs for SA: • Standard SAL for SA (Provides Standard IM/P), or • Enterprise (Provides Standard IM/P & Enterprise/Conferencing functionality), or • Plus (Provides Standard IM/P & Plus/Voice functionality), or • Enterprise SAL for SA and Plus SAL for SA (if they want Conferencing AND Voice functionality) The customer does not need to submit a license mobility verification form.

  18. Use Case #6: O365 E4 Customer with O365 E4 SKU, but wants deploy Lync through a Hosting Partner. Customer purchases/maintains: • O365 E4 for each user • Lync Server License: On Premise with SA • SQL Server License: On Premise with SA • Windows Server License: On Premise with SA Service Provider • Windows Server License through it’s SPLA contract Note: Customer may buy E3 and Lync Server Plus CAL (or SPLA Plus SAL), instead of E4

  19. Resources Email: LMobASK@miscrosoft.com All images include link to document

  20. License Mobility on MPN https://partner.microsoft.com/global/licensing/volumelicensesoftwareassurance

  21. Appendix A – LM Eligibility by Product (as of Oct 2012) For directional purposes only. Please verify latest PUR to validate eligibility.

More Related