Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Self-service password reset fails with SSPR_0029 or SSPR_0030: fixing password writeback on Microsoft Entra Connect

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A user who resets a password through self-service password reset (SSPR) sees SSPR_0029 or SSPR_0030. The password could not be written back to on-premises Active Directory. SSPR_0029 points at the on-premises configuration and SSPR_0030 at the connection to it. The proof is in the Application event log on the Microsoft Entra Connect server, and the fix is on that server, on the domain controllers or on the network between them and Microsoft.

Match the event to the cause before changing anything. Several different faults produce the same message, and their fixes are unrelated.

What the error means

SSPR lets a user reset a password without help-desk involvement. In a hybrid tenant with password writeback enabled, Microsoft's how-it-works page says the password is updated in Microsoft Entra ID and written back to Active Directory. If SSPR writeback is not deployed and the password is managed on-premises, the user is asked to contact their administrator.

The SSPR troubleshooting page lists the user-facing messages and their technical text. Three matter here:

  • SSPR_0010: "We've detected that password writeback hasn't been enabled. Contact your admin and ask them to enable password writeback."
  • SSPR_0029: "We're unable to reset your password due to an error in your on-premises configuration. Contact your admin and ask them to investigate."
  • SSPR_0030: "We can't reset your password due to a poor connection with your on-premises environment. Contact your admin and ask them to investigate."

The same page ties SSPR_0030 to connectivity and says the problem might be resolved if the user tries again later. It points SSPR_0029 to the writeback troubleshooting page. That page adds that SSPR_0029 can appear when writeback is enabled following all of the required steps, and that the event log then shows "the management agent credential was denied access".

Two event sources matter on the Entra Connect server, both in the Application log. The PasswordResetService source describes operations and problems related to the operation of password writeback. The ADSync source describes operations and problems related to setting passwords in Active Directory Domain Services.

Likely causes

Cause What you see How to confirm
Writeback not enabled SSPR_0010 The Password writeback box under Optional features in the Entra Connect wizard, and the writeback option on the SSPR On-premises integration page
Firewall or proxy blocks outbound access SSPR_0030; events 32002, 31034 or 32011 Test-NetConnection to the service bus namespace named in event 31034 or 31019
Connector account denied remote calls to SAM SSPR_0029; "management agent credential was denied access" in the log RSOP for "Network access: Restrict clients allowed to make remote calls to SAM"
Connector account lacks Reset password permission Access denied during resets; events 31003, 31008 or 33004 Effective Access of the connector account on a test user
Connector account password longer than 256 characters Resets and unlocks fail; "hr=800700CE, message=The filename or extension is too long" The event text on the Entra Connect server
Setup account was federated or had a wrong password Event 32009 "Error getting auth token." at the end of the installation The Hybrid Administrator account used when writeback was configured
Password writeback service did not start Event 6800 Application log after a restart of the sync service
Forest added after writeback was enabled Event 6329 with "0x8023061f (The operation failed because password synchronization isn't enabled on this Management Agent)" Forest changes since writeback was enabled
Password fails the domain's age, history, complexity or filter rules Event 6329 "0x80230619", or events 31008 or 33008 Domain password policy against the password chosen
User present and enabled in more than one forest, or duplicated anchors "Multiple matches found" error, event 33003 or "hr=80230402" Sync logs and the object in each forest
Domain controllers lack the LDAP password policy control Event 6329 "The server doesn't contain the LDAP password policy control." Domain controller version; the page says they must be Windows Server 2016 or later
Reserved characters in an organisational unit (OU) name Event 33001 The OU names against the page's list of reserved characters

Prove the cause before changing anything

Read these first. They are checks, not fixes; read any script before you run it.

  1. Note the exact message, the time and the user.
  2. On the Microsoft Entra Connect server, open Event Viewer > Windows Logs > Application. Microsoft's page recommends inspecting this log when troubleshooting writeback.
  3. Look for event 6800 (service did not start), 32002 ("Error Connecting to ServiceBus. The token provider was unable to provide a security token."), 32009, 31034, 32011, 6329, 31008 and 33004. Note any text that says "hr=800700CE".
  4. To test outbound access, find event 31034 or 31019, take the namespace from the event, and run the test from the server, replacing the placeholder with that namespace:
Test-NetConnection -ComputerName <namespace>.servicebus.windows.net -Port 443
Invoke-WebRequest -Uri https://<namespace>.servicebus.windows.net -Verbose
  1. Microsoft's page names these outbound HTTPS destinations for Entra Connect 1.1.443.0 and later: *.passwordreset.microsoftonline.com and *.servicebus.windows.net. The page also says: "The most common point of failure is that firewall or proxy ports, or idle time-outs are incorrectly configured." Event 32011 names TCP 443 and TCP 9350-9354.
  2. Check that TLS 1.2 is enabled on the sync server. The page links a PowerShell check script, to be run in Admin Mode, and says the output must show the path, name and value columns enabled correctly. Do not run the enabling script at this stage; it is a fix, covered below.
  3. Check that Microsoft .NET Framework 4.8 or higher is present on the sync server. The page links a registry query for this.
  4. Check permission: in Synchronization Service Manager, open the on-premises Active Directory connector Properties and note the account under Connect to Active Directory Forest. In Active Directory Users and Computers (Advanced Features on), open a test user's Properties > Security > Advanced > Effective Access, pick that account, and look for Reset password.
  5. For SSPR_0029 with "management agent credential was denied access", use RSOP on the Entra Connect server and on your domain controllers to see whether "Network access: Restrict clients allowed to make remote calls to SAM" is enabled. It is found under Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.

Example (illustrative): at Contoso (contoso.com.au), Hannah's reset ends with SSPR_0029. On sync01 the Application log shows the ADSync management agent was denied access. RSOP on sync01 shows "Network access: Restrict clients allowed to make remote calls to SAM" is enabled and the connector account is not in it. The fix is to add the connector account to that policy's allowed list.

Fix

Fix only the cause you proved.

  • SSPR_0010, writeback not enabled: Save first: write down the current value and which optional features the Entra Connect wizard shows ticked. Risk: turning writeback on lets a cloud password reset change the password of the on-premises account. On the SSPR On-premises integration page the writeback option set to Yes enables writeback and No disables it. Set it to Yes. Back-out: set the option back to its recorded value; with No, Microsoft's page says users are not able to reset their passwords, which is the state that produced SSPR_0010.
  • Firewall or proxy: Save first: export the current rule set and the Application log, and note when the last synchronisation finished. Risk: a firewall change affects other traffic. Disruptive step: restarting the server stops synchronisation and writeback until it is back. Allow the destinations above. After you update the rules, Microsoft's page says to restart the Microsoft Entra Connect server. Back-out: remove the rule you added; there is no way back from a restart, so wait for the server to start, then look for event 31015.
  • SSPR_0029 through the SAM policy: Save first: record the current policy value from RSOP and from the Group Policy that sets it. Disruptive step: the policy edit changes a security policy. Edit the policy to include the management account, shown as MSOL_ followed by characters, as an allowed user. Back-out: restore that value.
  • Reset password permission missing: Save first: export the current permissions on the target container. Risk: the grant widens what the connector account can do. Grant the permission to the Active Directory Management Agent (ADMA) account, following the page's reference to setting up the appropriate Active Directory permissions. Back-out: remove the permission you added. The page says it can take up to one hour for the permission to reach user objects through the sdprop background task, and until then resets keep failing with access denied.
  • Connector account password over 256 characters (event hr=800700CE): Save first: record the connector account name and the time of the change. Disruptive step: the account password and the password stored on the connector's Credentials page must match, so change both in one sitting. Reset the Active Directory account's password so it has no more than 256 characters, then open Synchronization Service, browse to Connectors, select the Active Directory Connector, select Properties and enter the new password on the Credentials page. Back-out: there is no restoring the old value, because it is the over-length password that caused the fault; if the new one is rejected, set another of no more than 256 characters in both places.
  • Hybrid Administrator account problem (event 32009): rerun the configuration with the correct username and password, and make sure the account is a managed (cloud-only or password-synchronised) account, not a federated one.
  • Restart the sync service: Save first: export the Application log. Disruptive step: the restart stops synchronisation and writeback. services.msc, find Azure AD Sync, Restart. Back-out: start the service again.
  • Disable and re-enable password writeback in the Entra Connect wizard, if the restart did not help or after a forest change (event 6329 with 0x8023061f). Save first: note which optional features are ticked. Disruptive step: while Password writeback is off, users cannot reset passwords. In the wizard enter the Microsoft Entra Hybrid Administrator credentials and the on-premises Active Directory Domain Services admin credentials, clear Password writeback under Optional features, select Next to Ready to configure, check it shows writeback as disabled, select Configure, and on Finished clear Synchronize now and select Finish. Then repeat the steps and tick Password writeback. Back-out: run the wizard again and tick Password writeback.
  • TLS 1.2 or .NET Framework missing: the page links an enabling script for TLS 1.2, followed by a server reboot, and a download for .NET Framework 4.8. Disruptive step: both change the server and the TLS script needs a reboot. Save first: take a checkpoint or backup of the sync server. Back-out: restore it.
  • Password policy failures (event 6329 0x80230619, 31008, 33008): the user must choose a password that meets the domain's age, history, complexity and filter rules. The page suggests setting minimum age and history to 0 only "For testing purposes"; do not change production policy for one user.
  • Duplicate users, protected groups, reserved OU characters, or domain controllers older than Windows Server 2016: the page identifies these but gives no repair steps, so decide with the owner of Active Directory. Accounts in protected groups, such as domain or enterprise admins, disallow password set operations, and 33004 can also occur when the user's AdminCount attribute is set to 1.

If the sync service restart and the writeback toggle do not fix it, the page's last step is to install the latest Microsoft Entra Connect release as an in-place upgrade, after backing up any customised sync rules. That upgrade is not covered here.

Confirm the fix

  1. Have a test user reset a password through SSPR and sign in with it. Do not repeat resets on one account while testing: the SSPR page says an automatic throttle applies after five reset attempts for the same account in one hour and the user must then wait 24 hours.
  2. In the Application log on the server, look for event 31002 (PasswordResetSuccess), which the page describes as the password being successfully written back to the local Active Directory environment. Event 31007 (ChangePasswordSuccess) is the event for a password change, not a reset, so a reset test will not produce it.
  3. Check that event 31015 (WriteBackServiceStarted) appears after a service restart.
  4. Check that no new 6800, 32002 or 6329 events appear.

What to watch afterwards

  • Events 31044 and 31034, which show writeback or the service bus listener failing.
  • Event 32014, which the page describes as a retry to connect to your tenant's Service Bus instance; if you see it many times, the page suggests checking your network connection to Service Bus.
  • New forests or domain controller changes: event 6329 follows forest changes after writeback was enabled.
  • User accounts in protected groups, where password set operations are disallowed (events 31003 and 31008).

Risks and limits

  • These commands have not been run or lab-tested.
  • Microsoft gives no time for network changes to take effect, apart from the one hour for permissions.
  • The TLS 1.2 and .NET Framework steps rely on scripts and downloads that Microsoft's writeback page links to; follow that page for them.
  • Check the current Microsoft pages for destinations and ports before changing a firewall.
  • Event 32002 and 32011 name a specific service bus address in the page; use the namespace in your own event.

Sources