You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/cloud-sync/how-to-install.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,6 +100,18 @@ To verify that the agent is running:
100
100
>[!IMPORTANT]
101
101
>The agent has been installed, but it must be configured and enabled before it will start synchronizing users. To configure a new agent, see [Create a new configuration for Azure AD Connect cloud sync](how-to-configure.md).
102
102
103
+
### Enable password writeback in Azure AD Connect cloud sync
104
+
105
+
To use password writeback and enable the SSPR service to detect the cloud sync agent , you need to use the `Set-AADCloudSyncPasswordWritebackConfiguration` cmdlet and tenant’s global administrator credentials:
106
+
107
+
```
108
+
Import-Module "C:\\Program Files\\Microsoft Azure AD Connect Provisioning Agent\\Microsoft.CloudSync.Powershell.dll"
Copy file name to clipboardExpand all lines: articles/active-directory/cloud-sync/how-to-troubleshoot.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article describes how to troubleshoot problems that might aris
4
4
author: billmath
5
5
ms.author: billmath
6
6
manager: daveba
7
-
ms.date: 01/19/2021
7
+
ms.date: 10/13/2021
8
8
ms.topic: how-to
9
9
ms.prod: windows-server-threshold
10
10
ms.technology: identity-adfs
@@ -22,6 +22,7 @@ Cloud sync touches many different things and has many different dependencies. Th
22
22
|[Agent problems](#agent-problems)|Verify that the agent was installed correctly and that it communicates with Azure Active Directory (Azure AD).|
23
23
|[Object synchronization problems](#object-synchronization-problems)|Use provisioning logs to troubleshoot object synchronization problems.|
24
24
|[Provisioning quarantined problems](#provisioning-quarantined-problems)|Understand provisioning quarantine problems and how to fix them.|
25
+
|[Password writeback](#password-writeback)|Understand common password writeback issues and how to fix them.|
25
26
26
27
27
28
## Agent problems
@@ -227,6 +228,19 @@ If you need to repair the cloud sync service account you can use the `Repair-AAD
227
228
228
229
5. Once this completes it should say that the account was repaired successfully.
229
230
231
+
## Password writeback
232
+
The following information is important to keep in mind with regard to enabling and using password writeback with cloud sync.
233
+
234
+
- If you need to update the [gMSA permissions](how-to-gmsa-cmdlets.md#using-set-aadcloudsyncpermissions), it may take up to an hour or more for these permissions to replicate to all the objects in your directory. If you don't assign these permissions, writeback may appear to be configured correctly, but users may encounter errors when they update their on-premises passwords from the cloud. Permissions must be applied to “This object and all descendant objects” for **Unexpire Password** to appear.
235
+
- If passwords for some user accounts aren't written back to the on-premises directory, make sure that inheritance isn't disabled for the account in the on-prem AD DS environment. Write permissions for passwords must be applied to descendant objects for the feature to work correctly.
236
+
- Password policies in the on-premises AD DS environment may prevent password resets from being correctly processed. If you are testing this feature and want to reset passwords for users more than once per day, the group policy for Minimum password age must be set to 0. This setting can be found under **Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies** within **gpmc.msc**.
237
+
- If you update the group policy, wait for the updated policy to replicate, or use the gpupdate /force command.
238
+
- For passwords to be changed immediately, Minimum password age must be set to 0. However, if users adhere to the on-premises policies, and the Minimum password age is set to a value greater than zero, password writeback will not work after the on-premises policies are evaluated.
0 commit comments