<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>azure adconnect</title><link>https://evotec.xyz/es/tags/azure-adconnect</link><description>Evotec Main Website</description><atom:link href="https://evotec.xyz/es/tags/azure-adconnect/index.xml" rel="self" type="application/rss+xml" /><item><title>Upgrade Azure Active Directory Connect fails with unexpected error</title><link>https://evotec.xyz/es/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error</link><description>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.</description><pubDate>Wed, 02 Oct 2024 12:17:34 GMT</pubDate><guid>https://evotec.xyz/es/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error</guid><category>azure ad</category><category>azure adconnect</category><category>error</category><category>errors</category><category>Office 365</category><category>office365</category></item><item><title>Azure AD – Removing Inactive Azure AD Pass-through Agent</title><link>https://evotec.xyz/es/blog/azure-ad-removing-inactive-azure-ad-pass-through-agent</link><description>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.</description><pubDate>Sat, 25 Apr 2020 18:28:30 GMT</pubDate><guid>https://evotec.xyz/es/blog/azure-ad-removing-inactive-azure-ad-pass-through-agent</guid><category>azure ad</category><category>azure adconnect</category></item><item><title>AzureAD – Enable Password Expiration with Password Hash Synchronization</title><link>https://evotec.xyz/es/blog/azuread-enable-password-expiration-with-password-hash-synchronization</link><description>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.</description><pubDate>Mon, 24 Feb 2020 19:53:50 GMT</pubDate><guid>https://evotec.xyz/es/blog/azuread-enable-password-expiration-with-password-hash-synchronization</guid><category>Active Directory</category><category>azure ad</category><category>azure adconnect</category><category>powershell</category></item><item><title>Azure ADConnect Export Failed – Permission-issue error</title><link>https://evotec.xyz/es/blog/azure-adconnect-export-failed-permission-issue-error</link><description>During our recent setup of Azure ADConnect for one of our Clients we’ve been getting permission-issue – Insufficient access rights…</description><pubDate>Sun, 08 Oct 2017 19:23:20 GMT</pubDate><guid>https://evotec.xyz/es/blog/azure-adconnect-export-failed-permission-issue-error</guid><category>active directory</category><category>adconnect</category><category>azure ad</category><category>azure adconnect</category><category>error</category><category>errors</category><category>export failed</category><category>office 365</category><category>permission-issue</category><category>permissions</category><category>powershell</category><category>windows 2012R2</category><category>windows 2016</category><category>windows server 2016</category></item></channel></rss>