We plan to add the auto-start to the regular Compute blade at some point. However, if you create the VMs in a Lab, the auto-start is already available.
Also, we do de-allocate.
Thanks for the input!
Auto start would be an excellent addition but even better would be the option to customize the auto start stop options with day by day option this looks like it is in the dev test labs already but it is also needed for the production environment
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
This is something we’re still actively working on. It has a been a big area of investment and it still is moving forward. We keep investing in performance, both from a client and server side perspective.
We have a few things coming in the near future which should help address some of the initial UI performance issues. We’re also heavily engaged with all of our partners driving a broad effort to improve performance across the portal for all experiences.
If you have any specific areas which are causing pain please feel free to reach out to me or comment and state if we can contact you, it would be great to understand the common pain points.
Make the portal faster and more responsive
it takes on average 195 Seconds from logging on to refresh the status of 175 Azure VM's in the portal
I can refresh the same number of VM's in my on premise estate in only 20 seconds why is there such a difference
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
Still Getting errors and nothing working yet what is the story when will this be fixed
There was an error moving resources. Code:
Resources'/subscriptions/(ID_Removed)/resourceGroups/(VM_NAME)/providers/Microsoft.ClassicCompute/virtualMachines/Cloud service (classic) '
could not be moved. The tracking Id is 'c51ed486-8d19-4a12-9611-6b28be81d80f'
TIME Wednesday, January 6, 2016, 1:28:18 PM
CORRELATION IDS clientNotification-c61079eceab94a839158e477c5a24e6b0-XX
1 voteSimon Eastwood shared this idea ·
113 votesunder review · 2 comments · Azure portal » Resource management · Flag idea as inappropriate… · Admin →