We are looking at simplifying the automation scripts used for starting and shutting down VMs in your subscription so hopefully that will make it easier to use. We will update with the status here once we have a solution in place.
Thanks for the feedback.
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:
An error occurred while saving the commentPRISMA Computer GmbH commented
I'm completely shocked to hear that resources are really identified and related by their names and not by their GUID or whatever other kind of resource ID!!! Otherwise it's not explainable why a simple rename of a resource means moving the resource instead of just giving an unique identifier another human readable name... ridiculous!!
Apologies closed in error. Reopening
DNSSEC remains on our long term roadmap, however it is unlikely to be available in CY 2019. If DNSSEC is a critical and immediate requirement for your business we’d suggest that you consider evaluating 3rd party DNS hosting solutions that provide this feature.
We’re thinking about some networking updates across the platform that will enable this feature. Thanks for your feedback
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature