microsoftgraph / microsoftgraph/msgraph-sdk-powershell

Get-MgIdentityGovernanceAccessReviewDefinitionInstance returns 500 error

Open
#3,540 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Service issue type:bug
Dominant language
C#
Stars
898
Forks
230
Avg merge
2d 5h
Merged PRs (30d)
31

Description

Describe the bug

When running this cmdlet

Get-MgIdentityGovernanceAccessReviewDefinitionInstance `
-AccessReviewScheduleDefinitionId $schedule.Id -Filter "Status eq 'InProgress'"

I get a 500 internal server error. When I switched to the Beta module to test, I also got a 500 error, but the error said that this call was deprecated. I switched my script to use the Invoke-MgFilterIdentityGovernanceAccessReviewDefinitionInstanceByCurrentUser cmdlet (as suggested by the API doco) everything started working again.

Should this cmdlet be working or not?

Expected behavior

command executes without error and returns a list of instances

How to reproduce
  1. Execute Get-MgIdentityGovernanceAccessReviewDefinitionInstance -AccessReviewScheduleDefinitionId $schedule.Id -Filter "Status eq 'InProgress'"
  2. See error
Get-MgIdentityGovernanceAccessReviewDefinitionInstance_List: An error has occurred.

Status: 500 (InternalServerError)
ErrorCode:
Date: 2026-02-23T23:56:26

Headers:
Vary                          : Accept-Encoding
Strict-Transport-Security     : max-age=31536000
request-id                    : abcb8795-48c2-4233-8b1e-61685e0a3148
client-request-id             : d1b37d8c-bfdf-4de2-b043-4114373bbe33
x-ms-ags-diagnostic           : {"ServerInfo":{"DataCenter":"Australia East","Slice":"E","Ring":"5","ScaleUnit":"002","RoleInstance":"SY2PEPF0000208C"}}
Date                          : Mon, 23 Feb 2026 23:56:25 GMT


  Recommendation: See service error codes: https://learn.microsoft.com/graph/errors
SDK Version

2.35.1

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output
Click to expand log ```

DEBUG: ============================ HTTP RESPONSE ============================

Status Code:
InternalServerError

Headers:
Vary : Accept-Encoding
Strict-Transport-Security : max-age=31536000
request-id : df8f9e31-2089-46c6-9b24-c2df899edb44
client-request-id : e6f438f5-9be9-496e-9b40-1d46b3b70d70
x-ms-ags-diagnostic : {"ServerInfo":{"DataCenter":"Australia East","Slice":"E","Ring":"5","ScaleUnit":"000","RoleInstance":"SY3PEPF0001CBA1"}}
Date : Tue, 24 Feb 2026 00:07:53 GMT

Body:
{
"error": {
"code": "",
"message": "An error has occurred.",
"innerError": {
"date": "2026-02-24T00:07:54",
"request-id": "df8f9e31-2089-46c6-9b24-c2df899edb44",
"client-request-id": "e6f438f5-9be9-496e-9b40-1d46b3b70d70"
}
}
}

</details>


### Configuration

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

### Other information

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Get-MgIdentityGovernanceAccessReviewDefinitionInstance command from the issue with SDK version 2.35.1, then compare its response with the beta module and the Invoke-MgFilterIdentityGovernanceAccessReviewDefinitionInstanceByCurrentUser workaround. Check whether the failure is in the cmdlet request or the service response; done means the supported behavior is confirmed and the issue has a fix or documented resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
api, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.