Menu

Azure AllocationFailed, SkuNotAvailable and quota errors: which is which, and which one a retry fixes
📰

Azure AllocationFailed, SkuNotAvailable and quota errors: which is which, and which one a retry fixes

DEV Community: cloud·Gonzalo Gjuka·2 days ago
#QfJPwZUs
#devtocloud#devto#dev#size#quota
Reading 0:00
15s threshold

An r/AZURE thread this week (40 comments) was looking for a small database in West Europe and could not find a single available size; the replies mixed capacity, retiring sizes and quota. Azure returns three different errors that look the same from the portal: AllocationFailed , SkuNotAvailable and the quota one, OperationNotAllowed . Each has a different cause and a different fix, and only one of them can be solved by retrying. It is Azure's counterpart to OCI's "Out of host capacity", which has its own note with a retry loop . Everything below comes from learn.microsoft.com; the sources are at the end.

The three errors

AllocationFailed or ZonalAllocationFailed : "Allocation failed. We do not have sufficient capacity for the requested VM size in this region". This is capacity: right now there are no free hosts for that size in the region or zone. It shows up on create, on starting a deallocated VM or on resizing one.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.