fix: Contact Center Scenario Displays Incorrect Dataset Title Instead of "Contact Center Dataset"

[Priyanka2-Microsoft]

Purpose

• ...
  This pull request introduces improvements to package management and deployment reliability across the project. The main changes are the enforcement of custom package registries for both Python and Node.js dependencies, enhancements to deployment scripts to ensure backend SQL readiness, and infrastructure template adjustments for improved resource deployment sequencing.

Package Management and Dependency Configuration:

• Enforces the use of the Microsoft package feed proxy for Python dependencies by adding --index-url https://packagefeedproxy.microsoft.io/pypi/simple/ to all relevant requirements.txt files and setting the PIP_INDEX_URL environment variable in GitHub Actions workflows (.github/workflows/deploy.yml, .github/workflows/job-test-automation.yml, .github/workflows/pylint.yml, .github/workflows/test-automation.yml, .github/workflows/test.yml, infra/scripts/post-provision/requirements.txt, infra/vscode_web/endpoint-requirements.txt, infra/vscode_web/requirements.txt, src/api/requirements.txt) [1] [2] [3] [4] [5] [6] [7] [8].
• Configures Node.js to use the Microsoft npm registry by updating .npmrc, Dockerfiles, and devcontainer settings (src/app/.npmrc, .devcontainer/Dockerfile, .devcontainer/devcontainer.json, src/app/WebApp.Dockerfile) [1] [2] [3] [4].

Deployment and Reliability Enhancements:

• Adds a PowerShell function in setup-data.ps1 to wait for backend SQL connectivity before proceeding with scenario registration, reducing race conditions during deployment.
• Updates SQL service initialization logging to indicate that failed initialization attempts will be retried, improving resiliency (src/api/storage/sql_service.py).

Infrastructure Template Updates:

• Changes the default value of virtualMachineAvailabilityZone from 1 to -1 in Bicep and generated ARM templates, and adjusts resource dependency ordering for private DNS zones to ensure correct deployment sequencing (infra/avm/main.bicep, infra/avm/main.json, infra/main.json) [1] [2] [3] [4] [5].

Dependency Updates:

• Updates PyYAML version in src/api/requirements.txt from 6.0.2 to 6.0.3.

These changes ensure all environments and CI pipelines consistently use the organization's package feeds, improve deployment robustness, and address minor dependency and infrastructure issues.

BUG ID : https://dev.azure.com/CSACTOSOL/CSA%20Solutioning/_workitems/edit/50875/

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

[Copilot]

Pull request overview

This pull request improves deployment/runtime resiliency by (1) changing Azure SQL initialization behavior to allow retries after transient failures and (2) adding a post-provision script gate that waits for backend SQL connectivity before attempting scenario registration/cleanup calls.

Changes:

• Update Azure SQL init logging to indicate failures will be retried on subsequent use.
• Add Wait-ForBackendSqlHealthy to poll /api/health until SQL is reachable before proceeding with data setup.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/api/storage/sql_service.py	Updates Azure SQL init failure handling/log messaging to support retry-on-next-use semantics.
infra/scripts/post-provision/setup-data.ps1	Adds a SQL readiness wait/poll step against the backend deep health endpoint before scenario/data operations.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.