400 votesunplanned · 41 comments · Azure portal » Resource management · Flag idea as inappropriate… · Admin →
We will take a look at this ask as we improve the VM API for more granular controls on start/stop and autoscale.
You can also use Azure Automation. We use runbooks here to increase/decrease VMs on a schedule as well as take image backups on a schedule. Give it a look as they are looking to improve the scheduling functionality as well.
We are considering this support to rename a VM.
One thing to watch with this will be other services that depend on that name. Not sure if Azure could identify this but if you use Azure Automation for anything it's name specific and would break if the name changes.
Given the sparse nature of Windows Azure Storage and with recent announcement for trim support on guest OS’s that support trim, the need for resizing should be reduced, as you should just assume you start with the largest size possible and only pay for what you use.
This is great if you are setting up a new server or have the ability to just rebuild a server(s) but what about exiting servers that need to be increased?
469 votesunder review · AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
We are looking into this. There are a few updates that we need to make on how we configure the ephemeral disk to ensure that Windows will consistently keep the same drive letter for this drive so that we can continue to keep the pagefile on the ephemeral disk to ensure optimal performance.
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 should be made available for ALL VMs not just virtual machines v2 which most are not using
428 votes24 comments · Networking » VPN Connectivity (Point-to-Site, Site-to-Site) · Flag idea as inappropriate… · Admin →
This can be done via Azure Monitor. Site-to-Site completed. Point-to-Site included in planning.
Good feedback to improve experience around endpoint mapping.
It would also be nice if we could apply lockdown groups by country (based on known IP ranges for each country). This would allow us to only expose Azure services to a known set of IP ranges.
For example, if clients only connect for the US then only those IP addresses should be allowed to connect to it. This would shrink the exposure.