SSO not working for end-users first time after pre-provisioning 24h2

Jonas Hosni 0 Reputation points
2024-11-29T10:49:44.3866667+00:00

After pre-provisioning a user registers for Windows Hello For Business. However when trying to access Teams, Edge, OneDrive for the first time, the users are prompted for username and password for every single app. This is a broken SSO experience.

Have anyone else experienced this and how did you resolve it?

dsregcmd.exe /status:

AzureAdPrt: YES

Windows for business | Windows Client for IT Pros | User experience | Other
{count} votes

1 answer

Sort by: Most helpful
  1. Zafer KAYA 335 Reputation points MVP
    2025-10-08T10:25:17.6033333+00:00

    Fix: Force Full Sign-In Cycle Post-Provisioning

    1. 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.
    1. Clear Web Account Manager (WAM) Cache

    Sometimes stale WAM tokens block SSO:

    cmdkey /list

    cmdkey /delete:<AzureAD resource>

    Then restart the device.

    1. 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.

    1. 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.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.