Azure Regions and Regional Endpoints

To increase the reliability, availability and performance of Azure, multiple Azure regions are available that aim to keep all traffic for an application inside the same geographical area. See here for more information about Azure regions: https://azure.microsoft.com/en-ca/global-infrastructure/geographies/#geographies

In order to make use of regional endpoints, MSAL Java allows developers to either set the region that the library should try to use for its token calls, or if the application is running on an Azure product (such as an Azure VM or Azure Functions) the library could attempt to detect the region automatically. If for some reason the region can't be detected or used during some call, then the library will fallback to using the global endpoint.

When building your client application object, you can either set the 'azureRegion' field to the short name for the region you want to use (such as ‘westus’) and the library will try to use that endpoint, or you can set the 'autoDetectRegion' field to true and the library will try to detect the region for you based on some metadata that can be found in different Azure environments.