Obsidian Systems is designing a hybrid identity and multi-tenant collaboration solution to integrate their on-premises Active Directory Domain Services (AD DS) forest, obsidian.local, with multiple Microsoft Entra ID tenants. The solution must adhere to strict authentication, provisioning, and business continuity requirements. Match each business requirement on the left to the most appropriate Microsoft Entra ID technology or configuration on the right.
- Evaluate on-premises account status and sign-in hours in real-time for cloud sign-ins without deploying Active Directory Federation Services (AD FS).Pass-through Authentication (PTA)
- Provide cloud authentication that continues working during on-premises network outages with the least amount of infrastructure overhead.Password Hash Synchronization (PHS)
- Automate user account provisioning and lifecycle management across multiple distinct internal Microsoft Entra ID tenants.Microsoft Entra Cross-Tenant Synchronization
- Enable users from an external vendor using a non-Azure identity provider to authenticate using their own credentials without manual guest invitations.SAML/WS-Fed Direct Federation
Answer
1 matches Pass-through Authentication (PTA), 2 matches Password Hash Synchronization (PHS), 3 matches Microsoft Entra Cross-Tenant Synchronization, and 4 matches SAML/WS-Fed Direct Federation.
Pass-through Authentication validates passwords on-premises in real-time to respect sign-in hours without AD FS. Password Hash Sync enables authentication to continue during local internet outages. Cross-Tenant Synchronization automates provisioning across internal Entra ID tenants. SAML/WS-Fed Direct Federation allows external users to authenticate using their non-Azure identity provider.
Step-by-Step Solution
Key Concept
Selecting appropriate Microsoft Entra ID hybrid identity and multi-tenant solutions based on security, availability, and provisioning constraints.
Estimated Time:2m 30s