Microsoft Power BI Reviews

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.

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 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.

We use Power BI to manage all business indicators. Our customers' files, operations, number of transactions, satisfaction levels, history. We have a very powerful dashboard we use in Power BI and all our customers use it. I use it to drill down data from customers, to make decisions regarding business and other things. We are Microsoft partners and I'm a board member of our company.  

Power BI has a unique set of APIs to connect different databases on different systems. It means that I can extract data from a variety of sources and systems. It's very flexible. I work with numerous systems. We have new systems, super fast systems, and I have very old systems that run very well. They don't need updating because they run so well. Power BI has the power to connect with different sources, and I have a data scientist that orchestrates all that data because it's also about understanding the data, the application of intelligence and strategy on the data, and exposing it on the dashboard. 

I think that they should improve the mobile application that they have, it's very poor. We generally have a very huge area to cover, to move blocks and data. But sometimes I need a small set of data that I can see in my personal iPhone. But the iPhone solution, and the solution from any smartphone, tablet, etc., is so limited. It's particularly important now when so many people are working from home. Sometimes I need to reply to a call from my support or customer teams, they might be asking for a concession for a customer. I want to be able to look at the data on that customer. I take out my phone and I have no data. It's the worst. I think that if they improve the mobile solutions, it would help me and my team. 

I've been using this solution for five years. 

The stability of the product is very good. Microsoft solutions are very reliable. They're very mature and deliver reliable solutions. 

The scalability is good and powerful. Everyone in the company uses Microsoft tools, predictive tools. Microsoft 365, Power BI, SharePoint, Teams, Word, PowerPoint.

Technical support is a challenge, it's a complex question. Microsoft has different levels of support, it's all very customized. Different kinds and sizes of companies require different levels of support. The support is strong but it comes at a price. It's their business model. I can buy a number of hours from a specialist and get a real-time response.

The initial setup is quite complex and not easy to manage. You need a data scientist. It's not only connected to a data source, it's not only connected to an Excel sheet. For basic use that's okay but for corporate use to extract major features from the solution, you need a data scientist. It's expensive but a necessity and it's a very good investment for companies, because the data scientist enables the company to make better decisions and to help improve customer satisfaction.

It's very important to have a very good data scientist, without that it's very difficult. It's a key requirement. I'm only unhappy with the Windows software. I'm a Mac user for over 20 years, and, in comparison, Windows is bad. For us, SAP, Oracle, Salesforce, IBM are not affordable. They're interested in larger companies. In the last few years, Microsoft seems to be happier to go for the smaller companies too.

I would rate this solution a nine out of 10. 

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.

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.