Repository navigation
Add automatic Foundry routing and Microsoft MAI support - #1892
Merged
Paul Lizer (paullizer) merged 2 commits intoNov 5, 2026
Merged
Paul Lizer (paullizer) merged 2 commits into
Paul Lizer (paullizer) merged 2 commits into
Conversation
Route native Foundry models through their supported inference APIs while preserving discovery endpoints and Custom gateway contracts. Preconfigure canonical model identity from built-in selections, add MAI request and authentication compatibility, and cover mixed-model clients and metadata consumers. Co-authored-by: Copilot App <[email protected]>
Integrate the latest base document-index, Excel inspection and conversation-menu changes while retaining automatic Foundry model routing. Combine release notes and tabular test metadata, and align the pending feature release at 0.261.410. Co-authored-by: Copilot App <[email protected]>
Paul Lizer (paullizer)
merged commit Nov 5, 2026
268bfa8
into
paullizer-react-v2-ui
11 of 12 checks passed
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.
Summary
Linked issue
N/A. The user opted to continue without an associated issue.
Release Notes & Latest Features
Is this visible to end users?
Is this admin-facing (Admin Settings, governance, deployment, config)?
Should this become a Latest Feature card?
Screenshot needed for the card?
Version bump
application/single_app/config.pyVERSIONthird segment bumped, or not needed because this is docs-onlydeployers/version.txtbumped, or not needed becausedeployers/was not changedApplication: latest base 0.261.409 -> 0.261.410. The initial feature draft was 0.261.407; the pending release and its documentation/test headers are now aligned with the latest base. No deployer files changed.
Testing / validation
b0a358646: 268 tests and 755 subtests. The following targeted suites include real SDK request construction, mixed-model native connections, streaming/tool continuation, normal and optimized Python, capture/workflow metadata, and tabular budgets. All inference HTTP is mocked; no production deployment or paid inference was performed.python -m pytest -q --disable-warnings .\functional_tests\test_tabular_model_token_budgets.py .\functional_tests\test_excel_native_inspection_chat_evidence.py .\functional_tests\test_tabular_table_aware_analytics_replay.py- passed, 63 tests, covering the overlapping base Excel/table-aware changes and model budgets.node .\functional_tests\test_v2_model_connections_logic.mjs- passed, 43 checks.python -m pytest -q --disable-warnings .\functional_tests\test_v2_model_catalog_workbench.py- passed, 3 tests, including 12 bundled TypeScript checks. The browser-origin fixture was completed for the existing API client.npm --prefix .\application\v2_ui run typecheck -- --pretty false- passed.npm --prefix .\application\v2_ui run build- passed; existing large-bundle warning remains.python .\functional_tests\route_tests\test_route_blueprint_policy_inventory.py- passed, 15 checks.python .\functional_tests\route_tests\test_route_unauthenticated_policy_contract.py- passed, 10 checks.python .\functional_tests\route_tests\test_route_policy_test_coverage.py- passed, 3 checks.python .\scripts\build_docs_inventory.py- passed before the base merge, regenerated inventory had no content changes.python .\functional_tests\test_docs_app_surface_coverage.py- passed after the base merge, 7 checks.python .\functional_tests\test_docs_site_quality.py- passed after the base merge, 6 checks.python -m pytest --collect-only -q .\ui_tests\test_microsoft_mai_ai_connections.py- 4 tests collected before the base merge. Browser execution was intentionally not performed; desktop/mobile native saves, automatic matching/presets, and Custom alias preservation are covered by the authored fixtures.python .\scripts\check_xss_sinks.py --full-file .\application\v2_ui\src\components\admin\ModelConnectionsManager.tsx .\application\v2_ui\src\components\admin\ModelCatalogManager.tsx .\application\v2_ui\src\lib\modelConnections.ts .\application\v2_ui\src\lib\customModelConnections.ts .\application\v2_ui\src\lib\modelInference.ts .\application\v2_ui\src\lib\modelCatalog.ts- passed before the base merge, 6 files; those feature implementations were unchanged by conflict resolution.git diff --checkandgit diff --cached --check- passed.Historical baseline limitations: Before the latest-base integration, additional legacy reasoning/staging fixtures had 42 failures from missing extracted AST dependencies (
apply_model_profile,should_include_current_turn_images) and an outdated staging callback. The same failures were reproduced against pre-feature commit98e01345f. The base update repairs the staging fixture, and all current tabular model-budget tests now pass in the 63-test overlap suite above. Older unrelated reasoning/Custom/image/embedding fixtures are not represented as passing checks or independently repaired here.Live model access, RBAC, regional availability, quotas, and gateway readiness remain deployment-specific checks. Custom connections do not acquire the application's managed-identity token automatically, and the optional encrypted MAI reasoning envelope is not requested.
Documentation
Updated the AI Connections guide, AI Models and Model Catalog references, release notes, and
docs/explanation/fixes/MICROSOFT_MAI_MODEL_CONNECTIONS_FIX.mdwith the automatic native flow and explicit gateway boundary. Conflict resolution preserves the base Excel release entries and both sets of tabular test metadata.Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()No routes or frontend settings-exposure boundaries were added by this feature. Existing authentication/authorization policies are verified by the route-policy checks.