Yes, please add this feature!!
Don't agree and don't make sense to accomplish this. It's important to audit activities.
We are evaluating what we can do to address this feedback and would very much appreciate your continued votes and suggestions on it.
One alternative to mounting the share on-premises over port 445 is Azure File Sync, which enables you to create a cache of an Azure file share on an on-premises Windows Server. Azure File Sync only sends data over the Azure Files HTTPS (using the File REST APIs). You can learn more about Azure File Sync here: https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-planning
Please don’t hesitate to reach out if you have any additional questions!
Program Manager, Azure Files
The ability to change 445 port is the best way to resolve the Azure File connection problem. Please update!
Vote! This is very important! It's hard to imagine that a cloud resource is not able to move due to a software limit.
707 votesunder review · AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
This request is still something that we still have on our backlog for a potential future update, but we are not able to provide a timeline for it at this point.
we need to be able to rename VMs, why is it not possible, even it is so simple
120 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.
307 votesunplanned · 43 comments · Azure portal » Resource management · Flag idea as inappropriate… · Admin →
Yes, https://cloudcraft.co is a perfect tool for AWS architecture, so how to do it for Azure?