You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Machine Learning source is based off of App Service 2017 (MSALs do not support this App Service 2017 version, only 2019). In the 2017 API, the client id should be passed to the network request as "clientid" instead of "client_id".
This bug was identified recently after Azure-SDK-for-JS removed their App Service 2017 implementation in favor of MSALJS's (msal-node) Machine Learning implementation. An Azure-SDK-for-JS customer is seeing network errors due to the incorrect way client id is being passed to the network request.
Relevant code snippets
Expected behavior
No response
Identity provider
Other
Regression
No response
Solution and workarounds
No response
The text was updated successfully, but these errors were encountered:
Avery-Dunn
added
Bug
Something isn't working, needs an investigation and a fix
P2
Normal priority items, should be done after P1
and removed
needs attention
Automatically used when an issue is created through an issue template
untriaged
Automatically used when an issue is created through an issue template
labels
Mar 11, 2025
Library version used
latest
Java version
latest
Scenario
ManagedIdentityClient - managed identity
Is this a new or an existing app?
None
Issue description and reproduction steps
The Machine Learning source is based off of App Service 2017 (MSALs do not support this App Service 2017 version, only 2019). In the 2017 API, the client id should be passed to the network request as "clientid" instead of "client_id".
This bug was identified recently after Azure-SDK-for-JS removed their App Service 2017 implementation in favor of MSALJS's (msal-node) Machine Learning implementation. An Azure-SDK-for-JS customer is seeing network errors due to the incorrect way client id is being passed to the network request.
Relevant code snippets
Expected behavior
No response
Identity provider
Other
Regression
No response
Solution and workarounds
No response
The text was updated successfully, but these errors were encountered: