What's new 
We have a Windows passcode policy in Hexnode that requires at least 8 characters with uppercase, lowercase, and a number. The affected users are signing in with local Windows accounts that are synced with Google Workspace using Google Credential Provider for Windows (GCPW). In most cases, changing the Google password to match the requirements fixes it, but on a few devices Hexnode still shows a password complexity conflict even though the password should be compliant. Has anyone seen this with GCPW or local accounts connected to a work account?
8 Views
Replies (1)
Marked SolutionPending Review
Hexnode Expert
1 hour ago
Jul 03, 2026
Marked SolutionPending Review
This can happen because Windows handles password complexity differently depending on the account type.
For Hexnode passcode complexity policies on Windows:
– Local accounts support all password complexity options.
– Microsoft accounts support only limited complexity options, such as digits only or digits and lowercase letters.
– Domain accounts are not supported for this type of password complexity enforcement.
With Google Credential Provider for Windows, the account may appear local from the sign-in flow, but Windows can still treat it as a work-managed or domain-like account because the credentials are synced through Google Workspace. In that case, Windows expects the identity provider to manage the password rules, and Hexnode may report a complexity conflict.
Also check whether another Microsoft account is connected on the device. Go to Settings > Accounts > Access work or school and confirm whether any secondary Microsoft account is present. If there is one, remove it and then reapply the Hexnode policy.
Regards,
Mary Romero
Save