Question 10
Your tenant currently has only contoso.onmicrosoft.com as a verified user-principal-name suffix. A developer asks to create lee@newbrand.example as a member UPN, but newbrand.example has not been verified in your tenant. What should you do first?
Explanation
Correct Answer
A Microsoft Entra user's UPN suffix must be a tenant-verified domain or an eligible existing tenant suffix. Adding a custom domain to the tenant requires a supported ownership-verification process before it can be used for normal member UPNs. Verify the new domain first, then create or update the user with the intended UPN. Using the already verified onmicrosoft.com suffix is a temporary alternative that creates an actual valid user without asserting ownership of an unverified company domain.
Incorrect Answers
An unverified custom UPN suffix is not usable merely because the developer supplied an address. The directory must ensure that the tenant has ownership of the sign-in domain before assigning it to managed users. Ignoring a validation failure would not create a reliable user object with the requested sign-in name and may encourage an incorrect workaround. Domain verification is a tenant identity-domain operation, not an Azure networking or resource-management privilege grant.
Azure subscription Contributor controls resource management operations at an Azure scope. It cannot prove ownership of an external DNS domain to Microsoft Entra, and it does not grant the necessary directory custom-domain verification permissions. The desired UPN requires a tenant identity-domain operation rather than broader Azure resource-management access.
An Azure Private DNS zone serves private name resolution for linked virtual networks, not public domain ownership verification for Microsoft Entra identities. Creating such a zone does not prove possession of the company's public domain records. The administrator must complete the supported tenant domain verification workflow or choose a verified suffix.