Do you need an evaluation dataset?
Create a dataset when you want a stable test set that you can rerun against different model, prompt, or agent versions. Reusable datasets work well for regression testing, CI/CD quality gates, and comparisons across evaluation runs. You don’t always need a dataset. If your Foundry agent already has responses or your application emits traces to Application Insights, you can evaluate that data where it exists. See Evaluate interactions by response ID and Evaluate traces.How Foundry uses evaluation data
In a JSONL dataset, themessages field represents model or agent
interactions. Each message identifies a role and its content.
If your dataset contains completed responses, Foundry evaluates those
responses directly. If you run the evaluation against a model or agent,
Foundry generates a new response for each input and evaluates that response.
Any response already stored in the dataset is ignored.
For example, consider a user who can’t sign in. The agent asks which error
appears, the user says their password is rejected, and the agent recommends a
password reset. Turn-level evaluation scores an individual agent response,
such as the password-reset guidance, by using preceding messages as context.
Conversation-level evaluation scores the complete interaction.
The evaluation_level setting on the run controls the scoring granularity.
The dataset and selected evaluators must support that level. For details, see
Choose an evaluation level.
For standard columns and examples, see
Evaluation dataset schema.