Question 39 — AB-650 Case Study Set
Business Context
Paideffort is opening a new international office with 60 employees. Human Resources delivers onboarding and department-change files as CSV exports, and the identity team must process each batch before the employees' first working day. The same automation will be reused for future hiring waves expected to exceed 300 accounts per quarter. Security governance requires each administrative script to request only the Microsoft Graph permissions needed for its assigned operation rather than using broad directory-wide permissions for convenience.
The onboarding workflow must create enabled Microsoft Entra user accounts with temporary passwords and force each employee to change the password at first sign-in. A separate audit workflow must export complete user profiles without changing directory objects. Group administrators must add selected new hires to the Overseas-Office group, while identity architects must create an administrative unit for delegated management of the new office.
Current Automation
The identity engineering team prepared the following PowerShell provisioning script:
Connect-MgGraph -Scopes "Directory.ReadWrite.All"
$newHires = Import-Csv -Path "C:\Paideffort\overseas-hires.csv"
foreach ($hire in $newHires) {
New-MgUser -DisplayName $hire.DisplayName `
-UserPrincipalName $hire.UserPrincipalName `
-AccountEnabled `
-PasswordProfile @{
Password = $hire.TempPassword
ForceChangePasswordNextSignIn = $true
}
}
Each CSV row contains the following data:
[
{
"DisplayName": "Daniel Owusu",
"UserPrincipalName": "daniel.owusu@paideffort.com",
"MailNickname": "daniel.owusu",
"TempPassword": "Temporary-Value-01",
"Department": "Operations"
}
]
Additional Identity Workflows
The quarterly audit job runs Get-MgUser to export full user information and is prohibited from making directory changes. The department-maintenance job uses Update-MgUser to apply values from department-updates.csv. The offboarding process uses Remove-MgUser for approved account deletions.
Eight new employees must also become members of the Overseas-Office security group. The current implementation reconnects to Microsoft Graph inside the loop before adding every individual member by using New-MgGroupMemberByRef.
A dedicated administrative unit named Overseas Operations must be created so regional administration can later be scoped to that organizational segment.
Paideffort records the intended permission model in YAML:
workflows:
userProvisioning:
operation: create-update-delete-users
scope: User.ReadWrite.All
quarterlyAudit:
operation: export-users
scope: User.Read.All
officeMembership:
operation: modify-group-membership
scope: GroupMember.ReadWrite.All
regionalDelegation:
operation: manage-administrative-units
scope: AdministrativeUnit.ReadWrite.All
Procurement also supplies 40 external vendor contacts that must appear in Paideffort's address book. These people are not employees, must never sign in to Microsoft Entra ID, and already have external email addresses at their own organizations. An engineer has proposed adding them to the same onboarding CSV and processing them through New-MgUser.
Future Requirements
Paideffort wants every batch operation to remain repeatable, auditable, and suitable for larger hiring waves. Scripts must avoid unnecessary interactive reconnections, separate read-only operations from write operations, and preserve least privilege as new workflows are added. Operations teams also want failed rows logged independently so a single invalid employee record does not require administrators to recreate the entire batch manually.