You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|[Higher capacity and more vector quota at every tier (same billing rate)](search-limits-quotas-capacity.md#service-limits)| Infrastructure | Partition sizes are now even larger for Standard 2 (S2), Standard 3 (S3), and Standard 3 High Density (S3 HD) for all services created after April 3, 2024. If you create a new service now, you get the larger partitions. If you created a new service between April 3 and May 17, you get the larger partitions automatically. <br><br>Storage Optimized tiers (L1 and L2) also have more capacity. L1 and L2 customers must create a new service to benefit from the higher capacity. There's no in-place upgrade at this time. <br><br>Extra capacity is now available in [more regions](search-limits-quotas-capacity.md#supported-regions-with-higher-storage-limits): South Africa North, Germany North, Germany West Central, Switzerland West, East US 2 EUAP/PPE, and Azure Government (Texas, Arizona, and Virginia).|
26
+
|[Higher capacity and more vector quota at every tier (same billing rate)](search-limits-quotas-capacity.md#service-limits)| Infrastructure | Partition sizes are now even larger for Standard 2 (S2), Standard 3 (S3), and Standard 3 High Density (S3 HD) for all services created after April 3, 2024. If you create a new service now, you get the larger partitions. If you created a new service between April 3 and May 17, you get the larger partitions automatically. <br><br>Storage Optimized tiers (L1 and L2) also have more capacity. L1 and L2 customers must create a new service to benefit from the higher capacity. There's no in-place upgrade at this time. <br><br>Extra capacity is now available in [more regions](search-limits-quotas-capacity.md#supported-regions-with-higher-storage-limits): Germany North, Germany West Central, South Africa North, Switzerland West, and Azure Government (Texas, Arizona, and Virginia).|
27
27
|[OneLake files and shortcuts integration (preview)](search-how-to-index-onelake-files.md)| Feature | New indexer for OneLake files and OneLake shortcuts. If you use Microsoft Fabric and OneLake for data access to Amazon Web Services (AWS) and Google data sources, use this indexer to import external data into a search index. This indexer is available through the Azure portal, the [2024-05-01-preview REST API](/rest/api/searchservice/data-sources/create-or-update?view=rest-searchservice-2024-05-01-preview&preserve-view=true), and Azure SDK beta packages. |
28
28
|[Relevance tuning and search results customization](vector-search-how-to-query.md)| Feature | Three enhancements improve vector search relevance. <br><br>First, you can now set thresholds on vector search results to exclude low-scoring results. <br><br>Second, you can set `MaxSizeTextRecall` and `countAndFacetMode` in hybrid queries to specify the maximum number of documents that can be recalled using text query in hybrid (text and vector) search. Previously, the maximum was fixed at 1,000. If you have more matches, you can now specify a higher limit to get more results back. <br><br>Third, for hybrid queries, you can set a weight on vector queries to have more or less importance than the nonvector query. |
29
29
|[Binary vectors support](/rest/api/searchservice/supported-data-types)| Feature |`Collection(Edm.Byte)` is a new supported data type. This data type opens up integration with the [Cohere v3 binary embedding models](https://cohere.com/blog/int8-binary-embeddings) and custom binary quantization. Narrow data types lower the cost of large vector datasets. See [Index binary data for vector search](vector-search-how-to-index-binary-data.md) for more information.|
Copy file name to clipboardExpand all lines: includes/azure-search-limits-per-service.md
+11-20Lines changed: 11 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,8 +13,8 @@ ms.custom: include file, build-2024
13
13
Search service limits for storage, partitions, and replicas vary by service creation date, with higher limits for newer services in supported regions. Limits vary by service creation date:
14
14
15
15
+[Before April 3, 2024](#before-april-3-2024)
16
-
+[After April 3, 2024](#after-april-3-2024)
17
-
+[After May 17, 2024 (L1 and L2 only)](#after-may-17-2024)
16
+
+[Between April and May 2024 (Basic, S1, S2, S3, S3 HD)](#after-april-3-2024)
17
+
+[After May 17, 2024 (L1 and L2)](#after-may-17-2024)
18
18
19
19
A search service is subject to a maximum storage limit (partition size multiplied by the number of partitions) or by a hard limit on the [maximum number of indexes](../articles/search/search-limits-quotas-capacity.md#index-limits) or [indexers](../articles/search/search-limits-quotas-capacity.md#indexer-limits), whichever comes first.
20
20
@@ -33,13 +33,9 @@ Free services don't have fixed partitions or replicas and they share resources w
33
33
34
34
### After April 3, 2024
35
35
36
-
For new services created after April 3, 2024:
37
-
38
-
+ Basic tier can have up to three partitions and three replicas, and a total of nine search units (SU).
39
-
+ Basic, S1, S2, S3 have more storage per partition, ranging from 3-7 times more, depending on the tier.
40
-
+ Your new search service must be in a [supported region](#supported-regions-with-higher-storage-limits) to get the extra capacity for Basic and other tiers.
41
-
42
-
Currently, there's no in-place upgrade. You should [create a new search service](/azure/search/search-create-service-portal) to benefit from the extra storage.
36
+
+ Basic tier supports three partitions and three replicas, for a total of nine search units (SU). It also has larger partitions.
37
+
+ S1, S2, S3, and S3 HD have larger partitions, ranging from 3-7 times more, depending on the tier.
38
+
+ Higher capacity is limited to [new search services](/azure/search/search-create-service-portal) in [supported regions](#supported-regions-with-higher-storage-limits). There is no in-place upgrade at this time.
@@ -50,13 +46,8 @@ Currently, there's no in-place upgrade. You should [create a new search service]
50
46
51
47
### After May 17, 2024
52
48
53
-
S2, S3, and S3 HD have larger partition sizes starting on May 17, 2024. If you created an S2 or higher search service after April 3, the higher partition size becomes available automatically. If you're running an older search service, you must [create a new search service](/azure/search/search-create-service-portal) to get the higher limits.
54
-
55
-
Storage Optimized tiers (L1 and L2) now have larger partitions at the current pricing.
56
-
57
-
+ S2, S3, S3 HD automatically have more storage per partition on search services running on the April 3 infrastructure, or on new services created after May 17.
58
-
+ L1 and L2 have more partition storage and compute power, but you must create a new service.
59
-
+ Your new search service must be in a [supported region](#supported-regions-with-higher-storage-limits) to get the extra storage.
49
+
+ L1 and L2 have more partition storage and compute power.
50
+
+ Higher capacity is limited to [new search services](/azure/search/search-create-service-portal) in [supported regions](#supported-regions-with-higher-storage-limits). There is no in-place upgrade at this time.
@@ -69,23 +60,23 @@ Storage Optimized tiers (L1 and L2) now have larger partitions at the current pr
69
60
70
61
Services must be in one of the following regions to get the extra storage. Watch for announcements in [What's New in Azure AI Search](/azure/search/whats-new) for expansion to other regions.
71
62
72
-
### Roll out on May 17 2024
63
+
### Available starting on May 17, 2024
73
64
74
65
| Country | Regions providing extra capacity per partition |
0 commit comments