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. As you may be already aware, there is now 2 versions of Azure AD Connect: 1.x and 2.x The 1.x version is some sort of legacy version allowing customer still running […]
Azure AD – The Azure AD Connect version 1.x will be retired in August 2022 Read More »
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 may already be using Azure AD Connect, you (should) also know that you need to keep up with the Azure AD
As announced in early November 2020, support for old versions of TLS (TLS 1.0 and TLS 1.1) and ciphers (3DES cipher suite) are going to be deprecated and no longer supported starting June 30, 2021. You have to ensure your on-premises systems interacting with Azure AD – such as Azure AD Connect, Azure AD Application
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). Well, with this new version – 1.6.2.4 – available for download here https://go.microsoft.com/fwlink/?LinkId=615771
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. It was running the latest version at that time (1.5.42). The error was: An error occurred while connecting to the state store: Attempted to
By now, you already know Azure AD Connect, the directory synchronization tool from Microsoft to provision your identities in Azure Active Directory (AAD). Well, a new version has been released (version 1.5.42.0) which allows you to export your configuration and then re use it when installing/configuring a new instance. You may already know the Azure
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). Well, AAD Connect just got an upgrade (version 1.5.30.0) which support the new Azure AD Connect sync V2 endpoint API (currently in preview –
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 In addition of the usual bug fixes – see below, there has been some improvements too: Fixed issues: Fixed a bug in the group writeback forest/OU
Azure – A new version of the Azure AD Connect has been released Read More »
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. Everything else was working perfectly fine (password sync, password write-back, sync
Azure AD Connect – Getting stopped-server-down error when importing from Azure AD Read More »
The following issue occurred for one of my customers after enabling MFA for all users. The directory synchronization stopped working. The above situation may not occur often as usually you are excluding trusted locations (aka your corporate network public endpoints) from applying conditional policies – especially when enabling MFA – and your Azure AD Connect
