-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Expose the region or error used by MSAL #2975
Comments
@bgavrilMS can this be prioritized for upcoming release? |
We were thinking to wrap up msal 4.38 and not start new work. Note that MSAL exposes |
I think having the entire token endpoint is not straightforward for people who don't know what they are looking for. If this is not needed, close the issue. Can you also remove the 4.38 milestone, if it won't be in that release? Thanks. |
@bgavrilMS The amount of work should be minimal, but the clarity to users should be beneficial. I propose we take this in the next release (maybe even do a quick small one). |
Ok |
I propose that we take this as we're getting more and more issues around auto-discovery. |
CC @gladjohn |
Part of AuthenticationResultMetadta, expose a
string RegionOrDiscoveryError
which is populated only ifWithAzureRegion
is used.If region auto-detection failed, this metric should describe the reason (over and over again!)
{
AuthenticationMetadata.RegionDiscoveryOutcome -> [RegionOutcome, Exception, RegionUsed]
}
The text was updated successfully, but these errors were encountered: