Azure Logic Apps as MCP servers: what the docs skip

Azure Logic Apps can now act as remote MCP servers, which puts 1,400+ Microsoft connectors — Dataverse, SharePoint, SQL, Outlook, SAP, ServiceNow — in reach of AI agents in Claude Code, VS Code Copilot or Cursor. The feature has been in preview since March 2026. The headline is easy; the parts the docs skip are what decide whether you should use it.

How it works

Logic Apps Standard exposes selected workflows as callable tools. You pick a connector, choose the actions to expose, and Azure builds the MCP endpoint — no custom TypeScript or Python wrapper per integration. The protocol is JSON-RPC 2.0 over Server-Sent Events, transported over HTTP. Your MCP server runs in Azure while the client runs locally, so this is remote MCP, not local.

Two setup paths, and they are not equivalent

A detailed walkthrough on Dev.to argues that Microsoft presents two options as interchangeable when they are not:

• Direct from the Logic App. Under Agents, an MCP servers blade lets you create a server, select workflows and choose OAuth or API key auth. Fast — but no rate limiting, no usage analytics, no key-rotation policy, and no catalog for other teams to discover it. Fine for dev/test and personal tooling.
• Via API Center. Adds API Management for auth, throttling and usage tracking, plus API Center for discovery and governance. The chain becomes client → API Management → API Center → Logic App → connectors → enterprise systems. This is the path for production and anything touching customer data.

The auth details worth knowing before you build

The author's central warning is that Easy Auth is not optional — without it the MCP server accepts calls from anyone — and that the setup runs eight steps, including an app registration in Entra ID and an allowed token audience that requires a trailing slash.

API keys, per the same walkthrough, support exactly three expiration durations: 24 hours, 7 days, or 30 days. No custom duration, no automatic rotation.

The governance gap is the sharper point. When the MCP server calls a connector — Outlook, say — it uses the credentials stored in the Logic App's API connection. The agent therefore sends email as whoever set that connection up. Read and query connectors carry less risk; anything that creates, updates or sends data needs a service account or a shared connection, decided before you expose it.

What it costs

MCP servers need a persistent HTTP endpoint, so this runs on Logic Apps Standard — an always-on App Service plan — not on Consumption, which spins up per trigger and shuts down between calls. The author puts the entry-level Workflow Standard (WS1) plan at roughly $160 per month for the minimum always-on configuration at list rates, citing the Azure Logic Apps pricing page, and notes that region and reservation discounts vary.

That figure is the whole buyer-intent question in one line. For a light dev/test setup it is a real cost against zero for idle Consumption workflows. For a production server several teams call, the author's read is that it is noise.

Worth it?

Use the direct path if you control both client and server and you are prototyping — you get 1,400+ connectors as agent tools for the price of an always-on plan and an afternoon of Easy Auth setup. Go through API Center the moment a second team or real customer data is involved, because none of the throttling, audit or discovery you will be asked about later exists on the direct path.

Answer the connector-credential question first, though. Deciding which identity your agents act as is cheaper before the server exists than after someone's inbox has sent a hundred agent-written emails.