Convert Plugins to Microsoft Agent Framework and rename to Agent Framework quick start #121
Description
Path to Microsoft Agent Framework
Many customers are already using Semantic Kernel or AutoGen in production today. Both projects will remain supported but most investment is now focused on Microsoft Agent Framework. Developers using Semantic Kernel or AutoGen will find the transition straightforward:
For Semantic Kernel users:
Migration is straightforward: replace Kernel and plugin patterns with the Agent and Tool abstractions.
.NET developers move from Microsoft.SemanticKernel.* to the new Microsoft.Extensions.AI.* namespaces, with agents created directly from providers instead of requiring Kernel coupling.
Python developers can install the full package (pip install agent-framework) or just the components they need (e.g., agent-framework-azure-ai, agent-framework-redis).
Agents now manage threads natively, simplify invocation with RunAsync / RunStreamingAsync, and register tools inline without attributes or plugin wrappers.
Existing vector store integrations (Azure AI Search, Postgres, Cosmos DB, Redis, Elasticsearch, etc.) continue to work through connectors.
Plugins like Bing, Google, OpenAPI, and Microsoft Graph port directly as tools, often exposed via MCP or OpenAPI.
The net result: less boilerplate, simplified memory management, and alignment with open standards.