MSAL Authentication Issue After Upgrading to 10.0.8 (Blazor WebAssembly

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

I’m currently facing an issue with MSAL authentication in a Blazor WebAssembly application after upgrading the packages from 10.0.7 to 10.0.8.
Everything was working correctly in 10.0.7 with the same configuration. However, after the upgrade:

User.Identity.IsAuthenticated is always returning false
RemoteUserAccount is coming through as null
The application does not recognize the user as authenticated

No configuration changes were made during the upgrade, which makes this behavior particularly confusing.
Has anyone encountered a similar issue or identified any changes in authentication behavior between these versions that could explain this?

---

Original Comments

Feedback Bot on 5/28/2026, 09:08 PM:

Based on similar issues resolved with Microsoft in the last 6 months, the following can help resolve this issue faster.

If not already included, please provide:

Detected: OS: not provided, VS: not provided, Project type: Blazor WebAssembly

Please share:

• The exact Visual Studio version/build and .NET/SDK version used before and after the change from 10.0.7 to 10.0.8.
• Whether this happens in a new, minimal Blazor WebAssembly app or only in the existing project.
• The exact authentication setup/configuration used for MSAL, plus any changes made during the 10.0.8 upgrade.
• The step-by-step repro flow and where IsAuthenticated becomes false / RemoteUserAccount is null.
• Any relevant browser console errors or app output logs from the failing run.

Muthukumar S on 5/28/2026, 09:13 PM:

(private comment, text removed)

Feedback Bot on 5/29/2026, 03:40 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

[muthustarr]

The exact Visual Studio version/build and .NET/SDK version used before and after the change from 10.0.7 to 10.0.8.
Visual Studio 2026 and the SDK version is 10.0.300 even before and after upgrading

Whether this happens in a new, minimal Blazor WebAssembly app or only in the existing project.
Existing project

The exact authentication setup/configuration used for MSAL, plus any changes made during the 10.0.8 upgrade.
No other changes made during the upgrade

The step-by-step repro flow and where IsAuthenticated becomes false / RemoteUserAccount is null.
During login-callback call, RemoteUserAccount is always null after upgrading while entering into the CreateUserAsync method in ClaimFactory class

Any relevant browser console errors or app output logs from the failing run.
Logged only the need authentication and observed that AuthenticationService.Js was not invoked after upgrading

Console Message :
info : User is not authenticated. Skipping claims population.

info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[2]
Authorization failed. These requirements were not met:
DenyAnonymousAuthorizationRequirement: Requires an authenticated user.