Valerius Logistics is designing a hybrid identity solution to integrate their on-premises Active Directory Domain Services (AD DS) forest, which contains 22,000 users, with a new Microsoft Entra ID tenant.
The design must satisfy the following constraints:
- Authentication: Users must sign in to cloud applications using their on-premises credentials.
- Business Continuity: Cloud authentication must remain functional if the on-premises datacenter experiences an internet connectivity outage.
- Self-Service: Users must be able to reset their expired passwords via the Azure portal, and the changes must immediately update on-premises AD DS.
- Governance: To prevent administrator lockout during a tenant-wide Conditional Access policy deployment, at least two emergency access (break-glass) accounts must be created and excluded from all Multi-Factor Authentication (MFA) policies.
Which solution should you recommend to meet these requirements with the lowest administrative and infrastructure overhead?
- AImplement Microsoft Entra Connect with Pass-through Authentication (PTA) and enable Password Writeback. Create two cloud-only emergency access accounts and exclude them from all Conditional Access multi-factor authentication (MFA) policies.
- BImplement Active Directory Federation Services (AD FS) and enable Password Writeback. Create two cloud-only emergency access accounts and exclude them from all Conditional Access multi-factor authentication (MFA) policies.
- Implement Microsoft Entra Connect with Password Hash Synchronization (PHS) and enable Password Writeback. Create two cloud-only emergency access accounts and exclude them from all Conditional Access multi-factor authentication (MFA) policies.Cevap
- DImplement Microsoft Entra Connect with Password Hash Synchronization (PHS) and enable Password Writeback. Create two cloud-only emergency access accounts and enforce multi-factor authentication (MFA) on all administrator accounts without exclusions.