Microsoft Power BI Reviews

We use Power BI for a variety of applications, including retail analytics, sales, and process digitization. Except for time series data, we use it for everything. 

We have both deployment options open, so we have the requirements for both on-prem as well as on the cloud. 

One of the most valuable features of Power BI is the ease of use. It is comfortable and there is not a steep learning curve for this solution. If you have some idea of the data and basic visualization ideas, you can use this solution comfortably. 

Power BI's drillthrough feature could be improved. I didn't like drillthrough and those options much, but I did like it in MicroStrategy. 

As for additional features, I think Power BI could have better interactive features for the end user and scalable drillthrough options. 

I have one year of experience with Microsoft BI. 

Power BI is stable. I have not used it extensively, but from what I understand from my colleagues, it's stable. 

Power BI is scalable. In my organization, there are probably 400 or 500 companies using this solution. We are probably going to increase our usage. 

I have no idea whether the installation process was straightforward or not, on the admin side. As for the technical team required for deployment and maintenance, I would say you need maybe one or two admins. The development is based on use cases, but on average, I would say you need some 10 to 15 BI developers. 

We pay for licensing for Power BI. 

We are also using MicroStrategy. I did not like the drillthrough feature in Power BI, but I liked it in MicroStrategy. The way visualization works, I found that the interactiveness of MicroStrategy was better than Power BI. Similarly to Power BI, you can comfortably use MicroStrategy if you have some idea of the data and basic visualization ideas. 

I rate Power BI an eight out of ten. 

I would recommend Power BI to those considering using it, but would also recommend that they explore it themselves and understand their requirements. Their requirements will be different, so it's all use case based. 

We are using Microsoft BI to generate point of sale reports.

The solution overall is very useful. The reports that are generated and the reporting functionality management are beneficial.

We have used other solutions and the reporting functionality should be user-friendly and have a drag and drop feature should be available, but Microsoft BI doesn't have these features. When you are creating reports and you can't change as a user. Every time you need one developer or one technical person to make the changes.

I have been using Microsoft BI for approximately six years.

Microsoft BI is highly stable.

The performance depends on the requirement. You have to complete your requirement which is a priority. After that, you understand your requirement and the performance could be better. The performance is the second.

I have found Microsoft BI to be scalable.

The installation difficulty depends on the integration, once integrated properly you can receive results. Microsoft BI can be very helpful to your business.

The implementation took us 15 to 20 days.

We use two Microsoft consultants to do the implementation of the solution.

I have evaluated other solutions.

I rate Microsoft BI a five out of ten.

If I compare Microsoft BI with other solutions, other solutions are much better, but because we have already invested in Microsoft BI. We are using this and maybe in one or two years, we will use something else. We will finalize the testing of other solutions and implement one of them.

We use that solution to provide all the KPIs for the software development to manage the business, et cetera.

The solution is very helpful for managing the business. 

The initial setup is easy.

We have found the scalability to be quite good.

Stability is excellent overall.

Technical support is good.

For managing the business, it's okay, however, as a product management tool, it's lacking. I would like to use BI to provide services for the customers eventually. Microsoft's solution is not good for improving the product for the customers. It's just good for managing the business, and not supporting the customers.

The solution doesn't integrate well with third-party tools.

I'd like them to add to the knowledge base, or at least to offer more documentation about how to use the solution.

It would be helpful if more AI was integrated into the solution. 

I['ve used the solution since 2013.

I find the product to be quite stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The scalability of the product is quite good. If a company needs to expand it, it can.

We get technical support from a third party, however, they offer very good support and we have been quite happy with their level of service. They always have enough staff. 

The implementation process is straightforward. It's not overly complex or difficult.

Deployment took less than a month.

I'm also aware of Power BI, which has better integration with third-party tools.

We do not sell Microsoft products. We just use them.

I'm not sure which version of the solution we're using.

We use both cloud and on-premises deployments. 

I'd rate the solution at an eight out of ten. I'd recommend the solution to others as the management portion of the solution is very easy.

We use it for taking data and turning it into intelligence.

I have been using the most recent version of it. It is deployed in a government cloud.

It saved time.

Its ease of use is most valuable.

The biggest thing with Microsoft right now is better support. There should be more timely support. We can do 90% of it ourselves by the same token. When we're into the 10%, we do not get timely support via Microsoft's support team.

Its speed can also be improved. They should come up with a fix for the speed issue and give us some good parameters as to what would help with the speed. They should give us a good white paper that has a compatibility list, similar to what they provide with operating systems, and that describes what you should have before you use Microsoft BI.

There should also be a better way to possibly do things like geolocation, and where they do it, they should do it better. If you have a satellite, offices, and that sort of thing, it would be nice to see it in Tableau and different formats.

I have been using this solution since it came out. It was probably 2010. I'm a Microsoft engineer, so I'm on a lot of beta test teams. So, I would see these items a bit earlier than anybody else.

It is overall in mid-range. Sometimes, it works very well, and sometimes, it doesn't. If it is not working very well sometimes, that means it is not a hundred percent stable.

Its scalability is good. I've used it in very large major banks down to smaller entities, and it seems to not care about the scale.

Currently, we probably have 50 users. Its usage is moderate. We will increase its usage if they come up with a fix for the issues such as the speed.

There should be more timely support. I would rate them a two out of 10 because of the lack of availability. Sometimes, we can't fix what we don't know how to fix, and it causes us a lot of time and waiting and that sort of thing. We have to have a US citizen, and I'm sure that they're just not scaled up to that.

Negative

I have used other solutions but not in this cooperation.

Its initial setup is somewhere in the middle. Each deployment seems to be a little different. You have auto-updates all the time on PCs. When you image a PC, it doesn't always match. So, each deployment is different, and I'm not sure they can change that because most of the updates are for security, but it is very important to be sure that you test the environment first before you put it into production. I know a lot of people who just put it into production because of the ease of use, but sometimes, that can be problematic. In terms of maintenance, it is not terrible.

It was done in-house with the help of a Microsoft partner. Our experience with them was horrible. We ended up fixing it all ourselves. If five was the top, they were a zero.

I would advise others to just do their homework. You should check it out first, do the trial, get it into your test environment, and then make your decisions. Don't rush to production. Everybody is a bit different. If you have monster databases out there, the performance might be a little different.

I would rate it a six out of 10. If their support were better, it would get a higher rating. 

We were using Microsoft BI but it could not do what we wanted it to do. Then we moved to an open-source platform, which was Apache Tika, Kafka, and third solution. We ended up moving back to Power BI only to display the information because displaying information with Power BI is better than open-source software. We are not using all aspects of the solution at the moment.

In the process of using data there is the Extract, Transform and Load (ETL). For extracting we are using another software, for transforming we are using our own coding in C#, and then we use Microsoft BI for loading the information. Microsoft BI displays information very well.

The solution could improve the extraction and transformation of data. For example, you transform the data and then send it to Microsoft BI without having to use your own API. We are only providing the API to Power BI, and then Power BI is doing the job.

In an upcoming release, Microsoft BI should increase the functionality of the solution.

I have been using Microsoft BI for approximately six years.

We were satisfied with the stability of Microsoft BI.

We have 30 users using the solution in my organization.

We are in contact with the support of Microsoft but I have not been in contact directly.

I have used other solutions, such as Apache Tika and Kafka.

The initial setup was straightforward.

The solution only needs one person to do the maintenance.

There are a few options available for purchasing a license. Typically the number of users you have will determine the price of the license. The more users you have the more you will pay.

The solution has had a lot of changes over the years and it is very good. However, there is more work to be done on extract and transform functions for it to be done properly.

I rate Microsoft BI an eight out of ten.

I would describe myself as more of a casual user, only because I have so many other things that I have to get done. I wish I could be more of a user, but it's hard. Right now, I have two different main use cases. I use it for teaching. At another institution, I use it for demonstrating how easy it is to build dashboards. It was really to show to all my users the benefit of business analytics. I use it to demonstrate how easy it is to generate your own analytics versus having a department run reports for you then putting it in Excel and making graphs. 

I like the fact that Power BI lets me use Excel data. At least 90% of my state data is in Excel spreadsheets. Having the ability to just attach a spreadsheet as a data source is very, very important. It's also good for training and teaching. Sometimes you don't always have access to a live production database, so having a spreadsheet with sample data is always nice.

The Microsoft BI interface should be simpler and more user-friendly. I find it very difficult to move between their data sources and their analytics section. It's probably designed by data analysts that typically get the data from somewhere else. So, one person logs into Power BI, moves the data around and puts it in the proper form then somebody else goes in from the dashboard. What I'm finding more and more is that the person playing with the data is also going to be the person building the dashboard, so the interface needs to be more seamless and dumbed down for the average user. 

Tableau is much better at that, which is probably why it's more expensive. The days where one person works on the data and someone else does the analytics are coming to an end. In the past, larger organizations usually had a dedicated analytics team and a dedicated data team. Now we buy data as a service, so we got rid of our data team and we don't have analysts per se. Instead, we have smart users. So I think Microsoft BI needs to move on to the next iteration of truly user-friendly solutions.

I've been using Microsoft BI for about three years.

Microsoft BI has never crashed on me.

I honestly can't comment on how scalable Microsoft BI is because I've never taken it beyond training or simple use. But I would imagine, if it's on Azure, that it's scalable. I haven't had the pleasure of scaling it, so I don't know, but it doesn't strike me as a solution that would have problems with scalability.

I have not had to contact technical support, but I've actually downloaded and taken three Power BI courses for free and they're very good.

I was using Tableau but the licensing cost went up when Salesforce required them to raise the price. But if the price hadn't changed, I would've absolutely stuck with Tableau because I like it. I do not know about the cost of the licenses. We buy it from the state and when it went up, our CIO at the time said no more Tableau licenses. I had to scramble to find a replacement, and fortunately, I discovered that Power BI is included in Microsoft 365. However, I prefer Tableau's interface. Microsoft BI's user interface is convoluted in terms of how you attach a data source. You have a separate screen for defining your data and then you have to jump to a different screen to model the results. In other words, there are two separate interfaces for data and analytics. In Tableau, it's more seamless. 

Setup is very easy. You click on the icon, download the MSI, and it loads itself. It takes about a couple of hours to deploy overall.

I'd rate Microsoft BI as an eight out of 10. The biggest drawback is the user interface. From what I'm seeing, Windows 11 is going to have a more user-friendly interface. Even Microsoft Edge is adopting a more user-friendly interface. I'm hoping that Power BI follows this trend as well. 

My advice for anyone who is thinking about adopting Microsoft BI is to understand what you're trying to do with it. If you're trying to do analytics with it, then it depends on the kind of analytics. If you're want to do statistical analytics, it's not the tool for you. It's a tool that's better suited for visual analytics than it is for straight-up analytics. If you're dealing with patterns and data, it's great. If you're working with numbers and data, it's not so good. You're better off with a statistical package.

I'm a project manager and we are customers of Microsoft.

I like the toggling feature, the ability to switch from one page to another. 

I have a couple of dashboards that are weekly and monthly. I was able to download the dashboard, but I cannot paste any images into PowerPoint. There are also visuals based on the brand that should automatically pop up in the graph and which should be a toggling option. And I'm having performance issues if I want to add two or three tables at a time, which I could easily do in Tableau. Copy-pasting data to PowerPoint for presentation to the executive level should be easy but we're only able to copy the visual, not the underlying data. 

I've been using this solution for the past eight months. 

The solution is scalable but we haven't yet migrated everyone to Power BI. Our users are not finding Power BI as good as Pique, which perhaps they're just more used to. They're trying but some of the features available in Pique are not there so they are not comprehensively using it. It's being used mainly for internal analysis for now. 

We initially used Tableau because our data was an internal data source, and now all of our data is migrated to tool environments, that the Power BI is more comfortable with. BI is also a free product which is another reason the company recommends it.

The initial setup was straightforward, we have a Power BI admin team who take care of all that. 

Because of performance issues and because we're unable to do all the aggregation, I rate this solution six out of 10. 

We are using it for financial analytics and reporting. We are using it to keep a track of projects and being able to degrade the projects. We are also using it for contract closeout.

My technical guy has been using the first version of it since it came out, but we are getting ready to upgrade to the newer version. It comes along in a bundle with the 365 Enterprise version.

It is on the cloud. We're probably going to run a hybrid because we want to be able to move around. If anything happens or if needed, we can move from platform to platform.

We can see things from a bird's eye view. We can do predictive analytics. I can tell who's capable, who's doing what, when and how much money they're spending, and how fast they're burning. So, it gives us a bird's eye view over the financials and the money. It basically gives us the ability to collaborate and keep track of everything that's going on in an organization. We were able to bring all the collaboration and tasks right into Power BI.

It is easy to use. It has got a desktop where people can develop their own dashboards. Basically, we have figured out how to connect finance contracts and all programs for the government agency. So, they can see everything in a dashboard. So, it is very easy to use from a technical standpoint of view. We publish a report every morning for the government, and we got all the data into one place. The data can be refreshed. We are using the API to connect to various systems, such as the financial system, contract writing system, and workflow. We are able to bring things from NIPA, which is their budget and where they keep all their money. There are a lot of features, but the most important thing is it is very easy to use. It is not like Tableau. With Tableau, you've almost got to be a rocket scientist.

On the user side, it is quite simple. If you know how to run a pivot table, and then you can do almost anything. All the data is right there in the database. So, if you understand pivot tables and know how they are run, and you know the reports that you are looking for, then everything becomes very easy to run in your organization.

Its desktop tool is a little bit memory CPU intensive, and it can be improved, but the machines nowadays come with a lot of memory. For the desktop users who are using it on the desktop, we recommend that they do an upgrade. It is a minor issue. We can fix it on the desktop.

We've been using Microsoft BI for about four and a half years.

Its stability is pretty good. It is pretty stable.

I would rate it an eight out of 10 in terms of scalability. Currently, we are running a pilot. We're doing a pilot for army headquarters. They dictate what happens and what they use. Currently, there are 10 users, but I'm looking to go up to at least a hundred. 

We got an architect and an assistant administrator. We got a staff of three and a half people because people take vacations or sick leaves. The good part about it is that these people can work from anywhere.

We are a Microsoft reseller. We have partnered with Microsoft. We have developed a relationship with their technical folks over the years. So, we kind of go directly to them. My partner came from Microsoft, so he has a very good relationship with a few technical folks. So, we, kind of, have some special privileges that a couple of other vendors don't have.

As a matter of fact, we had built a tool, but it took so long to get it vetted and get it through to ATOs. That's when we decided to convert to Microsoft Power BI. It has already been vetted and approved in the army environment. It is an approved government site for cloud services. We were looking for the easiest path, and that's why we worked with Microsoft BI. They've already been embedded into the government. It is bundled with Office 365.

If my technical person had to rate it, he would say very easy. All we need is to have the software.

It was done in-house.

They are charging us by users in storage, and there is a license fee. My financial people handle all that. The client has already worked out a contract with Microsoft, and basically, we're getting government prices.

The backend is the most important part. We understand its backend. We implemented the on-time system for an airport. We don't find its modeling complicated. We set up the back offices and get all the modeling done and everything connected. The customer doesn't even see that. They only see the part where they're running their reports and doing the analytics or whatever they need to do. We give them all the information at their fingertips.

Everybody is going to Business Analytics. A lot of people don't understand the difference between analytics and coding, but that's something for me to teach and educate them on.

I would advise doing your testing and environment setup. You should evaluate your product very well and figure out what platform your organization is running on. You should be careful and look at how well it integrates with other products. If you're not in a Microsoft environment, it is going to be quite difficult. Oracle and Microsoft are competitive. So, you go with one or the other. The reason why I like Microsoft is that they integrate with all applications. Microsoft controls 99% of the desktops.

I would rate Microsoft BI a nine out of 10.