HomeArtificial IntelligenceMicrosoft Brings MCP to Azure Logic Apps (Commonplace) in Public Preview, Turning...

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


Microsoft has launched a public preview that allows Azure Logic Apps (Commonplace) to run as Mannequin 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 truly transport

  • Distant MCP server on Logic Apps (Commonplace): You configure a Commonplace logic app to host an MCP endpoint (/api/mcp) and floor HTTP Request/Response workflows as instruments. Authentication is front-doored by Simple Auth; MCP endpoints default to OAuth 2.0. VS Code (≥1.102) contains GA MCP consumer assist for testing.
  • API Heart registration path (preview): You can too create/register MCP servers in Azure API Heart, the place chosen managed connector actions grow to be 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: Instruments should be applied 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; Simple Auth enforces consumer/id/tenant restrictions. Throughout setup, App Service authentication should enable unauthenticated requests (the MCP move 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 change: MCP APIs are enabled by including extensions.workflow.McpServerEndpoints.allow=true in host.json.

API Heart path: preview limitations that matter

When creating MCP servers by way of API Heart backed by Logic Apps, the present preview imposes the next limits:

  • Begin with an empty Commonplace logic app useful resource.
  • One connector per MCP server.
  • Constructed-in service-provider and customized connectors aren’t supported on 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 Commonplace (single-tenant) is the goal?

Commonplace runs on the single-tenant Logic Apps runtime (on Azure Features), helps a number of workflows per app, and integrates straight with digital networks and personal endpoints—all related for exposing personal programs safely to brokers and for predictable throughput/latency. Against this, 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 conduct.

Connectors and enterprise attain

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

Operations, governance, and testing

Run historical past plus Software Insights/Log Analytics can be found for diagnostics and auditability. VS Code supplies fast consumer validation by way of MCP: Add Server, together with OAuth sign-in and gear enumeration. Registering by way of API Heart brings discovery/governance to MCP servers throughout groups.

Manufacturing notes (preview)

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

Abstract

The preview cleanly MCP-enables Logic Apps (Commonplace): you expose HTTP-based workflows as OAuth-protected instruments; you’ll be able to catalog them in API Heart; and you’ll attain personal programs by single-tenant networking. For groups already invested in Logic Apps, this can be a low-friction, standards-aligned path to operationalize enterprise agent tooling—simply thoughts the API Heart limits, SSE stipulations, and Simple Auth nuances throughout rollout.


Take a look at extra particulars right here. Be happy to take a look at our GitHub Web page for Tutorials, Codes and Notebooks. Additionally, be at liberty to observe us on Twitter and don’t neglect to affix our 100k+ ML SubReddit and Subscribe to our Publication.

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


Michal Sutter is an information science skilled with a Grasp of Science in Knowledge Science from the College of Padova. With a stable basis in statistical evaluation, machine studying, and knowledge engineering, Michal excels at reworking advanced datasets into actionable insights.

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -
Google search engine

Most Popular

Recent Comments