As a Data Scientist, my main use case for Fabric Data is to manipulate data inside Lakehouses and develop Power BI reports and publish to them in Fabric.

A quick specific example of how I have used Fabric Data recently is that I imported a dataset and used Python to run a notebook against the data to extract latitude and longitude for 300,000 addresses.

I don't have anything else to add about how I use Fabric Data in my day-to-day work; it is a great tool and a good tool to have in your toolbox.

In my opinion, the best features Fabric Data offers include the ability to work inside and spin up SQL databases and Lakehouses and work with Python, all within the same environment without having to go outside and use multiple other tools that are not compatible with the language and file system and data types that I am currently working with.

Fabric Data has positively impacted my organization because the company has a long history of working with data, and previously, there have been multiple pipelines for how to manage data from going from Power Apps into Excel and into SharePoint and then importing back into Power BI. Fabric Data has allowed us to change that and put the entire solution in one package and one environment, and that also makes things much more stable.

This move to one environment has led to measurable improvements, as it prevents a lot of breakage points and removes a lot of the complexity. The consistency between being able to use it inside one environment and not having to rely on other people outside of Fabric Data to do their job allows us to do more. It has also improved the user experience from within Fabric Data. For example, by using Translytical Taskflows, users that use Power BI no longer have to go outside Power BI to update data and have it returned back into their report; they can experience that all from the same environment.

I find the integration between these different tools within Fabric Data has some learning curves because Fabric Data is growing. It can sometimes be challenging to learn new tasks and items to get it to function, but overall, it usually works pretty well, even when things are in preview mode.

Fabric Data can be improved because it tends to be run by Fabric Capacity, which is basically the compute cycles, and it is not very clear on how and what that is going to be used. There should be a lot more transparency on what things actually cost when it comes to Fabric Capacity. In addition, some of the tools offered by Fabric Data don't provide really good guidelines for how to accomplish things inside Fabric Data; they just have all these tools and you have to know which one to go to make it work.

Fabric Data is laid out an umbrella with all the tools underneath it, and I don't find that their use case or how to maneuver or manage inside Fabric Data is intuitive. I wish they had spent more time developing the menus or how to get from one place to the other.

I have been using Fabric Data since 2024.

Fabric Data is stable most of the time, but not always.

The scalability of Fabric Data is great, and there is absolutely no problem with it. The biggest problem is the hidden cost of Fabric Capacity.

I haven't had to rely on customer support, so in this case, I would say it is great.

I did previously use different solutions before Fabric Data. We were using Power BI as a standalone reporting tool, SharePoint, Excel, Power Automate, and Power Apps, all combined to do the same things that we are currently doing in Fabric Data, plus we were using additional databases such as SQL, Mongo, and Snowflake, where Fabric Data now can manage everything.

Before choosing Fabric Data, we evaluated Databricks and decided that because it was not within the Microsoft umbrella, it would not be beneficial to use Databricks as an analytical tool.

I recently ran into Translytical Taskflows, which helps; it is basically SQL write-back, and I am finding the process very helpful in solving other problems.

My advice for others looking into using Fabric Data is to know what your Fabric Capacity usage is going to be. Do a really deep dive analysis of what that cost is going to be. Getting the right Fabric Capacity for your purchase is important, and the big break is at using F64 SKUs.

I am glad Fabric Data is available, and I enjoy working with it. I gave this review a rating of 8.

My main use case for Fabric Data is data integration, ETL, and BI. A specific example of how I use Fabric Data for integration, ETL, and BI is that we integrate several data sources such as SAP, Business Central, or any kind of data source, database, or API to build a Lakehouse. With the information on the Lakehouse, we perform an ETL process. Finally, we create BI solutions with Power BI.

The best features Fabric Data offers for my work include its integrated environment with many solutions inside the same platform. The features I use most often or find most valuable are Lakehouse, pipelines, dataflows, data agents, and reports and semantic models.

Fabric Data has positively impacted my organization as my company is a consultant company and we have implemented these projects for our clients. I have seen positive results and feedback from my clients after implementing Fabric Data. Specific outcomes and examples of how my clients benefited include cost savings and various KPIs, depending on the business.

To improve Fabric Data, I suggest more integration with additional data sources and better integration for data agents.

I have been using Fabric Data for three years.

In my experience, Fabric Data is stable.

Fabric Data's scalability is adequate; it is very scalable.

Customer support for Fabric Data is provided through partners.

Before Fabric Data, I used MicroStrategy. I switched from MicroStrategy to Fabric Data because of the revolution with Power BI.

I have seen a return on investment with time saved.

My experience with pricing, setup cost, and licensing is that it is acceptable.

Before choosing Fabric Data, I did not evaluate other options.

I do not have any advice to give to others looking into using Fabric Data. I have no additional thoughts about Fabric Data. I found this interview satisfactory and nothing should change for the future. I would rate this review an 8.

My main use case for Fabric Data is centralized data analytics and reporting in my organization, where I work on integrating data from multiple sources, transforming it, and building reporting solutions using Power BI. Fabric Data helps me handle data storage, preparation, and analytics on a unified platform, reducing dependency on multiple separate tools, while also improving collaboration between data engineering and reporting teams for scalable and efficient BI solutions.

In my recent reporting project, I had data coming from multiple sources including SQL-based transactional systems and manual business data, and we used Fabric Data to centralize the data into a single analytical environment. The main challenge was efficiently handling large datasets and reducing report refresh time using Fabric Data components such as Dataflows and Lakehouse integration, along with Power BI. We streamlined the transformation process and created a centralized semantic model for reporting, which helped improve report performance, reduced manual effort, and provided faster business insights for stakeholders, enhancing collaboration between data preparation and reporting layers.

Apart from centralized reporting analytics, I also use Fabric Data for improving data accessibility and scalability for business users, especially through its integrations with Power BI as I am a Power BI developer and Business Intelligence Engineer. I also explored pipeline-based data movement and data preparation workflows to reduce manual intervention and improve consistency in reporting. Overall, my focus has mainly been on using Fabric Data to simplify data integration, improve reporting performance, and support scalable BI solutions.

Fabric Data offers many features, but one that stands out to me is the unified platform approach, where data integration, storage, transformation, and reporting are all connected within the same ecosystem. I find the seamless integration with Power BI very valuable for creating a semantic model that enables efficient reporting for business users. Another strong feature is the Lakehouse concept, which helps in managing both structured and semi-structured data effectively for analytics use cases, along with pipeline-based orchestration and scalability for handling growing data volumes and reducing manual effort in data workflows.

The Lakehouse feature specifically helps my team by providing a centralized and scalable data storage layer where both structured and semi-structured data can be managed effectively. Earlier, data was spread across multiple systems and formats, making transformation and reporting complex, but with the Lakehouse approach, it became easier to organize, access, and process data for analytics and reporting use cases. What I value most is the seamless integration with Power BI, which simplifies data connectivity, semantic modeling, and report development without requiring multiple disconnected tools, improving collaboration between teams as data engineers and BI developers work more effectively within the same ecosystem. Scalability and pipeline orchestration are also useful for supporting growing data volumes and more automated workflows.

An additional key feature that I find valuable is the flexibility Fabric Data provides across data engineering, analytics, and reporting. It reduces tool fragmentation and helps teams collaborate more effectively while offering flexibility for scaling analytics solutions as business data grows. Overall, I see it as a strong platform for building modern end-to-end BI and analytics solutions.

Fabric Data is a strong platform overall but still has areas for improvement. One area is performance optimization and monitoring visibility for large-scale workloads. Having more granular monitoring and troubleshooting capabilities would help teams manage workloads more effectively. Another area is the learning curve and usability. Since Fabric Data combines multiple capabilities in one ecosystem, better simplification and guidance for new users could enhance adoption. Deeper integration across certain enterprise scenarios and third-party tools could also continue to improve as the platform matures, with some organizations needing more maturity in advanced governance and cost optimization features for large enterprise environments.

One feedback I have heard from my team is that because Fabric Data is evolving rapidly, some features and integrations are still maturing compared to more established enterprise data platforms. Teams face challenges in understanding the best architectural approach, especially when combining multiple services such as Lakehouse, pipelines, semantic models, and reporting. Another pain point discussed involves cost and capability management visibility for larger workloads, where organizations want more detailed optimization and monitoring controls. Governance and role-based access management can also become complex as the platform scales across larger teams and projects. However, most feedback has been positive, as the platform significantly simplifies end-to-end analytics and improves collaboration between data engineering and BI teams.

I have been using Fabric Data for around four years.

We did see a positive return on investment through reduced manual effort, faster reporting cycles, and improved operational efficiency. For example, before centralizing an analytics workflow, generating consolidated business reports from multiple systems involved significant manual data preparation. After streamlining the process with Fabric Data, reporting effort was reduced significantly, with approximately 40 to 50 percent faster turnaround time for activities. While it may not directly reduce headcount, it helped teams work more effectively by automating and simplifying several analytics and reporting processes.

Regarding the experience with pricing, setup cost, and licensing, it is generally good from a scalability and integration perspective, especially for organizations already using Microsoft tools such as Power BI and Azure. The unified ecosystem helps reduce complexity compared to managing multiple separate analytics tools, although larger workloads and enterprise-scale usage require proper capacity planning and cost monitoring to optimize resource usage effectively. Overall, the experience has been positive and manageable from both setup and usability perspectives.

My advice for others looking into using Fabric Data is to first focus on building a strong data foundation and clearly defining the business use cases before implementing Fabric Data. Since it is a broad unified analytics platform, organizations should plan their architecture, governance, and data workflows properly from the start to maximize benefits. I recommend beginning with a phased approach, starting with reporting and centralized analytics, and gradually expanding to advanced data engineering and large-scale analytics workloads. Investing time in understanding the integration between Lakehouse, pipelines, semantic models, and Power BI is crucial as that integration is one of Fabric Data's greatest strengths. For organizations already using Microsoft technologies and Power BI, Fabric Data can provide a very strong and scalable end-to-end analytics ecosystem.

Overall, I think Fabric Data is a very promising and modern analytics platform that simplifies end-to-end data workflows by bringing data engineering, analytics, and reporting together into a unified ecosystem. Its integration with Power BI, centralized data management approach, and scalability make it especially valuable for organizations looking to modernize their analytics landscape. While still evolving, I see strong long-term potential for enterprise analytics and collaboration use cases, and my experience with the platform has been positive. I would rate this product a 9 out of 10.

My main use case for Fabric Data is to extract, transform, and load the data.

To start a transformer and load the data using Fabric Data, I transfer the data into one big database for data analytics.

Additionally, the normalization of the database is critical and I use this database for data analytics.

The best features Fabric Data offers are its versatility, as you can use data fabric for many uses in one single platform.

This unique platform for all teams helps because you can use it for various needs such as data analytics, data engineering, and database administration.

Fabric Data has positively impacted my organization by accelerating the development of the software.

It has accelerated my software development because it is a platform that allows you to develop software with a GUI.

I have an idea for Fabric Data regarding improvements.

I would note that Fabric Data is a perfect software, which reflects my thoughts on the needed improvements.

I have been working in my current field for 10 years.

Fabric Data is stable based on my experience.

Fabric Data is scalable.

To clarify, I have not tried the changes regarding Fabric Data's scalability.

Microsoft support is the best for Fabric Data.

I would rate the customer support for Fabric Data as a 10.

Before choosing Fabric Data, I did not evaluate other options.

Regarding my experience with pricing, setup cost, and licensing, I have one year of experience.

I am a partner with this vendor beyond being just a customer.

I have indeed seen a return on investment with Fabric Data.

I measured that return on investment through time savings, which reflects increased productivity.

My experience with the pricing for Fabric Data shows that it is a little expensive.

Before choosing Fabric Data, I did not evaluate other options.

The advice I would give to others looking into using Fabric Data is to focus on data analytics. I have provided an overall rating of 9 for this product.

I am leading the entire Fabric Data CI/CD project, where the development has already been completed in Fabric Data. I am here to enable CI/CD and environment segregation in Fabric Data, where I use Fabric Data CI/CD libraries. I also work on a data engineering project where I build pipelines from end to end.

I have used the Fabric Data CI/CD library and MD files to create the pipelines. I have also used Copy Data activities in Azure Data Factory.

Because it is under one ecosystem, our time has been saved. Cost has been saved but not as much as I expected it to be.

Money and time have been saved significantly. The training and cost of training for people has reduced because Fabric Data is quite easy to understand.

The best features are that the entire ecosystem is inside Microsoft and it is under a SaaS platform. I do not have to rely on any other tools or cross-functional tools to deploy or develop. The entire CI/CD, from development to testing to deployment, the entire operation can be done under the same Fabric Data platform.

The all-in-one system has been the most helpful for me.

Earlier we used to rely on different tools and had to purchase different enterprise-level tools. Different billing used to happen and they were not in line or were very inconsistent. Now that the entire thing comes under a single ecosystem, we do not have such issues.

Fabric Data needs more ecosystem support.

It needs a lot of support on the CI/CD part. It is still in development.

It needs more improvement on aspects like CI/CD.

I have been using Fabric Data for four months.

Currently, as Fabric Data is new, Microsoft is constantly developing it. There were a lot of issues in the initial days, but now Microsoft is working and trying to make it better every day.

Fabric Data does not have scalability issues.

Customer support receives a rating of six out of ten because they themselves are trying to figure out what is new and what the issue is.

I did not switch anything. Since the start, I have been in Azure and Azure cloud only.

I was considering choosing Databricks, but we are Microsoft partners, so I did not.

The initial setup was smoother than other tools.

The implementation team can use Fabric Data properly.

My overall review rating for Fabric Data is six out of ten.