chore: dev to main merge

[Ragini-Microsoft]

Purpose

This pull request makes significant updates to deployment scripts, documentation, and infrastructure configuration to streamline regional support, remove the separate Content Understanding (CU) resource, and improve parameter validation and notifications. The changes simplify resource deployment, clarify region requirements, and enhance validation feedback.

Key changes include:

Infrastructure and Deployment Updates:

• Removed the separate Content Understanding (CU) resource and its parameters from infra/main.bicep, deployment scripts, and outputs, consolidating all AI Foundry and CU functionality into a single resource and endpoint. This simplifies deployments and eliminates the need for the contentUnderstandingLocation parameter. [1] [2] [3] [4] [5]
• Expanded and updated the list of supported regions for deployments and quota checks, both in Bicep parameters and documentation. Removed francecentral and added regions such as southcentralus and westeurope. [1] [2] [3]

Parameter Validation and Notification Enhancements:

• Improved the Bicep parameter validation workflow to generate an HTML report (email_body.html) and use it in email notifications, providing more detailed and user-friendly feedback on validation results. [1] [2] [3]

Documentation Improvements:

• Updated deployment and customization guides to remove references to the separate CU Foundry resource, clarify required parameters, and document the new region requirements for reusing an existing Foundry project. [1] [2] [3] [4] [5] [6]
• Corrected and clarified instructions for app registration and parameter usage. [1] [2]

Configuration File Updates:

• Renamed and updated analyzer configuration files to use new base analyzers and removed obsolete fields, aligning with the updated resource structure. [1] [2]

These changes collectively simplify deployment, improve clarity for users, and ensure compatibility with supported Azure regions.

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]

Coverage Report •

File	Stmts	Miss	Cover	Missing
src/api/api
history_routes.py	256	39	84%	42, 159, 163, 241–243, 248–252, 268, 272, 400, 404, 407, 410, 430, 433–436, 441–445, 462, 466, 477, 481, 495–497, 503–507
TOTAL	1310	151	88%

Tests	Skipped	Failures	Errors	Time
163	0 💤	0 ❌	0 🔥	5.930s ⏱️

[Copilot]

Pull request overview

Improves robustness of the /history/delete_all endpoint by retrying conversation listing once to mitigate transient Cosmos DB connection issues after idle periods, and by ensuring FastAPI HTTPExceptions aren’t masked as generic 500s. Also updates a documentation step for clarity in app registration setup.

Changes:

• Added a one-time retry when listing conversations prior to deleting all conversations.
• Re-raised HTTPException in delete_all_conversations so the correct HTTP status codes are returned.
• Updated an app registration instruction from “Add a platform” to “Add redirect URI”.

Reviewed changes

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

File	Description
src/api/api/history_routes.py	Adds retry logic around get_conversations for delete-all and avoids masking HTTPException as 500.
documents/create_new_app_registration.md	Clarifies the UI step for adding a redirect URI.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 28 out of 32 changed files in this pull request and generated 5 comments.

Comments suppressed due to low confidence (1)

infra/scripts/index_scripts/content_understanding_client.py:281

• get_file_from_analyze_operation still asserts Content-Type == 'image/jpeg' even though it now retrieves an arbitrary file from /files/{file_path}. This assertion can fail for non-JPEG outputs (or for headers like image/jpeg; charset=...) and crash consumers; consider removing the assertion or validating against the expected MIME type for the specific requested file.

            response = requests.get(url=file_retrieval_url, headers=self._headers)
            response.raise_for_status()

            assert response.headers.get("Content-Type") == "image/jpeg"

            return response.content

[github-actions]

🎉 This PR is included in version 3.22.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀