SAMexpert logo

Licensing NON-PRODUCTION virtual machines (Microsoft Licensing)

There is an issue with interpreting Microsoft Licensing rules for non-production virtual machines. Those that are used by your IT people for DevOps and testing.

What if they are deployed in the same cluster with production virtual machines? Does it create a licensing issue. Is it compliant? Is it expensive to do so?

It's not that simple, and open to interpretation. However, please let me help you avoid the confusion and clarify the rules.

What is a Production Environment, in the first place? Let's dive in!

0:00 Using non-production virtual machines in production clusters
0:33 The story began many years ago
1:33 What happened in October 2014
1:57 What is the definition of a Production Environment
2:36 Let's get to the drawing board
4:17 What is my opinion on the rules of mixing production and non-production
5:20 What to do if you or someone else disagrees with this interpretation
5:45 What I advise to do to avoid this issue entirely

If you prefer reading, here's an article I wrote on the subject:

Want us to solve your licensing headaches?
We'll figure out a way to do it with zero BS and zero waste.
► Let's have a chat:


► Join this channel to support our mission:
► Follow or connect to Daryl Ullman on LinkedIn:
► Follow or connect to Alexander Golev on LinkedIn:
► Follow SAMexpert on LinkedIn:
► Follow SAMexpert on Twitter:
► Follow the Telegram channel:

#Microsoft #ITProcurement #MicrosoftLicensing

Please watch: "Microsoft Cloud & Licensing Update October 2023: CoPilot, Teams, ESU"