Merge pull request #204992 from MicrosoftDocs/main

"Merge default branch to live Sunday 4 PM

Author: tamarakhader

articles/azure-monitor/logs/dashboard-upgrade.md

@@ -66,10 +66,14 @@ As dashboards may contain multiple visualizations from multiple queries, the tim
 
 ### Query data values - 25 values and other grouping
 
-Dashboards can be visually dense and complex. In order to reduce cognitive load when viewing a dashboard, we optimize the visualizations by limiting the display to 25 different data types. When there are more than 25, Log Analytics optimizes the data. It individually shows the 25 types with most data as separate and then groups the remaining values into an “other” value. The following chart shows such a case.  
+Dashboards can be visually dense and complex. To reduce cognitive load when viewing a dashboard, we optimize the visualizations by limiting the display to 25 different data types. When there are more than 25, Log Analytics optimizes the data. It individually shows the 25 types with most data as separate and then groups the remaining values into an “other” value. The following chart shows such a case.  
 
 ![Screenshot that shows a dashboard with 25 different data types.](media/dashboard-upgrade/values-25-limit.png)
 
+### Query results limit
+
+A query underlying a Log Analytics dashboard can return up to 2000 records.  
+
 ### Dashboard refresh on load
 
 Dashboards are refreshed upon load. All queries related to dashboard-pinned Log Analytics visualizations are executed and the dashboard is refreshed once it loads. If the dashboard page remains open, the data in the dashboard is refreshed every 60 minutes.

articles/data-factory/TOC.yml

@@ -1113,6 +1113,8 @@ items:
       href: data-flow-reserved-capacity-overview.md
     - name: Data flow understand reservation charges
       href: data-flow-understand-reservation-charges.md
+    - name: Better understand different integration runtime charges
+      href: better-understand-different-integration-runtime-charges.md
     - name: Plan and manage costs     
       href: plan-manage-costs.md 
       displayName: diu

articles/data-factory/better-understand-different-integration-runtime-charges.md

@@ -0,0 +1,92 @@
+---
+title: Examples for better understanding pricing model under different integration runtime types
+description: Learn about pricing model under different integration runtime types from some examples.
+ms.author: lle
+author: lrtoyou1223
+ms.service: data-factory
+ms.subservice: integration-runtime
+ms.topic: conceptual
+ms.date: 07/17/2022
+---
+
+# Examples for better understanding pricing model under different integration runtime types
+
+[!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
+
+In this article, we'll illustrate the pricing model using different integration runtime through some concrete examples. These examples only focus on copy activity, pipeline activity and external activity running on the integration runtime. It doesn't involve charges for Data Factory Pipeline Orchestration, Data Factory Operations and Data Factory Operations. For all pricing details, see [Data Pipeline Pricing and FAQ](pricing-concepts.md).
+
+The integration runtime, which is serverless in Azure and self-hosted in hybrid scenarios, provides the compute resources used to execute the activities in a pipeline. Integration runtime charges are prorated by the minute and rounded up.
+
+> [!NOTE] 
+> The prices used in these examples below are hypothetical and are not intended to imply actual pricing.
+
+## Azure integration runtime
+
+**Example 1: If there are 6 copy activities executed sequentially. 4 DIUs are used for the first 2 copy activities and the execution time of each is 40 seconds. The other 4 choose using 8 DIUs and the execution time of each is 1 minute and 20 seconds.**
+
+In this example, the execution time of the first 2 activities is both rounded up to 1 minute each. The other 4 are all rounded up to 2 minutes each. 
+
+:::image type="content" source="./media/integration-runtime-pricing/azure-integration-runtime-example-1.png" alt-text="Screenshot of calculation formula for Azure integration runtime example 1.":::
+
+
+**Example 2: If there are 50 copy activities triggered by Foreach. 4 DIUs are used for each copy activity, and each executes for 40 seconds. The parallel is configured as 50 in Foreach.**
+
+In this example, the execution time of each copy activity is rounded up to 1 minute. Although the 50 copy activities run in parallel, they use different computes. So they're charged independently. 
+
+:::image type="content" source="./media/integration-runtime-pricing/azure-integration-runtime-example-2.png" alt-text="Screenshot of calculation formula for Azure integration runtime example 2.":::
+
+
+**Example 3: If there are 6 HDInsight activities triggered by Foreach. The execution time of each is 9 minutes and 40 seconds. The parallel is configured as 50 in Foreach.**
+
+In this example, the execution time of each HDInsight activity is rounded up to 10 minutes. Although the 6 HDInsight activities run in parallel, they use different computes. So they're charged independently. 
+
+:::image type="content" source="./media/integration-runtime-pricing/azure-integration-runtime-example-3.png" alt-text="Screenshot of calculation formula for Azure integration runtime example 3.":::
+
+
+## Azure integration runtime with managed virtual network enabled
+
+**Example 1: If there are 6 copy activities executed sequentially. 4 DIUs are used for each copy activity and the execution time of each is 40 seconds. Assume the queue time is 1 minute and no TTL enabled.**
+
+In this example, the execution time and queue time totally are rounded up to 2 minutes. As no TTL is enabled, every copy activity has a queue time. The price for copy activity using Azure integration runtime with managed virtual network enabled is $0.25 /DIU-hour.
+
+:::image type="content" source="./media/integration-runtime-pricing/vnet-integration-runtime-example-1.png" alt-text="Screenshot of calculation formula for Azure integration runtime with managed virtual network example 1.":::
+
+**Example 2: If there are 6 copy activities executed sequentially. 4 DIUs are reserved for copy activity and the execution time of each is 40 seconds. Assume the queue time is 1 minute and TTL is 5 minutes.**
+
+As the compute is reserved, the 6 copy activities aren't rounded up independently and are charged together. And TTL is enabled, so only the first copy activity has queue time. 
+
+:::image type="content" source="./media/integration-runtime-pricing/vnet-integration-runtime-example-2.png" alt-text="Screenshot of calculation formula for Azure integration runtime with managed virtual network example 2.":::
+
+**Example 3: If there are 6 HDInsight activities triggered by Foreach. The execution time of each is 9 minutes and 40 seconds. The parallel is configured as 50 in Foreach. TTL is 30 minutes.**
+
+In this example, the execution time of each HDInsight activity is rounded up to 10 minutes. As the 6 HDInsight activities run in parallel and within the concurrency limitation (800), they're only charged once. 
+
+:::image type="content" source="./media/integration-runtime-pricing/vnet-integration-runtime-example-3.png" alt-text="Screenshot of calculation formula for Azure integration runtime with managed virtual network example 3.":::
+
+
+## Self-hosted integration runtime
+
+**Example 1: If there are 6 copy activities executed sequentially. The execution time of each is 40 seconds.**
+
+In this example, the execution time of each copy activity is rounded up to 1 minute each. 
+
+:::image type="content" source="./media/integration-runtime-pricing/self-hosted-integration-runtime-example-1.png" alt-text="Screenshot of calculation formula for Self-hosted integration runtime example 1.":::
+
+**Example 2: If there are 50 copy activities triggered by Foreach. The execution time of each is 40 seconds. The parallel is configured as 50 in Foreach.**
+
+In this example, the execution time of each copy activity is rounded up to 1 minute. Although the 50 copy activities run in parallel, they're charged independently.
+
+:::image type="content" source="./media/integration-runtime-pricing/self-hosted-integration-runtime-example-2.png" alt-text="Screenshot of calculation formula for Self-hosted integration runtime example 2.":::
+
+**Example 3: If there are 6 HDInsight activities triggered by Foreach. The execution time of each is 9 minutes and 40 seconds. The parallel is configured as 50 in Foreach.**
+
+In this example, the execution time of each HDInsight activity is rounded up to 10 minutes. Although the 6 HDInsight activities run in parallel, they're charged independently.
+
+:::image type="content" source="./media/integration-runtime-pricing/self-hosted-integration-runtime-example-3.png" alt-text="Screenshot of calculation formula for Self-hosted integration runtime example 3.":::
+
+
+## Next steps
+
+Now that you understand the pricing for Azure Data Factory, you can get started!
+
+- [Create a data factory by using the Azure Data Factory UI](quickstart-create-data-factory-portal.md)