Updating Job Title failing due to commas in the titles

dannig178 · 2021-10-12T14:43:30.000Z

I have a script I developed with help here last week to update fields in Azure AD off of PS script. It works beautifully, except in cases where the user has a comma in the job title.

A example would be if a user has a job title like - “New, Job Title”

My output then says “WARNING user@domain.com;New Department;New, Job Title not found, skipped”

My script:

Connect to AzureAD

Connect-AzureAD

Get CSV content

$CSVrecords = Import-Csv C:\temp\test.csv -Delimiter “;”

Create arrays for skipped and failed users

$SkippedUsers = @()
$FailedUsers = @()

Loop trough CSV records

foreach ($CSVrecord in $CSVrecords) {
$upn = $CSVrecord.UserPrincipalName
$user = Get-AzureADUser -Filter “userPrincipalName eq ‘$upn’”
if ($user) {
try{
$user | Set-AzureADUser -Department $CSVrecord.Department -JobTitle $CSVrecord.jobTitle
} catch {
$FailedUsers += $upn
Write-Warning “$upn user found, but FAILED to update.”
}
}
else {
Write-Warning “$upn not found, skipped”
$SkippedUsers += $upn
}
}

Array skipped users

$SkippedUsers

Array failed users

$FailedUsers

Neally · 2021-10-12T17:57:19.000Z

If you post code, please use the ‘Insert Code’ button. Please and thank you!

PLEASE READ BEFORE POSTING! Read if you're new to the PowerShell forum! Programming & Development

Hi, and welcome to the PowerShell forum! Don’t apologize for being a “noob” or “newbie” or “n00b.” There’s just no need – nobody will think you’re stupid, and the forums are all about asking questions. Just ask! Use a descriptive subject. Don't say "Need help" or "PowerShell Help", actually summarize what the problem is. It helps the rest of us keep track of which problem is which. Don’t post massive scripts. We’re all volunteers and we don’t have time to read all that, nor will we copy, past…

192033ab-bb8f-4032-88a5-8e2313af0344-codebutton_small.png

Neally Bot

Evan7191 · 2021-10-12T18:02:12.000Z

Can you post a sanitized sample of what your CSV file looks like, including the header?

dereks · 2021-10-12T18:04:02.000Z

I don’t have Azure AD here but, based on the code and the error, that makes no sense that it would be based off the job title having a comma.
What I’d suggest though is curating your CSV file to only a couple test accounts. 1 that you know works and 1 that you know fails. Using powershell ISE, set some breakpoints and do a check to make sure exactly where it is failing and that the data is coming in as expected.
Without knowing how you are getting the CSV file I did my own small scale test. Created a CSV with the 3 fields. Had JobTitle with a comma in it then manually edited the file to put the semi-colon delimiter which meant the job title that had the comma was in quotes. When I checked the CSVrecord.JobTitle it had no issue with the comma there.

jitensh · 2021-10-12T18:11:35.000Z

if you have, commas at job title then put in under quotation

like

job title
"new Job, Title"

dannig178 · 2021-10-12T18:12:17.000Z

@techadmin8

The first two rows of my csv:

userPrincipalName;department;jobTitle

first.last@domain.com;User Department;VP, Marketing

Thank you!

jimlong3 · 2021-10-12T18:16:18.000Z

You say this is working?

$user = Get-AzureADUser -Filter "userPrincipalName eq '$upn'"

??

Normally, the comparison operator has a ‘-’ in front of it, and you don’t put apostrophes around your $string variable names. Also, I’ve found the -Filter parameters seem to work better in curly braces. I would think that line should look like this:

$user = Get-AzureADUser -Filter {userPrincipalName -eq $upn}

But that’s beside the point. Which line gives you the error you showed?

I went and put a ‘,’ in my own Job Title & I can’t get it to fail. It also lets me set the Job Title with or without a ‘,’. Not using Azure, so the Root Cause could be in those cmdlets…

Neally · 2021-10-12T18:20:05.000Z

Normally, the comparison operator has a ‘-’ in front of it

A lot of azure stuff does not follow the convention…

learn.microsoft.com

Get-AzureADUser (AzureAD)

The Get-AzureADUser cmdlet gets a user from the Microsoft Entra ID.

1f988a26-6197-48e4-ac24-5255f60fd76f-2021-10-12_13-19-37.png

dannig178 · 2021-10-12T18:21:49.000Z

@jitensh

That changed my error message but otherwise did not work:

WARNING: first.last@domain.com;Department;“VP, Marketing” not found, skipped

dannig178 · 2021-10-12T18:29:58.000Z

@jimlong3

The output error does not list a line that it occurred on.

jimlong3 · 2021-10-12T18:31:45.000Z

Neally:

A lot of azure stuff does not follow the convention…

OMG. Why am I not surprised.

Hyphens? We ain’t got no hyphens. We don’t need no hyphens! We don’t have to show you any stinking hyphens!
~ Treasure of the Sierra Modules

Neally · 2021-10-12T18:34:42.000Z

Dannig178:

The output error does not list a line that it occurred on.

As Evan said, please provide a (sanitized) sample what you CSV looks like.

dannig178 · 2021-10-12T18:37:15.000Z

I got the issue resolved.

I saved the csv file with the user’s information in separate columns and removed the line in the input - -Delimiter “;”

It now works like a charm regardless of the input data listed in the sheet.

Thank you for all of the troubleshooting tips, very appreciated!

jimlong3 · 2021-10-12T18:38:01.000Z

Dannig178:

The output error does not list a line that it occurred on.

That means it’s coming from the Else{} in the

if ($user) {

block.

That means we’re back to

$user = Get-AzureADUser -Filter "userPrincipalName eq '$upn'"

So… Right after that line, you can temporarily add this to see what you’re working with:

Read-Host "User is $user"

or:

$user | FL *
Read-Host "Get that?"

to see your Root Cause.

Neally · 2021-10-12T18:41:34.000Z

Dannig178:

input - -Delimiter “;”

that means it’s not a valid CSV. Sure you can ‘fix’ it by adding the delimiter parameter, but I’d suggest to stick as close as possible to a valid CSV file.

CSV - comma separated values

IETF Datatracker

RFC 4180: Common Format and MIME Type for Comma-Separated Values (CSV) Files

This RFC documents the format used for Comma-Separated Values (CSV) files and registers the associated MIME type "text/csv". This memo provides information for the Internet community.

Evan7191 · 2021-10-12T18:51:36.000Z

Jim6795:

Dannig178:

The output error does not list a line that it occurred on.

That means it’s coming from the Else{} in the
if ($user) {
block.

It’s not an error message. It is a warning message from Set-AzureADUser. Warning messages do not list line numbers.

gary-m-g · 2021-10-13T16:25:38.000Z

So many standards to choose from.

jimlong3 · 2021-10-19T18:01:06.000Z

Evan7191:

It’s not an error message. It is a warning message from Set-AzureADUser. Warning messages do not list line numbers.

#[...]
 else {
        Write-Warning "$upn not found, skipped"
        $SkippedUsers += $upn
    }
#[...]

If $upn has junk in it (like " user@domain.com;New Department;New, Job Title "), that would give this message:

My output then says "WARNING user@domain.com;New Department;New, Job Title not found, skipped"

¯_(ツ)_/¯