Microsoft Power BI Reviews

The visualization and reporting are the most valuable features of this solution.

It is quite flexible for reporting purposes.

This solution is resource-heavy. I would like to see it consume fewer resources. When I use it on my laptop, it consumes a lot of resources.

I have used this solution within the last 12 months.

We are using the latest version.

It can scale easily.

We have more than 50 people who are using this solution in my company. Across the company, most are in marketing and finance.

I would rate the technical support an eight out of ten.

We use Oracle BI and Oracle OBIEE.

The initial setup was pretty straightforward.

It would be better if the price was cheaper.

I would recommend this solution and suggest they use it.

I would rate this solution an eight out of ten.

I mainly use it for sales analysis. We are in the telecom industry, so on a daily basis, we see a couple of trends in the number of activations of customers and registration, the performance of the dealer, and items like that.

Its integration with the Microsoft Office Suite is great. I can easily connect it to any of the Excel or any CSV files, and I can immediately create a dashboard. 

It's like the higher level of pivot tables. For the people who mainly use Excel, this is like an advanced version. This is much more flexible and I don't have to train people to use it, as it's very user-friendly compared to Qlik. Qlik needs some expertise and a layman cannot immediately go to Qlik and do stuff unless he understands it. When it comes to Power BI it's a five minutes tutorial, he can definitely understand what needs to be done.

The solution is stable and scalable. So far I don't have any issues, however, it depends on the amount of data we use. I'm just running it on my PC.

The initial setup is straightforward. 

The solution is free as it's bundled with Office 365.

Maybe they can enhance the UI a bit. Right now, it's very basic, I would say, compared to the MicroStrategy or Qlik. 

They could also improve the mobile experience. If people are using this mobile app for BI, they need better performance there. The rendering of the objects, for example, if you create the dashboard on Power BI when someone sees that on the app, it comes in a different format. They can do some enhancements there to standardize it.

Once we expand it as a centralized repository, if I could find much more use cases, that would be ideal. However, now it's very limited in our organization.

We don't use the solution filly and don't yet have a license for it. That said, I've had the chance to work with it for more than a year now.

The solution is stable. There are no bugs or glitches and we don't have any trouble with it crashing or freezing. It's reliable and the performance is good. 

My understanding is that the solution is scalable. 

I can easily load a billion rows in less than two or three minutes and play around with it. However, I haven't tested on big data files or anything like that.

Right now, we don't have too many users. It's just three to four people as of now, as our primary BI tool is still Qlik Sense. It's only for ad hoc use cases we use Power BI, and just myself and a couple of team members, as well as the BI specialist, that access it.

I've never reached out to technical support in the past. If I run into issues, I tend to Google solutions to find answers to my questions. YouTube is also a good resource if you need information.

We currently use Qlik Sense as our BI product.

The initial setup is not complex or difficult. It's simple and straightforward. 

It took, 10 to 15 minutes, if I remember correctly, to set everything up. It's just a .exe file installing. It's not hard and it's pretty fast.

We did not need a consultant or an integrator to handle the implementation. I just played around a bit with it.

We don't have a license on Power BI, so we don't publish anything. It's mainly for some ad hoc use cases that we use Power BI format.

Power BI is free; it comes with Office 365.

I've currently looked at MicroStrategy and am in the process of comparing a few other products.

We are just a customer and an end-user.

We are using Power BI, however, not to the full scale. It's still unlicensed as of now, and I'm using desktop versions only.

I don't remember the version, as it comes with Office 365. I didn't give a thought to the version.

From my experience with the desktop version, I'd rate the solution at a nine out of ten.

From my experience, I'd recommend the solution to others. 

We have a startup focused on analytics around sports and athletes' performance. The data sits in our platform called Hercules, which is exposed through an ODBC connector or API layer. We're currently building a connector to expose that data in a consumable way, inside Power BI (with one connector for Tableau as well). 

I love the fact that it's got a very intuitive user interface. 

I like the fact that you can create aggregations and view measures and metrics on the fly. 

I like the visuals themselves as all of our customers are moving away from Excel and this gives them a very unique way to have their data represented in a more visual manner with active slicing and dicing data right there, with the time dimensions and different dimensions. 

I also like the automatic refresh mechanism that it can do. You can have the data refresh automatically every 30 minutes, for example.

The initial setup is pretty simple. 

The stability has been pretty good.

The solution can scale.

Technical support has been great.

Most clients have MacBooks. Therefore, they use Tableau as Power BI Desktop is not available for the MacBook right now.

When you're building, the documentation sucks. It's a painful experience to find out how to do things inside the connector framework. 

I don't like the fact that they need to have a premium excuse to manage larger sets of data. On top of that, there are limitations in building a custom connector. If you want to build a custom connector for your customers, the navigation is flawed. For example, when I build a custom connector to talk to Power BI and report, I want some contextual data of the report, and I want to have what we call incremental refresh. However, incremental refresh right now is only supported in a SQL-based backend. It's not supported for API-based connectors. That's something that we really, really want. We only try to work around it.

Basically, I would love to see that incremental refresh with API-based connectors. I'd also want the report-based contextual information available inside the connector.

The licensing is very confusing.

I've been using the solution since about 2014. I've used it for many years at this point.

We've found the stability to be fine so far. there are no bugs or glitches. It doesn't crash or freeze. 

It's easy to scale if you have the premium model. We just started exploring that right now.

The clients we have that use it are medium-sized businesses. These are basically soccer clubs or sports clubs, who are internally using it. however, we want to give it to a larger audience. We haven't gone there yet, though likely we will in the future.

Technical support has been awesome. they are helpful and responsive and we are more than satisfied with the level of service we receive from them.

I also use Tableau. I've used Power BI to a larger extent than Tableau, however, we have a startup in which we have an audience on BI and we are doing research to see how many of them are on Tableau versus Power BI.

We didn't previously use a different solution. We started with Power BI because that was one of our device partner's tools of choice. However, we are trying to support Tableau and Power BI now.

The setup was pretty straightforward. I mean the setup for the Power BI Desktop. The download is pretty straightforward. Once you get to do more complex things with it, using the gateway and things like that, then it gets a little complex. On top of that, the documentation is difficult. It's there, however, it's difficult to find.

The licensing is a little convoluted, and not easy to take advantage of. You're able to scale it in the premium model. However, they are very different versions. There's a difficulty in understanding which one of them applies to you and what the costs would be eventually, and what the performance and thresholds are for each one. The documentation might be there, however, for a small company, in order to find out all the aspects of licensing it's not that easy.

We've also evaluated Tableau and we use both right now.

We are in the startup program for Microsoft.

I'm on the latest version of the solution. I cannot speak to the exact version number.

It's deployed on the cloud for automatic refreshment service and it's got a gateway on-prem.

It's a very good tool to quickly get started and it does scale, however, as you get into the larger deployments and at a larger scale, it's better to involve a Power BI expert or a partner to help you get there.

I'd rate the solution at an eight out of ten. There's room for improvement from the setup and scale perspective.

Compared to Cognos, Tableau and Power BI are pretty fast. 

The initial setup is very quick. Connectivity, installation, and configuration are pretty fast and seamless compared to Cognos. Power BI eradicated dependency on a framework model. 

Power BI is cheaper than Tableau and Cognos.  Power BI Desktop comes free and the Pro license is $10 per month whereas Tableau desktop would cost you $70 per month. Cognos is mostly suited for large and medium size companies 

For someone who is new, I think that Power BI can be a little complicated. Overall, on a scale from one to ten, I would give Power BI a rating of seven. 

I'm using the desktop version and collaborating within our company.

As a training company we wish to analyze the instructions as they relate to our customers. Also, we take certain examples for our classrooms, our training.

I consider the solution to be quite good. In contrast to what we were using before I think that Power BI has given us more extensive results. It's more intuitive and it is better for understanding the whole process without much code. We're only using the user interface, not writing code.

We find it to be easier and it provides a better understanding of the results, both for us and our customers.

I cannot think of anything needing improvement at present and am quite satisfied with what we have, This said, I would like to see integration with Excel. This is because many of our customers like to have their results appear not only on a dashboard, but also in Excel, as they use it extensively. They would approve of the integration. 

Also, there should be greater functionality from Power BI for the performance of certain complex tasks. Many things are being done with the interface and if we'll want automation to play a role then we will need more flexible programming, such as we have with Data Expressions. The interface must be utilized for carrying out more complex tasks. We wish to automate this using software and programming language. 

I have been using Microsoft BI for one or two years. 

I feel the technical support to be fine. We have all the support that we need.

Having a proper understanding of how the data is modeled poses the greatest challenge. However, someone who has this should find the installation to be quite straightforward. The initial step involves having an understanding of the data model. 

I think the setup is quite easy and straightforward. The solution can simply be downloaded  and used. The most difficult thing involves the distillation of SQL Server, not what relates to Power BI.

From our side we have around 20 people who are responsible for the deployment and maintenance, although I include in this figure not only the technical but all of the administrative staff. We have the trainers and also the people who are working with the technical support to deliver the training.

The cost of the solution is more flexible for us because the desktop is free and we pay as we use it in the cloud.

The customers have licenses of their own. We use their installations to help them with their work. Usually, these people represent new entries into the company and we give them the initial experience to start working with the software.

As I could tell, I feel the solution to be easy. It is very good that all the users, as they use MS SQL, have a product from the same company. It is an overall experience for them to use Power BI.

We are an end-user and a partner to the vendor. We do training and provide consultations to our customers. 

We work with companies, around eight in total, and we deal with their employees. Overall, we are talking about approximately 300 people. We give training to the employees of these companies and also provide consultations. 

I strongly recommend the solution because I think it's a very modern tool and quite easy for all the data analysts and programmers.

I believe that all of the people who we have mentioned so far are quite satisfied with the solution.

I rate Microsoft BI as a nine out of ten. 

We have some monitoring data from turbines, and we want to plot the data to monitor the health state of turbines in different time stamps. I tried to download some data from the Postgres database and then do some plotting with that. I also tried to link different plots with each other to filter them and things like that.

I liked that Microsoft Power BI handles a large amount of data. I can handle hundreds of rows from Postgres in a few minutes. I also like how it detects the relationship between the tables without explicitly saying that. It just detects the relationship automatically. That made it easier to work with the data.

It's not really complicated, but I didn't find the things I was looking for. The ones I used to work with within Dash are more open, and there are more choices. But with Power BI, there are only limited types of plots that I can use.

For example, when I wanted to put the plots in Power BI, there was no extendable space. You have a limited page where you can place a maximum of three plots in that, and you can't do more than that on a single page. You have to create a new page, a different page for that. That made it a bit annoying, and the filtering part is limited, with basic functions. If you want to make custom filtering or custom functions, you can't do that.

Suppose you want to code a plot, Python available. You can code the plot you want, and you don't have to use a predefined one. But when you want to plot it and you want to import like five or ten packages in Python, there are limitations. It doesn't support all the libraries that Python has. Microsoft BI only supports a few, like three or four libraries at most. When I want to use my old code in Power BI, it doesn't handle it, and that was also annoying.

In the next release, it'll help if they added a coding area where you are more open to make custom things. Especially for a developer, it needs to be improved. For a Power BI person, it's fine, I think, because it doesn't require much technical knowledge, but a developer will need it. Maybe they should create a space for that.

I have been using Microsoft BI for the last three months. 

It's stable, but it's so slow. Sometimes it takes some time to respond, especially when you put two or three plots with big data. It becomes very slow.

I didn't contact technical support as I used the support on the internet. I'm satisfied with the documentation, but I didn't find what I was looking for.

I was using Dash Open Source, but when I discovered that it would take a lot of time, I wanted to define a platform for that. So, Power BI was the solution. Now I want to try Tableau, but I haven't had a chance to do that yet.

I used a two months free trial to see if it had what I needed. I can pay later for a full license, but I don't think I will do that.

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

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.

We're a retail hospitality chain spread throughout India, operating over 330 outlets across the country in various formats, ranging from a coffee chain to fast food restaurants through our in-house bespoke brands. All these brands run out of travel hubs like airports, railway stations, and highways stops. We needed a solution to manage both the multiple SKU levels and in terms of individual dynamics, the profitability of each store. We constantly track the various types of back-end raw materials, specifically on our prediction modeling where we use Power BI. We also use Power BI analytics to drive those results with regard to the day-to-day dashboarding, reporting in terms of collection, on sales trends per hour, manpower and the like. We are customers of Microsoft and I'm the CIO. 

I like that the interface is very fluid in the sense that you can upload via Excel or you can attach via connectors, any software you like.

The challenge of this product is in truncating the table data. It would be great if Microsoft would include a naming convention which has the advantage of enabling a VLOOKUP on top of it, so two tables can be merged more seamlessly. Currently, the time it takes to merge two tables in Power BI makes the entire analysis quite complex because it requires common numbering in one table and then creating another common indicator in another table in order to merge the two. It wastes precious time. 

Secondly, while they talk about visual analytics, sometimes the challenge is when you're looking for more in terms of geovisual analytics, such as city maps which requires a functionality whereby you can upload transactions. For example, if I want to visually present my data on an airport map, showing which stores are generating what revenue dependent on the traffic heat map, I am unable to do that because I cannot upload drawings. Ideally, I'd like to show each store as a bar map with waves explaining the sales in each location. It allows me to pinpoint which locations are more profitable. 

I'd like to see a degree of variability so I have the flexibility of putting those variable components in my predictive modeling, and I can get a feel for the trends. It requires a common input database. You can do it in Excel, but you can't do it in Power BI, which I find surprising.

We've been using this solution for nine months. 

The product is fairly stable, it doesn't get too many upgrades or updates from that perspective so it's fairly straightforward in terms of implementation and our entire ecosystem was on Microsoft which helped us. The only area that can be problematic is when you're trying to create relationships between two databases and you're trying to link it with your Power BI solution, sometimes that mapping takes considerable time.

The solution is scalable. We are a cluster of eight legal entities and we've been able to expand to all of them. We started with 20 outlets and today we have 350 outlets. We are more granular and today Power BI allows us to drill down to the last voucher. We have around 14 users from the finance and operations teams.

We haven't needed to call Microsoft, because we worked with one of their gold partners in India. So we are on an AMC model with them in terms of manpower. If there are any problems or upgrades we need, we reach out to the partner. 

The initial setup was straightforward for the simple reason that our entire ecosystem was on Microsoft and we use Azure Web Services in terms of hosting. We split the entire project into two parts to simplify things. The first part was more about the granular analysis of sales and various other elements, which took considerable time due to the many external stakeholders involved. Phase two was relatively simple, because it was department specific and we created a split team, which led to the creation of a better platform.

Licensing is on an annual basis. We have a complete Microsoft Ecosystem license. I think there is room for improvement with the licensing, specifically during the pandemic when it would have been reasonable to offer a discount. Many other companies, SAP and Oracle, for example, gave waivers to the MSME sector. Microsoft traditionally is used by smaller or medium-sized companies so I was expecting some sort of discount on the pricing, but unfortunately that didn't happen. We managed to avoid an escalation in cost, but frankly speaking, a discount would have been much appreciated.

It's important to understand your entire ecosystem in terms of your tables; the kinds of tables your back-end database has and the elements of analysis that you are looking at. If you are looking at predictive modeling, you need to have at least two to three years of data, because that allows you to define the trajectory of the predictive modeling. Otherwise, it doesn't serve any purpose. Secondly, be very specific with your implementation partner, as to how you'd like a particular visualization tool to look, otherwise you may not get what you want. Finally, it's important to invest in people and create a center of excellence made up of people who know Power BI well, or who will get trained and certified on it. You'll need an in-house team which can do the small tweaks and changes as you require, otherwise you'll get stuck each time you need to do something.

I rate this solution an eight out of 10.