Merge pull request #380 from MicrosoftDocs/main

9/19/2024 AM Publish

Author: Taojunshen

articles/ai-studio/toc.yml

@@ -8,7 +8,7 @@ items:
     href: what-is-ai-studio.md
   - name: Azure AI Studio architecture
     href: concepts/architecture.md
-  - name: "AI Studio or AML: Which should I choose?"
+  - name: AI Studio versus AML studio
     href: /ai/ai-studio-experiences-overview?context=/azure/ai-studio/context/context
   - name: Region support
     href: reference/region-support.md
@@ -65,16 +65,50 @@ items:
     - name: Create a project
       href: how-to/create-projects.md
     - name: Create and manage compute
-      href: how-to/create-manage-compute.md
-    - name: Connect to external resources
+    href: how-to/create-manage-compute.md
+  - name: Connect to services and resources
+    items:
+    - name: Connections overview
+      href: concepts/connections.md
+    - name: Create a connection
+      href: how-to/connections-add.md
+    - name: Create a connection using the Azure Machine Learning SDK
+      href: how-to/develop/connections-add-sdk.md
+      displayName: code
+    - name: Azure AI services connections
       items:
-      - name: Connections overview
-        href: concepts/connections.md
-      - name: Create a connection
-        href: how-to/connections-add.md
-      - name: Create a connection using the Azure Machine Learning SDK
-        href: how-to/develop/connections-add-sdk.md
-        displayName: code
+      - name: What are AI services?
+        href: ../ai-services/what-are-ai-services.md?context=/azure/ai-studio/context/context
+        displayName: cognitive
+      - name: Get started with AI services in AI Studio
+        href: ai-services/get-started.md
+      - name: Connect AI services in AI Studio
+        href: ai-services/connect-ai-services.md
+      - name: Azure OpenAI
+        items:
+        - name: Get started with Assistants and code interpreter in the playground
+          href: ../ai-services/openai/assistants-quickstart.md?context=/azure/ai-studio/context/context
+        - name: Analyze images and video with GPT-4 for Vision in the playground
+          href: quickstarts/multimodal-vision.md
+        - name: Use your image data with Azure OpenAI
+          href: how-to/data-image-add.md
+          displayName: vision, gpt, turbo
+      - name: Azure AI Content Safety
+        items:
+        - name: Content filtering
+          href: concepts/content-filtering.md
+        - name: Prevent input attacks with Prompt Shields
+          href: how-to/prompt-shields.md
+        - name: Detect groundedness in chat responses
+          href: how-to/groundedness.md
+      - name: Speech
+        items:
+        - name: Real-time speech to text
+          href: ../ai-services/speech-service/get-started-speech-to-text.md?context=/azure/ai-studio/context/context
+        - name: Pronunciation assessment
+          href: ../ai-services/speech-service/pronunciation-assessment-tool.md?context=/azure/ai-studio/context/context
+        - name: Hear and speak with chat in the playground
+          href: quickstarts/hear-speak-playground.md
   - name: Select and deploy AI models
     items:
     - name: Model catalog
@@ -261,40 +295,6 @@ items:
       href: how-to/monitor-quality-safety.md
     - name: Troubleshoot deployments and monitoring
       href: how-to/troubleshoot-deploy-and-monitor.md
-  - name: Get started with Azure AI services
-    items:
-    - name: What are AI services?
-      href: ../ai-services/what-are-ai-services.md?context=/azure/ai-studio/context/context
-      displayName: cognitive
-    - name: Get started with AI services in AI Studio
-      href: ai-services/get-started.md
-    - name: Connect AI services in AI Studio
-      href: ai-services/connect-ai-services.md
-    - name: Azure OpenAI
-      items:
-      - name: Get started with Assistants and code interpreter in the playground
-        href: ../ai-services/openai/assistants-quickstart.md?context=/azure/ai-studio/context/context
-      - name: Analyze images and video with GPT-4 for Vision in the playground
-        href: quickstarts/multimodal-vision.md
-      - name: Use your image data with Azure OpenAI
-        href: how-to/data-image-add.md
-        displayName: vision, gpt, turbo
-    - name: Azure AI Content Safety
-      items:
-      - name: Content filtering
-        href: concepts/content-filtering.md
-      - name: Prevent input attacks with Prompt Shields
-        href: how-to/prompt-shields.md
-      - name: Detect groundedness in chat responses
-        href: how-to/groundedness.md
-    - name: Speech
-      items:
-      - name: Real-time speech to text
-        href: ../ai-services/speech-service/get-started-speech-to-text.md?context=/azure/ai-studio/context/context
-      - name: Pronunciation assessment
-        href: ../ai-services/speech-service/pronunciation-assessment-tool.md?context=/azure/ai-studio/context/context
-      - name: Hear and speak with chat in the playground
-        href: quickstarts/hear-speak-playground.md
   - name: Costs and quotas
     items:
     - name: Plan and manage costs

articles/search/media/vector-search-index-size/deployment-details.png

@@ -11,7 +11,7 @@ ms.custom:
   - references_regions
   - build-2024
 ms.topic: conceptual
-ms.date: 08/22/2024
+ms.date: 09/19/2024
 ---
 
 # Create an Azure AI Search service in the portal
@@ -87,25 +87,25 @@ Service name requirements:
 ## Choose a region
 
 > [!IMPORTANT]
-> Due to high demand, Azure AI Search is currently unavailable for new instances in West Europe. If you don't immediately need semantic ranker or skillsets, choose Sweden Central because it has the most data center capacity. Otherwise, North Europe is another option. Currently, there are also capacity constraints for Basic and Standard (S1) tiers within a given region.
+> Due to high demand, Azure AI Search is currently unavailable for new instances in some regions. 
 
 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 egress among same-region services.
 
 Generally, choose a region near you, unless the following considerations apply:
 
-+ Your nearest region is capacity constrained. West Europe is at capacity and unavailable for new instances. Other regions are [at capacity for specific tiers](search-sku-tier.md#region-availability-by-tier). One advantage to using the Azure portal for resource setup is that it provides only those regions and tiers that are available. You can't select regions or tiers that are unavailable.
++ Your nearest region is capacity constrained. For example, West Europe is at capacity and unavailable for new instances. Other regions are [at capacity for specific tiers](search-sku-tier.md#region-availability-by-tier). One advantage to using the Azure portal for resource setup is that it provides only those regions and tiers that are available.
 
 + You want to use integrated data chunking and vectorization or built-in skills for AI enrichment. Azure OpenAI and Azure AI services multiservice accounts must be in the same region as Azure AI Search for integration purposes. [Choose a region](search-region-support.md) that provides all necessary resources.
 
 + You want to use Azure Storage for indexer-based indexing or you need to store application data that isn't in an index. Debug session state, enrichment caches, and knowledge stores are Azure AI Search features that have a dependency on Azure Storage. The region you choose for Azure Storage has implications for network security. Specifically, if you're setting up a firewall, you should place the resources in separate regions. For more information, see [Outbound connections from Azure AI Search to Azure Storage](search-indexer-securing-resources.md).
 
 Here's a checklist for choosing a region:
 
-1. Is Azure AI Search available in a nearby region? Check the [supported regions list](search-region-support.md). Capacity-constrained regions are indicated in the footnotes.
+1. Is Azure AI Search available in a nearby region? Check the [supported regions list](search-region-support.md).
 
 1. Do you know which tier you want to use? Tiers are covered in the next step. Check [region availability by tier](search-sku-tier.md#region-availability-by-tier) to determine if you can create a search service at the desired tier in your region of choice.
 
-1. Do you need [AI enrichment](cognitive-search-concept-intro.md) or [integrated data chunking and vectorization](vector-search-integrated-vectorization.md)? Verify that Azure OpenAI and Azure AI services are [offered in the same region](search-region-support.md) as Azure AI Search. 
+1. Do you need [AI enrichment](cognitive-search-concept-intro.md) or [integrated data chunking and vectorization](vector-search-integrated-vectorization.md)? Verify that Azure OpenAI and Azure AI multiservice are [offered in the same region](search-region-support.md) as Azure AI Search. 
 
    Be aware that Azure AI Vision multimodal embeddings API, used for [integrated image vectorization](search-get-started-portal-image-search.md), must be accessed through an Azure AI multiservice account, but is available in a [smaller subset of regions](/azure/ai-services/computer-vision/overview-image-analysis#region-availability).
 

articles/search/media/vector-search-index-size/resource-group-deployments.png

@@ -8,7 +8,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 09/04/2024
+ms.date: 09/19/2024
 ms.custom:
   - references_regions
   - build-2024
@@ -80,53 +80,29 @@ When estimating document size, remember to consider only those fields that add v
 
 When you index documents with vector fields, Azure AI Search constructs internal vector indexes using the algorithm parameters you provide. The size of these vector indexes is restricted by the memory reserved for vector search for your service's tier (or `SKU`).
 
-The service enforces a vector index size quota **for every partition** in your search service. Each extra partition increases the available vector index size quota. This quota is a hard limit to ensure your service remains healthy, which means that further indexing attempts once the limit is exceeded results in failure. You can resume indexing once you free up available quota by either deleting some vector documents or by scaling up in partitions.
-
-Vector limits vary by service creation date and tier.
-
-+ To check the age of your search service or learn more about vector indexes, see [Vector index size and staying under limits](vector-search-index-size.md).
-
-+ To view the vector quota in effect for your search service, use [GET Service Statistics](/rest/api/searchservice/get-service-statistics/get-service-statistics), or check the **Properties** and **Usage** tabs for your search service in the Azure portal.
-
-#### Vector quota per partition (GB)
+Vector limits vary by [service creation date](vector-search-index-size.md#how-to-check-service-creation-date) and [tier](search-sku-tier.md). For guidance on managing and maximizing vector storage, see [Vector index size and staying under limits](vector-search-index-size.md).
 
 This table shows the progression of vector quota increases in GB over time. The quota is per partition, so if you scale a new Standard (S1) service to 6 partitions, total vector quota is 35 multiplied by 6.
 
 | Service creation date |Basic | S1| S2 | S3/HD | L1 | L2 |
 |-----------------------|------|---|----|----|----|----|
 |**Before July 1, 2023** <sup>1</sup> | 0.5 | 1 | 6 | 12 | 12 | 36 |
 | **July 1, 2023 through April 3, 2024** <sup>2</sup>| 1  | 3 | 12 | 36 | 12 | 36 |
-|**April 3, 2024 through May 17, 2024** <sup>3</sup> | 5  | 35 | 100 | 200 | 12 | 36 |
-|**After May 17, 2024** <sup>4</sup> | 5  | 35 | 150 | 300 | 150 | 300 |
+|**April 3, 2024 through May 17, 2024** <sup>3</sup> | **5**  | **35** | **150** | **300** | 12 | 36 |
+|**After May 17, 2024** <sup>4</sup> | 5  | 35 | 150 | 300 | **150** | **300** |
 
 <sup>1</sup> Initial vector limits during early preview.
 
 <sup>2</sup> Vector limits during the later preview period. Three regions didn't have the higher limits: Germany West Central, West India, Qatar Central.
 
-<sup>3</sup> Higher vector quota based on the larger partitions for supported tiers and regions.
+<sup>3</sup> Higher vector quota based on the larger partitions for supported tiers and regions. 
 
 <sup>4</sup> Higher vector quota for more tiers and regions based on partition size updates.
 
-#### Partition limits (GB)
-
-This table repeats [partition storage limits](#service-limits) for context. The table shows the progression of storage quota increases in GB over time. Vector quota is per partition, so the more significant increases in vector quota that occurred starting in April 2024 correspond to the increases in per-partition storage occuring at the same time. 
-
-Higher capacity partitions were brought online starting in April 2024.
-
-| Service creation date |Basic | S1| S2 | S3/HD | L1 | L2 |
-|-----------------------|------|---|----|----|----|----|
-|**Before July 1, 2023** <sup>1</sup> | 2  | 25 | 100 | 200 | 1,024 | 2,048 |
-|**July 1, 2023 through April 3, 2024** <sup>2</sup>| 2  | 25 | 100 | 200 | 1,024 | 2,048 |
-|**April 3, 2024 through May 17, 2024** <sup>3</sup> | 15  | 160 | 512 | 1,024 | 1,024 | 2,048 |
-|**After May 17, 2024** <sup>4</sup> | 15  | 160 | 512 | 1,024 | 2,048 | 4,096 |
-
-<sup>1</sup> Partition sizes during early preview.
-
-<sup>2</sup> No change during the later preview period.
-
-<sup>3</sup> Higher capacity storage for Basic, S1, S2, 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​.
+The service enforces a vector index size quota **for every partition** in your search service. Each extra partition increases the available vector index size quota. This quota is a hard limit to ensure your service remains healthy, which means that further indexing attempts once the limit is exceeded results in failure. You can resume indexing once you free up available quota by either deleting some vector documents or by scaling up in partitions.
 
-<sup>4</sup> Higher capacity storage for more tiers and more regions. **Europe**: Germany North​, Germany West Central, Switzerland West​. **Azure Government**: Texas, Arizona, Virginia. **Africa**: South Africa North​. **Asia Pacific**: China North 3, China East 3.
+> [!IMPORTANT]
+> Higher vector limits are tied to larger partition sizes. Regions that run on older infrastructure are subject to the July-April limits. Review the [regions list](search-region-support.md) for status on partition storage limits.
 
 ## Indexer limits