Поддержка сообщества Azure
Задавайте вопросы, получайте ответы и связывайтесь с инженерами корпорации Майкрософт и экспертами сообщества Azure.
Форум MSDN
Ответы Майкрософт на технические вопросы по Azure
Auto-shutdown did not work on Win 10 VM
Forum: Azure Virtual Machines
Forum: Azure Virtual Machines
Virtual machine RDP is not working on Mac OSX for guest account
Forum: Azure Virtual Machines
Increasing Azure VM Spot price
Forum: Azure Virtual Machines
42
Голоса
MS Learn/ Sandbox Creation Error
Forum: Azure Virtual Machines
32
Голоса
Forum: Azure Virtual Machines
27
Голоса
Multiple IP addresses for a VM to be able to use Multiple HTTPS endpoints
Forum: Azure Virtual Machines
26
Голоса
Azure VMs no longer see themselves via public virtual IP
Forum: Azure Virtual Machines
73
Ответы
MS Learn/ Sandbox Creation Error
Forum: Azure Virtual Machines
51
Ответы
VM becomes unresponsive or disk becomes read-only
Forum: Azure Virtual Machines
42
Ответы
Question about deploying multiple VMs with template
Forum: Azure Virtual Machines
37
Ответы
Forum: Azure Virtual Machines
StackOverflow
Ответы сообщества на вопросы по разработке
34
Голоса
Server Fault
Ответы сообщества на вопросы системных и сетевых администраторов
15
Голоса
10
Голоса
Отзыв по Azure
У вас есть идеи или предложения на основе опыта работы с Azure?
There is no documentation in azure that clearly states the maximum number of NICs supported by each VM size. Please incorporate and 2 core 8 GB machines should support atleast 3 NIcs like in AWS and google.This is very bad documentation as it is a chain of links that point to other link example - https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface-vm#constraints
Documentation stating maximum number of NIC per VM size
Azure has no documentation that states maximum number of NIC supported by wach VM size. The documentation only does a ping pong of links and still doesnt give anything clearly, Example the below link says in constraint to check another link referring to linux general purpose VM sizes, but it has nothing on number of NICs supportedhttps://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface-vm#constraints
| Temporary Disk | Add on/off options for temporary disk when creating Azure VM
End user could ignore the DATA LOSS file on temporary disk which comes from Azure VM by default, if it's possible to add on/oof options for temporary disk when creating Azure VM?One more thing, when the VM is using temporary disk, if it's possible to pop-up a dialog box to notify the user that the data in temporary disk could be lose after stopping/deallocating the VM? (Like the public ip pop-up diaglog in the attachment)
5202
Голоса
Virtual machine console access
There is no VMConnect capability for console access to the VM as there is with Hyper-V.So in the situation where I lost connectivity, by misconfiguration, or system failure, is there only one very time and bandwith consuming way to fix it - download the VHDs on-premise, boot it in Hyper-V and VMConnect to repair VM, then upload all GBs back to the Azure...I requesting console access, also with ability to mount some image for repair and boot from it (as we do it in standard environment).
1435
Голоса
VM Created from custom image should be able to select storage account for VHD
When we try to create a virtual machine from a custom image the VHD's for the new virtual machine are created in the same storage account as the custom image. This is not ideal because most customers have different environments in different subscriptions so they are forced to copy the image into storage account in each subscriptions. It is not easy to copy the images between the storage accounts either.
1433
Голоса
Add the ability to rename a VM. The VM name is what appears in Azure, not the DNS name.Changing a VM's name should not affect the VM in any way. If you need a unique identifier for a VM that does not change, I suggest using a GUID rather than the VM's name in Azure.
1201
Голоса
Live migrate the VMs during maintenance/hardware failures
Right now Azure VM customers experience very frequent restarts that impact the availability of services. As far as I know, these restarts are mostly caused by either host upgrades or hardware failures.Developing a HA setup is pretty straightforward for some scenarios (web servers), complex (database back-ends, notably MySQL) or extremely difficult (back-end applications used by our accounting department, for instance, which were designed to be run on one machine). Of course, HA setups are necessary for any major applications, but most of the setups we see have lots of single-instance roles (and for good reason most of the times).Currently, if you don't have an HA setup, machines are restarted about once per month or even more frequent (some as often as weekly). If this restart occurs during business hours, then this means downtime.Furthermore, for services like MySQL or SQL Server, this also means that the entire buffer pool is emptied and the performance of the application is degraded until the buffer pool fills up again.What we would love to have is something like Google Cloud's Live Migration - the VM would be moved to another host in case of hardware failures or host upgrades without restarts or downtime.
Allow to set the value of shutdown timeout (force shutdown)
According to the current behavior, if it is not completed within 10 minutes after the stop(deallocate) operation of Azure VM, I believe that the stop will be forced.However, it may take a lot of time due to the stop processing of process or OS task.I hope to be able to determine the forced out timeout time ourselves.
Azure VM limits should be visible on VM Overview page graphs
In a support case I found one of my VMs was being throttled because it was over disk write limit; the performance (other colors, not red) and limits (in red) should be on the graphs on the overview. This seriously impacts availability when VMs are being throttled and makes for an insidious and hard to understand issue. All performance limits should be visible! Please implement?
For the maintenance that doesn't require a reboot, customers can know it only through Scheduled Events API.https://docs.microsoft.com/en-us/azure/virtual-machines/maintenance-and-updates?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json#maintenance-that-doesnt-require-a-rebootSeveral customer requests easier way to grasp the affected resources and that history (e.g. dashboard).
Currently if you want to change the VM Size of Azure, VM is restarted. VM Resize shouldn't require downtime and it should be done in the backend. As CPU and RAM is still throttle when we use more resources then why can't we just remove the throttling limit and inform customer that VM is resized from A to D series when request is raised of resize?