New-MgUser command fails with "A password must be specified to create a new user"

[sofbkeller]

Describe the bug

I am trying to create a new user using Microsoft Graph. This was working in versions prior to 2.25 unfortunately I didn't take note of the working module version before removing it.
When I attempt to create a new user I get: New-MgUser_CreateExpanded: A password must be specified to create a new user.

Expected behavior

User is created successfully. It was working previously but when I passed the script to a new colleague, they said it didn't work. Updating to the latest version of Microsoft.Graph broke it for me as well.

How to reproduce

New-MgUser -AccountEnabled -DisplayName "John_doe" -GivenName "John" -Surname "Doe" -UserPrincipalName "John_Doe@domain.com" -MailNickname "John_Doe" -OfficeLocation "123456" -PasswordProfile @{Password="BananaSam1234!!"; ForceChangePasswordNextSignIn=$true}

SDK Version

2.27.0

Latest version known to work for scenario above?

No response

Known Workarounds

Unknown

Debug output

Click to expand log

```

VERBOSE: Performing the operation "New-MgUser_CreateExpanded" on target "Call remote 'POST /users' operation".
New-MgUser_CreateExpanded: A password must be specified to create a new user.

Status: 400 (BadRequest)
ErrorCode: Request_BadRequest
Date: 2025-05-02T23:11:03

Headers:
Cache-Control : no-cache
Vary : Accept-Encoding
Strict-Transport-Security : max-age=31536000
request-id : 45d21c5d-e766-4b39-8e31-80c7658524a8
client-request-id : d6f206f9-71f8-4728-a24b-c7ab0591a0c0
x-ms-ags-diagnostic : {"ServerInfo":{"DataCenter":"West US 2","Slice":"E","Ring":"4","ScaleUnit":"005","RoleInstance":"MWH0EPF0009A7D1"}}
x-ms-resource-unit : 1
Date : Fri, 02 May 2025 23:11:03 GMT

</details>


### Configuration

- OS: Windows 11 Enterprise 24H2
-Powershell Version:

Name                           Value
----                           -----
PSVersion                      7.4.7
PSEdition                      Core
GitCommitId                    7.4.7
OS                             Microsoft Windows 10.0.26100
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0


-Module:
get-installedmodule | where {$_.Name -like "Microsoft.Graph"}

Version              Name                                Repository           Description
-------              ----                                ----------           -----------
2.19.0               Microsoft.Graph                     PSGallery            Microsoft Graph PowerShell module

### Other information

_No response_

[12Knocksinna]

Did you run with Debug to verify that all the expected parameter values are being passed to the Graph request?

[offprem-cloud]

Having same issue here..

@12Knocksinna - running with debug I can see it seems to be stripping out the password

Still able to use REST to create user

$headers = @{
    "Authorization" = "Bearer $AccessToken"
    "Content-Type" = "application/json"
}

$body = @{
    accountEnabled = $true
    displayName = "Example User"
    givenName = "Example"
    mailNickname = "Example_User"
    passwordPolicies = "DisablePasswordExpiration"
    passwordProfile = @{
        forceChangePasswordNextSignIn = $false
        password = "$ExamplePassword"
    }
    surname = "User"
    userPrincipalName = "example_user@domain.onmicrosoft.com"
    userType = "Member"
} | ConvertTo-Json

Invoke-RestMethod -Method Post -Uri "https://graph.microsoft.com/v1.0/users" -Headers $headers -Body $body

[12Knocksinna]

OK, so it's the same bug as has been reported several times with SDK V2.27 cmdlets stripping properties from payloads.

The workarounds are to revert to V2.25, use the bodyparameter parameter to pass the payload, or use a Graph request.

[sofbkeller]

Understood - I had only tried the body param against the password property specifically. I will give it a go against the whole command.
I tried rolling back to v2.25 with a fresh environment and it didn't seem to result in success but something else could have been going on.

[timayabi2020]

Please update to the latest SDK (2.28.0)