How to Change Azure AD Connect to Federated Sign-In with AD FS
Question details
The administrator wants to update the Azure AD Connect sign-in method to manage federation and support device registration without disrupting existing AD FS claim rules.

- Product
- Azure AD Connect
- Device & OS
- not provided
- Scenario
- Changing the sign-in method in Azure AD Connect from 'Do not configure' to 'Federated sign-in with AD FS'.
- Observed behavior
- An existing AD FS farm is already working manually with Azure AD Connect. The administrator needs to know if shifting federation management to Azure AD Connect will overwrite or break the existing relying-party or claims-provider rules.
Before altering your Azure AD Connect settings, ensure you have fully backed up your existing AD FS configuration and test the sign-in method change in a controlled staging environment first.
Updating Azure AD Connect Sign-In Method
Safely change your authentication method to Federated Sign-in with AD FS. This process simply redirects authentication and preserves your custom claim rules.
When AD FS federation is already manually configured, updating Azure AD Connect to manage the federation redirects authentication directly to your AD FS sign-in page.
Because claims-provider rules (which store authentication attributes in Active Directory) and relying-party rules (which receive claims in Azure AD) operate independently, updating the sign-in method in the wizard will not overwrite your existing custom rule sets.
Open the Azure AD Connect wizard on your primary server.
From the list of available tasks, click on 'Change user sign-in' and then click Next.
Enter your Azure AD Global Administrator credentials when prompted to authorize the configuration changes.
Select the radio button for 'Federation with AD FS' as your new sign-in method.
Follow the remaining prompts, ensuring you specify your existing AD FS farm. Apply the settings to finalize the transition.
Equip Your Enterprise with a Seamless Office Suite
While managing complex AD FS and Azure environments, it's crucial to provide your endpoint users with a reliable, lightweight, and highly compatible office suite. WPS Office offers an enterprise-friendly alternative to Microsoft Office that is cost-effective and easy to deploy.

Frequently Asked Questions
Will changing to Federated Sign-in delete my custom AD FS rules?
No. Claims-provider rules and relying-party rules are handled separately. Changing the sign-in method in Azure AD Connect simply updates the authentication routing flow and will not overwrite or break your existing custom claim rules.
What is the difference between a relying party and a claims provider?
A claims provider (such as Active Directory) stores the user attributes required for authentication. A relying party (such as Azure AD) is the application or service that receives these claims to authenticate and authorize the user.
Why should I let Azure AD Connect manage federation instead of doing it manually?
Allowing Azure AD Connect to manage your federation simplifies ongoing configuration, enables seamless updates, and provides built-in support for advanced features like Hybrid Azure AD join and seamless device registration.




