Thank you for voting on this suggestion. It is now completed and can be done via custom Azure Policy. Here is a sample custom policy to apply a specific tag at the RG and have them inherited by the Resources in that RG: https://github.com/Azure/azure-policy/tree/master/samples/ResourceGroup/copy-resourcegroup-tag
Tag inheritance for existing resources is something that we plan to add support for in 2019.
We are looking at options to enable this.
Thanks for the feedback. We’re working on this. We started with the top bar, then added favorites, and continued by shrinking the list of resources after opening the resource blade. Much more is in the works — all based on your feedback. Keep it coming and, in the meantime, we’ll keep working on this to streamline the experience for you.
At this point our recommendation is to move resources into a new Resource Group with the new name.
Thanks for the feedback – we will be looking into this
This is a great idea. We are thinking about adding such functionality to the Portal. No confirmed plan yet. Thanks.
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 Team
4 votesunder review · 0 comments · Azure portal » Create + deployments · Flag idea as inappropriate… · Admin →
I’m following up with the team on this item and we’ll update this forum post ASAP.
We are likely to support this in phases. Stay tuned for more details.