Microsoft Power BI Reviews

We mostly use this solution for dashboards and reporting.

There are roughly 2000 people in our office. At the least, 100 people use Power BI. We have around 10 super users who use it a lot. A lot of people just use it to look at dashboards. A lot of managers look at Power BI for their dashboards.

It has centralized our organization. It has democratized dashboard and report building and provides a centralized format. Without Microsoft BI, people would otherwise develop and manage their spreadsheets in Excel, which is just a lot harder than what Power BI enables us to do.

The standard BI visualization capabilities are great. It makes all the visualizations and has a drag and drop builder. It also has a power query data modeling capability that's excellent.

We're a big organization. We're looking at standardizing. Anybody can just pick it up and use it because it's easy. We want to be able to standardize what Power BI is and I think that's a challenge that we're encountering now.

Anything they can do to improve enterprise collaboration is going to help people get set up and utilize the solution.

I have been using Microsoft BI for roughly two years.

It has crashed, but it's pretty stable. I haven't had any problems where a published dashboard was not working. Once a dashboard is published, I haven't seen any problems with it.

I think it depends a lot on the data access. As long as the data backend can get into Power BI, then everything works. If there are any data connection issues, that's when there will be problems.

I get tech support from my admin. I've never contacted support.

We have a Power BI admin administrator that helped us with the initial setup. From the user's perspective, it's pretty easy.

I think it's a good price, from what I've heard. I know it's competitive with other Power BI tools. It comes in lower. I've heard no complaints about the pricing.

Our company did evaluate Tableau and a couple of other tools. We ended up promoting Power BI for everyone because it was licensed and we were already using Office 365. It integrates well with all of our existing environments.

From a user's perspective, I'd advise people to really try to understand the data sources and have a good data environment in place, beforehand. That makes the Power BI environment much better.

Overall, on a scale from one to ten, I would give this solution a rating of nine. I think it's the best BI tool that I've used. I know it has a really good rating. It accomplishes a lot for us in terms of data manipulation and BI in the reporting.

We primarily use the product for running the reports and all data extraction in our organization.

The solution is a wonderful tool overall. 

Power BI is very powerful and very easy to use. Its user-friendliness is one of its most valuable aspects. It has a very nice user interface that makes everything easy to navigate.

The product can go easily go and extract data and it can put it into any format.

It's a very good data analytic tool.

The initial setup is pretty easy. It's pretty straightforward in general.

I can't say that anything glaring is missing from the offering at this time.

Microsoft is doing a lot of research on it and they're coming up with a lot of good release items.

I'm not overly technical, and so I can't really speak to any shortcomings from a technical standpoint.

I'd like to have more time with the solution to evaluate it to see if there's really anything missing. We don't really go in-depth with the product.

I've been using the solution since about 2017. It's been a few years now.

The stability is very good. It's a Microsoft product and therefore they wouldn't put anything out that wasn't tested and worthy of release. There aren't bugs or glitches. It doesn't crash or freeze. It's quite reliable and offers good performance. 

While the scalability is there, the cost is what you have to factor in. It has to scale as if there's more data, it needs to meet that demand and be able to extract and analyze it.  

Technical support for the most part has been very good. They are helpful and responsive. We are satisfied with the level of support we receive. On a scale of one to 25, I would give it a mark of 20.

We've found the initial setup to be pretty straightforward. It's not complex. A company shouldn't have too much trouble getting everything up and running.

I'm not sure of the exact cost of the solution. It's not an aspect of the product I need to worry about.

I am aware that we currently have an enterprise license.

I personally haven't evaluated or compared any other solutions. I don't have any knowledge in terms of how it compares to other options.

We are customers and end-users. We don't have a specific business relationship with Microsoft.

I would rate the solution eight out of ten overall. We've been pretty satisfied with the product.

We primarily sell Power BI licenses. 

Mostly, we focus on the retail industry. Usually, we are using the Power BI reports for dashboards. We are also providing our customers with some data warehouse reporting. Basically, we do long-term categorization of stock and inventory numbers and sales figures so that they can compare the sales and stocks to the inventory numbers.

We tend to deal with physical inventory reports. We tend not to deal with the solution for financial operations.

The solution has different licensing tiers.

The product can scale if you need it to.

Technical support is quite good.

With the cloud deployment, there's no setup required.

The product works well for small or mid-level organizations.

The solution's stability could be improved. In the retail industry, due to issues with information updating and data uploading. Clients may end up pricing items wrong as they could accidentally base their choices on old or wrong data.

The licensing needs improvement. There needs to be a middle option between Pro and Premium versions. It could also be less expensive.

While we have experience with Microsoft tools for the past ten years, I personally have had experience with Microsoft BI for the past two or so years.

The solution is not really stable. I've faced a lot of limitations especially in terms of some data flows updates. We have faced some exceptions. Right now, we have created a case for Microsoft in order to solve some problems we've been having as, right now, there's some sort of system fault.

While the platform is a little more stable, the big problem is the latency issues around customer updates.

In a recent project, in Sweden, we faced an exception in Power BI from the update path. Whenever we refresh the animations and the fact tables, we faced something that said we couldn't upload the data. After 20 minutes we tried to refresh again. We didn't change anything with our reports or platform or anything related to infrastructure or schema. We didn't touch anything. An yet, the data is updated successfully. That leads us to ask the question: what was the problem 20 minutes ago? We still don't know the answer.

That is why we need some stability for the update service. We are deciding some business decisions based on this data. If this data is not updated, we may decide to take the wrong path. 

This is very important in the retail industry. For example in the grocery field, sometimes with vegetables or fruits or other products, customers need to decide to change the prices within lock days. They need to decide, based on demand, if they should increase or lower prices. They can't make the correct decisions if the numbers don't update.  

The scalability potential actually depends on your licenses. Microsoft provides three licenses. One of them is absolutely free. Another is called Pro. Yet another is per user or Premium. There is a huge difference between the Pro license and the Premium license. There is no need to scale the Pro license or other license models.

When you put the on-premise reports, you can scale out or scale up. It depends on your existing resources. However, in the services as a software (SaaS) version, it actually comes with Microsoft's units or Microsoft resources. 

We have an ASFP agreement with Microsoft. As a Gold Partner, Microsoft is pretty good and responding automatically and helping us resolve issues.

If a partner does not have an ASFP agreement, they tend to have to go to forums or try to Google answers to their problems.

We are aware that sometimes when we make changes to BI, the solutions might be complex. There might be SQL involved, which needs to be taken into account, for example. We may have to look into other resources and other tools to see if there are interactions that are the issue. However, Microsoft is quite helpful as we work through issues. We're quite satisfied with their level of support.

We also work with and sell MicroStrategy in Turkey. 95% of the MicroStrategy projects have been completed with our company. It is a direct competitor with Power BI. My company commonly does consulting for some small and medium markets and for that we recommend Power BI. Whenever we talk about enterprise-level solutions, the company we will use is MicroStrategy.

There isn't much of an installation process, as the solution is on the cloud.

There is a free license, however, it is limited. The Premium license and the Pro license functionalities are very different. Whenever we talk with our customers, they ask "Should we chose the Premium?" We say that "No, you don't need to, as it's too expensive. It is much more expensive than the Pro license." However, the Pro license functionality is not enough for some customers. There is no middle between Pro and the Premium. We need something in between.

The Pro license is maybe suitable for SMBs, small and medium-sized businesses. The premium version is ideal for companies that need to scale up and out.  

There also may be some additional costs that can drive up the price.

I prefer this product and I suggest Power BI to all customers, however, we know that if Power BI is a new idea, we make sure to show company-specific data or analytics for analyzing the data and how this solution can analyze everything quickly. That said, it's not for everybody. If all companies tried to put all their reporting expectations in the Power BI, it would not fit their expectations.

It's not a standalone solution. You need other items in your toolbelt. You need, for example, something that can handle raw data, you need warehousing, et cetera.

In general, I would rate the solution eight out of ten.

We primarily use the solution for building dashboards, one-off analytics, and things of that nature that combine data.

The functions from a standpoint of generating analytics have been really helpful overall. That aspect has helped improve our organization.

In general, we are pretty pleased.

The ability to combine the data and to connect with pretty established platforms has been the solution's most valuable aspect to us. 

The fact that you can visualize items is great. The visualization power is very good.

The initial setup is straightforward.

I don't know if I can pinpoint any specific items that I don't like. However, the more connectors that they provide the better. 

I don't use it day in, day out to tell you if it has any kind of functionality items that may be open up for improvement opportunities. 

The solution could probably beef up items related to statistics and things to cover the gap between the advanced things that you can do with Tableau. Any kind of advanced statistical analysis would be very helpful in future releases.  

The solution could be quicker at rendering data.

I've been using the solution for three years or so.

The solution is very stable. It's reliable. We've been happy with it. There aren't bugs or glitches. It doesn't crash or freeze.

The solution can scale well if you need it to. That shouldn't be a problem for any organization.

I'm not sure how many people are actually using the solution in our organization. Everybody has been kind of encouraged to leverage the platform on an ongoing basis. However, obviously, those that are holding jobs related to any kind of analytics are probably more prone to using it.

I don't tend to deal with technical support. That's probably more on the IT team than on my plate and therefore I don't really know how their tech support works. I can't speak to their knowledgeability and response times.

With our company, there were probably those that needed to do advanced analytics that were using solutions like Tableau or Excel.

The initial setup is not complex. It's pretty straightforward. A company shouldn't run into any problems when it comes to setting it up.

We have a pretty strong partnership with Microsoft and we tend to help them develop their product as well.

We are using the latest version of the solution at this time.

I would advise other organizations that the product has a lot to offer and therefore it's worth the investment and the effort.

I would rate the solution at a nine out of ten. Sometimes it could be quite at rendering data, however, overall, we've been happy with the results.

I lead the data visualization competency. As a competency leader, my responsibility is to make people grow in this technology. It could be Power BI, Tableau, or QlikView. We are service-oriented, and depending upon the demand, we have to have experienced people and a resource pool ready in these areas. Depending upon the requirement, I decide how many people need to be trained or hired.

Most of the clients I am interacting with are looking towards Power BI because of the cost and simplicities. It provides an entire feature set and a complete solution. It has tight integration with Office 365, Dynamics 365, Microsoft Technology Stack, and datatypes like R and Python. 

It should be more scalable for an enterprise-level implementation. When you deploy large data sets, the response has to be faster in Power BI. This is one thing that needs to be improved in it.

I have been using this solution for close to two years.

We found no issues. It is an aggregated reporting tool. It cannot handle a detailed level of data. It is meant only for the dashboarding purpose. You need to have your underlying data in an aggregated way, and then it would be faster. It depends on whether you have a live connection or you don't have a live connection.

We don't see many issues, but whenever we put a request, they at least respond.

I have worked on Tableau. Before Tableau, I have worked with traditional tools, such as SAP BusinessObjects. My team has got experience with Spotfire, but we are not seeing a great demand for Spotfire.

If you ask me for the top three, I would qualify Power BI, then Tableau, and then QlikView. That's the demand that I'm seeing in the market from various customers.

I am satisfied with its price. Its price is very less as compared to Tableau and QlikView.

My first advice is to learn SQL. The foundational knowledge and SQL skills are the most important. You have to be very strong in writing SQL code. You have to improve your mind so that you know what you are writing in Power BI. After that, it is very easy to pick up any front-end reporting tool, such as Power BI or Tableau. After you have good expertise in Power BI, you can slowly learn Python so that you can do good integration. All these efforts would be great for your career.

Being a gold partner of Microsoft for the past few years, we work directly with Microsoft product teams. Sometimes as part of a pre-launch, they also connect with us. If we see a feature or functionality that a client requires, we at least put it across to them. How they prioritize it within their product team is up to them. They prioritize depending on the need of the market and demand from various clients, and they release features accordingly. Sometimes, we also work on a pre-release.

They release new features and functionalities every month. They have also recently released data protection smart narratives. If you look at the Gartner report, they are leading. I see a lot of demand for this solution.

I would rate Microsoft BI an eight out of ten.

We are an analytics company, and we consult for different companies. Currently, we were doing automation of financial reporting, income statements, balance sheets, cash flow, and different kinds of analysis on revenue and products. We extract data from ERP solutions, accounting data, and then we transform that into financial reports.

The data modelling and the use of decks are key features. It is difficult to create financial statements using most BI solutions, with decks it is a bit easier to summarize data and to have cascading totals that you would find in an income statement or balance sheet. Most other solutions, you can not have a moving total but with this solution, we found it very easy to implement. 

I also find connecting to different data sources is quite simple. Other solutions we were using before were complicated. 

I think that there should be visuals for financial reporting videos. It should just be a plug and play because there is a lot of coding that goes into it with different clients. We should have a visual for income statements and other elements, this should be made easier. For example, suppose you are looking at an inventory report, it is all plug and play because you can just use a matrix or a table to summarize the information and the visuals. The systems are more adapted to that kind of area than for financial purposes.

For the next release, I think they need to improve on getting more visuals that are related to the finance side of things. Like I mentioned before, the matrix now is more of an OLAP cube, we are looking into something more adapted to the finance field, such as a drag and drop where you can build an income statement very quickly without too much code. This would be a nice addition. 

As far as I understand Microsoft has two solutions that are similar, Power BI Report Builder and Power BI Desktop. The features that you get in Power BI Desktop are more advanced than the features that you get in Power BI Report Builder. They should just merge the two and move forward this way. There is no reason to have two different applications serving the same purpose.

I have been using the solution for 18 months.

The biggest problem we have had is refreshing with MySQL, we are using a MySQL backend. It has to refresh all the data at once and store it in a cache, is my understanding. I am not sure where Power BI stores the data that it gets from the warehouse, this takes some time. If there are interruptions in the network, then the figures become messed up at some point. It should either commit all the data or it should not commit anything at all if there are errors. I think that is the biggest issue we have had so far.

We are rolling out the solution to various clients and one of them is a large client in the manufacturing industry. The solution scalability is very good, we can do a lot with it.

We have about 40 users at the moment. As we continue to expand, we are looking at approximately 20 companies with about five users at a time. Currently, we have done five companies, but I think by the end of this quarter, we should have about 100 users in total. At the end of the year, we hope to have at least 200 users from different financial departments in different companies. It is my team that does the financial reporting, we also have other companies that have the operations and logistics. We are looking to probably double that figure because eventually, we should be moving to the enterprise license. We had seen that the enterprise license will be beneficial to us. If everything goes as planned, we are looking at about 500 users at some point.

At the moment we have not needed much technical support from Microsoft. Most of the problems we have faced have either been resolved by someone else on the forums available. We also have an expert consultant in the UK who helps us. The areas that have needed assistance has been very minimal.

We have used Eclipse BIRT and Knowage in the past but were not as good and more complicated. We find Power BI is more direct, it is much easier to connect to other data sources and so forth.

The setup was very straightforward. You just download through the Windows Store or through the website, then you just start to connect your databases.

The first deployment took approximately four months. The data preparation took most of the time, once we got into Power BI we had most of our financial reports in a month.

Part of our implementation strategy was to get the requirements from the customer, documents, information on what they were using before, key performance indicators and other information. Afterwards, we started to build the data warehouse with the requirements in mind. We tried to mimic the reports that they were using before when we were building the Power BI reports. We tried as much as possible to have reports that look similar to the reports to meet our customer's needs.

There is a similarity between Microsoft Excel and Power BI. If you understand one it make the other easier to understand. If you grasp Excel, it is easy to grasp Power BI as a user. We wanted to make it as similar as possible to the Microsoft Excel experience, with the drill-downs and the pivot tables and so forth. I think with the matrix in Power BI, it is more or less similar, it is the same experience. To summarize our implementation strategy, it was to try to mimic the reports as much as possible and then add more features that are available in Power BI.

We pay on a monthly basis which is approximately $10 per user on the Microsoft Power BI Pro license. At the moment we are still down at 400 users, but once we reach 500 users, we will move to the premium edition. The premium is $5,000 for unlimited users. Currently, with the 40 users, the cost is roughly $500. 

There can be some additional cost, for instance, it was an internal decision to have an on-premises gateway set up with the standard Windows Server installed on it. We had to set up this server on our side, which costs us no more than $400. This was important because we needed something to allow our reports to refresh on a regular interval without people using the personal gateways.

I would advise those thinking about implementing the solution to compare different products to see what is on the market. They have to look at the pricing which is what we looked at initially, I think it quite affordable. Additionally, research the infrastructure that is required and the cost per user for the different BI solutions. Some of the solutions are cheap, such as Eclipse BIRT and Knowage, but it takes a lot of efforts to get your reports out with them.

With this solution, it is more of a drag and drop scenario. You have a quicker delivery time as compared to the traditional or the older BI solutions.

The biggest lesson I have learned with working with this solution has been in the area of data warehousing, you should develop something that is more like a star schema when building a BI solution, especially with this solution. It makes things much easier. We did not favour the star schema, we preferred the snowflake approach. However, data modelling is easier when you use the star schema.

I rate Microsoft BI a seven out of ten.

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.

Usually, when dealing with business intelligence projects with big data, all customers have Office 365 but within these licenses, Microsoft BI is often included.

The use case depends on the project. For example, in the logistics project, we need maybe four persons. For retail sales without stocks, it's a very easy project for us, but only for sales, and purchase orders, it's a standard part of the tool, to incorporate warehousing. Sometimes it's more difficult to clean the data if you have something like visualizations. It is often more difficult to understand what kind of data you need for the customer, or the strategy of the company who needs the information, to build a suitable solution. Customers often change their requirements. That's why Microsoft BI is more useful than traditional user tools, as it is flexible to changing requirements.

It's a great tool for visualization data, and it's free for engineers. Microsoft BI has a good online community. You don't need to be an engineer to use it. In Microsoft BI you can embed the visualisation and reports into your applications. Embedded items are much faster and cheaper to use. It's very easy to work with the customers using this kind of tool, rather than say, Oracle. I have used the personal edition, but some customers have been trained to use the professional version. Initially, I spent a lot of time learning the new system. As I was already experienced in other, similar technologies it was not difficult to understand the visualizations. I encouraged our clients to do more with Microsoft BI.

It should work faster and have more common languages so that you can use it more in different types of connections. It doesn't work well on big data. It is too slow. I hope in future it will be a comparable big data tool, such as, for example, Data Lake. It uses the DAX language, which is not used widely. Maybe they should develop this part of the tool to improve access to people who don't know DAX. Sometimes it needs to have a special configuration and hardware to connect to a data warehouse. So, interoperability with other systems could be improved.

I began using it a few years ago. I was involved in testing and last year, I was tasked with some large projects in Azure which included databases, a data warehouse with SQL, and Azure SQL. It is a cloud-based service, which means that a project is easy to use and design. You can use different tools for different things, but all the visualization in Microsoft BI is all in one tool. 

Microsoft BI is stable and works consistently well. 

Microsoft BI is a very scalable tool. You can start small and build up your project as you wish. 

I used Microsoft Azure support because we have a project. I have a good relationship with Microsoft. I don't have any problems.

It is easy to install Microsoft BI. You simply download and install it from the Microsoft Microsoft BI website, and it is available to download on windows. It can be downloaded and installed in 5 minutes.

Microsoft BI is free for the personal edition, but there is also a paid-for professional version. Setting up Microsoft BI is simple.

Oracle products are well-engineered but too heavy to accomplish small tasks. However, to use it for enterprise, you need to have a lot of knowledge about the different kinds of tools available. It has more flexibility but is more complex because it's designed for enterprise-level systems. Comparing this to Oracle which is at least 10 years old. Java is also old, but it's more structured. It's more proprietary.

Every month Microsoft puts in another update. We are likely to use Microsoft BI in future projects. Microsoft BI does not fit every business case, so for that reason, I would give it an eight out of 10.