Enabling password hash sync with empty passwords

FP 0 Reputation points
2023-02-24T14:27:11.7533333+00:00

Hello,

I took over an environment which was set up in a non-ideal way.

A small business unit within a big company was carved out and so was their IT environment.

It was clear there were multiple On-Prem systems and also accounts that need to be migrated.

Unfortunately, they set up a fully working Azure AD only environment first and users started working with the Azure AD environment.

Afterwards they copied all the needed on-Prem ressources (groups and users) from the old on-prem AD to a new on-Prem AD using a 3rd party tool. The password hash was not copied over, so all copied on prem users now have NO password.

Azure AD Connect was set up afterwards without password hash sync. All on-prem accounts are now synced with their Azure AD Counterpart. Only issue is that the Azure AD User has a PW that works fine and the on prem user has no password at all.

This prevents users from accessing on-prem server as those are joined to the new on-prem AD.

My question is:
How can I get this solved without a major impact on the current operation? My original plan was to enable pw writeback and set an expiration date of 5 days in AzureAD so that every users would change their PW within the next 5 days and this new PW would be written back to on-Prem.

I activated password writeback but this doesn't seem to work if Passwordhash sync or ADFS is not activated.

What happens to the Azure AD Usersaccounts if I enable password hash sync but all on-prem users do not have a password?

Thanks in advance for any input.

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Michael Durkan 12,236 Reputation points MVP
    2023-02-24T14:49:38.37+00:00

    Hi

    when you enable Password Hash Sync, Active Directory becomes your "source or truth", so any Active Directory passwords that exist for Soft-Matched users in Azure AD will replace any existing Azure AD passwords that are in use.

    Password Writeback only works at the time of reset, so all existing passwords are not written back to on-premise AD.

    It a tricky one - my advice (depending on the amount of users in the business unit) would be to look at a trial of an AD Self-Service Password Reset tool to allow the users to create new passwords prior to enabling PHS. You should also ensure that any AD Password policies are secure as these will carry forward into Azure AD.

    Hope this helps, and good luck.

    Thanks

    Michael Durkan

    • If the reply was helpful please upvote and/or accept as answer as this helps others in the community with similar questions. Thanks!

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.