Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
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^
Options that preserve the existing app
- Try each acceptable non-Premium SKU separately
- Open Azure portal → App Service → Settings → Scale up (App Service plan).
- Select the lowest acceptable tier, such as B2, S1, or another displayed SKU, and select Apply.
- Request the minimum worker count, normally one, during the SKU change.
- If it succeeds, scale out afterward if more instances are required.
- Retry later Regional capacity changes over time. Repeating the operation later is the documented action for this exact capacity message. Avoid rapid repeated tier changes because App Service also limits the number of scale changes allowed within an hour.^2^
- Optionally enable asynchronous scaling Async Scaling is a preview feature supported for Basic, Standard, and Premium plans. Enable it on the existing plan with the minimum acceptable worker count:
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.az appservice plan update \ --resource-group <resource-group> \ --name <app-service-plan> \ --async-scaling-enabled true \ --number-of-workers 1
Distinguish capacity from quota
Your quoted message is the documented capacity error, not the normal quota error:
- Capacity:
No available instances to satisfy this request - Quota:
SubscriptionIsOverQuotaForSku
Quota 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:
- In the portal, search for Quotas.
- Select App Service (Public Preview).
- Filter by the affected subscription and region.
- Review the exact target SKU and Total Regional VM usage/limit.
- Request an increase only if the limit is insufficient.
Viewing or requesting quota requires the Quota Request Operator role or equivalent permission. A quota increase will not correct regional capacity exhaustion.
If every acceptable SKU remains unavailable
Open an Azure support request and provide:
- Subscription and region
- Windows or Linux
- Current SKU and every attempted target SKU
- Required worker count
- UTC timestamps
- Full scale-operation error from App Service plan → Activity log → failed operation → JSON
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