Repository navigation
docs(decisions): add Databricks and Microsoft Foundry as decisions providers - #2241
Merged
kerrylu-berri merged 2 commits intoOct 10, 2026
Merged
Conversation
…oviders Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
Author
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
kerrylu-berri
enabled auto-merge (squash)
October 10, 2026 04:34
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
kerrylu-berri
deleted the
litellm_decisions_databricks_foundry_providers
branch
October 10, 2026 04:40
This branch was successfully deployed
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
1 participant
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
The Supported providers table on
docs/decisions.mdlisted seven providers whileProviderConfigManager.get_provider_decisions_configon litellm main dispatches nine. This adds the two missing rows, Databricks (DatabricksDecisionsConfig, BerriAI/litellm#45200) and Microsoft Foundry (AzureAIDecisionsConfig, BerriAI/litellm#45673), with the same columns as the other rows: example model, credential env vars, upstream path and image supportIt also spells out the two things a reader cannot guess from the table. On Databricks the model is the bare serving endpoint name and
DATABRICKS_API_BASEhas to point athttps://<workspace-host>/serving-endpoints. On Foundry the model is the deployment name, a project-scopedapi_baseis trimmed back to the resource host, and since Azure refusesMicrosoft-Decision-1as a deployment name the config example setsmodel_info.base_model: azure_ai/Microsoft-Decision-1so cost tracking resolves the price. The availability line notes that both landed on main afterv1.106.0-dev.3Before
https://docs.litellm.ai/docs/decisions#supported-providers as published today
After
npm run buildof this branch, served locally and opened at/docs/decisions/#supported-providersLink to Devin session: https://app.devin.ai/sessions/c046e935789f4045b72c925daca6d1bc
Open in Devin Desktop: https://app.devin.ai/desktop/session/c046e935789f4045b72c925daca6d1bc?variant=devin
Requested by: @kerry-berri
Note
Devin errored when opening this Pull Request as kerry-berri.
As a fallback, Devin opened this PR as itself.