Microsoft.Graph PowerShell needs updating for vital bug fix

[chris5287]

Description

The Microsoft.Graph PowerShell module has a bug introduced in 2.250.0 that impacts a lot of the commands that take a payload with slashes in). This has now been fixed in 2.26.1

microsoftgraph/msgraph-sdk-powershell#3154

Can a new image be release that pins to 2.26.1 or later?

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 20.04
• Ubuntu 22.04
• Ubuntu 24.04
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025

Image version and build link

20250224.5.0

Is it regression?

20250120.2.0

Expected behavior

Microsoft.Graph PowerShell commands work as before

Actual behavior

Microsoft.Graph PowerShell commands fail with weird error messges (eg: New-MgGroup when specifying an owner errors out with Invalid URL format specified in @odata.bind for owners)

Repro steps

Create a pipeline that invokes the following PowerShell command, with < 2.26.1 module it fails. >= 2.26.1 has this fixed.

$params = @{
    description = 'Group description'
    displayName = 'group1'
    groupTypes = @()
    mailEnabled = $false
    mailNickname = '00000000-0000-0000-0000-000000000000'
    securityEnabled = $true
    'owners@odata.bind' = [
        'https://graph.microsoft.com/v1.0/users/00000000-0000-0000-0000-000000000000'
    ]
}

New-MgGroup -BodyParameter $params

[hemanthmanga]

Hi @chris5287, Thank you for bringing this issue to our attention. We are looking into this issue and will update you on this issue after investigating.

[matsest]

Same issue here - workaround is to either force an update or install the previous (2.25.0) version in our pipeline.

Looks like it will be fixed by #11719

[hemanthmanga]

Hi @chris5287, The latest Windows-2022 image has been rolled out, and the Microsoft.Graph PowerShell version has been updated to 2.26.1. Kindly use the latest image to resolve the issue. We are closing this issue. Thank you.