Microsoft Power BI Reviews

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. 

It is one of the business intelligence tools we are using—mainly for all our data visualization purposes and building interactive dashboards. We use Microsoft Power BI to generate all different types of analytic reports. We move information from our data warehouse to a SSAS cube that we've built on top of all our dimensions. We also do a certain level of aggregation in the cube itself, which is then connected to Power BI.

It works well with SSAS, which we use to generate all different kinds of trending and analytics reports. Sometimes we use Power Query and DAX to build some aggregations on the Power BI side as well.  

I would like to see Microsoft BI add custom visuals and certain machine-learning capabilities. It would be nice if the DAX functions could perform some kind of predictive modeling. Right now, it just does a kind of descriptive analytics.

I've been working on Microsoft Power BI for three years. 

Throughout several updates over the past three years, I never saw any issues, particularly with installation or anything, so I see the product as stable.

I feel that scalability is one area where there is room for improvement. When there is a huge volume of data, like when we apply the aggregation, the reporting slows down. That's why we mostly build things in the SSAS cube itself instead of bringing it back to Microsoft BI to do the aggregation. Certain incredibly small aggregations can be done on the Microsoft BI side, but if the dashboard size is more than 1 Gigabyte, you start to see some performance issues. 

The Power BI community is really big, so we mostly rely on other users for support.

In some projects, we have used Tableau or ThoughtSpot. If we're dealing with big data, then we often consider using Tableau. Power BI has some additional features that Tableau doesn't have, like DAX and Power Query, but Tableau works better from a scalability standpoint. Sometimes for reporting purposes, when we want to generate some kind of dashboard on the fly for the user, we have used ThoughtSpot. 

We didn't experience any complications. We built everything on the desktop and in the .pvi files, then just move those files to the server. Afterward, we didn't see any issues at all in terms of setup.

I'm unsure about the exact cost, but the Pro license comes out to around $10 per user. There are also additional costs for custom visuals that you can pay for.

I would rate Microsoft BI an eight out of ten. 

The visualization part and its inclusion in a cloud-based application are valuable features. 

The solution is somewhat costly in comparison with MSBI tools. 

In MSBI, when it comes to mobile and maps-related applications, we are always looking for some support with the reporting tools. Once we click on the region, then automatically it goes to the two area maps. Based on the map, it will reinforce our data values. There is constant change involved and new updates and enhancements are coming out as needed in new versions. 

The solution performs well and is stable. 

The scalability is very good and use of the application is flexible. 

We can create certain tickets, contact them and explain our requirements and they will look into the issue and help us to find a workaround for us to implement. They will address the issue in the next version. 

We are very satisfied with their support. 

We are implementers of this solution and maintain the visualization on the reporting parts, as well as fulfill the business requirements. 

The solution is less expensive than other PowerBI tools, but more so than those of MSBI. 

The solution is less expensive than other PowerBI tools, which is why most people go with it, although it does cost more than MSBI tools. It has good feasibility for fulfilling one's business needs. PowerBI is very strong in the market at the moment and we are creating visualization that works. It is a stable tool, as well. 

While PowerBI is cloud-based, it can be used both on-and-off-premises. MSBI can also be implemented on-premises. PowerBI mostly involves visualization. 

I rate Microsoft BI as an eight out of ten. 

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.

I use Microsoft Power BI for analytics. It is an online service for business intelligence. I use it to analyze every piece of data that I have. My key performance indicators are on Power BI. My sales indicators, such as number of clients, number of sales and region, type of client, type of solution, due to date comparison, and due to year comparison, are really based on the sales of the company. I am using Power BI Pro.

Constant collaboration is the most valuable. I can build a dashboard, and several co-workers can access this dashboard. We can share information that is important for decision-making.

It is a very easy-to-deploy solution. It is compatible with a lot of data sources. It is also very stable and scalable. There is also a very good forum and a lot of help and online training.

I would like them to provide a license that just allows us to see dashboards. What I don't like about this solution is that in order to just watch a dashboard, you need a license. Currently, you need to purchase a full license of Power BI Pro just to see something, which is not attractive. If you have a license, you can see a shared dashboard, but you can also build a dashboard or you can collaborate with other people. However, if you only want to see a dashboard, there is no license for that. I only want to see the dashboard, and I don't want to do anything more than watching the information on the dashboard. There is no license that allows you to see a shared dashboard. This is one of the areas of opportunity because I would like a lot of people to be able to see a shared dashboard, not to interact with it or to collaborate online with it. 

I would like to see more compatibility with non-Microsoft data sources. Given the fact that everything is related to Microsoft Azure and all services available on Microsoft Azure, I see that they're building more connections to Microsoft Azure services instead of other non-Microsoft services. I understand the strategy, but it would be good to have more compatibility with non-Microsoft data sources.

It is a very robust and stable solution. We are a company that works with enterprise solutions from SAP and Microsoft. We have worked with companies that have 5,000 users and without a problem. So, it is very robust and stable.

Being a cloud solution, it is very scalable. You can easily scale it based on the usage. If you're using it, you pay for it, and if you're not using it, you stop paying for it.

In our company, Power BI being used by maybe 15 people out of 70. It is a growing solution. Three years ago, we had only five people who were working with Power BI. Now, we are building more and more dashboards for our service desk area, and its usage is growing.

I haven't contacted them. We report everything to our own Service Desk, and they are the ones who scale the problem to the manufacturer. This means that every time that we have important issues, they have to be solved in a very decent period of time by the manufacturer. There is a very good response time, and every time we had problems, they were solved. We didn't have anything pending.

Given the fact that it is on the cloud, it is really easy to deploy. It is only about connecting the engine to your data source and start building the dashboards. You can just connect your data. It doesn't matter if it is on-premises or as a service. You can just connect it.

It is based on the usage. If you're using it, you pay for it, and if you're not using it, you stop paying for it.

If your data source is a Microsoft-based data source, this is the best choice. If you have a data source that is not Microsoft-based and is on a non-Microsoft platform, such as MongoDB or Unix, you should see some solutions like MicroStrategy or Qlik. If you have a pure 100% Microsoft-based data source, Microsoft Power BI is the answer. You can do wonders with Microsoft Power BI. It is a very cool solution.

I would rate Microsoft Power BI a nine out of ten.

We use Microsoft BI on our portfolio management platform. We use live dashboards, in the public cloud.

We only use it for export and import, but that suits our purpose, along with the dashboards.

The upgrade process could be improved. Sometimes we miss information if we haven't kept up with the versions. It should be easy to migrate, but it does not provide enough information about what may be lost if you upgrade, especially if something goes wrong with the upgrade. Any current developments should be included in the upgrade so that it is a seamless process.

We have been using Microsoft BI for about 4 years. We use the latest version, and we have 4 users.

Very good. We don't have any issue regarding the stability of the solution.

The scalability is good.

You can find everything on their website. We rarely need to contact Microsoft directly, so I would rate Microsoft support for Microsoft BI as excellent.

Our setup is very straight forward and can be done in a matter of hours.

You have to know what you want to accomplish, meaning that you have to know why you are using the solution, what kind of information you want to show in that solution and the location of the data. I would rate this solution 9 out of 10.

I have taught and mastered many desktop tools, including Power BI, for the purpose of prototyping designs for business intelligence and data warehousing. Currently, I am teaching data analytics at graduate level and Power BI is on my schedule.

We teach tools like Power BI by going through common scenarios in a business intelligence environment, which most often deal with the factual numerics that get designed into a sales force reporting dashboard or similar solution, showing details like order placement, orders shipped and paid for, etc. The templates for these typically use a style of diagramming called star schema, which is a common dimension modeling technique. 

I can't say whether it's the most frequent real-world use case that a real customer would focus on, but for the level of our tutorials, a sales scenario might involve a description of customers, products, locations, maybe geography, and the timing of sales for trends analysis.

Other than Power BI, I also teach AWS and Azure, where I help guide students to plan and come up with architecture for deploying to the cloud. It's not actually very hands-on, as it's more to help with architecture diagramming for the intentions that students have when using them. And at our institution, all of our courses last only four weeks, so it's very fast tracked, which sometimes means that we don't really go too in-depth.

AWS has a lot of samples and diagrams, including many graphics that are fairly artistically detailed. The level at which I've helped students reference those kinds of diagrams is mainly for their team projects, to illustrate their intention, for example, to deploy a database into AWS. If it's an SQL Server database, we usually choose Azure. But it's not to actually do it. It's rather to have the intention to, for illustration purposes.

I had a brilliant student in May last year, 2019, who did her graduate capstone project - where I was her advisor - using Power BI. And she has two times now responded to my invitation to be a guest speaker on that tool to classes such as the data analytics class that I've been teaching for about 20 times now, going back six years.

At my institution, I'm the only one teaching database design, whether undergrad or grad, and I found Power BI was a very attractive tool to introduce during the database design class, and then later enable the students to use it for their capstone. Unfortunately, it didn't work out in November this year, because few of the students picked up on it and gave the actual time it would take to focus their attention on using Power BI templates.

Overall, my observation is that the enrollment is way down and the students who are still in the program are very distracted, I think because of the pandemic. Despite this, Power BI has helped me introduce students to business intelligence and data analytics because it's a very attractive and cost-effective tool (there's no cost to it, it's free).

Another reason I'm inspired to focus my time on helping students with Power BI is because of the analyses done by the Gartner Group and Forrester Research, wherein they reviewed the strengths of Power BI. Both of them call it a "killer app". That caught my attention. And Power BI seems like the best thing to suggest to the students.

And I'm up to it on my side teaching through online, although I'm regretting that I cannot go on a campus to be still there for the students whose strong preference is to be together in a room learning on site. I hope that in the class in May, there'll be more people really interested in actually using it. In November, I was hoping some of the students would, but for reasons such as the pandemic, these online students have too many distractions. Especially if they're also still working or they have families with kids at home.

What Power BI is, is a whole collection of templates of small amounts of data that can be used to do something for a real world project, that can be easily set up and become the business intelligence environment or a data warehouse for a large amount of data, for a real world customer. That's what is remarkable. And that's what it takes.

It makes use of the ordinary things, and they'll sound familiar. Excel, Access, or SQL Server as the database, and the deployment techniques like Azure for it to be in the cloud.

It's very heavily like Microsoft promoting its own products, but I forgive it because this time it works. And I'm speaking from some experience; I worked in the data warehouse technology group at Oracle for three and a half years, and I was helping Oracle's clients put up a data warehouse with Oracle as the database, and to migrate data into the Oracle database. So that was my background. And for me to be persuaded that this collection of regular, already known, already used desktop tools could work just as well, but with the added value of the samples, the templates, frequent updates, and lots of support. That says a lot.

It also has other features that I like, especially regarding the designs in the set of templates for things that would perhaps be very puzzling to somebody doing it for themselves. It has pre-built tables to hold, during project lifestyle, maybe a small select amount of test data with the intention of the large amount of data going into production after deployment. And it has all the table designs that start out generic but that can be easily customized.

When it comes to improvement, I would say there could be more tutorials for students in universities who are just learning it. And it wouldn't have to be just for students in universities. It might also be for the people who use it in the real world.

The evidence that I see when I look into it is there's a lot of user group type of connections to the Power BI world. And many, many bloggers telling their stories and promoting themselves or small businesses promoting themselves to do it for you using Power BI. The claim being that they could help you get it done instead of you doing it yourself. That's what goes on in this industry. You see a lot of entrepreneurial people who want to work in the role of consultant and get paid for it. There's a lot of that.

And the invitation to look into the websites comes from little mini tutorials, which can be very helpful. But the next step of those tutorials, if most of the people get what they want out of them, is a contract to do the work. I don't want to introduce those kinds of things to my students, because it's kind of promoting something that could be a distraction.

I worked for years as an independent consultant. I even did a fairly long series of contracts up in the state of Washington at Microsoft and I had 38 years in the industry before I became an academic teacher. But I'm avant-garde when it comes to sales. I avoid salesman because I don't want to believe the hype. I don't want to be deceived. And I don't want to suggest that somebody go that way. The topic of sales is overdone. This is an opinion on my part.

On a practical note, the process of importing data into a new environment that has recently been designed is always a major effort. And Power BI has some weaknesses when it comes to loading data into an otherwise good concept and a good design because if it's not seriously tested and all shortcomings noticed beforehand, the importing process will fail.

Even a cool tool like Power BI cannot anticipate the complexity of the variety of sources of data. But they're not alone. That would not be a disqualifier. But because I don't have direct yet, hands-on, having done this, I don't really know how Microsoft would improve this area.

I think they've got it handled on integration. Everything that you're working with is already a Microsoft environment or a Microsoft tool. It's integrated. But if you're using the desktop tools by Microsoft and you need to deploy into a backend of Oracle, there might be some things that a smart consultant has to help out with. So cross-platform integration could use some improvement in terms of ease-of-use.

I have used Microsoft BI in my data analytics classes for a few years now. 

In an abstract sense, it's holding up. I don't speak to actual customers of Microsoft products to answer that question. But I would suggest that it's holding up because the Gartner Group put out another magic quadrant output that describes it as being in the leader category.

It's a well-respected research group, Gartner. In fact, companies that want to acquire its research for anything more specific or consulting, have to pay for it and have ownership. I don't pay for it. But there are many vendors who have my school email on their lists, so I get the reports for free, and I have my hands on quite a collection of the reports.

And that's why I'm mentioning them because the Gartner Group has mentioned Power BI twice now. So as far as long-term prospects go, I'd say Power BI is a stable solution.

Microsoft provides frequent updates and a lot of support for Power BI.

I have worked in the data warehouse technology group at Oracle for three and a half years, helping Oracle's clients deploy a data warehouse with Oracle as the database. But when Power BI came onto the scene, I was more and more persuaded to use it instead for business intelligence and data warehouse purposes. This was mainly because I enjoyed how easily Power BI builds on existing tools that I'm already familiar with like Excel and Access. 

The setup is straightforward, because it exhibits itself within familiar tools, like spreadsheets.

The complexity comes when you try to convert from simple beginnings into something that needs to eventually become reality. But I'm guessing. I don't know that it's complex. And anyway, I personally like complex. It attracts my attention.

For my primary use case, i.e. teaching students, the free version of Power BI is adequate.

May is the next time I'll be teaching the data analytics class, the graduate class, and I will be actively trying to promote Power BI for the team project.

I would rate Microsoft Power BI an eight out of ten. 

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.