Dude, Make Up Your Mind

There's a special kind of exhaustion reserved for people who work with Microsoft products. It's not the exhaustion of debugging a null pointer at 2 a.m., or the exhaustion of a meeting that should've been an email. It's the exhaustion of opening a tutorial you bookmarked four months ago and realizing every single product name in it is now wrong.

Let me tell you what set me off this time.

A Platform With an Identity Crisis

It started as Azure AI Studio. Fine. Reasonable name. It's a studio, it's on Azure, it does AI.

Then at Ignite 2024, it became Azure AI Foundry. Okay, sure. "Foundry" sounds more industrial, more serious. I updated my slides. I updated the one paragraph in my docs that mentioned it.

Then — appreciate the timing here — barely twelve months later at Ignite 2025, it became Microsoft Foundry. They dropped the "Azure." The official justification is that dropping "Azure" signals agents are now "first-class citizens" in the Microsoft ecosystem rather than just another Azure service. The agents got a promotion. I got homework.

That's two rebrands in twelve months for one product. The half-life of a Microsoft product name is now shorter than the time it takes me to finish the course explaining it.

This Is Not an Isolated Incident. This Is a Lifestyle.

If Foundry were a one-off, I'd let it slide. But Microsoft renames things the way other people breathe.

Azure Active Directory → Microsoft Entra ID. Which is genuinely funny, because now Azure Active Directory isn't Azure Active Directory anymore, but Active Directory — the actual on-prem thing — is still Active Directory. Cleared that right up.

Office → Office 365 → Microsoft 365 → Microsoft 365 Copilot. At this point calling it "Office" is like calling a stadium by the name of a company that stopped sponsoring it a decade ago. Everyone knows what you mean, and everyone knows you're old.

Configuration Manager holds the record. SMS → SCCM → Endpoint Configuration Manager → Configuration Manager. Four names. It renamed itself back to almost where it started, like a man who tries three haircuts and goes back to the original.

Someone built a rename tracker. It catalogues over 40 products and 65+ name changes going back to 2006. The renaming is so relentless it spawned its own cottage industry of tools whose only job is to help you figure out what the thing you already own is called this week.

The Thing Is, They're Not Wrong — And That's What's So Annoying

Here's the infuriating part. Every rename has a defensible reason.

Azure AI Studio genuinely outgrew "studio." It became a full platform with an agent service, model catalog, evaluations, and governance. Dropping "Azure" genuinely reflects that Foundry now reaches into GitHub, VS Code, Microsoft 365, and runs locally off the cloud too.

Renaming Azure AD to Entra genuinely reduced confusion with on-prem Active Directory — while creating a whole new confusion, but let's not relitigate.

Each individual decision, in a well-lit conference room, makes sense. But strategy changes every eighteen months, and so does the name. And nobody in that room is the one explaining to a room full of bootcamp students why the platform in their official study materials has a different name than the platform on the actual screen. That person is me.

The Real Cost Isn't Confusion. It's Trust.

Rename once, people update. Rename twice in a year, people stop learning the name at all. They just wait to see if it sticks. That's the actual damage — the slow erosion of anyone treating the name as load-bearing.

Every reference now comes with a genealogy. I catch myself writing "Microsoft Foundry (formerly Azure AI Foundry, formerly Azure AI Studio)" like I'm reading the credits of a witness protection program. Every doc needs a footnote. Every conversation starts with a five-second disambiguation ritual.

The machinery doesn't care what the marquee says. Under all the names, the URLs, APIs, endpoints, and keys usually stay the same. So the rename changed nothing that functions and everything that's documented — maximum disruption to humans, zero disruption to the product.

So, Microsoft, From One Tired Engineer

I'm not asking you to never rename anything. Products evolve. Names should too, occasionally, with ceremony and warning and a very good reason.

I'm asking you to pick a name and sit with it. Let it get old. Let it get comfortable. Let a full generation of Stack Overflow answers reference it before you tear it all down again. Let me write one tutorial that's still accurate by the time someone reads it.

Dude. Make up your mind.

And if it's changed again by the time you're reading this — no it hasn't. I refuse.