Fabric Data Agent Accuracy Is a Distribution, Not a Number
I asked a Fabric data agent 24 questions in three wordings, ten times each, on real AEMO data. It scored 82%, but only 39% of wordings were always right.
44 articles
I asked a Fabric data agent 24 questions in three wordings, ten times each, on real AEMO data. It scored 82%, but only 39% of wordings were always right.
ultrathink now runs at xhigh effort in Claude Code. I ran six exact-answer tasks 96 times from low to max: every level got them right; higher just cost more.
I hid five bugs in a real change and ran /code-review at low, medium, high and xhigh. Medium found all five for 15 cents. Here's what each level adds.
I gave Haiku 5.5 and Opus 5.5 the same five chores in this blog's repo. Both passed every run. Haiku cost 25 times less, and the diffs show what Opus adds.
GPT-6 arrived in Foundry ten weeks after GPT-5.6. Pin versions, gate on real queries, shadow traffic and plan retirements before you switch tiers on day one.
Fabric data agents now use GPT-5.1 and a Responses API client. What notebook, Foundry and app callers must change, and why you need a full eval re-run.
Foundry Model Router picks from OpenAI, Anthropic, DeepSeek, xAI and Meta models. Treat subsets, policy and model logging as governance, not tuning knobs.
GPT-5.6 in Foundry has a 5x price spread across Sol, Terra and Luna. Choose a tier for each workflow step, back it with eval gates, then pick deployment types.
Before an eval score becomes a product metric, join its verdicts to real outcomes like escalations and re-asks, and check whether failing answers do worse.
Good retrieval is wasted if users cannot verify the answer, so design RAG citations to be checkable, validated in code and measured like relevance.
How I sample real user queries by stratum, redact PII before anyone reads them, split off a holdout and keep the eval set current as the product changes.
Hybrid search is default RAG advice, but the BM25 leg has real costs; a three-way test on Azure AI Search shows which questions it rescues.
Once retrieval is ruled out, ungrounded answers fall into a few repeatable patterns: label them, fix one at a time and track completeness too.
A tool policy nobody tests is a comment. How to assert agent tool lists and approvals in CI, then gate tool use on a golden set of scenarios.
Make retrieval-first a team rule: an owned question set, a side-by-side index comparison on Azure AI Search, and a gate that fails on lost answers.
Most eval sets only ask questions the documents can answer. Add unanswerable, false-premise and stale-context cases, each with an expected behaviour.
The semantic ranker only reorders the top 50 results. A with-and-without test on a labelled set shows which RAG queries it rescues and which it just slows.
Treat answer quality like availability: define a good answer, agree a target with the product owner, and let the error budget decide when changes stop.
Profile each LLM request by segment, rank the cuts by quality risk, and keep only the token savings that survive a paired evaluation against the baseline.
Most wrong RAG answers start with the passages, not the prompt. A labelled question set and a retrieval-only triage on Azure AI Search show which one to fix.
How I compare a baseline and a candidate prompt or model on frozen context, count groundedness regressions per row, and treat fluency as a tie-breaker.
An LLM judge has its own biases: how to write pass/fail criteria, measure its kappa and false-pass rate against human labels, and know when to skip it.
A layered test strategy for LLM apps: stubbed unit tests per commit, pass-rate gates on PRs, nightly evaluator runs and red teaming before release.
Eight prompt engineering myths worth dropping in 2026, from verbose prompts to reflexive chain-of-thought and temperature rules, and what to measure instead.
Continuous evaluation maintains AI quality standards throughout the system lifecycle.
Regular evaluation with consistent metrics drives continuous improvement in AI quality.
A practical first project in Azure AI Foundry for data teams: hubs and projects, the preview azure-ai-projects SDK, and an evaluation loop from day one.
Late-2024 safety research on scheming, alignment faking and prompt injection, translated into concrete controls for Azure teams shipping AI in 2025.
Weights & Biases provides a comprehensive platform for LLM observability, evaluation, and collaboration. Its strength lies in combining experiment tracking…
Quality isn't one dimensional. Consider: Accuracy : Factual correctness Completeness : Covering all aspects Coherence : Logical flow and consistency…
Individual component metrics tell part of the story, but end-to-end evaluation measures how well your entire RAG pipeline performs as a system.
While context precision measures noise in retrieved results, context recall measures completeness. Are you retrieving all the documents needed to fully…
Context precision measures whether the retrieved documents are actually relevant to answering the question. High precision means less noise for the…
An answer can be factually correct and grounded in context but still fail to address what was actually asked. Answer relevancy measures how well the…
Faithfulness is perhaps the most critical metric for RAG systems. An unfaithful answer that hallucinates information not in the source documents can be…
While retrieval metrics measure what documents are found, generation metrics evaluate the quality of the synthesized answer. This guide covers metrics…
The retrieval component of RAG systems directly impacts generation quality. This guide provides a comprehensive overview of retrieval metrics and how to…
RAGAS (Retrieval Augmented Generation Assessment) is an open-source framework for evaluating RAG pipelines. This guide covers how to implement and use RAGAS…
Retrieval-Augmented Generation (RAG) systems combine retrieval and generation components, each requiring specific evaluation strategies. This guide covers…
Generic benchmarks like MMLU and HumanEval don't predict performance on your specific use cases. This guide covers how to design and implement task-specific…
MMLU (Massive Multitask Language Understanding) is one of the most cited LLM benchmarks. Understanding what it measures and its limitations is crucial for…
Understanding LLM benchmarks is essential for making informed model selection decisions. This guide covers the major benchmarks and how to interpret their…
Rigorous model evaluation is critical for production AI systems. This guide covers the major evaluation frameworks and how to implement comprehensive…
LLM benchmarking methodology matters more than the benchmark scores themselves, because the standard public benchmarks (MMLU for general knowledge…