Skip to content

feat: Add Multi-Industry Use Case Support (Contact Center & IT Helpdesk) with Deployment Improvements#699

Merged
Avijit-Microsoft merged 50 commits intomainfrom
dev
Dec 18, 2025
Merged

feat: Add Multi-Industry Use Case Support (Contact Center & IT Helpdesk) with Deployment Improvements#699
Avijit-Microsoft merged 50 commits intomainfrom
dev

Conversation

@Pavan-Microsoft
Copy link
Contributor

Purpose

This pull request introduces several updates to support multiple industry use cases (Contact Center and IT Helpdesk), enhances deployment flexibility, and improves documentation and setup scripts. The most significant changes are the addition of a configurable use case parameter, updates to deployment and customization instructions, and improvements to local development and devcontainer environments.

Support for Multiple Use Cases:

  • Added a usecase parameter to the infrastructure (infra/main.bicep) to allow selection between "telecom" (Contact Center) and "IT_helpdesk" use cases during deployment. This enables tailored resource provisioning and configuration for different scenarios. [1] [2]
  • Updated documentation (DeploymentGuide.md, SampleQuestions.md, README.md) to describe and provide sample prompts for both Contact Center and IT Helpdesk scenarios, including a new use case table and example questions for each. [1] [2] [3] [4]

Deployment and Setup Improvements:

  • Enhanced deployment instructions to include explicit steps for selecting the use case, running data processing scripts, and handling parameterized script execution for both sample and custom data. [1] [2] [3]
  • Updated script permissions and renamed scripts to make the process for loading sample and custom data clearer (process_sample_data.sh, process_custom_data.sh).

Devcontainer and Local Development Enhancements:

  • Added installation of Microsoft ODBC Driver 18 for SQL Server in both documentation and devcontainer configuration, ensuring compatibility and reducing setup friction for developers. [1] [2] [3]

Resource and Parameter Cleanup:

  • Removed unused or redundant parameters and DNS zone entries from the Bicep infrastructure code, simplifying resource management. [1] [2] [3]
  • Added a new optional parameter for the Content Understanding API version to support future flexibility.

Documentation Updates:

  • Improved clarity and accuracy of service names and links in deployment guides.

These changes collectively make the solution more adaptable to different business scenarios, streamline the deployment and customization process, and improve the developer experience.

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.

- Introduced `04_cu_process_custom_data.py` for processing custom data and integrating with Azure services.
- Removed obsolete `azure_credential_utils.py` as its functionality is now integrated elsewhere.
- Updated `content_understanding_client.py` to improve error handling.
- Created `process_custom_data_scripts.sh` for streamlined script execution and dependency management.
- Enhanced `process_data_scripts.sh` to include additional parameters and improved error handling.
- Refactored `run_create_index_scripts.sh` to support Azure authentication and role assignment.
- Deleted `run_create_index_scripts_manual.sh` as its functionality is now covered in the updated script.
- Adjusted `run_process_data_scripts.sh` to reference the new Bicep file for custom data processing.
…ole assignments, and error handling; remove run_process_data_scripts.sh
…mands in Azure YAML and update SQL output directory path in Python script
…rove error handling in bash script for enabling public access
…lt dependencies and streamline parameter handling

- Removed Key Vault related parameters and configurations from Bicep templates.
- Updated Python scripts to accept command line arguments for necessary endpoints and models instead of retrieving them from Key Vault.
- Modified shell scripts to pass new parameters to Python scripts for improved flexibility and clarity.
- Cleaned up unused variables and consolidated logic for better maintainability.
…essing data

- Introduced a new script `process_custom_data.sh` to manage public network access for Azure resources and execute data processing.
- Implemented functions to enable and restore public access for Storage Account, AI Foundry, CU Foundry, and SQL Server.
- Added error handling and logging for network access changes.
- Refactored existing `process_sample_data.sh` to remove deployment output retrieval logic, now handled in `process_custom_data.sh`.
- Removed SQL table creation logic from `run_create_index_scripts.sh` to streamline the process.
…Azure services and Content Understanding API
…SSQL ODBC driver and correct script permissions
… improve SQL Server public access feedback in scripts
…rivate endpoint management and remove secrets export configuration
Pavan-Microsoft and others added 17 commits December 15, 2025 16:16
…ndant code and streamline role assignments in Azure CLI scripts
…undant code and streamline role assignments in Azure CLI scripts
@Avijit-Microsoft Avijit-Microsoft merged commit bf7caa5 into main Dec 18, 2025
9 checks passed
@github-actions
Copy link
Contributor

🎉 This PR is included in version 3.17.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants