[BC] Functions Breaking Change Announcement by JunKai-v · Pull Request #29139 · Azure/azure-powershell

JunKai-v · 2026-02-05T03:57:43Z

Description

Migration PR: #29111

Mandatory Checklist

Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)
- General release
- Public preview
- Private preview
- Engineering build
- No need for a release
Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

SHOULD update ChangeLog.md file(s) appropriately
- Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
  - A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
- Should not change ChangeLog.md if no new release is required, such as fixing test case only.
SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
SHOULD have proper test coverage for changes in pull request.
SHOULD NOT adjust version of module manually in pull request

azure-client-tools-bot-prd · 2026-02-05T03:57:46Z

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

Copilot

Pull request overview

This PR adds breaking change announcements to the Azure Functions PowerShell module in preparation for the AutoRest v4 migration (PR #29111). The changes notify users that cmdlets will undergo breaking changes in Az v16.0.0, scheduled for release in May 2026.

Changes:

Added preview message attributes to 15 Functions cmdlets warning about upcoming breaking changes
Updated module metadata including version numbers, GUIDs, and generation dates
Added AutoRest README.md directives to generate preview announcements
Added stub test files for cmdlets with breaking changes

Reviewed changes

Copilot reviewed 29 out of 29 changed files in this pull request and generated 16 comments.

Show a summary per file

File	Description
src/Functions/Functions/Az.Functions.psd1	Updated generation date and formatting (tags array spacing, comment indentation)
src/Functions/Functions.sln	Updated project GUID references for AutoRest-generated project
src/Functions/Functions.Autorest/test/*.Tests.ps1	Added 9 stub test files for cmdlets (skipped tests with NotImplementedException)
src/Functions/Functions.Autorest/generate-info.json	Updated generation ID for new AutoRest run
src/Functions/Functions.Autorest/docs/Az.Functions.md	Updated module GUID
src/Functions/Functions.Autorest/custom/*.ps1	Added PreviewMessage attributes to 15 cmdlets announcing breaking changes
src/Functions/Functions.Autorest/README.md	Added AutoRest directives to configure preview-announcement messages
src/Functions/Functions.Autorest/Properties/AssemblyInfo.cs	Bumped version from 4.2.1 to 4.3.1

Copilot · 2026-02-05T04:08:17Z

src/Functions/Functions.Autorest/custom/Get-AzFunctionAppSetting.ps1

@@ -1,4 +1,9 @@
 function Get-AzFunctionAppSetting {
+    [Microsoft.Azure.PowerShell.Cmdlets.Functions.Runtime.PreviewMessage("**********************************************************************************************`n
+    * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n


The preview message text uses "to be released on May 2026" but the correct preposition should be "in" (e.g., "to be released in May 2026") when referring to a month. The README.md directives use "in May 2026" which is grammatically correct, but the generated custom cmdlet files incorrectly use "on May 2026".

Suggested change

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot · 2026-02-05T04:08:17Z

src/Functions/Functions.Autorest/custom/Get-AzFunctionAppPlan.ps1

@@ -1,4 +1,9 @@
 function Get-AzFunctionAppPlan {
+    [Microsoft.Azure.PowerShell.Cmdlets.Functions.Runtime.PreviewMessage("**********************************************************************************************`n
+    * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n


The preview message text uses "to be released on May 2026" but the correct preposition should be "in" (e.g., "to be released in May 2026") when referring to a month. The README.md directives use "in May 2026" which is grammatically correct, but the generated custom cmdlet files incorrectly use "on May 2026".

Suggested change

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot · 2026-02-05T04:08:18Z

src/Functions/Functions/Az.Functions.psd1

 # Generated by: Microsoft Corporation
 #
-# Generated on: 1/27/2026
+# Generated on: 05-Feb-26


The ChangeLog.md file should be updated with an entry under the "Upcoming Release" section describing the breaking change announcements that were added to the Functions module cmdlets. Per the repository's contribution guidelines, all changes should have corresponding ChangeLog entries.

Copilot · 2026-02-05T04:08:18Z

src/Functions/Functions.Autorest/custom/Remove-AzFunctionApp.ps1

@@ -1,4 +1,9 @@
 function Remove-AzFunctionApp {
+    [Microsoft.Azure.PowerShell.Cmdlets.Functions.Runtime.PreviewMessage("**********************************************************************************************`n
+    * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n


The preview message text uses "to be released on May 2026" but the correct preposition should be "in" (e.g., "to be released in May 2026") when referring to a month. The README.md directives use "in May 2026" which is grammatically correct, but the generated custom cmdlet files incorrectly use "on May 2026".

Suggested change

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot · 2026-02-05T04:08:18Z

src/Functions/Functions/Az.Functions.psd1

 # Generated by: Microsoft Corporation
 #
-# Generated on: 1/27/2026
+# Generated on: 05-Feb-26


The date format "05-Feb-26" is inconsistent with the previous format "1/27/2026". Consider maintaining consistency with the original date format, or if this is an intentional change, ensure it follows the repository's standard date format conventions.

Suggested change

# Generated on: 05-Feb-26

# Generated on: 2/5/2026

Copilot · 2026-02-05T04:08:20Z

src/Functions/Functions.Autorest/custom/New-AzFunctionAppPlan.ps1

@@ -1,4 +1,9 @@
 function New-AzFunctionAppPlan {
+    [Microsoft.Azure.PowerShell.Cmdlets.Functions.Runtime.PreviewMessage("**********************************************************************************************`n
+    * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n


The preview message text uses "to be released on May 2026" but the correct preposition should be "in" (e.g., "to be released in May 2026") when referring to a month. The README.md directives use "in May 2026" which is grammatically correct, but the generated custom cmdlet files incorrectly use "on May 2026".

Suggested change

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot · 2026-02-05T04:08:20Z

src/Functions/Functions.Autorest/custom/Stop-AzFunctionApp.ps1

@@ -1,4 +1,9 @@
 function Stop-AzFunctionApp {
+    [Microsoft.Azure.PowerShell.Cmdlets.Functions.Runtime.PreviewMessage("**********************************************************************************************`n
+    * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n


The preview message text uses "to be released on May 2026" but the correct preposition should be "in" (e.g., "to be released in May 2026") when referring to a month. The README.md directives use "in May 2026" which is grammatically correct, but the generated custom cmdlet files incorrectly use "on May 2026".

Suggested change

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot · 2026-02-05T04:08:21Z

src/Functions/Functions.Autorest/custom/Start-AzFunctionApp.ps1

@@ -1,4 +1,9 @@
 function Start-AzFunctionApp {
+    [Microsoft.Azure.PowerShell.Cmdlets.Functions.Runtime.PreviewMessage("**********************************************************************************************`n
+    * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n


The preview message text uses "to be released on May 2026" but the correct preposition should be "in" (e.g., "to be released in May 2026") when referring to a month. The README.md directives use "in May 2026" which is grammatically correct, but the generated custom cmdlet files incorrectly use "on May 2026".

Suggested change

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot · 2026-02-05T04:08:21Z

src/Functions/Functions.Autorest/custom/Restart-AzFunctionApp.ps1

@@ -1,4 +1,9 @@
 function Restart-AzFunctionApp {
+    [Microsoft.Azure.PowerShell.Cmdlets.Functions.Runtime.PreviewMessage("**********************************************************************************************`n
+    * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n


The preview message text uses "to be released on May 2026" but the correct preposition should be "in" (e.g., "to be released in May 2026") when referring to a month. The README.md directives use "in May 2026" which is grammatically correct, but the generated custom cmdlet files incorrectly use "on May 2026".

Suggested change

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot · 2026-02-05T04:08:21Z

src/Functions/Functions.Autorest/custom/Remove-AzFunctionAppPlan.ps1

@@ -1,4 +1,9 @@
 function Remove-AzFunctionAppPlan {
+    [Microsoft.Azure.PowerShell.Cmdlets.Functions.Runtime.PreviewMessage("**********************************************************************************************`n
+    * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n


The preview message text uses "to be released on May 2026" but the correct preposition should be "in" (e.g., "to be released in May 2026") when referring to a month. The README.md directives use "in May 2026" which is grammatically correct, but the generated custom cmdlet files incorrectly use "on May 2026".

Suggested change

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n

* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot

Pull request overview

Copilot reviewed 30 out of 30 changed files in this pull request and generated no new comments.

breaking change announcement for functions module

d267da0

Copilot AI review requested due to automatic review settings February 5, 2026 03:57

Copilot started reviewing on behalf of JunKai-v February 5, 2026 03:59 View session

Copilot AI reviewed Feb 5, 2026

View reviewed changes

JunKai-v requested a review from Francisco-Gamino February 5, 2026 04:39

update and rebuild

5852af0

JunKai-v added Breaking Change Preannounce This PR adds preannouncement about upcoming breaking change autorest v4 migration pr migrating module from generated by autorest.powershell v3 to v4 labels Feb 5, 2026

update change log md

a698a2f

Copilot AI review requested due to automatic review settings February 12, 2026 09:31

Copilot started reviewing on behalf of JunKai-v February 12, 2026 09:33 View session

Copilot AI reviewed Feb 12, 2026

View reviewed changes

	* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
	* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Conversation

JunKai-v commented Feb 5, 2026

Description

Mandatory Checklist

Uh oh!

azure-client-tools-bot-prd bot commented Feb 5, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant