Get-MgIdentityGovernanceAccessReviewDefinition -Search

[insomniacc]

Microsoft.Graph.Identity.Governance 2.8.0

First time using this module, but I've used Users and Groups plenty.

Get-MgIdentityGovernanceAccessReviewDefinition -Search "Displayname:stringToSearch"

The -Search parameter does not appear to be functiona and the the response is always:

Get-MgIdentityGovernanceAccessReviewDefinition_List: The query parameter '$search' is not supported.
Status: 400 (BadRequest)

[timayabi2020]

@insomniacc the command you are running translates to this http request https://graph.microsoft.com/v1.0/identityGovernance/accessReviews/definitions?$search="DisplayName:stringToSearch" which has a $search query parameter and it's not supported by the API. You will get an API response similar to the screen shot below if you put a -Debug option at the end of the command.

Please use this Get-MgIdentityGovernanceAccessReviewDefinition -Filter "DisplayName eq 'stringToSearch'" as an alternative.

[insomniacc]

@timayabi2020 - The reason that I was using the search parameter is because this would typically automatically wildcard my search.

So for example, if I had multiple access review definitions with the name 'prefix something suffix'
I could run a search across 'something' to fine all the associated items.

I'm not sure how I can accomplish this using -filter, since the following:

Get-MgIdentityGovernanceAccessReviewDefinition -Filter "contains(DisplayName,'something')" 

also does not work.

Regardless though, if -Search is not supported, it should not be presented as a parameter on the function.

[timayabi2020]

@insomniacc - Thank you for further clarification on the usage of the command. Unfortunately for such service issues, we may not be best placed to resolve it. I would therefore recommend that you to open an issue here https://developer.microsoft.com/en-us/graph/support and the service/API owner will action on it.

[insomniacc]

I'll be honest, I'm failing to understand how it's a service issue and not a build issue with the module or underlying dependencies (in which case I would have thought this is the correct channel to raise issue so that it can be internally be routed to the right team). It's a fundamental problem with the module that there's parameters which are effectively broken and cannot be used, but they are being provided as functionality - this should be tracked in this repo in my opinion, especially considering it's the first place other individuals will come looking for the same issue/answer as it's PowerShell module specific.

If it's not currently a feature, the module should be updated and the parameter should be removed.
If it should exist as a feature I would expect this issue to remain open and the relevant parties to be contacted to make them aware there's an issue with consistency and a standard is not being maintained, so that it can be rectified and tracked in line with the modules that are expecting to support it.

[timayabi2020]

@insomniacc if we revisit my first response to this issue, it shows how the command execution translates to a http request made to the API responsible for processing and availing data to a user. This means that you can copy the request and run it against a command like Invoke-MgGraphRequest -Uri <paste url here> and you will still get the same result. You can also make use of this tool https://developer.microsoft.com/en-us/graph/graph-explorer to directly run http requests against graph just to confirm that you are dealing with an issue that is not unique to the sdk.

Having said that, kindly note that cmdlets generation/builds are driven by openAPI specifications defined by the API/Service owner. In this case the search parameter is defined in the specification (See image below) and so the cmdlet will be generated with that parameter and the expectation is that it should be working. This clearly points to API functionality which I am not best placed to answer hence the request for you to log that issue with graph support team (https://developer.microsoft.com/en-us/graph/support).
NB. This repository is intended for issues related to the functionality of the module (bugs and feature requests)
Also have a look at https://learn.microsoft.com/en-us/powershell/microsoftgraph/troubleshooting?view=graph-powershell-1.0#using--debug for more troubleshooting pointers.