Azure Cognitive Search is now called Azure AI Search, and it has moved from a single-query search engine to a service with two modes: classic search and agentic retrieval. Microsoft's documentation describes classic search as one request against one index, and agentic retrieval as a multi-query pipeline in which an LLM can plan subqueries, run them in parallel across one or more knowledge sources, rerank them and return grounded results for an agent to use. For most enterprises the practical question is no longer "search or AI" but which mode fits which workload, and what an agentic AI layer should add on top.
Our view is that retrieval and action should be designed separately. Azure AI Search should stay the governed retrieval layer, agentic retrieval should be switched on where questions are genuinely multi-part, and an agent layer should act on the answers only inside approved policy. This guide covers what changed, a decision table, governance and cost, an adoption sequence and the trade-offs.
They are the same product. Microsoft's FAQ states that Azure Search, Azure Cognitive Search and Azure AI Search are one product, rebranded in October 2019 and again in October 2023, and that you may still see the former names in programmatic interfaces. Microsoft's "What's new" page lists the sequence as Azure Search (March 2015), Azure Cognitive Search (October 2019) and Azure AI Search (November 2023). The semantic search feature was renamed semantic ranker in the same month. If your architecture documents still say "Cognitive Search", they describe the same service, but they may also describe a pre-agentic design.
Microsoft now describes Azure AI Search as a fully managed, cloud-hosted service that connects enterprise data to AI so that agents and LLMs can produce grounded answers. It supports full-text, vector, hybrid and multimodal queries, AI enrichment, relevance tuning, and security through Microsoft Entra ID, Azure Private Link, document-level access control and role-based access. It also underpins Foundry IQ, Microsoft's managed knowledge layer for agents in the Foundry portal. Source: Microsoft Learn, What is Azure AI Search.
Agentic retrieval is a query pipeline that targets a knowledge base rather than a single index. A knowledge base references one or more knowledge sources, an optional LLM for query planning and answer synthesis, and parameters that govern retrieval. Microsoft's overview describes four steps: your application calls the knowledge base with a query and conversation history; the knowledge base plans focused subqueries (skipped at minimal reasoning effort); subqueries run simultaneously as keyword, vector or hybrid searches with semantic reranking; and the results are merged into a unified response, with optional source references and an activity log.
Knowledge sources can be indexed, backed by a search index on your service, or remote, retrieved live from an external platform at query time. Microsoft's November 2025 update added indexed OneLake, indexed SharePoint, remote SharePoint and web knowledge sources. For retrieval that must respect who is asking, Microsoft notes that remote SharePoint is designed for user-based permission inheritance. Source: Microsoft Learn, Agentic retrieval in Azure AI Search.
Teams that need enterprise search across unstructured knowledge with role-aware results can also look at AgentSearch, an ElixirData agent for context-aware search across unstructured knowledge bases that stays inside existing permissions.
Microsoft's guidance is direct: if you are building a traditional app without an agent or chatbot, direct index queries can meet most needs with lower cost and complexity. Agentic retrieval is for work across multiple knowledge sources or more advanced scenarios, and it adds latency compared with a single-query pipeline. The table below combines Microsoft's documented behaviour with our recommendation.
| Option | What it does | When it fits | Current status (Microsoft Learn) |
|---|---|---|---|
| Classic search | One request against one predefined index, ranked results in one response, no LLM planning | Predictable, low-latency lookups; traditional search apps | Generally available |
| Agentic retrieval | LLM-assisted or user-provided plan, parallel subqueries across knowledge sources, merged grounding data | Multi-part questions, chat context, several sources, agent grounding | Generally available, with some capabilities in preview (query planning, answer synthesis, higher reasoning effort) |
| Agent layer on top | Reasons over retrieved content and triggers actions in other systems | When the answer must start a workflow, such as a ticket or an approval | Your own design; keep actions inside policy and logged |
Two production details matter. Microsoft says to use the 2026-04-01 REST API for production workloads that use generally available knowledge source types with minimal, extractive retrieval, and the 2026-08-01-preview API for preview capabilities, which are not covered by a service-level agreement. Objects created in the Azure or Foundry portals may use preview schemas and need migration when you move to the generally available API.
| Change | When | Why it matters for your design |
|---|---|---|
| Product renamed Azure AI Search | November 2023 | Update documents, tags and runbooks; API strings may still show the old name |
| Semantic search renamed semantic ranker | November 2023 | Same L2 reranking, clearer name; it is used inside agentic retrieval |
| Knowledge agents renamed knowledge bases | November 2025 | Breaking changes to REST routes and properties; follow Microsoft's migration guide |
| New knowledge source types (OneLake, SharePoint, web) | November 2025 | Retrieval can span more of the estate without copying everything into one index |
| Generally available agentic retrieval path in the 2026-04-01 REST API | 2026 | A supported route for minimal, extractive retrieval in production |
Source: Microsoft Learn, What's new in Azure AI Search.
Retrieval answers a question. An agent layer decides what to do with the answer. In the original version of this article we described this as autonomy, contextual reasoning and action-oriented outcomes, and that framing still holds, with one correction: reasoning is no longer absent from the Microsoft stack, because agentic retrieval itself can plan queries with an LLM. What Azure AI Search does not do for you is execute business actions, so that is where AI agents and agentic workflows come in.
These are illustrative patterns, not Microsoft features. For build, orchestration and governance of such agents we use ElixirClaw, an agentic OS platform to build, orchestrate and govern AI agents and automation workflows while keeping humans in control.
To map one search-driven decision your agents should make, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.
Yes. Microsoft states they are the same product, renamed in October 2019 and again in October 2023, and former names can still appear at the programmatic level.
It is a multi-query pipeline that targets a knowledge base, plans subqueries, runs them in parallel across knowledge sources, reranks them semantically and returns merged grounding data for agents and apps.
Partly. Microsoft lists it as generally available with some capabilities in preview. Query planning, answer synthesis and non-minimal reasoning effort are preview features.
It is billed differently. Classic search is query based, while agentic retrieval is token based and also incurs Azure OpenAI charges for planning and answer synthesis.
No. Microsoft states that indexed knowledge sources use the same indexing and query engines as classic search, so existing indexes can sit behind a knowledge base.
Disclosure: XenonStack builds ElixirClaw, ElixirData and the ElixirData agents mentioned in this article.