Are my Azure subscriptions configured incorrectly?

Hello Rusty Green ,

Greetings! Thanks for raising this question in the Q&A forum.

This is normal, expected behavior for Azure and it is not a misconfiguration on your account or tenant. New subscriptions, especially newly created pay-as-you-go subscriptions under an existing account or new billing accounts, start with low or zero regional quota for many resource types by design, as a fraud and capacity-protection measure. Azure's quota model is deliberately conservative on new subscriptions because it cannot yet establish a usage history for that subscription, and it is treating each new subscription as an unknown risk until you demonstrate legitimate usage or request quota explicitly. The fact that your requests get approved once submitted confirms your account itself is in good standing; the friction you are seeing is the default posture for all new subscriptions, not something specific to you.

A few important details that explain the pattern you're seeing:

Quota is scoped per subscription, per region, per resource provider, not globally Compute (Microsoft.Compute), App Service (Microsoft.Web), and Azure Database for PostgreSQL each maintain independent quota pools. This is why standing up one App Service backed by PostgreSQL can require separate approvals since the platform checks vCPU quota under Microsoft.Compute, worker/plan quota under Microsoft.Web, and any database-specific SKU quota separately, even though from your side it feels like one deployment.

This is more aggressive on brand-new subscriptions than on established ones As a subscription accrues usage history and stays in good standing, Microsoft's automated systems generally raise default quotas over time without you needing to ask, so the multi-day quota-request cycle tends to reduce significantly after your first few subscriptions and deployments in an account.

There is a self-service path for many, but not all, resource types Go to Quotas in the Azure Portal, filter by provider (Microsoft.Compute, Microsoft.Web, etc.) and region, and check whether the specific SKU shows a pencil/Request increase icon versus a support-request icon. Adjustable quotas can be raised instantly from this blade without opening a ticket; only non-adjustable quotas require a support request.

There is no current setting to pre-provision "reasonable defaults" across all services for new subscriptions This is a known pain point, and it does not have a self-service toggle today. If this materially affects your workflow, the actionable path is to submit product feedback through Azure's feedback channels, since this is a platform design decision rather than something support can override per-customer as a standing default.

If you consistently deploy the same stack, plan ahead For predictable multi-service deployments like App Service plus PostgreSQL, submit quota requests for all required providers up front as part of subscription provisioning, before you need to deploy, rather than reactively after a failed deployment. This avoids the multi-day serial wait you described.

This behavior is intentional platform design rather than an account defect, so there is no fix to apply on your end beyond requesting quota ahead of deployment and, where available, using the self-service Quotas blade instead of a support ticket.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.