[Az.Migrate] Bug fixes and new id validations

[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.

[Copilot]

Pull Request Overview

This PR fixes a bug in the New-AzMigrateLocalDiskMappingObject function where the validation logic for PhysicalSectorSize was incorrectly triggering when the parameter wasn't explicitly provided by the user.

• Modified validation logic to only check PhysicalSectorSize when explicitly provided
• Enhanced error message to include the actual value that was provided
• Added parameter existence check using $PSBoundParameters.ContainsKey()

[YanaXu]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[NoriZC]

Hi @minhsuanlee, please update the Changelog accordingly. And I also wondering if this need a test case

[github-actions]

This PR was labeled "needs-revision" because it has unresolved review comments or CI failures.
Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.

[github-actions]

‼️ DO NOT MERGE THIS PR ‼️
This PR was labeled "Do Not Merge" because it contains code change that cannot be merged. Please contact the reviewer for more information.

[minhsuanlee]

Hi @minhsuanlee, please update the Changelog accordingly. And I also wondering if this need a test case

I've updated the Changelog. As for test case, we are testing PS module change with our dev test pipelines. I will keep the DoNotMerge tag for now but please continue with the review. Thank you.

[NoriZC]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[NoriZC]

@minhsuanlee can I ask why the do not merge tag is here? Are you expecting another reviewer from your owne team?

[minhsuanlee]

@minhsuanlee can I ask why the do not merge tag is here? Are you expecting another reviewer from your own team?

Yes, and also we may push more changes if new bugs come up before Code Complete for this iteration.

[NoriZC]

@minhsuanlee Please keep me updated if you have other updates. Or you can choose to merge this first and raise another PR for further review & merge

[isra-fel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[VeryEarly]

Hi @minhsuanlee ,

Please let me know when you finish the test

[minhsuanlee]

Passing dev test run with private build (v3.0.13) at https://dev.azure.com/msazure/One/_build/results?buildId=137281957&view=results

[isra-fel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[minhsuanlee]

@isra-fel @VeryEarly How should I resolve powershell-core pipeline failure in this PR?

[isra-fel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[isra-fel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).