microsoft · Fr4nc3 · Oct 6, 2025 · Oct 6, 2025 · Oct 13, 2025 · Oct 17, 2025
@@ -21,7 +21,7 @@ jobs:
       #   run: |
       #     curl -fsSL ${{ vars.AUTOGEN_WHL_URL }} -o agnext-biab-02/autogen_core-0.3.dev0-py3-none-any.whl
       - name: Log in to the Container registry
-        uses: docker/login-action@v3
+        uses: docker/login-action@v4
         with:
           registry: ${{ env.REGISTRY }}
           username: ${{ github.actor }}

@@ -61,7 +61,7 @@ jobs:
 
     # Initializes the CodeQL tools for scanning.
     - name: Initialize CodeQL
-      uses: github/codeql-action/init@v3
+      uses: github/codeql-action/init@v4
       with:
         languages: ${{ matrix.language }}
         build-mode: ${{ matrix.build-mode }}
@@ -89,6 +89,6 @@ jobs:
         exit 1
 
     - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v3
+      uses: github/codeql-action/analyze@v4
       with:
         category: "/language:${{matrix.language}}"
@@ -18,7 +18,7 @@ jobs:
         with:
           ref: ${{ github.event.workflow_run.head_sha }}
 
-      - uses: codfish/semantic-release-action@v3
+      - uses: codfish/semantic-release-action@v4
         id: semantic
         with:
           tag-format: 'v${version}'

@@ -1,4 +1,4 @@
-name: Validate WAF Deployment v3
+name: Validate WAF Deployment v4
 
 on:
   push:
@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout Code
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Run Quota Check
         id: quota-check

@@ -1,13 +1,13 @@
-name: Validate Deployment v3
+name: Validate Deployment v4
 
 on:
   workflow_run:
-    workflows: ["Build Docker and Optional Push v3"]
+    workflows: ["Build Docker and Optional Push v4"]
     types:
       - completed
     branches:
       - main
-      - dev-v3
+      - dev-v4
       - hotfix
   schedule:
     - cron: "0 11,23 * * *" # Runs at 11:00 AM and 11:00 PM GMT
@@ -27,7 +27,7 @@ jobs:
       CONTAINER_APP: ${{steps.get_backend_url.outputs.CONTAINER_APP}}
     steps:
       - name: Checkout Code
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Run Quota Check
         id: quota-check
@@ -116,9 +116,9 @@ jobs:
         id: deploy
         run: |
           if [[ "${{ env.BRANCH_NAME }}" == "main" ]]; then
-            IMAGE_TAG="latest_v3"
-          elif [[ "${{ env.BRANCH_NAME }}" == "dev-v3" ]]; then
-            IMAGE_TAG="dev_v3"
+            IMAGE_TAG="latest_v4"
+          elif [[ "${{ env.BRANCH_NAME }}" == "dev-v4" ]]; then
+            IMAGE_TAG="dev_v4"
           elif [[ "${{ env.BRANCH_NAME }}" == "hotfix" ]]; then
             IMAGE_TAG="hotfix"
           else

@@ -1,11 +1,11 @@
-name: Build Docker and Optional Push v3
+name: Build Docker and Optional Push v4
 
 on:
   push:
     branches:
       - main
-      - dev-v3
-      - demo-v3
+      - dev-v4
+      - demo-v4
       - hotfix
   pull_request:
     types:
@@ -15,8 +15,8 @@ on:
       - synchronize
     branches:
       - main
-      - dev-v3
-      - demo-v3
+      - dev-v4
+      - demo-v4
       - hotfix
   workflow_dispatch:
 
@@ -32,7 +32,7 @@ jobs:
         uses: docker/setup-buildx-action@v1
 
       - name: Log in to Azure Container Registry
-        if: ${{ github.ref_name == 'main' || github.ref_name == 'dev-v3'|| github.ref_name == 'demo-v3' || github.ref_name == 'hotfix' }}
+        if: ${{ github.ref_name == 'main' || github.ref_name == 'dev-v4'|| github.ref_name == 'demo-v4' || github.ref_name == 'hotfix' }}
         uses: azure/docker-login@v2
         with:
           login-server: ${{ secrets.ACR_LOGIN_SERVER || 'acrlogin.azurecr.io' }}
@@ -52,11 +52,11 @@ jobs:
         id: determine_tag
         run: |
           if [[ "${{ github.ref }}" == "refs/heads/main" ]]; then
-            echo "TAG=latest_v3" >> $GITHUB_ENV
-          elif [[ "${{ github.ref }}" == "refs/heads/dev-v3" ]]; then
-            echo "TAG=dev_v3" >> $GITHUB_ENV
-          elif [[ "${{ github.ref }}" == "refs/heads/demo-v3" ]]; then
-            echo "TAG=demo_v3" >> $GITHUB_ENV
+            echo "TAG=latest_v4" >> $GITHUB_ENV
+          elif [[ "${{ github.ref }}" == "refs/heads/dev-v4" ]]; then
+            echo "TAG=dev_v4" >> $GITHUB_ENV
+          elif [[ "${{ github.ref }}" == "refs/heads/demo-v4" ]]; then
+            echo "TAG=demo_v4" >> $GITHUB_ENV
           elif [[ "${{ github.ref }}" == "refs/heads/hotfix" ]]; then
             echo "TAG=hotfix" >> $GITHUB_ENV
           else

@@ -12,7 +12,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v3
+        uses: actions/setup-python@v4
         with:
           python-version: ${{ matrix.python-version }}
 

@@ -26,7 +26,7 @@ jobs:
 
     steps:
       - name: Checkout code
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Set up Python
         uses: actions/setup-python@v4

@@ -337,7 +337,7 @@ PublishScripts/
 !**/packages/build/
 # Uncomment if necessary however generally it will be regenerated when needed
 #!**/packages/repositories.config
-# NuGet v3's project.json files produces more ignorable files
+# NuGet v4's project.json files produces more ignorable files
 *.nuget.props
 *.nuget.targets
 

@@ -8,7 +8,7 @@
 import pytest
 
 # Add the agents path
-agents_path = Path(__file__).parent.parent.parent / "backend" / "v3" / "magentic_agents"
+agents_path = Path(__file__).parent.parent.parent / "backend" / "v4" / "magentic_agents"
 sys.path.insert(0, str(agents_path))
 
 @pytest.fixture

@@ -18,9 +18,7 @@
       "use_mcp": false,
       "use_bing": false,
       "use_reasoning": false,
-      "index_name": "macae-index",
-      "index_foundry_name": "",
-      "index_endpoint": "",
+      "index_name": "macae-retail-customer-index",
       "coding_tools": false
     },
     {
@@ -35,7 +33,7 @@
       "use_mcp": false,
       "use_bing": false,
       "use_reasoning": false,
-      "index_name": "macae-index",
+      "index_name": "macae-retail-order-index",
       "index_foundry_name": "",
       "coding_tools": false
     },
@@ -45,8 +43,8 @@
       "name": "AnalysisRecommendationAgent",
       "deployment_name": "o4-mini",
       "icon": "",
-      "system_message": "You are a reasoning agent that can analyze customer data and provide recommendations for improving customer satisfaction and retention. You do not have access to any data sources, but you can reason based on the information provided to you by other agents. Use your reasoning skills to identify patterns, trends, and insights that can help improve customer satisfaction and retention. Provide actionable recommendations based on your analysis. You have access to other agents that can answer questions and provide data about customers, products, orders, inventory, and fulfilment. Use these agents to gather information as needed.",
-      "description": "A reasoning agent that can analyze customer data and provide recommendations for improving customer satisfaction and retention.",
+      "system_message": "You are a reasoning agent that can analyze customer and order data and provide recommendations for improving customer satisfaction and retention. You do not have access to any data sources, but you can reason based on the information provided to you by other agents. Use your reasoning skills to identify patterns, trends, and insights that can help improve customer satisfaction and retention. Provide actionable recommendations based on your analysis. You have access to other agents that can answer questions and provide data about customers, products, orders, inventory, and fulfilment. Use these agents to gather information as needed.",
+      "description": "A reasoning agent that can analyze customer and order data and provide recommendations for improving customer satisfaction and retention.",
       "use_rag": false,
       "use_mcp": false,
       "use_bing": false,

@@ -0,0 +1,71 @@
+{
+  "id": "1",
+  "team_id": "team-clm-1",
+  "name": "RFP Team",
+  "status": "visible",
+  "created": "",
+  "created_by": "",
+  "description": "A specialized multi-agent team that analyzes RFP and contract documents to summarize content, identify potential risks, check compliance gaps, and provide action plans for contract improvement.",
+  "logo": "",
+  "plan": "",
+  "agents": [
+    {
+      "input_key": "",
+      "type": "summary",
+      "name": "SummaryAgent",
+      "deployment_name": "gpt-4.1-mini",
+      "icon": "",
+      "system_message":"You are the Summary Agent. Your role is to read and synthesize RFP or proposal documents into clear, structured executive summaries. Focus on key clauses, deliverables, evaluation criteria, pricing terms, timelines, and obligations. Organize your output into sections such as Overview, Key Clauses, Deliverables, Terms, and Notable Conditions. Highlight unique or high-impact items that other agents (Risk or Compliance) should review. Be concise, factual, and neutral in tone.",
+      "description": "Summarizes RFP and contract documents into structured, easy-to-understand overviews.",
+      "use_rag": true,
+      "use_mcp": false,
+      "use_bing": false,
+      "use_reasoning": false,
+      "index_name": "macae-rfp-index",
+      "index_foundry_name": "",
+      "index_endpoint": "",
+      "coding_tools": false
+    },
+    {
+      "input_key": "",
+      "type": "risk",
+      "name": "RiskAgent",
+      "deployment_name": "gpt-4.1-mini",
+      "icon": "",
+      "system_message": "You are the Risk Agent. Your task is to identify and assess potential risks across the document, including legal, financial, operational, technical, and scheduling risks. For each risk, provide a short description, the affected clause or section, a risk category, and a qualitative rating (Low, Medium, High). Focus on material issues that could impact delivery, compliance, or business exposure. Summarize findings clearly to support decision-making and escalation.",
+      "description": "Analyzes the dataset for risks such as delivery, financial, operational, and compliance-related vulnerabilities.",
+      "use_rag": true,
+      "use_mcp": false,
+      "use_bing": false,
+      "use_reasoning": false,
+      "index_name": "macae-rfp-index",
+      "coding_tools": false
+    },
+    {
+      "input_key": "",
+      "type": "compliance",
+      "name": "ComplianceAgent",
+      "deployment_name": "gpt-4.1-mini",
+      "icon": "",
+      "system_message": "You are the Compliance Agent. Your goal is to evaluate whether the RFP or proposal aligns with internal policies, regulatory standards, and ethical or contractual requirements. Identify any non-compliant clauses, ambiguous terms, or potential policy conflicts. For each issue, specify the related policy area (e.g., data privacy, labor, financial controls) and classify it as Mandatory or Recommended for review. Maintain a professional, objective tone and emphasize actionable compliance insights.",
+      "description": "Checks for compliance gaps against regulations, policies, and standard contracting practices.",
+      "use_rag": true,
+      "use_mcp": false,
+      "use_bing": false,
+      "use_reasoning": false,
+      "index_name": "macae-rfp-index",
+      "coding_tools": false
+    }
+  ],
+  "protected": false,
+  "starting_tasks": [
+    {
+      "id": "task-1",
+      "name": "RFP Document Summary",
+      "prompt": "I would like to review the Woodgrove Bank RFP response from Contoso",
+      "created": "",
+      "creator": "",
+      "logo": ""
+    }
+  ]
+}
@@ -9,6 +9,7 @@ This document provides guidance on post-deployment steps after deploying the Mul
 ## Overview
 
 After deploying the infrastructure using AVM, you'll need to complete the application layer setup, which includes:
+
 - Configuring team agent configurations
 - Processing and uploading sample datasets
 - Setting up Azure AI Search indexes
@@ -25,14 +26,15 @@ Before starting the post-deployment process, ensure you have the following:
 
 2. **[Azure CLI](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli)** <small>(v2.50+)</small> - Command-line tool for managing Azure resources
 
-3. **[Python](https://www.python.org/downloads/)** <small>(v3.9+ recommended)</small> - Required for data processing scripts
+3. **[Python](https://www.python.org/downloads/)** <small>(v4.9+ recommended)</small> - Required for data processing scripts
 
 4. **[Git](https://git-scm.com/downloads/)** - Version control system for cloning the repository
 
 ### Azure Requirements
 
 5. **Azure Access** - One of the following roles on the subscription or resource group:
-   - `Contributor` 
+
+   - `Contributor`
    - `Owner`
 
 6. **Deployed Infrastructure** - A successful Multi-Agent Custom Automation Engine deployment from the [AVM repository](https://github.com/Azure/bicep-registry-modules/tree/main/avm/ptn/sa/multi-agent-custom-automation-engine)
@@ -56,6 +58,7 @@ First, clone this repository to access the post-deployment scripts:
 ```powershell
 git clone https://github.com/microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator.git
 ```
+
 ```powershell
 cd Multi-Agent-Custom-Automation-Engine-Solution-Accelerator
 ```
@@ -65,6 +68,7 @@ cd Multi-Agent-Custom-Automation-Engine-Solution-Accelerator
 The post-deployment process is automated through a single PowerShell or Bash script that completes the following tasks in approximately 5-10 minutes:
 
 #### What the Script Does:
+
 1. **Configure Team Agent Settings** - Upload HR, Marketing, and Retail team configurations
 2. **Process Sample Datasets** - Upload and index sample customer data, analytics, and business metrics
 3. **Set Up Azure AI Search** - Create and configure search indexes for agent data retrieval
@@ -77,6 +81,7 @@ The post-deployment process is automated through a single PowerShell or Bash scr
    **If you deployed using custom templates, ARM/Bicep deployments, or `az deployment group` commands:**
 
    - **For PowerShell (Windows/Linux/macOS):**
+
      ```powershell
      .\infra\scripts\Team-Config-And-Data.ps1 -ResourceGroup "<your-resource-group-name>"
      ```
@@ -85,10 +90,11 @@ The post-deployment process is automated through a single PowerShell or Bash scr
      ```bash
      bash infra/scripts/team_config_and_data.sh "<your-resource-group-name>"
      ```
-   
+
    **If you deployed using `azd up` command:**
 
    - **For PowerShell (Windows/Linux/macOS):**
+
      ```powershell
      .\infra\scripts\Team-Config-And-Data.ps1
      ```
@@ -97,7 +103,7 @@ The post-deployment process is automated through a single PowerShell or Bash scr
      ```bash
      bash infra/scripts/team_config_and_data.sh
      ```
-   
+
    > **Note**: Replace `<your-resource-group-name>` with the actual name of the resource group containing your deployed Azure resources.
 
    > **💡 Tip**: Since this guide is for AVM deployments, you'll most likely use the first command with the `-ResourceGroup` parameter.
@@ -110,6 +116,7 @@ During script execution, you'll be prompted for:
 - Select the appropriate Azure subscription
 
 #### Resource Validation
+
 - The script will automatically detect and validate your deployed Azure resources
 - Confirmation prompts will appear before making configuration changes
 
@@ -121,4 +128,4 @@ Upon successful completion, you'll see a success message.
 
 ### Step 5: Set Up App Authentication (Optional)
 
-Follow the steps in [Set Up Authentication in Azure App Service](azure_app_service_auth_setup.md) to add app authentication to your web app running on Azure App Service.
+Follow the steps in [Set Up Authentication in Azure App Service](azure_app_service_auth_setup.md) to add app authentication to your web app running on Azure App Service.