Microsoft Power BI Reviews

I use the solution to visualize charts and graphs that provide data insights.

The product is user-friendly.

Power BI shows reports on actual data, not metadata.

I have been using the solution for a few months.

I rate the tool’s stability an eight out of ten.

The tool is scalable. We can create multiple reports. We have two to three customers who use the solution. Within the client organizations, teams can use different solutions. It depends on the client’s needs.

Creating a report takes 10 to 30 minutes, based on our requirements. It is easy if we have simple requirements. If it is complex, building a report can take days. The product is cloud-based.

People use other tools in the market, like Tableau and Qlik Sense. They are good competitors.

I work in data management. I focus on connecting to the source and getting the metadata information from the tool. I'm interested in metadata, not actual data. Integration with other tools is possible. The solution provides APIs.

I will recommend the solution to others, but my recommendation depends on the clients. If a customer uses Microsoft products, they can use Power BI. If someone wants to build good reports and perform data analysis, Power BI is a good choice. Any dashboarding tool is good for data analysis. Overall, I rate the product an eight out of ten.

In my project, I have an integration with Microsoft Power BI: I bring the lock from Azure Monitor to Microsoft Power BI, then create a dashboard from there. In the morning, we have a screenshot of the dashboard, and it can show you if there's a failure or not, based on the locking, so I combine the data which we get from the on-premises system, Azure Monitor, and other tools.

What I find most valuable in Microsoft Power BI is that it gives users detailed error messages. The lock I bring from Azure Monitor into Microsoft Power BI shows us detailed error messages which is helpful, and this is something you can't get from Azure Monitor, unless you do a custom query.

With Microsoft Power BI, I just need to put everything into a table, so people can filter the data, then they can see the error messages which they find useful. In the morning, if we see some failure in our solution, we can go to the "Detail" tab to see detailed error messages.

Microsoft Power BI can be confusing, because it has two languages that you need to learn if you want to use it. This is its area for improvement. First, you have to learn DAX (data analysis expressions), then you also have to learn Power Query M. You need to learn two languages simultaneously. If they can combine and make it just one language, it will be easier for nontechnical users.

We've dealt with Microsoft Power BI for six months.

Microsoft Power BI is very stable, and it's a nine out of ten for me.

I'm rating the scalability of Microsoft Power BI a nine out of ten. Its scalability is really good, because Microsoft has put in a lot of effort. They have a lot of connectors that let us bring in a lot of data, and even if we don't have enough data, we can use HTTP and REST API code to get data, so that's good.

The way Microsoft Power BI is used, particularly its Cleaner tool, should be improved. I just started using the solution and I use the PowerBI Cleaner with all the BI tools, and we need to have a dedicated data warehouse for that. PowerBI Cleaner would just be plugged directly to the data, and that's not good when you use your analytics solution, plugging it directly to the online transaction database.

We should have an OLAP (online analytical processing) software that's dedicated only for that solution, but we don't do that yet. If we have time, we should do that, but the PowerBI Cleaner would just stop at that stage, because it serves it purpose, e.g. it serves us what we need.

We use this solution for all of our self-service analytics. 

We have the analysis services on-prem and Power BI Pro in the cloud. We are using the latest version of Microsoft BI.

It's the analytic engine in terms of the interface on the Power BI environment, as opposed to pivot tables, and it's a mobile solution.

They have a new update every month. It seems to be pretty dynamic in terms of improvement every year.

Right now, their premium pricing is keeping us out of the premium market. The premium price per user just doesn't make sense for us, but we haven't reached the limit of 500 users to justify the premium.

The stability is good.

We could scale up to premium or Azure. We're fine.

I haven't really used it other than going on their documentation and seeing posts. I have never had to call for technical support.

The initial setup was straightforward. I would rate it a 5 out of 5. 

Deployment was completed in-house.

I would rate them 4 out of 5 for their current pricing. There are no additional costs to the standard licensing fees.

I would rate this solution 9 out of 10. 

They're a market leader. They're the best in class, so I would definitely use them over any analytic tool.

We have many use cases, from creating full ETL workloads for supporting some dashboards to only building dashboards by themselves. For example, there is one stage where we had to do some data integration from several sources to assess the quality of the data that we are consuming for our projects. We had to ingest data and convert it using Power BI, which is useful but isn't the best ETL tool, and I understand that that is not its purpose. Finally, we built out a schema model and built reports upon that. It's a full project. 

We also have another project, where we are attempting to do some incremental refresh because we are ingesting a lot of data from lake sources and SQL sources. We are doing direct query and applying some optimization from Synapse.

I am currently using the latest version of Power BI.

The most valuable feature is definitely the visual aspect and the DAX capabilities to virtually do anything.

Something that everyone has suggested and that we are currently implementing and testing is the ability to export tables with the same format. That is something many customers were seeking, and right now it is possible to do that. Focusing on table support is a huge opportunity.

One opportunity for improvement would be on the Power Query side. As a consultant, I know Power Query is not the main strength of Power BI. It is not where Power BI shines, but many customers use Power Query to do full ETL workloads for deliverable cookies.

When you try to process a lot of data from one million records, it breaks. The computer runs out of CPU and memory. It's terrible, but I know it's not its main purpose, so that would be my suggestion.

It's stable, but the desktop is not so stable. I have experienced several crashes. I would say there is a lot of opportunity for improvement on that.

A couple of people are needed for deployment and maintenance. You always need a developer who is proficient on Power Query and maybe some other DevOps guy who sets up the pipeline. So, maybe two people at most. It's very easy.

Scalability on the ETL side is not so good. When you run the workloads on service, you can fail almost anything, but it's not exactly the best for scaling.

On the virtualization side, I would say it's good.

I haven't actually needed much technical support. I know there are forums and people respond, but I haven't really sought that out. There is so much documentation online, there are books online, and there are YouTube channels from guys that provide solutions to issues and to some other stuff. The community is very proficient.

It is very easy. Even non-IT professionals use it and deliver value to the company.

I would rate this solution 8 out of 10. 

My advice is to just jump right into it, download the Power BI desktop and start looking at YouTube channels. There are lots of people who have made wonderful things on YouTube.

The solution is basically used for data. It's on a proprietary piece of equipment on which we collect data. We look at impurities in molten metal, and it's a database and it keeps track of all the batches that we have through the furnace that we have. It tells when it's dirty and stuff like that. It's a large database that we keep track of the history of all the ingots that we run.

The solution serves its purpose. When you have the recurring cost every year on this other project, Qlik Sense didn't fit with it as you'd have to have Qlik Sense plus something else. 

As long as you don't need the data in real-time, it's okay.

The solution is stable.

We have found the product to be scalable. 

We looked at it for these two new projects too, however, we needed more real-time data on this other project and so it wasn't a good solution and we thought Qlik Sense would work better.

If you need data in real-time, it's not an ideal solution.

I've dealt with the solution for about a year or so at this point.

From what I have seen, the solution seems to be very stable. There are no bugs or glitches and it doesn't crash or freeze. It's reliable. 

The scalability of the product has been fine. We can expand it if we want to.

I've never contacted technical support. I cannot speak to how helpful or responsive they are. 

We have more of an industrial type application and we're going to have Tulip interface with Qlik Sense or we're just going to use Domo's platform. Domo is more expensive, a little bit more expensive, however, one of my colleagues here already used Domo and he really liked it, so we're gearing towards Domo. We haven't purchased it yet.

We looked at Qlik Sense. However, when you have the recurring cost every year on this other project, Qlik Sense didn't fit with it because you'd have to have Qlik Sense plus something else.

Our corporate office may have some sort of agreement with Microsoft. We're just an end-user.

Corporate is kind of pushing Microsoft BI, and they have questions about using it for this project, however, we had an IT consultant that said it's not a good solution.

I would rate the solution at an eight out of ten. It's not ideal for every application, however, it works pretty well.

We use this solution for dashboards and reporting.

We work in manufacturing and we track any incidents that we have regarding safety.

The most valuable feature of this solution is real-time report tracking. For example, we have a report for a human body and the human body is populated with injury data. In real-time, we can see where most of the injuries have occurred. 

It is a difficult tool to use and it's hard to figure it out.

It's not user-friendly; more tutorials, training, and better documentation would be helpful.

I have been using Microsoft BI for three months.

We are running the latest version.

I don't have any issues with the stability of Microsoft BI. It's a stable solution.

It's mainly used by developers. We have 10 to 20 developers who are using this solution in our organization.

Technical support could be improved. If you are able to get someone it's great, but if you don't then you are left hanging. 

Previously, they were using BusinessObjects.

With the EA agreement, we get access to everything from Microsoft. It just made sense to switch.

The initial setup was completed through our internal Microsoft team.

Licensing costs are on an annual basis. There are no fees in addition to the licensing.

For anyone who is interested in using this solution, they should hire a dedicated Microsoft team to implement it, and get a lot of training.

I don't know it well but I would rate it a five out of ten.

There are multiple use cases. I can't count them even on my fingers. There are around 20 to 30 solutions we have been deploying. We use it across finance, procurement, HR, engineering, and whatnot. Each of the domains we have touched. Data visualization is the main need of any organization. With Microsoft being in our ecosystem, Power BI works perfectly well for us.

The solution overall works quite well, especially if you have a Microsoft-heavy ecosystem.

The ease of creating the dashboard is quite good. 

The analytics are very strong when we couple it with Azure. It offers very good Big Data Analytics that work perfectly well. 

Scalability is not at all a problem. 

You can perform the role-based access perfectly. It gives you everything you need with a single sign-on authentication due to the fact that we are in the Microsoft environment.

You don't have to worry about security. That is very robust.

What matters most is the turnaround time to create a solution, which is quite fast. This is due to the fact that it's quite intuitive in nature. Even those new to the solution can create solutions very quickly. There isn't a high learning curve.

The initial setup was not difficult.

The pricing has been pretty good. 

Technical support is quite responsive.

Overall, the solution is quite intuitive.

If I compare it to Tableau, I'd say the visualizations can be better. We should have multiple options. By that I mean, while there are multiple options for the visualization, the look and feel of the dashboard when you compare to Tableau is on the lower side. Tableau has a much better visualization.

We've been using the solution for three and a half years at this point. We've definitely used it over the last 12 months.

The product is quite stable. It works well in the Microsoft environment. It doesn't crash or freeze. there are no bugs or glitches. It's reliable.

The solution scales very well. If a company needs to expand its offering, it can do so easily. It's one of the selling points of the solution.

We have about 60 to 70 people on the solution currently.

We already are deployed it at a global level. It's just not India-based. We use it across our organization, and it is getting used a lot.

We've dealt directly with technical support. They have been responsive. We have called them multiple times and the response was good. We are quite satisfied with the level of service.

The initial setup was okay. We didn't have any problems. I wouldn't call it complex. I'd describe it more as straightforward. It took us around three or four months to set up and deploy the solution.

We have a yearly contract. We signed up for three years and that rolls over annually.

We have a bundle, an enterprise-level package. Its pricing is good for us.

We did evaluate Tableau for a moment, however, due to the existing license of Microsoft, the default choice was Power BI.

We are using the latest version of the solution. I can't recall the exact version number.

It's one of the leaders in the top data visualization and analytics toolsets. I'd advise other companies to go for it. It's stable, scalable, and a powerful product and it comes very handy when you want to create visualizations very fast. It's a go-to product if you want to go for data visualization and reporting.

Overall, I would rate the solution at a nine out of ten.

We are using it for reporting, analytics, and data science. We have its latest version.

Microsoft's CRM platform has very limited reporting capabilities. Power BI was able to meet the business requirements for reporting and more in-depth analytics. It is a part of the Microsoft Ecosystem, and there is a straightforward connection from Power BI to CRM. 

It is a pretty straightforward and flexible solution for data integration and modeling. It is a low-code solution. When you are doing data integration, you can use the GUI, which is very simple and straightforward. You can also do very intricate custom queries and model it at different levels. It is very easy to use and scalable. 

It is kept very current, and there is an update literally every month. However, the interface changes quite randomly with no documentation, which is difficult at the domain and architectural level where you're planning things and engaging the business. Things change frequently, and you wonder where has the button for the new report gone. They should provide better documentation on interface changes.

It should be better optimized. It is supposed to be a data integration tool, but it is doing relatively simple queries. It has its limitations. For example, you can only pull a number of columns. So, there is room for optimization on its ability to integrate multiple data sources. 

The desktop tool is very memory-intensive, and again, this is not documented clearly. It requires a heavy CPU and memory use, and it causes your operating systems to become unstable.

I would like to see the ability to create datasets within Power BI. Microsoft is promoting Azure as a cloud solution, but it is dependent upon a desktop component, which seems a little bit deceptive. Data set is the basic element that you report from, but it has to be created on the desktop and then published to the cloud. So, you're in the cloud, and you create a data structure or the data flow, but you can't report from that. You have to leave the cloud, go to your desktop, create the data set on your desktop, and publish it to the cloud. You go back to the cloud and create your report by using that published data set, which is very non-intuitive. If you go to the Microsoft Power BI community, this is a common complaint across the entire community.

I have been using this solution for about 18 months.

It is pretty stable. I haven't determined any major issues.

It is very scalable. It fits perfectly with the larger Azure Data Lake reference architecture. Power BI platform is a fundamental piece, and it becomes scalable to use with other components within that reference architecture.

We're in the process of laying out a three-phase approach. Over the next year, its usage will increase from 50% to 75%. In terms of the number of users, we have around 150 users who are data scientists and data analysts. We have around 5,500 desktop users, and it is a part of 365, which is on every desktop. 

There is a lot of online support. We also have Microsoft consultants on contract, and the support comes through them. Their support is very good.

We also have IBM Cognos. We haven't switched. They're being used in tandem. There are different sets of requirements for two different solutions. 

I wasn't part of the deployment, but my understanding is that it was pretty straightforward.

We used a Microsoft consultant for implementation. Our experience was good. We don't have any maintenance crew.

I would rate Microsoft BI a nine out of ten.