Azure charges for SSD still occur when VM is stopped

#1

I followed Donovan Brown’s post here to create a build pipe line for VB6. So as to avoid charges I turned the VM off except for when I needed to build.

However my subscription (that comes with my developer MSDN subscription) is now disabled due to overspending and I am trying to understand why.

I can see that a two resource names containing osdisk have charges of over $25 Their resource group name is vb6Agent.

Why would these be incurring charges when the VM is stopped?

I tried putting a support ticket into Azure but although the subscription can be picked in a dialog box, I cannot submit the ticket… maybe because the subscription is disabled.

[Update]
It turned out that I had selected a premium SSD and charges for the fast disk still incur when the VM is stopped.

0 Likes

#2
0 Likes