fix(provider): support custom Azure deployments#232
Closed
JohnYin-hub wants to merge 3 commits into
Closed
Conversation
Allow Azure OpenAI users to configure deployment names directly in the provider setup flow and cover the runtime/test-credentials path so custom deployments are usable. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep saved Azure deployment names visible when editing provider settings and separate catalog model counts from custom deployments. Co-authored-by: Cursor <cursoragent@cursor.com>
Avoid persisting Azure deployment names from connection tests, keep save feedback consistent, and tighten Azure-specific UI/test coverage. Co-authored-by: Cursor <cursoragent@cursor.com>
duguwanglong
approved these changes
May 8, 2026
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
2 participants
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.
Allow Azure OpenAI users to configure deployment names directly in the provider setup flow and cover the runtime/test-credentials path so custom deployments are usable.