Repository navigation
[Bug] HttpClientTransport setting is not applied after MSAL upgraded #6124
Description
Library version used
4.85.2
.NET version
4.7.2
Scenario
ManagedIdentityClient - managed identity
Is this a new or an existing app?
The app is in production, and I have upgraded to a new version of MSAL
Issue description and reproduction steps
After we upgraded version from 4.84.2 t0 4.85.2, we notice the same issue as
#5286 (comment) happened again.
The regression is most likely caused by changes from 4.85.0.
Relevant code snippets
Expected behavior
No response
Identity provider
Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)
Regression
No response
Solution and workarounds
No response
Activity
bgavrilMS commentedon Jul 21, 2026
Gladwin Johnson VR (@gladjohn) - can you pls take a look
gladjohn commentedon Aug 7, 2026
xula2018 apologies for the delay on this one
Thanks for the report. I ran a real repro on 4.85.2: a normal IMDS managed-identity acquisition with a custom  HttpClientTransport (plain IMsalHttpClientFactory ) correctly routes every request through the caller's transport â so I can't reproduce a transport bypass on the IMDS path in 4.85.2. To pin this down, could you confirm:
Note: the one place MSAL still builds its own  HttpClient (bypassing a plain custom transport) is Service Fabric, to attach its server-cert validation callback â but that's been the case since 4.62.0 (#4818), so it wouldn't be a 4.84.2â4.85.2 regression. If you're on Service Fabric, the supported path is to supply an IMsalSFHttpClientFactory .