chore: merging dev changes into main

[Roopan-Microsoft]

Purpose

This pull request introduces important improvements to authentication and security guidance for Azure Container Apps deployments, ensuring that both frontend and backend APIs are properly protected. It updates documentation and setup scripts to require backend authentication for public deployments, clarifies quota requirements for additional Azure OpenAI models, and upgrades infrastructure templates. The most significant changes are summarized below.

Authentication & Security Enhancements:

• Updated documentation to require backend authentication for public deployments, emphasizing that both frontend and backend Container Apps must be secured to prevent anonymous access to admin APIs. Added detailed instructions and warnings about running the setup_auth script, which now configures both apps in one step. [1]], [2]], [3]])
• Improved post-deployment setup guidance in azure.yaml and relevant scripts, adding explicit steps to run the authentication setup script (setup_auth.ps1 or setup_auth.sh) after deployment for both Windows and Bash environments. [1]], [2]])

Quota & Model Guidance Updates:

• Updated quota documentation to include both the chat (gpt-5.4-mini) and reasoning (gpt-5-mini) models, ensuring users check for sufficient quota for both models post-deployment. Adjusted example commands and quota check instructions accordingly. [1]], [2]], [3]], [4]], [5]])

Infrastructure & Metadata:

• Upgraded Bicep template version and hashes in infra/avm/main.json to reflect the latest tooling and template changes. [1]], [2]], [3]], [4]], [5]], [6]], [7]], [8]], [9]], [10]], [11]], [12]])

Documentation Improvements:

• Clarified and expanded explanations in admin and authentication docs, including new details on layered access control, the importance of backend authentication, and step-by-step alternative manual setup in the portal. [1]], [2]])

Metadata and Dates:

• Updated documentation metadata such as ms.date and descriptions to reflect the latest changes and improve clarity. [1]], [2]])

These changes collectively strengthen the security posture of deployments, provide clearer operational guidance, and ensure compatibility with updated Azure infrastructure tooling.

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information