Part 21 · One Agent, Five Platforms

Microsoft shops already have most of the pieces: Logic Apps for workflows, Functions for code, and API Management in front of their APIs. So this part asks one question: how do the same nine tools look on Azure?

Like the MuleSoft, Boomi and SAP builds ( Parts 11 , 14 and 17 ), this build is documentation-only . Everything below comes from Microsoft Learn as I read it on 9 November 2026, linked in the text. I haven't run the invoice agent on Azure yet. This part covers only the tools. The agent in Foundry Agent Service, identity, the Teams approval and the scores come in Part 22.

The short answer

Azure gives you three ways to host an MCP tool, and one gateway to put in front of them:

Logic Apps (Standard) can act as a remote MCP server. Each workflow becomes a tool.

Azure Functions has an MCP tool trigger. Each function becomes a tool.

API Management can expose a REST API as an MCP server.…