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
MsalSilentTokenProvider always receives the non-broker IPublicClientApplication, so it can never acquire tokens
silently from the WAM broker cache. This means every invocation requires interactive authentication when the broker is enabled and ARTIFACTS_CREDENTIALPROVIDER_RETURN_ENTRA_TOKENS is set (session cache not used).
In MsalTokenProvidersFactory.cs, two separate IPublicClientApplication instances are created:
app - without broker
appInteractiveBroker - with broker
In MsalTokenProviders.cs, the silent provider receives app:
yield return new MsalSilentTokenProvider(app, logger); // non-broker
yield return new MsalBrokerInteractiveTokenProvider(appInteractiveBroker, logger); // broker
Because app has IsBrokerEnabled = false, the #if INCLUDE_BROKER block in MsalSilentTokenProvider that adds
OperatingSystemAccount never activates, and GetAccountsAsync() never queries WAM. The MSAL file cache is also empty because broker interactive auth stores tokens in WAM's cache, not the file cache.
closing - released and switched to latest please reopen if you run into any further issues. We will have a follow up version to address the WSL issue addressed in 676
Activity
Fix silent WAM broker token acquisition (#664) (#666)
Fix silent auth failure in WSL caused by broker token provider (#675)
CP -> releases/2.0.2 Fix silent auth failure in WSL caused by broker β¦
embetten commentedon May 7, 2026
This fix was published as pre-release https://github.com/microsoft/artifacts-credprovider/releases/tag/v2.0.2 please try it out and let me know if this resolves the issue!
embetten commentedon May 12, 2026
closing - released and switched to latest please reopen if you run into any further issues. We will have a follow up version to address the WSL issue addressed in 676