163 votesstarted · AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
Startup times for VMs continues to be a focus in Azure. I am leaving this item in the “Started” state because we still have work to be done, but the current deployment time we are seeing for Windows Server on average is 2 minutes (1 minute for Linux). We’ll continue to invest resources in driving down this number.
We do have this feature on our backlog, but do not have a timeline for it as yet.
We will update the status as soon as we have an ETA.
314 votestriaged · 11 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
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
Apologies for the delay in responding here. I know we did have a bug earlier this year. Can you please confirm if this issue is fixed or you are still having the issue.
An error occurred while saving the commentChristian D. commented
Same issue. I understand the default behavior is "protective" but it would be nice when deleting to have a checkbox that allows to "release" the name for use on other subscriptions and/or resource groups (and in the ARM Template or API as well of course).
In a DEV/TEST cycle this is very annoying...