Pricing example: Using mapping data flow debug for a normal workday
APPLIES TO: 
Azure Data Factory 
Azure Synapse Analytics
Tip
Try out Data Factory in Microsoft Fabric, an all-in-one analytics solution for enterprises. Microsoft Fabric covers everything from data movement to data science, real-time analytics, business intelligence, and reporting. Learn how to start a new trial for free!
This example shows mapping data flow debug costs for a typical workday for a data engineer.
The prices used in this example below are hypothetical and are not intended to imply exact actual pricing. Read/write and monitoring costs are not shown since they are typically negligible and will not impact overall costs significantly. Activity runs are also rounded to the nearest 1000 in pricing calculator estimates.
Refer to the Azure Pricing Calculator for more specific scenarios and to estimate your future costs to use the service.
Azure Data Factory engineer
A data factory engineer is responsible for designing, building, and testing mapping data flows every day. The engineer logs into the ADF UI in the morning and enables the Debug mode for Data Flows. The default TTL for Debug sessions is 60 minutes. The engineer works throughout the day for 8 hours, so the Debug session never expires. Therefore, Sam's charges for the day will be:
8 (hours) x 8 (compute-optimized cores) x $0.193 = $12.35
Related content
- Pricing example: Copy data from AWS S3 to Azure Blob storage hourly for 30 days
- Pricing example: Copy data and transform with Azure Databricks hourly for 30 days
- Pricing example: Copy data and transform with dynamic parameters hourly for 30 days
- Pricing example: Run SSIS packages on Azure-SSIS integration runtime
- Pricing example: Transform data in blob store with mapping data flows
- Pricing example: Data integration in Azure Data Factory Managed VNET
- Pricing example: Get delta data from SAP ECC via SAP CDC in mapping data flows