I'm a consultant engineer specializing in factory upgrades, and I've noticed a trend where getting Windows Server licenses has become a huge hassle. Every time my vendor asks for the admin for my customer's Microsoft tenant, it leads to a frustrating back-and-forth about access and responsibilities. This drawn-out process ends up taking weeks out of my schedule. I'm curious, for systems that aren't connected to the internet, why can't I just buy a license and assign it to the VM like we used to? Is there a way to simplify these conversations with vendors? What am I missing?
5 Answers
Welcome to the world of cloud-based licensing! There's no longer a simple license key you can buy and hand over. Your client needs to license the software themselves, even if your job is to handle the installation. But if the systems aren't online, you could try saying, 'I'm buying this license for X, please register it to them.' That may work, but results can vary based on the software and your vendor.
Honestly, it’s been like this for a while now. Windows licensing has evolved into this cloud-based model. As frustrating as it is, you have to navigate through Microsoft’s tenant system to manage licenses if you’re working with Windows products.
When did this become a strict requirement? Seems like no one around gets it.
It’s definitely a frustrating system for many. Licensing requirements have just become more complicated.
To save time, I recommend having the factory's IT department purchase and provide the MS licenses. Just tell them exactly what you need, and don’t go ahead until you have the licenses in hand. That way, it cuts down on the back-and-forth with vendors.
If you're looking for more efficient solutions, consider checking what other vendors or software might offer more straightforward licensing, but I know that not all software will work without Windows support.
You can't just buy a license outright because the system belongs to your customer. They need to own the license, and everything is tied to their Microsoft tenant, which manages these licenses via Microsoft 365 online. This is why you're having all those back-and-forths.
So, it's all about proving who owns the license in the end?
Yep, that's exactly the issue. They want to ensure the correct ownership.
I tried that approach before, but it didn't sit well with the vendor.