Want to deploy a new Windows VM on Microsoft Azure? Today might not be your lucky day

It is shaping up to be a Black Wednesday for providers of online services after Microsoft Azure Virtual Machines users suffered lingering near-global glitches that prevented them from spinning up new Windows-based systems. According to Microsoft's status page, the downtime happened "as early as" 05:12 UTC today and has yet to …

[lansalot]

annnnd...

that's it back.

Wondering if any VMs left in a "Failed" state accrued cost, as technically they weren't deallocated?

Regardless... hours that took! Very little in the way of useful updates, and status.azure.com was over an hour before it mentioned anything. Not very impressive.

[Robert Grant]

Re: annnnd...

Do governments that use Windows VMs also end up as failed states?

[Peter-Waterman1]

Re: annnnd...

Why does Msft have built-in Global dependencies? Each region should be a separate entity so that doing something in region A, cant affect Region B. Without this it makes the concept of a region redundant. This is 101 stuff that Amazon has been doing since day one. Seems crazy that a public cloud provider the size of Azure gets away with such crap engineering.

[PeterM42]

Joining Office and Windows .....?

.........364½ or less

[katrinab]

Re: Joining Office and Windows .....?

I prefer to call it Office 356.

[Anonymous Coward]

They also had issues with autopilot pre-provisioning / auto-deployment this morning too.. so not just a VM thing.

[Anonymous Coward]

Cloud.

lol.

Beat your competitors and save money too! Bring it all in-house.