Microsoft Power BI Reviews

I am a Power BI technical senior developer and consultant and I use Power BI to provide solutions for my clients.

Everything that's in M Query and DAX is the heart of Power BI because with these tools you can make up for a lot of other missing features. When I say "missing features", I mean it in the sense that, even if you don't have a direct feature to do something, there are quite a few workarounds that you can figure out with DAX and M Query to make different situations work. I think these two are really the soul of the tool because they make a lot of impossible things possible.

There's a lot of room for improvement because Power BI is a new tool and hasn't really been in the market for that long, especially considering alternative tools such as MicroStrategy or Tableau which have been around for more than a decade. Because Power BI is younger than those tools, I feel it hasn't reached a certain level of maturity that comes with time and it is lacking in quite a few areas which I'm hoping will be seen to in the future, given how it has been progressing so far with its new releases.

There is no specific area that I have a problem with. It's just that, with whatever feature you come across, every visual has its own formatting and behavior. What you get in one visual for a feature, you don't seem to get in another.

When it comes to the feature's functionality, that's all fine, but, say, for instance, that you want to go ahead and turn off only the sub totals and not the grand totals. This might not be immediately possible, especially if you are working in a project where your technical solution is the backend site which the users don't quite care about. What they care about is what they see and interact with, and the visuals and formatting (and visual settings) at hand are what really matter to them.

This is where I think standardization really needs to come in. Basic stuff like being able to selectively turn on or off only the sub totals or grand totals. There should be certain formatting options which should be standard across every visual. What options you get here, you should also get over there, for example. These are simple things, but many a time it's something the end user takes very seriously. They generally do not care about what's happening in the background with regard to the calculations and everything else.

In essence, the standard visualizations should have features and options in common with one another, even when it comes to other visualization tools such as bar charts and line charts. These are all pretty basic visualization features, and giving them some standard way to be customized will make them as capable and competitive as what other tools allow you to do. Of course, you can do this if you add your own custom visuals from the library, but when it comes to basic default stuff, they should at least be deep enough in terms of standard customization to compete.

Right now it seems like they're trying to add a lot of features, but at the expense of losing out on the essence of the basics. The basics in Power BI should be equally as good as the basics in any other tool, and in this case I believe it to be a problem of adding more depth to certain features. The width, and variety, of features is not a problem for me. Whatever features are already available need to be deep enough to work with comfortably, and I feel this is where Microsoft needs to direct its focus.

I have been in the BI world for about six or seven years now and for the last few years it's all been Power BI for me.

Their support is a little slow in the sense that when I post a question to them, I don't get a response as fast as I'd like. Unless you're a premium user and you've got a dedicated technical support team — that's a different thing.

When it comes the usual Microsoft bugs, they generally don't come up with solutions too quickly. And many a time they don't even have a running solution; some bug fixes will probably only be part of the next release. Even then, however, the new releases are themselves often not terribly stable. Whenever you get a new feature, you almost know that this one's not going to work as perfectly as you would want it to. So you just have to wait for the next one, and that's what it is. It takes a little while to stabilize. This kind of thing, along with their support in general, can probably be sped up a little bit.

I am certified in MicroStrategy and have worked with it for several years. However, most of the business I am getting lately is all Power BI.

In my experience, everybody is switching from either MicroStrategy to Power BI or Tableau to Power BI. I'm hearing and seeing this going on in the market, for some very good reasons. I'm no longer working with MicroStrategy, but not because I don't like it. It's simply that I'm not getting enough work in that area.

Setup is very easy. In Power BI that's one thing you will find across the board when using it. It is very easy in terms of getting something done. Even complex things can be done in a pretty easy way and there's no complex challenge in it.

The pricing is good. It's pretty competitive because I have worked on a few other tools as well, and Power BI is on the cheaper side.

That said, many times people are attracted by its affordable price tag, but then they see that it doesn't do everything they want and they conclude that that was the reason why it was so cheap. There's a problem with this kind of thinking, because even though it might not have everything, the price is still on the cheaper side compared to other analysis products like MicroStrategy. The complete suite of features from MicroStrategy is very costly, but at the same time there's no doubt that it can achieve a lot.

What you get with Power BI is that you start to find that even simple stuff requires a lot of gymnastics to achieve because there's no in-built, straightforward feature for it and you need to come up with a workaround. There are a few too many workarounds needed for my comfort, but otherwise it's a very good tool and it's one of my favorites. The pricing is competitive for a reason.

If you are looking for tabular reporting, then Power BI is not the tool for you. This isn't something that Microsoft speaks much about, and in my experience, if you want to do tabular reporting then there first has to be something in Power BI which can actually take loads of data and print it out on visuals in a tabular way, which is currently lacking. Power BI is really designed for analytical dashboarding and that's what it does best. For tabular reporting, on the other hand, it's better to just get the data exported out into Excel and do the rest there.

I would rate Microsoft PowerBI a seven out of ten.

I primarily use the solution for the reports. We use it a lot for self-reporting.

We're making a dashboard that can show specific details and can be easily customized. It's very useful for creating dashboards.

The reporting is good.

The solution is stable. 

We can scale it if we need to.

It's a very easy-to-use solution. The product is quite user-friendly.

The initial installation is difficult. 

The pricing is a bit high and we'd like it to be less expensive.

I've used the solution for two years now.

The product is stable. Its performance is good. There are no bugs or glitches. It doesn't crash or freeze.

The scalability is good. If a company wants to, it can expand.

We have about 15 to 20 people that use the solution.

We're not sure if we will expand usage in the future or not. That's still to be decided.

We manage technical support ourselves. We do not need to reach out to Microsoft for help. Therefore, I can't speak to how helpful or responsive they would be.

I found the initial setup to be difficult. It's not exactly straightforward. The deployment might take about an hour.

We use three people for deployment and maintenance tasks. 

We have to pay for licensing. I've paid for a license in the past.

We'd like for it to be a little less expensive.

I would recommend the solution to others based on its ease of use.

All our operational dashboards are on Microsoft BI. Visualization is primarily what we use Microsoft Power BI for today. 

We're in a position to explore all the underlying data. For example, your SLAs, how they're trending month on month, or how your backlog of tickets is going.

We look at all the respondent resolution SLAs or different priorities every month. If there's a dip somewhere, we're able to double click and then go to the actual client or the ticket, which has caused a problem.

You can go back and see if you need to do anything to recover from that situation. For example, if your SLA brings 25% and if you're dipping to 94%, go back and see why you're dipping. If there are, let's say, too many incidences from a specific technology or a specific client, go back and see what you need to do to fix those things.

We're now looking to get to the next level with exploratory analytics. We want to go into what we call explanatory analytics, which analyzes the underlying data. Instead of waiting for something to fail, you come out and say, "Hey, these are some areas that are not working well, and you probably need to look at it."

We're trying to use Microsoft BI and for what we call actionable insights. This tool should be able to build up and show you what the underlying data is telling you. For example, our affiliates may be trending at 95%, but since we run a shared service, there could be some clients where it's 100% and some clients where it's probably 85%. Those claims could lead to a client-side problem or a client satisfaction issue.

Explanatory analytics can give you such exceptions automatically. Then you can go back and work on those clients to ensure that you pull your SLA back up from 85% to 95% and ensure that customer satisfaction doesn't dip.

I think the visualization part is valuable. It's also very easy to build new dashboards. It's fairly intuitive for people who understand the Microsoft Power BI tool.

We're fairly happy with the product in terms of both configuring the Microsoft BI dashboards and making changes to them. It's fairly easy to make changes.

Actionable insights could be better. I would like it to provide exceptional reports that you need to act upon to keep your operations or businesses going. That's something I would like to see. 

On the origination side, if there are better graphs and maps to visualize data like I've seen other tools like Tableau do, it might be useful. They need to have very different ways of presenting information. If it's eye-catching, better than a pie chart or a bar graph, that's even better.

I have been using Microsoft Power BI for about a year.

Microsoft BI is stable. We aren't faced with too much downtime. On a scale of five, I would probably rate it at 4.8 out of five throughout any given week.

I think we have scaled up Microsoft BI fairly easily because it's on a cloud. We've added users. We added more dashboards from our different service lines, and we found it fairly easy to scale up.

The initial setup is fairly easy and straightforward.

I would definitely recommend Power BI from a visualization perspective. It's quick and easy to set up and scales up very well. If you've been using data on Excel sheets and converting them to graphs on PowerPoint, I think this is a tool that gives you almost a live visualization of what your operations are. 

We use it for our day-to-day IT operations. I'm sure it can also be used to visualize other data like how many clients, how clients build up weekly, and the various stages of transitioning client needs into services. These things can be very easily developed on our Microsoft BI dashboard.

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

Microsoft Power BI gives a true self-service tool to the user. The IT team can focus on ensuring that the database is in a good place. It is also in the cloud, which makes it easy for mobile access of reports and data. 

The business users have taken to Microsoft BI like a duck to water. It requires a low amount of training. Users already using Excel can generate new reports and dashboards within minutes.

• Real-time refreshing for SAP BW would be nice. We know its on the radar for the development team at MS. 
• Not having to login again after a mobile app upgrade. A simple login on mobile would be great. 

None.

None.

They are fabulous.

The previous products include Tableau, Cognos, BusinessObjects, and Sisense. All of them have high price tags! Why pay and get ripped off for these products when you have Power BI? It will give you just as much, growing every month at an acceptable cost model.

Want to waste a lot of money? Then go for the others, I can recommend BusinessObjects as a great way to burn your money.

Initial setup was very straightforward. Users can get up and running reporting on databases within minutes. I can read a number of databases including a good old Excel spreadsheet. 

Internal Team. It is that easy. However, we did get a third party to do the training to key users for us. The course was tailored to our business. 

Paid for itself in the first month. 

Make it low in cost. It is a no-brainer! 

Remove the cost of a licence to show a dashboard within SharePoint. Why should readers of a dashboard have to pay to view? 

Globally, we evaluated a number of products, including Salesforce's product, Microsoft won on the ground of simple functionally and cost. 

Love that fact that we have a great development team that is moving the product forward every month. 

SSRS and the Tabular server/Vertipaq engine/DAX are probably the two most valuable components, leaving out SQL Server (and Azure versions of it, including the Azure warehouse and big data technologies). SSRS's display functionality is resoundingly flexible, and by comparison to other vendors, relatively easy to learn. SSAS Tabular performs very well with modest effort in design, and the ability to perform complex business modeling through DAX calculations stands out in a crowd.

Microsoft BI really entails a whole catalog of products. The relative ease with which these products work together is where the primary value comes into play. When you buy SQL Server Enterprise, you automatically have access to SSAS, which can handle Tabular or multidimensional cubes and data mining, SSIS offering a pretty comprehensive integration toolset, SSRS, covering just about any paginated and subscription-based reporting, and of course all of the in-built features of SQL Server, the individual useful features of which there are too many to spout out here. Each of these components work well enough in isolation, or as part of a larger ecosystem with other vendors, but together are a well-integrated machine that can handle end-to-end needs on the entire lifecycle of data. Being one of the more popular vendors, Microsoft products are also the first compatibility for other vendors' products. The breadth of products do a fine job at enabling the delivery of data and insights to the right people, in the right format, at the right time. Doing so efficiently/quickly is where a huge amount of value comes in. Many other enterprise vendors are capable, but are either slower to execute, more work to maintain, cost much more to find talent and skills for, or some combination of all of the above.

No product is perfect, and the Microsoft stack is no exception. The first things that come to mind are Microsoft's recent shift in strategy to focus on cloud first. While this makes sense for them, it leaves the on-premise products lagging in support and new features, while the vast majority of users (mid to large corporations) are still using on-premise solutions and/or are cloud-averse. For example, the announcement that the pricing model for Power BI would change, simultaneously rolling out both Power BI Premium and Power BI Report Server created a great deal of confusion for people who were very enthusiastic about the product. The failures to address concerns with the speed and nature of the changes were felt by users across the spectrum, and it was a situation created by their cloud-first strategy. Similarly, if you look at the tried and true on-premise options for data processing, interfacing with emerging technologies, especially big data technologies, lags behind. This is considerably less true for Azure users, but that is specifically a cloud offering, which again, many corporate entities are not yet ready to embrace.

It's easy to think of BI as only the visualization aspect of data, and that point of contact between users and data is absolutely where the rubber meets the road in BI. In reality, there are a whole stack of tools and concepts behind the visualization that enable that interaction - from security, data governance, integration, performance, network and infrastructure, and automation... there are many facets to BI as a system. The visualization aspect, while being the most visible to business users, also happens the be the weakest point in the entire Microsoft BI stack. The PowerBI visualization experience is underwhelming in almost every way compared to many alternatives.

Another difficulty is navigating the many products within the suite. There are many components, and each component has many versions. Dealing with feature and compatibility issues with so many versions of so many products can be very frustrating at times. Microsoft does not do itself any favors on this front with the way they name their products. "PowerBI", for example, could be in reference to the desktop design tool, a cloud-based service for publishing and administering data models (which comes with three distinctively different pricing models, the features of which are different and not interchangable), or an on-premise server solution replacing SSRS. You'll make yourself dizzy looking at the Azure services offered. The good news is the sky's the limit, the bad news is you'll have to navigate some pretty cloudy areas to make heads or tales of what to actually use.

Four years, using largely SQL Server 2012 and related versions/components.

In general, no. Most stability issues encountered have been more related to network or infrastructure, and not the products being used.

As with any system, good design is paramount. I have certainly run into times when performance suffers, or changes and enhancements are slow and expensive. In every case, redesign has solved the issues. As hardware improves, and the many options (especially in the Azure and big data space) continue to evolve, designing for scale has become easier and easier. One of the difficulties that naturally occurs in this ecosystem is simply knowing how to design with so many options that can potentially do the same or similar task.

I have experienced mixed results on this front. We have had some very available and supportive account reps at times, and other times not so much. My biggest complaint would have to be that the disorganization from Microsoft's side makes the results on this front inconsistent.

Depends on which components we are talking about. For reference, however, I don't think there is a single Microsoft component that was as painful as any given Oracle component to work with.

Do your homework when deciding what components to leverage. The worst thing you can do is try to use them all. The gamut of products under the Microsoft BI banner enables every form of BI - choose the ones that serve your specific purposes, and leave the rest on the table until a new need arises.

We use Microsoft Power BI to budget for all departments and to compare the balance of the past month.

The accounting data needs improvement. 

I have been using Microsoft Power BI for a year. 

It is a stable solution. 

Ten users are using the solution. 

The initial setup is complex. 

I would rate the overall solution an eight out of ten. 

The solution is very powerful and very flexible. 

It is very easy to set up and you can connect it to multiple systems very easily.

They keep on upgrading, performance-wise. 

Power BI is very fast; they have improved Power BI a lot in general over time. YOu can see the difference. 

The stability is great and continues to get better and better.

The pricing is pretty good.

They should provide some kind of extra visual. There are a lot of third-party companies that provide these visuals, however, it would be better if, instead of relying on a third party, they could have their own. We should have by default in the package itself, some good visuals.

Technical support could be a bit better.

The performance could be enhanced in the sense that there is a limitation of the volume of data that it can hold. 

While they have some different options out there, they did not improve anything when you connect to any dataset, when you have to import. You need to connect online, meaning live.  

You cannot create so many things on the Power BI side, such as adding a new column, which is not possible in your live reporting, direct query option. In contrast, with the import method, you can do so many things. They need to improve on the direct query option side.

The product is stable. I have seen a lot of improvements in the stability of their application lately. If you compare what's available now to the last three to four years back, you can see it's more stable.

It's scalable and it scales quickly. Nowadays, being on the cloud, expanding is very easy.

While support is okay, they need to improve it a lot. Of course, they're improving as we speak, yet, I would say, if you can ask me the ratings, I would still say it's still rather low and good - not great.

I'm also familiar with SAP, which doesn't scale as well. SAP also is much more expensive. SAP is a big product, whereas Microsoft BI is much smaller. They only overlap in terms of the analytics cloud and the SAP goes above and beyond and offers many, many more things. 

The pricing is fair. They give you many options by splitting up the licensing. They have multiple types of licenses out there based on your usage. You can increase your pricing if you use it a bit more, however, it's still quite reasonable as compared to SAP. 

We are a customer and end-user. We are not a Microsoft (or SAP) partner.

I would rate the solution at a seven out of ten.

We have both deployments for Microsoft BI, cloud, and the on-premise.

We are using SAP BI and Microsoft BI to augment the other.

Overall Microsoft BI is meeting our needs.

In Microsoft Excel, you are able to have tabs. However, in Microsoft BI you do not have this flexibility.

When you create tables in Microsoft BI, you have to create them separately. I can't have several reports packed together in one document, whereby I can have different tabs. You could have several pages of your dashboard, such as a summary page with all the detail. However, in the paginated reports, you don't have that kind of flexibility. This is a major area that Microsoft needs to work on.

I have been using Microsoft BI for approximately three years.

Microsoft BI is stable.

I have found Microsoft BI to be scalable. We did an enterprise-wide deployment and every one of the 500 people in the company uses it.

I have not needed to contact Microsoft or the local vendor.

We use SAP BI in parallel to Microsoft BI currently. Our plan is to replace the SAP BI with Power BI. The phase we are in now is to run both of them in parallel and see how everything is operating before we completely phase out SAP BI. The focus isn't on SAP or Power BI. It used to be our SAP BI solution. Since we started using Power BI, the plan is to actually discontinue SAP BI. maybe by next year we will no longer use the SAP BI.

I switched to Microsoft BI from SAP BI because, in my part of the world, it is becoming the most popular BI tool. Additionally, the ease of integration and our organization is a Microsoft shop. Everything is Microsoft, our databases, our ERP, and we use Microsoft dynamics and Business Center. 

The ease of integration of the BI tool is important for our organization. The scalability and then the licensing are good. If you choose the cloud for SAP BI, you have to spend more. The planning modules sometimes do not come with the package and you will need to spend on it.

It is not necessarily that Microsoft BI is better, but because there are other benefits when you consider Microsoft BI. The ease of integration with the DB and the ERP, and then you look at the overall cost.

The initial setup is simple to do.

We did the implementation ourselves. The solution does require maintenance.

The price of Microsoft BI is reasonable. Other solutions such as SAP Cloud are more expensive.

We pay annually for the license of the solution and we are using a premium license.

The choice of a BI tool is relative. If you have the capacity and the budget, you could decide to use SAP BI. There are other BI tools on the market. Why did we choose Microsoft BI is because of the nature of our business environment, the nature of your data, and many other factors that have to be considered.

I rate Microsoft BI a seven out of then.