Verifying the rollout
What to expect on the device and in the console, and what to do when it differs.
Verifying the rollout
Walk through the whole chain on the test device, signed in with the work account of a test user without admin rights. The per-step checks above remain the place to zoom in.
Sync the device
As in step 1: Settings → Accounts → Access work or school → the connected work account → Info → Sync. Or restart the device.
Check the policy
chrome://policy or edge://policy: the BeeSensible line is under ExtensionInstallForcelist, and the BeeSensible section shows configVersion 1 and loginHint with the work address, both with source Platform and status OK.
Check the extension
The BeeSensible extension is in the browser and cannot be removed. Check on chrome://extensions or edge://extensions that the version is at least the one from Automatic Microsoft sign-in.
Check the sign-in
Open a site where BeeSensible works. Expected: the extension recognises the work account and starts the sign-in by itself, without typing an address and without an account picker. In Chrome this is silent once CloudAPAuthEnabled is on the device; in Edge a Microsoft window can appear. Note whatever still appears, for example two-factor authentication.
Check the console
The test member appears on the deployment console under Observed usage; on the members page the sign-in shows as Managed.
Check a second user
Sign in a second standard user on the same device and check that they have their own sign-in hint and see nothing of the first user.
Check the desktop app
After the next Windows sign-in, the BeeSensible icon is in the system tray and the app is signed in with the work account, or asks for it once.
Check private windows
Only if you set that measure: open an InPrivate or Incognito window and check the behaviour from Private windows.
Troubleshooting
The detailed blocks sit with the step where the problem arises; this is the signpost.
Nothing arrives on the device
Force the sync as in step 1 and keep in mind that scripts and configuration profiles each have their own rhythm: the extension being present says nothing about the script.
The sign-in script does nothing
See the blocks at step 1: Entra joined, work account sign-in, loaded profile, verified domain, and the logs on the device.
The sign-in is not silent in Chrome
See Silent sign-in in Chrome under Optional hardening.
The extension version lags behind
Extension updates flow through the browser store and cannot be pinned; see the callout Updates flow through the store at step 2 and the Edge block at Automatic Microsoft sign-in.
The desktop app shows Pending or Failed
See the blocks at the Verify step under Deploying the desktop app.
