Share via

Subscription `quotaId` invisibly gates service availability

Kevin Zhao 0 Reputation points
2026-06-04T01:23:44.8333333+00:00

Hi everyone,

We are migrating a production system from Railway and Supabase to Azure. I applied to the Microsoft for Startups program and received $1,000 in Azure credits after validating my LinkedIn and company profiles.

The first 24 hours of trying to provision basic services have been frustrating, and I am hoping the community can help me understand whether this behavior is expected for startup-credit subscriptions.

After debugging with Claude and the Azure CLI, my tentative conclusion is that the subscriptions I created are using the Sponsored_2016-01-01 offer type.

However, the Azure portal does not make this clear:

  • The Subscription Overview page shows: “Plan: Microsoft Azure Plan.”
  • Billing Properties shows the same plan, along with billing account and invoice information.
  • I cannot find anywhere in the portal that clearly displays the underlying offer type or the restrictions associated with it.

PostgreSQL Flexible Server availability

Azure Database for PostgreSQL Flexible Server appears to be unavailable in many regions for my subscription.

Most regions return the following error:

LocationIsOfferRestricted

The error message links to aka.ms/postgres-request-quota-increase, but that page provides generic quota-increase guidance and does not seem to address restrictions based on subscription offer type or regional availability.

So far, only Canada Central and Central US appear to work. East US and East US 2 return an error similar to:

Subscription “Azure subscription 1” is not allowed to provision in “East US.”

Azure OpenAI model availability

Azure OpenAI appears to be limited to GPT-4.1-mini. All other GPT models show “No Quota.”

Questions

How can I move away from the Sponsored_2016-01-01 offer type?

Every subscription I create appears to use this offer type, even when I select “Add a different type of subscription” and choose Pay-As-You-Go.

Is there a documented way to see all limits and restrictions imposed on an account or subscription?

I would especially like to understand regional service restrictions, quota limitations, and model availability before planning a production migration.

What response time should I expect from support?

I submitted an Azure OpenAI quota-increase request two days ago and have not received a response. I also filed a support ticket for PostgreSQL Flexible Server this morning and have not received a response after eight hours.

Any guidance from people who have used Microsoft for Startups credits for production workloads would be greatly appreciated.

Azure | Azure Startups
Azure | Azure Startups

Startups: Companies that are in their initial stages of business and typically developing a business model and seeking financing.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Kevin Zhao 0 Reputation points
    2026-06-04T02:47:17.8266667+00:00

    The AI answer clarifies the situation a bit. But,

    First, none of that is documented anywhere. To me it's one surprise after another surprise.
    Second, I tried to create a new subscription with Pay-As-You-Go offer type but it still somehow fall under "Sponsored" offer type after I check it with CLI.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-06-04T01:24:13.01+00:00

    Startup credits from Microsoft for Startups are delivered through a sponsored Azure subscription. These subscriptions can have restrictions that don’t apply to standard pay-as-you-go offers, including:

    • Regional limitations for certain services
    • Service-type limitations
    • Different or lower default quotas

    This behavior is expected for non-paid offers in general. For example, Visual Studio subscriber credits explicitly note that:

    • Some geographies may not be available for creating VMs and Azure services
    • Certain service types may not be available
    • Default quotas can be lower than on paid subscriptions

    The same pattern applies conceptually to sponsored/startup-credit subscriptions: the underlying offer can restrict regions, services, and quotas even when the portal shows “Microsoft Azure Plan.”

    To move production workloads off a restricted offer, the supported pattern is:

    1. Create or use a standard pay-as-you-go–rated subscription (for example, a pay-as-you-go offer or an Azure plan with pay-as-you-go rates).
    2. Move resources from the sponsored subscription to the new subscription using the documented “Move resources to new resource group or subscription” flow.
    3. If the subscription is tied to a specific billing account or sponsorship, work with Support to adjust which subscription is associated with the sponsorship or credits.

    When switching offers or moving subscriptions, be aware:

    • Some offers prohibit production use; production resources may need to be moved to another subscription.
    • Any quota increases above default limits are reset when switching offers.
    • Usage and billing data before an offer change isn’t kept, so it should be exported before switching.

    For Microsoft for Startups specifically:

    • Startup credits are applied to a sponsored Azure subscription.
    • Credits apply to eligible Azure services that are billed as standard Azure consumption.
    • Non-Azure products, support plans, marketplace items, and some other services may not be covered.
    • Startup credits and benefits must be activated with the same Microsoft Account used for program registration; work or school accounts can cause activation issues.
    • Once credits are exhausted, the subscription transitions to pay-as-you-go billing.

    If regional or service availability is blocked by the sponsored offer, Support is the escalation path:

    • Program Support (via the Microsoft for Startups portal) handles onboarding, credit activation, benefit redemption, billing profile issues, and entitlement corrections.
    • Standard Azure Support handles service-specific issues such as regional availability, quota increases, and platform errors.

    For billing and sponsorship alignment (for example, when credits apply to the wrong subscription or billing account):

    • Support can move a sponsorship to the correct subscription and reconcile existing bills.
    • Moving subscriptions between billing accounts can change an offer from “Sponsorship” to “Pay-As-You-Go,” which affects how credits apply; this typically requires Support intervention to correct.

    There is no single public document in the provided material that lists all per-offer restrictions (regions, models, quotas) for sponsored/startup-credit subscriptions. The documented guidance is:

    • Some non-paid or credit-based offers have restricted geographies, services, and quotas.
    • Startup credits are intended for building and scaling on Azure, with eligibility and increases based on verified progress and sustained usage.
    • For detailed, subscription-specific limits (including regional restrictions and model availability), Support must be engaged.

    Regarding support response times, the context only notes that:

    • Quota increases and sponsorship/billing corrections are handled via support requests.
    • There is no documented SLA for response time in the provided material.

    For the current situation, the actionable path based on the documentation is:

    1. Keep the sponsored/startup subscription for development and credit-backed usage.
    2. Create a standard pay-as-you-go subscription for production workloads that require broader regional and service availability.
    3. Use the documented “Move resources to new resource group or subscription” process to migrate production resources as needed.
    4. Open or continue working with:
      • Program Support (from the Microsoft for Startups portal) for:
        • Clarifying which subscription is sponsored
        • Adjusting which subscription the startup credits apply to
        • Entitlement corrections if services are unexpectedly blocked
      • Azure Support for:
        • Regional restrictions (e.g., PostgreSQL Flexible Server)
        • Azure OpenAI quota and model availability

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.