Question 43 — AB-650 Case Study Set
Given that the system must place Paideffort's external vendors in the organizational address book without creating sign-in accounts, which implementation should the identity architecture team choose? (Select one answer)
Process the vendors with
New-MailContactin Exchange Online PowerShell instead of creating Microsoft Entra users withNew-MgUser.Create disabled Microsoft Entra users with
New-MgUserand store each vendor's external address as the user principal name.Create the vendors with
New-MgUserunderUser.ReadWrite.Alland remove their passwords immediately afterward.Create ordinary users through Microsoft Graph and then convert those user objects to mail contacts through
Update-MgUser.
Correct answers
Process the vendors with
New-MailContactin Exchange Online PowerShell instead of creating Microsoft Entra users withNew-MgUser.
Explanations
Correct Answer:
Process the vendors with New-MailContact in Exchange Online PowerShell instead of creating Microsoft Entra users with New-MgUser.
Explanation:
Paideffort's 40 vendors need address-book representation but must never become sign-in identities. They therefore belong to the mail-contact management boundary rather than the Microsoft Graph user-provisioning workflow. New-MailContact in Exchange Online PowerShell creates the correct type of object.
Wrong Answers:
Create disabled Microsoft Entra users with New-MgUser and store each vendor's external address as the user principal name.
This still creates user objects for people whom Paideffort requires to exist only as external mail contacts. Disabling sign-in does not make the object a mail contact.
Create the vendors with New-MgUser under User.ReadWrite.All and remove their passwords immediately afterward.
Removing passwords does not change the object type. Paideffort would still be provisioning Microsoft Entra users instead of Exchange Online mail contacts.
Create ordinary users through Microsoft Graph and then convert those user objects to mail contacts through Update-MgUser.
Update-MgUser modifies user properties; it does not provide Paideffort with a conversion path from a Microsoft Entra user object to an Exchange mail contact.