Microsoft Power BI Reviews

The main use case is for dashboarding on Excel spreadsheets until data lake and similar sources are ready for us to start integrating and dashboarding that information. We are a government motor transport entity and for each vehicle, there's a lifecycle. At every step of that life cycle, we need to know how many of a particular type of vehicle we have in our fleet and its status. I'm an IT service and strategy consultant and we are customers of Microsoft BI.

BI is very easy to use including the desktop version. The visualization is valuable, it's easy to select visualizations and show your data in different views. It opens up a lot of possibilities that weren't previously available and it's versatile. We're integrating with other solutions and if you look at Power BI pulling information from the data warehouse, it's integrated to an Oracle warehouse and works well.

The formatting template could be improved. In order for me to easily do visualizations, I have to format my Excel spreadsheet in a very specific template. I can't take a spreadsheet from my financial director and quickly put it in Power BI and then pivot into visualizations. I have to first check the formatting, that it's in the proper columns, and headings are logical. It needs all of that database thinking before you can actually get valuable information out of it. 

I'd like to see more templates and better tooling so that when one opens a spreadsheet it's possible to manipulate data from Power BI without having to format the spreadsheet. If you were able to pull the information out of the spreadsheet via more detailed tooling, that would be brilliant.

We've been using this solution for about three months. 

Stability has been good so far. 

The scalability is good. 

We haven't required technical support.

The initial setup was straightforward and didn't take too long. We had a team, the Azure FastTrack team, that assisted us and they were superb.

We're using a subscription-based license and the government has a transversal agreement with Microsoft. We use the solution according to that contract, it's an EA license. When it comes to premium licenses, I think they all have room for improvement.

I would recommend this solution to everyone, whether small, medium, or enterprise-size companies. Smaller companies should use the free version because it offers quite a lot and is valuable. I would recommend it for any size environment and specifically because it's not boxed in and you can visualize data that's on Microsoft products. 

I rate the solution eight out of 10. 

I used it to build a simple dashboard. What I did was very simple. I used it to load different datasets. I defined relationships between them and played around with the data by using visuals.

I must have downloaded the version that was really available at that time.

I had to build a simple dashboard in which I had to combine two or three different datasets. They were large enough, so it wasn't possible to work on them easily in Excel. In Power BI, I used the relationship feature, and I was able to store the data in such a way that it does not occupy a lot of space. I could then send the file over email.

Its visualization capabilities are pretty good. It is very easy to use. You can easily make your dashboard.

There is a lot of self-help content available from a lot of different platforms, such as YouTube. So, whenever I faced an issue, it was not difficult. I could always find a solution to the issue I was facing.

Defining a relationship was very confusing. There were circular directions for which I had to do a lot of adjustments in the data. They can do something to make it easier.

I worked on it this summer. I just used it for a month or two.

Defining Relationships can be confusing when you are working with a complex data model. It can result in circular relationship referencing and the interface does not help solve it, or even understand it, in any way. It takes time to figure out a different way to structure the data model and Power BI offers no guidance on that. Online help is limited.

There is a lot of content available online. When I started out, the way I was defining the relationship between the data and the way my model was structured was not very efficient. I spent a lot of time in making it more efficient. So, I would advise others to do enough research. I was learning on the go. If you spend about six or seven hours learning it, it would be much better. Even though it is marketed as something that is easily usable and anyone can come and start using it, there is a bit of a learning curve.

I was very easily able to load the data and conduct an as-is analysis of what is happening, but if I want to do a deeper analysis of the data and break down a variable into different components, I don't know if it is possible in Power BI. I tried to do it a little bit, but it was not easy. So, it is good when you have the data, and you just want to present it and look at it in different ways, but if you want to analyze the data and break down the numbers and play around with the data, I don't know if it is possible in Power BI.

I would rate Power BI a seven out of 10.

I use Microsoft BI for the reports and our displaying the data in different ways. As a project manager, I need to follow the budget and receive confirmation about our projects. We have an SAP database and we follow and check all the budget data of the project including data usage.

What I have found valuable about Microsoft BI is its performance and ease of use. The interface is very simple and it is accessible to everyone. If someone is new to this type of solution it is straightforward to understand.

The solution could improve by having more options to manipulate the views of the data on the dashboards. I sometimes need to make them myself but there should be more customizable with drag-and-drop elements and filters on that data differently than it was designed. There are filters in the design stage but there are times you need something else other than how it was designed. For example, if you did not have some of the information at the time of the design. Having the ability to design, or request the data from the database as an end-user is very important. It would be beneficial to have more autonomy on the design of the requested data. You are not able to change the fields or the request data because it was done in the backend and you are not able to see how that request happened. Sometimes you need to make your own requests or have different requests regarding the data. We do not have access because we are not administrators.

In the future, Microsoft BI can be better by increasing user-friendliness.

I have been using this solution for approximately three years.

The solution is stable.

I have found it to be scalable.

We have approximately 1,000 people using the solution in my organization.

I have previously used QlikView and Qlik Sense.

I would recommend this solution to others.

I rate Microsoft BI a seven out of ten.

We use Microsoft BI primarily for analyzing data to construct indicators and dashboards. We use the information to better understand our business to make effective decisions about our business for the future, such as keeping competitive with other companies.

The most useful features are the ability to connect different databases to Microsoft BI and explore them. Once the database information has been extracted, you have the ability to construct indicators and dashboards from the information.

Microsoft BI is a complete tool, it has all the functions needed for its purpose.

The solution could improve by simplifying the user interface and adding integration or compatibility with APA.

I have been using Microsoft BI for many years.

The solution is stable.

The solution is scalable. We are able to see the users and the capability from the cloud platform.

Microsoft provides good technical support.

The installation is easy. However, there are many options and areas to configure that can be difficult.

I would recommend those wanting to use this solution to take some courses to at least learn the minimal knowledge to analyze and construct indicators. This is a very powerful tool and if you understand it you can get the most out of it.

I rate Microsoft BI a nine out of ten.

I've been a consultant, so I've built some reports for some clients. I use and prefer its desktop version. 

It is a little easier at buildings charts and graphs than Tableau.

At the enterprise level, it is a little expensive. To get the full capacity of integrations, you need to go premium.

It has limited performance capabilities in terms of connecting to large transactional databases, but it is fine for simple and quick queries from Excel spreadsheets or one table. The premium level is going to be more applicable for the higher transaction-level databases. 

I've been in the Business Intelligence Industry for about seven years. I use this product off and on.

It is complex to scale. There are just too many things you have to put in place. You got to have the gateways, and you got to have the premium service. There are a lot of components that get involved. It is not very straightforward. 

We sell our own BI tool. So, we have hundreds of clients. They are mid-sized organizations. We're building out our Power BI stack because people do like it, but right now, we have most of our stuff in Tableau.

I also use Tableau. They're very comparable products. I worked for different companies that built their own proprietary stuff, and mainly for visualization, Tableau and Power BI were the connectors to go to. So, there wasn't a switch.

I really like Tableau's web version over Power BI's web version. It is just easier to drag and drop things and blend data on the backend. It has a little simpler process in that regard. I don't like the charting in Tableau. Its charting is a little more complex than Power BI's charting.

Calculations are a little harder in Tableau. They can be a little more complex in Tableau as compared to Power BI. Tableau is a little more detailed in terms of creating calculations. You can't just add two columns together. Tableau should have the ability to add or subtract columns. They should make it like a wizard.

The simple stuff is easy. When you want to get into the calculations and building DAX-type formulas, I don't think DAX is that great. I find Tableau's coding a little easier.

Its pricing is reasonable for the desktop stuff, but for enterprise-level, it is a little expensive. 

I would advise others to just do their research and figure out what they want to do with it so that they know if it is going to be hard or easy.

I would rate Microsoft BI an eight out of 10.

There were two systems that the client was looking at creating some BI visualizations for. There was the system called ICE, which is a system that takes in automated calls, for service calls. They go into voicemail, however, if there's not an agent to take the call, it'll track statistics like how long a client was on hold, if an agent actually took the call, if the person hung up, et cetera. There are all of these different statuses and it would take all of those statistics. The product was used primarily to take that data in that case.

The other system was an ITSM system, which was the ticketing system. It would

it was my first time using Power BI, I can say that it was fairly easy to learn, especially if you already know BI-type tools. But the one thing that I noticed specifically was the graphical features, and some of the analytical features, I think they were stronger on the Tableau side. But the data preparation features, I much preferred the Power BI with the Power Query type features, at least for the datasets that we were working with. They were helpful in preparing the data.

 combine those two data sets and reduce a merged analytical set of reports to just show when the call volumes were and what the performance rate was and the nature of the calls and things like that.

As it was my first time using Power BI, I can say that it was fairly easy to learn, especially if you already know BI-type tools. 

The data preparation features were great. I much preferred the Power BI with the Power Query type features - at least for the datasets that we were working with. They were helpful in preparing the data.

The one thing that I noticed specifically was the graphical features, and some of the analytical features. They were stronger on the Tableau side.

There are two areas where the solution can be enhanced. One is natural language, where you can have third parties, however, it would be nice to have it built-in within Power BI, where a graph could be automatically explained in whatever language so that somebody can just kind of read through and have the graphic as an extra for exploring. That's something that I was looking at.

The other is the explained data, which is more of a lineage-type feature. My understanding is Tableau has that feature and Power BI doesn't. I was looking at a graph of comparisons and I noticed Tableau had this explained data feature, which gives, some lineage where data has come from, and Power BI doesn't have that. Or, if it does, it's not as well developed as Tableau.

I used the solution a few months ago. I'm semi-retired, however, I did have a two-month contract and did some work with it. On the project, I did work a lot with Tableau, however, I also used Power BI, and would like to continue to use it more. 

It was a short project on the Power BI side. I didn't really identify any glitches. Certainly, over time things might've come out, however, I enjoy doing experimenting and playing around with things. The one definite thing that I noticed, as I do art with Tableau, is some really neat art stuff, so I tried to replicate that with Power BI and the quality just wasn't there.

With ITSM, there's a lot of data that they collect on that side. That could be an issue, scalability. It wasn't moved to production yet. I basically produced a report as there were some issues with the ICE data, the voicemail system, and data collection. They had some issues that they had to solve. However, they were collecting data on a daily basis. You get thousands and thousands of calls on a daily basis. It depends on how they want to store that data historically. There may be some performance issues and scalability issues, however, for me, I can't really address that, as I didn't see that side. There's always a potential for trouble.

It was a really short project for me. I was really there just to analyze those two data sources and produce a report for them, with some examples, using Power BI. I was able to do that without getting tech support involved.

I've used other solutions, such as Tableau and Power Query. Tableau from a graphical point of view is much better than Power BI, however, from a data manipulation standpoint and things like that, I prefer Power BI and Power Query to prep the data.

Tableau got bought out by Salesforce, which is a cloud-based company, so they're all going to push everything to the cloud. I'm sure they'll incorporate all these new features.

I downloaded the solution from their website. 

The server side was already set up, therefore, I don't know much about the initial setup process. As a contractor, I came in just on the development side, which was just downloading the Power BI tool as a client. It was fairly easy. That's the nice thing is it's easy to set up. It is similar to Tableau, in that Tableau is fairly easy to set up. It is all built towards this whole idea of self-service.

I'm just a customer.

As I downloaded the solution right off the website, I assume it was the latest version. I don't know the version number off-hand. 

I would do the development on-pre

There were two systems that they were looking at creating some BI visualizations for. So there was the system called ICE, which is a system that takes in automated calls, for service calls. And so goes into voicemail, but if there's not an agent to take the call, it'll track statistics like how long you were on hold, if an agent actually took your call, if you hung up. All of these different statuses would take all of those statistics. And so it was to take that data.

And the other system was the ITSM system, which is the ticketing system. And kind of combine those two data sets and reduce a merged analytical set of reports to just show when were the call volumes were, and what was the performance rate, and the nature of the calls and things like that.

It's easy to set up, however, regarding scalability and high-end analytical features, Tableau is still better on that. It's always important to keep up, as technology's changing all the time. They're always adding new features. There are no negatives in exploring these tools. In the end, you just want some visualizations that help you make decisions. Both Tableau and Power BI tools are great for that. However, if you want advanced stuff, then it's just about experimenting and seeing what will help you solve your problems.

I'd rate the solution at an eight out of ten.

We use Microsoft BI typically to clean up data in Excel, as well as to create reports for my supervisor that will be analyzed and then used to draw conclusions.

It provides the common ground for data to be cleaned. We use this for everyone to work on cleaning up data in order to use it for visualizations, which has been helpful.

The transforming data before you start with the visualization comes in pretty handy.

It is quite easy to use and it helps me to achieve the projects that I've been assigned.

I have never had the inability to perform the tasks I've been assigned with the software. 

It's very useful because you can create helpful reports, which assist you to analyze data in a very organized way.

I feel the modeling page should be simplified. The links between different parts of your data, on the models' page, are a bit confusing. It was difficult for me to learn. 

I have been using Microsoft BI for three months.

We are using an older version specific to the organization.

Microsoft BI is a stable product.

Microsoft BI is quite scalable, especially with the number of coding languages that are available to use.

We have approximately 23 data scientists in our organization who are using this solution. We use it extensively.

We are mostly using Microsoft BI but we are trying to bring in Tableau and maximize the potential of both.

I have not contacted technical support.

I also have experience with Tableau.

When I arrived, this solution was already set up.

For others who want to start using Microsoft BI, I would say go through some tutorials on your own first and then try and practice with practice data sets that are available online. Also, feel free to play around with the different tools, and the different visualizations, because you can use them differently for different things.

I would rate Microsoft BI a nine out of ten.

I am using this solution to monitor the dashboards that someone else has created.

The solution is easy to use and flexible.

The solution could improve the mobile application design. It is difficult to use compared to the desktop version. Additionally, we have experienced a problem when attempting to update the desktop application. When we click to update we are unable to open the file to update.

I have been using this solution for approximately two years.

I have found the solution to be stable.

We have approximately 50 people using this solution in my organization.

I have previously used Microsoft Excel.

The installation was simple and it takes approximately five minutes.

I did the implementation of the solution.

We have a professional license for Microsoft BI and the price is fair. 

I would recommend this solution to others.

I rate Microsoft BI a seven out of ten.

We primarily use the solution for analysis. I have a DB setup that I have. I use that DB for analyzing data, providing business solutions or business insights to the customers. Most of the time, I use Power BI for that or sometimes even Tableau.

The solution isn't hard to use. It's very user-friendly. 

The product is stable. 

The product is easy to install.

I haven't used the advanced version and therefore haven't accessed all of the features.

The solution isn't very scalable. My data is restricted to my DB and I'm not sure how this would handle an extremely large dataset.

I've been using the solution for two years. 

The stability of the product is good. It doesn't crash or freeze. there are no bugs or glitches. It's reliable. 

I wouldn't describe the solution as scalable. 

While it is available as an option to most people in our organization, I'm not sure how many people are actually actively using it. I know that I use it myself quite often. 

I've never reached out to technical support for assistance. I cannot speak to how helpful or responsive they are. 

I also use Tableau. I've used Tableau for about seven months. 

There are other programming languages like Python and R, where they use analytics for graphical representation, or they can use Power BI and Tableau in our company. There are many options.

The installation is not complex or difficult. It's straightforward. 

We have Office 365, which holds Power BI, and therefore I was able to have it easily installed.

I can't recall how long the deployment actually took. 

I personally do not pay for a license. It may be arranged through our company. I have no insights into that aspect of the solution, however. 

I'm a customer and an end-user.

The solution, being on the cloud, is automatically updated, and therefore, you are always on the latest version if you are using it. 

I'd rate the solution at a seven out of ten.

I'd recommend the product to those who want a basic tool that can help them study analytics.

I have used Microsoft BI for sales analysis. I've also used it to analyze people. Pretty much across the board, whether it's the number of people, number of dresses, number of hamburgers, number of widgets and then creating the dashboards and the metrics and so forth.

The best feature for me is Power Query. I know that probably sounds strange, but you can't do too much with visuals and reports if the backend stuff is horribly dirty and just bad. But for me, that is absolutely fantastic. I can load the data and do the transformation and be able to load it in a useful way. There are tons of connections, which is absolutely fantastic as well. It's been fairly easy, and it's intuitive.

It would be better if they had some video tutorials. Most people from an Excel background may struggle with measures in Microsoft BI.

I have used Microsoft BI over the last 12 months.

I haven't really had any issues, but I haven't given it the full whammy or the full monty. It's been stable for my use.

The initial setup was easy for me.

I would tell potential users that there are many other tools out there, but I think it's a steep learning curve. For example, Alteryx and Domo, and Trifacta can be difficult to learn unless you have a SQL background. But if you're a Microsoft person, the transition is fairly easy for Microsoft BI. It's intuitive, and I would recommend it from that perspective. 

On a scale from one to ten, I would give Microsoft BI an eight.