Skip to content

How to Create a Fine-Grained Password Policy in Active Directory Print

  • 0

A fine-grained password policy lets an AD domain apply a different password and account-lockout policy to selected users. It is represented by a password settings object, or PSO, rather than by linking a password GPO to an OU. Use it for a defined account population with an owner, clear precedence and a verified resultant policy.

This guide uses a pilot global security group before broader assignment. The example values illustrate the mechanism and must be replaced with the organization's approved security policy. Password length, expiry and lockout settings should reflect the authentication design, threat model and support process rather than being copied from a generic “strict” profile.

Confirm that fine-grained policy is the right tool

Fine-grained policies apply to user objects and global security groups, not directly to organizational units. Moving a user into an OU does not by itself assign a PSO. If the desired population follows an OU, maintain an explicit supported group-membership process rather than pretending the PSO has an OU link.

The policy concerns AD domain passwords and lockout behavior. It does not establish MFA, smart-card requirements, local account policy, application-specific password stores or every aspect of privileged access. Use those controls through their own management systems.

Check the current domain functional level and the management prerequisites for your environment. Microsoft's current ADAC workflow lists Windows Server 2012 or later functional level and suitable AD tools. Use an authorized delegated administrator or the documented administrative role; do not give application operators broad directory privileges merely so they can view a password policy.

Inventory existing policies and assignments

Inspect the default domain password policy and existing PSOs before creating another one:

Get-ADDomain | Select-Object DNSRoot,DomainMode
Get-ADDefaultDomainPasswordPolicy
Get-ADFineGrainedPasswordPolicy -Filter * |
    Select-Object Name,Precedence,MinPasswordLength,MaxPasswordAge,LockoutThreshold

Record current assignments and any direct per-user exceptions. A domain with many undocumented PSOs can produce surprising results, especially where users belong to several targeted groups. Identify an owner and justification for each policy before adding overlapping rules.

Review service accounts separately. Applying a new expiry or lockout policy to a traditional service account can create an outage at the next password-age decision, failed login burst or service restart. Prefer a supported managed-account design where appropriate and coordinate any traditional-account exception explicitly.

Understand precedence before choosing a number

A user can be associated with several PSOs but has one resultant policy. A directly assigned policy takes precedence over group-derived policies. Among applicable policies in the relevant selection stage, a lower numerical precedence value has higher priority. Do not assume a policy named “Privileged” automatically wins.

Avoid equal precedence values where overlapping applicability is possible. Directory tie-breaking rules exist, but relying on them makes the design difficult to explain and audit. Choose a documented numbering scheme and verify the actual resultant object rather than reasoning only from the policy list.

If no PSO applies, the default domain password policy remains relevant. A command returning no fine-grained resultant object does not mean the user has no password controls. Include that fallback in reports and support instructions.

Create a pilot group and an unassigned policy

Create a dedicated global security group with a clear owner, for example GG-PasswordPolicy-Pilot. Add only approved test users initially. Do not include production privileged or service accounts until the policy and rollback behavior are understood.

Create the PSO with explicit values so readers can review the entire policy. The following is an illustration, not a recommended baseline:

New-ADFineGrainedPasswordPolicy -Name 'PSO-Pilot-Example' `
    -Precedence 20 -MinPasswordLength 15 -PasswordHistoryCount 24 `
    -ComplexityEnabled $true -ReversibleEncryptionEnabled $false `
    -MinPasswordAge (New-TimeSpan -Days 1) `
    -MaxPasswordAge (New-TimeSpan -Days 90) `
    -LockoutThreshold 10 `
    -LockoutObservationWindow (New-TimeSpan -Minutes 15) `
    -LockoutDuration (New-TimeSpan -Minutes 15)

Review each value with the security owner. The maximum-age example deliberately demonstrates an expiry value; choose an approved expiry approach rather than treating ninety days as an automatic best practice. Check platform and application support for the selected minimum length and other controls.

Reversible encryption should remain disabled unless an exceptional supported requirement has been explicitly approved. It is not needed to make ordinary Windows password authentication work.

Assign the policy and inspect the result

Associate the PSO with the pilot global security group:

Add-ADFineGrainedPasswordPolicySubject -Identity 'PSO-Pilot-Example' `
    -Subjects 'GG-PasswordPolicy-Pilot'
Get-ADFineGrainedPasswordPolicySubject -Identity 'PSO-Pilot-Example'

Allow directory replication and query a pilot user through the appropriate domain context:

Get-ADUserResultantPasswordPolicy -Identity 'PasswordPolicyTest' |
    Select-Object Name,Precedence,MinPasswordLength,MaxPasswordAge,LockoutThreshold

Use the actual approved test account. Verify that the returned policy is the intended one and compare all relevant settings, not just the name. Where a different controller is involved in testing, use the supported Server parameter and account for replication rather than repeatedly changing assignments.

Test password and lockout behavior safely

Use a dedicated test account and a controlled password-change procedure. Verify the expected acceptance or rejection of candidate passwords without printing them into logs or tickets. Complexity and history checks can interact with other password-filtering products, so interpret the resulting error in that context.

Lockout testing should be isolated and authorized. Repeated failures against a production employee or administrator account can deny service and generate misleading security incidents. Coordinate with monitoring, define the test duration and verify the expected unlock behavior.

Understand timing. A new minimum-length requirement does not magically rewrite existing passwords, while age and lockout settings can affect users operationally. Review password-age and exemption properties before a rollout so the help desk knows what users may experience.

Distinguish directory replication from Group Policy refresh

A PSO is a directory object, not an ordinary linked GPO. Repeatedly running gpupdate on a workstation does not correct a missing PSO subject association or broken AD replication. Query the resultant policy through the relevant controller and compare the directory state before changing client settings.

For an affected user, also inspect PasswordLastSet, PasswordNeverExpires and LockedOut through an authorized account query. These properties help explain operational behavior that the PSO name alone cannot. Do not remove an exemption or unlock a production account as a diagnostic shortcut without its owner's approved process.

Roll out with ownership and support readiness

Expand group membership in controlled stages and verify representative users' resultant policies. Include users with overlapping group memberships and direct exceptions. Keep the membership source aligned with account lifecycle changes so a user does not retain an unintended policy after moving roles.

Communicate any user-visible password or lockout changes and prepare support staff with the effective-policy query. Monitor lockout events, failed logons and service failures after rollout. A surge can indicate stale stored credentials or an unexpected account included in scope, not necessarily an attack alone.

Record the policy values, assignment group, precedence rationale, approving owner and validation evidence. Review those details whenever another PSO is introduced, since a new overlap can change the resultant policy without editing the original object.

Reverse assignment before deleting the object

To withdraw the pilot policy, remove its intended subject association and verify the user's new resultant policy. Do not delete a PSO first without understanding every user and group it affects. Falling back to another policy can loosen or tighten controls unexpectedly.

Changing or removing the PSO does not undo passwords users already changed, restore failed service transactions or erase lockout history. Address those consequences separately. Retain the previous values and assignments so the rollback is a concrete configuration change rather than a guess.

Microsoft's configuration guide and resultant-policy reference describe the supported assignment and precedence model.

Related procedures

How to Configure a Dedicated Service Account for a Windows Application; How to Configure the Active Directory Recycle Bin; How to Audit Active Directory Group Membership Changes.


Was this answer helpful?

« Back