There’s been an important development in the Agentic RAG & Foundry IQ space that caught my attention, and I wanted to break it down — not just what was announced, but why it matters and how it fits into the bigger picture.

What’s New

If you’re new to fuzzing and want to learn the fundamentals first, check out our Fuzzing 101 course atgh.io/fuzzing101.

Continuous fuzzing is not a magic solution that solves all your problems . Even projects that have been enrolled in OSS-Fuzz for years can still hide critical bugs, and the reason is almost always the same: someone needs to keep an eye on coverage, write new harnesses for the code that nobody is reaching, and triage the crashes that come out the other end. In other words, fuzzing still needs a human in the loop.

So the natural question I kept asking myself was: how much of that human work can we actually hand over to an LLM agent?

That is what led me to build the Fuzzing Taskflow, an autonomous fuzzing pipeline for C/C++ projects. You only need to point it at a GitHub repository, and it does the rest: it identifies the suitable entrypoints, analyzes the build system, writes the harnesses, runs AFL++, reads the coverage reports, improves the harnesses, triages every crash, and writes a vulnerability report for each unique bug, all without a human babysitting it.

How to run it

The simplest way to run it’s just to go tohttps://github.com/GitHubSecurityLab/seclab-taskflows-fuzzingand start a codespace.

./scripts/fuzzing/run_fuzzing.sh PROJECT

./scripts/fuzzing/run_fuzzing.sh PROJECT

./scripts/fuzzing/run_fuzzing.sh tukaani-project/xz

Model selection

Some frontier models impose security guardrails on their outputs. For the fuzzing task flow, we useClaude Sonnet 5 by defaultbecause it passed all of our internal tests without issues. You can choose a different model by modifying the following file:src/seclab_taskflows_fuzzing/configs/model_config.yaml.

src/seclab_taskflows_fuzzing/configs/model_config.yaml

Key Takeaways

  1. If you’re new to fuzzing and want to learn the fundamentals first, check out our Fuzzing 101 course atgh.io/fuzzing101.
  2. Continuous fuzzing is not a magic solution that solves all your problems .
  3. So the natural question I kept asking myself was: how much of that human work can we actually hand over to an LLM agent?.
  4. That is what led me to build the Fuzzing Taskflow, an autonomous fuzzing pipeline for C/C++ projects.
  5. The Fuzzing Taskflow is built on top of theGitHub Security Lab Taskflow Agent, our framework for writing LLM-driven security automation, so the pipeline is expressed as a set of taskflows that an agent runs end to end.

Why This Matters

Traditional RAG is a static pipeline: query → retrieve → generate. Agentic RAG flips this — the agent decides when to retrieve, what to retrieve, and how many steps of retrieval to perform based on the complexity of the question. Foundry IQ (alongside Fabric IQ and Work IQ) provides the enterprise intelligence backbone that makes this context engineering practical at scale.

This development is particularly significant because it reflects the broader industry shift toward making AI more accessible, enterprise-ready, and integrated into existing workflows. For teams already invested in the Microsoft ecosystem, this is a clear signal of where the platform is heading.

My Take

The shift from static RAG to Agentic RAG is architecturally significant. Three patterns define the new state of the art: (1) Agent-driven retrieval planning — instead of a fixed retrieval step, the agent evaluates query complexity and dynamically decides whether to do single-hop retrieval, multi-hop reasoning across documents, or decompose into parallel sub-queries. (2) Foundry IQ as context layer — a unified intelligence surface that combines knowledge indices, enterprise memory, and organizational graph into a single query plane that agents can access through standard tool interfaces. (3) Context engineering over prompt engineering — the focus shifts from crafting clever prompts to building robust knowledge pipelines that deliver the right context at the right time. What’s technically compelling is how Foundry IQ integrates with Azure AI Search’s agentic retrieval mode — the search service itself becomes an agent that can re-rank, filter, and synthesize across heterogeneous data sources. Combined with AI Citadel’s governance controls, you get enterprise-grade knowledge access with full auditability.

Business Translation

For the C-Suite: Agentic RAG with Foundry IQ transforms your enterprise knowledge from a cost center into a revenue-generating intelligence asset. Traditional search gives you documents; Agentic RAG gives you answers grounded in your entire organizational memory. The ROI case: 80-90% reduction in knowledge worker research time, 3-5x improvement in decision quality (measured by accuracy and completeness vs. manual research). Foundry IQ’s enterprise intelligence layer means every AI agent you deploy gets smarter because it draws from the same organizational knowledge graph — creating compounding returns as your data and context grow. Organizations without this intelligence layer are building agents that operate in isolation, repeatedly solving problems your organization has already solved.

📖 Read the original article for the full details and official documentation.

Written by Cyril Bou-Harb — Solution Engineer, Cloud & AI at Microsoft. Opinions and analysis are my own and do not represent Microsoft’s official position.