fix: merging dev to main

[Roopan-Microsoft]

Purpose

• This pull request introduces significant changes to the infrastructure and data processing scripts to standardize and improve the use of Azure Managed Identities and Azure AI Foundry (Inference) services. The main updates include replacing the previous SQL-specific managed identity with a more general backend managed identity, updating role assignments and resource references throughout the Bicep infrastructure, and refactoring Python scripts to use the new Azure AI Foundry clients for embeddings and chat completions.

Infrastructure changes:

• Replaced the dedicated SQL managed identity (sqlUserAssignedIdentity) with a new, more general backend managed identity (backendUserAssignedIdentity). All resource assignments, outputs, and environment variables now reference the backend identity instead of the SQL-specific one. [1] [2] [3] [4] [5]
• Updated role assignments for Azure AI services, Search, and CosmosDB to grant necessary permissions to the backend managed identity, ensuring it has access to required resources. [1] [2] [3] [4]
• Adjusted outputs and deployment script parameters to use the backend managed identity, streamlining identity usage across the solution. [1] [2]

Python script refactoring:

• Migrated from the legacy openai library to the new Azure AI Foundry (Inference) clients (ChatCompletionsClient, EmbeddingsClient) for chat completions and embeddings, improving compatibility and future-proofing. [1] [2] [3] [4]
• Refactored secret retrieval and endpoint configuration to use new Azure AI Agent endpoints and deployment names, supporting the new inference clients. [1] [2]
• Updated embedding and chat completion utility functions and their usage throughout the scripts to work with the new client interfaces, simplifying function signatures and error handling. [1] [2] [3] [4]

These changes collectively enhance security, maintainability, and alignment with Azure best practices for identity and AI service integration.

References:
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21]

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

[github-actions]

🎉 This PR is included in version 3.15.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀