Is North Europe running short on VM capacity?

Different VM options showing up across subscriptions doesn’t, by itself, prove the whole region is unavailable. Check the exact subscription, VM size, and deployment settings that fail, and keep the full error message. A size being listed is not a guarantee that Azure can allocate it right now.

If this is blocking a deployment, share those details with Azure support and test the same workload in a fallback region or with another VM size. Don’t rely on a fallback until you’ve confirmed it can actually deploy.

There are reports of B-series allocation problems, and some people are seeing issues with other VM families too. That still doesn’t tell us whether this is a short-lived capacity crunch, a wider regional constraint, or something specific to a subscription. I’d plan as though capacity may be tight, rather than assume there’s one clear cause.

If a VM must be restarted reliably, be careful about deallocating it just to save compute charges. After deallocation, getting the same size back may not be possible at that moment.

One confusing part is that a pricing reservation and a capacity reservation are not the same thing. A pricing reservation can reduce costs without holding a VM slot for you. A capacity reservation may not be available for a size that Azure cannot currently allocate, so it may not solve an immediate shortage.

Check which kind you’re trying to create, and confirm that the specific VM size is allocatable before building a plan around a reservation.