Skip to content

Commit 07b8929

Browse files
authored
Merge pull request #98 from kromerm/80activities
Update concepts-pipelines-activities.md
2 parents 094cd0f + 23b85bb commit 07b8929

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/data-factory/concepts-pipelines-activities.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: data-factory
88
ms.subservice: orchestration
99
ms.custom: synapse
1010
ms.topic: conceptual
11-
ms.date: 10/20/2023
11+
ms.date: 03/11/2024
1212
---
1313

1414
# Pipelines and activities in Azure Data Factory and Azure Synapse Analytics
@@ -30,6 +30,10 @@ Azure Data Factory and Azure Synapse Analytics have three groupings of activitie
3030

3131
An input dataset represents the input for an activity in the pipeline, and an output dataset represents the output for the activity. Datasets identify data within different data stores, such as tables, files, folders, and documents. After you create a dataset, you can use it with activities in a pipeline. For example, a dataset can be an input/output dataset of a Copy Activity or an HDInsightHive Activity. For more information about datasets, see [Datasets in Azure Data Factory](concepts-datasets-linked-services.md) article.
3232

33+
> [!NOTE]
34+
> There is a default soft limit of maximum 80 activities per pipeline, which includes inner activities for containers.
35+
36+
3337
## Data movement activities
3438

3539
Copy Activity in Data Factory copies data from a source data store to a sink data store. Data Factory supports the data stores listed in the table in this section. Data from any source can be written to any sink.

0 commit comments

Comments
 (0)