*** is being affected by a service health event: Active - Virtual Machines allocation failures in East US

Hi NFaustino

Thank you for your patience regarding the ongoing Virtual Machines allocation failures in the East US region.

At this time, capacity in East US remains constrained due to sustained and heightened demand. Microsoft engineering and capacity teams are actively monitoring and working on regional capacity optimization; however, there is currently no definitive ETA for full resolution of this Service Health event.

Recent internal validations indicate that VM deployments have succeeded for certain VM sizes, suggesting that availability has improved intermittently. As a result, your deployment may succeed if retried, depending on the requested SKU and zone availability.

Recommendations:

Retry VM creation using the same or alternative VM SKUs.

Specify different Availability Zones, where applicable.

Consider deploying workloads to a nearby region such as East US 2 to reduce latency impact.

Continue monitoring the Azure Service Health dashboard for personalized updates.

For any specific, tailored capacity guidance, could you please let us know will check with capacity team.

This allows the Capacity team to review your exact requirements (VM size, quantity, region, and urgency) and provide targeted recommendations based on current availability.

For additional context on allocation failures and mitigation steps, please refer to the official documentation:

https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/allocation-failure