The features that I've found most valuable, in order: That it is a complete ETL Solution, the second one is interface, the third one workflow, and the fourth one ease of use.
Team Leader at a insurance company with 201-500 employees
Complete solution with good interface, workflow, and ease of use
Pros and Cons
- "It is a complete ETL Solution."
- "The Microsoft documentation is too complicated."
What is most valuable?
What needs improvement?
The only thing that we're struggling with is increasing the competency of my team. So we think that the Microsoft documentation is too complicated.
I would like to see it more connected. I know they're working on the Snowflake data warehouse connector, but more connectors would be helpful.
For how long have I used the solution?
I've been using Azure Data Factory for a few months.
What do I think about the stability of the solution?
It is stable.
Buyer's Guide
Azure Data Factory
November 2024
Learn what your peers think about Azure Data Factory. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
What do I think about the scalability of the solution?
Azure Data Factory is a scalable solution.
How are customer service and support?
In terms of support, we haven't used the direct support but the community support is very good.
Which solution did I use previously and why did I switch?
We previously used the Oracle Warehouse Builder. The reasons we stopped using it were that Warehouse Builder is at the end of its life-cycle and its slow performance.
How was the initial setup?
The initial setup is complex.
What about the implementation team?
We first implemented it ourselves but we're using a partner now. We thought we could do it ourselves but we needed specialty help.
What's my experience with pricing, setup cost, and licensing?
I would highly recommend Azure Data Factory as it has proof of concept.
What other advice do I have?
We have nine people using Azure Data Factory.
On a scale of one to ten, I give it an eight.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Business Unit Manager Data Migration and Integration at a tech services company with 201-500 employees
Offers good flexibility and has good support
Pros and Cons
- "The flexibility that Azure Data Factory offers is great."
- "The number of standard adaptors could be extended further."
What is our primary use case?
We use this solution for data integration. We use it to feed operational data into a data warehouse. We also use it for creating connections between applications.
Within our organization, there are a few thousand users of Azure Data Factory.
We believe that the number of customers and usage of this product will extend over the next few years. For this reason, we invest a lot of resources in building skills, and we make sure to hire consultants who know their way around Data Factory.
What is most valuable?
The flexibility that Azure Data Factory offers is great.
What needs improvement?
The number of standard adaptors could be extended further. What we find is that if we develop data integration solutions with Data Factory, there's still quite a bit of coding involved, whereas we'd like to move in a direction with less coding and more select-and-click.
For how long have I used the solution?
I have been using Azure Data Factory for one year.
What do I think about the scalability of the solution?
We don't have any complaints regarding scalability or stability.
How are customer service and technical support?
I think Microsofts' technical support does a pretty good job. There is a lot of information available on the internet to find out how to use their products. There's also quite an active community. If you really can't find a solution, you can always call Microsoft. Our organization is partnered with Microsoft, so we usually get answers directly from them.
Which solution did I use previously and why did I switch?
We used SSIS. We're still using SSIS. SSIS is an old product. The development of SSIS has more or less stopped and the development is now focused on cloud services — it's the future. Azure Data Factory Is great because it's a cloud service; you do not have to take care of the installation and configuration yourself. The cost buildup is also quite different. I am not sure that's a huge financial advantage yet, but we do believe that it will be in the future.
How was the initial setup?
The initial setup was straightforward.
We didn't have to deploy Azure Data Factory. It's available as an Azure service, so Microsoft takes care of that.
What's my experience with pricing, setup cost, and licensing?
It's a pay-per-use model. So if you run it, it's hardly licensing. The entire cost of Azure is per-use. The price you pay is determined by how much you use it.
What other advice do I have?
I would definitely recommend Azure Data Factory. On a scale from one to ten, I would give this solution a rating of eight.
If there were a larger amount of automated features, I would give them a higher rating. As I mentioned earlier, if we are working on complex applications, then there is a lot of coding involved. What we hope is that over time, there'll be less coding and more "off the shelf" functionality.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Azure Data Factory
November 2024
Learn what your peers think about Azure Data Factory. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
Principal Data Architect at Predica
Very stable, a friendly user interface and easy to set up
Pros and Cons
- "The user interface is very good. It makes me feel very comfortable when I am using the tool."
- "The solution should offer better integration with Azure machine learning. We should be able to embed the cognitive services from Microsoft, for example as a web API. It should allow us to embed Azure machine learning in a more user-friendly way."
What is most valuable?
The user interface is very good. It makes me feel very comfortable when I am using the tool.
What needs improvement?
The solution could use some merge statements.
The solution should offer better integration with Azure machine learning. We should be able to embed the cognitive services from Microsoft, for example as a web API. It should allow us to embed Azure machine learning in a more user-friendly way.
For how long have I used the solution?
I've been using the solution for three years.
What do I think about the scalability of the solution?
The solution is scalable.
How are customer service and technical support?
We've been satisfied with the level of technical support we've received.
How was the initial setup?
The initial setup is very straightforward. The only thing which we had to consider at the beginning was the gateway for the on-premises environment. Otherwise, it's very easy.
What other advice do I have?
We use both the on-premises and cloud deployment models. We typically work with enterprise-level companies.
Azure Data Factory is pretty good but should be considered as an orchestrator, not as an integrated tool. We can use some building components in that tool to orchestrate the entire workflow but if we are thinking about more details, processing, or data modification during the flow, we'd have to consider Azure Databricks or Data Flow for making those calculations or changes. Users will need Azure Data Factory plus third party tools to reach that level of functionally.
I would recommend using Data Factory. I don't have a lot of experience with integration or with integration services, for example, SQL server integration services. However, there are points that should be considered if you are already using SQL server integration services already. You can implement the packages already prepared in Azure Data Factory. It's something that needs to be considered when deciding which technology you are going to use.
I'd rate the solution eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Principal Consultant at a tech services company with 11-50 employees
A straightforward solution with a nice interface and ability to integrate with GitHub
Pros and Cons
- "The solution has a good interface and the integration with GitHub is very useful."
- "In the next release, it's important that some sort of scheduler for running tasks is added."
What is our primary use case?
We are working on a data warehouse integration which means that I am working on some big data projects. I'm preparing data for the licensing. One of the projects is preparing data in Azure Data Lake, to run some transformation scripts, perform some ETL processing, and to fulfill the stage layer of the data warehouse. It means that I help with ETL use cases.
What is most valuable?
I like the feature that allows you to connect to different sources. You can go through forms and click on them and you don't have to provide the scripts. The solution has a good interface and the integration with GitHub is very useful.
There is also a self-service integration that allows you to run the BTS pages on the SQL server from an SIS. Users have an option to configure this self-service integration engine to run items as a part of a pipeline of the Azure data factory.
What needs improvement?
I think more integration with existing Azure platform services would be extremely beneficial.
In the next release, it's important that some sort of scheduler for running tasks is added. A built-in scheduling mechanism for running the treasury will be a very helpful improvement.
For how long have I used the solution?
I implement this solution and have been doing so for two years.
What do I think about the stability of the solution?
I've never experienced any issues with the solution's stability.
What do I think about the scalability of the solution?
The scalability of the connected engines makes this solution very scalable.
How are customer service and technical support?
Although I've had to contact support for other Azure products, I haven't had to for this solution, so I can't speak to any experience with technical support directly.
How was the initial setup?
The initial setup is straightforward. It's got a very nice welcome page where everything explained. Depending on the complexity, deployment takes only a few days. You only need one person for the deployment of the solution. This is dependent, however, on how many pipelines you are implementing. Afterward, you would probably only need one person to maintain it.
What about the implementation team?
I'm an integrator, so I work with clients to help them implement the solution.
What's my experience with pricing, setup cost, and licensing?
I'm not sure of the specific cost, but it is monthly and is somewhere in the ballpark of a few hundred Euros. You don't have to pay for extras. Everything is included in the cost.
What other advice do I have?
I don't use Azure Data Factory for my own company; I help clients implement the solution for their companies.
In terms of advice that I would give to others looking to implement the solution, I would say you have to learn. You have to really understand the overall concept. It does not allow you to just click and go.
I would rate this solution ten out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Enterprise Data Architect at a financial services firm with 201-500 employees
Good support, easy to use, and integrates well with the rest of the activities on Azure
Pros and Cons
- "Its integrability with the rest of the activities on Azure is most valuable."
- "It can improve from the perspective of active logging. It can provide active logging information."
What is our primary use case?
In my new organization, we are currently analyzing this solution. In my previous organization, I have worked with Azure Data Factory and Databricks.
It is deployed in a virtual private cloud.
What is most valuable?
Its integrability with the rest of the activities on Azure is most valuable.
It is also easier to work with. It has a nice user interface that would seem very familiar to some of the people who are coming from Microsoft SSIS and other similar kinds of activities. It makes it easy for them to pick it up quickly.
What needs improvement?
It can improve from the perspective of active logging. It can provide active logging information.
It should provide support for changing data capture on several other platforms.
For how long have I used the solution?
I have been using this solution for two years.
What do I think about the scalability of the solution?
It is scalable. From the security perspective, it depends on how we implement it. It depends on the organization, but I don't see a challenge.
In my previous organization, we had close to a hundred people.
How are customer service and technical support?
Their technical support is very good.
How was the initial setup?
It was very easy.
What other advice do I have?
I would generally recommend this solution if you have an Azure setup or Azure as a baseline.
I would rate Azure Data Factory an eight out of 10.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Microsoft Consultant at a tech services company with 201-500 employees
Good support for SAP services and databases, a simple initial setup and good scalability
Pros and Cons
- "From what we have seen so far, the solution seems very stable."
- "The solution needs to integrate more with other providers and should have a closer integration with Oracle BI."
What is most valuable?
The support for SAP services and databases, specifically SAP HANA, has been a game-changer for us.
What needs improvement?
It would be helpful if they could adjust the data capture feature so that when there are source-side changes ADF could automatically figure it out.
The solution needs to integrate more with other providers and should have a closer integration with Oracle BI.
For how long have I used the solution?
I've been working with the solution for just over a year.
What do I think about the stability of the solution?
From what we have seen so far, the solution seems very stable.
What do I think about the scalability of the solution?
The solution is scalable. Right now, we have only three or four people on it. We may increase usage int eh future.
How are customer service and technical support?
We have direct technical support in Israel. In India, we haven't used it yet. However, for other services, the help provided is fine.
How was the initial setup?
The initial setup was pretty fast and simple. I wouldn't say it was too complex. For deployment, it depends on your environment. In our POC, it didn't take more than two to three hours. In the production environment, however, it takes a bit more time for operations.
What's my experience with pricing, setup cost, and licensing?
In general, we've been satisfied with the pricing. However, since it's a service based on usage, it's really hard to estimate the cost in advance for this product. This makes it hard to quote. It's not so easy to estimate the costs in advance when giving a quote. That makes it difficult to convince some customers because most would like to see a number in advance.
What other advice do I have?
We primarily use the solution in a hybrid environment. We're Azure partners.
I would suggest others start with a small POC and with a smaller dataset or simple pipeline to test the product before fully implementing it. Users shouldn't hesitate to try it, because there are not so many risks. Practice is the best way to start with this service, as opposed to planning.
I'd rate the solution eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Azure Data Factory Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Popular Comparisons
Informatica Intelligent Data Management Cloud (IDMC)
Informatica PowerCenter
Teradata
Oracle Data Integrator (ODI)
Talend Open Studio
IBM InfoSphere DataStage
Oracle GoldenGate
Palantir Foundry
SAP Data Services
Qlik Replicate
StreamSets
Alteryx Designer
Fivetran
Buyer's Guide
Download our free Azure Data Factory Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Which solution do you prefer: KNIME, Azure Synapse Analytics, or Azure Data Factory?
- How do Alteryx, Denod, and Azure Data Factory overlap (or complement) each other?
- Do you think Azure Data Factory’s price is fair?
- What kind of organizations use Azure Data Factory?
- Is Azure Data Factory a secure solution?
- How does Azure Data Factory compare with Informatica PowerCenter?
- How does Azure Data Factory compare with Informatica Cloud Data Integration?
- Which is better for Snowflake integration, Matillion ETL or Azure Data Factory (ADF) when hosted on Azure?
- What is the best suitable replacement for ODI on Azure?
- Which product do you prefer: Teradata Vantage or Azure Data Factory?