Skip to content

Conversation

@Robbie-Microsoft
Copy link
Contributor

Fixes #5350

If the Machine Learning System Assigned Managed Identity is being used, the "clientid" request parameter will be set to the DEFAULT_IDENTITY_CLIENT_ID environment variable instead of being omitted in the network request.

@Robbie-Microsoft Robbie-Microsoft requested a review from a team as a code owner June 18, 2025 11:48
@gladjohn
Copy link
Contributor

looks good @Robbie-Microsoft, but there are few MI test failures, are they related?

Copy link
Member

@bgavrilMS bgavrilMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not make breaking changes to AppService2017, instead just add support for this Default_Client_id stuff

@gladjohn
Copy link
Contributor

Do not make breaking changes to AppService2017, instead just add support for this Default_Client_id stuff

a well explained bug on the changes we are making will be a good place to start with. The reason why I ask this is, It is not clear if Azure ML Source and Azure ML API source are same or are they different?

My understanding, is Azure ML uses App Service 2017. Does Azure ML API also use App Service 2017?

@chlowell
Copy link

My understanding, is Azure ML uses App Service 2017. Does Azure ML API also use App Service 2017?

Azure ML and App Service have always had different managed identity implementations. Azure ML imitated App Service 2017 when designing their managed identity API, however the implementations never behaved the same and Azure ML's API is now incompatible with App Service 2017 in that it requires clientid for all token requests.

@Robbie-Microsoft Robbie-Microsoft merged commit 2a23172 into main Jul 1, 2025
10 checks passed
@Robbie-Microsoft Robbie-Microsoft deleted the ml_updates branch July 1, 2025 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Support for new Azure ML Managed Identity

6 participants