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.
67 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.
Fabric's preview data engineering agent runs with the launching engineer's permissions. What to delegate first, which settings to pick, and what stays human.
Foundry routines run an agent on a timer, a schedule or a GitHub or Teams event. When to use them, when to use a workflow, and guardrails for unattended runs.
Foundry's preview egress controls attach ordered destination rules to a hosted agent. Why that limits prompt-injection damage, and how to roll it out safely.
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.
Claude hosted on Azure in Foundry now runs web fetch, web search, tool search and an MCP connector for you. Decide which belong behind your own gateway.
Hosted agents in Foundry Agent Service are GA. How they compare with Agent Framework on Container Apps or AKS on identity, networking, cold starts and tracing.
Foundry Model Router picks from OpenAI, Anthropic, DeepSeek, xAI and Meta models. Treat subsets, policy and model logging as governance, not tuning knobs.
The Agent Framework Harness bundles planning, memory, compaction, approvals and telemetry. When to accept its opinions and when a plain Agent is better.
Decide what an agent does when a tool fails, a step runs out of budget or grounding is weak before launch, and make the release check fail without it.
Typed state and checkpoints don't stop an agent paying twice: five places agent workflow state breaks at its boundaries, and patterns that hold.
Tool rules inside agent code drift once several teams build agents. Put identity, rate limits and tracing for MCP tools in Azure API Management instead.
How I'd run Microsoft Foundry agent changes like releases in April 2026: definitions in Git, versions from CI, evaluation gates and Agent Application promotion.
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.
Agents get confused when workflow state lives in the chat transcript. Four patterns for typed state, fresh context and code-owned transitions.
Foundry Agent Service went GA in mid-March 2026, but monitoring and tracing are still preview. What's governed now, and the controls I'd add first.
Agent reliability depends on which tools a model can reach. Four layers of tool policy (surface, schema, approval, budget) with Agent Framework code.
Agent Framework is still in preview and Semantic Kernel is in fix-and-stabilise mode: how to decide whether to stay, bridge, or rewrite in February 2026.
Most agent designs only need autonomy in one step. How to build the workflow around it with Agent Framework executors, switch-case edges and loop caps.
Azure AI Search knowledge bases now plan queries for you, in preview. When to hand over the RAG pipeline, when to keep building it, and how to test both.
Running Semantic Kernel agents in production in early 2026: which APIs are GA, which are preview, how to guard tool calls, and where Agent Framework fits.
Instead of a single LLM handling all tasks, multi-agent systems divide work among specialized agents that communicate and coordinate to achieve goals.
The Copilot agent framework represents a significant step toward enterprise AI automation, enabling organizations to build intelligent assistants that work…
Semantic Kernel abstracts the complexity of working with multiple AI services while providing extensibility through plugins. This allows developers to…
Traditional chatbots follow rigid conversation flows. AI agents powered by Copilot Studio understand intent, access knowledge bases, and execute multi-step…
AutoGen enables building sophisticated AI systems that can decompose complex tasks and collaborate to find solutions.
Long-term memory transforms one-shot interactions into ongoing relationships. Users feel understood when the AI remembers their preferences, past issues…
Multi-agent architectures shine for tasks requiring diverse expertise: research reports, code reviews, complex analysis, and creative projects. The key is…
At its core, an AI agent follows a simple loop: observe, think, act, repeat. Tools should be focused, well-documented, and handle errors gracefully.
Define clear responsibilities for each agent to avoid confusion and improve reliability. Multi-agent architectures excel at complex workflows where…
Planners analyze a user's goal and create an execution plan using available plugins. The Handlebars planner generates a template-based plan, while function…
The new agent framework introduces several critical improvements. First, native multi-agent orchestration allows agents to collaborate without custom…
Late-2024 safety research on scheming, alignment faking and prompt injection, translated into concrete controls for Azure teams shipping AI in 2025.
A practitioner's read on Anthropic's Model Context Protocol in January 2025: the primitives, a read-only SQL server in Python, and when not to use it.
Run an LLM tool-calling loop inside Azure Durable Functions so it checkpoints each step, stays within a step budget and waits hours for human approval.
Four multi-agent orchestration patterns, what Semantic Kernel, AutoGen 0.4 and Azure AI Agent Service offered for each in January 2025, and when to skip them.
A practical look at the agent tooling that really exists on 1 January 2025, what is still preview, and where to draw the line on autonomy.
Start with declarative agents for rapid prototyping and move to custom engines when you hit limitations.
Enterprise agents require these patterns to ensure security, compliance, and reliable operation at scale. Implement them from the start rather than…
Templates accelerate agent development by providing battle-tested patterns. Start with a template, customize for your needs, and iterate based on real usage.
Multi-agent systems unlock sophisticated automation capabilities. Start with simple patterns and evolve complexity as needed.
Azure AI Agent Service provides the foundation for building sophisticated AI systems that can reason, plan, and act autonomously. Start with simple agents…
Observability transforms AI agents from black boxes into understandable systems. Combine metrics, logs, and traces to gain complete visibility into agent…
Comprehensive audit logging is essential for AI agents in production. It enables debugging, ensures compliance, and provides the visibility needed to build…
Permission models for AI agents must be flexible yet secure. Combine RBAC for broad access patterns with capabilities for fine-grained, time-limited access.
Sandboxing is your last line of defense. Even trusted agents can behave unexpectedly - proper isolation ensures that unexpected behavior doesn't become a…
Agentic capabilities transform AI from a question-answering system into an autonomous problem-solver. The key is combining planning, tools, memory, and…
Computer Use is a significant step toward truly autonomous AI agents. Use it responsibly with appropriate safety controls.
Building reliable agents requires investment in error handling, recovery mechanisms, and observability. These patterns form the foundation for production AI…
AI Agent Best Practices: Lessons from Production
Single agents have limits. Multi-agent systems multiply capabilities. Today I'm exploring architectures for agent collaboration.
AI agents need memory to maintain context across interactions. Today I'm exploring how to implement effective memory systems.
AI agents often need to work with files - reading documents, processing data, generating outputs. Today I'm exploring safe and effective file handling patterns.
Code execution is one of the most powerful capabilities for AI agents - and one of the most dangerous. Today I'm exploring how to implement it safely.
Tools extend what AI agents can do beyond text generation. Today I'm exploring patterns for effective tool use in production agents.
Building single agents is one thing. Orchestrating multiple agents for complex workflows is another. Today I'm exploring production-ready orchestration…
AI agents are systems that can take actions autonomously to achieve goals. Today I'm exploring how to build agents from simple tool-using assistants to…
Azure AI Agent Service provides: Managed agent runtime No infrastructure to manage Built in tools Code execution, file handling, web search Memory…
How LangChain 0.1, AutoGen 0.2, CrewAI 0.1 and Semantic Kernel 1.0 differ in maturity, control and Azure OpenAI fit, and which one I'd pick for what.
A practical look at CrewAI 0.1.x with Azure OpenAI: how agents, tasks and sequential crews work, what's missing today, and when to choose it.
A practical look at AutoGen 0.2 with Azure OpenAI: wiring the config, stopping runaway conversations, sandboxing generated code and registering tools.
When a single GPT-4 agent stops being reliable, split it into specialists. A framework-free supervisor pattern on Azure OpenAI, with trade-offs and limits.
How to add retrieval grading, query rewriting, and groundedness checks to RAG on Azure OpenAI and Azure AI Search without tripling latency or cost.
The Azure OpenAI Assistants API — launched in preview on Azure shortly after the OpenAI DevDay announcement in November 2023 — is the stateful AI agent…
The most consequential design decision in a function-calling agent isn't the model you choose — it's how you write the tool definitions. The model selects…
Function calling, released last week with the 0613 model versions, gives AI agents a proper foundation — and I've been rebuilding some agent prototypes to…
Function calling patterns enable sophisticated AI agents. Tomorrow, I will cover building AI agents in more depth.