Skip to content

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

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

Open
yangchengs opened this issue Apr 3, 2025 · 2 comments
Labels
customer-reported feature-request This issue requires a new behavior in the product in order be resolved. Resource Graph Service Attention This issue is responsible by Azure service team.

Comments

@yangchengs
Copy link

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

@yangchengs yangchengs added bug This issue requires a change to an existing behavior in the product in order to be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Apr 3, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported needs-triage This is a new issue that needs to be triaged to the appropriate team. and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Apr 3, 2025
@isra-fel
Copy link
Member

isra-fel commented Apr 8, 2025

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.

@isra-fel isra-fel closed this as completed Apr 8, 2025
@isra-fel isra-fel removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Apr 8, 2025
@isra-fel isra-fel reopened this Apr 8, 2025
@isra-fel isra-fel added feature-request This issue requires a new behavior in the product in order be resolved. Service Attention This issue is responsible by Azure service team. Resource Graph and removed bug This issue requires a change to an existing behavior in the product in order to be resolved. labels Apr 8, 2025
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported feature-request This issue requires a new behavior in the product in order be resolved. Resource Graph Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants