For running VM, "Service healing" will prevents down-time.
On the other hands, for initiation of VM, user have to wait for VM fully starts and user cannot detect the reason why VM starts slowly.
I would propose that Azure automatically retry starting VM on another node in case Azure detect unhealthy node events.1 vote
valid suggestion subject to customer upvote
We need more custom VM sizes besides the existing ones. Sometimes we may need more or less vCPU/RAM, which are not included in the existing VM sizes. It would be better for customers to config their prefer sizes.1 vote
Valid suggestion subject to customer upvotes
When I use ARM template and Custom Script Extensions with protected settings, these options are available in clear text in Deployment option.
Can you fix it?1 vote
In linux environment default permission of /mnt/resource is 755.
It is nice to have a functionality to set any permission to that.1 vote
Valid Suggestion subject to upvote
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
- Don't see your idea?