Question

Difficulty: MediumHybrid and Multi-Tenant Identity Solutions

Solas Renewable Solutions is designing a hybrid and multi-tenant identity solution to support its growing infrastructure. The company has an on-premises Active Directory Domain Services (AD DS) forest and has recently acquired a subsidiary with its own Microsoft Entra ID tenant.

Solas has the following identity and access management requirements:
- Ensure that users from the corporate office can sign in to Microsoft Entra ID services even if the on-premises datacenter goes offline.
- Enable automatic account lifecycle management and Global Address List (GAL) visibility for users from the acquired subsidiary's tenant.
- Allow external suppliers to securely access internal resources using their existing corporate credentials.
- Ensure that certain security-sensitive on-premises users have their login credentials validated in real-time against on-premises domain controllers, without storing password hashes in the cloud.

You need to recommend the appropriate identity technology for each requirement.

Match the identity requirements on the left with the correct Microsoft Entra feature or configuration on the right.

  • On-premises users must sign in to Microsoft Entra ID using their on-premises passwords. The authentication must be processed entirely in the cloud to ensure sign-in availability during an on-premises network outage.Password Hash Synchronization (PHS)
  • External partners must access corporate line-of-business applications. They must use their own corporate or social identities, and Solas must not manage their password resets or lifecycles.Microsoft Entra B2B collaboration
  • A newly acquired business unit with its own Microsoft Entra ID tenant must have its user accounts automatically provisioned and updated in the Solas corporate tenant to facilitate search in the global address list.Cross-tenant synchronization
  • User authentication requests must be validated in real-time against the on-premises Active Directory Domain Services (AD DS) using lightweight agents, without storing password hashes in the cloud.Pass-through Authentication (PTA)

Answer

Match the requirements as follows: cloud-resilient sign-in matches Password Hash Synchronization; automated tenant provisioning matches Cross-tenant synchronization; external contractor access matches Microsoft Entra B2B collaboration; real-time on-premises validation without cloud hashes matches Pass-through Authentication.
Matching cloud-resilient sign-in to Password Hash Synchronization (PHS) ensures authentication is processed entirely in the cloud. Matching automated tenant provisioning to Cross-tenant synchronization automates user creation between Microsoft Entra ID tenants. Matching external contractor access to Microsoft Entra B2B collaboration leverages external identities, and matching real-time local verification to Pass-through Authentication (PTA) prevents password hashes from being stored in the cloud.

Step-by-Step Solution

1
Analyze the requirement for on-premises user sign-in that remains functional during on-premises outages.
Password Hash Synchronization (PHS) is selected.
PHS copies password hashes to Microsoft Entra ID, allowing authentication to occur completely in the cloud, independent of on-premises connectivity.
2
Analyze the requirement to automate provisioning and Global Address List visibility between the corporate tenant and the acquired subsidiary's tenant.
Cross-tenant synchronization is selected.
Cross-tenant synchronization automates the creation, management, and deletion of B2B users between distinct Microsoft Entra ID tenants within the same organization.
3
Analyze the requirement to allow external suppliers to access internal resources using their own corporate credentials.
Microsoft Entra B2B collaboration is selected.
B2B collaboration allows external partners to access corporate apps while managing their own credentials, offloading management from Solas.
4
Analyze the requirement for real-time validation against on-premises domain controllers without storing password hashes in the cloud.
Pass-through Authentication (PTA) is selected.
PTA validates credentials in real-time using lightweight on-premises agents, meaning no password hashes are stored in the cloud.

Key Concept

Selecting appropriate Microsoft Entra hybrid and multi-tenant authentication and collaboration features based on organization resiliency, security, and governance requirements.
Rate this question