Microsoft Foundry as a Hyperscaler Control Plane

A 21-part guide. Start at Part 1, or jump to any part below.

The parts

1. Microsoft Foundry Is Not a Product You Log Into. It Is an ARM Resource.
2. Your agent is four lines away from a governed cloud endpoint
3. Every platform says it is Framework-Agnostic. here is the receipt.
4. Your Foundry agent is deployed and has no idea who is calling it
5. There is no FoundryCheckpointSaver
6. Your agent's tools should not ship on your release cadence
7. Microsoft Foundry Ships a Thousand Tools. The Only Two Questions That Matter Are Not on the List.
8. Foundry memory does the expensive part, then hands you the harder one
9. One agent, three hundred users, one endpoint, and a security reviewer who wants proof
10. Your agent cannot start itself, survive a hangup, or survive a crash, and those are three different bugs
11. Your agent pays frontier prices to summarize a press release
12. The Paragraph in the PDF Was Addressed to Your Agent
13. Foundry Is Not Tracing Your Agent, and Nothing Will Tell You
14. Your agent is fully traced and still ungradeable
15. Microsoft Foundry Multi-Agent: The Protocol Is a Weekend. The Permissions Are the Project.
16. Your agent fleet dashboard is lying to you, and the permission model is why
17. The Azure AI agent decisions you cannot undo
18. The publish button is four API calls in a trench coat
19. Hosted Agents Do Not Exist in Azure Government. Read That Table Before the ATO Review.
20. Microsoft Foundry Lock-In Is Real. It Is Not Where You Think It Is.
21. Two Control Planes, Nine Axes, and the Third Column This Article Refuses to Print