List of target databases or tools applications where data can be moved using Azure Data Factory (aka. Azure Data Factory Connectors)

-

List of target databases or tools applications where data can be moved using Azure Data Factory (aka. Azure Data Factory Connectors)

 

Azure Data Factory as we know is an PaaS (Platform as a Service) offering by Microsoft Azure. Which is known for its fully managed integration services. Which can also be called as serverless integration service as most of the other PaaS offering. With use of Azure Data Factory one can seamlessly integrate the source data source, perform the data transformation (if any) and load the data into a difference data store. Basically, it's a fully-managed ETL (Extract-Transform-Load) process/ tool in other words. 

 

But most of us don’t know which are the data sources where Azure Data Factory can make connection with using there in built connectors. Well, there are more than 90 built-in, maintenace-free connectors (as per Azure official documentation). And in this article, we will try to understand what are those lists of connectors available. 

 

So, first lists try to split the data into multiple categories and then see what are the connections within those categories available. 

  • Azure 
  • Database 
  • NoSQL 
  • File 
  • Generic protocol 
  • Services and apps 

Now let's look into each category and list down their connectors. 

 

Azure 

  • Azure Blob Storage 
  • Azure Cognitive Search Index 
  • Azure Cosmos DB (SQL API) 
  • Azure Cosmos DB's API for MongoDB 
  • Azure Data Explorer 
  • Azure Data Lake Storage Gen1 
  • Azure Data Lake Storage Gen2 
  • Azure Database for MariaDB 
  • Azure Database for MySQL 
  • Azure Database for PostgreSQL 
  • Azure Databricks Delta Lake 
  • Azure File Storage 
  • Azure SQL Database 
  • Azure SQL Managed Instance 
  • Azure Synapse Analytics 
  • Azure Table Storage 

 

Database 

  • Amazon Redshift 
  • DB2 
  • Drill 
  • Google BigQuery 
  • Greenplum 
  • HBase 
  • Hive 
  • Apache Impala 
  • Informix 
  • MariaDB 
  • Microsoft Access 
  • MySQL 
  • Netezza 
  • Oracle 
  • Phoenix 
  • PostgreSQL 
  • Presto 
  • SAP Business Warehouse Open Hub 
  • SAP Business Warehouse via MDX 
  • SAP HANA 
  • SAP Table 
  • Snowflake 
  • Spark 
  • SQL Server 
  • Sybase 
  • Teradata 
  • Vertica 

 

NoSQL 

  • Cassandra 
  • Couchbase 
  • MongoDB 
  • MongoDB Atlas 

 

File 

  • Amazon S3 
  • File System 
  • FTP 
  • Google Cloud Storage 
  • HDFS 
  • SFTP 

 

Generic protocol 

  • Generic HTTP 
  • Generic OData 
  • Generic ODBC 
  • Generic REST 

 

Services and apps 

  • Amazon Marketplace Web Service 
  • Common Data Service for Apps 
  • Concur 
  • Dynamics 365 
  • Dynamics AX 
  • Dynamics CRM 
  • GitHub 
  • Google AdWords 
  • HubSpot 
  • Jira 
  • Magento 
  • Marketo 
  • Microsoft 365 
  • Oracle Eloqua 
  • Oracle Responsys 
  • Oracle Service Cloud 
  • PayPal 
  • QuickBooks 
  • Salesforce 
  • Salesforce Service Cloud 
  • Salesforce Marketing Cloud 
  • SAP Cloud for Customer (C4C) 
  • SAP ECC 
  • SharePoint Online List 
  • Shopify 
  • Square 
  • Web table (HTML table) 
  • Xero 
  • Zoho 

 

Supported File Formats 

Over and above the list of connectors listed above, Azure Data Factory provides support for following file formats. 

  • Avro 
  • Binary 
  • Delimited text 
  • Excel 
  • JSON 
  • ORC 
  • Parquet 
  • XML 

 

Conclusion 

In this post we tried to identify the list of connectors available in Azure Data Factory. 

Hope you liked the post, do provide inputs in the comment, also if you think the article will be helpful for any of your friends and relatives then please do share the article with them.  

And don't forget to subscribe for the new post available so that you get notified on your mailbox.  

Happy Learning. 📚 

 


Reference 

https://docs.microsoft.com/en-in/azure/data-factory/connector-overview 

Comments

Post a Comment

Popular posts from this blog

Disaster Recovery of Azure API Management (APIM)

-
Image
Disaster Recovery of Azure API Management (APIM)     In this post, we will try to understand how we can apply a disaster recovery approach for Azure API Management aka. APIM. So, first of all, we will have to understand the importance of it. It's very important for an application using APIM to have a strong disaster recovery approach, as in case of any issue because of disaster reported, the system using the APIs underneath should be accessible for the users/ systems, and since the APIM is used as the fore front of the applications (mostly)  it's  important to restore the APIM service ASAP in case of any disaster reported, so that the application consuming the APIs underneath it  is  not having issue connecting to the APIs.       There are 2 broader options which one can think of:   Have a stand-by service in one or more regions   Service back-up and restore features    Let's  talk about both the approaches (one at a ...
Read more

What is Cloud Computing?

-
What is Cloud Computing?     I am sure you much have heard tons of time about Cloud Computing and as few among us might be even aware of aware of this term as well. And one must not be surprised by that as this term had blown up the internet industry and everyone in past decade or so has been taking about it even if they know about it or not.     So, what exactly is cloud computing?      Well to understand that we have to understand how do internet work.     How internet works   Well internet is nothing but millions and millions of systems connected with each other and sharing data among themself. So, where do we need cloud computing in this. Internet is controller/ managed by multiple data centers and each data centers use to have numerous machines/ hardware. And anyone who need to consume the resource available in these data center need to pay for a complete machine up till a few decades ago, even though you need the complete machine c...
Read more

API Aggregation Using Azure API Management

-
  API Aggregation Using Azure API Management         There are cases where we need to call multiple APIs from the client at the same time in order to proceed further with the processing from the client application. Now as oppose to calling those APIs individually  i.e.,  making separate HTTP requests for all those multiple APIs what if we can make one HTTP request and get all the responses aggregated in one response as opposed to multiple response isn't it going to be super cool.       So,  in this post we will try to understand how we can aggregate/ merge multiple API responses from the backend and provide one single request and response from the Azure API Management (APIM) to the calling client application.       To do this first of all we need to understand our APIs request body which we want to merge using APIM, so let say we want to call 2 APIs and  their   URI  are like this.       ...
Read more