Files
Eduard van Valkenburg 1e350ea22f Python: [BREAKING] PR2 — Wire context provider pipeline, remove old types, update all consumers (#3850)
* PR2: Wire context provider pipeline and update all internal consumers

- Replace AgentThread with AgentSession across all packages
- Replace ContextProvider with BaseContextProvider across all packages
- Replace context_provider param with context_providers (Sequence)
- Replace thread= with session= in run() signatures
- Replace get_new_thread() with create_session()
- Add get_session(service_session_id) to agent interface
- DurableAgentThread -> DurableAgentSession
- Remove _notify_thread_of_new_messages from WorkflowAgent
- Wire before_run/after_run context provider pipeline in RawAgent
- Auto-inject InMemoryHistoryProvider when no providers configured

* fix: update all tests for context provider pipeline, fix lazy-loaders, remove old test files

* refactor: update all sample files for context provider pipeline (AgentThread→AgentSession, ContextProvider→BaseContextProvider)

* fix: update remaining ag-ui references (client docstring, getting_started sample)

* fix: make get_session service_session_id keyword-only to avoid confusion with session_id

* refactor: rename _RunContext.thread_messages to session_messages

* refactor: remove _threads.py, _memory.py, and old provider files; migrate devui to use plain message lists

* rename: remove _new_ prefix from test files

* refactor: rewrite SlidingWindowChatMessageStore as SlidingWindowHistoryProvider(InMemoryHistoryProvider)

* fix: read full history from session state directly instead of reaching into provider internals

* fix: update stale .pyi stubs, sample imports, and README references for new provider types

* fix: remove stale message_store, _notify_thread_of_new_messages, and session_id.key references in samples

* refactor: merge context_providers and sessions sample folders into sessions, remove aggregate_context_provider

* refactor: UserInfoMemory stores state in session.state instead of instance attributes

* feat: add Pydantic BaseModel support to session state serialization

Pydantic models stored in session.state are now automatically serialized
via model_dump() and restored via model_validate() during to_dict()/from_dict()
round-trips. Models are auto-registered on first serialization; use
register_state_type() for cold-start deserialization.

Also export register_state_type as a public API.

* fix mem0

* Update sample README links and descriptions for session terminology

- Replace 'thread' with 'session' in sample descriptions across all READMEs
- Update file links for renamed samples (mem0_sessions, redis_sessions, etc.)
- Fix Threads section → Sessions section in main samples/README.md
- Update tools, middleware, workflows, durabletask, azure_functions READMEs
- Update architecture diagrams in concepts/tools/README.md
- Update migration guides (autogen, semantic-kernel)

* Fix broken Redis README link to renamed sample

* Fix Mem0 OSS client search: pass scoping params as direct kwargs

AsyncMemory (OSS) expects user_id/agent_id/run_id as direct kwargs,
while AsyncMemoryClient (Platform) expects them in a filters dict.
Adds tests for both client types.

Port of fix from #3844 to new Mem0ContextProvider.

* Fix rebase issues: restore missing _conversation_state.py and checkpoint decode logic

- Add back _conversation_state.py (encode/decode_chat_messages) lost in rebase
- Fix on_checkpoint_restore to decode cache/conversation with decode_chat_messages
- Fix on_checkpoint_restore to use decode_checkpoint_value for pending requests
- Add tests/workflow/__init__.py for relative import support
- Fix test_agent_executor checkpoint selection (checkpoints[1] not superstep)

* Add STORES_BY_DEFAULT ClassVar to skip redundant InMemoryHistoryProvider injection

Chat clients that store history server-side by default (OpenAI Responses API,
Azure AI Agent) now declare STORES_BY_DEFAULT = True. The agent checks this
during auto-injection and skips InMemoryHistoryProvider unless the user
explicitly sets store=False.

* Fix broken markdown links in azure_ai and redis READMEs

* Fix getting-started samples to use session API instead of removed thread/ContextProvider API

* updates to workflow as agent

* fix group chat import

* Rename Thread→Session throughout, fix service_session_id propagation, remove stale AGUIThread

- Fix: Propagate conversation_id from ChatResponse back to session.service_session_id
  in both streaming and non-streaming paths in _agents.py
- Rename AgentThreadException → AgentSessionException
- Remove stale AGUIThread from ag_ui lazy-loader
- Rename use_service_thread → use_service_session in ag-ui package
- Rename test functions from *_thread_* to *_session_*
- Rename sample files from *_thread* to *_session*
- Update docstrings and comments: thread → session
- Update _mcp.py kwargs filter: add 'session' alongside 'thread'
- Fix ContinuationToken docstring example: thread=thread → session=session
- Fix _clients.py docstring: 'Agent threads' → 'Agent sessions'

* Fix broken markdown links after thread→session file renames

* fix azure ai test
1e350ea22f · 2026-02-12 21:00:32 +00:00
History
..

Azure AI Search Context Provider Examples

Azure AI Search context provider enables Retrieval Augmented Generation (RAG) with your agents by retrieving relevant documents from Azure AI Search indexes. It supports two search modes optimized for different use cases.

This folder contains examples demonstrating how to use the Azure AI Search context provider with the Agent Framework.

Examples

File Description
azure_ai_with_search_context_agentic.py Agentic mode (recommended for most scenarios): Uses Knowledge Bases in Azure AI Search for query planning and multi-hop reasoning. Provides more accurate results through intelligent retrieval with automatic query reformulation. Slightly slower with more token consumption for query planning. Learn more
azure_ai_with_search_context_semantic.py Semantic mode (fast queries): Fast hybrid search combining vector and keyword search with semantic ranking. Returns raw search results as context. Best for scenarios where speed is critical and simple retrieval is sufficient.

Installation

pip install agent-framework-azure-ai-search agent-framework-azure-ai

Prerequisites

Required Resources

  1. Azure AI Search service with a search index containing your documents

  2. Azure AI Foundry project with a model deployment

  3. For Agentic mode only: Azure OpenAI resource for Knowledge Base model calls

Authentication

Both examples support two authentication methods:

  • API Key: Set AZURE_SEARCH_API_KEY environment variable
  • Entra ID (Managed Identity): Uses DefaultAzureCredential when API key is not provided

Run az login if using Entra ID authentication.

Configuration

Environment Variables

Common (both modes):

  • AZURE_SEARCH_ENDPOINT: Your Azure AI Search endpoint (e.g., https://myservice.search.windows.net)
  • AZURE_SEARCH_INDEX_NAME: Name of your search index
  • AZURE_AI_PROJECT_ENDPOINT: Your Azure AI Foundry project endpoint
  • AZURE_AI_MODEL_DEPLOYMENT_NAME: Model deployment name (e.g., gpt-4o, defaults to gpt-4o)
  • AZURE_SEARCH_API_KEY: (Optional) Your search API key - if not provided, uses DefaultAzureCredential

Agentic mode only:

  • AZURE_SEARCH_KNOWLEDGE_BASE_NAME: Name of your Knowledge Base in Azure AI Search
  • AZURE_OPENAI_RESOURCE_URL: Your Azure OpenAI resource URL (e.g., https://myresource.openai.azure.com)
    • Important: This is different from AZURE_AI_PROJECT_ENDPOINT - Knowledge Base needs the OpenAI endpoint for model calls

Example .env file

For Semantic Mode:

AZURE_SEARCH_ENDPOINT=https://myservice.search.windows.net
AZURE_SEARCH_INDEX_NAME=my-index
AZURE_AI_PROJECT_ENDPOINT=https://<resource-name>.services.ai.azure.com/api/projects/<project-name>
AZURE_AI_MODEL_DEPLOYMENT_NAME=gpt-4o
# Optional - omit to use Entra ID
AZURE_SEARCH_API_KEY=your-search-key

For Agentic Mode (add these to semantic mode variables):

AZURE_SEARCH_KNOWLEDGE_BASE_NAME=my-knowledge-base
AZURE_OPENAI_RESOURCE_URL=https://myresource.openai.azure.com

Search Modes Comparison

Feature Semantic Mode Agentic Mode
Speed Fast Slower (query planning overhead)
Token Usage Lower Higher (query reformulation)
Retrieval Strategy Hybrid search + semantic ranking Multi-hop reasoning with Knowledge Base
Query Handling Direct search Automatic query reformulation
Best For Simple queries, speed-critical apps Complex queries, multi-document reasoning
Additional Setup None Requires Knowledge Base + OpenAI resource

When to Use Semantic Mode

  • Simple queries where direct keyword/vector search is sufficient
  • Speed is critical and you need low latency
  • Straightforward retrieval from single documents
  • Lower token costs are important

When to Use Agentic Mode

  • Complex queries requiring multi-hop reasoning
  • Cross-document analysis where information spans multiple sources
  • Ambiguous queries that benefit from automatic reformulation
  • Higher accuracy is more important than speed
  • You need intelligent query planning and document synthesis

How the Examples Work

Semantic Mode Flow

  1. User query is sent to Azure AI Search
  2. Hybrid search (vector + keyword) retrieves relevant documents
  3. Semantic ranking reorders results for relevance
  4. Top-k documents are returned as context
  5. Agent generates response using retrieved context

Agentic Mode Flow

  1. User query is sent to the Knowledge Base
  2. Knowledge Base plans the retrieval strategy
  3. Multiple search queries may be executed (multi-hop)
  4. Retrieved information is synthesized
  5. Enhanced context is provided to the agent
  6. Agent generates response with comprehensive context

Code Example

Semantic Mode

from agent_framework import Agent
from agent_framework.azure import AzureAIAgentClient, AzureAISearchContextProvider
from azure.identity.aio import DefaultAzureCredential

# Create search provider with semantic mode (default)
search_provider = AzureAISearchContextProvider(
    endpoint=search_endpoint,
    index_name=index_name,
    api_key=search_key,  # Or use credential for Entra ID
    mode="semantic",  # Default mode
    top_k=3,  # Number of documents to retrieve
)

# Create agent with search context
async with AzureAIAgentClient(credential=DefaultAzureCredential()) as client:
    async with Agent(
        client=client,
        model=model_deployment,
        context_providers=[search_provider],
    ) as agent:
        response = await agent.run("What information is in the knowledge base?")

Agentic Mode

from agent_framework.azure import AzureAISearchContextProvider

# Create search provider with agentic mode
search_provider = AzureAISearchContextProvider(
    endpoint=search_endpoint,
    index_name=index_name,
    api_key=search_key,
    mode="agentic",  # Enable agentic retrieval
    knowledge_base_name=knowledge_base_name,
    azure_openai_resource_url=azure_openai_resource_url,
    top_k=5,
)

# Use with agent (same as semantic mode)
async with Agent(
    client=client,
    model=model_deployment,
    context_providers=[search_provider],
) as agent:
    response = await agent.run("Analyze and compare topics across documents")

Running the Examples

  1. Set up environment variables (see Configuration section above)

  2. Ensure you have an Azure AI Search index with documents:

    # Verify your index exists
    curl -X GET "https://myservice.search.windows.net/indexes/my-index?api-version=2024-07-01" \
         -H "api-key: YOUR_API_KEY"
    
  3. For agentic mode: Create a Knowledge Base in Azure AI Search

  4. Run the examples:

    # Semantic mode (fast, simple)
    python azure_ai_with_search_context_semantic.py
    
    # Agentic mode (intelligent, complex)
    python azure_ai_with_search_context_agentic.py
    

Key Parameters

Common Parameters

  • endpoint: Azure AI Search service endpoint
  • index_name: Name of the search index
  • api_key: API key for authentication (optional, can use credential instead)
  • credential: Azure credential for Entra ID auth (e.g., DefaultAzureCredential())
  • mode: Search mode - "semantic" (default) or "agentic"
  • top_k: Number of documents to retrieve (default: 3 for semantic, 5 for agentic)

Semantic Mode Parameters

  • semantic_configuration: Name of semantic configuration in your index (optional)
  • query_type: Query type - "semantic" for semantic search (default)

Agentic Mode Parameters

  • knowledge_base_name: Name of your Knowledge Base (required)
  • azure_openai_resource_url: Azure OpenAI resource URL (required)
  • max_search_queries: Maximum number of search queries to generate (default: 3)

Troubleshooting

Common Issues

  1. Authentication errors

    • Ensure AZURE_SEARCH_API_KEY is set, or run az login for Entra ID auth
    • Verify your credentials have search permissions
  2. Index not found

    • Verify AZURE_SEARCH_INDEX_NAME matches your index name exactly
    • Check that the index exists and contains documents
  3. Agentic mode errors

    • Ensure AZURE_SEARCH_KNOWLEDGE_BASE_NAME is correctly configured
    • Verify AZURE_OPENAI_RESOURCE_URL points to your Azure OpenAI resource (not AI Foundry endpoint)
    • Check that your OpenAI resource has the necessary model deployments
  4. No results returned

    • Verify your index has documents with vector embeddings (for semantic/hybrid search)
    • Check that your queries match the content in your index
    • Try increasing top_k parameter
  5. Slow responses in agentic mode

    • This is expected - agentic mode trades speed for accuracy
    • Reduce max_search_queries if needed
    • Consider semantic mode for speed-critical applications

Performance Tips

  • Use semantic mode as the default for most scenarios - it's fast and effective
  • Switch to agentic mode when you need multi-hop reasoning or complex queries
  • Adjust top_k based on your needs - higher values provide more context but increase token usage
  • Enable semantic configuration in your index for better semantic ranking
  • Use Entra ID authentication in production for better security

Additional Resources