Azure-Communitysupport
Fragen stellen, Antworten erhalten und mit Microsoft-Technikern und Experten aus der Azure-Community in Verbindung setzen
MSDN-Forum
Antworten von Microsoft auf technische Azure-Fragen
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
Stimmen
MS Learn/ Sandbox Creation Error
Forum: Azure Virtual Machines
32
Stimmen
Forum: Azure Virtual Machines
27
Stimmen
Multiple IP addresses for a VM to be able to use Multiple HTTPS endpoints
Forum: Azure Virtual Machines
26
Stimmen
Azure VMs no longer see themselves via public virtual IP
Forum: Azure Virtual Machines
73
Antworten
MS Learn/ Sandbox Creation Error
Forum: Azure Virtual Machines
51
Antworten
VM becomes unresponsive or disk becomes read-only
Forum: Azure Virtual Machines
42
Antworten
Question about deploying multiple VMs with template
Forum: Azure Virtual Machines
37
Antworten
Forum: Azure Virtual Machines
StackOverflow
Antworten der Community auf Entwicklungsfragen
34
Stimmen
Server Fault
Antworten der Community auf Fragen zur Verwaltung von System und Netzwerk
15
Stimmen
10
Stimmen
Feedback zu Azure
Möchten Sie aufgrund Ihrer Erfahrung mit Azure neue Ideen oder Vorschläge einbringen?
Autoscaling in & out timewindow
Currently there is no documents explain the default timewindow for autoscaling in & out when creating a new VMSS. For scale out, the default number is 10, which shown on the Portal where it can be modified directly, while for scale in, we can only find it on template.So, hope the scale in timewindow can also be displayed on the portal, or demonstrate clear on the document. Thank you
Share Manage Disk across subscriptions within same tenant
Add support to allow Azure VM to attach Managed Disks from other subscriptions within the same tenant.For example, in my Azure account, I have two Azure subscriptions... I have a VM in Subscription A, and I would like to be able to attach a unattached Managed Disk available on Subscription B. As sharing VHDX is not support on Azure Storage. It would be great if users are allow to share Managed Disk across multiple subscriptions within a single Azure tenant.
Add multiple filter to list Resource SKU -List API`s
Currently there is only one filter available for Resource SKU -List APIGET https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Compute/skus?api-version=2019-04-01&$filter={$filter}This provide multiple results which are of not much use, If you can help us to add more filter like ( Virtual machine or VM size) which will be helpful in simplified search
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
5203
Stimmen
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
Stimmen
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.
1434
Stimmen
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
Stimmen
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?
Virtual Machine Image API - Include OS disk size info
Virtual Machine Image API reference: https://docs.microsoft.com/en-us/rest/api/compute/virtualmachineimages/getManaged Image API reference: https://docs.microsoft.com/en-us/rest/api/compute/images/getThe returned objects from the virtual machine images API do not include information of the image size on the OS disk, whereas the API for managed images do include this information. This prevents the possibility of creating a solution to verify whether a potential deployment of a VM has appropriately sized disks or not based on the selected marketplace image, while this capability is present if the deployment is using a managed image. I don't see why there shouldn't have feature parity in this regard between the two API namespaces, given how closely related they seem.
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).