Microsoft Windows Server Licensing per virtual machine consideration

Windows Server licensing has finally changed. And it changed drastically. What Microsoft is now allowing us to do is to license Windows Server per individual virtual machine, both on-premises and on authorized outsources.

But there's a little problem. It's not that easy for many clients to switch from the existing licensing model to the per-VM licensing model because Microsoft requires two things.

Firstly, it must be subscription licenses in CSP or licenses with Software Assurance.

And here's the bummer. All the client access licenses must be either subscription licenses or licenses with Software Assurance. There you go. Here's the breaking news.

LET'S TALK ABOUT YOU

❓ Would you like to check if you're getting a fair deal on Microsoft licenses and Cloud?
❓ Are you migrating to Azure and AWS and want to reduce costs?
❓ Is your agreement expiring soon?
❓ Are you being audited?

LET'S CONNECT

✅ Let's figure out a way to fix your licensing headaches the best way possible, with 🚫 zero BS and 🚫 zero waste.

-~-~~-~~~-~~-~-
Please watch: "SPLA Audit Readiness: Building a Fortress of Compliance"
-~-~~-~~~-~~-~-

[RMPLPRO]

What about rumors that we must assign minimum 8 core per VM and minimum purchase is 16 core ?

[jasonraewagan]

Hello Im an avid fan of your video because it really help me as a licensing consultant. For this, does it mean the windows server license will now be subscription based and need to be renew yearly? And what will happen to the licenses if it doesn't renew on time?