At Ignite 2025, Foundry tools were introduced in Microsoft Foundry – a unified catalog of tools, connectors and MCP servers.
We are excited to share more about Azure Logic Apps connectors now available as tools in Microsoft Foundry. This unlocks a seamless way for developers to give their agents secure, governed access to the systems they rely on—without writing boilerplate authentication code or managing API plumbing.
With this feature, agents can now use any Logic Apps connector—including SAP, ServiceNow, Dynamics, Salesforce, SQL, GitHub, and hundreds more—as a first-class MCP tool inside Foundry. This builds on our recent Public Preview of Logic Apps MCP Servers, which enable both connectors and workflows to be exposed as MCP tools.
How it works
Step 1 — Select a Logic Apps connector as a tool
In the Agent Tools catalog, you’ll now find Logic Apps connectors available alongside existing MCP tools. You can search by name or filter to show only Logic Apps connectors (marked with the Custom tag). After selecting a connector, you’ll move on to choosing a Logic App resource.
Step 2 — Create or select a Standard Logic App
Logic Apps connectors require a Standard Logic Apps resource as their host. If you don’t already have one, a new Logic App will be created automatically. If you do, you’ll see a dropdown allowing you to pick an existing Logic App.
Step 3 — Configure the connector as an MCP server
This is where Logic Apps provides its power and flexibility. You effectively generate an MCP server using your connector:
- Choose which operations you want to expose
- Optionally configure parameter behavior
- Specify whether parameters are provided by the model or the user
- Review or edit the autogenerated tool description based on the connector’s OpenAPI definition
Parameters that require user input are clearly indicated in the UI.
Step 4 — Register the MCP server as a tool in Foundry
This flow begins in the Azure portal and completes in the Foundry portal. After registration completes, your tool appears in the Agent tool list—ready to be added to any agent. In the Connected Resources view, you’ll also see the Logic Apps resource that backs your MCP tool.
In just a few steps, agents can now use Logic Apps connectors natively, unlocking secure enterprise connectivity without custom code.
Foundry continues to support custom MCP servers, including those created from Logic Apps workflows themselves. If you want to expose a workflow as an MCP tool, you can do so with the same mechanism. (See our detailed document on converting workflows to MCP tools.)
Roadmap
Unified Experience
Today, the flow spans the Azure portal and the Foundry portal. A fully Foundry-native experience is coming in an upcoming release.
OAuth-based First-Party Connectors
Some first-party connectors using OAuth are not yet supported. These will be enabled in the near future.
Next Steps
- Watch this short demo video to see the feature in action.
- Get started with the documentation to try it yourself.
Microsoft