|

Microsoft Brings MCP to Azure Logic Apps (Standard) in Public Preview, Turning Connectors into Agent Tools

ByRicardo

Microsoft has launched a public preview that permits Azure Logic Apps (Standard) to run as Model Context Protocol (MCP) servers, exposing Logic Apps workflows as agent instruments discoverable and callable by MCP-capable purchasers (e.g., VS Code + Copilot).

What’s really transport

  • Remote MCP server on Logic Apps (Standard): You configure a Standard logic app to host an MCP endpoint (/api/mcp) and floor HTTP Request/Response workflows as instruments. Authentication is front-doored by Easy Auth; MCP endpoints default to OAuth 2.0. VS Code (≥1.102) contains GA MCP shopper assist for testing.
  • API Center registration path (preview): You may create/register MCP servers in Azure API Center, the place chosen managed connector actions develop into instruments with cataloging and governance.
https://be taught.microsoft.com/en-us/azure/logic-apps/set-up-model-context-protocol-server-standard

Key necessities and transport particulars

  • Workflow form: Tools should be carried out as HTTP Request set off (“When a HTTP request is obtained”) plus a Response motion.
  • Auth & entry management: By default, MCP makes use of OAuth 2.0; Easy Auth enforces shopper/identification/tenant restrictions. During setup, App Service authentication should permit unauthenticated requests (the MCP stream nonetheless performs OAuth).
  • Transports: Streamable HTTP works out of the field. SSE moreover requires VNET integration and host.json setting
    Runtime.Backend.EdgeWorkflowRuntimeTriggerListener.AllowCrossWorkerCommunication=true.
  • Enablement swap: MCP APIs are enabled by including extensions.workflow.McpServerEndpoints.allow=true in host.json.

API Center path: preview limitations that matter

When creating MCP servers through API Center backed by Logic Apps, the present preview imposes the next limits:

  • Start with an empty Standard logic app useful resource.
  • One connector per MCP server.
  • Built-in service-provider and customized connectors aren’t supported in this path (managed connectors solely).
  • One motion per device.

These constraints materially have an effect on device granularity and server format in bigger estates.

Why Standard (single-tenant) is the goal?

Standard runs on the single-tenant Logic Apps runtime (on Azure Functions), helps a number of workflows per app, and integrates instantly with digital networks and non-public endpoints—all related for exposing non-public methods safely to brokers and for predictable throughput/latency. By distinction, Consumption is multitenant, single-workflow per app, and pay-per-execution.

Tooling semantics and discoverability

Microsoft recommends including set off descriptions, parameter schemas/descriptions, and required markers to enhance agent device choice and invocation reliability. These annotations are learn by MCP purchasers and affect calling habits.

Connectors and enterprise attain

Organizations can entrance present workflows and a big catalog of Logic Apps connectors (cloud and on-prem) by means of MCP, turning them into callable agent instruments; Microsoft explicitly cites “more than 1,400 connectors.”

Operations, governance, and testing

Run historical past plus Application Insights/Log Analytics can be found for diagnostics and auditability. VS Code offers fast shopper validation through MCP: Add Server, together with OAuth sign-in and power enumeration. Registering through API Center brings discovery/governance to MCP servers throughout groups.

Production notes (preview)

  • SSE requires each VNET and the cross-worker setting; with out these, use streamable HTTP.
  • Easy Auth should be configured exactly (together with the “permit unauthenticated” toggle) or shopper sign-in flows will fail regardless of OAuth expectations.
  • Throttling, idempotency, and schema versioning stay your accountability when wrapping connectors as instruments (not new, however now in the agent path). InfoQ highlights related operational issues from early adopters.

Summary

The preview cleanly MCP-enables Logic Apps (Standard): you expose HTTP-based workflows as OAuth-protected instruments; you’ll be able to catalog them in API Center; and you’ll attain non-public methods by means of single-tenant networking. For groups already invested in Logic Apps, this can be a low-friction, standards-aligned route to operationalize enterprise agent tooling—simply thoughts the API Center limits, SSE conditions, and Easy Auth nuances throughout rollout.

Check out extra details here. Feel free to take a look at our GitHub Page for Tutorials, Codes and Notebooks. Also, be happy to comply with us on Twitter and don’t overlook to be part of our 100k+ ML SubReddit and Subscribe to our Newsletter.

For content material partnership with marktechpost.com, please TALK to us

The put up Microsoft Brings MCP to Azure Logic Apps (Standard) in Public Preview, Turning Connectors into Agent Tools appeared first on MarkTechPost.

Similar Posts