Part 22 · One Agent, Five Platforms

Part 21 put the nine tools on Azure: Logic Apps, Functions and API Management, with one gateway in front. This part builds the agent on top. Microsoft shops already have identity in Entra and approvers in Teams and Outlook, so the question is: what does the agent build look like when identity and Office come for free?

It's documentation-only , like the other builds. Everything below comes from Microsoft Learn as I read it on 10 November 2026, linked in the text. It covers Foundry Agent Service, agent identity, the AI gateway, the Teams approval, observability, and Azure's provisional scores.

How the pieces map

Using the five layers from Part 3 :

Channel: the AP exception queue, and approvers in Teams .

Agent: a prompt agent in Foundry Agent Service , with its own Entra agent identity .

Tools: the three MCP servers from Part 21, behind API Management .

Process layer: process APIs with the rules and the approval_id check.

System of record: the ERP, reached only…