AWS prescriptive-guidance documentation change
Summary
Updated Microsoft licensing guidance with significant restructuring. Changes include: updated product version years (2024) for Office/Visio/Project LTSC; expanded BYOL eligibility details for Microsoft 365/Office 365 on Amazon WorkSpaces; replaced SPLA BYOL section with notice of its deprecation after October 2025; added Windows 11 BYOL requirements; restructured Windows Server BYOL section with Amazon EVS details; added licensing optimization guidance (Optimize CPU, High Availability); updated License Mobility verification contact details.
Security assessment
The changes are purely administrative and procedural updates related to Microsoft licensing terms, product versions, BYOL eligibility, and migration guidance. There is no mention of security vulnerabilities, patches, security configurations, or security incidents. The updates focus on compliance, cost optimization, and legal licensing requirements.
Diff
diff --git a/prescriptive-guidance/latest/migration-microsoft-workloads-aws/licensing-microsoft-workloads.md b/prescriptive-guidance/latest/migration-microsoft-workloads-aws/licensing-microsoft-workloads.md index 4d1e18b87..2f24262a5 100644 --- a//prescriptive-guidance/latest/migration-microsoft-workloads-aws/licensing-microsoft-workloads.md +++ b//prescriptive-guidance/latest/migration-microsoft-workloads-aws/licensing-microsoft-workloads.md @@ -25 +25 @@ For more information about current Microsoft licensing terms for products purcha -License included refers to Amazon EC2 instances that include the cost of the license in the compute costs. For Microsoft server workloads, AWS currently offers Windows Server ([Amazon EC2](https://aws.amazon.com/ec2/instance-types/), [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2/dedicated-hosts/pricing/), [Amazon EC2 Dedicated Instances](https://aws.amazon.com/ec2/pricing/dedicated-instances/), [AWS Outposts](https://aws.amazon.com/outposts/)) and SQL Server Enterprise, Standard, and Web editions ([Amazon EC2](https://aws.amazon.com/ec2/instance-types/)). These server licenses are offered per vCPU per second with the pay-as-you-go model as a benefit of license included EC2 instances. If the EC2 instance is scheduled to stop, or scales up or down based on demand, you only pay for the licensing for the time the instance is running. With on-demand pricing there are no long-term commitments, which is ideal for future modernization plans. +_License included_ refers to Amazon EC2 instances that include the cost of the license in the compute costs. For Microsoft server workloads, AWS currently offers Windows Server ([Amazon EC2](https://aws.amazon.com/ec2/instance-types/), [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2/dedicated-hosts/pricing/), [Amazon EC2 Dedicated Instances](https://aws.amazon.com/ec2/pricing/dedicated-instances/), [AWS Outposts](https://aws.amazon.com/outposts/)) and SQL Server Enterprise, Standard, and Web editions ([Amazon EC2](https://aws.amazon.com/ec2/instance-types/)). These server licenses are offered per vCPU per second with the pay-as-you-go model as a benefit of license included Amazon EC2 instances. If the Amazon EC2 instance is scheduled to stop, or if it scales up or down based on demand, you only pay for the licensing for the time the instance is running. With on-demand pricing there are no long-term commitments, which is ideal for future modernization plans. @@ -29 +29 @@ License included is available for current and legacy versions with Amazon Machin -There are no software upgrade fees with the license included option. As soon as a new version of the product is released by Microsoft, the new version is made available in the Amazon EC2 console right away for no additional cost above the current license included costs. Most importantly, AWS is responsible for the licensing compliance for license included EC2 instances. This can save a lot of time and effort for you because licensing compliance can be complex and difficult. +There are no software upgrade fees with the license included option. As soon as a new version of the product is released by Microsoft, the new version is made available in the Amazon EC2 console right away for no additional cost above the current license included costs. Most importantly, AWS is responsible for the licensing compliance for license included Amazon EC2 instances. This can save a lot of time and effort for you because licensing compliance can be complex and difficult. @@ -46,6 +46,6 @@ Office Professional Plus | Amazon WorkSpaces | 2019, 2016 -Office LTSC Professional Plus | Amazon EC2, Amazon WorkSpaces | 2021 -Visio LTSC Professional | Amazon WorkSpaces | 2021 -Visio LTSC Standard | Amazon WorkSpaces | 2021 -Project Professional | Amazon WorkSpaces | 2021 -Project Standard | Amazon WorkSpaces | 2021 -Remote Desktop Services SAL | Amazon EC2 | — +Office LTSC Professional Plus | Amazon EC2, Amazon WorkSpaces | 2021, 2024 +Visio LTSC Professional | Amazon WorkSpaces | 2021, 2024 +Visio LTSC Standard | Amazon WorkSpaces | 2021, 2024 +Project Professional | Amazon WorkSpaces | 2021, 2024 +Project Standard | Amazon WorkSpaces | 2021, 2024 +Remote Desktop Services SAL | Amazon EC2, Amazon WorkSpaces | — @@ -90 +90 @@ The Flexible Virtualization Program offered by Microsoft isn't available on AWS -Windows Server, Visual Studio, Microsoft Developer Network (MSDN), Windows desktop operating systems, Microsoft Office, and Microsoft 365 apps (formerly Office 365) don't have License Mobility rights granted to them in the Microsoft Product Terms, even if the licenses have SA or are active subscription licenses. As a result, bringing licenses for these products requires dedicated infrastructure: Amazon EC2 Dedicated Hosts, Amazon EC2 Dedicated Instances, VMware Cloud on AWS, and Dedicated Hosts on AWS Outposts. You must also follow other specific requirements to be eligible for BYOL to AWS. These requirements are a result of changes Microsoft made to the license terms for products without License Mobility when deployed on Listed Provider clouds, effective October 1, 2019. For more information, see [Updated Microsoft licensing terms for dedicated hosted cloud services](https://www.microsoft.com/en-us/licensing/news/updated-licensing-rights-for-dedicated-cloud) in the Microsoft documentation. +Windows Server, Visual Studio, Microsoft Developer Network (MSDN), Windows desktop operating systems, Microsoft Office, and Microsoft 365 apps (formerly Office 365) don't have License Mobility rights granted to them in the [Microsoft Product Terms](https://www.microsoft.com/licensing/terms/welcome/welcomepage), even if the licenses have SA or are active subscription licenses. As a result, bringing licenses for these products requires dedicated infrastructure: Amazon EC2 Dedicated Hosts, Amazon EC2 Dedicated Instances, Amazon Elastic VMware Service (Amazon EVS), and Dedicated Hosts on AWS Outposts. You must also follow other specific requirements to be eligible for BYOL to AWS. These requirements are a result of changes Microsoft made to the license terms for products without License Mobility when deployed on Listed Provider clouds, effective October 1, 2019. For more information, see [Updated Microsoft licensing terms for dedicated hosted cloud services](https://www.microsoft.com/en-us/licensing/news/updated-licensing-rights-for-dedicated-cloud) in the Microsoft documentation. @@ -109,3 +109 @@ Subscription licenses for products without License Mobility will lose BYOL once -Note: Products without License Mobility don't require active SA for BYOL on AWS, as long as the licenses meet the requirements above. - -As licensing can be complex, see the [Amazon Web Services and Microsoft FAQ site](https://aws.amazon.com/windows/faq/) to determine if your licenses are eligible for the BYOL to AWS option. If you don't find the information you need in the FAQ or are unsure where to start with migrating your Microsoft workloads to AWS, contact `[email protected]`. AWS has Microsoft workload and licensing specialists available to help make sure you have all the information that you need. +Products without License Mobility don't require active SA for BYOL on AWS, as long as the licenses meet the requirements above. @@ -115 +113 @@ As licensing can be complex, see the [Amazon Web Services and Microsoft FAQ site -Windows Server BYOL requires dedicated host tenancy (such as Amazon EC2 Dedicated Hosts and Dedicated Hosts on AWS Outposts) because Windows Server BYOL must be licensed by a physical core. +Windows Server BYOL requires dedicated host tenancy (such as Amazon EC2 Dedicated Hosts, Amazon Elastic VMware Service (Amazon EVS), and Dedicated Hosts on AWS Outposts) because Windows Server BYOL must be licensed by physical core. @@ -117 +115 @@ Windows Server BYOL requires dedicated host tenancy (such as Amazon EC2 Dedicate -#### BYOL for the Services Provider License Agreement (SPLA) +#### Microsoft 365 and Office 365 BYOL @@ -119 +117 @@ Windows Server BYOL requires dedicated host tenancy (such as Amazon EC2 Dedicate -The Services Provider License Agreement (SPLA) program was not affected by the October 1, 2019 [licensing changes](https://www.microsoft.com/en-us/licensing/news/updated-licensing-rights-for-dedicated-cloud) made by Microsoft. As a result, net new Windows Server licenses can be brought through SPLA for customers with their own SPLA licensing, without any purchase date or version restrictions. Any core or processor-based products licensed through SPLA require Amazon EC2 Dedicated Hosts, where user-based Subscriber Access Licenses (SALs) can be brought to shared-tenancy (default) EC2 instances. This is because the user-based SALs in SPLA are eligible for data center providers (DCPs) in the [Services Provider Use Rights (SPUR)](https://www.microsoft.com/licensing/spur). +Microsoft 365 and Office 365 are subscription licenses and are not eligible for License Mobility benefits. As a result, these products were impacted by the October 1, 2019 licensing changes from Microsoft and are not eligible for BYOL on AWS. The exception to this is on Amazon WorkSpaces offerings, where Microsoft allows BYOL of the Microsoft 365 apps for enterprise or business with the following eligible plans, effective August 1, 2023: @@ -121 +119 @@ The Services Provider License Agreement (SPLA) program was not affected by the O -###### Note + * Microsoft 365 E3/E5 @@ -123 +121 @@ The Services Provider License Agreement (SPLA) program was not affected by the O -Microsoft has [announced](https://blogs.partner.microsoft.com/partner/new-licensing-benefits-make-bringing-workloads-and-licenses-to-partners-clouds-easier/) that they will no longer allow SPLA BYOL on AWS or the other Listed Provider clouds after September 30, 2025. + * Microsoft 365 A3/A5 @@ -125 +123 @@ Microsoft has [announced](https://blogs.partner.microsoft.com/partner/new-licens -#### Amazon EC2 Dedicated Hosts + * Microsoft 365 G3/G5 @@ -127 +125 @@ Microsoft has [announced](https://blogs.partner.microsoft.com/partner/new-licens -Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2/dedicated-hosts/pricing/) include the following: + * Microsoft 365 Business Premium @@ -129 +126,0 @@ Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2 - * Pre-configured Amazon EC2 Nitro and Xen hypervisors with visibility into physical sockets and cores @@ -131 +127,0 @@ Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2 - * Multiple instance sizes within the same family supported on the same Dedicated Host (For the latest set of supported instance types, see [Amazon EC2 Dedicated Hosts](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-overview.html) in the Amazon EC2 documentation.) @@ -133 +128,0 @@ Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2 - * Automated management, auto-scaling, and instance placement control @@ -135 +130 @@ Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2 - * Ability to share a host across multiple AWS accounts +The following are also included in this update for BYOL on Amazon WorkSpaces: @@ -137 +132 @@ Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2 - * Integrated with [AWS License Manager](https://aws.amazon.com/license-manager/) for tracking license usage and management + * Microsoft Project licensed under Planner and Project Plan 3 or 5 @@ -139 +134 @@ Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2 - * Ability to maintain instance affinity to a host + * Microsoft Visio, licensed under Visio Online Plan 2 @@ -141 +136 @@ Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2 - * Automated host recovery + * Microsoft Teams, licensed under Microsoft Teams EEA, Enterprise, Essentials, or Premium @@ -143 +138 @@ Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2 - * Continuous monitoring with AWS Config + * Microsoft Power Automate, licensed under Microsoft Power Automate Premium @@ -144,0 +140 @@ Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2 + * Microsoft 365 app, licensed under Microsoft 365 Copilot @@ -148 +143,0 @@ Some key capabilities of [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2 -Because Windows Server BYOL requires dedicated infrastructure and physical core counts, Amazon EC2 Dedicated Hosts is a great option that can help you: @@ -150 +145 @@ Because Windows Server BYOL requires dedicated infrastructure and physical core - * Achieve significant savings +For confirmation on this, see the [Microsoft Product Terms for Amazon WorkSpaces Deployments](https://www.microsoft.com/licensing/terms/en-US/product/AmazonWorkspacesDeployments/EAEAS). @@ -152 +147 @@ Because Windows Server BYOL requires dedicated infrastructure and physical core - * Enable you to bring any Microsoft application to AWS, regardless of SA or License Mobility (subject to the October 1, 2019 purchase and version requirements) +#### Windows Desktop Operating System (Windows 11) BYOL @@ -154 +149 @@ Because Windows Server BYOL requires dedicated infrastructure and physical core - * Maximize the physical core licensing benefits of Windows Server Datacenter and SQL Server Enterprise editions +As a result of Microsoft's October 1, 2019 licensing changes, Windows Desktop OS BYOL on listed provider clouds, such as AWS, requires the following: @@ -156 +151 @@ Because Windows Server BYOL requires dedicated infrastructure and physical core - * Pay only per host, not per EC2 instance (This means that when you use dedicated hosts you can use the maximum number of instances available on the host without incurring any extra compute charges.) + * VDA E3/E5 user subscription license for each user with access to the virtual desktop instances @@ -157,0 +153 @@ Because Windows Server BYOL requires dedicated infrastructure and physical core + * Dedicated infrastructure, such as BYOL WorkSpaces, Amazon EC2 Dedicated Instances, Amazon EC2 Dedicated Hosts, Amazon Elastic VMware Service (Amazon EVS), or AWS Outposts @@ -161 +156,0 @@ Because Windows Server BYOL requires dedicated infrastructure and physical core -If you bring BYOL-eligible Windows Server licenses to Amazon EC2 Dedicated Hosts, you can license all physical cores (not vCPUs) of the host. For example, an R5 Amazon EC2 Dedicated Hosts has 48 physical cores. Bringing 48 cores of Windows Server Datacenter edition to an R5 Amazon EC2 Dedicated Hosts allows for as many EC2 instances to be deployed on the host as technically possible. Bringing 48 cores of Windows Server Standard edition allows up to two EC2 instances of any size on the host. @@ -163 +158 @@ If you bring BYOL-eligible Windows Server licenses to Amazon EC2 Dedicated Hosts -You can stack Windows Server Standard edition licenses to allow for additional EC2 instances on the same host, where all of the physical cores of the host licensed a second time allows for two additional EC2 instances (and so on). Licensing SQL Server Enterprise by physical core also requires that all physical cores of the host be licensed. This enables you to deploy the number of EC2 instances for SQL Server on the host equal to the number of physical cores licensed. For example, an R5 Amazon EC2 Dedicated Hosts licensed with 48 cores of SQL Server Enterprise allows you to deploy up to 48 EC2 instances running SQL Server on that host. If you bring BYOL-eligible Windows Server Datacenter and SQL Server Enterprise licenses and license the total physical cores of the host, you can see significant cost savings over license included for the same number and size of EC2 instances. This assumes the workloads can mostly fill the host and are running most of the time. For example, you could deploy 12 R5.2xlarge EC2 instances on shared-tenancy instances with license included Windows Server and SQL Server Enterprise BYOL with a total of 96 cores of SQL Server Enterprise required for licensing. However, if you deploy an R5 Amazon EC2 Dedicated Hosts (which can fit the same 12 R5.2xlarge EC2 instances), you can bring 48 cores of Windows Server Datacenter and 48 cores of SQL Server Enterprise BYOL-eligible licenses. You would not only save the Windows Server license included costs, but you would also only need to bring half the number of SQL Server Enterprise core licenses. +If using Microsoft 365 BYOL on Amazon WorkSpaces, VDA E3/E5 user subscription licenses (or VDA Add-Ons) are still required according to the Microsoft Product Terms. @@ -165 +160 @@ You can stack Windows Server Standard edition licenses to allow for additional E -BYOL on Amazon EC2 Dedicated Hosts is best for stable, predictable workloads where you can fill the host by at least 70 percent and where the workloads are running most of the time. To learn more about Microsoft Licensing on AWS, see [Microsoft Licensing on AWS](https://www.youtube.com/watch?v=8PM97sbg3n0) on YouTube and [Amazon Web Services and Microsoft Frequently Asked Questions](https://aws.amazon.com/windows/faq/) in the Microsoft documentation. +#### Services Provider License Agreement (SPLA) BYOL @@ -167 +162 @@ BYOL on Amazon EC2 Dedicated Hosts is best for stable, predictable workloads whe -## Mobilize +Effective October 1, 2025, Microsoft no longer allows BYOL of licenses purchased under the SPLA program on [listed provider clouds](https://www.microsoft.com/licensing/docs/view/Listed-Providers). As a result, the recommendation is to move to license included offerings available from AWS. @@ -169 +164 @@ BYOL on Amazon EC2 Dedicated Hosts is best for stable, predictable workloads whe -### AWS License Manager +#### Windows Server BYOL on Amazon EC2 Dedicated Hosts @@ -171,3 +166 @@ BYOL on Amazon EC2 Dedicated Hosts is best for stable, predictable workloads whe -As part of the mobilize phase for Microsoft licensing considerations, we recommend that you input the licenses you're planning to allocate to your workloads in AWS in [AWS License Manager](https://aws.amazon.com/license-manager/). License Manager is a free tool that makes it easier for you to manage your software licenses from vendors such as Microsoft, Oracle, IBM, and SAP across not only AWS but workloads on-premises or in other clouds, too. - -Inputting the Microsoft licensing you're bringing to AWS into License Manager will help you: +Windows Server BYOL is available for version 2019 or earlier with eligible licenses on Amazon EC2 Dedicated Hosts, Amazon EVS, Dedicated Hosts on AWS Outposts, Dedicated Host tenancy on bare metal (including Nutanix on EC2 (NC2) and Red Hat OpenShift (ROSA)). If you bring BYOL-eligible Windows Server licenses to Amazon EC2 Dedicated Hosts, you must license all physical cores (not vCPUs) of the host. For example, an R5 Amazon EC2 Dedicated Host has 48 physical cores. Bringing 48 cores of Windows Server Datacenter edition to an R5 allows for as many Amazon EC2 instances to be deployed on the host as technically possible. Bringing 48 cores of Windows Server Standard edition allows up to two Amazon EC2 instances of any size on the host. You can stack Windows Server Standard edition licenses to allow for additional Amazon EC2 instances on the same host, where all of the physical cores of the host licensed a second time allows for two additional Amazon EC2 instances (and so on). @@ -175 +168 @@ Inputting the Microsoft licensing you're bringing to AWS into License Manager wi - * Gain greater visibility and control over how software licenses are used and prevent misuse before they happen. +On Amazon EVS, Standard edition is not recommended due to having multiple hosts in a cluster, and instead Datacenter edition is recommended. For example, the minimum number of hosts on Amazon EVS is four `i4i.metal` hosts, each with 64 physical cores, totaling 256 cores. This configuration would require 256 cores of BYOL-eligible Windows Server Datacenter licenses, and it allows for unlimited virtualization for virtual machines running version 2019 or earlier. Because licensing can be complex, see the [Amazon Web Services and Microsoft FAQ site](https://aws.amazon.com/windows/faq/) to determine if your licenses are eligible for the BYOL to AWS option. If you don't find the information you need in the FAQ or are unsure where to start with migrating your Microsoft workloads to AWS, contact `[email protected]`. AWS has Microsoft workload and licensing specialists available to help make sure you have all the information that you need. @@ -177 +170 @@ Inputting the Microsoft licensing you're bringing to AWS into License Manager wi - * Save money with the maximum use of licenses, including how you track and manage licenses. +## Mobilize @@ -179 +172 @@ Inputting the Microsoft licensing you're bringing to AWS into License Manager wi - * Reduce the risk of noncompliance by enforcing license usage limits, blocking new launches, and using other controls. +### AWS License Manager @@ -181 +174 @@ Inputting the Microsoft licensing you're bringing to AWS into License Manager wi - * Increase your productivity by automating the placement, release, and recovery of hosts using host resource groups. +As part of the mobilize phase for Microsoft licensing considerations, we recommend that you input the licenses you're planning to allocate to your workloads in AWS in [AWS License Manager](https://aws.amazon.com/license-manager/). License Manager is a free tool that makes it easier for you to manage your software licenses from vendors such as Microsoft, Oracle, IBM, and SAP across not only AWS but workloads on-premises or in other clouds, too. @@ -182,0 +176 @@ Inputting the Microsoft licensing you're bringing to AWS into License Manager wi +To learn more about License Manager, see [Working with AWS License Manager](https://docs.aws.amazon.com/license-manager/latest/userguide/using-license-manager.html) in the License Manager documentation. @@ -183,0 +178 @@ Inputting the Microsoft licensing you're bringing to AWS into License Manager wi +### Licensing optimization @@ -184,0 +180 @@ Inputting the Microsoft licensing you're bringing to AWS into License Manager wi +[Optimize CPU](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-optimize-cpu.html) is an Amazon EC2 feature that allows you to turn off simultaneous multithreading (SMT) or hyperthreading or decrease to a specific number of vCPUs, while retaining all of the memory associated with the Amazon EC2 instance type. This helps you reduce the number of Microsoft SQL Server Core licenses that you need to bring (subject to a 4-core licensing minimum set by Microsoft), or lower the license included costs for Windows Server and SQL Server. To learn more, see the [Optimize CPU Best Practices for SQL Server Workloads](https://aws.amazon.com/blogs/modernizing-with-aws/optimize-cpus-best-practices-for-sql-server-workloads-continued/) blog post. @@ -186 +182 @@ Inputting the Microsoft licensing you're bringing to AWS into License Manager wi -To learn more about License Manager, see [Working with AWS License Manager](https://docs.aws.amazon.com/license-manager/latest/userguide/using-license-manager.html) in the License Manager documentation. +[High Availability for SQL Server on Amazon EC2](https://docs.aws.amazon.com/sql-server-ec2/latest/userguide/sql-high-availability.html) is another option to lower license included SQL Server costs for active-passive failover clusters. With this feature, you pay for SQL Server license included on only the active SQL Server Amazon EC2 instance, where the secondary passive instance is the same size or smaller in terms of vCPUs. For more information, see the [Reduce Microsoft SQL Server High Availability costs running on Amazon EC2](https://aws.amazon.com/blogs/modernizing-with-aws/amazon-ec2-reduces-costs-for-microsoft-sql-server-high-availability-deployments/) blog post. @@ -190 +186,3 @@ To learn more about License Manager, see [Working with AWS License Manager](http -Consider planning your migration around the licenses currently assigned to the workloads prior to migration. For example, if you're bringing several on-premises hosts to AWS, consider migrating by host rather than by grouping workloads that fall across several different hosts. This is because as you decommission an on-premises host, you free up the licenses associated to that host for use in AWS. Alternatively, you can use license included instances for Windows Server or SQL Server during your migration and switch over to the BYOL option after the migration is complete. However, this option requires using your own media and AMI from the beginning (even for license included options). The [license conversion feature](https://docs.aws.amazon.com/license-manager/latest/userguide/conversion-procedures.html) available with AWS License Manager only allows you to switch to BYOL from license included if the EC2 instances were originally created from your own media and AMIs. +We recommend completing a fully-funded [Optimization and Licensing Assessment (OLA)](https://aws.amazon.com/optimization-and-licensing-assessment/), which can help you right-size your instances and provides multiple pricing and migration options within a business case. It can also review your specific licensing and provide customized recommendations. + +Consider planning your migration around the licenses currently assigned to the workloads prior to migration. For example, if you're bringing several on-premises hosts to AWS, consider migrating by host rather than by grouping workloads that fall across several different hosts. This is because as you decommission an on-premises host, you free up the licenses associated to that host for use in AWS. Alternatively, you can use license included instances for Windows Server or SQL Server during your migration and switch over to the BYOL option after the migration is complete. However, this option requires using your own media and AMI from the beginning (even for license included options). The [license conversion feature](https://docs.aws.amazon.com/license-manager/latest/userguide/conversion-procedures.html) available with AWS License Manager only allows you to switch to BYOL from license included if the Amazon EC2 instances were originally created from your own media and AMIs. @@ -209 +207,3 @@ Within 10 days of deploying your Microsoft workloads on AWS, be sure to submit t -To learn more about the verification process, see [License Mobility through Software Assurance](https://www.microsoft.com/en-us/licensing/licensing-programs/software-assurance-license-mobility.aspx) in the Microsoft documentation. For more guidance, see Microsoft's [Verification Guide for Customers](https://download.microsoft.com/download/7/9/b/79bd917e-760b-48b6-a266-796b3e47c47a/License_Mobility_Customer_Verification_Guide.pdf) (downloadable PDF) in the Microsoft documentation. To download a copy of the License Mobility Verification Form, see [Licensing Resources and Documents](https://www.microsoft.com/licensing/docs/view/Forms?lang=1&year=2016) in the Microsoft documentation. +The **License Mobility Verification** form has a section to provide information about the authorized mobility partner. Use `[email protected]` as the email address, `Amazon Web Services` as the partner name, and `aws.amazon.com` as the partner website. + +To learn more about the verification process, see [License Mobility through Software Assurance](https://www.microsoft.com/en-us/licensing/licensing-programs/software-assurance-license-mobility.aspx) in the Microsoft documentation. For more guidance, see Microsoft's [Verification Guide for Customers](https://download.microsoft.com/download/7/9/b/79bd917e-760b-48b6-a266-796b3e47c47a/License_Mobility_Customer_Verification_Guide.pdf) (downloadable PDF) in the Microsoft documentation. To download a copy of the **License Mobility Verification** form, see [Licensing Resources and Documents](https://www.microsoft.com/licensing/docs/view/Forms?lang=1&year=2016) in the Microsoft documentation.