fix: deployment script issue - Add Azure AI Agent endpoint

[Pavan-Microsoft]

Purpose

This pull request updates the infrastructure code to support new AI agent endpoints, refactors identity naming, and upgrades the Azure API versions across multiple resources for improved compatibility and future-proofing. The most significant changes are the addition of the AZURE-AI-AGENT-ENDPOINT secret, renaming of identity resources, and broad updates to API versions in deployment templates.

KeyVault and Secrets Management:

• Added a new secret, AZURE-AI-AGENT-ENDPOINT, to both the Bicep and generated ARM templates, allowing downstream services to access the AI agent endpoint. [1] [2]
• Updated logic to retrieve the AI agent endpoint from either an existing value or the output of the aiFoundryAiServices resource. [1] [2]

User Assigned Identity Refactoring:

• Renamed the SQL user-assigned identity to backend user-assigned identity throughout the codebase, including variable names and resource deployment definitions. [1] [2]
• Updated role assignments to include the backend user-assigned identity for Cognitive Services resources. [1] [2]

Azure API Version Upgrades:

• Upgraded apiVersion for all major Azure resource deployments (e.g., Key Vault, Virtual Network, Application Insights, Bastion Host, Managed Identity, Private DNS Zone, CosmosDB, Storage Account, Cognitive Services, Private Endpoint, Secrets Export, AI Project) from 2022-09-01 to 2025-04-01. This improves compatibility with the latest Azure features and ensures long-term support. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]

Template and Metadata Updates:

• Updated Bicep template generator metadata and hashes to reflect the new version (0.39.26.7824) and changes in resource definitions. [1] [2] [3] [4] [5] [6]

Secure Value Retrieval:

• Updated calls to listOutputsWithSecureValues for CosmosDB and Storage Account secrets to use the new API version, ensuring secure and up-to-date secret retrieval. [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.

[github-actions]

🎉 This PR is included in version 3.15.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀