You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 02-explore-agentic-frameworks/README.md
+26-31
Original file line number
Diff line number
Diff line change
@@ -480,49 +480,44 @@ Azure AI Agent Service has the following core concepts:
480
480
**Use Cases**: Azure AI Agent Service is designed for enterprise applications that require secure, scalable, and flexible AI agent deployment.
481
481
482
482
## What's the difference between these frameworks?
483
-
483
+
484
484
It does sound like there is a lot of overlap between these frameworks, but there are some key differences in terms of their design, capabilities, and target use cases:
485
-
486
-
-**AutoGen**: Focuses on event-driven, distributed agentic applications, enabling multiple LLMs and SLMs, tools, and advanced multi-agent design patterns.
487
-
-**Semantic Kernel**: Focuses on understanding and generating human-like text content by capturing deeper semantic meanings. It is designed to automate complex workflows and initiate tasks based on project goals.
488
-
-**Azure AI Agent Service**: Provides more flexible models, such as directly calling open-source LLMs like Llama 3, Mistral, and Cohere. It offers stronger enterprise security mechanisms and data storage methods, making it suitable for enterprise applications.
489
-
485
+
486
+
-**AutoGen**: Is an experiementation framework focused on leading-edge research on multi-agent systems. It is the best place to experiment and prototype sophisticated multi-agent sytems.
487
+
-**Semantic Kernel**: Is a production-ready agent library for building enterprise agentic applications. Focuses on event-driven, distributed agentic applications, enabling multiple LLMs and SLMs, tools, and single/multi-agent design patterns.
488
+
-**Azure AI Agent Service**: Is a platform and deployment service in Azure Foundry for agents. It offers building connectivity to services support by Azure Found like Azure OpenAI, Azure AI Search, Bing Search and code exectuition.
489
+
490
490
Still not sure which one to choose?
491
491
492
492
### Use Cases
493
-
493
+
494
494
Let's see if we can help you by going through some common use cases:
495
-
496
-
> Q: My team is working on a project that involves automating code generation and data analysis tasks. Which framework should we use?
495
+
496
+
> Q: I'm experimenting, learning and building proof-of-concept agent applications, and I want to be able to build and experiment quickly
497
497
>
498
-
> A: AutoGen would be a good choice for this scenario, as it focuses on event-driven, distributed agentic applications and supports advanced multi-agent design patterns.
499
-
500
-
> Q: What makes AutoGen a better choice than Semantic Kernel and Azure AI Agent Service for this use case?
498
+
> A: AutoGen would be a good choice for this scenario, as it focuses on experimentation and building applications using the latest multi-agent patterns
499
+
500
+
> Q: I'm designing a building a application that I want to scale and use production or within my enterprise
501
501
>
502
-
> A: AutoGen is specifically designed for event-driven, distributed agentic applications, making it well-suited for automating code generation and data analysis tasks. It provides the necessary tools and capabilities to build complex multi-agent systems efficiently.
503
-
504
-
> Q: Sounds like Azure AI Agent Service could work here too, it has tools for code generation and more?
502
+
> A: Semantic Kernel is the best choice for build production AI agent applications. Experimental features from AutoGen are stabilized and added to Semantic Kernel reguarly.
503
+
504
+
> Q: Sounds like Azure AI Agent Service could work here too?
505
505
>
506
-
> A: Yes, Azure AI Agent Service also supports code generation and data analysis tasks, but it may be more suitable for enterprise applications that require secure, scalable, and flexible AI agent deployment. AutoGen is more focused on event-driven, distributed agentic applications and advanced multi-agent design patterns.
507
-
508
-
> Q: So you are saying if I want to go enterprise, I should go with Azure AI Agent Service?
506
+
> A: Yes, Azure AI Agent Service is a platform service for agents and add built-in capabilities for multiple models, Azure AI Search, Bing Search and Azure Functions. It makes it easy to build your agents in the Foundry Portal and deploy them at scale.
507
+
508
+
> Q: I'm still confused just give me one option
509
509
>
510
-
> A: Yes, Azure AI Agent Service is designed for enterprise applications that require secure, scalable, and flexible AI agent deployment. It offers stronger enterprise security mechanisms and data storage methods, making it suitable for enterprise use cases.
511
-
510
+
> A: A create choice is to build you application in Semantic Kernel first, and use Azure AI Agent Service to deploy you agent. This means you can easily perist your agents while still having the power to build multi-agent systems in Semantic Kernel. Semantic also has a connector in AutoGen to make it easy to use both frameworks together.
| AutoGen | Experimentation and proof-of-concept |
517
+
| Semantic Kernel | Product-ready enterprise AI agent applications |
518
+
| Azure AI Agent Service | Deployment, management and integration with Azure Foundry |
520
519
What's the ideal use case for each of these frameworks?
521
520
522
-
-**AutoGen**: Event-driven, distributed agentic applications, advanced multi-agent design patterns. Ideal for automating code generation, data analysis tasks.
523
-
-**Semantic Kernel**: Understanding and generating human-like text content, automating complex workflows, initiating tasks based on project goals. Ideal for natural language understanding, content generation.
524
-
-**Azure AI Agent Service**: Flexible models, enterprise security mechanisms, data storage methods. Ideal for secure, scalable, and flexible AI agent deployment in enterprise applications.
525
-
526
521
## Can I integrate my existing Azure ecosystem tools directly, or do I need standalone solutions?
527
522
528
523
The answer is yes, you can integrate your existing Azure ecosystem tools directly with Azure AI Agent Service especially, this because it has been built to work seamlessly with other Azure services. You could for example integrate Bing, Azure AI Search, and Azure Functions. There's also deep integration with Azure AI Foundry.
0 commit comments