How to Configure & Migrate Hybrid Exchange and Office 365 | Password Hash Sync - AD Connect Video 2

Second Video of Office 365 Hybrid Configuration on How to setup AD Sync using Password Hash Synch.
How password hash synchronization works
The Active Directory domain service stores passwords in the form of a hash value representation, of the actual user password. A hash value is a result of a one-way mathematical function (the hashing algorithm). There is no method to revert the result of a one-way function to the plain text version of a password. You cannot use a password hash to sign in to your on-premises network.
To synchronize your password, Azure AD Connect sync extracts your password hash from the on-premises Active Directory instance. Extra security processing is applied to the password hash before it is synchronized to the Azure Active Directory authentication service. Passwords are synchronized on a per-user basis and in chronological order.
The actual data flow of the password hash synchronization process is similar to the synchronization of user data. However, passwords are synchronized more frequently than the standard directory synchronization window for other attributes. The password hash synchronization process runs every 2 minutes. You cannot modify the frequency of this process. When you synchronize a password, it overwrites the existing cloud password.
The first time you enable the password hash synchronization feature, it performs an initial synchronization of the passwords of all in-scope users. You cannot explicitly define a subset of user passwords that you want to synchronize.
When you change an on-premises password, the updated password is synchronized, most often in a matter of minutes. The password hash synchronization feature automatically retries failed synchronization attempts. If an error occurs during an attempt to synchronize a password, an error is logged in your event viewer.
The synchronization of a password has no impact on the user who is currently signed in. Your current cloud service session is not immediately affected by a synchronized password change that occurs, while you are signed in, to a cloud service. However, when the cloud service requires you to authenticate again, you need to provide your new password.
A user must enter their corporate credentials a second time to authenticate to Azure AD, regardless of whether they're signed in to their corporate network. This pattern can be minimized, however, if the user selects the Keep me signed in (KMSI) check box at sign-in. This selection sets a session cookie that bypasses authentication for 180 days. KMSI behavior can be enabled or disabled by the Azure AD administrator. In addition, you can reduce password prompts by turning on Seamless SSO, which automatically signs users in when they are on their corporate devices connected to your corporate network.

[@BeHappy-rq9ql]

I love your teaching step by step on Hydrib setup in office 365. Awesome. thank you 🙏🏼

[@LordTachanka10]

Good video, you have a gift to explain technical subjects.

[@dannymatocinos9029]

You are the man!

[@aniludayabhanu652]

Good one keep it up.

[@syedrazi82]

In this video, we need to install Azure AD connect on which server? On prem-AD server or domain controller or we introduce a new VM as a connector between on prem and Azure AD? Kindly clarify this point

[@fasikhan3741]

Nice 1

[@alistairfreedom2456]

With AD sync is it important to sync the disabled 'arbitration mailbox' user objects from onprem to AAD ? In this demo I dont seem them listed in AAD...

[@sheldoncooper789]

Good one bro

[@kyecalitv713]

do i have to acquire/subscribe for AAD separately or it is already included during the subscription of o365?

[@kabyson]

++