https://evotec.xyz/es/tags/azure-adconnect/index.atom.xml2024-10-02T12:17:34.0000000ZEvotec Main Websitehttps://evotec.xyz/es/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error2024-10-02T12:17:34.0000000Z

Today, I made the decision to upgrade my test environment and update the version of Azure AD Connect to the latest one. The process is usually simple: download a new MSI, run it, click next a few times, enter the credentials for your Global Admin, and you’re finished. However, this time, I encountered an error.

https://evotec.xyz/es/blog/azure-ad-removing-inactive-azure-ad-pass-through-agent2020-04-25T18:28:30.0000000Z

Recently I was switching Office 365 tenant from ADFS to Azure AD Pass-through authentication (PTA). It all went smoothly with one exception. After removing one of the Azure AD Connect servers and all applications from its Azure AD Connect interface still is showing said agent, just inactive.

https://evotec.xyz/es/blog/azuread-enable-password-expiration-with-password-hash-synchronization2020-02-24T19:53:50.0000000Z

Azure AD Connect allows three ways to make sure the user password is the same in Active Directory and Office 365. Those are Password Hash Sync, Pass-Thru Authentication, and ADFS. While my preferred option to go with would be Pass-Thru Authentication, only Password Hash Synchronization is the easiest and least resource-intensive. It synchronizes user password to Office 365, and even if your Active Directory is down, you can still log in to Office 365. It’s perfect for small and even more significant companies that don’t have resources or can’t guarantee that their infrastructure will stay 100% time online so users can authenticate based on their Active Directory.

https://evotec.xyz/es/blog/azure-adconnect-export-failed-permission-issue-error2017-10-08T19:23:20.0000000Z

During our recent setup of Azure ADConnect for one of our Clients we’ve been getting permission-issue – Insufficient access rights…