Enhance Az.Migrate to prep for service release

[minhsuanlee]

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.

[github-actions]

To the author of the pull request,
This PR was labeled "Breaking Change Release" because it contains breaking changes.

• According to our policy, breaking changes can only take place during major release and they must be preannounced.
• Please follow our guide on the detailed steps.
• Required: Please fill in the task below to facilitate our contact,you will receive notifications related to breaking changes.

[YanaXu]

Hi @minhsuanlee, if it's a breaking change PR, we'll leave this PR open till the breaking change release sprint.

[minhsuanlee]

Hi @minhsuanlee, if it's a breaking change PR, we'll leave this PR open till the breaking change release sprint.

The modified commands are all in preview which I believe breaking changes are allowed. Let me know if that is not the case. If not, please help me get pass the above failing checks.

[YanaXu]

Hi @minhsuanlee, if it's a breaking change PR, we'll leave this PR open till the breaking change release sprint.

The modified commands are all in preview which I believe breaking changes are allowed. Let me know if that is not the case. If not, please help me get pass the above failing checks.

Hi @minhsuanlee, it's not allowed to merge breaking change PRs to a GAed module. Az.Migrate is GAed (major version number is over 1). Thus, breaking changes will only be allowed in major release, and next major release is 15.0.0.

[YanaXu]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[YanaXu]

jor release

For record: New-AzMigrateLocalDiskMappingObject was added in PR #27207 with "Microsoft.Azure.PowerShell.Cmdlets.Migrate.Runtime.PreviewMessageAttribute". It means breaking changes are allowed to this cmdlet.

[YanaXu]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Copilot]

Pull Request Overview

This PR enhances the Az.Migrate module by updating help docs, adjusting solution/project references, bumping versioning, and adding new appliance parameters and validations for local server replication.

• Updated ChangeLog and module/project versions for the upcoming 2.8.0 release
• Added -SourceApplianceName and -TargetApplianceName parameters and improved validation logic in New-AzMigrateLocalServerReplication
• Refactored PowerShell helper and init scripts to use hashtables for parameter invocation and added new input validations

Reviewed Changes

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

Show a summary per file

File	Description
src/Migrate/Migrate/ChangeLog.md	Documented removal/addition of parameters and validations
src/Migrate/Migrate.sln	Updated project path and GUID, fixed BOM at solution start
src/Migrate/Migrate.Autorest/docs/README.md	Normalized path separators in docs
src/Migrate/Migrate.Autorest/docs/New-AzMigrateLocal*.md	Added docs for new appliance-name parameters and removed stale
src/Migrate/Migrate.Autorest/custom/New-AzMigrateLocal*.ps1	Updated PreviewMessageAttribute, added params & validations
src/Migrate/Migrate.Autorest/custom/Initialize-AzMigrateLocalReplicationInfrastructure.ps1	Enforced provisioning-state checks and refactored calls
src/Migrate/Migrate.Autorest/custom/Helper/*.ps1	Enhanced OS/VMware-tools validations and added comments
src/Migrate/Migrate.Autorest/custom/AzLocalDiskInput.cs	Removed deprecated storageContainerId property
src/Migrate/Migrate.Autorest/README.md	Bumped auto-rest module-version
src/Migrate/Migrate.Autorest/Properties/AssemblyInfo.cs	Updated assembly and file versions to 2.8.0

Comments suppressed due to low confidence (2)

src/Migrate/Migrate.Autorest/custom/New-AzMigrateLocalServerReplication.ps1:104

• [nitpick] New mandatory parameters lack explicit ParameterSetName assignments. Consider specifying ParameterSetName for clarity and to avoid unintentionally impacting other parameter sets.

        [Parameter(Mandatory)]

src/Migrate/Migrate.Autorest/custom/New-AzMigrateLocalDiskMappingObject.ps1:78

• New validation logic for VHD physical sector size was added; please ensure unit tests cover both passing and failing scenarios for this check.

        if ($Format -eq "VHD" -and $PhysicalSectorSize -ne 512) {

[Copilot]

This reassigns $targetDra from the full $targetDras list rather than the filtered $targetDra array. It should be \$targetDra = \$targetDra[0] to use the previously validated, filtered result.

Suggested change

	$targetDra = $targetDras[0]
	$targetDra = $targetDra[0]

[YanaXu]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).