foundry-evals

Evaluates Azure Foundry hosted agents via two-phase invoke-and-score with built-in evaluators.

5|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/aiappsgbb/awesome-gbb --skill foundry-evals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundry-evals
Source: https://github.com/aiappsgbb/awesome-gbb/tree/main/skills/foundry-evals
Command: npx skills add https://github.com/aiappsgbb/awesome-gbb --skill foundry-evals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires azure-ai-projects, azure-identity, python-dotenv, aiohttp, httpx, and includes references (resource) components.

What problem does it solve?

This Skill helps you reliably evaluate Azure Foundry hosted agents by separating response invocation from scoring, avoiding common endpoint routing and cold-start pitfalls.

Core Features & Use Cases

  • Two-phase invoke+score pattern: Invoke the hosted agent first, then score outputs using Foundry built-in evaluators.
  • Hosted-agent cold-start handling: Warm up with retry/backoff logic, enforce sequential invocation, and add pacing to prevent empty responses.
  • Production-grade eval operations: Supports dataset creation, evaluator configuration (including tool evaluators), judge model deployment requirements, and RBAC troubleshooting.

Quick Start

Use the foundry-evals skill to evaluate an already-deployed hosted agent against a set of test scenarios and generate Foundry eval scores.

Frequently Asked Questions about foundry-evals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate Azure Foundry hosted agents without getting empty responses from cold starts?

Evaluating Azure Foundry hosted agents requires a two-phase workflow that invokes the agent sequentially with cold-start-safe warmup using retry and backoff logic, then scores responses using Foundry built-in evaluators to ensure reliable post-deploy quality measurement.

What is the best way to score tool-grounding and citation quality for deployed AI agents?

Scoring tool-grounding and citation quality for deployed agents requires running Foundry built-in evaluators on enriched JSONL datasets containing tool definitions and tool_calls/tool_outputs, separating response invocation from scoring for accurate quality assessment.

How do I set up continuous evaluation gates for Azure Foundry agents?

Setting up continuous evaluation gates for Azure Foundry agents involves reusing Foundry eval definitions while updating per-run datasets, configuring built-in evaluators including tool evaluators, and ensuring sequential non-concurrent requests with pacing and retries.

Can I use Foundry built-in evaluators with custom test datasets for agent regression testing?

Yes, you can use Foundry built-in evaluators with custom JSONL datasets for agent regression testing by enriching dataset fields with tool_definitions and tool_calls/tool_outputs, then updating per-run datasets while reusing Foundry eval definitions.

Why does my Azure Foundry agent evaluation fail with RBAC or endpoint routing errors?

Azure Foundry agent evaluation can fail due to RBAC misconfigurations or incorrect endpoint routing, which requires using get_openai_client(agent_name=...) for correct agent endpoint invocation and applying RBAC troubleshooting steps for judge model deployment access.

Do I need a judge model deployment to run Foundry built-in evaluators on hosted agents?

Yes, running Foundry built-in evaluators on hosted agents requires a judge model deployment, along with proper RBAC configuration and correct agent endpoint invocation via get_openai_client(agent_name=...) to ensure successful scoring operations.