#DIFFERENCE BETWEEN RIGHT TO USE LICENSE AND HOSTING SOFTWARE#
#DIFFERENCE BETWEEN RIGHT TO USE LICENSE AND HOSTING LICENSE#

#DIFFERENCE BETWEEN RIGHT TO USE LICENSE AND HOSTING LICENSE#

Under MicrosoftРІР‚в„ўs new policy, for a customer to move a workload with an instance of Windows Server to VMware Cloud on AWS, a new license to Windows Server should be purchased via VMwareРІР‚в„ўs SPLA on a per host, per ESXi cluster basis.

#DIFFERENCE BETWEEN RIGHT TO USE LICENSE AND HOSTING SOFTWARE#

We understand Microsoft to have taken the position that a Windows Server license purchased by a customer on or after Octounder Volume Licensing agreement has no License Mobility and cannot be deployed in VMware Cloud on AWS, regardless of the product edition or whether the customer purchased Software Assurance. Customer renews subscription licenses in a subsequent EA contract or acquires new perpetual licenses in a subsequent EA contract on or after October 1, 2019.Customer upgrades an existing installation using a product version(s) released on/after October 1, 2019.Customer acquires new licenses on or after October 1, 2019.* The license date becomes effective in the following scenarios: OR customer does not have any Windows Server licenses and wants to have them on VMware Cloud on AWS hosts.Р”В¬ustomer must purchase new Windows Server licenses through VMware under VMware and Microsoft SPLA. Р”В¬ustomer acquires Microsoft Windows Server licenses and wants to move to VMware Cloud on AWS Customer ScenarioР”В¬ustomer owns licenses to Microsoft Windows Server 2019 or previous versions and wants to move to VMware Cloud on AWS.Р”В¬ustomer can leverage existing licenses (Bringing Your Own Licenses (BYOL). Table 1 summarizes our understanding of changes to Windows Server licensing. VMware has a SPLA with Microsoft and is now working through pricing and packaging details for selected Microsoft products, with details to be available soon.Р”В¬onsiderations for licensing Windows Server on VMware Cloud on AWS.

Instead, to provide access for customers to some of these products, including Windows Server, the hosting service must utilize a Services Provider License Agreement (SPLA) with Microsoft.

Microsoft has identified certain products as not eligible for BYOL.

Active Software Assurance is now required for all Microsoft products (with License Mobility through Software Assurance ) when BYOL to VMware Cloud on AWS is considered.

We see two key elements associated with these changes: We believe that these changes in the Microsoft licensing terms primarily affect customers wanting to use licenses purchased under Volume Licensing agreements with Microsoft when migrating Microsoft workloads to VMware Cloud on AWS (often referred to as Bringing Your Own Licenses or РІР‚СљBYOLРІР‚Сњ). What follows are some observations from VMware that may be helpful to enterprises looking to move Microsoft products to the VMware Cloud on AWS hosted service. Although we have reviewed MicrosoftРІР‚в„ўs published comments concerning the changes, VMware is not authorized to speak for Microsoft or make representations on its behalf. These changes are likely both to concern and to influence customers considering whether to move Microsoft workloads to dedicated hosted cloud services including VMware Cloud on AWS.

On OctoMicrosoft announced significant changes to the licensing terms for its products deployed on dedicated hosted cloud services. Are you thinking of migrating your Microsoft workloads to VMware Cloud on AWS? This blog gives you an overview of VMwareРІР‚в„ўs understanding of some elements of the Microsoft licensing changes that are likely to affect you if you do make the migration with VMware Cloud on AWS.

Difference between right to use license and hosting