Fix: Force Full Sign-In Cycle Post-Provisioning
- Have the user sign out and sign in again
- A full interactive sign-out and sign-in (not just lock/unlock) triggers proper token initialization.
- This restores SSO across apps.
- Clear Web Account Manager (WAM) Cache
Sometimes stale WAM tokens block SSO:
cmdkey /list
cmdkey /delete:<AzureAD resource>
Then restart the device.
- Verify WHfB and SSO Readiness
Check these in dsregcmd /status:
- AzureAdJoined: YES
- AzureAdPrt: YES
- SSO State: AzureADJoined + WHfB + PRT
If SSO State is missing WHfB or PRT, the sign-in cycle is incomplete.
- Optional: Disable WHfB during pre-provisioning
If this issue is widespread, consider disabling WHfB setup during pre-provisioning and letting users enroll post-login. This avoids token misalignment.