Try our new research platform with insights from 80,000+ expert users
reviewer2405217 - PeerSpot reviewer
Strategy Consultant at a computer software company with 201-500 employees
Consultant
Top 20
Hierarchical namespace for data and offers security measures like RLS
Pros and Cons
  • "Microsoft is quite good when it comes to integration. They have multiple connectors available and different ingestion and integration processes available."
  • "Microsoft, in general, needs to simplify its licensing model. That's one of the biggest issues with Microsoft. The licensing model is either quite difficult to understand or is constantly evolving."

What is our primary use case?

It is typically used in my data analytics workflows. I use it as a data lake. 

What is most valuable?

The hierarchical namespace is okay. It's not the kind of product I would have any issue with.

RLS (Row-Level Security) and these kinds of things have been effective for protecting data. 

Microsoft is quite good when it comes to integration. They have multiple connectors available and different ingestion and integration processes available.

What needs improvement?

There is room for improvement in Microsoft support. I didn't have a good experience with it. 

Microsoft, in general, needs to simplify its licensing model. That's one of the biggest issues with Microsoft. The licensing model is either quite difficult to understand or is constantly evolving.

I like the move from Data Lake to Lakehouse. I think it's more up to Microsoft, regarding the trends of the market and what organizations need.

For how long have I used the solution?

I use it, but it's integrated into Microsoft Fabric. 

Buyer's Guide
Azure Data Lake Storage
October 2025
Learn what your peers think about Azure Data Lake Storage. Get advice and tips from experienced pros sharing their opinions. Updated: October 2025.
872,706 professionals have used our research since 2012.

What do I think about the stability of the solution?

I don't have any performance issues. It's a reliable kind of product.

I would rate the stability an eight out of ten. 

How are customer service and support?

Technical support is not something I'm using a lot because I had a poor experience with it in the past, but not on these products, technically. I'm not using a lot of Microsoft support currently.

So, I don't really need it anymore because I've benefited from colleagues and the community to help, and it helps a lot.

Which solution did I use previously and why did I switch?

I work with Microsoft products in general, but mostly Fabric. There is also Data Factory, Databricks, and Synapse. My company is a Microsoft partner only.

What's my experience with pricing, setup cost, and licensing?

Microsoft, in general, needs to simplify its licensing model. That's one of the biggest issues with Microsoft. The licensing model is either quite difficult to understand or is constantly evolving. I think there's a will to simplify it because one of the biggest client complaints is that the licensing model is always messy and evolving. It's quite difficult to understand.

However, I'm quite satisfied with the pricing. It's quite good.

What other advice do I have?

I would recommend it to other users. I would not recommend it to the smallest companies because you have an entry ticket while using this kind of tool. It's based on usage, but it's mostly beneficial for companies that have big architecture to build, that are looking for a big, complex architecture. It's quite relevant for that. 

If you, as a small company, would like to simplify and rationalize, you may have some packaged products that would not only provide storage or transformation, but a different kind of end-to-end experience that would be better.

Overall, I would rate the solution an eight out of ten. 

Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
PeerSpot user