cube maia

If you still have on-premises Active Directory you probably are synching your directory with Azure AD using the directory synchronization tool Azure AD Connect.

If you are using Office 365 and/or Azure AD and have an on-premises Active Directory, you already know that you can synchronize your on-premises directory with Azure AD using Azure AD Connect.

As you know Azure Active Directory Connect (AAD Connect) is used to synchronize your on-premises Active Directory objects (users, groups, devices) to Azure AD with the option to synchronize the user’s hash password (aka password sync, aka password hash sync, aka PHS).

Recently I had to update the configuration of an existing Azure AD Connect – the directly synchronization tool from Microsoft to synchronize your Active Directory identities to Azure AD – instance.

By now, you already know Azure AD Connect, the directory synchronization tool from Microsoft to provision your identities in Azure Active Directory (AAD).

By now, you should already know that Azure Active Directory Connect (AAD Connect) is the directory synchronization tool used to synchronize your on-premises Active Directory identities to Azure Active Directory (AAD).

Azure Active Directory Connect (AAD Connect), the directory synchronization tool to synchronize your Active Directory with Azure AD, just got refreshed with the release of the new version 1.5.18.0

Just had a weird issue with Azure AD Connect (the directory synchronization tool from Microsoft to sync from your Active Directory to Azure Active Directory) where we were getting the error “stopped-server-down” during the Delta Import step from Azure Active Directory during a synchronization.

As you may be already aware, support for password less with FIDO2 keys has been in preview for quite some time already for Azure AD Joined devices and browser sign-ins (see https://t.co/6HfQaQrsuR).

The following issue occurred for one of my customers after enabling MFA for all users. The directory synchronization stopped working.