Azure quota requirements

Updated August 18, 2026

Art2link ESB installs into your own Azure subscription, so it can only create what your subscription is already allowed to create. Confirm the quota for your license tier, in the region you are deploying to, before you start the install.

Every tier provisions one App Service Plan and two Azure SQL databases, called SQL1 and SQL2 below. A private Foundry instance adds three more resources. That is the whole list.

Step 1

Find your tier

What the install provisions

License tier	App Service Plan	SQL1	SQL2
Starter	B2 or B3	S0, 10 DTU	S0, 10 DTU
Grow	P0v4	S0, 10 DTU	S0, 10 DTU
Enterprise 2-core	P1mv4	S1, 20 DTU	S1, 20 DTU
Enterprise 4-core	P2mv4	HS_Gen5_2, 2 vCores	HS_Gen5_2, 2 vCores
Enterprise 8-core	P3mv4	HS_Gen5_2, 2 vCores	HS_Gen5_4, 4 vCores
Enterprise 16-core	P4mv4	HS_Gen5_4, 4 vCores	HS_Gen5_8, 8 vCores

Starter can land on either Basic size. Size your Basic quota for B3 and you are covered whichever it takes.

Step 2

Add the private Foundry resources, if you chose private

Every tier picks either a shared Foundry instance, run by Cerebrum City, or a private one in your own subscription. Shared needs no quota from you. Private adds these three, in the same region.

Private Foundry only

Resource	SKU or model
Azure AI Search	F0, Free
Foundry model deployment	gpt-5.4-mini, version 2026-03-17
Foundry model deployment	text-embedding-3-small

The F0 free search tier is capped per subscription and cannot be raised on request. If your free slot is already used, release it or provision a paid search tier.

Step 3

Check what you already have

You need Owner or Contributor on the subscription. Requests are free. Set Location to your deployment region on every check, because quota is granted per region.

Where to check each resource

Resource	Open	Then filter by
App Service Plan	My quotas	Provider Microsoft.Web, then search Basic or Premium v4
SQL1 and SQL2, DTU tiers (S0, S1)	My quotas	Provider Microsoft.Sql, then search DTU
SQL1 and SQL2, Hyperscale (HS_Gen5_*)	My quotas	Provider Microsoft.Sql, then search vCore. Counted separately from DTU.
Foundry models	Foundry quota page	Token per minute tab, then Request quota
Azure AI Search F0	Not raisable. See AI Search service limits.

If My quotas lets you raise it there, do that and you are done. If it does not, or the resource is not listed, use the forms in Step 4.

Step 4

Fill out the request

The forms ask for a region, a SKU and a new limit. These are the numbers to give them. Both databases sit on one logical server, so the DTU figure is the pair added together.

What to ask for, by tier

License tier	App Service Plan	SQL DTU, per server	SQL Hyperscale vCores
Starter	1 instance of B3	20 DTU	not used
Grow	1 instance of P0v4	20 DTU	not used
Enterprise 2-core	1 instance of P1mv4	40 DTU	not used
Enterprise 4-core	1 instance of P2mv4	not used	4 vCores
Enterprise 8-core	1 instance of P3mv4	not used	6 vCores
Enterprise 16-core	1 instance of P4mv4	not used	12 vCores

New limit is additive. Ask for your current limit plus the figure above, not the figure on its own, or you will be granted less than you had.

Azure support request, for App Service and Azure SQL

Open a new support request and enter:

Field	Value
Issue type	Service and subscription limits (quotas)
Subscription	The subscription you are installing into
Quota type	App Service for the plan, SQL Database for the two databases. File them as two requests.
Location	Your deployment region
SKU or pricing tier	Your App Service Plan from Step 1
New quota or New limit	Current limit plus the figure from the table above

Azure SQL, which quota type to pick

If you need	Quota type	Enter
Hyperscale vCores, 4-core tier and up	vCores per subscription	New quota, current plus the vCore figure
DTU headroom on the logical server	DTUs	Server name and New limit in DTU
A region your subscription has never used	Region access	Expected Consumption in vCores
Zone redundancy in that region	Zone Redundant Access (Availability Zones)	Expected Consumption in vCores

Foundry model quota, private Foundry only

On the Foundry quota page, Token per minute tab, use Request quota. For a large increase use the model quota increase form, which also asks for your subscription ID.

Field	Value
Model	gpt-5.4-mini, version 2026-03-17, and separately text-embedding-3-small
Region	Your deployment region, and the model must be offered there
Tokens per minute	Confirm the figure with Cerebrum City before filing

Small increases in a region with capacity are often approved automatically. Large increases, brand new subscriptions and constrained regions get routed to a person and can take a business day. Foundry quota changes need up to 15 minutes to propagate once approved.

Ready to install

App Service Plan, both databases, and the Foundry resources if you chose private, all clear in your deployment region. See Azure Marketplace for the install itself.