Skip to content

Conversation

christinechen2
Copy link

Submitted via Learn Editor.

Copy link

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

@christinechen2 christinechen2 marked this pull request as ready for review October 1, 2025 20:23
@Copilot Copilot AI review requested due to automatic review settings October 1, 2025 20:23
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a new example to the Get-AzStorageAccountMigration cmdlet documentation showing how to check migration status for multiple storage accounts at once using a CSV file.

Key Changes

  • Added Example 2 demonstrating bulk migration status checking
  • Provided sample CSV format and PowerShell script for batch operations

@isra-fel
Copy link
Member

isra-fel commented Oct 1, 2025

/azp run

Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

christinechen2 and others added 3 commits October 2, 2025 13:56
Updated the script to ensure consistent formatting for getting storage account migration status.
@isra-fel
Copy link
Member

isra-fel commented Oct 2, 2025

/azp run

Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

isra-fel commented Oct 3, 2025

Hi @christinechen2 thank you very much for contributing! These examples seem more focused about your specific scenario (e.g. csv parsing, sku filtering) so I'm afraid I won't merge it.

@isra-fel isra-fel closed this Oct 3, 2025
@christinechen2
Copy link
Author

@isra-fel the documentation changes are necessary for helping customers do bulk LRS-ZRS migrations. I am a PM working on improving the LRS-ZRS migration experience. The example uses CSV parsing because customers will put their list of migrations in a CSV file and execute the script to start a migration for all the accounts at once. Could you please ping me @ christchen on Teams if you'd like to discuss the changes further?

@christinechen2 christinechen2 reopened this Oct 3, 2025
```powershell
# Log in to Azure
Write-Host "Logging into Azure..."
Connect-AzAccount
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Connect-AzAccount is no necessary.
This cmdlet is needed for all management plane cmdlets for all services, we won't add them for all example of all these cmdlet.
And there are clear error message if the cmdlets not run before run any management plane cmdlet.
So this cmdlet is not necessary in this example.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I actually put these changes in a different part of the docs and started a new PR for that (306548), but I have removed the login parts from the examples.


This command gets the migration status of the storage account myaccount under resource group myresourcegroup.

### Example 2: Get multiple Storage account migrations at once
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you please give the reason why need add this example?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are the example bulk migration scripts, so when customers want to start multiple migrations at once, they will also want to get the status of the same migrations at once, using the same CSV file where they listed all the accounts.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have moved these changes to the redundancy docs though, so I will close this PR as we don't need changes in the PS docs anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants