Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microsoft.Graph PowerShell needs updating for vital bug fix #11702

Open
2 of 15 tasks
chris5287 opened this issue Mar 2, 2025 · 2 comments
Open
2 of 15 tasks

Microsoft.Graph PowerShell needs updating for vital bug fix #11702

chris5287 opened this issue Mar 2, 2025 · 2 comments
Assignees
Labels
awaiting-deployment Code complete; awaiting deployment and/or deployment in progress bug report OS: Windows

Comments

@chris5287
Copy link

chris5287 commented Mar 2, 2025

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
    '[email protected]' = [
        'https://graph.microsoft.com/v1.0/users/00000000-0000-0000-0000-000000000000'
    ]
}

New-MgGroup -BodyParameter $params
@hemanthmanga
Copy link
Contributor

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
Copy link

matsest commented Mar 6, 2025

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 hemanthmanga added the awaiting-deployment Code complete; awaiting deployment and/or deployment in progress label Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-deployment Code complete; awaiting deployment and/or deployment in progress bug report OS: Windows
Projects
None yet
Development

No branches or pull requests

3 participants