ADFS confounding with EntaID connect

Question

Hello All , a customer has old Azure AD Connect and ADFS to connect to M365 the Azure AD connect does not manage ADFS, user sign in option in the old AAD connect os set to " do not configure" . they want to do swing migration to the newest EntraID connect, how they should configure the option of user sign in , should they leave it as " do not configure" ? and ADFS will continue to work ?

Answer 1

Hello @Hazem Elsaiegh Thank you for reaching out to Microsoft QnA Platform. I would like to state that if you already have an existing AD FS infrastructure and are performing a swing migration to new version of Azure AD Connect, then you can leave "User Sign-In" option to "Do not configure". This would not impact or make any changes to your existing ADFS architecture. Which means your user sign-in would flow through ADFS as expected.

I hope this helps and fixes your issue. Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Answer 2

@Hazem Elsaiegh

Thank you for posting this in Microsoft Q&A. As Harpreet mentioned in above answer, if you have already configured ADFS in your environment then you do not have to configure anything for "User Sign-in" option while configuring Entra connect.

You can select the option "Do not configure" in Entra ID connect while doing a swing migration. Make sure you upgrade the staging server first and then you can test the staging server. Once everything is fine you can move new staging server to production and then move old production to staging server. Once you move the old production server to staging, you can now upgrade the new staging server as well. Let us know if you have any further questions. Please "Accept the answer" if the information helped you. This will help us and others in the community as well.