255 votes11 comments · Networking » Security (ACLs, Firewalls, Intrusion Detection) · Flag idea as inappropriate… · Admin →
Thanks for the feedback, we’ll consider this feature for future improvements
Renaming resources is like refactoring code, it really would be helpful.
We have reviewed this and have elected to not include this on our road map for the time being. We may revisit this in the future so will leave as unplanned rather than declined or closed.
Thanks for your suggestion and comments.
We are excited to announce the next generation AzCopy, v10, which now supports /MIR functionality through the ‘sync’ command. AzCopy v10 is available for Windows, Linux and MacOS and is now in Public Preview. See https://github.com/azure/azure-storage-azcopy for more information
Support for premium file shares is now available in limited preview: https://azure.microsoft.com/en-us/blog/premium-files-pushes-azure-files-limits-by-100x/
We are working to make this preview broadly available, but in the meantime, we would appreciate anyone who wants to give us feedback on our premium file shares applying for access to our limited preview by filling out this survey: https://aka.ms/PremiumFilesPreview
Program Manager, Azure Files
this is very important feature. In our scenario the Azure File API is used to keep up to date a drive of data, which serves as the base for several FTP servers. The solution works great, but the throughput of HDD is becoming a bottleneck.
There are multiple responses to this suggestion.
Support for SQL-like syntax for UPDATE, DELETE and INSERT INTO are not on our road map at this time.
However, the underlying functionality for an UPDATE, SET is essentially a PATCH. This functionality we are actively working on. See this User Voice item here to track for future updates. https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/6693091-be-able-to-do-partial-updates-on-document
Thank you for your suggestion.
At this point our recommendation is to move resources into a new Resource Group with the new name.
The proposed solution is going nowhere ... new types of resources can not be moved ... like managed disks, vm's using managed disks neither ... The solution should be based on GUID's and display names. If this is not a simple task, then at least it should be the strategy so that every service of Azure can implement that.
We are considering this support to rename a VM.
Every resource should be possible to rename. Everytime I start to try Azure again for some purpose, I really get soo frustrated by the inability of renaming of any of the resources really makes quit trying to get something done on azure.