Skip to content

Commit

Permalink
Remove link to document that is internal/outdated.
Browse files Browse the repository at this point in the history
  • Loading branch information
localden committed Jul 5, 2023
1 parent 910ce17 commit 5447305
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ description: "To increase the reliability, availability and performance of appli

To increase the reliability, availability and performance of applications running in Azure, multiple Azure regions are available that aim to keep all traffic for the application inside the same geographical area. Relevant for MSAL are the regional endpoints for the secure token service, allowing an application using MSAL to retrieve tokens from a regional endpoint rather than the default global endpoint.

See [here](https://azure.microsoft.com/global-infrastructure/geographies/#geographies) for more information about specific Azure regions, and before trying to use a regional endpoint ensure that your authentication flow or scenario is supported by looking at the [regional token service FAQ](/identity/microsoft-identity-platform/ests-r-faq).
See [Azure geographies](https://azure.microsoft.com/global-infrastructure/geographies/#geographies) for more information about specific Azure regions.

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 accessed during a token request, then the library will fallback to using the global endpoint and continue to use the global endpoint when refreshing that token.

Expand Down

0 comments on commit 5447305

Please sign in to comment.