address feedbacks

Author: Samantha-Yu

articles/data-factory/TOC.yml

@@ -646,7 +646,7 @@
   - name: Understanding pricing
     items:
     - name: Plan and manage costs     
-      href: billing-acom.md 
+      href: plan-and-manage-costs.md 
     - name: Pricing examples     
       href: pricing-concepts.md  
   - name: Troubleshooting guides

articles/data-factory/media/billing-acom/copy-output.png renamed to articles/data-factory/media/plan-and-manage-costs/copy-output.png

@@ -12,6 +12,8 @@ ms.date: 05/14/2020
 
 # Plan and manage costs for Azure Data Factory
 
+[!INCLUDE[appliesto-adf-xxx-md](includes/appliesto-adf-xxx-md.md)]
+
 Azure Data Factory is a serverless and elastic data integration service built for cloud scale.  This means there is not a fixed-size compute that you need to plan for peak load; rather you specify how much resource to allocate on demand per operation, which allows you to design the ETL processes in a much more scalable manner. In addition, ADF is billed on a consumption-based plan, which means you only pay for what you use.
 
 This article describes how you can plan and manage costs for Azure Data Factory.
@@ -32,17 +34,20 @@ One of the commonly asked questions for the pricing calculator is what values sh
 For example, let’s say you need to move 1 TB of data daily from AWS S3 to Azure Data Lake Gen2.  You can perform POC of moving 100 GB of data to measure the data ingestion throughput and understand the corresponding billing consumption.
 
 Here is a sample copy activity run detail (your actual mileage will vary based on the shape of your specific dataset, network speeds, egress limits on S3 account, ingress limits on ADLS Gen2, and other factors).
-![S3 copy run](media/billing-acom/s3-copy-run-details.png)
+
+![S3 copy run](media/plan-and-manage-costs/s3-copy-run-details.png)
 
 By leveraging the [consumption monitoring at pipeline-run level](#monitor-consumption-at-pipeline-run-level), you can see the corresponding data movement meter consumption quantities:
-![S3 copy pipeline consumption](media/billing-acom/s3-copy-pipeline-consumption.png)
+
+![S3 copy pipeline consumption](media/plan-and-manage-costs/s3-copy-pipeline-consumption.png)
 
 Therefore, the total number of DIU-hours it takes to move 1 TB per day for the entire month is:
 
 1.2667 (DIU-hours) * (1 TB / 100 GB) * 30 (days in a month) = 380 DIU-hours
 
 Now you can plug 30 activity runs and 380 DIU-hours into ADF pricing calculator to get an estimate of your monthly bill:
-![S3 copy pricing calculator](media/billing-acom/s3-copy-pricing-calculator.png)
+
+![S3 copy pricing calculator](media/plan-and-manage-costs/s3-copy-pricing-calculator.png)
 
 ## Use budgets and cost alerts
 
@@ -56,7 +61,8 @@ As you start using Azure Data Factory, you can see the costs incurred in the [co
 2. The default view shows accumulated costs for the current month.  You can switch to a different time range and a different granularity such as daily or monthly.
 3. To narrow costs for a single service such as Azure Data Factory, select **Add filter** and then select **Service name**.  Then choose **Azure data factory v2** from the list.
 4. You can add additional filters to analyze cost for specific factory instance and specific ADF meter granularity.
-   ![Cost analysis](media/billing-acom/cost-analysis.png)
+
+   ![Cost analysis](media/plan-and-manage-costs/cost-analysis.png)
 
 ## Monitor consumption at pipeline-run level
 
@@ -65,8 +71,10 @@ Depending on the types of activities you have in your pipeline, how much data yo
 You can view the amount of consumption for different meters for individual pipeline runs in the Azure Data Factory user experience. To open the monitoring experience, select the **Monitor & Manage** tile in the data factory blade of the [Azure portal](https://portal.azure.com/). If you're already in the ADF UX, click on the **Monitor** icon on the left sidebar. The default monitoring view is list of pipeline runs.
 
 Clicking the **Consumption** button next to the pipeline name will display a pop-up window showing you the consumption for your pipeline run aggregated across all of the activities within the pipeline.
-![Pipeline run consumption](media/billing-acom/pipeline-run-consumption.png)
-![Pipeline consumption details](media/billing-acom/pipeline-consumption-details.png)
+
+![Pipeline run consumption](media/plan-and-manage-costs/pipeline-run-consumption.png)
+
+![Pipeline consumption details](media/plan-and-manage-costs/pipeline-consumption-details.png)
 
 The pipeline run consumption view shows you the amount consumed for each ADF meter for the specific pipeline run, but it does not show the actual price charged, because the amount billed to you is dependent on the type of Azure account you have and the type of currency used.  To view the full list of supported account types, see [Understand Cost Management data](https://docs.microsoft.com/azure/cost-management-billing/costs/understand-cost-mgt-data).
 
@@ -76,10 +84,12 @@ Once you understand the aggregated consumption at pipeline-run level, there are
 To see the consumption at activity-run level, go to your data factory **Author & Monitor** UI. From the **Monitor** tab where you see a list of pipeline runs, click the **pipeline name** link to access the list of activity runs in the pipeline run.  Click on the **Output** button next to the activity name and look for **billableDuration** property in the JSON output:
 
 Here is a sample out from a copy activity run:
-![Copy output](media/billing-acom/copy-output.png)
+
+![Copy output](media/plan-and-manage-costs/copy-output.png)
 
 And here is a sample out from a Mapping Data Flow activity run:
-![Dataflow output](media/billing-acom/dataflow-output.png)
+
+![Dataflow output](media/plan-and-manage-costs/dataflow-output.png)
 
 ## Next steps