AzureFeeds

The promise of agentic AI is not simply more capable chat. It is autonomous work that advances real business processes. To achieve this, agents require two things: a place to be built with the appropriate models, instructions, knowledge, and guardrails and a place to be invoked and orchestrated, with triggers, workflows, and connections to the systems where work actually occurs.

Today, we are announcing a significantly improved experience that brings these two platforms together: Microsoft Foundry and Azure Logic Apps. Together, they form a single agentic stack. Foundry provides the intelligence, and Logic Apps provides the automation and orchestration.

What’s new

This release introduces a set of updates that taken together, brings a really better together experience to build and automate AI 

A streamlined experience to create and invoke Foundry Agents from Azure Logic Apps. You can now move from having an agent to running that agent inside a production business workflow in a few steps. You can author, configure, and call a Foundry Agent directly from the Logic Apps designer, with no custom integration code required.

Run Foundry Agents autonomously with Logic Apps triggers. This capability is what enables embedding Foundry Agents in workflows. A chat-bound agent runs only when a user types a message; an autonomous agent runs when the business requires it. With this release, you can pair any Logic Apps trigger with a Foundry Agent to build a business process, automating agents to react to events, run on a schedule, or both. These triggers can come from any of the 1,400+ connectors that expose them — such as ServiceNow incidents, GitHub issues, Jira tickets, and SAP IDocs — each capable of initiating a Foundry Agent. The result is that your agents do not wait for someone to interact with them. They activate the moment work arrives, reason about it, take action through their tools, and, where appropriate, hand off to long-running workflows. 

Logic Apps connectors are now available as tools for Foundry Agents. Any of those same 1,400+ Azure Logic Apps connectors can now be exposed directly to a Foundry Agent as a native tool. An agent can reason about a customer issue and then update the CRM, file the ticket, send the approval, or post the message.

Invoke entire workflows, including long-running ones, as Foundry agent tools. Tools are not limited to a single API call. With Logic Apps, an agent can invoke an entire workflow as a tool: a multi-step approval that waits days for a human response, a webhook callback, a long-running orchestration spanning multiple systems, or a process that pauses and resumes on external events. The agent reasons, and the workflow executes durably for as long as the process requires.

Business process automation, durable workflows, and agentic AI are now available on the same stack.

Why this matters

Building automations with agents and deterministic logic has meant working across two separate worlds: one platform to build and host the agent, and another to connect it to the systems where work happens and to invoke it when needed. This release brings those two worlds together. Foundry and Logic Apps now work as one agentic stack, with each platform handling what it does best

Getting Started

If you already have a Foundry Agent and a Logic Apps environment, you’re a few clicks away. Here are the steps to Create and/or Invoke Foundry Agents from Logic Apps Workflows

Add an Agent node to your workflow: In the Logic Apps designer, add the Agent node to your workflow.

Creation connection: If you don’t already have a connection, you’ll be prompted to create one. Make sure it’s a Foundry Project connection: select Foundry Project from the Agent Model Source drop-down, then provide your project endpoint and API key.

Invoke an existing Foundry agent: Once the Agent node is added, pick an agent from the Agent drop-down. Logic Apps defaults to the latest version and shows the agent’s configured model and instructions. You can invoke the agent as-is, or make changes from the designer, including adding Logic Apps tools to the Foundry Agent.

Or create a new agent: To create a new agent from the designer, provide an Agent Name and Model, then choose Create; the agent is created in Foundry. You can optionally add Instructions and Logic Apps tools before saving.

Configure Agent: When you choose to create a new agent, you add the Agent Name and Model and that allows you to Create that agent in Foundry. Optionally you can add Instructions and Logic Apps tools from the designer. The Agent is Created when you click on Create. You can invoke from Logic Apps or from Foundry portal as well.

Add tools: Logic Apps tools are how your agent takes action. A tool can include not just 1400 connectors, but also MCPs, workflows, custom code, Agents or APIs

Closing

Agents are only useful when they can act – and act autonomously, durably, and across the systems and timeframes that real business processes require. With Microsoft Foundry providing the agent platform, and Azure Logic Apps providing the triggers, workflows, connectors, webhooks, and agent-as-tool composition, AI capability turns into automated business processes.