refactor: restructuring infra

.github/agents/speckit.contentpack.agent.md

@@ -153,7 +153,7 @@ referenced in the KB registration.
 
 ### Step 3 — Register the Knowledge Base
 
-Add an entry to `infra/scripts/seed_knowledge_bases.py` in the `KNOWLEDGE_BASES`
+Add an entry to `infra/scripts/post-provision/seed_knowledge_bases.py` in the `KNOWLEDGE_BASES`
 dict. Place it before the `# ── Example Pack ──` comment block:
 
 ```python
@@ -203,7 +203,7 @@ and **never hallucinate data**.
 
 ## Registering in the Deployment Script
 
-Edit `infra/scripts/Selecting-Team-Config-And-Data.ps1`. Search for `NEW CONTENT PACK`
+Edit `infra/scripts/post-provision/Selecting-Team-Config-And-Data.ps1`. Search for `NEW CONTENT PACK`
 — each insertion point has a comment template. There are **4 things** to do:
 
 | # | What | Where |
@@ -245,7 +245,7 @@ After adding your entry, update `$allOption` to `N + 1` so "All" is always last.
 azd up
 
 # 2. Provision pack resources — select your pack or "All"
-./infra/scripts/Selecting-Team-Config-And-Data.ps1 -ResourceGroup <rg>
+./infra/scripts/post-provision/Selecting-Team-Config-And-Data.ps1 -ResourceGroup <rg>
 ```
 
 ---

.github/workflows/deploy-waf.yml

@@ -45,10 +45,10 @@ jobs:
           GPT41_MINI_MIN_CAPACITY: ${{ env.GPT41_MINI_MIN_CAPACITY }}
           AZURE_REGIONS: ${{ vars.AZURE_REGIONS }}
         run: |
-          chmod +x infra/scripts/checkquota.sh
-          if ! infra/scripts/checkquota.sh; then
+          chmod +x infra/scripts/pre-provision/checkquota.sh
+          if ! infra/scripts/pre-provision/checkquota.sh; then
             # If quota check fails due to insufficient quota, set the flag
-            if grep -q "No region with sufficient quota found" infra/scripts/checkquota.sh; then
+            if grep -q "No region with sufficient quota found" infra/scripts/pre-provision/checkquota.sh; then
               echo "QUOTA_FAILED=true" >> $GITHUB_ENV
             fi
             exit 1  # Fail the pipeline if any other failure occurs

.github/workflows/deploy.yml

@@ -52,10 +52,10 @@ jobs:
           GPT41_MINI_MIN_CAPACITY: ${{ env.GPT41_MINI_MIN_CAPACITY }}
           AZURE_REGIONS: ${{ vars.AZURE_REGIONS }}
         run: |
-          chmod +x infra/scripts/checkquota.sh
-          if ! infra/scripts/checkquota.sh; then
+          chmod +x infra/scripts/pre-provision/checkquota.sh
+          if ! infra/scripts/pre-provision/checkquota.sh; then
             # If quota check fails due to insufficient quota, set the flag
-            if grep -q "No region with sufficient quota found" infra/scripts/checkquota.sh; then
+            if grep -q "No region with sufficient quota found" infra/scripts/pre-provision/checkquota.sh; then
               echo "QUOTA_FAILED=true" >> $GITHUB_ENV
             fi
             exit 1  # Fail the pipeline if any other failure occurs
@@ -194,7 +194,7 @@ jobs:
 
           # Run PowerShell script with 'All' use case automatically selected
           # Provide two inputs: '1' for keeping current subscription, '5' for All use cases
-          echo -e "1\n5" | pwsh -File infra/scripts/Selecting-Team-Config-And-Data.ps1 -ResourceGroup "${{ env.RESOURCE_GROUP_NAME }}"
+          echo -e "1\n5" | pwsh -File infra/scripts/post-provision/Selecting-Team-Config-And-Data.ps1 -ResourceGroup "${{ env.RESOURCE_GROUP_NAME }}"
 
           echo "=== Post-Deployment Script Completed Successfully ==="
 

.github/workflows/job-deploy-linux.yml

@@ -360,7 +360,7 @@ jobs:
           
           # Upload team configurations and index sample data in one step
           # Automatically select "6" (All use cases) for non-interactive deployment
-          echo "6" | bash infra/scripts/selecting_team_config_and_data.sh
+          echo "6" | bash infra/scripts/post-provision/selecting_team_config_and_data.sh
 
       - name: Generate Deployment Summary
         if: always()

.github/workflows/job-deploy-windows.yml

@@ -365,7 +365,7 @@ jobs:
           
           # Upload team configurations and index sample data in one step
           # Automatically select "6" (All use cases) for non-interactive deployment
-          echo "6" | bash infra/scripts/selecting_team_config_and_data.sh
+          echo "6" | bash infra/scripts/post-provision/selecting_team_config_and_data.sh
 
       - name: Generate Deployment Summary
         if: always()

.github/workflows/job-deploy.yml

@@ -311,10 +311,10 @@ jobs:
           GPT41_MINI_MIN_CAPACITY: ${{ env.GPT41_MINI_MIN_CAPACITY }}
           AZURE_REGIONS: ${{ vars.AZURE_REGIONS }}
         run: |
-          chmod +x infra/scripts/checkquota.sh
-          if ! infra/scripts/checkquota.sh; then
+          chmod +x infra/scripts/pre-provision/checkquota.sh
+          if ! infra/scripts/pre-provision/checkquota.sh; then
             # If quota check fails due to insufficient quota, set the flag
-            if grep -q "No region with sufficient quota found" infra/scripts/checkquota.sh; then
+            if grep -q "No region with sufficient quota found" infra/scripts/pre-provision/checkquota.sh; then
               echo "QUOTA_FAILED=true" >> $GITHUB_ENV
             fi
             exit 1  # Fail the pipeline if any other failure occurs

.github/workflows/validate-bicep-params.yml

@@ -13,7 +13,7 @@ on:
     paths:
       - 'infra/**/*.bicep'
       - 'infra/**/*.parameters.json'
-      - 'infra/scripts/validate_bicep_params.py'
+      - 'infra/scripts/pre-provision/validate_bicep_params.py'
   workflow_dispatch:
 
 env:
@@ -39,7 +39,7 @@ jobs:
         run: |
           set +e
           RUN_URL="https://github.com/${GITHUB_REPOSITORY}/actions/runs/${GITHUB_RUN_ID}"
-          python infra/scripts/validate_bicep_params.py --dir infra --strict --no-color \
+          python infra/scripts/pre-provision/validate_bicep_params.py --dir infra --strict --no-color \
             --json-output infra_results.json \
             --html-output email_body.html \
             --accelerator-name "${ACCELERATOR_NAME}" \

.gitignore

@@ -17,6 +17,8 @@ appsettings.json
 # Distribution / packaging
 .Python
 build/
+!infra/scripts/build/
+!infra/scripts/build/**
 develop-eggs/
 dist/
 downloads/

azure.yaml

@@ -19,7 +19,7 @@ hooks:
 
           Write-Host " Upload Team Configurations, index sample data and create the Knowledge base from content Packs" -ForegroundColor White
           Write-Host "  👉 Run the following command in Bash:" -ForegroundColor White
-          Write-Host "   bash infra/scripts/post_deploy.sh" -ForegroundColor Cyan
+          Write-Host "   bash infra/scripts/post-provision/post_deploy.sh" -ForegroundColor Cyan
           Write-Host ""
 
           Write-Host "🌐 Access your deployed Frontend application at:" -ForegroundColor Green
@@ -35,7 +35,7 @@ hooks:
 
           Write-Host " Upload Team Configurations, index sample data and create the Knowledge base from content Packs" -ForegroundColor White
           Write-Host "  👉 Run the following command in PowerShell:" -ForegroundColor White
-          Write-Host "   infra\scripts\post_deploy.ps1" -ForegroundColor Cyan
+          Write-Host "   infra\scripts\post-provision\post_deploy.ps1" -ForegroundColor Cyan
           Write-Host ""
 
           Write-Host "🌐 Access your deployed Frontend application at:" -ForegroundColor Green
@@ -60,7 +60,7 @@ hooks:
 
         printf  "Upload Team Configurations, index sample data and create the Knowledge base from content Packs:\n"
         printf  "  👉 Run the following command in Bash:\n"
-        printf  "   ${Blue}bash infra/scripts/post_deploy.sh${NC}\n\n"
+        printf  "   ${Blue}bash infra/scripts/post-provision/post_deploy.sh${NC}\n\n"
 
         printf "🌐 Access your deployed Frontend application at:\n"
         printf "   ${Blue}https://%s${NC}\n\n" "$webSiteDefaultHostname"

azure_custom.yaml

@@ -34,12 +34,12 @@ services:
       prepackage:
         windows:
           shell: pwsh
-          run: ../../infra/scripts/package_frontend.ps1
+          run: ../../infra/scripts/build/package_frontend.ps1
           interactive: true
           continueOnError: false
         posix:
           shell: sh
-          run: bash ../../infra/scripts/package_frontend.sh
+          run: bash ../../infra/scripts/build/package_frontend.sh
           interactive: true
           continueOnError: false
 
@@ -56,9 +56,9 @@ hooks:
           Write-Host "===============================================================" -ForegroundColor Yellow
           Write-Host ""
 
-          Write-Host " Upload Team Configurations and index sample data" -ForegroundColor White
+          Write-Host " Upload Team Configurations, index sample data and create the Knowledge base from content Packs" -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
+          Write-Host "   bash infra/scripts/post-provision/post_deploy.sh" -ForegroundColor Cyan
           Write-Host ""
 
           Write-Host "🌐 Access your deployed Frontend application at:" -ForegroundColor Green
@@ -72,9 +72,9 @@ hooks:
           Write-Host "===============================================================" -ForegroundColor Yellow
           Write-Host ""
 
-          Write-Host " Upload Team Configurations and index sample data" -ForegroundColor White
+          Write-Host " Upload Team Configurations, index sample data and create the Knowledge base from content Packs" -ForegroundColor White
           Write-Host "  👉 Run the following command in PowerShell:" -ForegroundColor White
-          Write-Host "   infra\scripts\Selecting-Team-Config-And-Data.ps1" -ForegroundColor Cyan
+          Write-Host "   infra\scripts\post-provision\post_deploy.ps1" -ForegroundColor Cyan
           Write-Host ""
 
           Write-Host "🌐 Access your deployed Frontend application at:" -ForegroundColor Green
@@ -97,11 +97,12 @@ hooks:
         printf "${Green} POST-DEPLOYMENT STEPS (Bash)\n"
         printf "${Yellow}===============================================================${NC}\n\n"
 
-        printf  "Upload Team Configurations and index sample data:\n"
+        printf  "Upload Team Configurations, index sample data and create the Knowledge base from content Packs:\n"
         printf  "  👉 Run the following command in Bash:\n"
-        printf  "   ${Blue}bash infra/scripts/selecting_team_config_and_data.sh${NC}\n\n"
+        printf  "   ${Blue}bash infra/scripts/post-provision/post_deploy.sh${NC}\n\n"
 
         printf "🌐 Access your deployed Frontend application at:\n"
         printf "   ${Blue}https://%s${NC}\n\n" "$webSiteDefaultHostname"
+
       shell: sh
       interactive: true

content_packs/README.md

@@ -149,7 +149,7 @@ referenced in the KB registration.
 
 ### Step 3 — Register the Knowledge Base
 
-Add an entry to `infra/scripts/seed_knowledge_bases.py` in the `KNOWLEDGE_BASES`
+Add an entry to `infra/scripts/post-provision/seed_knowledge_bases.py` in the `KNOWLEDGE_BASES`
 dict. Place it before the `# ── Example Pack ──` comment block:
 
 ```python
@@ -199,7 +199,7 @@ and **never hallucinate data**.
 
 ## Registering in the Deployment Script
 
-Edit `infra/scripts/Selecting-Team-Config-And-Data.ps1`. Search for `NEW CONTENT PACK`
+Edit `infra/scripts/post-provision/Selecting-Team-Config-And-Data.ps1`. Search for `NEW CONTENT PACK`
 — each insertion point has a comment template. There are **4 things** to do:
 
 | # | What | Where |
@@ -241,7 +241,7 @@ After adding your entry, update `$allOption` to `N + 1` so "All" is always last.
 azd up
 
 # 2. Provision pack resources — select your pack or "All"
-./infra/scripts/Selecting-Team-Config-And-Data.ps1 -ResourceGroup <rg>
+./infra/scripts/post-provision/Selecting-Team-Config-And-Data.ps1 -ResourceGroup <rg>
 ```
 
 ---

content_packs/example_pack/README.md

@@ -107,7 +107,7 @@ Replace `datasets/data/<your_data>` with your source data. Supported formats:
 
 ### Step 4 — Register the Knowledge Base
 
-Add an entry to `infra/scripts/seed_knowledge_bases.py` in the `KNOWLEDGE_BASES` dict:
+Add an entry to `infra/scripts/post-provision/seed_knowledge_bases.py` in the `KNOWLEDGE_BASES` dict:
 
 ```python
     # ── Your Pack ──
@@ -184,7 +184,7 @@ Create `agent_teams/your_pack.json`. Key fields:
 
 ### Step 6 — Register your pack in the deployment script
 
-Edit `infra/scripts/Selecting-Team-Config-And-Data.ps1`. There are **4 locations**
+Edit `infra/scripts/post-provision/Selecting-Team-Config-And-Data.ps1`. There are **4 locations**
 to update (each is marked with a `NEW CONTENT PACK` comment block in the script):
 
 | # | Section | What to add |
@@ -206,22 +206,22 @@ azd up
 
 # 2. Provision pack resources (indexes, blob uploads, team configs, KBs)
 #    Run the post-deploy script and select your pack or "All"
-./infra/scripts/Selecting-Team-Config-And-Data.ps1 -ResourceGroup <rg>
+./infra/scripts/post-provision/Selecting-Team-Config-And-Data.ps1 -ResourceGroup <rg>
 ```
 
 The script handles everything: team config upload, data indexing, and KB seeding.
 For manual runs of individual steps:
 
 ```bash
 # Upload team config only
-python infra/scripts/upload_team_config.py \
+python infra/scripts/post-provision/upload_team_config.py \
   "https://<backend-url>" \
   "content_packs/your_pack/agent_teams" \
   "<user-principal-id>" \
   "<team-uuid>"
 
 # Seed KBs only (after indexes exist)
-python infra/scripts/seed_knowledge_bases.py
+python infra/scripts/post-provision/seed_knowledge_bases.py
 ```
 
 ---
@@ -249,7 +249,7 @@ Use this checklist to verify completeness:
 - [ ] `content_packs/<pack>/datasets/` contains source data files
 - [ ] `content_packs/<pack>/agent_teams/<pack>.json` exists with valid agents
 - [ ] At least one agent has `"use_knowledge_base": true` with a valid `knowledge_base_name`
-- [ ] KB entry added to `infra/scripts/seed_knowledge_bases.py` (index_name matches pack.json)
+- [ ] KB entry added to `infra/scripts/post-provision/seed_knowledge_bases.py` (index_name matches pack.json)
 - [ ] `team_id` is a stable UUID (prevents duplicate teams on re-upload)
 - [ ] `starting_tasks` has at least one example prompt
 - [ ] Agent `system_message` instructs the agent to use its search tool (not hallucinate)

docs/AVMPostDeploymentGuide.md

@@ -82,12 +82,12 @@ The post-deployment process is automated through a single PowerShell or Bash scr
    - **For PowerShell (Windows/Linux/macOS):**
 
      ```powershell
-     infra\scripts\Selecting-Team-Config-And-Data.ps1 -ResourceGroup "<your-resource-group-name>"
+     infra\scripts\post-provision\Selecting-Team-Config-And-Data.ps1 -ResourceGroup "<your-resource-group-name>"
      ```
 
    - **For Bash (Linux/macOS/WSL):**
      ```bash
-     bash infra/scripts/selecting_team_config_and_data.sh --resource-group "<your-resource-group-name>"
+     bash infra/scripts/post-provision/selecting_team_config_and_data.sh --resource-group "<your-resource-group-name>"
      ```
 
    > **Note**: Replace `<your-resource-group-name>` with the actual name of the resource group containing your deployed Azure resources.

docs/DeploymentGuide.md

@@ -345,12 +345,12 @@ After successful deployment:
 
   - **For Bash (Linux/macOS/WSL):**
     ```bash
-    bash infra/scripts/selecting_team_config_and_data.sh
+    bash infra/scripts/post-provision/selecting_team_config_and_data.sh
     ```
 
   - **For PowerShell (Windows):**
     ```powershell
-    infra\scripts\Selecting-Team-Config-And-Data.ps1
+    infra\scripts\post-provision\Selecting-Team-Config-And-Data.ps1
     ```
 
 

docs/quota_check.md

@@ -76,7 +76,7 @@ The final table lists regions with available quota. You can select any of these
    **To check quota for the deployment**  
 
     ```sh
-    curl -L -o quota_check_params.sh "https://raw.githubusercontent.com/microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator/main/infra/scripts/quota_check_params.sh"
+    curl -L -o quota_check_params.sh "https://raw.githubusercontent.com/microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator/main/infra/scripts/pre-provision/quota_check_params.sh"
     chmod +x quota_check_params.sh
     ./quota_check_params.sh
     ```