Merge pull request microsoft#1082 from microsoft/psl-mainChanges

feat: upgrade to GPT-5.4 models, add default teams with per-user isolation, and ACR image build scripts

Author: Avijit-Microsoft

.github/workflows/azd-template-validation.yml

@@ -34,7 +34,7 @@ jobs:
           AZURE_LOCATION: ${{ vars.AZURE_LOCATION }}
           AZURE_ENV_AI_SERVICE_LOCATION: ${{ vars.AZURE_AI_DEPLOYMENT_LOCATION }}
           AZURE_ENV_GPT_MODEL_CAPACITY: 1
-          AZURE_ENV_MODEL_4_1_CAPACITY: 1 # keep low to avoid potential quota issues
+          AZURE_ENV_MODEL_5_4_CAPACITY: 1 # keep low to avoid potential quota issues
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
       - name: print result

.github/workflows/azure-dev.yml

@@ -18,7 +18,7 @@ jobs:
       AZURE_LOCATION: ${{ vars.AZURE_LOCATION }}
       AZURE_ENV_AI_SERVICE_LOCATION: ${{ vars.AZURE_AI_DEPLOYMENT_LOCATION }}
       AZURE_ENV_GPT_MODEL_CAPACITY: 1
-      AZURE_ENV_MODEL_4_1_CAPACITY: 1
+      AZURE_ENV_MODEL_5_4_CAPACITY: 1
       GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
       AZURE_DEV_COLLECT_TELEMETRY: ${{ vars.AZURE_DEV_COLLECT_TELEMETRY }}
     steps:

.github/workflows/deploy-waf.yml

@@ -22,9 +22,8 @@ jobs:
     runs-on: ubuntu-latest
     environment: production
     env:
-      GPT_MIN_CAPACITY: 1
-      O4_MINI_MIN_CAPACITY: 1
-      GPT41_MINI_MIN_CAPACITY: 1
+      GPT_5_4_MINI_MIN_CAPACITY: 1
+      GPT_5_4_MIN_CAPACITY: 1
     steps:
       - name: Checkout Code
         uses: actions/checkout@v6
@@ -40,9 +39,8 @@ jobs:
         id: quota-check
         env:
           AZURE_SUBSCRIPTION_ID: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
-          GPT_MIN_CAPACITY: ${{ env.GPT_MIN_CAPACITY }}
-          O4_MINI_MIN_CAPACITY: ${{ env.O4_MINI_MIN_CAPACITY }}
-          GPT41_MINI_MIN_CAPACITY: ${{ env.GPT41_MINI_MIN_CAPACITY }}
+          GPT_5_4_MINI_MIN_CAPACITY: ${{ env.GPT_5_4_MINI_MIN_CAPACITY }}
+          GPT_5_4_MIN_CAPACITY: ${{ env.GPT_5_4_MIN_CAPACITY }}
           AZURE_REGIONS: ${{ vars.AZURE_REGIONS }}
         run: |
           chmod +x infra/scripts/checkquota.sh
@@ -133,9 +131,8 @@ jobs:
               solutionName=${{ env.SOLUTION_PREFIX }} \
               location="${{ env.AZURE_LOCATION }}" \
               azureAiServiceLocation='${{ env.AZURE_LOCATION }}' \
-              gptDeploymentCapacity=${{ env.GPT_MIN_CAPACITY }} \
-              gpt4_1ModelCapacity=${{ env.GPT41_MINI_MIN_CAPACITY }} \
-              gptReasoningModelCapacity=${{ env.O4_MINI_MIN_CAPACITY }} \
+              gptDeploymentCapacity=${{ env.GPT_5_4_MINI_MIN_CAPACITY }} \
+              gpt5_4ModelCapacity=${{ env.GPT_5_4_MIN_CAPACITY }} \
               enableTelemetry=true \
               enableMonitoring=true \
               enablePrivateNetworking=true \

.github/workflows/deploy.yml

@@ -17,9 +17,8 @@ on:
     - cron: "0 11,23 * * *" # Runs at 11:00 AM and 11:00 PM GMT
   workflow_dispatch: #Allow manual triggering
 env:
-  GPT_MIN_CAPACITY: 150
-  O4_MINI_MIN_CAPACITY: 50
-  GPT41_MINI_MIN_CAPACITY: 50
+  GPT_5_4_MINI_MIN_CAPACITY: 100
+  GPT_5_4_MIN_CAPACITY: 150
   BRANCH_NAME: ${{ github.head_ref || github.ref_name }}
 
 jobs:
@@ -47,9 +46,8 @@ jobs:
         id: quota-check
         env:
           AZURE_SUBSCRIPTION_ID: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
-          GPT_MIN_CAPACITY: ${{ env.GPT_MIN_CAPACITY }}
-          O4_MINI_MIN_CAPACITY: ${{ env.O4_MINI_MIN_CAPACITY }}
-          GPT41_MINI_MIN_CAPACITY: ${{ env.GPT41_MINI_MIN_CAPACITY }}
+          GPT_5_4_MINI_MIN_CAPACITY: ${{ env.GPT_5_4_MINI_MIN_CAPACITY }}
+          GPT_5_4_MIN_CAPACITY: ${{ env.GPT_5_4_MIN_CAPACITY }}
           AZURE_REGIONS: ${{ vars.AZURE_REGIONS }}
         run: |
           chmod +x infra/scripts/checkquota.sh
@@ -153,7 +151,7 @@ jobs:
               backendContainerImageTag="${IMAGE_TAG}" \
               frontendContainerImageTag="${IMAGE_TAG}" \
               azureAiServiceLocation='${{ env.AZURE_LOCATION }}' \
-              gptDeploymentCapacity=50 \
+              gptDeploymentCapacity=100 \
               createdBy="Pipeline" \
               tags="{'Purpose':'Deploying and Cleaning Up Resources for Validation','CreatedDate':'$current_date'}" \
             --output json

.github/workflows/job-deploy.yml

@@ -98,9 +98,8 @@ on:
         value: ${{ jobs.azure-setup.outputs.QUOTA_FAILED }}
 
 env:
-  GPT_MIN_CAPACITY: 150
-  O4_MINI_MIN_CAPACITY: 50
-  GPT41_MINI_MIN_CAPACITY: 50
+  GPT_5_4_MINI_MIN_CAPACITY: 100
+  GPT_5_4_MIN_CAPACITY: 150
   BRANCH_NAME: ${{ github.event.workflow_run.head_branch || github.head_ref || github.ref_name }}
   WAF_ENABLED: ${{ inputs.trigger_type == 'workflow_dispatch' && (inputs.waf_enabled || false) || false }}
   EXP: ${{ inputs.trigger_type == 'workflow_dispatch' && (inputs.EXP || false) || false }}
@@ -306,9 +305,8 @@ jobs:
         id: quota-check
         env:
           AZURE_SUBSCRIPTION_ID: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
-          GPT_MIN_CAPACITY: ${{ env.GPT_MIN_CAPACITY }}
-          O4_MINI_MIN_CAPACITY: ${{ env.O4_MINI_MIN_CAPACITY }}
-          GPT41_MINI_MIN_CAPACITY: ${{ env.GPT41_MINI_MIN_CAPACITY }}
+          GPT_5_4_MINI_MIN_CAPACITY: ${{ env.GPT_5_4_MINI_MIN_CAPACITY }}
+          GPT_5_4_MIN_CAPACITY: ${{ env.GPT_5_4_MIN_CAPACITY }}
           AZURE_REGIONS: ${{ vars.AZURE_REGIONS }}
         run: |
           chmod +x infra/scripts/checkquota.sh

.github/workflows/job-send-notification.yml

@@ -68,7 +68,7 @@ on:
         type: string
 
 env:
-  GPT_MIN_CAPACITY: 100
+  GPT_5_4_MINI_MIN_CAPACITY: 100
   BRANCH_NAME: ${{ github.event.workflow_run.head_branch || github.head_ref || github.ref_name }}
   WAF_ENABLED: ${{ inputs.trigger_type == 'workflow_dispatch' && (inputs.waf_enabled || false) || false }}
   EXP: ${{ inputs.trigger_type == 'workflow_dispatch' && (inputs.EXP || false) || false }}

TRANSPARENCY_FAQS.md

@@ -26,4 +26,4 @@ The system allows users to review, reorder and approve steps generated in a plan
 
 ## What operational factors and settings allow for effective and responsible use of Multi Agent: Custom Automation Engine – Solution Accelerator? 
 Effective and responsible use of the Multi Agent: Custom Automation Engine – Solution Accelerator depends on several operational factors and settings. The system is designed to perform reliably and safely across a range of business tasks that it was evaluated for. Users can customize certain settings, such as the planning language model used by the system, the types of tasks that agents are assigned, and the specific actions that agents can take (e.g., sending emails or scheduling orientation sessions for new employees). However, it's important to note that these choices may impact the system's behavior in real-world scenarios.
-For example, selecting a planning language model that is not well-suited to the complexity of the tasks may result in lower accuracy and performance. Similarly, assigning tasks that are outside the system's intended scope may lead to errors or incomplete results. Users can choose the LLM that is optimized for responsible use. The default LLM is GPT-4o which inherits the existing RAI mechanisms and filters from the LLM provider. Caching is enabled by default to increase reliability and control cost. 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-40. To ensure effective and responsible use of the accelerator, users should carefully consider their choices and use the system within its intended scope.
+For example, selecting a planning language model that is not well-suited to the complexity of the tasks may result in lower accuracy and performance. Similarly, assigning tasks that are outside the system's intended scope may lead to errors or incomplete results. Users can choose the LLM that is optimized for responsible use. The default LLM is GPT-5.4 which inherits the existing RAI mechanisms and filters from the LLM provider. Caching is enabled by default to increase reliability and control cost. 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-5.4. To ensure effective and responsible use of the accelerator, users should carefully consider their choices and use the system within its intended scope.

azure.yaml

@@ -17,6 +17,11 @@ hooks:
           Write-Host "===============================================================" -ForegroundColor Yellow
           Write-Host ""
 
+          Write-Host " Build and push the backend/frontend/mcp_server container images to ACR, then point the container app and webapp at them:" -ForegroundColor White
+          Write-Host "  👉 Run the following command in Bash:" -ForegroundColor White
+          Write-Host "   bash infra/scripts/build_and_push_images.sh" -ForegroundColor Cyan
+          Write-Host ""
+
           Write-Host " Upload Team Configurations and index sample data" -ForegroundColor White
           Write-Host "  👉 Run the following command in Bash:" -ForegroundColor White
           Write-Host "   bash infra/scripts/selecting_team_config_and_data.sh" -ForegroundColor Cyan
@@ -33,6 +38,11 @@ hooks:
           Write-Host "===============================================================" -ForegroundColor Yellow
           Write-Host ""
 
+          Write-Host " Build and push the backend/frontend/mcp_server container images to ACR, then point the container app and webapp at them:" -ForegroundColor White
+          Write-Host "  👉 Run the following command in PowerShell:" -ForegroundColor White
+          Write-Host "   infra\scripts\Build-And-Push-Images.ps1" -ForegroundColor Cyan
+          Write-Host ""
+
           Write-Host " Upload Team Configurations and index sample data" -ForegroundColor White
           Write-Host "  👉 Run the following command in PowerShell:" -ForegroundColor White
           Write-Host "   infra\scripts\Selecting-Team-Config-And-Data.ps1" -ForegroundColor Cyan
@@ -58,6 +68,10 @@ hooks:
         printf "${Green} POST-DEPLOYMENT STEPS (Bash)\n"
         printf "${Yellow}===============================================================${NC}\n\n"
 
+        printf  "Build and push the backend/frontend/mcp_server container images to ACR, then point the container app and webapp at them:\n"
+        printf  "  👉 Run the following command in Bash:\n"
+        printf  "   ${Blue}bash infra/scripts/build_and_push_images.sh${NC}\n\n"
+
         printf  "Upload Team Configurations and index sample data:\n"
         printf  "  👉 Run the following command in Bash:\n"
         printf  "   ${Blue}bash infra/scripts/selecting_team_config_and_data.sh${NC}\n\n"
@@ -66,4 +80,4 @@ hooks:
         printf "   ${Blue}https://%s${NC}\n\n" "$webSiteDefaultHostname"
 
       shell: sh
-      interactive: true
+      interactive: true

data/agent_teams/contract_compliance_team.json

@@ -5,7 +5,8 @@
   "status": "visible",
   "created": "",
   "created_by": "",
-  "deployment_name": "gpt-4.1-mini",
+  "deployment_name": "gpt-5.4-mini",
+  "is_default": true,
   "description": "A multi-agent compliance review team that summarizes NDAs, identifies risks, checks compliance, and recommends improvements using advanced legal reasoning and retrieval-augmented analysis.",
   "logo": "",
   "plan": "",
@@ -14,7 +15,7 @@
       "input_key": "",
       "type": "summary",
       "name": "ContractSummaryAgent",
-      "deployment_name": "gpt-4.1-mini",
+      "deployment_name": "gpt-5.4-mini",
       "icon": "",
       "system_message": "You are the Summary Agent for compliance contract analysis. Your task is to produce a clear, accurate, and structured executive summary of NDA and legal agreement documents. You must deliver summaries organized into labeled sections including: Overview, Parties, Effective Date, Purpose, Definition of Confidential Information, Receiving Party Obligations, Term & Termination, Governing Law, Restrictions & Limitations, Miscellaneous Clauses, Notable or Unusual Terms, and Key Items for Risk & Compliance Agents. Highlight missing elements such as liability caps, dispute resolution mechanisms, data handling obligations, or ambiguous language. Maintain a precise, neutral legal tone. Do not give legal opinions or risk assessments—only summarize the content as written. Use retrieval results from the search index to ensure completeness and reference contextual definitions or standard clause expectations when needed.",
       "description": "Produces comprehensive, structured summaries of NDAs and contracts, capturing all key terms, clauses, obligations, jurisdictions, and notable provisions.",
@@ -29,7 +30,7 @@
       "input_key": "",
       "type": "risk",
       "name": "ContractRiskAgent",
-      "deployment_name": "gpt-4.1-mini",
+      "deployment_name": "gpt-5.4-mini",
       "icon": "",
       "system_message": "You are the Risk Agent for NDA and compliance contract analysis. Use the NDA Risk Assessment Reference document and retrieved context to identify High, Medium, and Low risk issues. Evaluate clauses for missing liability caps, ambiguous terms, overly broad confidentiality definitions, jurisdiction misalignment, missing termination rights, unclear data handling obligations, missing dispute resolution, and any incomplete or poorly scoped definitions. For every risk you identify, provide: (1) Risk Category (High/Medium/Low), (2) Clause or Section impacted, (3) Description of the issue, (4) Why it matters or what exposure it creates, and (5) Suggested edit or corrective language. Apply the risk scoring framework: High = escalate immediately; Medium = requires revision; Low = minor issue. Be precise, legally aligned, and practical. Reference retrieved examples or standards when appropriate. Your output must be structured and actionable.",
       "description": "Identifies and classifies compliance risks in NDAs and contracts using the organization's risk framework, and provides suggested edits to reduce exposure.",
@@ -44,7 +45,7 @@
       "input_key": "",
       "type": "compliance",
       "name": "ContractComplianceAgent",
-      "deployment_name": "gpt-4.1-mini",
+      "deployment_name": "gpt-5.4-mini",
       "icon": "",
       "system_message": "You are the Compliance Agent responsible for validating NDAs and legal agreements against mandatory legal and policy requirements. Use the NDA Compliance Reference Document and retrieval results to evaluate whether the contract includes all required clauses: Confidentiality, Term & Termination, Governing Law aligned to approved jurisdictions, Non-Assignment, and Entire Agreement. Identify compliance gaps including ambiguous language, missing liability protections, improper jurisdiction, excessive term length, insufficient data protection obligations, missing dispute resolution mechanisms, or export control risks. For each issue provide: (1) Compliance Area (e.g., Term Length, Jurisdiction, Confidentiality), (2) Status (Pass/Fail), (3) Issue Description, (4) Whether it is Mandatory or Recommended, (5) Corrective Recommendation or Suggested Language. Deliver a final Compliance Status summary. Maintain professional, objective, legally accurate tone.",
       "description": "Performs compliance validation of NDAs and contracts against legal policy requirements, identifies gaps, and provides corrective recommendations and compliance status.",

data/agent_teams/hr.json

@@ -5,13 +5,14 @@
   "status": "visible",
   "created": "",
   "created_by": "",
-  "deployment_name": "gpt-4.1-mini",
+  "deployment_name": "gpt-5.4-mini",
+  "is_default": true,
   "agents": [
     {
       "input_key": "",
       "type": "",
       "name": "HRHelperAgent",
-      "deployment_name": "gpt-4.1-mini",
+      "deployment_name": "gpt-5.4-mini",
       "icon": "",
       "system_message": "You have access to a number of HR related MCP tools for tasks like employee onboarding, benefits management, policy guidance, and general HR inquiries. Use these tools to assist employees with their HR needs efficiently and accurately.If you need more information to accurately call these tools, do not make up answers, call the ProxyAgent for clarification.",
       "description": "An agent that has access to various HR tools to assist employees with onboarding, benefits, policies, and general HR inquiries.",
@@ -28,7 +29,7 @@
       "input_key": "",
       "type": "",
       "name": "TechnicalSupportAgent",
-      "deployment_name": "gpt-4.1-mini",
+      "deployment_name": "gpt-5.4-mini",
       "icon": "",
       "system_message": "You have access to a number of technical support MCP tools for tasks such as provisioning laptops, setting up email accounts, troubleshooting, software/hardware issues, and IT support. Use these tools to assist employees with their technical needs efficiently and accurately.  If you need more information to accurately call these tools, do not make up answers, call the ProxyAgent for clarification.",
       "description": "An agent that has access to various technical support tools to assist employees with IT needs like laptop provisioning, email setup, troubleshooting, and software/hardware issues.",