feat: Update scenario-based agent setup and model references to GPT-5.1#993
Draft
Avijit-Microsoft wants to merge 379 commits into
Draft
feat: Update scenario-based agent setup and model references to GPT-5.1#993Avijit-Microsoft wants to merge 379 commits into
Avijit-Microsoft wants to merge 379 commits into
Conversation
Move CitationPanel outside the flex layout container (.main-container) and render it as a fixed-position overlay. This prevents the two panels from competing for flex space, which caused: - Closing Chat History to also close Citation panel - Opening Citation to push Chat History off-screen Fixes AB#43310 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
fix: Added data collection rules for VM, added double encryption for storage account and added e2eEncryption in app service
Address review feedback: CitationPanel is now a flex participant inside .main-container using .citation-panel-wrapper (flex: 0 0 20%) instead of a fixed-position overlay. This reserves layout space and avoids blocking clicks on underlying panels. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…istory Citation panel is now a fixed overlay that dynamically offsets its position when Chat History is open, preventing click-blocking while maintaining full panel independence. - Overlay shifts left by Chat History width when both panels are open - Panels remain fully independent (opening/closing one never affects the other) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The simple overlay approach is the cleanest solution - Citation floats independently without any coupling to the flex layout. Tested and verified that all 4 panels (Dashboard, Chat, Citation, Chat History) work correctly side by side. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Extract --header-height CSS custom property to avoid 6vh duplication - Add pointer-events: none on overlay container to prevent dead zones - Use <section> with aria-label for citation overlay accessibility Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
generate_title uses get_azure_credential_async; the stale patch on the removed get_azure_credential symbol broke after the F401 cleanup. Aligns with the sibling test_generate_title_success patch target. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ential Addresses Copilot review feedback on PR #915 (merged into dev). The two helpers get_azure_credential_async (async fn) and get_async_azure_credential (sync fn) differ only by word order, which is easy to confuse at call sites. Renaming the sync builder to build_async_azure_credential makes the sync-vs-async distinction explicit: build_ implies sync construction, async describes the returned credential type. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Use flex-based citation-panel-wrapper for consistent height alignment - Add box-sizing: border-box to include padding/border in height calc - Prevent horizontal overflow on main-container Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Citation should close when Chat panel is hidden since citations originate from chat responses. ChatHistory toggle remains independent. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ential (address Copilot review on #915)
Agent-Logs-Url: https://github.com/microsoft/Conversation-Knowledge-Mining-Solution-Accelerator/sessions/ded6036c-43b4-462c-b7a0-f8c5483b6a1f Co-authored-by: Dhanushree-Microsoft <250931221+Dhanushree-Microsoft@users.noreply.github.com>
chore: dev to main merge
…edge-Mining-Solution-Accelerator into km-gen-depdh # Conflicts: # src/App/package-lock.json
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
refactor: Updated Foundry Roles name
…d by enrich_byod_data.py, which imports src.api.* modules (config,processing.service, ingestion.external_index) directly.
chore: Enhance UI integration with seeded scenarios and update dependencies
…ns based on scenarios
chore: Update Deployment Guide and enhance role assignment logic
…c in Deployment documentation
…in Deployment Guide
…exists during data setup
chore: Enhance deployment documentation and scripts for Azure AI Search
fix: update Dockerfiles to improve installation and build processes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request introduces several important updates to support Azure OpenAI GPT-5.1 as the default language model, improve scenario-based agent configuration, and enhance Azure role assignments for AI Foundry integration. The changes also streamline environment setup and add dynamic tool selection for agents based on scenario data types.
Model Upgrade and Documentation Updates:
Agent Creation and Scenario Configuration:
scripts/create_agent.py) now loads scenario-specific prompts and tool configurations, regenerating the agent prompt for the selected scenario and dynamically enabling SQL analytics tools for structured data scenarios. [1] [2] [3]scenarios.json, enabling SQL analytics only for relevant scenarios (e.g., JSON, CSV, WAV) and defaulting to search-only otherwise. [1] [2]Infrastructure and Role Assignment Enhancements:
Environment Setup Improvements:
.venv(fromvenv) in both PowerShell and Bash setup scripts, and the agent setup step is removed from the default deployment flow for clarity. [1] [2]File Path Consistency:
data/configinstead ofSample_Data/configfor consistency.These changes collectively modernize the platform to use the latest Azure OpenAI model, make agent capabilities scenario-aware, and improve deployment reliability and maintainability.
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information