Skip to content

Commit b4ca4ff

Browse files
authored
Update frequently-asked-questions.yml
Updating FAQ as there is lack of clarity and not explicitly stated if an organization should have one or multiple instances of ADF. This has lead to confusion in the field and multiple use cases when a customer has committed to a single instance of ADF when it is not in their best interest to do so.
1 parent 94fb7fc commit b4ca4ff

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/data-factory/frequently-asked-questions.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -200,6 +200,10 @@ sections:
200200
- question: |
201201
Technical deep dive
202202
answer: |
203+
### How many instances of Azure Data Factory should I have?
204+
205+
The answer to this question will depend on the security model your organazation has adapted. Each instance of Azure Data Factory should be scoped with Least Privileged access in mind. This could be a situation where one instance of ADF supports all HR workloads and another supports all Finance data. Each ADF has access to different Linked Services and each instance could be supported by different development teams. There is no additional cost as you are billed by compute increments so the same 100 pipelines in 1 instance of ADF would cost the same as 10 pipelines across 10 instances of ADF.
206+
Access in mind.
203207
### How can I schedule a pipeline?
204208

205209
You can use the scheduler trigger or time window trigger to schedule a pipeline. The trigger uses a wall-clock calendar schedule, which can schedule pipelines periodically or in calendar-based recurrent patterns (for example, on Mondays at 6:00 PM and Thursdays at 9:00 PM). For more information, see [Pipeline execution and triggers](concepts-pipeline-execution-triggers.md).

0 commit comments

Comments
 (0)