[Bug] TenantId Not Overridden in AcquireTokenInteractive When Using Public Client with WithTenantId

[narendran-dev]

Library version used

4.69.1.0

.NET version

.NET 8.0.8

Scenario

PublicClient - desktop app

Is this a new or an existing app?

The app is in production, I haven't upgraded MSAL, but started seeing this issue

Issue description and reproduction steps

When using the AcquireTokenInteractive method in MSAL.NET and passing the TenantId (either organisation or consumers), the expected behavior of overriding the tenant ID does not occur. The authentication flow defaults to the common tenant, even when a specific TenantId is passed during the interactive token acquisition.

Relevant code snippets

this._msalClient =  PublicClientApplicationBuilder .Create(authEndPointSetting.CommonEndPointClientId)
                                    .WithDefaultRedirectUri()
                                    .WithLegacyCacheCompatibility(false)
                                    .WithHttpClientFactory(new MsalHttpFactory())
                                    .Build();



            var authRequest = __msalClient.AcquireTokenInteractive(scopes)
                .WithLoginHint(userName)
                .WithUseEmbeddedWebView(isEmbeddedWebView)
                .WithTenantId(tenantId.ConvertToLoginTenantType());// based on the user’s email we will pass consumer or organisation or common.

Expected behavior

No response

Identity provider

Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)

Regression

No response

Solution and workarounds

No response

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• [Bug] [M] WithTenant ignored, resulting in CA failures for multi-tenant apps #2543

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Use a tenanted authority instead, i.e. https://login.microsoftonline.com/{tenantId}

Reference:

• [Bug] [M] WithTenant ignored, resulting in CA failures for multi-tenant apps #2543 (comment)

Powered by issue-sentinel