Get-AzResourceProvider is not returning the latest versions for Microsoft.Resources/resourceGroups

[dreuss-ka]

Description

Per https://learn.microsoft.com/en-us/azure/templates/microsoft.resources/2024-11-01/resourcegroups?pivots=deployment-language-arm-template there are newer versions available, but calling ((Get-AzResourceProvider -ProviderNamespace Microsoft.Resources).ResourceTypes | Where-Object ResourceTypeName -eq resourceGroups).ApiVersions is returning 2023-07-01 as the newest version (actual newest per the website is 2025-04-01).

I spot checked some other resource versions they all seemed to be correct, so this appears to only be a problem with resource groups.

This occurred running locally and on GitHub build agents.

Issue script & Debug output

PS C:\GitHub\automation\scripts> ((Get-AzResourceProvider -ProviderNamespace Microsoft.Resources).ResourceTypes | Where-Object ResourceTypeName -eq resourceGroups).ApiVersions
2023-07-01-preview
2023-07-01
2023-03-01-preview
2022-12-01
2022-11-01-preview
2022-09-01
2022-06-01
2022-05-01
2022-03-01-preview
2022-01-01
2021-04-01
2021-01-01
2020-10-01
2020-09-01
2020-08-01
2020-07-01
2020-06-01

Environment data

PS C:\GitHub\automation\scripts> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.4.17
PSEdition                      Core
GitCommitId                    7.4.17
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

PS C:\GitHub\automation\scripts> Get-Module Az*

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Script     5.3.4                 Az.Accounts                         {Add-AzEnvironment, Clear-AzConfig, Clear-AzConte…
Script     6.8.0                 Az.Resources                        {Export-AzResourceGroup, Export-AzTemplateSpec, G…

Error output

[a0x1ab]

Bug Analysis

The issue reports that Get-AzResourceProvider -ProviderNamespace Microsoft.Resources returns stale ApiVersions for the
Microsoft.Resources/resourceGroups resource type (latest returned is
2023-07-01, but ARM now exposes newer versions such as 2025-04-01, per
https://learn.microsoft.com/en-us/azure/templates/microsoft.resources/2024-11-01/resourcegroups).
Get-AzResourceProvider surfaces whatever the ARM Providers - Get API
returns, so please verify whether:

• the SDK/client used by Get-AzResourceProvider in the Resources module is
  pinned to an older ARM API version that limits the returned provider
  metadata, or
• there is any local caching/filtering of ResourceTypes/ApiVersions in the
  Resources module cmdlet code that could be dropping newer versions.

Reproduction steps and environment (PSVersion 7.4.17, Az.Resources 6.8.0) are
in the issue. Please investigate the Resources module's provider-listing
cmdlet implementation and update it so newer ApiVersions (matching what ARM
returns) are surfaced for Microsoft.Resources/resourceGroups (and verify no
other resource types are similarly filtered).

Use this EXACT PR title: [Resources] Return current ApiVersions for Microsoft.Resources/resourceGroups

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):

[Resources] Return current ApiVersions for Microsoft.Resources/resourceGroups

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 #29883 in the description so the PR auto-closes it.
• ChangeLog — add a bullet describing the fix under the ## Upcoming Release header of src/Resources/Resources/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/Resources/).

---

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