How to Choose Between Copy and Web Activity for APIs in Azure Data Factory
Question details
The user needs to determine whether a Copy activity or a Web activity is the appropriate choice for extracting data from an API within an Azure Data Factory pipeline.
- Product
- Azure Data Factory
- Device & OS
- not provided
- Scenario
- Designing an Azure Data Factory pipeline to successfully connect to, extract, and load data from an external API endpoint.
- Observed behavior
- Evaluating activity types based on the API's response payload, authentication requirements, pagination rules, and the final data destination.
Identify your API's authentication method, payload size limitations, and whether the data needs to be written directly to a database or storage account before configuring your pipeline.
Evaluate the Capabilities of Copy and Web Activities
Understand the core differences between the Copy Data activity and Web activity to select the most efficient method for your API extraction.
The Copy Activity is typically the best choice when moving large volumes of data directly from a REST API to a supported sink (destination) such as Azure SQL Database, Blob Storage, or Data Lake. It handles built-in pagination, complex schema mapping, and robust authentication methods natively.
The Web Activity is designed primarily for control flow. It is ideal for triggering external endpoints, passing small JSON payloads between pipeline activities, or handling custom authentication steps where the immediate goal is not to write bulk data to a sink.
If you intend to sink the API response directly into a database or storage account, select the Copy Data activity and configure a REST linked service.
If the API requires pagination (such as following 'next page' URLs or using offset parameters), use the Copy activity, which features robust native pagination rules configurable in the Source tab.
If you only need to trigger an API, retrieve a token, or get a small JSON response (under 4MB) to pass as a variable to a subsequent activity, choose the Web activity.
Consult Microsoft Learn Q&A for Complex Scenarios
Seek official guidance from Azure specialists when dealing with highly customized APIs or unique authentication flows.
Enhance Your Technical Documentation with WPS Office
While managing complex cloud data pipelines in Azure Data Factory, you often need a reliable office suite to map out API architectures, draft technical documentation, and present data workflows. WPS Office provides a free, lightweight, and fully compatible alternative to Microsoft Office.
- 1. Visit the WPS Office Website: Navigate to the official WPS Office website on your device.
- 2. Download the Installer: Click the 'Free Download' button to get the lightweight installation package.
- 3. Install and Document: Run the installer, open WPS Office, and start drafting your API architecture documents immediately.

Frequently Asked Questions
Can I use Web Activity to extract large datasets from an API?
No, the Web Activity has a maximum output response size limit (typically around 4MB). For extracting and moving large datasets, you should always use the Copy Data activity with a REST or HTTP linked service.
How do I securely pass an authentication token to a Copy Activity?
A common Azure Data Factory pattern is to first use a Web Activity to call an authentication endpoint and retrieve a Bearer token. You can then pass this token securely via dynamic content (e.g., @activity('WebActivity').output.access_token) into the additional headers of your subsequent Copy Activity.
Does the Copy Activity support automatic API pagination?
Yes, the Copy Activity's REST source allows you to define complex pagination rules. You can configure it to extract next-page URLs from the response body, headers, or query parameters to automatically loop through and extract all pages of API data.




