Microsoft Licensing Guide for Frame
Ultimately, Frame customers are responsible for ensuring their compliance with Microsoft Licensing Terms and any other agreements pertaining to Microsoft.
This guide specifically covers Microsoft licensing from a Windows Operating System (OS) VM access perspective for use as a Frame workload VM. This does not include any relevant Windows endpoint device licensing, Microsoft Office/O365, or any other Microsoft or third-party software and/or subscription licensing that may be required.
This document is provided as-is for informational purposes only and may not reflect the most up-to-date requirements from Microsoft. The information in this guide is provided to help guide your authorized use of Microsoft products you are licensing; it is not your agreement with Microsoft. Frame customers are strongly encouraged to speak with their Microsoft representative to validate compliance.
Windows 10 and Windows 11
Deploying on Amazon Web Services (AWS)
To comply with Microsoft's licensing terms, all virtualized Windows desktops and applications deployed in AWS must run on Dedicated Instances. This applies to both Frame-provided and customer BYO images running Windows 10 or 11. The Dedicated Instance infrastructure ensures that each virtual machine runs in an isolated environment, meeting the requirements outlined in the Microsoft EULA. The AWS infrastructure must either be customer-managed (BYO) or Dizzion-provided (Complete customers only). Legacy Frame customers using Frame IaaS are not eligible.
Every user accessing a Windows 10 or 11 desktop or application must have a VDA (Virtual Desktop Access) entitlement.
Windows Activation via KMS or ADBA
When deploying BYO Windows 10 or 11 images, customers must configure an activation method to ensure compliance.
Activation Options:
- KMS (Key Management Service)
- KMS can be configured within the customer’s infrastructure or on a utility server. Frame virtual machines must have network access to the KMS server.
- ADBA (Active Directory-Based Activation)
- Recommended if KMS is not already in place. ADBA simplifies the activation process by leveraging existing Active Directory infrastructure.
If neither KMS nor ADBA is configured, Frame virtual machines may not activate properly, which can result in compliance issues.
Deploying on Nutanix AHV
In order to access a Windows 10/11 VM hosted on-premises by Nutanix AHV, the device used to access the Windows 10/11 VM or the user must have a Windows Virtualization Rights entitlement. This entitlement is included with the Microsoft licenses listed in the table below:
| Model | Microsoft License | How to Purchase |
|---|---|---|
| Per User | Windows Enterprise E3 Subscription License | Bring Your Own License |
| Windows Enterprise E5 Subscription License | ||
| Windows VDA E3 Subscription License | ||
| Windows VDA E5 Subscription License | ||
| Per Device | Windows VDA Subscription Licenses | |
| Windows 10 Software Assurance |
Only one of the licenses in the table above are required on either a per-user or per-device basis.
Microsoft 365 licenses that include Windows 10/11 Enterprise E3/E5 are only eligible for Windows Virtualization Rights entitlement if the user is the primary user of a device with a Qualifying Operating System.
Deploying on Microsoft Azure
In order to access a Windows 10/11 VM hosted in Microsoft Azure, the user must have a Windows 10/11 Multitenant Hosting Rights entitlement. This entitlement is included with the Microsoft licenses listed in the table below:
| Model | Microsoft License | How to Purchase |
|---|---|---|
| Per User | Windows Enterprise E3 Subscription License | Bring Your Own License |
| Windows Enterprise E5 Subscription License | ||
| Windows VDA E3 Subscription License | ||
| Windows VDA E5 Subscription License |
- Only one of the licenses listed in the table above are required on a per-user basis.
- Microsoft 365 licenses that include Windows 10 Enterprise E3/E5 are only eligible for Windows 10 Multitenant Hosting Rights entitlement if the user is the primary user of a device with a Qualifying Operating System.
Windows Server
Deploying on Nutanix AHV
In order to access a Windows Server (2012 R2, 2016, 2019) VM hosted on-premises on Nutanix AHV, the device used to access the Windows Server VM or the user must have both a Windows Server CAL (Client Access License) that matches the specific Windows Server OS version and a Microsoft RDS (Remote Desktop Services) CAL allocated.
| Model | Microsoft License | How to Purchase |
|---|---|---|
| Per User | Windows Server CAL + Microsoft RDS CAL | Bring Your Own License |
| Per Device | Windows Server CAL + Microsoft RDS CAL |
Only one set of licenses listed in the table above are required on either a per-user or per-device basis.
Windows Server CAL may already be included with your Windows Server OS (depending on edition). The above does not include any required Windows Server Standard Edition or Datacenter Edition core-based licensing when deploying Windows Server VMs on-premises. These must be purchased as well.
Deploying on Microsoft Azure, AWS, or GCP
In order to access a Windows Server (2012 R2, 2016, 2019) VM hosted in Microsoft Azure, the Windows Server license must be included as part of the cloud provider's hourly pay-go pricing. As an exception that applies only to Azure, if the customer already owns on-premises Windows Server licenses with active Software Assurance, they can leverage the Azure Hybrid Use Benefit to pay a lower hourly rate for pay-go Windows Server VMs.
In addition, each device used to access the Windows Server VM or each user must have a Microsoft RDS CAL allocated with active Software Assurance. Alternatively, customers can purchase a Microsoft RDS SAL (Subscriber Access License), which is only available on a per-user per-month basis.
| Model | Microsoft License | How to Purchase |
|---|---|---|
| Per User Per Month | Microsoft RDS SAL | Available for Purchase from Frame or Bring Your Own License |
| Per User | Microsoft RDS CAL with Software Assurance | Bring Your Own License |
| Per Device | Microsoft RDS CAL with Software Assurance |
- Only one of the licenses listed in the table above are required on either a per-user or per-device basis.
Purchasing Microsoft RDS SAL from Frame
Customers who elect to purchase Microsoft RDS SALs from Frame are still liable for ensuring compliance with Microsoft Licensing Terms for the relevant Windows Server product being accessed.
Using Frame Secure Anonymous Tokens
Customers using Secure Anonymous Tokens for user authentication in to Frame are required to maintain a detailed record of all unique users logging into Frame each month throughout the term of their Frame subscription. For these customers who purchased Microsoft RDS SALs via Frame, they are also required to send Frame the actual number of unique users who accessed Frame during the previous monthly billing cycle on a monthly basis for compliance purposes. The following information should be provided to Frame:
- Frame Customer entity name
- Monthly billing period (MM/DD/YY - MM/DD/YY)
- Number of unique users