Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
The required next action is to open a billing and subscription support request for the failed Free Trial-to-Pay-As-You-Go conversion, because Free Trial subscriptions are not eligible for quota increases and the portal error does not identify why the conversion failed.
1. Escalate the failed subscription upgrade
Because the portal upgrade has already failed with “We can't upgrade your subscription right now. Please try again later,” do not submit another quota request yet.
- In the Azure portal, go to Help + support.
- Select New support request.
- Choose the category for Billing or Subscription management.
- Select the affected Free Trial subscription.
- Use a title such as:
Free Trial to Pay-As-You-Go upgrade fails with “We can't upgrade your subscription right now”
- Include:
- The complete upgrade error.
- The approximate time and time zone of the failed attempt.
- Confirmation that the subscription still shows Free Trial under Subscriptions → affected subscription → Overview.
- A request to identify and remove the billing or account restriction preventing self-service conversion.
- The statement: “Do not deploy resources or initiate charges. Assistance is requested only to resolve the subscription conversion error.”
Azure provides billing and subscription support through support requests.^1^ Creating the request requires Owner, Contributor, Support Request Contributor, or equivalent Microsoft.Support/* permissions at subscription scope; account-specific billing changes can additionally require the billing administrator.^2^
Submitting a support request does not itself authorize deployment. However, completing the upgrade changes the subscription to Pay-As-You-Go billing, so approve that conversion only when ready.
2. Why the B1 quota request is currently blocked
Free Azure Trial subscriptions are not eligible for limit or quota increases.^3^ App Service documentation also states that free, trial, and other restricted offers can have a default quota of zero or may not support the requested increase.^4^
Therefore:
- The current Free Trial offer can prevent the East US B1 quota from being raised.
- The failed upgrade and the B1 quota restriction are separate operations.
- Resolving the upgrade does not automatically guarantee or approve B1 capacity.
The official upgrade path is Subscriptions → affected subscription → Upgrade subscription, followed by payment-method and identity verification when requested.^5^ Since that path already produced an error, billing support must investigate the account-specific failure; the available information does not establish whether it is caused by payment validation, identity verification, permissions, or another billing restriction.
3. Request East US Basic B1 only after conversion succeeds
After support confirms that the subscription shows a standard paid offer:
- In the Azure portal, search for Quotas.
- Select App Service (Public Preview).
- Filter by:
- The affected subscription
- East US
- The exact Basic B1 SKU
- Select the B1 quota entry.
- Enter 1 as the new total limit—not “1 additional.”
- Submit the request.
- Wait until the Quotas page displays the updated limit before creating the App Service plan.
This requires Quota Request Operator or equivalent permission. App Service quota is scoped independently by subscription, region, deployment type, and SKU.^4^
If the automated request cannot be fulfilled, use the support-request option presented in the Quotas experience. Include:
- Region: East US
- SKU: Basic B1
- Current usage: 0
- Current limit: 0
- Requested new total: 1
- The complete deployment or quota error
Microsoft can review and potentially approve the request, but approval cannot be guaranteed. Quota controls what the subscription may deploy; it does not guarantee current physical B1 capacity in East US. If the resulting error says “No available instances” rather than a quota error such as SubscriptionIsOverQuotaForSku, the issue is regional capacity; the documented alternatives are to retry later, choose another compatible SKU, or use another suitable region.^4^
No deployment or charge occurs merely from checking quota or filing these support requests. Charges can begin only after the paid subscription is active and billable resources are used.
References