Azure Data Factory Reviews

The primary use case is to connect to various different data sets and do an EAT into our data warehouse.

We have been using drivers to connect to various data sets and consume data. The solution gives everything under one roof, which is an important feature.

We require Azure Data Factory to be able to connect to Google Analytics.

I have been using the solution for two years.

The solution is stable.

The solution is scalable.

We had a few technical calls with the Microsoft technical support team for some issues that we were facing, which they helped us resolve.

The initial setup is straightforward and the team is able to deploy between six and seven days.

The implementation was completed in-house.

The cost is based on the amount of data sets that we are ingesting. The more data we ingest the more we pay.

I give the solution a nine out of ten. We have been happy with all the customer implementations, and the customers are satisfied with the ADF pipelines. We are also currently examining the Synapse pipelines, which are likely similar.

We have six developers using the solution in our organization.

People should use the solution for two reasons. Firstly, we can switch off any data pipelines we set up to save costs. Secondly, there are several connectors available in one place, including most standard connectors.

We use this solution to quickly instantiate certain components in Azure with the aim of having consistent use of certain components and objects. It provides one point of reference rather than having the need to replicate points of references, and then having to keep them in sync. 

It has helped our company by providing consistency. For example, by making sure that the way certain objects and components are defined is consistent throughout every step. If things change at any point, they should be reflected at all points. It's the consistency that makes implementations less buggy and less complex.

The function is the central point of reference and the most valuable thing about Data Factory.

I'd like to see videos on YouTube or the Microsoft site with more detailed implementations. The solution lacks a decent UI that allows us to see what kinds of requests are for what objects and how the population of objects is being requested and compared. Right now we have to look at logs to get an idea of what types of calls the data factory receives in what sequence, for example. It would be nice to be able to see it graphically because we currently have to interpret the logs and then create a graphical representation to have an idea of what's going on. In general, it could be simplified and made more user-friendly.

I've been using this solution for six months.

This solution is stable. 

There are thousands of users so the solution is scalable. 

The customer service is excellent. 

Positive

I previously used a combination of solutions to achieve the same end. Data Factory simplifies things which is why we switched to it. 

The initial setup was complex. The deployment was carried out in-house and we had around 10 people involved in the implementation. 

In terms of time and effort savings, we have a return on our investment. 

It's important to have a good data model before you start using the solution; an idea of the types of data architecture, data objects and components in order to use them. Because of the lack of more user-friendly interfaces, especially for the people debugging the system, I rate this solution eight out of 10.

As a management consultancy company, we help our clients deploy Azure Data Factory or any other cloud-based solution depending on data integration needs. Regarding how we use Azure Data Factory within our company, we are on the Microsoft Stack, so we use the solution primarily for data warehousing and integration.

The feature I found most helpful in Azure Data Factory is the pipeline feature, including being able to connect to different sources.

I also found running Python codes whenever you need to valuable in Azure Data Factory, especially for certain features of the solution, such as data integrations, aggregations, and manipulations.

Azure Data Factory also has built-in security, which is another valuable feature.

I also like that you get access to the whole Azure suite through Azure Data Factory, so the overall architecture design, defining security and access, role-based access management, etc. It's helpful to have the whole suite when designing applications.

Areas for improvement in Azure Data Factory include connectivity and integration.

When you use integration runtime, whenever there's a failure, the backup process in Azure Data Factory takes time, so this is another area for improvement.

Database support in the solution also has room for improvement because Azure Data Factory only currently supports MS SQL and Postgres. I want to see it supporting other databases.

If you want to connect the solution from on-premises to the cloud, you will have to go with a VPN or a pretty expensive route connection. A VPN connection might not work most of the time because you have to download a client and install it, so an interim solution for secure access from on-premise locations to the cloud is what I want to see in Azure Data Factory.

I've been using Azure Data Factory for about a year now.

Azure Data Factory is very stable, so it's a four out of five for me. In some instances, the solution failed, but I wouldn't wholly blame Azure Data Factory because my company connected to some on-premise databases in some cases. Sometimes, you'll get errors from self-hosted integration, faulty connections, or the on-premise server is down, so my rating for stability is a four.

Scalability-wise, Azure Data Factory is a four out of five because Microsoft is still developing certain tiers, which means you can't upgrade an older skill or tier. In contrast, the more modern, newer tiers could be upgraded easily. Rarely will you get stuck in one platform where you have completely destroyed that container and then fit a new container. Most of the time, Azure Data Factory is pretty easy to scale.

We haven't used Microsoft support directly because whenever we have issues with Azure Data Factory, we can find resolutions through their online documentation.

We're using both Azure Data Factory and SSIS.

We had several in-house solutions, but we moved to Azure Data Factory because it was straightforward. From a deployment standpoint, the solution comes with different services, so we didn't have to worry about separate hardware or infrastructure for networking, security, etc.

The initial setup for Azure Data Factory was easy, so I'd rate the setup a four out of five.

The implementation strategy was looking into what my organization needed overall, then planning and direct deployment. My company first did a test, a dummy version, then a UAT with stakeholders before going into production.

It took about two months to complete the deployment for Azure Data Factory.

An in-house team, the digital data engineering team, deployed Azure Data Factory.

We're still computing the ROI from Azure Data Factory. It's too early to comment on that.

My company is on a monthly subscription for Azure Data Factory, but it's more of a pay-as-you-go model where your monthly invoice depends on how many resources you use.

On a scale of one to five, pricing for Azure Data Factory is a four.

It's just the usage fees my company pays monthly. No support fees because my company didn't need support from Microsoft.

If you're not using core Microsoft products, the cost could be slightly higher, for example, when using a Postgres database versus an MS SQL database.

My company uses Azure Data Factory, SSIS, and for a few other instances, Salesforce.

My company currently has about fifty Azure Data Factory users, but not directly exposed to the solution compared to the developers; for example, members of corporate management and other teams apart from the development team are exposed to Azure Data Factory.

Shortly, there could be about two hundred users of Azure Data Factory within the company.

The developer team working directly on Azure Data Factory comprises ten individuals.

For the maintenance of the solution, my company has two to three staff, but it could reach up to eight or ten for the entire product. It's a mix of engineers and business analysts who handle Azure Data Factory maintenance.

I'd rate Azure Data Factory as eight out of ten.

My company is an end user of Azure.

My clients use Data Factory to exchange information between the on-premises environment and the cloud. Data Factory moves the data, and we use other solutions like Databricks to transform and clean up the data. My teams typically consist of three or four data engineers.

I like how you can create your own pipeline in your space and reuse those creations. You can collaborate with other people who want to use your code.

DataStage is easier to learn than Data Factory because it's more visual. Data Factory has some drag-and-drop options, but it's not as intuitive as DataStage. It would be better if they added more drag-and-drop features. You can start using DataStage without knowing the code. You don't need to learn how the code works before using the solution.

I think the communication about the ADA's would be interesting to see in the platform. How to interact with those kind of information and use it on your pipelines.

I have used Data Factory for eight months.

I have never experienced downtime with Data Factory. 

It isn't that expensive to scale Data Factory up. My client can ask for more resources on the tool, and paying more is never an issue. 

I rate Azure support seven or eight out of 10. There is room for improvement. Sometimes, you don't know where the errors originate. You have to send a ticket to Azure, and they take two or three days to respond. The issue may resolve itself by then. The problem is fixed, but you don't know how to prevent it or what to do if it happens in the future. 

The data transfer has stopped a few times for unknown reasons. We don't know if the resources are insufficient or if there is a problem with the platform. By the time we hear back from Microsoft, the issue has been resolved.

Positive

Data Factory is effortless to set up.

I rate Azure Data Factory nine out of 10. When implementing Data Factory, you should document where you are building so you can pass that information. Sometimes you build something for a specific purpose, but you can use that information for other solutions. If you have a community where you are building things, you can reuse them on the platform, so don't need to build everything from scratch.

For developers that are very accustomed to the Microsoft development studio, it's very easy for them to complete end-to-end data integration.

One of the features that still is in development is data privacy to the cloud side of the SAP integration.

I have been using Azure Data Factory for 3 years. 

I rate the stability a 9 out of 10. 

6 developers are using the solution at present. 

The initial setup is not very straightforward. I rate it a seven out of ten. 

The pricing is a bit on the higher end. 

Overall, I rate the solution an 8 out of 10. 

I'm not sure how much information I can provide regarding to some kind of security of my company, but I can tell you that we were migrating integrations from from platform to the other, and the other platform was error data factory.

For me, it was that there are dedicated connectors for different targets or sources, different data sources. For example, there is direct connector to Salesforce, Oracle Service Cloud, etcetera, and that was really helpful.

It's a good idea to take a Microsoft course. Because they are really helpful when you start from your journey with Data Factory.

I have been using Azure Data Factory for one year. 

The solution doesn't have stability issues. 

It is easy to scale. 

The initial setup is straightforward. Deployment is automatic and takes few minutes. 

Overall, I would rate it an eight out of ten. 

We use Azure Data Factory to set up a data lake information repository.

Most of our customers are Microsoft shops and prefer Azure Data Factory because they have good licensing options and a trust factor with Microsoft. Our core customers are traditional Microsoft shops who prefer to expand on Microsoft on-cloud.

Azure Data Factory's pricing in terms of utilization could be improved. Our customers complain that the solution's bills keep growing.

I have worked with Azure Data Factory for more than five years as a consultant.

Azure Data Factory is a pretty stable solution. I rate Azure Data Factory a nine out of ten for stability.

Azure Data Factory is a scalable solution. We have around 15 to 20 customers, of which about 8 to 10 use Azure Data Factory.

Azure Data Factory's initial setup needs some amount of professional training and qualification.

It seems very low initially, but as the data grows, the solution’s bills grow exponentially.

Azure Data Factory is deployed on-cloud for our clients.

Azure Data Factory is a pretty solid solution with all the factors and integration built in. It's as good as any product.

I recommend users compare with Snowflake before choosing Azure Data Factory. We've had customers who prefer Snowflake just for its ease of use. Since we're not a Microsoft official reseller, I give options to customers and then let them pick and choose some from Azure Data Factory, Snowflake, or anything on Amazon.

Overall, I rate Azure Data Factory an eight out of ten.

Our company uses the solution to extract, transform, and load the data into the database.

Feature-wise, one of the most valuable ones is the data flows introduced recently in the solution.

Currently, our company requires a monitoring tool, and that isn't available in Azure Data Factory. Although the platform displays which pipelines are running, it doesn't offer a monitoring tool that allows for the sequential execution of pipelines and the ability to visualize end-to-end data flow. As such, this feature is currently missing from the platform.

I have been using Azure Data Factory for more than six years. Also, I am an end-user of the solution, and I initially used to work on Azure Data Factory V1. Now, I have switched to Azure Data Factory V2.

It is a stable solution. Stability-wise, I rate the solution an eight or nine out of ten.

Scalability-wise, I rate the solution a seven or eight out of ten. So, scalability can be improved. Also, there are around 150 people in my company using the solution. Moreover, we use the solution daily in our company.

I rate the technical support between eight to nine out of ten.

Positive

Previously, I was using Informatica. My company wanted to shift to a solution that could be deployed on the cloud, so we chose Azure Data Factory.

The solution's initial setup process was easy. On a scale where one is difficult and ten is easy, I rate the initial setup process an eight out of ten. The solution is deployed on the cloud.

Since multiple projects are going on in my organization, there is no uniformity in the time taken to deploy the solution in our company. However, I can say that it only takes a few days to carry out the deployment process.

Our organization has multiple project teams, so each team carries out its deployment process.

To give an average, I would consider that if there are fifty ongoing projects in our company, and if we consider a person from each project, fifty people are needed for the deployment and maintenance process.

The solution's implementation process was done with our in-house team's help.

I cannot comment on the pricing parts since our company's admin team handles it.

Those who want to move to a cloud platform can choose Azure Data Factory since it is the best tool. Since certain improvements are required in the solution, I rate the overall solution an eight out of ten.

We primarily use the solution for data warehousing. I'm integrating data from multiple sources.

I have a team helping me out from India. It helps manage the data and collect everything from sources.

The product has a lot of features.

It makes it easy to collect data from different sources.

The solution offers good integration with pretty much any system.

I like that it is cloud-based. 

Sometimes when I run some jobs, I have issues with the log flow. I want to see where the data goes. I want to see the data stream.

I'd like more integrations with other APIs. Sometimes I need to do some coding, and I'd like to avoid that. I'd like no-code integrations. 

I've been using the solution for four or five years. 

I'm using the solution as an end-user.

We are using the latest version of the solution. 

I'd rate the solution seven out of ten.

I primarily use Data Factory to ingest data. For example, if we need to pull data into our data warehouse from somewhere like Azure Event Hub or salesforce.com.

We have telemetry that streams into an Azure Event Hub, and Data Factory allowed us to move that data from the Event Hub into our data lake and reduce the cost of that compared to the other tooling we were using.

Data Factory's best features are simplicity and flexibility. It's been very easy to set up connections to different types of data sources to pull data into our warehouse.

Data Factory would be improved if it were a little more configuration-oriented and not so code-oriented and if it had more automated features.

I've been using Data Factory for about three years.

I would rate Data Factory's stability eight out of ten.

I would rate Data Factory's scalability eight out of ten.

The initial setup was straightforward, and only one person was required for deployment.

I would rate Data Factory's pricing nine out of ten.

I think Data Factory is a good fit when you need a light, inexpensive way to ingest data. I would rate it eight out of ten.