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
The solution leverages Azure OpenAI Service, Azure Container Apps, Azure Cosmos DB, and Azure Container Registry to create an intelligent automation pipeline. It uses a multi-agent approach where specialized AI agents work together to plan, execute, and validate tasks based on user input.
Follow the quick deploy steps on the deployment guide to deploy this solution to your own Azure subscription.
72
72
73
-
[Click here to launch the deployment guide](./documentation/DeploymentGuide.md)
73
+
[Click here to launch the deployment guide](./docs/DeploymentGuide.md)
74
74
<br/><br/>
75
75
76
76
|[](https://codespaces.new/microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator)|[](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator)|
@@ -79,13 +79,13 @@ Follow the quick deploy steps on the deployment guide to deploy this solution to
<br/>To ensure sufficient quota is available in your subscription, please follow [quota check instructions guide](./documentation/quota_check.md) before you deploy the solution.
82
+
<br/>To ensure sufficient quota is available in your subscription, please follow [quota check instructions guide](./docs/quota_check.md) before you deploy the solution.
83
83
84
84
<br/>
85
85
86
86
### Prerequisites and Costs
87
87
88
-
To deploy this solution accelerator, ensure you have access to an [Azure subscription](https://azure.microsoft.com/free/) with the necessary permissions to create **resource groups and resources**. Follow the steps in [Azure Account Set Up](./documentation/AzureAccountSetUp.md).
88
+
To deploy this solution accelerator, ensure you have access to an [Azure subscription](https://azure.microsoft.com/free/) with the necessary permissions to create **resource groups and resources**. Follow the steps in [Azure Account Set Up](./docs/AzureAccountSetUp.md).
89
89
90
90
Check the [Azure Products by Region](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/table) page and select a **region** where the following services are available: Azure OpenAI Service, Azure AI Search, and Azure Semantic Search.
91
91
@@ -107,11 +107,11 @@ Use the [Azure pricing calculator](https://azure.microsoft.com/en-us/pricing/cal
107
107
either by deleting the resource group in the Portal or running `azd down`.
Copy file name to clipboardExpand all lines: docs/CustomizeSolution.md
+16-17Lines changed: 16 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,18 @@
1
+
# Table of Contents
2
+
3
+
-[Table of Contents](#table-of-contents)
4
+
-[Accelerating your own Multi-Agent - Custom Automation Engine MVP](#accelerating-your-own-multi-agent---custom-automation-engine-mvp)
5
+
-[Technical Overview](#technical-overview)
6
+
-[Adding a New Agent to the Multi-Agent System](#adding-a-new-agent-to-the-multi-agent-system)
7
+
-[API Reference](#api-reference)
8
+
-[Models and Datatypes](#models-and-datatypes)
9
+
-[Application Flow](#application-flow)
10
+
-[Agents Overview](#agents-overview)
11
+
-[Persistent Storage with Cosmos DB](#persistent-storage-with-cosmos-db)
12
+
-[Utilities](#utilities)
13
+
-[Summary](#summary)
14
+
15
+
1
16
# Accelerating your own Multi-Agent - Custom Automation Engine MVP
2
17
3
18
As the name suggests, this project is designed to accelerate development of Multi-Agent solutions in your environment. The example solution presented shows how such a solution would be implemented and provides example agent definitions along with stubs for possible tools those agents could use to accomplish tasks. You will want to implement real functions in your own environment, to be used by agents customized around your own use cases. Users can choose the LLM that is optimized for responsible use. The default LLM is GPT-4o which inherits the existing responsible AI mechanisms and filters from the LLM provider. We encourage developers to review [OpenAI’s Usage policies](https://openai.com/policies/usage-policies/) and [Azure OpenAI’s Code of Conduct](https://learn.microsoft.com/en-us/legal/cognitive-services/openai/code-of-conduct) when using GPT-4o. This document is designed to provide the in-depth technical information to allow you to add these customizations. Once the agents and tools have been developed, you will likely want to implement your own real world front end solution to replace the example in this accelerator.
@@ -15,21 +30,6 @@ This application is an AI-driven orchestration system that manages a group of AI
15
30
This code has not been tested as an end-to-end, reliable production application- it is a foundation to help accelerate building out multi-agent systems. You are encouraged to add your own data and functions to the agents, and then you must apply your own performance and safety evaluation testing frameworks to this system before deploying it.
16
31
17
32
Below, we'll dive into the details of each component, focusing on the endpoints, data types, and the flow of information through the system.
18
-
# Table of Contents
19
-
20
-
-[Table of Contents](#table-of-contents)
21
-
-[Accelerating your own Multi-Agent - Custom Automation Engine MVP](#accelerating-your-own-multi-agent---custom-automation-engine-mvp)
22
-
-[Technical Overview](#technical-overview)
23
-
-[Adding a New Agent to the Multi-Agent System](#adding-a-new-agent-to-the-multi-agent-system)
24
-
-[API Reference](#api-reference)
25
-
-[Models and Datatypes](#models-and-datatypes)
26
-
-[Application Flow](#application-flow)
27
-
-[Agents Overview](#agents-overview)
28
-
-[Persistent Storage with Cosmos DB](#persistent-storage-with-cosmos-db)
29
-
-[Utilities](#utilities)
30
-
-[Summary](#summary)
31
-
32
-
33
33
## Adding a New Agent to the Multi-Agent System
34
34
35
35
This guide details the steps required to add a new agent to the Multi-Agent Custom Automation Engine. The process includes registering the agent, defining its capabilities through tools, and ensuring the PlannerAgent includes the new agent when generating activity plans.
@@ -41,7 +41,6 @@ Every agent is equipped with a set of tools (functions) that it can call to perf
41
41
42
42
Example (for a `BakerAgent`):
43
43
```python
44
-
from autogen_core.components.tools import FunctionTool, Tool
@@ -615,4 +614,4 @@ This application orchestrates a group of AI agents to accomplish user-defined ta
615
614
616
615
Understanding the flow of data through the endpoints, agents, and persistent storage is key to grasping the logic of the application. Each component plays a specific role in ensuring tasks are planned, executed, and adjusted based on feedback, providing a robust and interactive system.
617
616
618
-
For instructions to setup a local development environment for the solution, please see [local deployment guide](./LocalDeployment.md).
617
+
For instructions to setup a local development environment for the solution, please see [deployment guide](./DeploymentGuide.md).
Copy file name to clipboardExpand all lines: docs/DeploymentGuide.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## **Pre-requisites**
4
4
5
-
To deploy this solution accelerator, ensure you have access to an [Azure subscription](https://azure.microsoft.com/free/) with the necessary permissions to create **resource groups, resources, app registrations, and assign roles at the resource group level**. This should include Contributor role at the subscription level and Role Based Access Control role on the subscription and/or resource group level. Follow the steps in [Azure Account Set Up](../documentation/AzureAccountSetUp.md).
5
+
To deploy this solution accelerator, ensure you have access to an [Azure subscription](https://azure.microsoft.com/free/) with the necessary permissions to create **resource groups, resources, app registrations, and assign roles at the resource group level**. This should include Contributor role at the subscription level and Role Based Access Control role on the subscription and/or resource group level. Follow the steps in [Azure Account Set Up](../docs/AzureAccountSetUp.md).
6
6
7
7
Check the [Azure Products by Region](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/?products=all®ions=all) page and select a **region** where the following services are available:
8
8
@@ -223,7 +223,7 @@ This guide provides step-by-step instructions for deploying your application usi
223
223
224
224
There are several ways to deploy the solution. You can deploy to run in Azure in one click, or manually, or you can deploy locally.
225
225
226
-
When Deployment is complete, follow steps in [Set Up Authentication in Azure App Service](../documentation/azure_app_service_auth_setup.md) to add app authentication to your web app running on Azure App Service
226
+
When Deployment is complete, follow steps in [Set Up Authentication in Azure App Service](../docs/azure_app_service_auth_setup.md) to add app authentication to your web app running on Azure App Service
4. Select the first option `Microsoft Entra Id` from the drop-down list. If `Create new app registration` is disabled, go to [Step 1a](#step-1a-creating-a-new-app-registration).
24
+
4. Select the first option `Microsoft Entra Id` from the drop-down list and select `client secret expiration` under App registration.
25
+
> NOTE: If `Create new app registration` is disabled, then go to [Create new app registration](/docs/create_new_app_registration.md) and come back to this step to complete the app authentication.
4. Provide the `Name`, select supported account types as `Accounts in this organizational directory only(Contoso only - Single tenant)`, select platform as `Web`, enter/select the `URL` and register.
8. Enter the `web app URL` (Provide the app service name in place of XXXX) and Save. Then go back to [Step 1](#step-1-add-authentication-in-azure-app-service-configuration) and follow from _Point 4_ choose `Pick an existing app registration in this directory` from the Add an Identity Provider page and provide the newly registered App Name.
56
-
E.g. <<https://<< appservicename >>.azurewebsites.net/.auth/login/aad/callback>>
0 commit comments