Configuring Pass-through Authentication for Entra ID Protection

MS-102 By islever Editorial Last updated

Short answer

D Select Pass-through authentication to allow Microsoft Entra ID Protection to evaluate sign-in risks and detect leaked credentials in real-time against on-premises Active Directory.

Question

Your on-premises network contains an Active Directory Domain Services (AD DS) domain.
You have a Microsoft 365 E5 subscription.
You plan to implement Microsoft Entra Connect Sync and use Microsoft Entra ID Protection.
You need to configure Microsoft Entra Connect Sync to ensure that Microsoft Entra ID Protection can detect leaked credentials.
What should you select?
  1. Password writeback
  2. Password Hash Synchronization
  3. Configure Hybrid Microsoft Entra join
  4. Pass-through authentication Correct Answer
  5. Enable single sign-on

Key Takeaways

The main trap is confusing Password Hash Synchronization with Pass-through authentication; only PTA provides the necessary real-time authentication flow that integrates seamlessly with ID Protection's risk evaluation for leaked credential detection.

Learn why Pass-through authentication is required for Microsoft Entra ID Protection to detect leaked credentials in a hybrid environment with on-premises AD DS.

Common mistake: Candidates often choose Password Hash Synchronization because it is a common sync method, but it does not offer the same direct integration with on-premises security contexts needed for effective leaked credential detection via ID Protection.

Expert Analysis

The requirement is to enable Microsoft Entra ID Protection to detect leaked credentials. Microsoft Entra ID Protection relies on analyzing sign-in risk events, which requires it to have visibility into the authentication process and the ability to block risky sign-ins.

Pass-through authentication (PTA) allows Microsoft Entra ID to validate passwords against the on-premises AD DS in real-time without storing hashes in the cloud or requiring complex synchronization of password data. Crucially, PTA enables Microsoft Entra ID Protection to evaluate risk policies at the time of authentication. When a user attempts to sign in, the authentication request is forwarded to an agent on-premises, but the risk evaluation happens in the cloud based on the sign-in context. This architecture supports the detection of anomalous behaviors and leaked credentials because the cloud service can inspect the sign-in event details.

Other options do not support this specific capability effectively:

  • Password Hash Synchronization (PHS) stores hashed passwords in Azure AD. While it allows for some risk detection, it does not provide the same level of integration with on-premises security controls for detecting leaked credentials in the context of hybrid identity management as PTA does when combined with ID Protection's risk-based blocking capabilities.
  • Password writeback allows users to change passwords on-premises from the cloud but does not inherently enable ID Protection's leaked credential detection.
  • Hybrid Microsoft Entra join is about device identity, not user credential leakage detection.
  • Single sign-on is a feature of authentication methods, not a configuration setting for ID Protection detection.

Therefore, Pass-through authentication is the correct choice to ensure Microsoft Entra ID Protection can effectively detect and respond to leaked credentials by evaluating risk during the authentication flow.

Exam Strategy

When configuring hybrid identity solutions, always consider the security features you need to support. If the question specifies using Microsoft Entra ID Protection for risk detection, prioritize authentication methods like Pass-through authentication that allow the cloud service to evaluate risk during the actual authentication attempt against on-premises sources.

Frequently Asked Questions

Why can't Password Hash Synchronization be used for leaked credential detection?

While PHS allows for some risk detection, Pass-through authentication provides a more direct link to on-premises security contexts, enabling better integration with ID Protection for detecting credentials that have been exposed in breaches.

Does Pass-through authentication require password synchronization?

No, Pass-through authentication does not synchronize passwords. It forwards authentication requests to on-premises servers for validation, keeping passwords secure within the local network.

More MS-102 FAQ →

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 2 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 2

  1. n_mehr69 👍 2 Answered B
    correct
  2. Nick_UNO 👍 1 Answered B
    B is correct

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Practice All MS-102 Questions

Access 111 questions with complete answers and detailed explanations.

View Full MS-102 Practice Test →

← Back to MS-102 Study Guide