Tim

Hi @gavinbarron I checked, and most cmdlets now exist under different modules. The module mapping is based on the tags gotten from the metadata. We are also working to update...

@irvinesunday I've responded on the main issue. However, we can continue with this thread over here since it's an internal issue. On the latest metadata pull we have ``users.GetPhotos`` and...

@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...

@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...

@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...

Hi @uta-sheppardpj I wasn't able to reproduce your issue. However, I think you are experiencing module conflicts. Please uninstall all graph versions, manually delete module folders from the module installation...

@MSFT-klpinhac I think your issue will be best resolved/answered by the API owner. Kindly raise an issue here https://developer.microsoft.com/en-us/graph/support so that the API owner can respond to it.

@TWells94 thank you for logging this issue. Please use ``Invoke-MgGraphRequest`` cmdlet and let us know if you are still having the same experience. Please use the sample request below. Maybe...

@TWells94 is it possible to switch to a different network environment and execute the request?

Hi @TWells94 apologies for that experience. At this point, this now seems to be a service issue and unfortunately for API related issues/questions we are not best placed to give...