Azure Data Factory Connectors: A Complete Guide with Real-Time Examples
Introduction
One of the biggest strengths of Azure Data Factory (ADF) is its ability to connect to hundreds of different data sources without requiring custom integration code.
Whether your data is stored in:
SQL Server
Oracle
SAP
Azure Storage
AWS S3
Salesforce
REST APIs
Snowflake
MongoDB
PostgreSQL
MySQL
Azure Data Factory provides built-in Connectors that make it easy to move and transform data.
Think of a connector as a bridge between Azure Data Factory and an external data source or destination.
What is an Azure Data Factory Connector?
A connector is a built-in component that enables Azure Data Factory to communicate with external systems.
Without connectors, developers would have to write custom code to:
Authenticate
Read data
Write data
Handle errors
Manage connections
ADF connectors eliminate this complexity by providing a standardized way to access data.
How Connectors Work
Azure Data Factory
│
------------------------
│ │
Source Connector Destination Connector
│ │
SQL Server Azure SQL Database
Oracle Azure Blob Storage
REST API Azure Data Lake
SAP Synapse Analytics
Salesforce Snowflake
A connector can act as both a Source (reading data) and a Sink (writing data), depending on the service.
Types of Connectors
Azure Data Factory categorizes connectors into several groups.
1. Azure Connectors
These connect to Azure-native services.
Examples:
Azure SQL Database
Azure Blob Storage
Azure Data Lake Storage Gen2
Azure Synapse Analytics
Azure Cosmos DB
Azure Table Storage
Azure Files
Azure SQL Managed Instance
Azure Key Vault
Azure Database for PostgreSQL
Azure Database for MySQL
Real-Time Example
A retail company stores invoices in Azure Blob Storage.
ADF reads invoice files from Blob Storage and loads them into Azure SQL Database for reporting.
2. Database Connectors
Used to connect to relational databases.
Supported databases include:
SQL Server
Oracle
MySQL
PostgreSQL
IBM DB2
SAP HANA
MariaDB
Teradata
Vertica
Informix
Sybase
Real-Time Example
A bank stores customer accounts in Oracle.
ADF copies customer information every night into Azure Synapse Analytics.
3. File-Based Connectors
Used for files stored on-premises or in the cloud.
Supported formats include:
CSV
Excel
JSON
XML
Parquet
Avro
ORC
Text files
Storage Locations
Local File System
Azure Blob Storage
ADLS Gen2
Amazon S3
Google Cloud Storage
FTP
SFTP
Real-Time Example
Every hour, an SFTP server receives supplier CSV files.
ADF automatically:
Reads the files.
Validates the data.
Loads it into Azure SQL Database.
Archives the processed files.
4. Cloud Storage Connectors
ADF integrates with multiple cloud storage providers.
Examples:
Azure Blob Storage
Azure Data Lake Storage
Amazon S3
Google Cloud Storage
Oracle Cloud Storage
Real-Time Example
A company migrating from AWS to Azure uses ADF to copy files from Amazon S3 to Azure Data Lake Storage.
5. SaaS Application Connectors
ADF supports popular Software-as-a-Service applications.
Examples:
Salesforce
Dynamics 365
ServiceNow
HubSpot
Marketo
Shopify
Real-Time Example
A sales organization pulls Salesforce opportunity data every night into Azure Synapse for executive dashboards.
6. ERP Connectors
Enterprise Resource Planning systems are common in large organizations.
Supported systems include:
SAP ECC
SAP S/4HANA
SAP BW
SAP HANA
Real-Time Example
A manufacturing company extracts purchase orders from SAP every hour and loads them into a data warehouse for analytics.
7. CRM Connectors
Examples:
Dynamics 365
Salesforce
Zoho CRM
Real-Time Example
Marketing teams synchronize customer information from Dynamics 365 into Azure SQL for campaign analysis.
8. Big Data Connectors
Examples:
Apache Hive
Apache HBase
Apache Spark
Azure Databricks
Snowflake
Real-Time Example
ADF orchestrates a pipeline that copies raw IoT data to Azure Data Lake, triggers an Azure Databricks notebook for processing, and stores the results in Snowflake.
9. API Connectors
ADF can integrate with RESTful web services.
Supported APIs:
REST APIs
OData
HTTP endpoints
GraphQL (through HTTP/REST patterns)
Real-Time Example
An e-commerce application exposes order data through a REST API.
ADF retrieves new orders every 30 minutes and stores them in Azure SQL Database.
10. Messaging Connectors
Examples:
Azure Service Bus
Azure Event Hubs
Kafka (typically integrated through compatible services or custom approaches)
Real-Time Example
An online shopping application sends order events to Azure Event Hubs. ADF orchestrates downstream processing and stores aggregated data for reporting.
Commonly Used Enterprise Connectors
| Connector | Source | Destination | Common Use Case |
|---|---|---|---|
| SQL Server | ✔ | ✔ | Transactional databases |
| Azure SQL Database | ✔ | ✔ | Cloud relational data |
| Oracle | ✔ | ✔ | Banking and ERP systems |
| Azure Blob Storage | ✔ | ✔ | File storage |
| ADLS Gen2 | ✔ | ✔ | Data lakes |
| Amazon S3 | ✔ | ✔ | Multi-cloud migration |
| Salesforce | ✔ | ✔ | CRM data |
| REST API | ✔ | ✔ | Third-party integrations |
| SAP | ✔ | ✔ | Enterprise ERP |
| Snowflake | ✔ | ✔ | Cloud data warehouse |
| PostgreSQL | ✔ | ✔ | Open-source databases |
| MySQL | ✔ | ✔ | Web applications |
How ADF Uses a Connector
Suppose you need to move customer data from SQL Server to Azure SQL Database.
Step 1: Create a Linked Service
Source:
SQL Server
Destination:
Azure SQL Database
Step 2: Create Datasets
Customer Table
↓
Azure SQL Customer Table
Step 3: Create a Copy Activity
Source Dataset
↓
Copy Activity
↓
Destination Dataset
Step 4: Publish and Run
ADF automatically:
Connects to SQL Server.
Reads the customer records.
Transfers the data securely.
Writes the data to Azure SQL Database.
Logs execution details for monitoring.
No custom coding is required for the data movement.
Authentication Methods Supported by Connectors
Different connectors support different authentication mechanisms, including:
SQL Authentication
Windows Authentication
Azure Active Directory (Microsoft Entra ID)
Managed Identity
Service Principal
Shared Access Signature (SAS)
Storage Account Keys
OAuth 2.0
Anonymous Access (where applicable)
Best Practice: Use Managed Identity or Microsoft Entra ID whenever possible, and store secrets securely in Azure Key Vault instead of embedding credentials.
Best Practices for Using Connectors
Use parameterized Linked Services to avoid duplication.
Store secrets in Azure Key Vault.
Use Self-hosted Integration Runtime for on-premises systems.
Prefer Managed Identity for Azure resources.
Configure retries for transient network failures.
Enable monitoring and alerting for production pipelines.
Choose Incremental Loads over Full Loads for large datasets.
Validate connectivity before deploying to production.
Real Enterprise Scenario
A multinational retail company needs to integrate data from several systems:
| System | Connector |
|---|---|
| SQL Server | SQL Server Connector |
| SAP | SAP Connector |
| Salesforce | Salesforce Connector |
| Oracle | Oracle Connector |
| Amazon S3 | Amazon S3 Connector |
| Azure Blob Storage | Azure Blob Connector |
| REST APIs | REST Connector |
| Azure Synapse Analytics | Synapse Connector |
Workflow:
SQL Server
│
Oracle
│
SAP
│
Salesforce
│
Amazon S3
│
REST APIs
│
Azure Data Factory
│
Data Validation
│
Azure Data Lake
│
Azure Synapse Analytics
│
Power BI Dashboard
This architecture enables a single, automated data integration platform that powers enterprise reporting, analytics, and machine learning while reducing manual effort and improving reliability.
Conclusion
Azure Data Factory connectors are the backbone of modern cloud data integration. They allow organizations to connect to a wide variety of on-premises, cloud, SaaS, and enterprise systems without writing complex integration code. By combining connectors with pipelines, activities, and Integration Runtime, organizations can build secure, scalable, and automated data workflows that support business intelligence, analytics, and AI initiatives.
