Merge pull request #269645 from HeidiSteen/heidist-april3

[azure search] vector megastore & compression docs (azure search, april 3 release)

Author: American-Dipper

articles/search/TOC.yml

@@ -188,8 +188,6 @@
       href: search-sku-tier.md
     - name: Service limits
       href: search-limits-quotas-capacity.md
-    - name: Vector index size limits
-      href: vector-search-index-size.md
     - name: Plan capacity
       href: search-capacity-planning.md
     - name: Plan and manage costs
@@ -254,6 +252,10 @@
     items:
     - name: Create a vector store
       href: vector-search-how-to-create-index.md
+    - name: Vector quotas and staying under limits
+      href: vector-search-index-size.md
+    - name: Configure quantization and storage (preview)
+      href: vector-search-how-to-configure-compression-storage.md
     - name: Configure a vectorizer (preview)
       href: vector-search-how-to-configure-vectorizer.md
     - name: Chunk documents

articles/search/index.yml

@@ -42,8 +42,10 @@ landingContent:
         links:
           - text: Vectors in Azure AI Search
             url: vector-search-overview.md
-          - text: Integrated vectorization (preview)
+          - text: Built-in vectorization (preview)
             url: vector-search-integrated-vectorization.md
+          - text: Built-in scalar quantization (preview)
+            url: vector-search-how-to-configure-compression-storage.md
           - text: Retrieval Augmented Generation (RAG)
             url: retrieval-augmented-generation-overview.md
       - linkListType: quickstart

articles/search/media/search-create-service-portal/select-pricing-tier.png

@@ -10,7 +10,7 @@ ms.service: cognitive-search
 ms.custom:
   - ignite-2023
 ms.topic: conceptual
-ms.date: 01/10/2024
+ms.date: 04/03/2024
 ---
 
 # Estimate and manage capacity of a search service
@@ -85,7 +85,7 @@ With a rough estimate in hand, you might double that amount to budget for two in
 
 Dedicated resources can accommodate larger sampling and processing times for more realistic estimates of index quantity, size, and query volumes during development. Some customers jump right in with a billable tier and then re-evaluate as the development project matures.
 
-1. [Review service limits at each tier](./search-limits-quotas-capacity.md#index-limits) to determine whether lower tiers can support the number of indexes you need. Across the Basic, S1, and S2 tiers, index limits are 15, 50, and 200, respectively. The Storage Optimized tier has a limit of 10 indexes because it's designed to support a low number of very large indexes.
+1. [Review service limits at each tier](./search-limits-quotas-capacity.md#service-limits) to determine whether lower tiers can support the number of indexes you need. Across the Basic, S1, and S2 tiers, index limits are 15, 50, and 200, respectively. The Storage Optimized tier has a limit of 10 indexes because it's designed to support a low number of very large indexes.
 
 1. [Create a service at a billable tier](search-create-service-portal.md):
 
@@ -208,7 +208,11 @@ If your search service appears to be stalled in a provisioning state, check for
 
 ## Partition and replica combinations
 
-A Basic service can have exactly one partition and up to three replicas, for a maximum limit of three SUs. The only adjustable resource is replicas. You need a minimum of two replicas for high availability on queries.
+On search services created before April 3, 2024: Basic can have exactly one partition and up to three replicas, for a maximum limit of three SUs. The only adjustable resource is replicas. 
+
+On search services created after April 3, 2024 in [supported regions](search-limits-quotas-capacity.md#supported-regions-with-higher-storage-limits): Basic can have up to three partitions and three replicas. The maximum SU limit is nine to support a full complement of partitions and replicas.
+
+For search services on any billable tier, regardless of creation date, you need a minimum of two replicas for high availability on queries.
 
 All Standard and Storage Optimized search services can assume the following combinations of replicas and partitions, subject to the 36-SU limit allowed for these tiers. 
 

articles/search/search-capacity-planning.md

@@ -9,13 +9,14 @@ ms.author: heidist
 ms.service: cognitive-search
 ms.custom:
   - ignite-2023
+  - references_regions
 ms.topic: conceptual
-ms.date: 03/05/2024
+ms.date: 04/03/2024
 ---
 
 # Create an Azure AI Search service in the portal
 
-[**Azure AI Search**](search-what-is-azure-search.md) adds vector and full text search as an information retrieval solution for the enterprise, and for traditional and generative AI scenarios.
+[**Azure AI Search**](search-what-is-azure-search.md) is a vector and full text information retrieval solution for the enterprise, and for traditional and generative AI scenarios.
 
 If you have an Azure subscription, including a [trial subscription](https://azure.microsoft.com/pricing/free-trial/?WT.mc_id=A261C142F), you can create a search service for free. Free services have limitations, but you can complete all of the quickstarts and most tutorials, except for those featuring semantic ranking (it requires a billable service).
 
@@ -29,7 +30,7 @@ The following service properties are fixed for the lifetime of the service. Cons
 
 + Service name becomes part of the URL endpoint ([review tips for helpful service names](#name-the-service)).
 + [Tier](search-sku-tier.md) (Free, Basic, Standard, and so forth) determines the underlying physical hardware and billing. Some features are tier-constrained.
-+ [Service region](#choose-a-region) can determine the availability of certain scenarios. If you need high availability or [AI enrichment](cognitive-search-concept-intro.md), create the resource in a region that provides the feature. 
++ [Service region](#choose-a-region) can determine the availability of certain scenarios and higher storage limits. If you need availability zones or [AI enrichment](cognitive-search-concept-intro.md) or more storage, create the resource in a region that provides the feature. 
 
 ## Subscribe (free or paid)
 
@@ -88,11 +89,33 @@ Service name requirements:
 
 Azure AI Search is available in most regions, as listed in the [**Products available by region**](https://azure.microsoft.com/global-infrastructure/services/?products=search) page.
 
+We strongly recommend the following regions because they provide [more storage per partition](search-limits-quotas-capacity.md#service-limits), three to seven times more depending on the tier, at the same billing rate. Extra capacity applies to search services created after April 3, 2024:
+
+| Country | Regions providing extra capacity per partition |
+|---------|------------------------------------------------|
+| **United States** | East US​, East US 2, ​Central US​, North Central US​, South Central US​, West US​, West US 2​, West US 3​, West Central US​ |
+| **United Kingdom** | UK South​, UK West​ ​ |
+| **United Arab Emirates** | UAE North​​ |
+| **Switzerland** | Switzerland West​ |
+| **Sweden** | Sweden Central​​ |
+| **Poland** | Poland Central​​ |
+| **Norway** | Norway East​​ |
+| **Korea** | Korea Central, Korea South​ ​ |
+| **Japan** | Japan East, Japan West​ |
+| **Italy** | Italy North​​ |
+| **India** | Central India, Jio India West​ ​ |
+| **France** | France Central​​ |
+| **Europe** | North Europe​​ |
+| **Canada** | Canada Central​, Canada East​​ |
+| **Bazil** | Brazil South​​ |
+| **Asia Pacific** | East Asia, Southeast Asia​ ​ |
+| **Australia** | Australia East​, Australia Southeast​​ |
+
 If you use multiple Azure services, putting all of them in the same region minimizes or voids bandwidth charges. There are no charges for data exchanges among same-region services.
 
-Two notable exceptions might lead to provisioning Azure services in separate regions:
+Two notable exceptions might warrant provisioning Azure services in separate regions:
 
-+ [Outbound connections from Azure AI Search to Azure Storage](search-indexer-securing-resources.md). You might want Azure Storage in a different region if you're enabling a firewall.
++ [Outbound connections from Azure AI Search to Azure Storage](search-indexer-securing-resources.md). You might want search and storage in different regions if you're enabling a firewall.
 
 + Business continuity and disaster recovery (BCDR) requirements dictate creating multiple search services in [regional pairs](../availability-zones/cross-region-replication-azure.md#azure-paired-regions). For example, if you're operating in North America, you might choose East US and West US, or North Central US and South Central US, for each search service.
 
@@ -146,7 +169,7 @@ An endpoint and key aren't needed for portal-based tasks. The portal is already
 
 ## Scale your service
 
-After a search service is provisioned, you can [scale it to meet your needs](search-limits-quotas-capacity.md). If you chose the Standard tier, you can scale the service in two dimensions: replicas and partitions. For the Basic tier, you can only add replicas. For the free service, scale isn't available.
+After a search service is provisioned, you can [scale it to meet your needs](search-limits-quotas-capacity.md). On a billable tier, you can scale the service in two dimensions: replicas and partitions. For the free service, scale up isn't available and replica and partition configuration isn't offered.
 
 ***Partitions*** allow your service to store and search through more documents.
 

articles/search/search-create-service-portal.md

@@ -157,7 +157,7 @@ Creating and loading the index are separate steps. In Azure AI Search, the index
 
 The URI is extended to include the `docs` collections and `index` operation.
 
-- Paste in the following example to upload JSON documents to the search index. Then select **Send request**.
+1. Paste in the following example to upload JSON documents to the search index.
 
     ```http
     ### Upload documents
@@ -247,7 +247,9 @@ The URI is extended to include the `docs` collections and `index` operation.
         }
     ```
 
-In a few seconds, you should see an HTTP 201 response in the adjacent pane. If you get a 207, at least one document failed to upload. If you get a 404, you have a syntax error in either the header or body of the request. Verify that you changed the endpoint to include `/docs/index`.
+1. Select **Send request**. In a few seconds, you should see an HTTP 201 response in the adjacent pane. 
+
+   If you get a 207, at least one document failed to upload. If you get a 404, you have a syntax error in either the header or body of the request. Verify that you changed the endpoint to include `/docs/index`.
 
 ## Run queries
 

articles/search/search-get-started-rest.md

@@ -10,7 +10,7 @@ ms.service: cognitive-search
 ms.custom:
   - ignite-2023
 ms.topic: conceptual
-ms.date: 01/17/2024
+ms.date: 04/01/2024
 ---
 
 # Index large data sets in Azure AI Search
@@ -21,6 +21,8 @@ This article assumes familiarity with the [two basic approaches for importing da
 
 This article complements [Tips for better performance](search-performance-tips.md), which offers best practices on index and query design. A well-designed index that includes only the fields and attributes you need is an important prerequisite for large-scale indexing.
 
+We recommend using a newer search service, created after April 3, 2024, for [higher storage per partition](search-limits-quotas-capacity.md#service-limits).
+
 > [!NOTE]
 > The strategies described in this article assume a single large data source. If your solution requires indexing from multiple data sources, see [Index multiple data sources in Azure AI Search](/samples/azure-samples/azure-search-dotnet-scale/multiple-data-sources/) for a recommended approach.