The agent framework samples are designed to help you get started with building AI-powered agents from various providers.

The Agent Framework supports building agents using various inference and inference-style services. All these are supported using the single ChatClientAgent class.

The Agent Framework also supports creating proxy agents, that allow accessing remote agents as if they were local agents. These are supported using various AIAgent subclasses.

For published integrations maintained outside the Agent Framework team, see Community projects.

Start with 01-get-started/ and work through the numbered files:

1. 01_hello_agent — Create and run your first agent
2. 02_add_tools — Add function tools
3. 03_multi_turn — Multi-turn conversations with AgentSession
4. 04_memory — Agent memory with AIContextProvider
5. 05_first_workflow — Build a workflow with executors and edges

Some additional samples of note include:

• Agents: Basic steps to get started with the agent framework. These samples demonstrate the fundamental concepts and functionalities of the agent framework when using the AIAgent and can be used with any underlying service that provides an AIAgent implementation.
• Agent Providers: Shows how to create an AIAgent instance for a selection of providers.
• Agent Telemetry: Demo which showcases the integration of OpenTelemetry with the Microsoft Agent Framework using Azure OpenAI and .NET Aspire Dashboard for telemetry visualization.
• Durable Agent Framework extension: Durable agents and workflows for console applications and Azure Functions.

If you are migrating from Semantic Kernel to the Microsoft Agent Framework, the following resources provide guidance and side-by-side examples to help you transition your existing agents, tools, and orchestration patterns. The migration samples map Semantic Kernel primitives (such as ChatCompletionAgent and Team orchestrations) to their Agent Framework equivalents (such as ChatClientAgent and workflow builders).

For an in-depth migration guide, see the official migration documentation.

For prerequisites see each set of samples for their specific requirements.