Thank you for the suggestion. This feature is in preview! See this blog post for more information:
This would be great for ASE but also for standard Web Apps.
We have made some great progress on this idea and most of our services today do support move resources across groups.
We are still working towards 100% support and while we do that it would be great if you can help us prioritize the missing services.
Please file individual asks on each service category present in uservoice and vote for it.
Azure Portal TeamJoe commented
"We have made some great progress on this idea and most of our services today do support move resources across groups."
Yes you have and thank you for that!
Work for this feature is now planned. Will update when work on this feature starts and when it becomes generally available.
Azure Cosmos DB now provides the ability to access the change feed (https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed). A common pattern to implement eventing patterns is
1. Store every version/change as a separate item
2. Read the change feed to merge/consolidate changes and trigger appropriate actions downstream.
You can also expire old versions using TTL: https://docs.microsoft.com/en-us/azure/cosmos-db/time-to-live
Adam from the Azure Billing team here at Microsoft.
Our team is entirely committed to doing exactly what you suggest, which is to make all of the customer signup and billing experiences straightforward, comprehensible, and informative.
If you have more specific feedback on how we can make billing easy for you to understand, Please do not hesitate to expand upon your post in the comments.
Adam – Azure Customer Acquisitions & Billing
The Azure Resource Manager team is actively investigating the scenarios around renaming resource groups. To help us better understand the use-cases and to determine which implementations may be viable to address the problem, we would appreciate if you could fill out this 3-minute survey: