Purpose

This pull request introduces several improvements and fixes across the Azure deployment workflow, infrastructure scripts, troubleshooting documentation, and the React codebase. The most significant changes include restructuring Azure deployment workflows for better separation of concerns, enhancing troubleshooting documentation for private networking scenarios, improving the robustness of schema registration scripts, and removing the unused axios dependency from the frontend project.

Azure Workflow and Infrastructure Updates:

• Separated Azure template validation and deployment into two distinct GitHub Actions workflows: .github/workflows/azd-template-validation.yml now handles scheduled and manual template validation, while .github/workflows/azure-dev.yaml focuses on provisioning and deploying resources using azd, with clearer steps for environment setup and Azure authentication. [1] [2]
• Added a required Bicep version (>= 0.33.0) to azure.yaml to ensure infrastructure compatibility.
• The main Bicep template (infra/main.bicep) now outputs the name of the Content Understanding AI Services account for downstream use.

Troubleshooting and Documentation Enhancements:

• Expanded docs/TroubleShootingSteps.md with a new troubleshooting entry for "403 Forbidden" errors from Content Understanding in WAF/private networking deployments, including detailed causes and step-by-step resolutions. [1] [2]

Infrastructure Script Improvements:

• Refactored array handling in infra/scripts/post_deployment.sh for schema registration, improving correctness and maintainability. [1] [2] [3] [4]
• Added an automated refresh step for the Content Understanding Cognitive Services account at the end of the post-deployment script to ensure tag updates and resource readiness.

Frontend/React Codebase Clean-up:

• Removed the unused axios dependency from src/ContentProcessorWeb/package.json and pnpm-lock.yaml, and updated test instructions to reference httpUtility as the module to mock for API calls. [1] [2] [3] [4] [5] [6]
• Minor documentation and state mapping improvements in React code and instructions. [1] [2]

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information