Add service limit page

Author: jr-MS

articles/cognitive-services/Anomaly-Detector/How-to/batch-inference.md

@@ -30,6 +30,8 @@ You could choose the batch inference API, or the streaming inference API for det
 
 To perform batch inference, provide the blob URL containing the inference data, the start time, and end time. For inference data volume, at least `1 sliding window` length and at most **20000** timestamps.
 
+To get a better performance, we recommend you to send out no more than 150,000 data points for a batch inference. *(Data points = Number of variables * Number of timestamps)*
+
 This inference is asynchronous, so the results aren't returned immediately. Notice that you need to save in a variable the link of the results in the **response header** which contains the `resultId`, so that you may know where to get the results afterwards.
 
 Failures are usually caused by model issues or data issues. You can't perform inference if the model isn't ready or the data link is invalid. Make sure that the training data and inference data are consistent, meaning they should be **exactly** the same variables but with different timestamps. More variables, fewer variables, or inference with a different set of variables won't pass the data verification phase and errors will occur. Data verification is deferred so that you'll get error messages only when you query the results.

articles/cognitive-services/Anomaly-Detector/service-limits.md

@@ -0,0 +1,95 @@
+---
+title: Service limits - Anomaly Detector service
+titleSuffix: Azure Cognitive Services
+description: Service limits for Anomaly Detector service, including Univariate Anomaly Detection and Multivariate Anomaly Detection.
+services: cognitive-services
+author: jr-MS
+manager: nitinme
+ms.service: cognitive-services
+ms.subservice: anomaly-detector
+ms.topic: conceptual
+ms.date: 1/31/2022
+ms.author: jingruhan
+ms.custom: 
+---
+
+# Anomaly Detector service quotas and limits
+This article contains both a quick reference and detailed description of Azure Anomaly Detector service Quotas and Limits for all pricing tiers. It also contains some best practices to avoid request throttling.
+
+The quotas and limits apply to all the versions within Azure Anomaly Detector service.
+
+## Univariate Anomaly Detection
+|Quota<sup>1</sup>|Free (F0)|Standard (S0)|
+|--|--|--|
+| **All APIs per second** | 10 | 500 |
+
+<sup>1</sup> All the quota and limit are defined for one Anomaly Detector resource.
+
+## Multivariate Anomaly Detection
+
+### API call per minute
+|Quota<sup>1</sup>|Free (F0)<sup>2</sup>|Standard (S0)|
+|--|--|--|
+| **Training API per minute** | 1 | 20 |
+| **Get model API per minute** | 1 | 20 |
+| **Batch(async) inference API per minute** | 10 | 60 |
+| **Get inference results API per minute** | 10 | 60 |
+| **Last(sync) inference API per minute** | 10 | 60 |
+| **List model API per minute** | 1 | 20 |
+| **Delete model API per minute** | 1 | 20 |
+
+<sup>1</sup> All the quota and limit are defined for one Anomaly Detector resource.
+
+<sup>2</sup> For **Free (F0)** pricing tier see also monthly allowances at the [pricing page](https://azure.microsoft.com/pricing/details/cognitive-services/anomaly-detector/)
+
+
+### Concurrent models and inference tasks
+|Quota<sup>1</sup>|Free (F0)|Standard (S0)|
+|--|--|--|
+| **Maximum models** *(created, running, ready, failed)*| 20 | 1000 |
+| **Maximum running models** *(created, running)* | 1 | 20 |
+| **Maximum running inference** *(created, running)* | 10 | 60 |
+
+<sup>1</sup> All the quota and limit are defined for one Anomaly Detector resource. If you want to increase the limit, please contact [email protected] for further communication.
+
+
+## How to increase the limit for your resource?
+For the Standard pricing tier, this limit can be increased. Increasing the Concurrent Request limit does not directly affect your costs. Anomaly Detector service uses "Pay only for what you use" model. The limit defines how high the Service may scale before it starts throttle your requests.
+
+Existing value of Concurrent Request limit parameter is not visible via Azure portal, Command-Line tools, or API requests. To verify the existing value, create an Azure Support Request.
+
+If you would like to increase your limit, you can enable auto scaling on your resource. Follow this document to enable auto scaling on your resource [enable auto scaling](https://learn.microsoft.com/azure/cognitive-services/autoscale?view=form-recog-3.0.0&tabs=portal). You can also submit an increase TPS support request.
+
+### Have the required information ready
+
+* Anomaly Detector Resource ID
+
+* Region
+
+#### How to get those information above:
+
+* Go to [Azure portal](https://portal.azure.com/)
+* Select the Anomaly Detector Resource for which you would like to increase the transaction limit
+* Select Properties (Resource Management group)
+* Copy and save the values of the following fields:
+    * Resource ID
+    * Location (your endpoint Region)
+
+
+### Create and submit support request
+Initiate the increase of limit for your resource by submitting the Support Request:
+
+* Go to [Azure portal](https://portal.azure.com/)
+* Select the Anomaly Detector Resource for which you would like to increase the limit
+* Select New support request (Support + troubleshooting group)
+* A new window will appear with auto-populated information about your Azure Subscription and Azure Resource
+* Enter Summary (like "Increase Anomaly Detector TPS limit")
+* In Problem type, select *"Quota or usage validation"*
+* Select Next: Solutions
+* Proceed further with the request creation
+* Under the Details tab enters the following in the Description field:
+    * A note, that the request is about Anomaly Detector quota.
+    * Provide a TPS expectation you would like to scale to meet.
+    * Azure resource information you collected.
+    * Complete entering the required information and select Create button in *Review + create* tab
+    * Note the support request number in Azure portal notifications. You'll be contacted shortly for further processing

articles/cognitive-services/Anomaly-Detector/toc.yml

@@ -9,6 +9,8 @@
       href: https://aka.ms/adpricing
     - name: What's new
       href: whats-new.md
+    - name: Service limits
+      href: sevice-limits.md
     - name: FAQ
       href: faq.yml
 - name: Quickstarts