Hi, this happens when Chrome is not actually using the Windows Accounts extension / WAM for those users, even though the device has a valid PRT. In that case Chrome falls back to a plain browser flow, so Entra logs show Client app = Browser with no device information, while a separate broker sign-in appears for the PRT.
The fix is to force Chrome back onto the WAM path for those profiles. For the affected users, check that they are using a managed Chrome profile (not a local or guest profile), that the Windows Accounts extension is installed and enabled, and that they are signed into Chrome with their work account. Clearing Chrome’s profile data or creating a fresh Chrome profile often fixes it. Also verify that no user-level Chrome policies are disabling the extension or WAM integration for just those accounts. Once Chrome uses WAM again, the browser sign-in will include device info as expected.