SPLA Licensing Overview Introduction to the Services Provider Licensing Agreement

Agenda What is SPLA SPLA Licensing Models SPLA vs Traditional VL SPLA Overview SPLA Reporting SPLA Licensing Models Windows 2016 Leveraging Customer Owned Licenses Leveraging Datacenter Providers HPE SLMS Hosting Q&A

What is SPLA? The Service Provider License Agreement (SPLA) allows an organization to license Microsoft products and use them to provide software services to its customers. All products that are required to support the service provided to customers, must be licensed via SPLA (this includes backend SQL databases) Service Provider must maintain day to day management of this environment Types of Partners that typically enter into SPLA Web Hosters Application service providers Messaging and collaboration service providers (hosted email) ISVs w /hosted apps Outsourcers Platform infrastructure providers Infrastructure as a Service providers

Traditional* VL (Open, MPSA, EA) SPLA vs Traditional VL Traditional* VL (Open, MPSA, EA) SPLA Perpetual, upfront cost End Customer is the licensee Installed on-premise or with an outsourcer on dedicated physical machines Used for own internal use Non-perpetual, monthly reoccurring cost, pay on backend Service Provider is the licensee, but does not own the licenses Software is installed in a datacenter managed by the Service Provider and accessed remotely Used to provide a service to external users * There are terms that allow when traditional licensing to be used in certain circumstances

SPLA Overview Monthly “pay as you go” model No upfront commitment or purchase Can report zero usage or any volume of usage for first 6 months 7th month onward, must report equivalent of $100 USD to remain in the program One price for all Must be a registered member of the Microsoft Partner Network to enroll in the program 2 commercial types Corporate Academic End customer enrollment required when submitting usage >1k/month for a specific organization Can use for internal use if less than 50% of usage reported for that specific product

SPLA Reporting IMPORTANT: Monthly Usage Reports Access Service Provider is required to submit monthly usage, actual or zero, to HP by the 10th of each month, reporting the previous month’s usage. Usage should be submitted via OLS https://h40095.www4.hp.com/Phoenix/Welcome.do Access Log onto site using your email and PW Not sure of PW – select Forgot Password If you do not have access, contact hpeslmshosting@hpe.com

SPLA Licensing Models Universal Terms Host/Guest SAL Processor Core One license is required for each physical processor on a licensed server Each license permits use of one running instance of the server software in one OSE SAL for Server Software Must acquire a SAL for each user or device authorized by the customer to access the server regardless of actual access SAL for Management Servers Must acquire a SAL for each OSE or each user of OSEs Customer uses the software to Manage SAL for Desktop Applications Customer must acquire a SAL for each user or device authorized by Customer to access the desktop application software regardless of actual access. Customer must choose either licensing by physical core or virtual OSE. Physical Core on server The number of licenses required equals the number of physical cores on licensed server multiplied by the applicable core factor Virtual OSE The number of licenses required equals the number of virtual cores in the virtual OSE, subject to a minimum license requirement per virtual OSE Host/Guest requires both host licenses and guest licenses, as well as SALs for users accessing certain guest software functionality. Host software required for each physical processor Customer may run guest software only in a virtual OSE hosted using the hyper-v functionality of the MSFT Cloud Platform Suite.

Windows Server Licensing Windows Server 2016 Datacenter Edition Windows Server 2016 Standard Edition VMs & Hyper V containers Unlimited 1 Windows Server Containers Unlimited Unlimited Server: license all physical cores 8 core min/proc 1 proc 2012 R2 price = 8 core 2016 price Incremental cores licensed in packs of two Standard Edition Each coverage of cores entitles 1 instance  Nano Server install option  Infrastructure Software defined datacenter Base infrastructure services 8 cores min/proc 8 cores min/proc

Windows Server 2016 Datacenter Inventory the number of physical cores per server Minimum of 8 cores per processor (incremental cores in 2 core packs) Physical Cores per Processor 4 or less 6 8 10 12 Physical Processors per Server CORES REQUIRED TO BE LICENSED PER PROC Purchase additional cores in increments of 2 cores 1 8 8 8 10 12 2 16 16 16 20 24 3 32 32 32 40 48

Windows Server 2016 Datacenter Inventory the number of physical cores per server Minimum of 8 cores per processor (incremental cores in 2 core packs) Full coverage of cores on the server entitles 1 instance/Hyper-V container Physical Cores per Processor 4 or less 6 8 10 12 Physical Processors per Server CORES REQUIRED TO BE LICENSED PER PROC INSTANCES ENTITLED 1 8 8 8 10 12 Need to cover all cores again for 1 more instance 2 16 16 16 20 24 3 32 32 32 40 48

Containers and Virtual Machines Deployment options suited to many scenarios Server App A Bins Libraries Guest OS Hypervisor Virtual Machine App B Guest OS Containers in VMs: By combining containers with VMs users can deploy multiple, different VM operating systems, and inside, deploy multiple containers within those guest OSs. By combining containers with VMs, fewer VMs would be required to support a larger number of apps. Fewer VMs would result in a reduction in storage consumption. Each VM would support multiple isolated apps, increasing overall density. Flexible: Running containers inside VMs enables features such as live migration for optimal resource utilization and host maintenance.

Leveraging Customer Owned Licenses in Hosted Environments Dedicated, Hybrid, & Shared D H S Dedicated means both the host server(s) and VMs are dedicated to that customer SPLA can be used or end customer owned licenses can be used - there can also be a mixed, but not of the same product End customer owned licenses do not require software assurance Hybrid generally means the same environment is running both on end customer premise and in your cloud Key options to consider: SAL for SA License Mobility SPLA In a multi-tenant (shared) environment, there will always be some aspect of SPLA Opportunity to leverage customer owned licenses (for qualified products) through License Mobility

Customer Owned Licenses in Dedicated Environments The end customer is responsible for all software; while SP maintains day to day management of the environment Can leverage customer owned licenses. They do not need software assurance (SA) because everything is dedicated to that organization D The end customer is responsible for the applications; however, the SP is responsible for the infrastructure. Dedicated means both the host server(s) and VMs are dedicated to that customer SPLA can be used or end customer owned licenses can be used - there can also be a mixed, but not of the same product End customer owned licenses do not require software assurance Can leverage customer owned licenses (No SA required) for the applications & the SP would license Windows via SPLA The end customer does not want to be responsible for any of the software. Can license via SPLA, the hardware can be on customer premise if SP maintains day to day management of the environment

Customer Owned Licenses in Hybrid Environments The SP offers a shared environment, end customer has same applications running on prem End customer should purchase the on-premise license with software assurance. The SP would run the same applications in the shared environment but report SAL for SA SKU when available H End customer wants to leverage existing VL in SP’s share infrastructure Hybrid generally means the same environment is running both on end customer premise and in your cloud Key options to consider: SAL for SA License Mobility SPLA The SP must provide the end customer with a dedicated virtual machine, and for qualified products the end customer can leverage License Mobility to leverage their existing license purchases. The Windows Server is always reported by the SP under SPLA

Customer Owned Licenses in Shared Environments End customer wants to leverage existing VL in SP’s share infrastructure S In a multi-tenant (shared) environment, there will always be some aspect of SPLA Opportunity to leverage customer owned licenses (for qualified products) through License Mobility The SP must provide the end customer with a dedicated virtual machine, and for qualified products the end customer can leverage License Mobility to leverage their existing license purchases. The Windows Server is always reported by the SP under SPLA

Leveraging a Datacenter Outsourcer SP may use Data Center Providers and/or Outsourcing Companies in the delivery of its software services to end users. SP may install the products on servers under the day to day management and control of Data Center Providers and Outsourcing Companies Dedicated Environment (Servers & VMs) Dedicated VM, shared infrastructure Infrastructure products must be licensed by the Data Center Provider SAL based products can be licensed by SP SP may license all products under their own SPLA Agreement

www.hpesparc.com For additional info, contact HPE SLMS Hosting at HPESLMSHOSTING@hpe.com Google+: HPESPaRC LinkedIn: HPESPaRC Twitter: @HPESPaRC © Copyright 2016 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.