Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
Note
Azure AI Search is available through the Azure portal, REST APIs, and Azure SDKs. It also underpins Foundry IQ, the managed knowledge layer that transforms enterprise content into reusable, permission-aware knowledge bases for agents in the Microsoft Foundry portal.
Maximum limits on storage, workloads, and quantities of indexes and other objects depend on the pricing model of your Azure AI Search service.
Azure AI Search supports two pricing models, each with associated service tiers. The tier you select impacts the service limits outlined in this guidance.
- Dedicated: Fixed pricing measured by Search Units (SUs). Service tier options include: Basic, Standard (S1-S3, including S3 HD), Storage Optimized (L1-L2), and a Free tier with limited search service capabilities.
- Serverless (preview): Consumption-based pricing measured by Compute Units per hour (CU/hr) and per-GB/month for indexed storage. The current preview tier is: Serverless Developer. Limits are defined by per-index caps, per-service object counts, and Serverless throttling behavior.
Important
The Serverless Developer tier is currently in preview. This preview is provided without a service-level agreement and isn't recommended for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see Supplemental Terms of Use for Microsoft Azure Previews.
Billing for the Serverless Developer tier began on September 13, 2026. Charges for usage on or after that date appear on your Azure invoice. You aren't charged for usage before September 13, 2026.
The Serverless Developer tier doesn't support migration to or from other pricing tiers and some features available on other tiers aren't supported during Public Preview. Service limits, supported features, and pricing details may change before general availability.
During preview, the Serverless pricing model is supported only in specific regions.
To learn more, see Choose a pricing model and service tier.
Diagnose quota, capacity, or limit failures
Quota and capacity failures come from separate controls. Use the error from the completed operation to find which one applies.
If a create, scale, or upgrade operation is still running, wait for the provisioning state to become Succeeded or Failed. An operation in progress isn't evidence of a quota or capacity problem. If a scale operation fails, see Errors during scaling.
| Failure | Likely cause | First action |
|---|---|---|
| Service creation blocked in a subscription and region | Subscription quota | In the Quotas service, check the limit for your tier and region, then request more services. |
| Create, scale, or upgrade fails even though quota is available | Consider alternative regions and off-peak deployment | Check the footnotes in region support for high-demand tiers, then consider an alternative. |
| Replica, partition, tier, or object request rejected | Service or index limit | Compare your configuration and object counts with service limits and index limits. |
| The search service returns throttling responses under load | Throttling | Reduce the request rate or add search units. See Throttling limits. |
| Indexing fails near a storage or vector limit | Storage or vector quota | Compare storageSize with partition storage for disk and vectorIndexSize with vector index size limits for memory. |
| Indexer, skill, or vectorizer reports a 429 from another service | Azure OpenAI or other service quota | Follow the quota guidance for the service that issued the error, such as Azure OpenAI. |
Available subscription quota doesn't guarantee regional capacity, and requesting more quota doesn't resolve a capacity constraint. If the failure persists, open an Azure support request that includes the subscription, region, tier, requested configuration, full error text, UTC time, and any correlation or operation ID.
Subscription limits
You can create multiple billable search services (Basic and higher), up to the maximum number of services allowed at each tier, per region. For example, you can create up to 16 services at the Basic tier and another 16 services at the S1 tier within the same subscription and region. You can then create an additional 16 Basic services in another region for a combined total of 32 Basic services under the same subscription. For more information about service tiers, see Choose a pricing model and service tier.
You can raise maximum service limits by request. If you need more services within the same subscription, file a support request.
| Resource | Free 1 | Basic | S1 | S2 | S3 | S3 HD | L1 | L2 | Serverless Developer |
|---|---|---|---|---|---|---|---|---|---|
| Maximum services per region | 1 | 16 | 16 | 8 | 6 | 6 | 6 | 6 | 5 |
| Maximum search units (SU)2 | N/A | 3 SU | 36 SU | 36 SU | 36 SU | 36 SU | 36 SU | 36 SU | N/A |
1 You can have one free search service per Azure subscription. The free tier is based on infrastructure shared with other customers. Because the hardware isn't dedicated, scale-up isn't supported, and storage is limited to 50 MB. A free search service might be deleted after extended periods of inactivity to make room for more services.
2 Search units (SU) are billing units, allocated as either a replica or a partition. You need both. To learn more about SU combinations, see Estimate and manage capacity of a search service.
Service limits
In the Dedicated pricing model, plan capacity by multiplying replicas by partitions (search units).
| Resource | Free | Basic | S1 | S2 | S3 | S3 HD | L1 | L2 | Serverless Developer |
|---|---|---|---|---|---|---|---|---|---|
| Partitions | N/A | 3 1 | 12 | 12 | 12 | 3 | 12 | 12 | N/A |
| Replicas | N/A | 3 | 12 | 12 | 12 | 12 | 12 | 12 | N/A |
1 The Basic tier supports three partitions and three replicas, for a total of nine search units (SU) on new search services created after April 3, 2024. Older Basic services are limited to one partition and three replicas.
A search service is subject to a maximum storage limit (partition size multiplied by the number of partitions) or a hard limit on the maximum number of indexes or indexers, whichever limit comes first.
Service-level agreements (SLAs) apply to billable services that have two or more replicas for query workloads, or three or more replicas for query and indexing workloads. The number of partitions isn't an SLA consideration. For more information, see Reliability in Azure AI Search.
Free services don't have fixed partitions or replicas and share resources with other subscribers.
Partition storage (GB)
Per-service storage limits vary based on two factors: service creation date and region. Most supported regions offer higher limits for newer services.
This table shows the progression of storage quota increases in GB over time. Starting in April 2024, higher capacity partitions came online in the regions listed in the footnotes. If you have an older service in a supported region, check if you can upgrade your service to get higher storage limits.
| Service creation date | Basic | S1 | S2 | S3/HD | L1 | L2 | Serverless Developer |
|---|---|---|---|---|---|---|---|
| Before April 3, 2024 | 2 | 25 | 100 | 200 | 1,024 | 2,048 | N/A |
| April 3, 2024 through May 17, 2024 1 | 15 | 160 | 512 | 1,024 | 1,024 | 2,048 | N/A |
| After May 17, 2024 2 | 15 | 160 | 512 | 1,024 | 2,048 | 4,096 | N/A |
| After February 10, 2025 3 | 15 | 160 | 512 | 1,024 | 2,048 | 4,096 | N/A |
1 Higher capacity storage for Basic, S1, S2, and S3 in these regions. Americas: Brazil South, Canada Central, Canada East, East US, East US 2, Central US, North Central US, South Central US, West US, West US 2, West US 3, West Central US. Europe: France Central. Italy North, North Europe, Norway East, Poland Central, Switzerland North, Sweden Central, UK South, UK West. Middle East: UAE North. Africa: South Africa North. Asia Pacific: Australia East, Australia Southeast, Central India, Jio India West, East Asia, Southeast Asia, Japan East, Japan West, Korea Central, Korea South.