Azure-Communitysupport
Fragen stellen, Antworten erhalten und mit Microsoft-Technikern und Experten aus der Azure-Community in Verbindung setzen
Einführung in Azure on Q&A
Finden Sie Antworten auf Ihre technischen Fragen zu Azure-Produkten und -Diensten. Tauschen Sie sich mit Experten von Microsoft und aus der Community aus, teilen Sie Feedback, und lernen Sie aus den Erfahrungen anderer Benutzer. Azure on Q&A ist auf der Microsoft Q&A-Website verfügbar und ersetzt das MSDN-Forum. Sie können jedoch weiterhin die Forumsarchive durchsuchen.
Archiv des MSDN-Forums
Antworten von Microsoft und der Community auf ältere technische Fragen zu Azure
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
StackOverflow
Antworten der Community auf Entwicklungsfragen
35
Stimmen
Server Fault
Antworten der Community auf Fragen zur Verwaltung von System und Netzwerk
15
Stimmen
10
Stimmen
Feedback zu Azure
Ideen oder Vorschläge auf Grundlage Ihrer Erfahrungen mit Azure einbringen
Roadmap for "Azure AD login VM extension" to go GA
Looking to integrate VM login to AAD using the extension in preview described at https://docs.microsoft.com/en-us/azure/virtual-machines/linux/login-using-aad.Technically all working swimmingly well, but the log-in includes a warning message that the feature isn't for use in production.What's the guidance when this is expected to go GA?Raising here as suggested in handling of support ticket #120101924005145.
Make the port ip-adresses a list instead of a single input field
Hi, I would like a port ip-adresses to be displayed as a list where you can give each ip-adress a name. This would help me administrate the list of ip-adresses.
VM size which can be allocated on real-time
When user get the error "allocation Failed" at deploying the VM frequently, the user wants the feature to check the VM size which can be allocated by Azure Portal or Azure PowerShell / CLI.
Unable to mount lvm os disk snapshot on other vm for troubleshooting issue.
Yesteday , our one of the vm was not booting and going to emergency mode due to issue of invalid entry in fstab and unfortunalty we don't have root password . so thought to take sanpshot of root disk and create new disk with sanpshot and mount to other vm and change entry in fstab . but as os disk root partition was part of lvm so I was unable to mount it on other vm ...it was displaying error message "mount: unknown filesystem type 'LVM2_member'" lvm something . [root@azre3lpdukd01 ~]# mount /dev/sdj4 /mnt/troubleshootingdiskmount: unknown filesystem type 'LVM2_member'I have referred document https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/troubleshoot-recovery-disks-portal-linux.Kindly let us know if any solution for this.regardsbalaji mundhe
5247
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).
1459
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.
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.
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?
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?
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).