Get-AzureRmDnsRecordSet : The api-version '2018-03-01-preview' is invalid

[Christoba]

Description

It appears that 2018-03-01-preview is now unsupported. This version is pinned in Microsoft.Azure.Management.Dns.DnsManagementClient 2.1.0, which is packaged in AzureRm.Dns 4.1.2, which is pinned in AzureRm 5.7

AzureRm 6.13.1 does not appear to have this issue AzureRm 6.13.1 -> AzureRm.Dns 5.1.0 -> Microsoft.Azure.Management.Dns 3.0.0 uses ApiVersion 2018-05-01

As 5.7 is the last AzureRm5 version, this appears to require moving to AzureRm6/Az.

Script/Steps for Reproduction

This appears to now break when calling, e.g.

Get-AzureRmDnsRecordSet -RecordType A -ZoneName <zone> -ResourceGroupName <rgname>

Get-AzureRmDnsRecordSet : The api-version '2018-03-01-preview' is invalid. The supported versions are '2018-11-01,2018-09-01,2018-08-01,2018-07-01,2018-06-01,2018-05-01,2018-02-01,2018-01-01,2017-12-01,2017-08-01,2017-06-01,2017-05-10,2017-05-01,2017-03-01,2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'.

Module Version

AzureRm 5.7 AzureRm.Dns 4.1.2

Dll Version

Microsoft.Azure.Management.Dns 2.1.0

[maddieclayton]

@karravi-msft Can you take a look at this issue?

[Christoba]

Any updates on this? We've upgrade these specific calls to AzureRm 6, but it would be good to know if AzureRm 5 was indeed broken by this change and won't be supported moving forward.

[lwajswaj]

Why can't you migrate to AZ module?

[Christoba]

Our organization is in the process of doing this. I’m looking for confirmation that AzureRm 5 was deprecated and will no longer support this (and potentially other) workflows.

[lwajswaj]

AzureRm is deprecated according to my understanding as it's been replaced by AZ module. AzureRm won't have new functionality https://docs.microsoft.com/en-us/powershell/azure/new-azureps-module-az?view=azps-1.3.0

[Christoba]

@karravi-msft, can you confirm that 5.7 should be expected to no longer work and this issue will not be resolved?

@lwajswaj, this isn't new functionality, this was existing functionality that was broken by removing support for the api-version in the subject.

[karravi-msft]

@Christoba Azure DNS did not remove support for the 2018-03-01-preview version. We will look into this

[rohinkoul]

@karravi-msft any updates on this?

[karravi-msft]

Azure DNS service itself supports this API version. Looking into this

[KranthiPakala-MSFT]

Hi @Christoba As this issue seems to be very old and the Az PowerShell module is the replacement of AzureRM and is the recommended version to use for interacting with Azure, could you please try with Az Powershell module and let us know if this issue can be closed.

Because Az PowerShell modules now have all the capabilities of AzureRM PowerShell modules and more, and the AzureRM PowerShell modules are planned to be retired on 29 February 2024.

As per the guidance provided in this doc (Install Azure PowerShell on Windows with PowerShellGet), To avoid service interruptions, we request you to please update your scripts that use AzureRM PowerShell modules to use Az PowerShell modules. To automatically update your scripts, follow the quickstart guide.

And if you see any issues with Az Powershell Module, we request you to please open a new gitHub issue and also please confirm if this issue can be closed.

Thank you

[Christoba]

@KranthiPakala-MSFT, you are right that the issue was filed almost 3 years ago and there have been many azure powershell releases since as well as a number of REST releases since.

There are reproduction steps provided in the original post, but these aren't relevant to me any more (and likely irrelevant to anyone else). It does appear that this was an unannounced breaking change... there's been a few in azure powershell over the years :)

Closing this issue.

[KranthiPakala-MSFT]

Thanks for response and confirmation @Christoba ! :)