A (automatically) disabled subscription will automatically have all VM's deallocated.
The discrepancy you showed above is likely just an internal caching lag between the 2 screens, as you mentioned in your update that it does eventually show as deallocated later on.
Is virtual machine really really deallocated?
Update - less than 24 hours later, all VMs show as Stopped (deallocated).
My MSDN Azure account is disabled and I think the monthly spending limit was exceeded. The VM Manager shows VS2017VM stopped (but not deallocated).
However, when I look at the VM details, it shows Stopped (deallocated).
Unfortunately, because my account is disabled (I guess until the end of the month) I can't seem to try another stop to fix this. What should I do?
Error details
VS2017VM: The subscription 'xxx' is disabled and therefore marked as read only. You cannot perform any write actions on this subscription until it is re-enabled. (Code: ReadOnlyDisabledSubscription)
Azure Virtual Machines
1 answer
Sort by: Most helpful
-
Karl Tremain 86 Reputation points Microsoft Employee
2021-08-20T11:22:59.103+00:00