Az.ResourceGraph 1.2.0 cannot run search-AzGraph against China cloud (mooncake)

[yangchengs]

Description

I installed az module 13.4 along with Az.ResourceGraph 1.2.0, it has error to run search-AzGraph against China cloud.

If I override the Az.ResourceGraph to 1.0.0 and it works fine

Issue script & Debug output

Search-AzGraph: {
  "error": {
    "code": "InvalidResourceType",
    "message": "The resource type 'resources' could not be found in the namespace 'Microsoft.ResourceGraph' for api version '2024-04-01'. The supported api-versions are '2018-09-01-preview,2019-04-01,2021-03-01,2021-06-01-preview,2022-10-01'."
  }
}

Environment data

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

Module versions

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Script     4.1.0                 Az.Accounts                         {Add-AzEnvironment, Clear-AzConfig, Clear-AzConte…
Script     1.2.0                 Az.ResourceGraph                    {Search-AzGraph, Get-AzResourceGraphQuery, New-Az

Error output

[isra-fel]

Hi @yangchengs thanks for the feedback. The api version of azure powershell modules are usually aligned with public cloud. And because soverign clouds are sometimes behind public cloud in the sense of deployment, it may be the case that you need to use a previous version to get it work.

I'll loop in resource graph team to get their ideas.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @venu-l.

[hwwilliams]

I get the same error in US gov cloud