Azure-docs: Change history on moved resources

[whaakman]

Change history worked on a specific resource (microsoft.web/sites), after moving the resource to another resource group it no longer works (I'm guessing because the resourceID changed. New changes on the resource within the new Resource Group do work. If I'm interpreting this correctly, I detect resource moves through the Change History API's (the move is logged in the Acitivity Log though).

Regards, Wesley

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 733fcd9b-e234-8765-a7e0-498ded659ddc
• Version Independent ID: bd115a3e-37c9-66c9-da11-68b46b563275
• Content: Get resource changes - Azure Resource Graph
• Content Source: articles/governance/resource-graph/how-to/get-resource-changes.md
• Service: resource-graph
• GitHub Login: @DCtheGeek
• Microsoft Alias: dacoulte

[KrishnaG-MSFT]

@whaakman Thanks for the comment. We are actively investigating on the issue and will get back to you shortly with an update.

[SwathiDhanwada-MSFT]

@whaakman yes your understanding related to change api is indeed correct. Here is my inference of it.
1) When a resource (R) is moved from one resource group (A) to another resource group (B) ,
all the past activity log related to it is stored in the RG (A) from which it is moved.Even after moving the resource, the activity log or change history can be found with the old RG (A).
2) All the new changes made to the resource (R) can be seen in activity log or change history of resource in new RG (B).
3) When the move happens, the resource is logged as deleted in old RG(A) which is why it is not seen in the history of the resource and also in the new RG(B), it is treated as a new resource , so no change related to move is logged for the resource (R).

@DCtheGeek please provide your insights on the issue.

[DCtheGeek]

@whaakman Confirming with the team and will get back shortly. Thanks!

@MicrosoftDocs/azure-cxp-triage #in-progress

[jennyhunter-msft]

Thanks for your feedback. Your assessment is correct. Today we do not track resource moves. If this is something you are interested in, please vote for this item on our UserVoice page.

[DCtheGeek]

@whaakman Thanks again for the feedback! We'll go ahead and close this issue now.

@MicrosoftDocs/azure-cxp-triage #please-close