[Bug] MSAL Logs are not clear when regional is enabled and tokens are acquired from the cache

[trwalke]

When performing AcquireTokenForClient() and the region is configured, if MSAL has no tokens in the cache, MSAL will properly log the following message when acquiring the token from the identity provider:

"Fetched access token from host region.r.login.microsoftonline.com. Endpoint https://eastus.r.login.microsoftonline.com/Some Id/"

if MSAL already has a token in the cache, MSAL will log the following when returning the token from the cache:

"Fetched access token from host login.microsoftonline.com. Endpoint https://login.microsoftonline.com/Some Id/"

This can be very confusing for customers who expect all token acquisition traffic to go to the regional endpoint.

Which version of MSAL.NET are you using?
MSAL.NET 4.39.0

Platform
.NET FWK, .NET Core,

What authentication flow has the issue?

• Desktop / Mobile
  • Interactive
  • Integrated Windows Authentication
  • Username Password
  • Device code flow (browserless)
• Web app
  • Authorization code
  • On-Behalf-Of
• Daemon app
  • Service to Service calls

Other?

Is this a new or existing app?

Repro

            IConfidentialClientApplication app = ConfidentialClientApplicationBuilder.Create(clientId)
                .WithAzureRegion("SomeRegion")
                .WithCertificate(Cert)
                .Build();

            app.AcquireTokenForClient(scopes).ExecuteAsync(); //Logs are correct
            app.AcquireTokenForClient(scopes).ExecuteAsync(); //Logs are misleading

Expected behavior
It should be clear that MSAL is acquiring the token from the cache and not from the global endpoint

Actual behavior
"Fetched access token from host login.microsoftonline.com. Endpoint https://login.microsoftonline.com/Some Id/"

Additional context / logs / screenshots / links to code
Relevant migration conversation: Conversation

[bgavrilMS]

For issues that are known to be bugs please tag as "Bug" and assign a priority.

P0 = high impact, many users affected (e.g. a common scenario is blocked)
P1 = low impact x many users OR high impact x few users (e.g. a scenario is blocked but it is not very common)
P2 = P1 but workaround exists, supportability issues etc.
P3 = nice to have

[pmaytak]

For issues that are known to be bugs please tag as "Bug" and assign a priority.

P0 = high impact, many users affected (e.g. a common scenario is blocked)
P1 = low impact x many users OR high impact x few users (e.g. a scenario is blocked but it is not very common)
P2 = P1 but workaround exists, supportability issues etc.
P3 = nice to have

@bgavrilMS This is good. Added to our OneNote.

[SameerK-MSFT]

Fixed in MSAL 4.40.0