There should be the ability to 'cancel' a command executed in the RUN Command within Azure virtual machines.

Put this with "Run Command" to 'Remove Safemode' boot because I have seen many people have to spend hours trying to remove that.

if not, do we have a plan to support that?

I thought by using an automation account to run the powershell execute via commands in VM would be my solution.
I tested the RunPowerShellScript with:
Start-Process "C:\windows\system32\notepad.exe"
but it states that it can not find the path.
What is missing here?

Werk account

Werk account

Please allow to add Windows Virtual Desktop pool to a proximity group with existing VMs

Have possibility to replicate on-premise (Hyper-V, VMware) Virtual Machines with UEFI and SecureBoot enabled via Azure Site Recovery.

Nowadays replication of VMs with SecureBoot is not supported:
https://docs.microsoft.com/en-us/azure/site-recovery/vmware-physical-azure-support-matrix#storage

Se necesita que la VM se pueda abrir para corregir errores de conexión. En una máquina fisica, esta se enciende y se corrigen los errores, pero si no podemos abrir y corregir es un verdadero problema. Actualmente, si la VM pierde conexíón es como si se desapareciera una máquina física o se hiciera invisible.

Today, we can leverage "Planned Maintenance" to avoid any impact on VMs. But, the maintenance may fail if it cannot find appropriate resource to re-deploy a VM. It would be great if the 35 days maintenance window can be reset in that circumstance. In some mission-critical system, it's hard to secure sufficient time frequently for maintenance (let's say once a month). Thus, extending the window is needed in case of failure.

Currently, there aren't any ARM64 Windows VMs available. This e.g. blocks Continuous Integration scenarios for apps that want to support Windows on ARM (for e.g. the Microsoft Surface Pro X), like NodeJS: https://github.com/nodejs/build/pull/2408#issuecomment-671707155

While cross-compilation from a x64 host is possible, it's not possible to run automated tests on the ARM64 platform until VM images become available for that architecture.

Please add VM images for Windows ARM64 to Azure.

https://support.microsoft.com/en-us/help/4018933/the-default-size-of-windows-server-images-in-azure-is-changed-from-128 - Remove this article . I think default size is 128.

https://support.microsoft.com/en-us/help/4018933/the-default-size-of-windows-server-images-in-azure-is-changed-from-128 - Remove this article . I think default size is 128.

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)

thanks azure student. i like it. i still discover what the others content in azure. but so far, i like it. thanks :)

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.

bhimashankars@shravikasanstha.com