Skip to content

Commit e72de4a

Browse files
authored
clean up language to comply with MS style
1 parent 1e59ba7 commit e72de4a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/authentication/howto-sspr-writeback.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ To use password writeback, you must have one of the following licenses assigned
5656
> Standalone Office 365 licensing plans *don't support "Self-Service Password Reset/Change/Unlock with on-premises writeback"* and require that you have one of the preceding plans for this functionality to work.
5757
>
5858
59-
## Active Directory permissions and the on premises Password complexity policies.
59+
## Active Directory permissions and on-premises password complexity policies
6060

6161
The account specified in the Azure AD Connect utility must have the following items set if you want to be in scope for SSPR:
6262

@@ -96,7 +96,7 @@ To set up the appropriate permissions for password writeback to occur, complete
9696
* **Write pwdLastSet**
9797
9. Select **Apply/OK** to apply the changes and exit any open dialog boxes.
9898

99-
Since the Source of authority is on-premises, the password complexity policies will apply from the same connected data source. Make sure you have changed the existing Group policies for "Minimum Password Length". Since this is set to 1 (which translates to - password should be atleast a day old before it can be updated), make sure it is set to 0. These can located in gpmc.msc under "Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies". Make sure you run 'gpupdate /force' for this change to take effect.
99+
Since the source of authority is on premises, the password complexity policies apply from the same connected data source. Make sure you've changed the existing group policies for "Minimum Password Length". The group policy shouldn't be set to 1, which means password should be at least a day old before it can be updated. You need make sure it's set to 0. These settings can be found in `gpmc.msc` under **Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies**. Run `gpupdate /force` to ensure that the change takes effect.
100100

101101
## Next steps
102102

0 commit comments

Comments
 (0)