From 1f93bcf7359742e10c2a22f8e165678247e79c77 Mon Sep 17 00:00:00 2001 From: Roopan-Microsoft <168007406+Roopan-Microsoft@users.noreply.github.com> Date: Tue, 24 Dec 2024 17:31:09 +0530 Subject: [PATCH 1/9] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index bcaeda7b7..7dbafb6fc 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ -# Multi-Agent -Custom Automation Engine Solution Accelerator +# Multi-Agent-Custom Automation Engine Solution Accelerator -MENU: [**USER STORY**](#user-story) \| [**SIMPLE DEPLOY**](#quick-deploy) \| [**SUPPORTING DOCUMENTATION**](#supporting-documentation) \| +MENU: [**USER STORY**](#user-story) \| [**QUICK DEPLOY**](#quick-deploy) \| [**SUPPORTING DOCUMENTATION**](#supporting-documentation) \|


@@ -194,7 +194,7 @@ To add the identity provider, please follow the steps outlined in [Set Up Authen ### Run locally and debug -To debug the solution, you can use the Cosmos and OpenAI services you have manually deployed. To do this, you need to ensure that your Azure identity has the required permissions on the Cosmos and Open AI services. +To debug the solution, you can use the Cosmos and OpenAI services you have manually deployed. To do this, you need to ensure that your Azure identity has the required permissions on the Cosmos and OpenAI services. - For OpeAI service, you can add yourself to the ‘Cognitive Services OpenAI User’ permission in the Access Control (IAM) pane of the Azure portal. - Cosmos is a little more difficult as it requires permissions be added through script. See these examples for more information: From 0b739b55a1d9dc4df7e3a92ee0e556ec6a9902ad Mon Sep 17 00:00:00 2001 From: Roopan-Microsoft <168007406+Roopan-Microsoft@users.noreply.github.com> Date: Tue, 24 Dec 2024 17:31:46 +0530 Subject: [PATCH 2/9] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7dbafb6fc..c0a14b6aa 100644 --- a/README.md +++ b/README.md @@ -96,7 +96,7 @@ Manual Deployment differs from the ‘Quick Deploy’ option in that it will ins All of the necessary Azure services can be deployed using the /deploy/macae.bicep script. This script will require the following parameters: ``` -Az login +az login az account set --subscription az group create --name --location ``` From 6ab6060f71b78b24360187f589af07aed193a778 Mon Sep 17 00:00:00 2001 From: Roopan-Microsoft <168007406+Roopan-Microsoft@users.noreply.github.com> Date: Tue, 24 Dec 2024 17:35:10 +0530 Subject: [PATCH 3/9] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c0a14b6aa..fb82a494f 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# Multi-Agent-Custom Automation Engine Solution Accelerator +# Multi-Agent: Custom Automation Engine – Solution Accelerator MENU: [**USER STORY**](#user-story) \| [**QUICK DEPLOY**](#quick-deploy) \| [**SUPPORTING DOCUMENTATION**](#supporting-documentation) \| From ffbe33c95093a69ccd1c00fc156bd6cf152c1c3f Mon Sep 17 00:00:00 2001 From: Roopan-Microsoft <168007406+Roopan-Microsoft@users.noreply.github.com> Date: Tue, 28 Jan 2025 10:42:37 +0530 Subject: [PATCH 4/9] Update README.md --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index b67fd9c73..265fa3c17 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ This accelerator uses the AutoGen framework from Microsoft Research. This is an ### Use cases / scenarios The multi-agent approach allows users to utilize multiple AI agents simultaneously for repeatable tasks, ensuring consistency and efficiency. -The agents collaborate with a manager on various assignments for onboarding a new employee , such as HR and tech support AI working together to set up software accounts, configure hardware, schedule onboarding meetings, register employees for benefits, and send welcome emails. Additionally, these agents can handle tasks like procurement and drafting press releases. +The agents collaborate with a manager on various assignments for onboarding a new employee, such as HR and tech support AI working together to set up software accounts, configure hardware, schedule onboarding meetings, register employees for benefits, and send welcome emails. Additionally, these agents can handle tasks like procurement and drafting press releases. ### Business value Multi-agent systems represent the next wave of Generative AI use cases, offering entirely new opportunities to drive efficiencies in your business. The Multi-Agent -Custom Automation Engine Solution Accelerator demonstrates several key benefits: @@ -29,7 +29,7 @@ Multi-agent systems represent the next wave of Generative AI use cases, offering - **Enabling GenAI to scale:** by not needing to build one application after another, organizations are able to reduce the friction of adopting GenAI across their entire organization. One capability can unlock almost unlimited use cases. - **Applicable to most industries:** these are common challenges that most organizations face, across most industries. -Whilst still an emerging area, investing in agentic use cases, digitatization and developing tools will be key to ensuring you are able to leverage these new technologies and seize the GenAI moment. +Whilst still an emerging area, investing in agentic use cases, digitization and developing tools will be key to ensuring you are able to leverage these new technologies and seize the GenAI moment. ### Technical key features @@ -185,10 +185,10 @@ To add your newly created backend image: To add the new container to your website run the following: ``` -az webapp config container set --resource-group macae_full_deploy2_rg \ ---name macae-frontend-2t62qyozi76bs \ ---container-image-name macaeacr2t62qyozi76bs.azurecr.io/frontendmacae:latest \ ---container-registry-url https://macaeacr2t62qyozi76bs.azurecr.io +az webapp config container set --resource-group \ +--name \ +--container-image-name \ +--container-registry-url ``` @@ -199,7 +199,7 @@ To add the identity provider, please follow the steps outlined in [Set Up Authen To debug the solution, you can use the Cosmos and OpenAI services you have manually deployed. To do this, you need to ensure that your Azure identity has the required permissions on the Cosmos and OpenAI services. -- For OpeAI service, you can add yourself to the ‘Cognitive Services OpenAI User’ permission in the Access Control (IAM) pane of the Azure portal. +- For OpenAI service, you can add yourself to the ‘Cognitive Services OpenAI User’ permission in the Access Control (IAM) pane of the Azure portal. - Cosmos is a little more difficult as it requires permissions be added through script. See these examples for more information: - [Use data plane role-based access control - Azure Cosmos DB for NoSQL | Microsoft Learn](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/security/how-to-grant-data-plane-role-based-access?tabs=built-in-definition%2Cpython&pivots=azure-interface-cli) - [az cosmosdb sql role assignment | Microsoft Learn](https://learn.microsoft.com/en-us/cli/azure/cosmosdb/sql/role/assignment?view=azure-cli-latest#az-cosmosdb-sql-role-assignment-create) From a6f09cd09124e92da08b8b09f21f653210e5deef Mon Sep 17 00:00:00 2001 From: Roopan-Microsoft <168007406+Roopan-Microsoft@users.noreply.github.com> Date: Tue, 28 Jan 2025 11:03:45 +0530 Subject: [PATCH 5/9] Update LocalDeployment.md --- documentation/LocalDeployment.md | 32 +++++++++++++++++++++++++------- 1 file changed, 25 insertions(+), 7 deletions(-) diff --git a/documentation/LocalDeployment.md b/documentation/LocalDeployment.md index ae3aa7adc..e1c6cb8e5 100644 --- a/documentation/LocalDeployment.md +++ b/documentation/LocalDeployment.md @@ -22,7 +22,7 @@ ``` - To specify a tenant, use: ```bash - az login --tenant 16b3c013-0000-0000-0000-000000000 + az login --tenant ``` 3. **Create a Resource Group:** @@ -42,21 +42,39 @@ ```bash az ad signed-in-user show --query id -o tsv ``` - You will also be prompted for locations for Cosmos and Open AI services. This is to allow separate regions where there may be service quota restrictions + You will also be prompted for locations for Cosmos and Open AI services. This is to allow separate regions where there may be service quota restrictions. -5. **Create a `.env` file:** + - **Additional Notes**: + + **Role Assignments in Bicep Deployment:** + + The macae-dev.bicep deployment includes the assignment of the appropriate roles to AOAI and Cosmos services. If you want to modify an existing implementation—for example, to use resources deployed as part of the simple deployment for local debugging—you will need to add your own credentials to access the Cosmos and AOAI services. You can add these permissions using the following commands: + ```bash + az cosmosdb sql role assignment create --resource-group --account-name --role-definition-name "Cosmos DB Built-in Data Contributor" --principal-id --scope /subscriptions//resourceGroups//providers/Microsoft.DocumentDB/databaseAccounts/ + ``` + + ```bash + az role assignment create --assignee --role "Cognitive Services OpenAI User" --scope /subscriptions//resourceGroups//providers/Microsoft.CognitiveServices/accounts/ + ``` + **Using a Different Database in Cosmos:** + + You can set the solution up to use a different database in Cosmos. For example, you can name it something like autogen-dev. To do this: + 1. Change the environment variable **COSMOSDB_DATABASE** to the new database name. + 2. You will need to create the database in the Cosmos DB account. You can do this from the Data Explorer pane in the portal, click on the drop down labeled “_+ New Container_” and provide all the necessary details. + +6. **Create a `.env` file:** - Navigate to the `src` folder and create a `.env` file based on the provided `.env.sample` file. -6. **Fill in the `.env` file:** +7. **Fill in the `.env` file:** - Use the output from the deployment or check the Azure Portal under "Deployments" in the resource group. -7. **(Optional) Set up a virtual environment:** +8. **(Optional) Set up a virtual environment:** - If you are using `venv`, create and activate your virtual environment for both the frontend and backend folders. -8. **Install requirements - frontend:** +9. **Install requirements - frontend:** - In each of the frontend and backend folders - Open a terminal in the `src` folder and run: @@ -64,7 +82,7 @@ pip install -r requirements.txt ``` -9. **Run the application:** +10. **Run the application:** - From the src/backend directory: ```bash python app.py From 9edaf39b47840fadf173c5ae6199d2ddb7df3b82 Mon Sep 17 00:00:00 2001 From: Roopan-Microsoft <168007406+Roopan-Microsoft@users.noreply.github.com> Date: Tue, 28 Jan 2025 11:04:13 +0530 Subject: [PATCH 6/9] Update LocalDeployment.md --- documentation/LocalDeployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/LocalDeployment.md b/documentation/LocalDeployment.md index e1c6cb8e5..1e450330e 100644 --- a/documentation/LocalDeployment.md +++ b/documentation/LocalDeployment.md @@ -48,7 +48,7 @@ **Role Assignments in Bicep Deployment:** - The macae-dev.bicep deployment includes the assignment of the appropriate roles to AOAI and Cosmos services. If you want to modify an existing implementation—for example, to use resources deployed as part of the simple deployment for local debugging—you will need to add your own credentials to access the Cosmos and AOAI services. You can add these permissions using the following commands: + The **macae-dev.bicep** deployment includes the assignment of the appropriate roles to AOAI and Cosmos services. If you want to modify an existing implementation—for example, to use resources deployed as part of the simple deployment for local debugging—you will need to add your own credentials to access the Cosmos and AOAI services. You can add these permissions using the following commands: ```bash az cosmosdb sql role assignment create --resource-group --account-name --role-definition-name "Cosmos DB Built-in Data Contributor" --principal-id --scope /subscriptions//resourceGroups//providers/Microsoft.DocumentDB/databaseAccounts/ ``` From e22a128ddd756c6974b1e67215c1f5af83f9a5fa Mon Sep 17 00:00:00 2001 From: Roopan-Microsoft <168007406+Roopan-Microsoft@users.noreply.github.com> Date: Tue, 28 Jan 2025 11:09:22 +0530 Subject: [PATCH 7/9] Update azure_app_service_auth_setup.md --- documentation/azure_app_service_auth_setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/azure_app_service_auth_setup.md b/documentation/azure_app_service_auth_setup.md index b05ac0d8f..62c118347 100644 --- a/documentation/azure_app_service_auth_setup.md +++ b/documentation/azure_app_service_auth_setup.md @@ -18,7 +18,7 @@ ![Add Provider](./images/azure-app-service-auth-setup/AppAuthIdentityProviderAdd.png) -5. Accept the default values and click on `Add` button to go back to the previous page with the identify provider added. +5. Accept the default values and click on `Add` button to go back to the previous page with the idenity provider added. ![Add Provider](./images/azure-app-service-auth-setup/AppAuthIdentityProviderAdded.png) From a89fd3a8ddc8818bf2ddfe1ccd84189a26cd8b5d Mon Sep 17 00:00:00 2001 From: Roopan-Microsoft <168007406+Roopan-Microsoft@users.noreply.github.com> Date: Tue, 28 Jan 2025 11:16:41 +0530 Subject: [PATCH 8/9] Update LocalDeployment.md --- documentation/LocalDeployment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/LocalDeployment.md b/documentation/LocalDeployment.md index 1e450330e..03fd9ba2d 100644 --- a/documentation/LocalDeployment.md +++ b/documentation/LocalDeployment.md @@ -56,9 +56,9 @@ ```bash az role assignment create --assignee --role "Cognitive Services OpenAI User" --scope /subscriptions//resourceGroups//providers/Microsoft.CognitiveServices/accounts/ ``` - **Using a Different Database in Cosmos:** + **Using a Different Database in Cosmos:** - You can set the solution up to use a different database in Cosmos. For example, you can name it something like autogen-dev. To do this: + You can set the solution up to use a different database in Cosmos. For example, you can name it something like autogen-dev. To do this: 1. Change the environment variable **COSMOSDB_DATABASE** to the new database name. 2. You will need to create the database in the Cosmos DB account. You can do this from the Data Explorer pane in the portal, click on the drop down labeled “_+ New Container_” and provide all the necessary details. From ca1395a12bc0bd1a0d03a3ad1631c81742115c86 Mon Sep 17 00:00:00 2001 From: Roopan-Microsoft <168007406+Roopan-Microsoft@users.noreply.github.com> Date: Tue, 28 Jan 2025 11:26:26 +0530 Subject: [PATCH 9/9] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 265fa3c17..c84c56a7a 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# Multi-Agent: Custom Automation Engine – Solution Accelerator +# Multi-Agent-Custom-Automation-Engine – Solution Accelerator MENU: [**USER STORY**](#user-story) \| [**QUICK DEPLOY**](#quick-deploy) \| [**SUPPORTING DOCUMENTATION**](#supporting-documentation) \| @@ -13,7 +13,7 @@ Problem: Agentic AI systems are set to transform the way businesses operate, however it can be fairly complex to build an initial MVP to demonstrate this value. Solution: -The Multi-Agent -Custom Automation Engine Solution Accelerator provides a ready to go application to use as the base of the MVP, or as a reference, allowing you to hit the ground running. +The Multi-Agent-Custom Automation Engine Solution Accelerator provides a ready to go application to use as the base of the MVP, or as a reference, allowing you to hit the ground running. ### Technology Note This accelerator uses the AutoGen framework from Microsoft Research. This is an open source project that is maintained by [Microsoft Research’s AI Frontiers Lab](https://www.microsoft.com/research/lab/ai-frontiers/). Please see this [blog post](https://devblogs.microsoft.com/autogen/microsofts-agentic-frameworks-autogen-and-semantic-kernel/) for the latest information on using the AutoGen framework in production solutions. @@ -23,7 +23,7 @@ The multi-agent approach allows users to utilize multiple AI agents simultaneous The agents collaborate with a manager on various assignments for onboarding a new employee, such as HR and tech support AI working together to set up software accounts, configure hardware, schedule onboarding meetings, register employees for benefits, and send welcome emails. Additionally, these agents can handle tasks like procurement and drafting press releases. ### Business value -Multi-agent systems represent the next wave of Generative AI use cases, offering entirely new opportunities to drive efficiencies in your business. The Multi-Agent -Custom Automation Engine Solution Accelerator demonstrates several key benefits: +Multi-agent systems represent the next wave of Generative AI use cases, offering entirely new opportunities to drive efficiencies in your business. The Multi-Agent-Custom-Automation-Engine Solution Accelerator demonstrates several key benefits: - **Allows people to focus on what matters:** by doing the heavy lifting involved with coordinating activities across an organization, peoples’ time is freed up to focus on their specializations. - **Enabling GenAI to scale:** by not needing to build one application after another, organizations are able to reduce the friction of adopting GenAI across their entire organization. One capability can unlock almost unlimited use cases.