Mike Binnix
My feedback
-
927 votes
Hi folks,
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!
Thanks,
Will Gries
Program Manager, Azure FilesMike Binnix
supported this idea
·
-
1 voteMike Binnix
shared this idea
·
-
3 votes2 comments · Azure Monitor- Alert Management » Managing Alerts · Flag idea as inappropriate… · Admin →Mike Binnix
supported this idea
·
-
324 votesunplanned ·
AdminAzure IaaS Engineering Team
(Azure IaaS Engineering Team, Microsoft, Microsoft Azure)
responded
This is not something that we have on our roadmap. It is something that we may consider in the future.
Mike Binnix
commented
Would be very helpful even just for testing web apps so we can verify appearance performance in the safari browser on macOS.
Mike Binnix
supported this idea
·
-
87 votesunder review ·AdminAzure IaaS Engineering Team
(Azure IaaS Engineering Team, Microsoft, Microsoft Azure)
responded
This feature is under review for implementation.
Mike Binnix
supported this idea
·
This must be a high priority. We had an even more extreme example where customer service reported a systemic network failure in both US East2 and UK South. We could not start or provision any VMs for a 29 hour period during the service impact. BUT THE EVENT WAS NEVER REPORTED ON THE PORTAL SERIVCE HEALTH for US East2. NEVER MENTIONED. I find this an unacceptable omission in the process for managing system outages. The lack of communication is worse than the service disruption itself.