Study guide

5.3 AD FS Migration & Connect Health

Exam SC-300: Microsoft Identity and Access Administrator Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts & Logistics 1.2 Audience Profile, Zero Trust & Role Scope 1.3 Skills Measured & Study Map

2 Entra Tenant Administration

2.1 Tenant Properties, Domains & Company Branding 2.2 Built-in & Custom Roles, Effective Permissions 2.3 Administrative Units

3 Users, Groups, Licenses & Devices

3.1 Create, Configure & Manage Users 3.2 Groups & Custom Security Attributes 3.3 Licenses, Bulk Operations & Device Join

4 External Identities & Cross-Tenant Access

4.1 External Collaboration & Guest Lifecycle 4.2 Cross-Tenant Access Settings 4.3 Cross-Tenant Sync & External Identity Providers

5 Hybrid Identity

5.1 Entra Connect Sync vs Cloud Sync 5.2 PHS, PTA & Seamless SSO 5.3 AD FS Migration & Connect Health

6 Authentication Methods & MFA

6.1 Authentication Methods Portfolio 6.2 MFA, SSPR & Password Protection 6.3 Passwordless, Session Control & Entra Kerberos

7 Conditional Access

7.1 Planning, Assignments & Controls 7.2 Session Management, Device Restrictions & CAE 7.3 Auth Context, Protected Actions, Templates & Troubleshooting

8 Identity Protection & Global Secure Access

8.1 User Risk & Sign-in Risk 8.2 MFA Registration Campaigns & Risky Workloads 8.3 Global Secure Access

9 Workload & Managed Identities

9.1 Selecting Identities for Apps & Azure Workloads 9.2 Create, Assign & Use Managed Identities 9.3 Service Principals Fundamentals

10 Enterprise Apps & App Registrations

10.1 Enterprise Applications Integration 10.2 App Registrations, API Permissions & App Roles 10.3 Application Proxy & Consent

11 Microsoft Defender for Cloud Apps

11.1 Cloud Discovery & Connected Apps 11.2 CA App Control & Session Policies 11.3 OAuth App Policies & Catalog Management

12 Entitlement Management

12.1 Catalogs & Access Packages 12.2 Access Requests & Terms of Use 12.3 Connected Organizations & External User Lifecycle

13 Access Reviews

13.1 Plan & Create Access Reviews 13.2 Monitor & Respond to Access Reviews

14 Privileged Identity Management

14.1 PIM for Entra Roles & Azure Resources 14.2 PIM for Groups, Approval & Audit 14.3 Break-Glass (Emergency Access) Accounts

15 Monitoring, Logs & Secure Score

15.1 Sign-in, Audit & Provisioning Logs 15.2 Diagnostics, KQL & Workbooks 15.3 Identity Secure Score

5.3 AD FS Migration & Connect Health

Key Takeaways Explain This Topic AI

Migrating from AD FS to Microsoft Entra cloud authentication (PHS or PTA) reduces farm, proxy, and certificate operational burden while enabling modern Conditional Access and identity protection patterns.

Staged rollout / selective password hash sync lets you pilot cloud authentication for subsets of users before converting an entire federated domain.

Plan migration as: inventory apps and claims, enable PHS (and/or PTA), pilot with staged rollout, convert domain to managed, decommission AD FS when dependencies are gone.

Microsoft Entra Connect Health monitors Connect Sync and AD FS (and related components), surfacing performance, error, and availability signals administrators use for proactive operations.

Health alerts notify admins of sync failures, AD FS issues, and risky hybrid conditions so outages and silent identity drift are caught before users flood the helpdesk.

Last updated: July 2026

Why leave AD FS for cloud authentication

Active Directory Federation Services (AD FS) was the classic way to provide SSO from on-premises AD to Microsoft 365 and other claims-aware apps. It still works—and SC-300 still expects you to understand it—but Microsoft’s modernization guidance for most organizations is Microsoft Entra ID cloud authentication with password hash synchronization and/or pass-through authentication , plus Conditional Access, not a perpetual AD FS farm for first-party Microsoft workloads.

Pain points AD FS introduces that exam stems exploit:

  • Pain Operational impact
  • Farm servers + SQL/WID Patching, capacity, backup
  • Web Application Proxy / reverse proxies Extra internet edge components
  • Token-signing and SSL certificates Expiry causes company-wide outages
  • Network dependencies Branch/cloud sign-in fails when farm path breaks
  • Claims rules complexity Harder to reason than Entra Conditional Access
  • Duplicate security stacks MFA and policies split between AD FS and Entra

Migration value proposition: simpler auth path , better integration with Identity Protection , Conditional Access , passwordless methods, and reduced certificate-driven outages.

Managed versus federated domains

In Microsoft Entra ID, a custom domain’s authentication type is critical:

  • Domain state Sign-in behavior for password users
  • Managed Microsoft Entra cloud authentication (PHS and/or PTA as configured)
  • Federated Redirect to AD FS (or other IdP) for authentication

Migration’s technical climax is often converting a federated domain to managed after cloud auth prerequisites are healthy. Until conversion, federation may still handle password sign-ins even if PHS is already running in the background.

  • Migration roadmap (exam-ready sequence)
  • Use this ordered plan when a stem asks “how should the company migrate from AD FS?”
  • 1. Discover and inventory

List relying party trusts: Microsoft 365 / Entra, third-party SaaS, custom apps.

Note claims rules that Entra Conditional Access or app provisioning cannot replace without redesign.

Identify certificate auth, third-party MFA adapters, or legacy protocols still bound to AD FS.

Confirm hybrid sync is healthy (Connect Sync or Cloud Sync) and UPNs are aligned.

2. Enable cloud authentication prerequisites

Enable password hash synchronization (strongly preferred as primary or backup).

Or deploy PTA agents (multiple) if policy requires live AD validation.

Optionally enable seamless SSO for domain-joined UX.

Validate test accounts can authenticate when forced through cloud auth paths in a pilot.

3. Staged rollout / selective password hash sync concepts

Microsoft provides staged rollout of cloud authentication so you do not flip an entire federated domain on day one.

Conceptual behavior:

Domain may remain federated globally.

Selected users or groups are directed to cloud authentication (PHS or PTA) for supported apps while others still use AD FS.

You expand the pilot cohort as success metrics pass.

After confidence is high, convert the domain to managed and retire AD FS for those workloads.

Selective password hash synchronization language on exams may refer to controlling who gets hashes synchronized or which populations participate early in cloud auth—always read the stem. In practice, combine:

Sync scoping (OU/group) so only intended users exist/sync as expected.

Staged rollout groups for authentication path piloting.

Communication plans for password change timing and helpdesk scripts.

  • Phase Users Auth path Success checks
  • 0 None AD FS PHS/PTA installed and healthy
  • 1 IT pilot group Cloud auth via staged rollout Sign-in logs success, no cert dependency
  • 2 Business pilot Cloud auth App compatibility, MFA/CA policies
  • 3 Broad cohorts Cloud auth Support volume normal
  • 4 Domain conversion Managed domain AD FS traffic near zero for M365
  • 5 Decommission N/A Remaining apps moved or retired
  • 4. Convert domain and decommission carefully

Convert federated domain to managed when pilots succeed.

Keep AD FS online temporarily for any non-Entra relying parties still depending on it.

Migrate remaining apps to Entra ID (SAML/OIDC enterprise apps) or other IdPs.

Only then decommission AD FS farms and proxies; revoke unused certificates; update DNS/public endpoints.

Do not decommission AD FS the same afternoon you enable PHS without staged validation—classic exam fail.

Decision matrix: stay federated or migrate

  • Requirement Prefer
  • Microsoft 365 + modern CA + simplify ops Migrate to PHS/PTA
  • Complex claims only AD FS issues today Stay federated or redesign claims in Entra apps before cutover
  • Third-party IdP must remain authoritative Remain federated to that IdP

Certificate-based auth only via current AD FS design Plan alternative Entra certificate auth / CBA patterns before killing AD FS

  • Regulators demand on-prem password check PTA cloud auth (still can leave AD FS)
  • Frequent AD FS outages, simple claims Migrate urgently to PHS
  • Microsoft Entra Connect Health overview

Microsoft Entra Connect Health is the monitoring solution for hybrid identity infrastructure. Administrators use it to see whether sync and federation components are healthy before users report outages.

Primary workloads monitored (exam focus):

Microsoft Entra Connect Sync — sync errors, export failures, latency, dual-export risks, service status.

AD FS — farm health, authentication failures, proxy trust issues, performance, certificate-related problems.

Related agents/services depending on what is deployed in the environment (Connect Health agents installed on monitored servers).

High-level architecture:

Install Connect Health agents on Connect Sync servers, AD FS servers, and Web Application Proxy servers as applicable.

Agents upload health telemetry to Microsoft.

Admins view dashboards, trends, and alerts in the Microsoft Entra admin center (Connect Health blades).

Requires appropriate licensing (historically Entra ID P1 features for full Connect Health scenarios—exam may treat it as the correct monitoring product regardless of SKU deep dives).

What admins watch in Connect Health

  • Area Signals Why it matters
  • Sync errors Object-level export/import failures Missing users, stale attributes, broken groups
  • Sync latency Time since last successful export Password hashes and profile data delayed
  • Service status Connect service not running Complete sync stoppage
  • AD FS application Failed auths, extranet lockouts patterns User sign-in pain
  • AD FS performance Token request latency, CPU Capacity planning
  • Proxies WAP connectivity/trust External user auth breaks
  • Alerts Email/admin notifications Proactive response

During AD FS migration , Connect Health is doubly valuable: it proves the old farm’s failure modes and confirms the hybrid sync backbone remains green while staged rollout expands.

Health alerts and operational use cases

Alerts are the exam’s practical angle—why bother installing agents?

Common reasons admins rely on Connect Health alerts:

Silent sync failure — Connect server disk full or service stopped; cloud identities drift from AD for hours before anyone notices.

Certificate expiration approaching — AD FS token-signing or SSL issues historically cause sudden org-wide Microsoft 365 failures; health insights help catch farm problems earlier.

Sudden spike in AD FS auth failures — bad password spray, misconfigured relying party, or network path failure.

Export errors on high-value objects — executives or break-glass accounts failing to update.

Duplicate or topology warnings — risky Connect configurations (for example, unexpected server behaviors) that need immediate admin attention.

Response pattern for SC-300 troubleshooting stems:

Check Microsoft Entra sign-in logs for user-level auth errors.

Check Connect Health for infrastructure-level hybrid failures.

Check local Synchronization Service Manager / Cloud Sync provisioning logs for object errors.

Fix root cause (agent down, DC unreachable, cert expired, OU filter mistake); do not “reset MFA for everyone” as a first step.

Migration + health: end-to-end scenario

Contoso runs AD FS for contoso.com , suffers annual cert outages, and wants Conditional Access consistency.

Recommended storyline:

Ensure Entra Connect Sync (or Cloud Sync) is healthy; view status in Connect Health .

Enable PHS ; confirm hashes appear/sync errors are zero for pilot OUs.

Create staged rollout group Cloud-Auth-Pilot ; add identity team; validate Microsoft 365 sign-in uses cloud auth.

Expand pilot; monitor sign-in logs and Connect Health AD FS metrics (traffic should drop for pilot users).

Convert contoso.com from federated to managed .

Migrate leftover relying parties; decommission AD FS; keep Connect Health on sync servers ongoing.

If at step 3 pilot users fail, do not convert the domain. Roll back pilot membership, fix PTA agents or PHS issues, retest.

Common exam traps

Converting the domain to managed before enabling PHS/PTA.

Decommissioning AD FS while third-party apps still federate exclusively to it.

Using Azure Monitor alone as the “best” AD FS hybrid identity health product when the stem points to Connect Health .

Assuming staged rollout requires rewriting every user’s UPN.

Treating Connect Health as a replacement for Conditional Access or PIM.

Forgetting multiple PTA agents when migrating to PTA instead of PHS.

Quick recall table

  • Goal Tool / action
  • Pilot cloud auth without domain-wide cutover Staged rollout of cloud authentication
  • Primary simple cloud password auth Password hash synchronization
  • Live AD password validation PTA + multiple agents
  • Watch sync and AD FS health Microsoft Entra Connect Health
  • Finish migration Convert domain to managed; decommission AD FS when unused
  • Detect hybrid outages early Connect Health alerts + sign-in logs

Hybrid identity operations end where governance begins: a managed domain with healthy sync, modern authentication methods, and monitored infrastructure. For SC-300, migration is a planned staged process , and Connect Health is the operator’s windshield for Connect Sync and AD FS—not an optional nice-to-have.