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
Currently we will only fallback to global when region detection fails and not when regional ests fail. For regional ests failures we are waiting on the ests-r team to provide us with the allow list of errors for which we need to fallback to global.
Add an api FallbackToGlobal in the confidential client WithAzureRegion(AutoDetectRegion: true, FallbackToGlobal: true)
Fallback logic in case we fail to detect the region -- first request decides this and then cache
Add to telemetry if we are falling back to global for the request
The text was updated successfully, but these errors were encountered:
In case MSAL fails to detect the region, fallback to global endpoint.
Please refer to the design doc for details.
Currently we will only fallback to global when region detection fails and not when regional ests fail. For regional ests failures we are waiting on the ests-r team to provide us with the allow list of errors for which we need to fallback to global.
The text was updated successfully, but these errors were encountered: