Currently, from metric explorer I can view some metrics from a single node from a VMSS. For example, I can view CPU percentage for node-0 in a chart. However, it will be more useful if I can put CPU percentage metrics for other nodes in the same chart so that I can view all CPU usage in a single chart. Then I can do a second chart for network for all nodes.1 vote
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
Currently, to mount azure file share on Linux VM, we use mount command provide storage access key. If someone refresh their storage access keys, they need to un-mount the file share and then re-mount it. There should be an easier approach to handle this scenario. This become pain when you have auto-refresh policy in your organization.0 votes
upon creation of schedule for servers to be updated a specific date once a month is ignored if you do not change start day on top of UI. The server(s) will be updated on startday and time. Not as intended on the specific date the first time. You should remove start date, when selecting periodic updates. Alternative automatically change start date to the day the first updates should be applied according to schedule. I had servers rebooting yesterday because of this error and not at the 10th as scheduled.
The idea is, that i can change the order of interfaces under a vm. The problem is a third party device like Checkpoint firewalls get the port order from azure. So, if i want to rearrange the order i have to detach all interfaces and afterwards i have to attach them in the right order. This is very time consuming.
Moreover, if i make a mistake at the beginning, i have to detach all network interfaces, which i did attach to rearrange the order.0 votes
when we are creating VM image its shouldn't make VM power off, Please work on this and make VM image creation on fly when VM is running.
Compute, Capacity availability: The allocation hotspot chart should show the availability of the customers cores/VMs by a particular region.
Score - Capacity available measured from 0-10.
0 being lots of capacity /availability of cores in a Subscription.
10 full capacity / availability saturation of cores in a Subscription.
**Allocated Cores could calculate how many VMS you can request and break it down by VM size. Example; A1=151, DSV12-V2=36 etc.0 votes
When creating a new data disk for a VM it would be nice if the default size was not 1023Gb. At this moment the disk are Managed by default, which will result in billing allocated disk space and not billing disk space used. A default of 31Gb would be nice.0 votes
- Don't see your idea?