Microsoft Power BI Reviews

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.

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.

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.

We primarily use the solution primarily for making dashboards. We are also doing analytics on Microsoft BI.

The solution is very stable.

The product is easy to use and simple to navigate.

The product has proven to be quite flexible.

It is quite scalable and it is doing the work that we want it to. 

We'd like the solution to be more scalable. 

We'd like the ability to manage it on the cloud, as a cloud-based solution. It is running out of business as it is not able to keep pace with the big data. Big data is not something that BI can support. It cannot be scaled that much. 

The product doesn't support unstructured data. It doesn't support video, streaming, and strings of files. Microsoft is aware of this.

I've been using the solution for seven to eight years at this point. It's been a while. 

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable and the performance is very good.

The solution is quite scalable, although, in our case, as we are not on the cloud, we are facing some issues.

We have more than ten people using the solution currently.

I've never reached out to technical support in the past. I cannot speak to how helpful or responsive they are. 

I wasn't a part of the initial setup. That was something that was handled by another team. I can't speak to how long it took to deploy.

My understanding is that you only need two people to deploy the solution. Admins usually handle it.

I don't have any insights into the licensing and payments required. 

We are using the latest version of the solution. I'm not sure of the exact version number. 

I'd rate the solution at a seven out of ten. For us, it has met our expectations and we enjoy its capabilities.

I'd recommend this product to other users and organizations.

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. 

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.