> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview-2/azure-services/data-factory.md).
# Data Factory
Configuring Azure Data Factory in DuploCloud
DuploCloud supports integration with Azure Data Factory (ADF)--a fully managed cloud-based data integration service from Microsoft Azure. It enables users to create, schedule, and orchestrate data workflows, allowing for the movement and transformation of data across a wide variety of sources and destinations. It provides a platform for managing data pipelines, which are used to move and transform data from on-premises or cloud-based sources into data storage systems for analysis, reporting, and other business processes.
## Configuring Azure Data Factory in DuploCloud
1. Select the appropriate Tenant from the **Tenant** list box.
2. Navigate to **Cloud Services** -> **AI - ML**.
3. Select the **Data Factory** tab.
4. Click **Add**. The **Add Data Factory** pane displays.
The Add Data Factory pane
5. In the **Data Factory Name** field, enter a name. Note: The name must be globally unique across all of Azure.
6. Enable or disable **Allow Access Via Public Endpoint**.
7. Click **Create**. The configuration is finalized, and DuploCloud provisions the Azure Data Factory instance according to the provided settings.
The Data Factory tab in the DuploCloud Portal
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.duplocloud.com/docs/automation-platform/overview-2/azure-services/data-factory.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
