BC Announcement for DataMigration Autorest v3 to v4 Migration

[JiaSeng-v]

Description

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]

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

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR adds breaking change pre-announcements for the DataMigration module ahead of the Autorest v3 to v4 migration planned for Az v16.0.0 (November 2026). It introduces preview/breaking-change banners on relevant cmdlets via the AutoRest README directives and a custom cmdlet attribute, and updates module metadata.

Changes:

• Added breaking change pre-announcement messages for Get/New/Remove/Update DataMigration cmdlets via README directives and a PreviewMessage attribute on the custom New-AzDataMigrationToSqlManagedInstance cmdlet.
• Updated module manifest (Az.DataMigration.psd1), assembly version, solution project GUID, and module GUID/generate-id from regeneration.
• Added a ChangeLog entry pointing to the breaking changes documentation.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/DataMigration/DataMigration/ChangeLog.md	Adds an "Upcoming Release" note referencing the pre-announced breaking changes.
src/DataMigration/DataMigration/Az.DataMigration.psd1	Bumps Az.Accounts dependency, regenerated date/tags formatting, uncomments empty Scripts/TypesToProcess.
src/DataMigration/DataMigration.sln	Updates project GUID for the regenerated Az.DataMigration project.
src/DataMigration/DataMigration.Autorest/generate-info.json	Updates generate_Id from regeneration.
src/DataMigration/DataMigration.Autorest/docs/Az.DataMigration.md	Updates module GUID from regeneration.
src/DataMigration/DataMigration.Autorest/custom/Cmdlets/New-AzDataMigrationToSqlManagedInstance.ps1	Adds PreviewMessage attribute with breaking change banner.
src/DataMigration/DataMigration.Autorest/README.md	Adds AutoRest directives to attach breaking change preview messages to Get/New/Remove/Update cmdlets.
src/DataMigration/DataMigration.Autorest/Properties/AssemblyInfo.cs	Bumps assembly version to 1.0.0.

Comments suppressed due to low confidence (4)

src/DataMigration/DataMigration.Autorest/README.md:1

• The same long preview-message string is duplicated across four directives. Additionally, the top/bottom asterisk borders have different lengths than the interior lines, producing a ragged banner when displayed. Consider extracting the message into a YAML anchor/alias (e.g., &breakingChangeMessage / *breakingChangeMessage) to avoid duplication and ensure consistency, and equalize the asterisk widths so the framed banner renders cleanly.

<!-- region Generated -->

src/DataMigration/DataMigration.Autorest/README.md:1

• The same long preview-message string is duplicated across four directives. Additionally, the top/bottom asterisk borders have different lengths than the interior lines, producing a ragged banner when displayed. Consider extracting the message into a YAML anchor/alias (e.g., &breakingChangeMessage / *breakingChangeMessage) to avoid duplication and ensure consistency, and equalize the asterisk widths so the framed banner renders cleanly.

<!-- region Generated -->

src/DataMigration/DataMigration.Autorest/README.md:1

• The same long preview-message string is duplicated across four directives. Additionally, the top/bottom asterisk borders have different lengths than the interior lines, producing a ragged banner when displayed. Consider extracting the message into a YAML anchor/alias (e.g., &breakingChangeMessage / *breakingChangeMessage) to avoid duplication and ensure consistency, and equalize the asterisk widths so the framed banner renders cleanly.

<!-- region Generated -->

src/DataMigration/DataMigration.Autorest/README.md:1

• The same long preview-message string is duplicated across four directives. Additionally, the top/bottom asterisk borders have different lengths than the interior lines, producing a ragged banner when displayed. Consider extracting the message into a YAML anchor/alias (e.g., &breakingChangeMessage / *breakingChangeMessage) to avoid duplication and ensure consistency, and equalize the asterisk widths so the framed banner renders cleanly.

<!-- region Generated -->