Microsoft just released Azure Linux 4.0, their very own Fedora-derived, RPM-based server distribution. But that’s not all—they also dropped Azure Container Linux, Coreutils for Windows, and a $5,000+ AI workstation with native Linux GPU passthrough. Is Microsoft truly embracing open source, or are we witnessing the beginning of a new Embrace, Extend, Extinguish strategy?
In this deep dive, I break down exactly what Microsoft announced at Build 2026, the technical specs of Azure Linux 4.0 (including DNF5, Linux 6.18 LTS, and post-quantum cryptography), and what this means for competitors like Red Hat and Canonical. As a sysadmin with 25 years of IT experience, I’ll give you my honest assessment of whether you should trust Microsoft’s Linux on your Azure infrastructure.
Is Microsoft truly embracing open source, or are we witnessing the beginning of a new Embrace, Extend, Extinguish strategy?
it’s the second one
Yup. M$ finally figured out how to use EEE against Linux.
MiKKKro$oft: Hey Amazon, can I copy your homework?
Embrace <—em-dollar sign is here
Extend
Extinguishtale as old as time
This is how they get Linux users to forcefully dox themselves. /s but probably not
Well, you already need a Micro$oft account to access Azure, so you are doxxing yourself in a way.
The question M$ is asking is: How do we roll this out to the desktop market and recapture our lost market share?
Edit: I know, Windows 11 also needs a M$ account now. But M$ intends to extinguish Linux (and FOSS) so that there is no software but theirs, so forcing Linux users back to Microslop is the 1st goal. Doxxing is the icing on the cake.
Windows 11 doesn’t need a Microsoft account. It’s strongly suggesting and forcing you too try and set one up.
OK at least Windows 11 Pro, Shift+F10 at any point during setup, “oobe\bypassnro” and reboot. For network, it now bypasses network requirement and you choose “I don’t have internet” then setup a regular user account.
I haven’t tried Windows Home edition in forever, but I’m sure there’s something similar available of not the same thing. But I’ve confirmed it worked in 24H2 and I believe 25H2 from my most recent Lenovo device at work.
OK at least Windows 11 Pro, Shift+F10 at any point during setup, “oobe\bypassnro” and reboot.
This trick may have been patched as of 25H2. https://techcommunity.microsoft.com/discussions/windows11/why-oobebypassnro-not-working-for-windows-11-25h2/4465864
Although, for Pro, I don’t know why you wouldn’t just select “domain join instead” during setup: https://www.youtube.com/watch?t=57&v=qHxeZr7Pi6c
EDIT: I know the point was you don’t need an M$ account, but MicroSlop is making it harder to refuse getting one.
I’ll test that today then to see which version shipped on that Lenovo.
You dont need it, you just need to go into the terminal and type in this obscure incantation to fix everything.
Microslop regressing back to what Linux users had to deal with ten years ago is funny.
Meh, this just seems like a pragmatic business move since selling Linux VMs makes them a large share of their revenue.
It’s interesting that they go the redhat route given that they have been cooperating with Ubuntu multiple times before. Might again be a pragmatic move since redhat is more common among business customers in the US.
I found a YouTube link in your post. Here are links to the same video on alternative frontends that protect your privacy:
