fix: Improve Deployment Docs, Single-Tenant Teams Extension, and Ingestion Error Handling

[Pavan-Microsoft]

Purpose

This pull request introduces several improvements and updates across deployment documentation, Teams extension configuration, and backend data ingestion error handling. The main themes are: enhanced deployment options and documentation, improved Teams extension setup for single-tenant scenarios, and better user experience for URL ingestion errors.

Deployment Documentation & Configuration Updates:

• Added a comprehensive section to docs/LOCAL_DEPLOYMENT.md detailing sandbox and Well-Architected Framework (WAF) aligned deployment options, including instructions for selecting and customizing deployment parameters for different environments.
• Expanded and reorganized the environment variables table in docs/LOCAL_DEPLOYMENT.md to cover all relevant configuration options, including new variables for advanced image processing, speech services, security, and orchestration.

Teams Extension Improvements:

• Changed Teams extension documentation to reference "Microsoft 365 Agents Toolkit" instead of "Teams Toolkit" and clarified environment variable setup instructions for the Azure Function URL. [1] [2]
• Updated the Teams extension code and infrastructure to support single-tenant authentication: added tenantId to config.ts, set MicrosoftAppType to "SingleTenant" in index.ts, and added tenant ID parameter and environment variable in the Bicep template. [1] [2] [3] [4]

Backend Data Ingestion Error Handling:

• Improved error handling in the data ingestion flow (code/backend/pages/01_Ingest_Data.py): now, if URL processing fails, error messages are shown to the user via st.error and the textarea is only cleared on success. Functions now return booleans to indicate success/failure. [1] [2] [3]

Workflow Reliability:

• Replaced the use of the cache-apt-pkgs-action with direct apt-get installation for required tools in the GitHub Actions workflow, ensuring more reliable and up-to-date package installation. (.github/workflows/group_dependabot_security_updates.yml)

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 deployment

[github-actions]

🎉 This PR is included in version 1.16.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀