is adfs dead?

Security and Identity

The State of Active Directory Federation Services (AD FS)

AD FS is not officially "dead," but it is considered legacy technology by Microsoft. As such, the company advises organizations to migrate away from it toward modern, cloud-based identity solutions like Microsoft Entra ID.

Drivers for Migration

Several factors contribute to the push away from AD FS:

  • The shift to Microsoft Entra ID as Microsoft's primary identity and access management solution, providing single sign-on (SSO) and federation capabilities without requiring on-premises server infrastructure.
  • The complexity and security concerns associated with maintaining an AD FS farm, which acts as a high-value target for attacks.
  • The active deprecation of legacy protocols like WS-Federation and WS-Trust in favor of OpenID Connect (OIDC) and OAuth2.
  • The need to modernize application access, with Microsoft providing tools like the Microsoft Entra Staged Rollout and Entra ID Decommission Guide to transition applications away from AD FS federation.

Recommendations for AD FS Users

If you are currently running AD FS, it is essential to treat it as a legacy system. While there is no forced end-of-life date, new implementations and greenfield projects should default to Entra ID. For existing setups, planning a migration to cloud authentication using Password Hash Synchronization (PHS) or Pass-Through Authentication (PTA) is highly recommended to eventually retire on-premises AD FS servers.

Hosting Microsoft Entra ID On-Premises

It is not possible to host Microsoft Entra ID on-premises, as it is a cloud-native Identity-as-a-Service (IDaaS) platform running entirely on Microsoft's global cloud infrastructure. However, Microsoft provides tools to integrate Entra ID with your existing on-premises infrastructure:

  • Microsoft Entra Connect Sync: Syncs local Active Directory objects to Microsoft Entra ID, allowing users to use the same credentials for both local resources and cloud applications.
  • Private Network Connectors: Securely exposes on-premises apps to remote users via Microsoft Entra Private Access without requiring a traditional corporate VPN.
  • Windows Server Integration: Modern versions of Windows Server allow connecting local servers directly to Entra ID using Azure Arc, bringing cloud-based identity and security management to on-premises hardware.

Microsoft Entra ID Pricing

To fully replace AD FS capabilities, the Microsoft Entra ID P1 plan is required, which costs $6.00 per user/month (billed annually). This plan includes features like:

  • Conditional Access Policies: Replaces AD FS access control policies, allowing you to block or permit sign-ins based on location, device health, or application type.
  • Microsoft Entra Application Proxy: Replaces the AD FS Web Application Proxy (WAP), securely publishing internal, on-premises web apps to external users without opening inbound firewall ports.
  • Advanced Hybrid Sync: Enables seamless single sign-on (SSO) and password hash synchronization from your local Active Directory.

Other tiers are available, but the P1 plan is necessary for replacing AD FS infrastructure. When planning your infrastructure strategy, consider your compliance and network requirements to determine the best approach for your organization.

Back to all articles