Update-AzConfig displays "breaking change warning" while I use it to turn it off ??!

[andrePKI]

Description

I ask for suppression of these warnings
Update-AzConfig -DisplayBreakingChangeWarning $false -Scope Process

and very ironically I get

Upcoming breaking changes in the cmdlet 'Update-AzConfig' :
Parameter 'DisableErrorRecordsPersistence' will be deprecated, a new parameter 'EnableErrorRecordsPersistence' will be added instead. Writing error records to file system will become opt-in instead of opt-out. This change will happen around May 2024
- The change is expected to take effect in Az version : '12.0.0'
- The change is expected to take effect in Az.Accounts version : '2.X'
Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.

I suspect if I do not use -Scope Process it will be only once, but hey, I want to turn off exactly what I am getting...

Issue script & Debug output

Update-AzConfig -DisplayBreakingChangeWarning $false -Scope Process

Upcoming breaking changes in the cmdlet 'Update-AzConfig' :
Parameter `DisableErrorRecordsPersistence` will be deprecated, a new parameter `EnableErrorRecordsPersistence` will be added instead. Writing error records to file system will become opt-in instead of opt-out. This change will happen around May 2024
- The change is expected to take effect in Az version : '12.0.0'
- The change is expected to take effect in Az.Accounts version : '2.X'
Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.

Environment data

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

Module versions

Get-Module Az* did not give any output (The script is run from an Azure Runbook / Automation account)

Error output

No exception involved therefore cmdlet not run

[dolauli]

@isra-fel Please confirm whether it is expected behavior.

[andrePKI]

No, scope is Process, so I expect the very cmdlet also to shut up when I ask for it. Scope User or Global, then I can understand it. But I encounter this when executing a runbook in an Azure automation account, so can't make global changes. Vriendelijke groet, André Hoekstra Op do 29 mei 2025 04:18 schreef Xiaogang ***@***.***>:

…

*dolauli* left a comment (Azure/azure-powershell#27843) <#27843 (comment)> @isra-fel <https://github.com/isra-fel> Please confirm whether it is expected behavior. — Reply to this email directly, view it on GitHub <#27843 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFTL2FTX5AFPSPKBX53PRTT3AZVBHAVCNFSM6AAAAAB555NZAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJYGA2DEOJVGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[isra-fel]

This is a side effect of the lifecycle of cmdlets - printing the warning is part of BeginProcessing() which executes before ExecuteCmdlet() where the config is actually updated.

Moving the message printing to EndProcessing() might address this, but it's too big a change we need to consider carefully.

Alternatively, update Az.Accounts to v3.0.0+ and this particular message will be gone.