Unable to add tool evaluators to agents or workflow in Microsoft Foundry

Anonymous
2026-07-13T17:57:31.3566667+00:00

Hi everyone,

I am encountering two distinct blockers while trying to set up evaluations for an agent in Azure AI Foundry (utilizing an agent connected to a custom MCP server and an Azure AI Search index).

Issue 1: "Failed to save continuous evaluation settings" for Tool Evaluators

When navigating to my agent under Continuous Evaluations (Production/Continuous Monitoring), I can successfully add and save behavioral evaluators (like Coherence, Customer Satisfaction, and Intent Resolution).

However, whenever I attempt to add any of the following tool-based metrics:

  • Tool Call Accuracy Evaluator
  • Tool Input Accuracy Evaluator
  • Tool Output Utilization Evaluator

The portal UI instantly throws the error: Failed to save continuous evaluation settings. Please try again.

  • Context: My agent relies on an Azure AI Search index and a remote custom MCP server endpoint. Why does the continuous evaluation configuration fail to save specifically when these tool evaluators are selected? Is there a hidden schema or dataset dependency required to register them in production monitoring?

Issue 2: "No runs" in Foundry Portal & Missing Logs in App Insights / LAW

For the baseline evaluators that did successfully save (Coherence, Customer Satisfaction), the Foundry Portal dashboard shows "No runs" across all tabs.

To troubleshoot, I checked the underlying workspace-based Application Insights instance and the linked Log Analytics Workspace (LAW), but no evaluation traces or metrics are appearing there either.

  • Questions:
    1. Do continuous evaluations require a minimum baseline threshold of production traffic or chat interactions before the evaluation pipeline executes and populates the "Runs" tab?
      1. Is there a specific background service, latency period, or diagnostic logging setting required to force the continuous evaluation engine to start piping metrics into App Insights/LAW?
        1. I am concurrently working on uploading a generated custom dataset for a batch evaluation. Is continuous evaluation completely separate from dataset-driven evaluation runs, and if so, how do I kickstart the tracking for it?

Any guidance or troubleshooting steps on resolving the tool evaluator UI crash and locating the missing evaluation telemetry would be greatly appreciated!


Hi everyone,

I am encountering two distinct blockers while trying to set up evaluations for an agent in Azure AI Foundry (utilizing an agent connected to a custom MCP server and an Azure AI Search index).

Issue 1: "Failed to save continuous evaluation settings" for Tool Evaluators

When navigating to my agent under Continuous Evaluations (Production/Continuous Monitoring), I can successfully add and save behavioral evaluators (like Coherence, Customer Satisfaction, and Intent Resolution).

However, whenever I attempt to add any of the following tool-based metrics:

  • Tool Call Accuracy Evaluator
  • Tool Input Accuracy Evaluator
  • Tool Output Utilization Evaluator

The portal UI instantly throws the error: Failed to save continuous evaluation settings. Please try again.

  • Context: My agent relies on an Azure AI Search index and a remote custom MCP server endpoint. Why does the continuous evaluation configuration fail to save specifically when these tool evaluators are selected? Is there a hidden schema or dataset dependency required to register them in production monitoring?

Issue 2: "No runs" in Foundry Portal & Missing Logs in App Insights / LAW

For the baseline evaluators that did successfully save (Coherence, Customer Satisfaction), the Foundry Portal dashboard shows "No runs" across all tabs.

To troubleshoot, I checked the underlying workspace-based Application Insights instance and the linked Log Analytics Workspace (LAW), but no evaluation traces or metrics are appearing there either.

  • Questions:
    1. Do continuous evaluations require a minimum baseline threshold of production traffic or chat interactions before the evaluation pipeline executes and populates the "Runs" tab?
      1. Is there a specific background service, latency period, or diagnostic logging setting required to force the continuous evaluation engine to start piping metrics into App Insights/LAW?
        1. I am concurrently working on uploading a generated custom dataset for a batch evaluation. Is continuous evaluation completely separate from dataset-driven evaluation runs, and if so, how do I kickstart the tracking for it?

Any guidance or troubleshooting steps on resolving the tool evaluator UI crash and locating the missing evaluation telemetry would be greatly appreciated!


Azure OpenAI in Foundry Models

Answer accepted by question author
Anshika Varshney 15,625 Reputation points Microsoft External Staff Moderator
2026-07-14T17:27:52.42+00:00

Hello @Anonymous

Thanks for reaching out.

For Issue 1, the tool-based evaluators (Tool Call Accuracy, Tool Input Accuracy, and Tool Output Utilization) depend on tool invocation telemetry being available and correctly captured. Since your agent uses an Azure AI Search index and a custom remote MCP server, the "Failed to save continuous evaluation settings" error may indicate that the required tool-trace data isn't being detected or that the current agent configuration doesn't meet the prerequisites expected by these evaluators. I recommend checking the browser developer console and network traces for any detailed error messages, and verifying that tool calls are being logged successfully.

For Issue 2, continuous evaluation is separate from dataset-driven batch evaluations. Continuous evaluations rely on actual runtime interactions and telemetry from your deployed agent. If the portal shows**"No runs"**, verify that:

  • Production traffic is reaching the agent.
  • Azure AI Foundry tracing/monitoring is enabled.
  • Application Insights and the linked Log Analytics Workspace are correctly connected and receiving telemetry.
  • Sufficient interactions have occurred since enabling continuous evaluation.

To help narrow this down, could you share:

  • The Azure AI Foundry region.
  • Whether tracing/observability is enabled for the project.
  • A screenshot of the error shown when saving the tool evaluators.
  • Any errors captured in the browser's Developer Tools (Network/Console tab).

This information will help determine whether the issue is a configuration limitation, telemetry requirement, or a portal-side problem.

Thankyou!

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Christos Panagiotidis 3,551 Reputation points
    2026-07-14T07:33:56.7066667+00:00

    Hi, I would treat the save failure and the No runs result as two separate checks. Tool Call/Input/Output evaluators need traces that contain the expected tool-call fields; they cannot evaluate ordinary chat rows with no tool span. First confirm Application Insights tracing is enabled on the same Foundry project and that a fresh agent run shows tool spans and inputs/outputs in observability. Then create a small batch evaluation from an explicit dataset to validate the evaluator independently of continuous evaluation. Continuous evaluation is asynchronous and only processes new eligible traffic after configuration—it does not backfill old runs. If tool traces exist but the evaluator still will not save, capture the browser request/correlation ID and open a Foundry support case, because that points to project/preview backend state rather than the agent prompt.

    Was this answer helpful?

    0 comments No comments

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.