You have a Microsoft Entra tenant named contoso.onmicrosoft.com and an Azure subscription named Sub1. You need to implement Microsoft Entra Verified ID by using Quick Verified ID setup. What should…

Question

Options

• Aa security principal in contoso.onmicrosoft.com
• Ba custom domain in contoso.onmicrosoft.com
• Ca user-assigned managed identity in Sub1
• Dan Azure key vault in Sub1

• B
  86% (19)
• C
  5% (1)
• D
  9% (2)

Explanation

Microsoft Entra Verified ID uses Decentralized Identifiers (DIDs) to establish a trusted identity for the issuing organization. The Quick Verified ID setup (the simplified onboarding path) automatically provisions the key vault, storage, and service configuration - but it derives the DID from a verified custom domain associated with the tenant. Without a verified custom domain in the tenant (e.g., contoso.com instead of just contoso.onmicrosoft.com), the Quick setup cannot link the DID to a domain that you control and can publish in a DID document. Therefore, the first prerequisite is adding and verifying a custom domain in the Microsoft Entra tenant. A security principal (A) is not a setup prerequisite. A user-assigned managed identity (C) is not required. An Azure Key Vault (D) is used by Verified ID for key management, but Quick setup creates and configures this automatically - you do not need to create it manually first.

No community discussion yet for this question.