Microsoft Power BI Reviews

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.

We have a few projects. We're using the solution primarily to develop a modern sitemap.

The product has a very defined, well-prescribed format to it. It's easy for everyone to use for the most part.

The training is pretty good. It's well-described so that users can navigate the solution easily and follow the correct steps to initiate tasks effectively.

The user interface is pretty good.

The technical support on offer is excellent.

We've found the scalability to be quite good.

The solution's initial setup isn't too complicated.

I need more time with the solution. Right now, I can't think of any features that are missing from the product.

The integration with other solutions could be improved for reporting aspects. There are some reporting features in Tableau that we need access to and it would be ideal if there was a function between the two for data integration and data manipulation, with the final representation of the report available on Tableau.

I've been using the solution for a year or more at this point. It hasn't been too long.

So far, the solution has been largely stable. However, I'm still exploring the solution and testing it against my requirements. The stability hasn't quite been proven fully just yet.

The solution is pretty scalable. It meets all of my client's requirements. I'm able to make changes and expand if I need to. It's pretty simple to scale it out as necessary.

We deal, for the most part, with medium-sized companies. We don't really deal with smaller organizations or bigger enterprises.

I'm extremely satisfied with technical support. It's been excellent so far. They are responsive and knowledgeable and I always get my questions answered in a timely manner. I have no complaints about their level of service.

I've also worked with Tableau and SAP products. We use them all currently.

The initial setup is not complex in any way. It's quite straightforward. It was installed quite easily onto our system. We didn't run into any issues in that sense.

I'm using the calculator version of the solution.

We use both the cloud and on-premises deployment models.

We are Microsoft partners. We're not just users.

Overall, I would recommend the solution. We do have other plans to use other BI solutions, however, we haven't really focused on that just yet. So far, this product has met our needs pretty well.

On a scale from one to ten, I'd rate the solution at a nine. We've largely been happy with the product and its offering.

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. 

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.

Microsoft BI can be useful for several scenarios, depending on your end audience, or what they're looking for. Depending on your creativity, imagination, and what the tool allows you to build, you can create a lot of cool things with it. You can build a lot of very elaborate and dynamic reports for example. The most important thing to consider is to understand what your audience is looking for. The development side of the tool is not the problem.

The usability of the tool is very simple. If you know the basics, it's fine. Even if you don't have the basics, there is a lot of self-service documentation available which helps to guide the user to start to use the tool, and how to navigate through it. 

There was also a new feature added last month to help new users practice using the system by providing an example data set to experiment with. Power BI server can be run on-premise so that your reports are available locally. Or you can have a premium version, including all your reports on the Cloud. It can be determined by the number of refreshes required from the reports or can depend on the volume of users that are consuming the reports.

The tool is very flexible so it allows for creativity. Power BI allows you to incorporate Microsoft Visio diagrams and other graphics from Microsoft tools. You can also integrate third-party visual graphics created from other tools, such as R or Python. It is useful to be able to obtain additional charts or different types of graphics developed by a third-party tool. This gives you more options for your end solutions. However, for some third-party tools and graphics such as Zoom charts, you have to pay for those separately. This is useful if you really wish to mesmerize your audience with dynamic, interactive visuals.

Alternatively, if you just want to use what is available to you, and with a little bit of UX/UI knowledge and creativity, you can build really cool stuff with it. For example, you can have dynamic dashboards on a screen that is connected in real-time. Users can interact directly with the data, so when they click the mouse, they can see the data changing. There's a lot of things that you can do with it. Let's say you develop a report, to put on a big touchable screen. Let's say the CEO is presenting to someone, and he's on a big screen. As soon as he touches a dialogue or a graphic on the screen, all the data changes. 

As an example, in CNN news, or any news, where they are presenting, and there are some dashboards and reports, journalist clicks on the screen, and everything changes instantly. That's what Power BI can do. If you have touch screens Power BI allows you to interact with your data.

I think that the product would benefit by increasing the range of visuals and graphics readily available, as opposed to using a third party included as part of the product. One way they could do that is for Microsoft to buy some of those third party companies, as they are specialists in visual creation, and they are making money from that. However, I understand that perhaps Microsoft maybe doesn't want to invest in that side of the business. Perhaps it is a financial decision. I would say that if we can have those additional visuals built into the product, it will be great. Alternatively, in the future, there should be an additional tool there that allows you to create your own visuals. That will give users more flexibility. 

It would also be useful for users with little experience in coding, or other Microsoft tools such as Excel. For example, let's say, you are a random user, and you're just looking at the computer for the first time. You open Power BI, but you know you can go to an Excel file and connect to that Excel file from Power BI. This is very simple and intuitive. So, once you have connected to the data, you can see your fields on the right-hand side, and all you need to do then is to drag and drop the fields you need. You can then select a relevant visual or graphic, and put the information alongside that visual, and then you have the visual and the data created as one item. This is very useful and dynamic. This would also have the other huge advantage, in that it would be a cheaper solution to use. I would like the ability to reuse connections. 

For example, if I created a connection to an SQL server, and I published my report using that connection, and then shared my report, it would be useful to be able to reuse the existing connection to the SQL server. In this way, I can reuse the existing dataset to create another report. I believe this is already the subject of a support ticket. Say I then wanted to reuse another connection from a different connection, say Oracle, to use in the same report, I could use the connections to those two sources and build the report. If I already have the sources online, and available for me, it would make sense that I could reuse them. At the moment, you can only reuse one data source. You cannot reuse more than one data source, at least if the data sources are online. One workaround would be to access each data source in turn, to obtain the data for the report. However, from October 2020, when using Excel driven reports, it is possible to reuse data flows or reuse the data component, from Power BI in Excel. So Microsoft has already implemented it for Excel, but it is still in the preview features. That will help a lot in financial areas. This could also impact company sales forecasts and sales.

I have 10 years of experience using BI tools, like Tableau, Power BI, QuickView, and MicroStrategy. I have a background in technical architecture but my main expertise is in BI tools. I use Power BI. It's a business intelligence tool that helps you develop and create reports that you can connect to various data sources. Then you can slice and dice, and build what you want to build from there.

Microsoft BI is stable.

The product is scalable, and new updates come out every month.

Microsoft Technical Support is very good. If I need their assistance, they will liaise with me. They are very flexible, useful, and very friendly. They are very open to helping you out. So depending on how you escalate your call, and say it's a high-priority issue they contact you very fast. They have support lines globally. So if I'm in the Czech Republic, I may be contacted by someone from Romania, or from India, or another zone. It's fine, if, for example, I'm not English, and I need to speak to someone who speaks Spanish, they put me in touch with someone who speaks Spanish. There is a lot of available support for Power BI, and they have their own Power BI page called Power BI Support. Power BI issues are registered on that page. Support usually fixes the issues within the given timeframe. The other good part about Power BI is the huge Microsoft community that it is there. So you can raise tickets and use the community which is on the same page. Sometimes the community helps you find your solution. So, it provides two ways to access support solutions.

It's easy to install which helps new users to the product. The installation process is easy. You can install it from the Microsoft store, or you can go directly to the Microsoft portal, and download the version that you require. It keeps historical versions available in case you need to test a different version. The advantage of the Microsoft store is that as soon as you install it from there, it always keeps you updated with the latest version. Also from a Power BI service point of view, you have several capabilities. The learning curve comes in when researching the different features, and what is new in the product, as well as what is going to be provided in future versions. The advantage of Power BI is that every month you have something new provided with the update. For example, you may have a new connection, additional visuals, or use new narratives.

We have 8,000 Power Bi licenses in our organization, so it is widely used. Setup is easy, and the cost is economical. You do sometimes need to pay additional costs for third party products which "plug-in" to Microsoft BI.

I would give Microsoft BI a 10 out of 10.

I take care of business transformations in the company, which includes solution transformation, and so on. We have a range of products that are legacy products. They are fairly old. We are substituting them with new age products, and one of them is Power BI. We are using its latest version currently.

The drill-down capabilities and automatic charts are the best ones. The visualization is also very good. In terms of visualization, no competing product, such as IBM Cognos or any other product, has the same capabilities.

Microsoft BI comes under pressure when there is a lot of data to be crunched. It gets slower and slower, and the functionality becomes a bit of a problem. The performance goes down with data being fed into the system. The infrastructure requirement also increases if you have to increase the performance. This is the area that can be improved in my opinion. Initially, the product is good, but over the years, when data gets accumulated, it becomes a problem unless the old data is kind of archived and is no longer shown on the visualization.

It has a feature by using which a user can query for a report through simple questions to a bot. So, if I want to look for the customer share of revenue by geography, I just simply state that in the chatbot. If I wanted it in a pie chart, then you say, "Please show it to me in a pie chart." It comes out well for basic charts. This feature should be improvised more so that people can very quickly get customized reports on the go.

I have been using this solution for a couple of years. 

Its scalability is good. The only issue is the performance that degrades when more data comes in, but when it comes to scalability within a particular level of data, it is really good.

I don't know. I am not technically so much involved in the day-to-day side of this.

The initial setup is a process by itself, so we have to take external help in terms of implementation. In terms of various reports and other things, I don't have an idea about the complexity of the implementation because we took expert advice, and an external consultant implemented it for us. I would guess that it is a bit extensive and needs a lot of work to be usable.

I would definitely recommend Power BI for those entities that are not complex. Unless and until there is a very high volume to be handled, I believe Microsoft Power BI is the best solution to go for, particularly when somebody buys a stack of Microsoft products, which includes Office, SharePoint, and so on. The whole Microsoft Office Suite is a brilliant product in its entirety, and there is good and easy integration with SharePoint, etc. This is a nice feature that other products don't have. There is a stack of IBM as well, but it is not as good as Microsoft.

I would rate Microsoft BI an eight out of ten. I am pretty happy with this solution, and the two points are down because of the performance issue and probably the cost.