AI Alone Won’t Change the Business — the System Around It Will

Emiliano Montesdeoca — Sun, 14 Jun 2026 00:00:00 +0000

There is one line in the latest Microsoft AI platform essay that I think gets to the heart of the current moment:

the winners will not be the ones with the most demos, but the ones that turn AI into a governed, continuously improving system for real work.

That is exactly right.

This is one of the better strategic AI pieces because it gets the level right

Too many AI conversations still collapse into model talk.

Which model is smarter. Which model is cheaper. Which model is newest.

Those are not irrelevant questions, but they are too small if you are thinking like an enterprise.

The source article gets the scale of the challenge right. It says clearly that “What determines success is the system around the AI.”

That is the useful frame.

Because real enterprise value comes from the system around the model:

how agents are built
how they are grounded in enterprise context
how they are deployed
how they are governed
how they improve over time

That is what separates scattered experimentation from actual transformation.

Why I think this framing matters so much

If you only focus on the model, you get short-lived advantages.

If you focus on the system, you get leverage that compounds.

That is the key distinction.

And it aligns closely with where Foundry, GitHub, Microsoft IQ, and Agent Framework stories have all been heading lately.

My take

This is one of the stronger strategic pieces in the batch because it describes AI as an operating system for work, not as a set of disconnected demos.

That is the level enterprises actually need to think at.

And honestly, more of the public AI conversation should be happening at that level.

Original post: AI alone won’t change your business. The system running it will.

Azure DevOps and GitHub in the AI Era: The Platform Split Is Getting Clearer

Emiliano Montesdeoca — Wed, 03 Jun 2026 00:00:00 +0000

The latest Azure DevOps and GitHub announcement is interesting less for any single feature and more for the platform direction it makes explicit.

The message is pretty clear now:

GitHub is where the newest agentic development workflows land first
Azure DevOps still matters, especially in hybrid and transitional enterprise setups

That split is becoming easier to describe honestly.

The most useful thing about this post is that it stops pretending

One of the better lines in the source article is that for teams driving active development, moving repositories to GitHub often means unlocking “the latest AI-powered workflows,” while Azure DevOps continues to receive investment for teams that need more time.

That is a much more useful way to talk about the platform landscape than vague “everything is great everywhere” messaging.

Because the reality is simple:

GitHub is increasingly the leading edge for Copilot and agentic workflows
Azure DevOps still matters because real enterprises cannot always move everything at once

That is the practical truth.

Why this matters for teams making decisions now

The problem for many organizations is not whether GitHub has stronger AI momentum. It obviously does.

The problem is how to move without breaking:

planning workflows
pipeline investments
repo governance
migration timelines
internal processes around Azure Boards and test infrastructure

That is why the hybrid story matters so much.

The article makes it clear that Microsoft is not forcing a false all-or-nothing choice. It is building around a transitional reality.

Enterprise Live Migrations are probably the most operationally important part

I think the Enterprise Live Migrations preview is one of the most practical things in this announcement.

The idea that teams can migrate with “minimal cutover downtime” while developers keep working is exactly the sort of detail enterprises care about more than branding language.

This is where the strategy becomes real:

less freeze time
less migration drama
more realistic phased movement
better alignment with large-organization constraints

That is how platform direction becomes adoptable.

The Azure DevOps side is still meaningful

What I also appreciate here is that the Azure DevOps story is not being abandoned.

The article still highlights:

Copilot Code Review for Azure DevOps
Autofix for CodeQL in Azure DevOps
Apple Silicon hosted agents in Azure Pipelines
the Azure DevOps MCP server

That matters because a lot of organizations will live in a mixed state for quite a while.

And during that time, they still need better security and better developer workflows.

My take

For organizations planning their next moves, this is useful because it replaces vague platform positioning with something more operationally real.

GitHub is increasingly the AI-forward source-control center. Azure DevOps remains important for planning, pipelines, testing, and transition paths.

That is the practical reading.

And honestly, it is a much better message than pretending the transition problem does not exist.

Original post: Azure DevOps and GitHub: Journeying into the AI Era

GitHub | The .NET Blog

AI Alone Won’t Change the Business — the System Around It Will

This is one of the better strategic AI pieces because it gets the level right

Why I think this framing matters so much

My take

Azure DevOps and GitHub in the AI Era: The Platform Split Is Getting Clearer

The most useful thing about this post is that it stops pretending

Why this matters for teams making decisions now

Enterprise Live Migrations are probably the most operationally important part

The Azure DevOps side is still meaningful

My take