Merge pull request #90510 from HeidiSteen/heidist-gh

Azure Search customer case: document index throttle limits

Author: PRMerger7

articles/search/search-limits-quotas-capacity.md

@@ -6,7 +6,7 @@ manager: nitinme
 services: search
 ms.service: search
 ms.topic: conceptual
-ms.date: 07/01/2019
+ms.date: 10/03/2019
 ms.author: heidist
 ---
 # Service limits in Azure Search
@@ -142,6 +142,18 @@ For the Storage Optimized tiers,  you should expect a lower query throughput and
 
 A [cognitive search pipeline](cognitive-search-concept-intro.md) that makes calls to a Text Analytics resource for [entity recognition](cognitive-search-skill-entity-recognition.md), [key phrase extraction](cognitive-search-skill-keyphrases.md), [sentiment analysis](cognitive-search-skill-sentiment.md), and [language detection](cognitive-search-skill-language-detection.md) is subject to data limits. The maximum size of a record should be 50,000 characters as measured by [`String.Length`](https://docs.microsoft.com/dotnet/api/system.string.length). If you need to break up your data before sending it to the sentiment analyzer, use the [Text Split skill](cognitive-search-skill-textsplit.md).
 
+## Throttling limits
+
+Search query and indexing requests are throttled as the system approaches peak capacity. Throttling behaves differently for different APIs. Query APIs (Search/Suggest/Autocomplete) and indexing APIs throttle dynamically based on the load on the service. Index APIs have static request rate limits. 
+
+Static rate request limits for operations related to an index:
+
++ List Indexes (GET /indexes): 5 per second per search unit
++ Get Index (GET /indexes/myindex): 10 per second per search unit
++ Create Index (POST /indexes): 12 per minute per search unit
++ Create or Update Index (PUT /indexes/myindex): 6 per second per search unit
++ Delete Index (DELETE /indexes/myindex): 12 per minute per search unit 
+
 ## API request limits
 * Maximum of 16 MB per request <sup>1</sup>
 * Maximum 8 KB URL length