No agent Actions in Foundry agent setup

John Cummings 20 Reputation points
2026-08-07T21:46:17.7933333+00:00

In Foundry I have an agent. I'd like to add an Azure Logic Apps connector. Community information suggests I should see an Actions and Add Action option within the agent's setup. However, this is missing. I'm able to filter on, and see, various Logic app connectors when adding a tool at the Tools page, but wish to do so within the agent as various sources suggest there are more options available here. What do I need to do?

Azure Logic Apps
Azure Logic Apps

An Azure service that automates the access and use of data across clouds without writing code.

Answer accepted by question author

AI answer

2026-08-07T21:46:31.7+00:00

The missing Actions area is expected in some Foundry experiences because there are two different integration paths for Logic Apps, and they appear in different portals.

  • Connector-backed tools are added from Tools in the preview Foundry portal, not from the agent setup pane.
  • Azure Logic Apps actions/workflows are added from the agent’s Setup > Actions > Add flow in the classic Foundry portal.

What to do:

  1. If the goal is to add Logic App connectors as tools for the agent, use the preview Foundry portal flow:
    • Open the project and agent in the classic portal.
    • Select New Foundry to switch to the preview portal.
    • Open the agent, then go to Tools.
    • Select Connect a tool.
    • In Catalog, choose Registry > Logic app connectors.
    • Select the connector, then continue in Azure portal to register the MCP server and choose connector actions.
  2. If the goal is to add a Logic App workflow/action from inside the agent setup, use the classic Foundry portal flow:
    • Open the project.
    • Go to Build and customize > Agents.
    • Open the agent.
    • In Setup, scroll to Actions and select Add.
    • Choose Azure Logic Apps.
  3. If Actions is missing in the classic agent setup, check the model deployed for that agent.
    • The documented requirement is that the agent must use a model that supports actions.
    • If the Actions section is unavailable, deploy a GPT-4.1 model or earlier for the agent.

Important limitations that explain the behavior seen:

  • The experience to add an agent tool powered by Azure Logic Apps connectors is available only in the preview Foundry portal, not in the classic portal.
  • For connector-backed tools, only one connector can be selected for an agent tool.
  • This connector-based release supports only managed connectors that don’t use OAuth 2.0 authentication.
  • In the MCP server registration wizard, after selecting a connector, it can’t be changed or deleted to pick a different one.

So the practical answer is:

  • For connector catalog options, continue using Tools in preview Foundry.
  • For agent Setup > Actions, switch to classic Foundry and ensure the agent uses a model that supports actions; otherwise that section will not appear or will be unavailable.
AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Newest
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.