As a conclusion, if you want to run Windows 10 or Windows client OS in the cloud,
- Use Azure (you can use only azure to operate windows 10 in Public Clouds)
- Azure is the only cloud that can run Windows 10
- Can I use Windows 10 in other public cloud vendors?
- Can I use Windows 10 in AWS?
- Why we can not allow running Windows 10 in public cloud?
- related articles
Azure is the only cloud that can run Windows 10
It is decided by Microsoft.
Originally, Windows 10 was not licensed to run on the cloud in the first place.(Microsoft did not allow to run windows 10 in public cloud)
(It doesn't matter whether it works technically or not)
It is the first time that Microsoft has certified Windows 10 on Azure support (or rather, license use)
Can I use Windows 10 in other public cloud vendors?
- Windows 10 deployment in IaaS virtual machine is NG
- Windows 10 developed by yourself on a dedicated host is OK
In this case, you need an SA or VDA license
It is OK to bring your own license and deploy Window 10 as a virtual machine on a dedicated host that does not share the physical machine with other customers.
Deploying Windows 10 licenses for common virtual machine instances of the type that shares physical machines with other customers (multi-tenant type) is NG.
In other words, it cannot be a deployment method that you imagine.
This is the conclusion.
Can I use Windows 10 in AWS?
The answer is NG. (you can not run Windows 10 in AWS)
Can I bring in my own Windows Client licenses for use on AWS?
Yes. If you use Dedicated Instances or Dedicated Hosts, then you can bring in your own Windows Client licenses for use on AWS. Per Microsoft terms, you will require Software Assurance and/or Virtual Desktop Access (VDA) at SA renewal in order to utilize the Windows client operating systems such as Windows 10 on AWS.
Can I use License Mobility with Windows Client?
No, as specified in the Microsoft Product Terms, License Mobility does not apply to Windows Client. License Mobility is not required to deploy Windows Client licenses on EC2 Dedicated Hosts or EC2 Dedicated Instances. If you choose to use Dedicated Hosts and BYOL, then you can bring in your own licenses for Windows Client without needing License Mobility although you may be required to purchase a VDA license from Microsoft at future EA renewal.
For example, in AWS, there is a description in the FAQ that this can be done with bare metal equivalent hardware dedicated instances or Dedicated Hosts (SA rights are required).
Why we can not allow running Windows 10 in public cloud?
Again, it is possible in technically, but strictly means a license violation (contrary to license agreement)
- "Do not run", not "Windows 10 client OS does not run in public cloud"
using a Windows desktop operating system in a multi-tenant hosting environment such as Azure is not permitted, but OCI's VM also falls under this multi-tenant hosting environment. To work).
There is a description. Virtual cloud vendor virtual instances fall under the “multi-tenant hosting environment”
AWS / IBM / GCP / Oracle can't run Windows 10 in shared cloud.
You are allowed to deploy Windows 10 on a dedicated host (a type that exclusively occupies a physical server), but it is very expensive and requires a VDA license (or SA), so from the price point of view Very disadvantageous.
In other words, Azure has an overwhelming advantage and there is no point in choosing anything other than Azure.
By the way, SA is also troublesome, SA can be attached to a PC with Windows 10 in the first place.
That means that you need the same number of physical Windows 10 PCs as Windows 10 virtual machines to exercise the SA right, so it makes little sense to deploy Widnows 10 in the cloud.
Because everyone wants to access it from a thin client, Ipad or Chromebook.
When you design new on-premises IT platform you should check supported OS(s) before you begin to install operating system.
This article is about life-cycle policy of MAC OSX.