Windows 10 or later Configuration Policy - Block Password Saving In Google Chrome
Configuration policy for blocking password saving in Google Chrome
Settings this baseline controls
| Setting | What it does |
|---|---|
| Policy name | Name of the configuration policy. Learn more |
| Policy description | Description of the configuration policy. Learn more |
| Password manager enabled | Controls whether passwords can be saved using the password manager. Learn more |
| Group assignments | The list of group assignments for this configuration policy. Learn more |
Configure it
Add this to a tenant whose Windows fleet uses Google Chrome, so the browser stops acting as a password store in its own right.
-
Add the baseline to the tenant directly (Adding a baseline), or include it in a scheme you deploy to every tenant whose devices run Chrome (Deploying a scheme).
-
Leave Password manager enabled switched off; it’s the one setting that matters here. Chrome then stops offering to save or automatically fill in sign-in passwords on every device the policy reaches.
-
Save. There’s nothing else to configure. Turn on Auto-remediation if you want Octiga to recreate the policy in Intune whenever it’s changed or removed.
Check it worked
This baseline shows Passing once the configuration profile exists in Intune with the setting above and a Windows device has reported it applied successfully. To check progress, go to Devices → Manage devices → Configuration in the Microsoft Intune admin centre, open the profile (its Profile type reads “Settings catalog”), and use its device status and per-setting status views. Users notice Chrome no longer offers to remember or fill in a password when they sign in to a site.
Standards this addresses
Doing this for every tenant?
Step through the deploy wizard to apply a scheme to a tenant, groups or users, and see what Managed and Direct do at deploy time.