Last week, Amazon shouted from the rooftops that its customers are finally allowed to use Microsoft 365 from AWS WorkSpaces.
At the risk of looking a gift horse in the mouth, this is a stunning reversal of a licensing limitation that Microsoft has had in place since October of 2019. The limitation was seemingly put in place to restrict Office 365 usage at key competitors, but it has yet to be publicly challenged.
Per Microsoft’s announcement:
With this announcement, Microsoft lifted a very specific part of a broader set of limitations that has served as a point of frustration for vendors and customers alike.
In August 2019, Microsoft stated that on October 1, 2019:
As usual, Microsoft licensing interpretation is in the eye of the beholder, and if you ask 10 different people a Microsoft licensing question, you will get 11 different answers. However, here is some unambiguous language that specifically excludes Listed Providers from being able to provide Office or Windows. Those Listed Providers, in a document maintained by Microsoft and dated October 2019, are as follows:
There is also a note that says any service running on a Listed Provider is also subject to this policy, and it specifically cites VMware Cloud on AWS as an example. Effectively, it meant that the only way to run Office 365 was either on premises, from a cloud that’s not a Listed Provider or — and this is where the eyebrows start to rise — on Azure Virtual Desktop. This final option involves a different licensing path that’s not affected by this policy.
It seems counterintuitive that Microsoft should be on the list of excluded providers. My only possible explanation is that, by placing themselves on the list at the same time as creating another way to use Office 365 from the cloud — via Azure Virtual Desktop — that customers get as part of an enterprise agreement, Microsoft can say, “We excluded ourselves, too,” while at the same time onboarding people into their new ecosystem.
This policy, and the caveat that any services running on a Listed Provider were also affected, means that other services, such as Azure VMware Solution — which is effectively vSphere as a service, delivered by Microsoft — are also not able to run Office 365 or Windows desktop OSes. That is, they aren’t able to run without paying the license mobility fee, which is effectively just a VDA license in addition to your E3/E5 license.
Despite Microsoft being on the list, they still created a path that makes Azure Virtual Desktop the only place to go for customers who want to use Windows desktop operating systems, Windows multi-session and Office 365.
Microsoft appears to have walked back one very specific angle of its licensing policies: AWS WorkSpaces seems to have been carved out of the Listed Providers. What that means for the other Listed Providers remains to be seen, including non-WorkSpaces AWS workloads. For example, what does that mean for VMware and Citrix environments that want to run on VMware Cloud on AWS?
It does appear that software using WorkSpaces Core is included in this, which could be great news for partners such as Leostream, VMware, and Workspot that are working with AWS today.
It’s also worth noting that all the other licensing stipulations are still in effect with AWS and Microsoft. Windows Server instances can run on shared hardware with licensing built into the AWS WorkSpaces subscription cost, while Windows desktop OSes are bring your own license (BYOL) and must run on dedicated hardware.
This is a huge deal, for sure. But now it seems as though Microsoft is picking and choosing who it works with and who it doesn’t. To me, the real question is, “Why did they make that change? And why now?”
Could the heat have been on? Google and AWS, as well as independent groups like the Coalition for Fair Software Licensing, are attempting to shine a light on unfair practices across the industry, and it may be gaining traction among themselves and customers. One guess is that Microsoft’s hand was forced by some large customers, perhaps under the threat of a lawsuit that could force Microsoft to explain these license policies in a way that didn’t make them seem anti-competitive.
From intel based on industry conversations, the other Listed Providers are still playing by the old rules, though that could change. Perhaps the number of disenfranchised customers hasn’t hit a critical mass to force a broader change. But the other companies listed — or a partner of theirs like VMware — should be waving their hands wildly, asking when each of their platforms and customers are next. It’s also worth noting that this announcement does nothing to provide relief for customers that are paying for Windows VDA licenses when running desktops in Listed Providers and not in Azure Virtual Desktop.
Nevertheless, the key takeaway: This is a good thing for AWS and AWS WorkSpaces customers, and it levels the competitive landscape a tiny bit. There is a long way to go, but it gives hope that things may open up a bit more in the future.
It’s chock full of useful advice, exclusive events and interesting articles. Don’t miss out!