Microsoft Agent Framework (Python) — Model Providers

Model Providers — Python

Every chat client in agent-framework implements the same SupportsChatGetResponse protocol, so Agent(client=...) accepts them interchangeably. The import is always agent_framework.<provider>.<ClassName> — no Azure SDK import is required for any of these. The Azure SDK only becomes relevant for authentication (azure-identity) or for Azure-specific storage providers.

This page was verified against agent-framework-core==1.2.2 and provider packages at 1.0.0b260429 (April 2026). Each sub-package is imported lazily from the agent_framework.<provider> namespace — you install the provider package and import from agent_framework.<provider>.

Provider index

Provider	Package	Import path	Status
OpenAI	agent-framework-openai	agent_framework.openai	Stable
Azure OpenAI	agent-framework-openai	agent_framework.openai (same client)	Stable
Microsoft Foundry	agent-framework-foundry	agent_framework.foundry	Stable
Foundry Local	agent-framework-foundry-local	agent_framework.foundry	Beta
Anthropic	agent-framework-anthropic	agent_framework.anthropic	Beta
Anthropic on Bedrock	agent-framework-anthropic	agent_framework.anthropic	Beta
Anthropic on Vertex	agent-framework-anthropic	agent_framework.anthropic	Beta
Claude Code SDK	agent-framework-claude	agent_framework.anthropic	Beta
Ollama	agent-framework-ollama	agent_framework.ollama	Beta
Amazon Bedrock (native)	agent-framework-bedrock	agent_framework.amazon	Beta
GitHub Copilot	agent-framework-github-copilot	agent_framework.github	Beta
Copilot Studio	agent-framework-copilotstudio	agent_framework.microsoft	Beta

OpenAI (and Azure OpenAI)

A single class — OpenAIChatClient — drives both OpenAI and Azure OpenAI. The routing is determined by which arguments you pass: credential= or azure_endpoint= select Azure; otherwise it stays on OpenAI.

from agent_framework import Agent
from agent_framework.openai import OpenAIChatClient

# OpenAI — reads OPENAI_API_KEY and OPENAI_CHAT_MODEL from env
agent = Agent(
    client=OpenAIChatClient(),
    instructions="You are a helpful assistant.",
)
response = await agent.run("Hello")
print(response.text)

Responses API vs Chat Completions API: OpenAIChatClient uses the Responses API (recommended — supports hosted tools like file search, code interpreter). OpenAIChatCompletionClient uses the classic Chat Completions API for OpenAI-compatible gateways that don’t support /responses.

from agent_framework.openai import OpenAIChatClient, OpenAIChatCompletionClient

responses_client = OpenAIChatClient(model="gpt-5")            # /responses
completions_client = OpenAIChatCompletionClient(model="gpt-5")  # /chat/completions

Azure OpenAI with Entra ID (passwordless):

import os
from agent_framework import Agent
from agent_framework.openai import OpenAIChatClient
from azure.identity.aio import AzureCliCredential

credential = AzureCliCredential()  # or DefaultAzureCredential()
agent = Agent(
    client=OpenAIChatClient(
        model=os.environ["AZURE_OPENAI_CHAT_MODEL"],
        azure_endpoint=os.environ["AZURE_OPENAI_ENDPOINT"],
        api_version=os.environ.get("AZURE_OPENAI_API_VERSION"),
        credential=credential,
    ),
    instructions="You are a helpful assistant.",
)

Azure OpenAI with API key:

import os
from agent_framework.openai import OpenAIChatClient

client = OpenAIChatClient(
    model=os.environ["AZURE_OPENAI_CHAT_MODEL"],
    azure_endpoint=os.environ["AZURE_OPENAI_ENDPOINT"],
    api_key=os.environ["AZURE_OPENAI_API_KEY"],
)

Full-URL override (useful for reverse proxies): pass base_url="https://…/openai/v1" instead of azure_endpoint=.

Environment-variable cascade resolved inside the constructor:

Argument	OpenAI env var	Azure env var
model	OPENAI_CHAT_MODEL → OPENAI_MODEL	AZURE_OPENAI_CHAT_MODEL → AZURE_OPENAI_MODEL
api_key	OPENAI_API_KEY	AZURE_OPENAI_API_KEY
base_url	OPENAI_BASE_URL	AZURE_OPENAI_BASE_URL
azure_endpoint	—	AZURE_OPENAI_ENDPOINT
api_version	—	AZURE_OPENAI_API_VERSION
org_id	OPENAI_ORG_ID	—

Microsoft Foundry

Microsoft Foundry (formerly Azure AI Foundry) provides project-scoped model deployments plus first-party evaluation and agent hosting. The client talks to the OpenAI-compatible endpoint surfaced by the Foundry project.

from agent_framework import Agent
from agent_framework.foundry import FoundryChatClient
from azure.identity.aio import AzureCliCredential

async with AzureCliCredential() as credential:
    agent = Agent(
        client=FoundryChatClient(
            project_endpoint="https://<project>.services.ai.azure.com",
            model="gpt-4o-mini",
            credential=credential,
        ),
        instructions="You are a helpful assistant.",
    )
    response = await agent.run("Summarise agent-framework 1.2.2 in one line.")

Env vars: FOUNDRY_PROJECT_ENDPOINT, FOUNDRY_MODEL.

If you already hold an AIProjectClient, pass it directly and skip endpoint/credential:

from azure.ai.projects import AIProjectClient

project = AIProjectClient(endpoint=..., credential=...)
client = FoundryChatClient(project_client=project, model="gpt-4o-mini")

Service-managed agents. Use FoundryAgent when you want the agent’s identity, threads, and tool definitions to live in Foundry (not in your process):

from agent_framework.foundry import FoundryAgent

foundry_agent = FoundryAgent(
    project_endpoint="https://<project>.services.ai.azure.com",
    agent_name="contract-reviewer",
    agent_version="1.0",
    credential=credential,
)
response = await foundry_agent.run("Review contract.pdf")

Foundry Local

FoundryLocalClient targets the local Foundry inference runtime (GGUF/ONNX models served by foundry-local). Useful for offline development and compliance scenarios.

from agent_framework.foundry import FoundryLocalClient
from agent_framework import Agent

agent = Agent(
    client=FoundryLocalClient(model="Phi-3.5-mini-instruct"),
    instructions="You are a private offline assistant.",
)

Anthropic

Three transports — direct Anthropic API, Anthropic on AWS Bedrock, Anthropic on Google Vertex. All three implement the same chat-client protocol, so only the construction differs.

from agent_framework import Agent
from agent_framework.anthropic import (
    AnthropicClient,          # api.anthropic.com; reads ANTHROPIC_API_KEY
    AnthropicBedrockClient,   # Anthropic via AWS Bedrock
    AnthropicVertexClient,    # Anthropic via Google Vertex AI
)

agent = Agent(
    client=AnthropicClient(model="claude-sonnet-4-5"),
    instructions="You are a helpful assistant.",
)

Use the Claude Agent SDK instead of a chat client when you want Claude to drive its own tool loop, subagents, and session continuity:

from agent_framework.anthropic import ClaudeAgent, ClaudeAgentOptions

claude = ClaudeAgent(
    options=ClaudeAgentOptions(model="claude-sonnet-4-5", permission_mode="default"),
)
response = await claude.run("Refactor utils.py to use dataclasses.")

Ollama

Local models via the Ollama daemon.

from agent_framework import Agent
from agent_framework.ollama import OllamaChatClient

agent = Agent(
    client=OllamaChatClient(model="llama3.1"),
    instructions="You are a helpful assistant.",
)

Custom base URL (non-default daemon):

OllamaChatClient(model="llama3.1", base_url="http://gpu-host:11434")

Amazon Bedrock (native)

The agent_framework.amazon namespace exposes the native Bedrock Converse API (for Titan, Nova, Mistral, Cohere, DeepSeek, etc. on Bedrock). For Claude on Bedrock, use AnthropicBedrockClient from the Anthropic provider instead — it unlocks Anthropic-specific features like extended thinking.

from agent_framework import Agent
from agent_framework.amazon import BedrockChatClient

agent = Agent(
    client=BedrockChatClient(model="amazon.nova-pro-v1:0", region="us-east-1"),
    instructions="You are a helpful assistant.",
)

Guardrails:

from agent_framework.amazon import BedrockChatClient, BedrockGuardrailConfig

client = BedrockChatClient(
    model="amazon.nova-pro-v1:0",
    guardrail=BedrockGuardrailConfig(guardrail_id="gr-xyz", guardrail_version="1"),
)

GitHub Copilot

from agent_framework import Agent
from agent_framework.github import CopilotChatClient  # agent_framework_github_copilot

agent = Agent(
    client=CopilotChatClient(model="gpt-4o"),
    instructions="Pair-programmer mode.",
)

Copilot Studio

from agent_framework.microsoft import CopilotStudioAgent  # agent_framework_copilotstudio

agent = CopilotStudioAgent(
    bot_id="<bot id>",
    tenant_id="<tenant id>",
    # …auth config…
)

Swap providers at runtime

Because every client satisfies SupportsChatGetResponse, the agent stays identical — only the client changes:

import os
from agent_framework import Agent
from agent_framework.openai import OpenAIChatClient
from agent_framework.anthropic import AnthropicClient
from agent_framework.ollama import OllamaChatClient

def build_client():
    provider = os.environ.get("LLM_PROVIDER", "openai")
    if provider == "anthropic":
        return AnthropicClient(model="claude-sonnet-4-5")
    if provider == "ollama":
        return OllamaChatClient(model="llama3.1")
    return OpenAIChatClient(model="gpt-5")

agent = Agent(client=build_client(), instructions="Helpful assistant.")

Embeddings

Every provider with embedding support exposes an *EmbeddingClient alongside its chat client. All satisfy SupportsGetEmbeddings and return the same GeneratedEmbeddings[list[float], EmbeddingGenerationOptions] type, so you can swap them freely.

from agent_framework.openai import OpenAIEmbeddingClient
from agent_framework.ollama import OllamaEmbeddingClient
from agent_framework.foundry import FoundryEmbeddingClient
from agent_framework.amazon import BedrockEmbeddingClient

embeddings = OpenAIEmbeddingClient(model="text-embedding-3-large")
result = await embeddings.get_embeddings(["hello", "world"])

for vec in result:
    print(vec.dimensions, vec.model, vec.vector[:4])
# `result.usage` is a UsageDetails (dict-like); key names vary by provider.
print("tokens used:", (result.usage or {}).get("total_tokens", 0))

The Embedding and GeneratedEmbeddings types

get_embeddings always returns a GeneratedEmbeddings — it subclasses list[Embedding], so iteration, indexing, and len(...) work as you’d expect. Each Embedding is generic over the vector type (usually list[float], sometimes list[int] or bytes for quantised providers):

from agent_framework import Embedding, GeneratedEmbeddings

# Constructing an Embedding directly — dimensions default to len(vector).
single = Embedding(vector=[0.1, 0.2, 0.3], model="text-embedding-3-small")
assert single.dimensions == 3

# Wrapping a list of them as a GeneratedEmbeddings — this is the shape your
# code should handle from every *EmbeddingClient.
batch = GeneratedEmbeddings(
    [single, Embedding(vector=[0.4, 0.5, 0.6])],
    usage={"prompt_tokens": 10, "total_tokens": 10},
)
assert len(batch) == 2

Picking dimensions (OpenAI text-embedding-3-*)

The OpenAI text-embedding-3-* models support a dimensions parameter that lets you request a shorter vector without a separate model. Pass it through OpenAIEmbeddingOptions:

from agent_framework.openai import OpenAIEmbeddingClient, OpenAIEmbeddingOptions

client = OpenAIEmbeddingClient(model="text-embedding-3-large")

# 256-dim embeddings — cheaper to store, 4x smaller vector DB footprint.
result = await client.get_embeddings(
    ["hello"],
    options=OpenAIEmbeddingOptions(dimensions=256, encoding_format="float"),
)
assert result[0].dimensions == 256

Provider-neutral duck typing

Any code that embeds can take the SupportsGetEmbeddings protocol instead of a concrete class — type checkers will accept every first-party client and any subclass of BaseEmbeddingClient you write yourself:

from agent_framework import SupportsGetEmbeddings


async def index(client: SupportsGetEmbeddings, docs: list[str]) -> list[list[float]]:
    result = await client.get_embeddings(docs)
    return [e.vector for e in result]

Custom embedding client

Subclass BaseEmbeddingClient when you need to wrap a provider that isn’t first-party or want to add batching/caching/shadowing on top of an existing one. The full pattern lives in the Advanced page; the short version:

from agent_framework import BaseEmbeddingClient, Embedding, GeneratedEmbeddings


class StubEmbeddingClient(BaseEmbeddingClient):
    OTEL_PROVIDER_NAME = "stub"

    async def get_embeddings(self, values, *, options=None):
        return GeneratedEmbeddings(
            [Embedding(vector=[0.0] * 8, model="stub") for _ in values],
            options=options,
        )

Provider-neutral request options — ChatOptions

Every provider-specific options TypedDict (OpenAIChatOptions, AnthropicChatOptions, etc.) extends the generic ChatOptions base. When you’re writing code that should work against any client, type against ChatOptions — it captures the common denominator across all providers. All fields are optional (total=False), so you only set what you need.

from agent_framework import ChatOptions

common: ChatOptions = {
    "model": "gpt-5-mini",
    "temperature": 0.2,
    "top_p": 0.9,
    "max_tokens": 2_000,
    "stop": ["\n\nUSER:"],
    "seed": 1337,
    "frequency_penalty": 0.0,
    "presence_penalty": 0.1,
    "user": "user-42",               # end-user id for provider-side abuse tracking
    "metadata": {"env": "prod"},     # attached to the request; provider may echo it back
}

response = await agent.run("Summarise the dataset.", options=common)

The fields ChatOptions defines — every first-party client accepts at least this subset:

Field	Type	Purpose
model	str	Override the model for this one call
temperature / top_p	float	Sampling temperature and nucleus probability
max_tokens	int	Upper bound on output tokens
stop	str | Sequence[str]	Stop sequences
seed	int	Reproducibility hint (providers may ignore)
logit_bias	dict[str | int, float]	Per-token bias map
frequency_penalty / presence_penalty	float	Repetition / novelty penalties
tools	Sequence[FunctionTool | Callable | …] | None	Per-call tool list (additive over the agent’s)
tool_choice	ToolMode | "auto" | "required" | "none"	Force a tool, require any tool, or disable tools
allow_multiple_tool_calls	bool	Permit the model to request more than one tool per turn
response_format	type[BaseModel] | Mapping | None	Structured output — pass a Pydantic class or a JSON schema
metadata	dict[str, Any]	Free-form metadata the provider round-trips on the request
user	str	End-user identifier (OpenAI / Anthropic use it for abuse detection)
store	bool	Provider-side conversation storage (OpenAI Responses API, Foundry)
conversation_id	str	Continue a provider-managed conversation
instructions	str	Per-call system instructions override

Forcing a specific tool with ToolMode

tool_choice accepts either the shorthand literal strings or a ToolMode dict for when you want to pin the model to one specific function:

from agent_framework import ChatOptions, ToolMode

pin_to_search: ChatOptions = {
    "tool_choice": ToolMode(mode="required", required_function_name="search_products"),
    "allow_multiple_tool_calls": False,
}

await agent.run("Find red sneakers under $100", options=pin_to_search)

mode="none" disables tools entirely for one call (useful when you want a pure summary of the conversation without further tool-use); mode="required" without required_function_name forces the model to pick some tool.

Structured output in one line

response_format accepts a Pydantic model — the response comes back as a typed object via response.value:

from pydantic import BaseModel
from agent_framework import ChatOptions

class Extracted(BaseModel):
    sentiment: str
    score: float
    topics: list[str]

options: ChatOptions = {"response_format": Extracted}
response = await agent.run(
    "Summarise this review: 'Fast shipping, but the fabric snagged.'",
    options=options,
)
print(response.value.sentiment, response.value.score)

Providers that don’t support structured output natively fall back to JSON-mode + client-side validation — same surface either way.

Merging with client-level defaults

Every client accepts the same TypedDict on construction. The call-level options= is a shallow merge on top: keys you set win, keys you omit inherit from the client.

from agent_framework.openai import OpenAIChatClient

client = OpenAIChatClient(model="gpt-5-mini", temperature=0.7)

# Inherits temperature=0.7; only max_tokens is overridden.
await agent.run("Draft a tweet.", options={"max_tokens": 280})

Swapping the model on an existing client

Every client accepts model= at construction and remembers it. But you can also override the model for a single call without building a new client — use options= on the agent run:

from agent_framework.openai import OpenAIChatClient, OpenAIChatOptions

default_client = OpenAIChatClient(model="gpt-5-mini")

agent = Agent(client=default_client, instructions="…")

# Upgrade to a bigger model just for this one tricky question.
response = await agent.run(
    "Prove Fermat's last theorem in two sentences.",
    options=OpenAIChatOptions(model="gpt-5", temperature=0.2),
)

options is a provider-specific TypedDict — OpenAIChatOptions, OpenAIChatCompletionOptions, OpenAIEmbeddingOptions, and the equivalents under agent_framework.anthropic, agent_framework.amazon, agent_framework.ollama, etc. IDE autocomplete drives you through every tunable. The values merge with the client’s defaults; anything you omit stays as the client was constructed.

When to reach for the provider-specific TypedDict

Use the generic ChatOptions whenever the knobs you need are common across providers — that keeps the call site interoperable. Drop to the provider-specific dict only when you need a feature the base can’t describe:

• OpenAI-only (via OpenAIChatOptions): reasoning, prompt_cache_key, prompt_cache_retention, service_tier, top_logprobs, truncation, background, include, max_tool_calls, continuation_token.
• Anthropic-only: extended-thinking parameters, cache-control directives.
• Bedrock-only: guardrail references, additional_model_request_fields.

Mixing them is fine — a provider-specific dict is a superset of ChatOptions, so code typed against the base still accepts it.

Building your own chat client

For a provider that isn’t in the first-party list, or to wrap an existing client with caching / shadow traffic / logging, subclass BaseChatClient. Implement one method — _inner_get_response — and inherit middleware, telemetry, and the function calling loop for free. See the full recipe in Advanced → Custom chat client.

Picking a provider

• Prototyping — OpenAIChatClient() or OllamaChatClient(model="llama3.1"). Neither requires Azure tooling.
• Azure-native deployments — OpenAIChatClient with azure_endpoint + credential, or FoundryChatClient if you’re already on a Foundry project (evaluation, service-managed agents, private networking).
• Cross-cloud Claude — AnthropicClient for Anthropic direct; AnthropicBedrockClient or AnthropicVertexClient to keep data in AWS/GCP.
• Offline / compliance — OllamaChatClient or FoundryLocalClient.
• Multi-provider fallback — build a thin factory (example above) and let an env var pick at startup; the rest of your agent code stays unchanged.