[LI (ktz03)]

Motivation & Context

The Azure AI Search sample guide combines mutually exclusive index_name and knowledge_base_name arguments in its agentic example, which raises SettingNotFoundError during construction. It also lists obsolete script names and constructor options.

Description & Review Guide

• What are the major changes? Document existing-Knowledge-Base and index-backed setup separately, align parameter names/defaults and Azure CLI credential spelling with the shipped samples, and correct the sample commands and cross-reference.
• What is the impact of these changes? Only the README and a sample explanatory string change. Five local public-constructor controls cover the exact README calls, both shipped agentic setup calls and the default result limit. The old combined call raises SettingNotFoundError; documented argument names now match the current constructor. Ruff checks and source compilation pass on Windows with cached Azure Search SDK 12.0.0. No full sample, cloud retrieval, model, authentication, preview SDK, package build or full-suite run was performed.
• What do you want reviewers to focus on? The two supported setup paths and their required arguments match AzureAISearchContextProvider, and the documented commands name files that exist.

Related Issue

N/A - trivial change. These are obvious documentation corrections to match existing public constructors and shipped sample names. Existing Knowledge Base support was added in #2464; this change preserves that behavior and the initialization/sample work in #5021 and #2369.

AI Assistance

• No material AI assistance was used.
• This is an AI-assisted contribution. I reviewed, understood, and verified all submitted content and accept responsibility for it.

AI assistance details: Documentation, example verification, and this PR description.

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR links to an agreed issue with no competing open PR, or the Related Issue section documents a trivial-change or repository-automation exception.
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

[Copilot]

🟢 Approval recommended

The documentation-only corrections match the existing implementation and samples, with no unresolved findings.

No open issues 🎉

What changed in this PR

Corrects Azure AI Search sample documentation to match the existing provider API and shipped examples. No runtime behavior changes.

Changes:

• Separates existing Knowledge Base and index-backed agentic setup.
• Corrects parameter names, defaults, authentication guidance, and sample commands.
• Fixes the semantic sample reference in the agentic sample’s explanatory text.

File	Description
python/​samples/​02-agents/​context_providers/​azure_ai_search/​search_context_agentic.py	Corrects a filename reference in explanatory text.
python/​samples/​02-agents/​context_providers/​azure_ai_search/​README.md	Aligns setup instructions and examples with the current API.

_{Review effort: Balanced}

[Eduard van Valkenburg (eavanvalkenburg)]

The setup split and parameter corrections are otherwise sound, but the revised optional-key authentication path remains broken in the README examples.

[Eduard van Valkenburg (eavanvalkenburg)]

The README now says omitting AZURE_SEARCH_API_KEY uses AzureCliCredential, but this credential is only passed to the Foundry client. Both AzureAISearchContextProvider examples still pass api_key=search_key without a fallback credential, so construction raises when the key is absent. Please create/reuse an AzureCliCredential and pass it to the provider when no API key is configured, matching the shipped semantic and agentic samples.