Microsoft brings MCP to Azure Logic application in public preview (standard), turning connectors into proxy tools

Microsoft has released a public preview that can be enabled Azure Logic Application (Standard) Run as Model Context Protocol (MCP) Serveruses logical application workflows as proxy tools that can be discovered and callable through MCP-capable clients (e.g., VS Code + Copilot).

What actual transportation

• Remote MCP server on logical applications (standard): You configure the standard logic application to host the MCP endpoint (/api/mcp) and surface HTTP request/response Workflow as a tool. Authentication is made by Easy Auth; MCP endpoint Default is OAuth 2.0. VS code (≥1.102) includes GA MCP client support for testing.
• API Center Registration Path (Preview): You can also Azure API Centerthe place to choose Hosted Connectors Action becomes a tool for cataloging and governance.

Key requirements and shipping details

• Workflow shape: The tool must be implemented as HTTP Request Trigger (“on receiving HTTP request”) plus reply action.
• Identity card and access control: By default, MCP uses OAuth 2.0; Easy Auth enforces client/identity/tenant restrictions. In the settings, Application authentication must allow unauthenticated requests (The MCP stream still executes OAUTH).
• transportation: Streaming media http Use out of the box. SSE Also need VNET Integration and host.json environment
  Runtime.Backend.EdgeWorkflowRuntimeTriggerListener.AllowCrossWorkerCommunication=true.
• Enable switch: It can be enabled by adding the MCP API extensions.workflow.McpServerEndpoints.enable=true exist host.

API Center Path: Important Preview Limitations

By creating an MCP server API Center With the support of a logical application, the current preview imposes the following restrictions:

• Start with one Empty Standard logic application resources.
• One connector per MCP server.
• Built-in service provider and Custom connectors Not supported in this path (only by managed connectors).
• One action per tool.

These constraints essentially affect tool granularity and server layout in larger estates.

Why is the standard (single tenant) the goal?

standard Run when a single tenant logic application runs (on Azure functionality), support Multiple workflows per applicationand directly with Virtual network and Private endpoint– All about safe exposure of private systems to agents and predictable throughput/latency. In comparison Consumption is a multi-material, single workflow for every application and paying for.

Tool semantics and discoverability

Microsoft recommends adding Trigger description,,,,, Parameter mode/descriptionand Required Tags to improve proxy tool selection and call reliability. These comments are read by MCP customers and affect call behavior.

Connector and enterprise scope

The organization can host existing workflows and Large directory of logical application connectors (cloud and on-premises) through MCP, turn them into cocoa proxy tools; Microsoft explicitly quotes “More than 1,400 connectors. ”

Operation, governance and testing

Run history plus Application Insights/Log Analysis Can be used for diagnostic and auditability. VS code passes MCP: Add serverincluding Oauth login and tool enumeration. Registered by API Center Bring discovery/governance to cross-team MCP servers.

Production Notes (Preview)

• SSE Both need vnet and Cross-workers Environment; without these, please use streaming http.
• Easy Auth The client login stream must be configured accurately (including “allowing unverified” switches), or despite OAuth’s expectations, the client login stream will fail.
• Throw, splurge and pattern version Keep your responsibility when wrapping the connector as a tool (not new, but in the proxy path). InfoQ highlights similar operational issues for early adopters.

Summary

Preview cleaning MCP-Enables logic application (standard): You use HTTP-based workflows as a tool for OAuth protection; you can classify them in the API center; you can reach private systems through a single-tenant network. For teams that have already invested in logic applications, this is a low-friction, standard-consistent approach to operating enterprise agent tools, API Center Limitations,,,,, SSE Prerequisitesand Simple authorization During launch.

See more Details are here. Check out ours anytime Tutorials, codes and notebooks for github pages. Also, please stay tuned for us twitter And don’t forget to join us 100K+ ml reddit And subscribe Our newsletter.

Talk to us about your content partnership with Marktechpost.com

Michal Sutter is a data science professional with a master’s degree in data science from the University of Padua. With a solid foundation in statistical analysis, machine learning, and data engineering, Michal excels in transforming complex data sets into actionable insights.