[Az.Migrate] To Azure Local - additional 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.

[mayada83]

approving with suggestion, we should try to accommodate other guest os type to provided as param from user if he knows the flavor is linux, if tools are not installed we should throw warning not failure, as its not blocker for migration business.

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

[Copilot]

Pull Request Overview

This PR adds additional validations and parameter enhancements for the Azure Migrate "To Azure Local" functionality. The changes focus on improving error handling, validation logic, and adding OS type specification capabilities.

Key changes include:

• Added -OsType parameter to Set-AzMigrateLocalServerReplication for user-specified OS type
• Enhanced Arc Resource Bridge validation with clearer error messages
• Improved RunAsAccount retrieval logic for both Hyper-V and VMware scenarios
• Updated validation messages to be more informative and actionable

Reviewed Changes

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

Show a summary per file

File	Description
Set-AzMigrateLocalServerReplication.ps1	Added OsType parameter with validation and integration into update logic
Start-AzMigrateLocalServerMigration.ps1	Enhanced Arc Resource Bridge validation and refactored parameter handling
New-AzMigrateLocalServerReplication.ps1	Improved RunAsAccount retrieval and replaced cluster validation with Arc Resource Bridge checks
CommonHelper.ps1	Updated validation logic and renamed function for better clarity
AzLocalCommonSettings.ps1	Enhanced error messages and added Arc Resource Bridge validation messages
*.md files	Updated documentation to reflect new OsType parameter
README.md	Modified directive configuration for HyperV operations
Start-AzMigrateLocalServerMigration.Tests.ps1	Added LiveOnly tag to test

Comments suppressed due to low confidence (1)

src/Migrate/Migrate.Autorest/custom/Helper/CommonHelper.ps1:40

• The function name 'GetARGQueryForArcResourceBridge' uses inconsistent casing. PowerShell convention uses PascalCase with hyphens, so it should be 'Get-ARGQueryForArcResourceBridge' or follow the established pattern in the codebase.

function GetARGQueryForArcResourceBridge {

[YanaXu]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mayada83]

looks good.

[minhsuanlee]

/azp run azure-powershell - security-tools

[azure-pipelines]

Commenter does not have sufficient privileges for PR 28183 in repo Azure/azure-powershell

[minhsuanlee]

@YanaXu After building the module locally I see that Migrate.sln was automatically updated with some new GUID for Az.Migrate entry. Should I push that change too?

[YanaXu]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[YanaXu]

@YanaXu After building the module locally I see that Migrate.sln was automatically updated with some new GUID for Az.Migrate entry. Should I push that change too?

Yes, just submit it.

[YanaXu]

Hi @minhsuanlee, I see you add a label "Do not merge". I'll keep this PR unmerged till your remove this label.

[minhsuanlee]

@YanaXu After building the module locally I see that Migrate.sln was automatically updated with some new GUID for Az.Migrate entry. Should I push that change too?

Yes, just submit it.

Ok. I have also pushed other auto-updated files. Please let me know if any of them should not be included.

[YanaXu]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[YanaXu]

Hi @minhsuanlee, I've approved this PR. Please feel free to merge it if there are no other changes.
Please notice the next code complete date is 07/29/2025.