Bulk user operations from CSV in PowerShell - Step-by-Step Execution

Concept Flow - Bulk user operations from CSV

Start

↓

Import CSV file

↓

For each user in CSV

↓

Perform user operation

↓

Log success or error

↓

All users processed?

No→Next user

Yes↓

End

The script starts by loading user data from a CSV file, then loops through each user to perform the desired operation, logging results until all users are processed.

Execution Sample

PowerShell

Import-Csv users.csv | ForEach-Object {
  New-ADUser -Name $_.Name -SamAccountName $_.Username -AccountPassword (ConvertTo-SecureString $_.Password -AsPlainText -Force) -Enabled $true
  Write-Host "Created user: $($_.Name)"
}

This script reads users from a CSV and creates an Active Directory user for each, then prints confirmation.

Execution Table

Step	Action	User Data	Command Executed	Output
1	Import CSV	Loaded 3 users	N/A	N/A
2	Process user 1	{Name: Alice, Username: alice1, Password: pass123}	New-ADUser -Name Alice -SamAccountName alice1 ...	Created user: Alice
3	Process user 2	{Name: Bob, Username: bob2, Password: pass456}	New-ADUser -Name Bob -SamAccountName bob2 ...	Created user: Bob
4	Process user 3	{Name: Carol, Username: carol3, Password: pass789}	New-ADUser -Name Carol -SamAccountName carol3 ...	Created user: Carol
5	All users processed	N/A	N/A	Script completed successfully

💡 All users from CSV processed, script ends.

Variable Tracker

Variable	Start	After User 1	After User 2	After User 3	Final
$_	null	{Name: Alice, Username: alice1, Password: pass123}	{Name: Bob, Username: bob2, Password: pass456}	{Name: Carol, Username: carol3, Password: pass789}	null
Output	empty	Created user: Alice	Created user: Bob	Created user: Carol	Script completed successfully

Key Moments - 3 Insights

Why do we use $_ inside the ForEach-Object loop?

The $_ variable holds the current user object from the CSV during each loop iteration, as shown in execution_table rows 2-4.

What happens if the CSV file is empty?

The script imports zero users, so the loop does not run, and the script ends immediately (see execution_table row 5).

How does the script handle passwords securely?

Passwords are converted to secure strings using ConvertTo-SecureString before being passed to New-ADUser, ensuring they are not plain text in memory.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of $_ after processing the second user?

A {Name: Carol, Username: carol3, Password: pass789}

B {Name: Bob, Username: bob2, Password: pass456}

C {Name: Alice, Username: alice1, Password: pass123}

D null

💡 Hint

Check variable_tracker row for $_ after User 2

At which step does the script confirm all users are processed?

A Step 2

B Step 3

C Step 5

D Step 4

💡 Hint

Look at execution_table where output says 'Script completed successfully'

If the CSV had 5 users instead of 3, how would the execution table change?

A There would be 7 rows instead of 5, with two more user processing steps

B The script would stop after 3 users anyway

C The output column would be empty for extra users

D The script would fail immediately

💡 Hint

Each user adds one processing step row in execution_table

Concept Snapshot

Bulk user operations from CSV:
- Use Import-Csv to load user data
- Loop with ForEach-Object over each user
- Use $_ to access current user
- Perform user operation (e.g., New-ADUser)
- Log success or errors
- Script ends after all users processed

Full Transcript

This script starts by importing user data from a CSV file. It then loops through each user using ForEach-Object. Inside the loop, the current user is accessed with $_. For each user, a command like New-ADUser is run to create the user account. After each creation, a confirmation message is printed. Once all users are processed, the script ends. Variables like $_ change with each iteration, holding the current user data. The script handles passwords securely by converting them to secure strings before use. If the CSV is empty, the loop does not run and the script ends immediately.