Azure Data Factory Reviews

Used Azure Data Factory, Data Flow (private preview) and Databricks to develop data integration processes from multiple and varied external software sources to an OLTP application Azure SQL database. The tools are impressively well-integrated, allowing quick development of ETL, big data, data warehousing and machine learning solutions with the flexibility to grow and adapt to changing or enhanced requirements. I can't recommend it highly enough.

This solution will allow the organisation to improve its existing data offerings over time by adding predictive analytics, data sharing via APIs and other enhancements readily. It's as simple as extending the data pipelines with new modules and components. The solution is improving the organisation by offering something the organisation can grow with.

Data Flow and Databricks are going to be extremely valuable services, allowing data solutions to scale as the business grows and new data sources are added.

Data Flow is in the early stages — currently public preview — and it is growing into a tool that will offer everything other ETL tools offer. There are a few features still to come. The thing we missed most was data update, but this is now available as of two weeks ago. A feature that is confirmed as coming soon is the ability to pass in a parameter and filter, etc.

We use Data Factory in our projects, which we deliver to customers. We have almost five implementations in which we're using Data Factory.

It's cloud-based, but there's the integration runtime, which you can connect to on-premises sources. You can transfer data from on-premises to the cloud. We're integrating on-premise data sources to cloud data-based services, like rescue or finance and so on.

Azure Data Factory is very good for enterprise organizations like banks and international insurance companies.

It's cloud-based.

I like the basic features like the data-based pipelines.

We have had some issues, but it's critical to use Data Factory for what it was designed for. It's not very good for iteration processes for loop data activity because you must wait for the runtime. This is a downgrade, but we developed some workaround for it, and we're running the Azure function for these iteration processes.

There's space for improvement in the development process of the data pipelines.

I would rate the stability as nine out of ten, but there are some issues with the responsiveness of the interface.

It's easy to scale.

I would rate the technical support as four out of five.

I'm mostly working with cloud technology, and we use other vendors. On-premises, there is another team in my company that's working with Oracle tools. I'm focusing only on Azure technology, which means that I personally don't have hands-on experience with different tools.

Setup is very straightforward and simple, but it depends on the customers. We have more than 15 data engineers who have data engineer certification from Microsoft. For them, it's a very easy process. 

Of course, there are some issues when configuring the on-premise integration runtime because you have to deal with the network settings on on-premise infrastructure. In terms of ADF as a product, there are very good guides and documentation that you can use to navigate how to solve certain issues.

The price is fair.

I would rate this solution as nine out of ten.

For any customer who needs to transfer or transform the data from sources for analytical purposes, Azure Data Factory is a good product for that.

I like Azure Data Factory, it works quite well.

It is always effective. It's extremely consistent.

The only thing I wish it had was real-time replication when replicating data over, rather than just allowing you to drop all the data and replace it. It would be beneficial if you could replicate it.

Real-time replication is required, and this is not a simple task.

We are using the latest version of Azure Data Factory.

I have no issues with the stability of the Azure Data Factory. We have not had any glitches.

Azure Data Factory is extremely simple to scale.

This solution is used by a dozen people in our company.

I have not contacted technical support. We haven't needed the assistance of technical support.

We use Microsoft products such as Azure Databricks.

Azure Data Factory is the only solution that I have used since I started with this company.

The initial setup is pretty straightforward. However, there is a bit of a learning curve, but once you get it, it's pretty simple.

It's not particularly expensive.

It works very well.

I would rate Azure Data Factory an eight out of ten.

We use the solution to gather data from four separate operational systems.

The data copy template is a valuable feature. With the pipeline template, it takes only a few clicks for the on-premises data to come in. 

There is no built-in function for automatically adding notifications concerning the progress or outline of a pipeline run. I believe this requires a bit of development through power ups, but it would be nice to have a task for firing off an email through the GUI.

I have been using Azure Data Factory for around six months.

When it comes to stability, the solution is similar to the previous Azure Synapse Analytics. They are both very easy.

When it comes to scalability, the solution is similar to the previous Azure Synapse Analytics. They are both very easy.

The licensing cost is included in the Synapse.

I rate Azure Data Factory as an eight out of ten. 

I primarily use the solution for my small and medium-sized clients.

So far, I'm quite happy with the solution overall. It's got a lot of tools that I use in my work, and these are items I'm already recommending to my clients. I'm quite happy with it.

I'm not sure if I have any complaints about the solution at the moment. There are a few bits and pieces that we would like to see improved. These include improvements related to the solution's ease of use and some quality flash upgrades. However, these are minor complaints. 

If the user interface was more user friendly and there was better error feedback, it would be helpful.

I've been working with the solution for three to four years now.

On the tool itself, we've never experienced any bugs or glitches. There haven't been crashes. Stability has been good.

I haven't had the ability to scale any of my projects personally. I also wouldn't need to scale too high if I did. I'm not sure if I can speak to aspects of scalability as I've never dealt with it.

I've contacted Microsoft technical support in the past. I have to say that I've had a good experience with them. I've been quite satisfied with their level of service.

The initial setup was very straightforward. I wouldn't describe it as complex.

Deployment is fast. It only takes about half an hour at most.

I don't have any information about the pricing. I don't deal with that aspect of the solution.

I typically work with small to medium-sized companies. I'm a consultant, so I give different advice based on what my clients need and what they want to do. However, I would recommend this product. 

I'd rate the solution eight out of ten. All of the issues I have with the solution are very minor, however, it means the solution isn't exactly perfect just yet.

Azure Data Factory is for data transformation and data loading. It works from your transaction systems, and we are using it for our HRMS, Human Resource Capital Management System. It picks up all the transactional data pick and moves into the Azure Data Warehouse. From there, we would like to create reports in terms of our financial positions and our resource utilization project. These are the reports that we need to build onto the warehouse.

The purpose of Azure Data Factory is more about transformations, so it doesn't need to have a good dashboard. But, it has a feeding user interface for us to do our activities and debug actions. I think that's good enough.

Azure Data Factory's most valuable features are the packages and the data transformation that it allows us to do, which is more drag and drop, or a visual interface. So, that eases the entire process.

Azure Data Factory setup is quite user-friendly.

I am happy with the interface.

We are too early into the entire cycle for us to really comment on what problems we face. We're mostly using it for transformations, like ETL tasks. I think we are comfortable with the facts or the facts setting. But for other parts, it is too early to comment on.

We are still in the development phase, testing it on a very small set of data, maybe then the neatest four or bigger set of data. Then, you might get some pain points once we put it in place and run it. That's when it will be more effective for me to answer that.

We are building Azure Data Factory right now internally to extract data from our transactional systems and put them into the warehouse so that the reporting engine can be built too.

We have not tried it scaling up. But, Azure promises the stability and scalability should not be an issue.

From a development perspective, I think there were four developers who use Azure Data Factory. From a warehouse perspective, once we roll out the reports out, it should be used by at least 40 or 50 people minimum.

Generally, the documentation is pretty decent. All the issues that come up are here in the documentation part. We've not really had to go to Microsoft as of now from a support perspective. The documentation and the support that we get over the internet is quite good.

The initial setup was very straightforward.

The initial setup was quite quick, nothing much to do. Now, we are more developing the use cases. A use case with data generally takes around four or five days a use case because it will start right from identifying the right field, getting the data, transforming it, and finalizing the warehouse structure. That makes a bit of a thing, but it's pretty straightforward.

We are a technical team so we implemented it in-house.

It's a pay-as-you-go module. I'm not very sure about cost because our usage currently is very low. But, I feel that if the usage extends beyond a certain threshold, it will start getting expensive.

It depends what the threshold is. I see we're not at that threshold right now, so it's pretty decent right now.

We were looking at certain other projects and products. For example, we were looking at Snowflake that has a data warehouse. But the project wasn't working. That's why we selected Azure. The primary reason is the skills are very easily available for Azure. The second is from our strategy perspective, because we were trying to be a Microsoft shop it fits into our strategy. That's all.

If you're a Microsoft shop, if you want to get there easily, I think Azure is one of the better choices. Otherwise, other tools generally require specialized skills and specialized partners to come and implement it. Once implemented, then it becomes much easier to install.

I can't comment right now. I've not talked to it in that fashion. Whatever was required by us, business users have been satisfied in the Data Factory setup.

On a scale of one to ten, I would give Azure Data Factory an eight.

We primarily used this solution for getting data from a client's server, or online data, to an Azure Data Lake. We create pipelines to orchestrate the data flow from source to target.

The most valuable feature is the copy activity. Instead of creating a pipeline and then doing a source to target copy, this feature will create the pipeline directly.

Snowflake connectivity was recently added and if the vendor provided some videos on how to create data then that would be helpful. I think that everything is there, but we need more tutorials.

We have been working with Azure Data Factory for the past two years.

Occasionally, there are timeout issues that happen when connecting to the source or the target. Normally, you just hit refresh and it will connect properly.

Being a cloud product, it can scale as much as we need.

In my project, there are ten people using this product.

I have been in contact with technical support and it's good, as long as you directly connect with the appropriate technical person right away. When you raise an issue, sometimes the people who are available are unfamiliar with that particular technology, so they have to route the issue to the concerned person. This routing takes at least one or two days, so if you can directly get the corresponding person allocated to the ticket, that would be great. 

The initial setup is simple and it only takes perhaps five minutes to deploy.

When one of our developers wants to use it, they can create their own jobs.

Our deployment was completed by an in-house team.

No maintenance is required and when we experience problems, we normally solve them on our own.

The licensing is a pay-as-you-go model, where you pay for what you consume.

If you have Azure as a cloud service and you want to perform ETL then Azure Data Factory is a product that I can recommend.

I would rate this solution a six out of ten.

We are a tech services company and this is one of the tools that we use when implementing solutions for our clients. I am currently managing a team that is working with the Azure Data Factory.

Our clients that use this solution are migrating their data from on-premises to the cloud.

One of our clients is building an integrated data warehouse for all of their data, using this solution. It is used to extract all of the data from different servers and store it into one place.

Our clients find that this solution has a very good performance. They like the speed.

It is easy to deploy workflows and schedule jobs. You can just click on the desktop and it works.

The setup and configuration process could be simplified.

We have been using Azure Data Factory for the past six months.

This is a stable product and we're expecting more updates from Microsoft. We have not used more than one terabyte of data so that remains untested, but for one terabyte it works fine.

Development is only done on an occasional basis, but the solution is used every day. If it is streaming data then the process is continuous, otherwise, it is initiated by the user on demand.

This solution is 100% scalable.

We have two clients working with this solution.

It is another team who is responsible for contacting technical support.

We have used other ETL solutions in the past, and Azure Data Factory is the best one. Compared to SSIS, for example, ADF is easier to use and the performance is better.

Our clients are migrating from on-premises SSIS solutions to the cloud because they want to take advantage of the latest technologies.

The installation is very simple and it doesn't take much time. For us, the deployment took about two days, which does not seem unreasonable for something that is on the cloud. Most of the time is spent waiting for credentials.

Depending on the sources of the data, four people are required for deployment and maintenance. If the sources are SQL databases then it is straightforward and four people can cope with it. If the data is more difficult then we may need more people.

The deployment is done in-house with a technical person with knowledge of the Azure cloud.

This is a cost-effective solution.

We have another team that is moving to AWS, but for now, we will continue working with Azure Data Factory. Once they have explored the AWS solution fully, we will compare the two.

Within the next six months, we are planning to enter into the machine learning part of this solution. This is a product that I can recommend.

I would rate this solution an eight out of ten.