Az.PolicyInsights 2.0.0 Get-AzPolicyRemediation at management-group scope sends api-version 2024-10-01 to Microsoft.Management/managementGroups (unsupported)

[Radosz86]

Description

Get-AzPolicyRemediation at management-group scope is broken in Az.PolicyInsights 2.0.0. When listing remediations for a management group it resolves the Microsoft.Management/managementGroups resource using api-version 2024-10-01 — but the Microsoft.Management resource provider does not support that api-version, so the call fails.

Repro

Install-Module Az.PolicyInsights -RequiredVersion 2.0.0 -Force
Get-AzPolicyRemediation -ManagementGroupName

Expected: MG-scope resolution should use a supported Microsoft.Management api-version (e.g. 2023-04-01), as in 1.7.4. Get-AzPolicyRemediation -ManagementGroupName should return remediations without error.

Every management-group-scoped remediation status check fails. This breaks EPAC New-AzRemediationTasks monitoring for all MG-scoped remediation tasks.

Environment

Az.PolicyInsights: 2.0.0 (broken) / 1.7.4 (works)
PowerShell 7 / Linux

Workaround: pin Az.PolicyInsights to 1.7.4.

Issue script & Debug output

Get-AzPolicyRemediation_List3: .../Az.PolicyInsights/2.0.0/PolicyInsights.Autorest/custom/Get-AzPolicyRemediation.ps1:280
The resource type 'managementGroups' could not be found in the namespace 'microsoft.management'
for api version '2024-10-01'. The supported api-versions are
'2024-02-01-preview,2023-04-01,2021-04-01,2020-10-01,2020-05-01,2020-02-01,2019-11-01,
2018-03-01-preview,2018-01-01-preview,2017-11-01-preview,2017-08-31-preview,
2017-06-30-preview,2017-05-31-preview,2018-03-01-beta'.

Environment data

Reproduced in a Linux CI container (custom internal image), PowerShell 7.x (Core).
This is an api-version issue in the generated cmdlet, so it is OS-independent.

Module versions

Az.PolicyInsights 2.0.0 fails / 1.7.4 works

Error output

[azure-client-tools-agent]

Bug Analysis

Module: src/PolicyInsights (Az.PolicyInsights)

Problem: In Az.PolicyInsights 2.0.0, Get-AzPolicyRemediation -ManagementGroupName <mg-name> fails when resolving the Microsoft.Management/managementGroups resource. The generated custom cmdlet code
(PolicyInsights.Autorest/custom/Get-AzPolicyRemediation.ps1, around line 280) sends api-version=2024-10-01 for the Microsoft.Management resource provider, but that provider does not support 2024-10-01. The call errors with:

The resource type 'managementGroups' could not be found in the namespace 'microsoft.management'
for api version '2024-10-01'. The supported api-versions are
'2024-02-01-preview,2023-04-01,2021-04-01,2020-10-01,2020-05-01,2020-02-01,2019-11-01,
2018-03-01-preview,2018-01-01-preview,2017-11-01-preview,2017-08-31-preview,
2017-06-30-preview,2017-05-31-preview,2018-03-01-beta'.

Working version: Az.PolicyInsights 1.7.4 resolves the management group using a supported api-version (e.g. 2023-04-01) and works correctly.

Fix: Locate where the management-group resolution builds the Microsoft.Management/managementGroups request (likely in src/PolicyInsights/PolicyInsights.Autorest/custom/Get-AzPolicyRemediation.ps1 or a shared helper used for MG-scope resolution), and change the hardcoded/derived api-version for that specific call from 2024-10-01 to a supported version such as 2023-04-01, matching the working behavior in 1.7.4. Do not change api-versions used for other resource types/providers.

Test: Add/update a PolicyInsights.Test TestFx Record test exercising Get-AzPolicyRemediation -ManagementGroupName to confirm the fixed api-version resolves successfully.

Use this EXACT PR title: [PolicyInsights] Fix unsupported api-version for management-group scope

PR title & description (azure-powershell)

Follow CONTRIBUTING.md. azure-powershell does not enforce a strict title gate — it requires a clear, informative title and a fully filled-out PR template.

Suggested PR title (clear & informative; [Module] prefix is the common convention):

[PolicyInsights] Fix unsupported api-version for management-group scope

Required (per CONTRIBUTING.md):

• Fill out the PR template completely — PRs are not reviewed without the completed checklist; do not delete it.
• Link the issue — include Fixes #29850 in the description so the PR auto-closes it.
• ChangeLog — add a bullet describing the fix under the ## Upcoming Release header of src/PolicyInsights/PolicyInsights/ChangeLog.md. Do not add a new version header.
• Target branch — main.
• Tests — add/adjust test coverage for the change. Tests must not contain hardcoded values (location, resource id, etc.) and must be re-recordable; do not skip existing tests.
• Scope — keep the change limited to the affected module (src/PolicyInsights/).

---

Posted by agent-assist (autonomous bug-fix pipeline).