Set-MgUserLicense Error message

Thank you for the testing, reporting back, and sharing your possible work arounds. Hopefully the confirmation of the issue might inspire someone to fix the regression and allow the usage of Set-MgUserLicense without going back to an older version or coming up with custom workarounds.

Excellent fix for the issue. I've added it to my library of replacement cmdlets for when something gets broken.

$lic_fabric = Set-MgUserLicense -UserId $upn -AddLicenses @{SkuId = $fabric_sku.SkuId} -RemoveLicenses @()

Set-MgUserLicense : One or more parameters of the operation 'assignLicense' are missing from the request payload. The missing parameters are: removeLicenses.

I have this line in a script that I had been using for a good while without issue. Recently upgraded the module to 2.26.1 and started getting an error. It seems like an issue has been reported https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/3213 about this bug.

I am also facing the same issue

And I am running the command with -RemoveLicenses @(), still its throwing the same erroor

Set-MgUserLicense -Userd $user.Id -AddLicenses @{SkuId = 'XXXX'} -RemoveLicenses @()

Veersh - what version of Microsoft Graph do have installed?

Latest Version 2.26.1

Hey everyone,

I recently ran into this same Set-MgUserLicense issue where attempting to remove a license resulted in the error:

"One or more parameters of the operation 'assignLicense' are missing from the request payload. The missing parameters are: removeLicenses."

After extensive testing, I found that even when explicitly passing -RemoveLicenses, the cmdlet would still fail unless an empty array was also included for -AddLicenses. However, I was able to bypass this bug entirely by using a direct JSON API call via Invoke-MgGraphRequest instead of Set-MgUserLicense.

Working Solution (Removes Licenses Successfully)

Instead of

powershell
CopyEdit
Function Remove-UserLicense {
    param (
        [string]$UserEmail
    )

    # Get User ID from Microsoft Graph
    $UserId = (Get-MgUser -Filter "UserPrincipalName eq '$UserEmail'").Id

    if (-not $UserId) {
        Write-Host "Error: User $UserEmail not found in Microsoft Graph." -ForegroundColor Red
        return
    }

    # Get all assigned licenses
    $licenses = Get-MgUserLicenseDetail -UserId $UserId | Select-Object -ExpandProperty SkuId

    if ($licenses.Count -eq 0) {
        Write-Host "No licenses found for $UserEmail." -ForegroundColor Yellow
        return
    }

    Write-Host "Attempting to remove licenses ($($licenses -join ', ')) from $UserEmail..." -ForegroundColor Cyan

    # Create JSON payload for license removal
    $jsonBody = @{
        addLicenses    = @()  # Must be explicitly empty
        removeLicenses = $licenses  # Remove all assigned licenses
    } | ConvertTo-Json -Depth 10

    try {
        # Send Graph API request to remove the licenses
        Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/v1.0/users/$UserId/assignLicense" -Body $jsonBody -ContentType "application/json"
        Write-Host "Successfully removed licenses ($($licenses -join ', ')) from $UserEmail" -ForegroundColor Green
    } catch {
        Write-Host "Failed to remove licenses from $UserEmail: $($_.Exception.Message)" -ForegroundColor Yellow
    }
}

Why This Works

• This method avoids Set-MgUserLicense entirely, which seems to be bugged for certain tenants.
• The Graph API requires both addLicenses and removeLicenses to be defined, even if one is empty.
• Passing an explicitly empty array for addLicenses resolves the issue.
• The JSON payload directly interacts with Microsoft Graph, ensuring the correct format.

Microsoft: Can We Get Clarification?

1. Is this Set-MgUserLicense behavior a confirmed bug, or is this expected?
2. Will there be an update to fix this behavior, or should JSON-based license removal be considered the best practice?
3. Why does Set-MgUserLicense fail even when the correct parameters are provided?

I hope this helps others dealing with this frustrating issue!