Update move-resource-group-and-subscription.md with potential cost/charge factors to consider.

[jamesmicrosoft]

This stemmed from a case where cx was requesting cost information regarding moving a storage account from one subscription to another. This documentation is for moving within the same region. There is no publicly available information on what to factor in when considering cost. I can see this being the same as the Azure Resource Mover but I am not sure.

When moving resources across regions and using Azure Resource Mover, there is a documentation on how to and cost.

• How to: https://learn.microsoft.com/en-us/azure/resource-mover/move-region-within-resource-group?toc=%2Fazure%2Fazure-resource-manager%2Fmanagement%2Ftoc.json
• Frequently asked questions, "What charges do I incur while using Azure Resource Mover?" https://azure.microsoft.com/en-us/pricing/details/resource-mover/

When using AzCopy, there is a how to page and a whole page for Estimating the cost of using AzCopy to transfer blobs.

• How to: https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-copy?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json&bc=%2Fazure%2Fstorage%2Fblobs%2Fbreadcrumb%2Ftoc.json&branch=pr-en-us-259662
• Cost: https://learn.microsoft.com/en-us/azure/storage/blobs/azcopy-cost-estimation

I've written the question on line 490, "How much does it cost to move Azure resources to a new resource group or subscription within the same region, and what should I consider?" to get it started.

Answer is still needed.

[prmerger-automator[bot]]

@jamesmicrosoft : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod[bot]]

Learn Build status updates of commit 1fcd934:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/azure-resource-manager/management/move-resource-group-and-subscription.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[ttorble]

@mumian

Can you review and complete the proposed changes? Note that the content will need to be reworded to avoid discussing actual costs, which can't be publish in Learn articles.

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

[PMEds28]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[mumian]

#assign-reviewer:SomilGanguly

[mumian]

#assign-reviewer:peterhee

[v-dirichards]

@peterhee @SomilGanguly

Can you review this old PR and determine whether it needs to be closed or merged?

IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. If the changes no longer apply, add an explanation and a #please-close comment to close the PR.

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

@peterhee @SomilGanguly Would you add a comment to indicate what action to take on this PR?

Thanks!

[v-dirichards]

I sent a Teams message to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[mumian]

@jamesmicrosoft - Would these answer your question? If yes, I can update the article:

• While performing the relocation the source environment might need to be in running state to maintain lesser downtime, this needs to be considered in costing and have a dual cost (as both the source and target regions will be running until cutover)
• Also, when we relocate the resources to the target region, the individual resource price needs to be checked as per that regions (as there might be price difference based on the azure region chosen)

[mumian]

@jamesmicrosoft - I'll go ahead and close this PR due to the lack of response. If you have any questions or would like to revisit this, feel free to reply here.

#please-close