feat(datamigration): add support for blob to Sql MI identity migrations

[gansach]

Description

• Bumped up REST api spec from 2022-03-30 preview to 2025-03-15-preview
• Introduced new params to New-AzDataMigrationToSqlManagedInstance cmdlet
  • AzureBlobAuthType
  • AzureBlobIdentityType
  • AzureBlobUserAssignedIdentity <string[]>
    • Had to add a custom wrapper commandlet to input this param as the auto generated param had hashtable type
    • Made this change to adhere to best practices
    • These managed identity input best practices have been implemented autorest/powershell v4, but we encountered a bug while renaming the auto generated param, migrating to autorest/powershell v4 will be taken up as a separate effort.

Scenarios tested

• AzureBlobAuthType=abc- REJECTED
• AzureBlobAuthType=null - PASSED (implicit account key)
• AzureBlobAuthType=ManagedIdentity; AzureBlobIdentityType=null - REJECTED
• AzureBlobIdentityType=SystemAssigned - PASSED
• AzureBlobIdentityType=UserAssigned - PASSED
• AzureBlobIdentityType=abc - REJECTED
• AzureBlobIdentityType=SystemAssigned,UserAssgined - REJECTED
• AzureBlobIdentityType=UserAssigned; AzureBlobUserAssignedIdentity=null - REJECTED
• AzureBlobUserAssignedIdentity=invalid-url - REJECTED
• AzureBlobUserAssignedIdentity=valid1, valid2 - REJECTED

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.

[wyunchi-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[wyunchi-ms]

Please fix the failed test cases

[wyunchi-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[wyunchi-ms]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wyunchi-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[wyunchi-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).