Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Thanks for reaching out to Q&A, we are looking into the issue and we will keep you posted for any updates.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Always giving error:
No available instances to satisfy this request. App Service is attempting to increase capacity. Please retry your request later or consider enabling Async Scaling on your app service plan: aka.ms/async-scaling. If urgent, this can be mitigated by deploying this to a new resource group.
Migrating to a different resource group was of no use, same error there as well.
Enforcing me to use a premium plan. Any one experienced anything like that and if yes, did you find any solution other than creating a new app itself?
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Thanks for reaching out to Q&A, we are looking into the issue and we will keep you posted for any updates.
AI answer
No available instances to satisfy this request indicates unavailable physical capacity for the requested App Service SKU in that region, so moving the resources to another resource group in the same region is not expected to resolve it; retry the scale operation later or select another suitable SKU or region.^1^
az appservice plan update \
--resource-group <resource-group> \
--name <app-service-plan> \
--async-scaling-enabled true \
--number-of-workers 1
Then retry the desired tier under Scale up (App Service plan). Async Scaling lets the platform continue seeking requested capacity, but an SKU change can still fail when there are not enough instances to satisfy the complete request.^3^ It is primarily useful for scale-out. It does not guarantee that B1, S1, or another constrained worker type will become available.Your quoted message is the documented capacity error, not the normal quota error:
No available instances to satisfy this requestSubscriptionIsOverQuotaForSkuQuota determines how many workers the subscription may use; it does not guarantee that Azure has physical capacity for that SKU at that time.^1^
Nevertheless, check for a second quota blocker:
Viewing or requesting quota requires the Quota Request Operator role or equivalent permission. A quota increase will not correct regional capacity exhaustion.
Open an Azure support request and provide:
Ask support to confirm capacity for the specific region, OS, deployment unit, and SKU. This is the practical escalation when retries and alternate SKUs continue failing.
Changing only the resource group does not change the existing plan’s deployment unit or webspace. Plans cannot be moved between webspaces after creation.^3^
If support confirms sustained regional exhaustion, the remaining supported alternative is another region. An App Service plan’s region cannot be changed; moving regions requires cloning or redeploying the app into a plan in that region. For Windows apps, Development Tools → Clone app may reduce the migration work. This is the point at which a new app/plan becomes necessary—not merely because B1 temporarily lacks capacity.
References