[Bug] Managed Identity - Update logs or docs to clarify MI correlation ID is different than MSALs

[gladjohn]

Which version of MSAL.NET are you using?
4.49.1

Platform
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?
Dev App

Repro

using Microsoft.Identity.Client;

IConfidentialClientApplication cca = ConfidentialClientApplicationBuilder.Create("00bedee1-0e09-4a8d-81a0-0679c5a64a83")
                .WithExperimentalFeatures()
                .WithDebugLoggingCallback(logLevel: LogLevel.Verbose, enablePiiLogging: true, withDefaultPlatformLoggingEnabled: true)
                .Build();

string? scope = "https://management.azure.com";

do
{
    Console.WriteLine($"Acquiring token with scope {scope}");
    try
    {
        var result = await cca.AcquireTokenForClient(new string[] { scope })
            .WithManagedIdentity().ExecuteAsync().ConfigureAwait(false);

        Console.WriteLine("Success");
        Console.ReadLine();
    }
    catch (MsalServiceException e)
    {
        Console.WriteLine(e.ErrorCode);
        Console.WriteLine(e.Message);
        Console.WriteLine(e.StackTrace);
        Console.ReadLine();
    }

    Console.WriteLine("Enter the scope to acquire token, 'q' to quit.");
    scope = Console.ReadLine();
} while (scope?.Equals("q", StringComparison.InvariantCultureIgnoreCase) is false);

Expected behavior
With logging enabled and if MSI endpoint errors out then the correlation ID is different than the one MSAL uses. Need clarity in the logs or updated MSAL docs for this behavior

Additional context / logs / screenshots / links to code
Came as part of MSI Presentation the team did