It might just be that UserId is a mandatory parameter… Does the same error occur for other parameters?

I did this:

$Params = @{}
$Params.Add(“JobTitle”, “Road Sweeper”)
$Params.Add(“OfficeLocation”, “Paris”)
Update-MgUser -UserId Rene.Artois@Office365itpros.com -Office “Nouvon” -JobTitle “Chief” @Params

Get-MgUser -userid Rene.Artois@Office365itpros.com -Property Id, OfficeLocation, JobTitle | Select OfficeLocation, JobTitle

OfficeLocation JobTitle
————– ——–
Nouvon Chief

As you can see, the explicit parameters took precedence over those in the hash table. But this is PowerShell 7.4.2.

Who knows what might happen elsewhere…

https://mikefrobbins.com/2023/10/19/automatically-convert-a-powershell-command-to-use-splatting/

One thing I’ve noticed is that the following doesn’t seem to be true for me in PowerShell version 5.1:

“PowerShell applies the values for the parameters in the hash table except where a parameter value is explicitly passed.”

If I run this (somewhat silly) example:

$getMgUserSplat = @{
UserId = ‘user1@company.com’
Property = ‘Id’, ‘UserPrincipalName’, ‘mySite’
}
$user1 = Get-MgUser @getMgUserSplat
$user2 = Get-MgUser @getMgUserSplat -UserId ‘user2@company.com’

I get the following error on that second Get-MgUser:

Get-MgUser : Cannot bind parameter because parameter ‘UserId’ is specified more than once. To provide multiple values to parameters that can accept multiple values, use the array syntax. For example, “-parameter value1,value2,value3”.

When this comes up, I just replace the value in the hash table before running the second instance of the command:

$user1 = Get-MgUser @getMgUserSplat
$getMgUserSplat.UserId = ‘user2@company.com’
$user2 = Get-MgUser @getMgUserSplat

or, limit the hash table to only the “static” parameters and pass the variable parameters explicitly:

$getMgUserSplat = @{
Property = ‘Id’, ‘UserPrincipalName’, ‘mySite’
}
$user1 = Get-MgUser @getMgUserSplat -UserId ‘user1@company.com’
$user2 = Get-MgUser @getMgUserSplat -UserId ‘user2@company.com’

I know. But I like constructing hash tables in this manner. It just seems more logical and easier to do when building hash tables programmatically.

$Body = @{
Office = “Galway”
Department = “Business Development”
}

Update-MgUser -UserId $UserId @Body