Migrating SAML and OIDC Applications from AD FS to Azure AD Enterprise Applications
A zero-downtime migration blueprint for moving AD FS Relying Party Trusts into Azure AD Enterprise Applications to enforce centralized Conditional Access and Identity Protection.
Executive Summary and Federation Threat Context
Even after shifting core Microsoft 365 logins via Azure AD Staged Rollout, dozens of SaaS and internal apps frequently stay pinned as AD FS Relying Party Trusts, forcing teams to maintain twin identity planes. Using Azure AD Connect Health AD FS Application Activity telemetry, organizations gained clear migration readiness scores for every SAML, WS-Fed, and OIDC trust.
From an architectural evolution standpoint, this foundational design connects directly to modern platform controls. Initiated in 2022 to retire legacy AD FS federation farms, this SAML/OIDC app migration methodology anchors modern Entra Federation Retirement & Cloud Auth strategies.
Trust Boundaries and Federation Architecture Principles
- Combines
Get-AdfsRelyingPartyTrustexports with Connect Health Application Activity reports to classify apps as Ready or Requires Attention before migration. - Every application onboarded into Azure AD Enterprise Applications automatically inherits Conditional Access Authentication Strengths and real-time Identity Protection risk evaluation.
- Eliminates recurring WAP/AD FS token-signing certificate rotation risk and reduces external federation attack surface.
- Token-signing certificate lifecycles, extranet smart lockout thresholds, and custom
Relying Partyclaims must be audited before shifting authentication from on-premises AD FS farms to cloudPHS/PTAorAuthNextensions.
Prerequisites, RBAC Boundaries, and Migration Dependencies
- Licensing: Azure AD Premium P1/P2 (Microsoft 365 E3/E5 or EMS E3/E5) with Azure AD Connect Health Agent installed on AD FS nodes.
- RBAC Least Privilege: Delegate migrations using Application Administrator or Cloud Application Administrator roles rather than Global Administrator.
- Legacy Scope Note: Legacy Kerberos/NTLM web apps incapable of SAML/OIDC should be published via Azure AD Application Proxy.
Technical Verification, Identity Telemetry, and Controls
PowerShell Read-Only Audit and Pilot Validation
Inventorying active AD FS relying parties and verifying migrated SAML Enterprise Apps via Microsoft Graph PowerShell:
- Execution Environment and Prerequisites: Requires Microsoft.Graph, ActiveDirectory / RSAT / AD Sync / AD FS management host.
- Least Privilege and Operation Separation: Run with scoped Least-privilege Graph `.Read.All` scopes (delegated admin role only for writes) privileges. All statements above are **read-only (
Get-*/Test-*/Search-*)** verification checks making no direct configuration edits; still validate module/network prerequisites in a test cohort first. - Security Control Mapped and Boundary Note: Verifies active policy state and guards against silent drift or mis-scoped rollouts without blind production changes.
# 1. Inventory enabled AD FS Relying Party Trusts and protocol profiles
Get-AdfsRelyingPartyTrust | Where-Object { $_.Enabled -eq $true } |
Select-Object Name, Identifier, ProtocolProfile, SignatureAlgorithm, TokenLifetime |
Export-Csv -Path "C:\Temp\ADFS-RP-Inventory.csv" -NoTypeInformation
# 2. Verify migrated SAML Enterprise Applications in Microsoft Graph
Connect-MgGraph -Scopes "Application.Read.All", "Directory.Read.All"
Get-MgServicePrincipal -Filter "preferredSingleSignOnMode eq 'saml'" |
Select-Object DisplayName, AppId, PreferredSingleSignOnMode, AccountEnabledSecurity Telemetry and KQL Verification Query
KQL query auditing post-migration SAML/OIDC sign-in success and error codes across Enterprise Apps:
// Execution Scope: Read-only hunting/audit query (Log Analytics Reader / Security Reader)
// Data Source: Microsoft Entra ID Diagnostic Settings -> Log Analytics / Microsoft Sentinel (SigninLogs / AuditLogs)
SigninLogs
| where TimeGenerated > ago(7d)
| where AppDisplayName !in ("Office 365", "Microsoft Teams")
| extend StatusCode = toint(Status.errorCode), FailureReason = tostring(Status.failureReason)
| summarize TotalSignIns = count(), Failures = countif(StatusCode != 0) by AppDisplayName, FailureReason
| order by Failures desc, TotalSignIns descCritical Architectural Assessment, Cutover Risks, and Rollback Strategy
- Mismatched NameID Format or User Identifier: If AD FS issued
sAMAccountNameor email while Azure AD defaults touser.userprincipalname, SaaS vendors may lock users out or provision duplicate accounts. - Skipping Dual-Metadata Rollback Windows: SaaS platforms without staged multi-IdP testing require an explicit cutover window and preserved AD FS Relying Party rollback config (disabled, not immediately deleted).
- Risks Mitigated vs. Residual Limitations: Federation hardening and staged migration into cloud
PHS/PTAreduce extranet spray exposure against AD FS, mitigateGolden SAMLreliance, and lower on-premises certificate outage risk; however, they do not mitigateAiTMsession-cookie theft against weak MFA flows, unmigrated customSAMLrelying parties left behind during partial cuts, or lateral movement within legacy on-premisesKerberos/NTLMapplications. - New Dependencies and Production Failure Modes: Transitions rely directly on healthy
Entra ConnectPHS/PTApipelines, cleanImmutableIDmatching, and TLS 1.2+ alignment across AD FS/WAP farms. Retiring federation before translating custom AD FS claim transforms causes immediate SSO redirect loops for enterprise apps. - Rollback and Pilot Validation Procedure: Validate staged rollout batches on a bounded pilot security group first; if claim mismatches disrupt business apps, exclude the group via staged-rollout policies or keep AD FS nodes warm in standby until relying-party sign-in telemetry runs error-free.
Verified Primary Sources & Open-Source Repositories
This architectural guide was cross-corroborated against the official advisories, Microsoft Learn docs, and open-source PowerShell / KQL repositories below.
Multi-Channel Distribution Summary (X & LinkedIn Draft)
Toggle X (Twitter) & LinkedIn sharing drafts
Multi-Channel Distribution Summary (X & LinkedIn Draft)
Toggle X (Twitter) & LinkedIn sharing draftsStep-by-step blueprint for migrating AD FS SAML/OIDC Relying Party Trusts into Azure AD Enterprise Applications. #AzureAD #EntraID #ADFS
Retiring AD FS Safely: Using Connect Health inventory, custom claim mappings, and dual-window rollbacks to move SaaS apps onto centralized Conditional Access.