Guided collection · 3 notes

Azure AI Architecture

Field notes from my Microsoft role and AB-100 study: what Foundry actually is under the rebrand, when an agent is the wrong answer before it's even built, and where Copilot Studio's two orchestration protocols stop being interchangeable.

Your starting point

01 Start here

Before you build an agent, decide whether you should

Choose the least autonomous architecture that can complete the job reliably. 7 min read · Foundation Read the first note

Then keep going

The reading order

Each note builds on the question before it, without hiding the rest of the route.

02 Microsoft Foundry is one platform pretending to be three products Microsoft Foundry joins model, agent, tool, and evaluation work around shared project resources.
03 Copilot Studio didn't need a new protocol until agents had to talk to each other MCP connects an orchestrator to tools; A2A coordinates agents across a separate trust boundary.

← Browse every note