Virtual machine not starting for several days in East US region – possible regional issue?

Hi everyone,

We’ve been struggling with a persistent issue in the East US region and would appreciate some insight from the community or Microsoft team.

A few days ago, we changed the VM size (scaling), and it initially worked fine — the VM started successfully. However, for the past several days, the VM has consistently failed to start again, even after multiple attempts.

Here’s what we’ve tried so far:

• Restarting and redeploying the VM.
• Changing the VM size (SKU) -- no improvement.
• Verifying disks, NICs, and other dependencies -- all look healthy.
• Checking the Azure Status page -- it shows East US as healthy.

Unfortunately, due to policy restrictions, we cannot move the VM to another region at this time. That’s why we’re trying to determine whether this could be a regional capacity or platform issue in East US.

We’ve seen some deployment and start failures without clear error messages and in some cases, the activity log shows AllocationFailed, but it’s inconsistent.

Has anyone else experienced similar VM start failures or capacity problems in East US recently? If so, could you share:

• The approximate time window you noticed it,
• The VM size or SKU affected,
• Any confirmed information from Azure support.

We need to inform our management whether this is a localized platform issue or something specific to our deployment.

Thanks in advance for any updates or confirmation you can share.

Best regards,