fix: add OAuth, audience, connectorName fields and full authType enum to ConnectionConfig#51
Merged
trangevi merged 2 commits intoApr 13, 2026
Conversation
Add missing fields to the Bicep ConnectionConfig type so that all connection properties defined in azure.yaml are passed through to the ARM API without being silently dropped: - authorizationUrl / tokenUrl / refreshUrl / scopes (OAuth2 flows) - audience (UserEntraToken / AgenticIdentity auth types) - connectorName (managed OAuth connectors) Also extend the authType union to include all values the REST API accepts: UserEntraToken, AgenticIdentity, ManagedIdentity, ServicePrincipal, UsernamePassword, AccessKey, AccountKey, SAS.
therealjohn
reviewed
Apr 13, 2026
therealjohn
left a comment
therealjohn
left a comment
Contributor
There was a problem hiding this comment.
Looks good, thanks
nit: avoid whitespace issues to make the diff cleaner
trangevi
approved these changes
Apr 13, 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
3 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.
Problem
The
ConnectionConfigBicep type is missing several fields that the Azure AI Projects REST API accepts. When users specify these fields in theirazure.yaml, theazdextension reads them into Go structs, then passes them to Bicep as parameters — but because the Bicep type doesn't declare them, the values are silently dropped and never reach the ARM deployment.The affected fields are:
authorizationUrltokenUrlrefreshUrlscopesaudienceconnectorNameAdditionally, the
authTypeunion was missing several values the REST API accepts:UserEntraToken,AgenticIdentity,ManagedIdentity,ServicePrincipal,UsernamePassword,AccessKey,AccountKey,SAS.Changes
ConnectionConfigtype with 6 optional fields:authorizationUrl?,tokenUrl?,refreshUrl?,scopes?,audience?,connectorName?authTypeunion to cover all known auth type valuesconnectionresourcepropertiesblock so that each new field is forwarded to ARM when providedTesting
Verified against the
Azure AI ProjectsREST API (2025-04-01-preview) — all new fields map to documented connection properties.