Microsoft Power BI Reviews

To gain insights into our sales and financial aspects, we use the Power BI solution, which provides us with valuable information and analytics.

One of the most valuable aspects of this tool is its ease of use and the ability to easily share information with others.

There is room for improvement in terms of pricing for the solution.

We use Microsoft BI in our organization. I have been working with it for two years.

We have implemented the Power BI Pro solution in our organization.

I would rate the stability a nine out of ten.

I would rate the scalability a nine out of ten.

We have plans to increase our usage in the future.

I would rate the technical support a nine out of ten.

We use fast track support and it is very good.

I have been acquainted with SolarCloud for three months.

I haven't worked directly with the solution, but I downloaded the eBook to learn more about it.

Due to our extensive experience with the tool, the initial setup was straightforward and uncomplicated.

We have seen a return on investment.

The pricing for the solution is relatively higher compared to other alternatives.

I am a cybersecurity analyst.

Knowing the numbers and having comprehensive insights are important for our organization. It holds significant importance for various teams, including finance and other departments, to make informed decisions and drive overall growth and success.

I would rate Microsoft BI a ten out of ten.

We use the solution for data analytics, so we use it to manage data governance, manage the data for certain organizations, and present it in a way that is more advanced than the manual reporting that was being done before via Excel. Now it's kind of interactive. It's more modern, so there are a lot of new features. It can be integrated with more BI tools also.

I've been in different organizations with different setups. I've experienced using on-prem, cloud, and hybrid.

Considering that it's Microsoft, it can be integrated with the Power Platform, which is also Microsoft-based, like SharePoint, Power apps, Power Automate, and Power BI, which is the most user-friendly. It can also be integrated with more systems or domains that are non-Power BI domains, so it can be connected using API, SQL, or Azure. You can connect into your local premises, or database, et cetera. There's a lot that you can use Power BI with, and I think it's the number one BI platform in the market.

Based on my experience, everything's good in Power BI. Consistently, it's being updated every month. There's a new feature that is being added to the platform, but I think one thing that can be improved is with regard to the error messages. When there is a problem, the error message is not specific about what's causing the problem. Maybe they intentionally generalize it because there could be a lot of causes. From an improvement perspective, I think if the Power BI developers of that platform would really focus on being more detailed and specific on the error messages, it would help a lot of developers troubleshoot and maintain the report ECT or the dashboard ECT.

There needs to be more specific error messages. You encounter problems normally for the development part and maintainability part, and there are some issues that you or any developers would encounter. It's resolvable, but it would take some effort to really dig in and investigate. Some of the messages, for example, will say that the main package is missing, which could mean a lot of things. It could be a formatting error, it could be a file type error, it could be a transformation error on the helper file, et cetera. If there was a sub-description of what that is, it would be a great improvement on Power BI.

I have been using this solution for three years.

It is very stable. It's been around for more than five years. It was released to the market around 2015, it was conceptualized in 2011, and consistently it's been at the top of the market, against all its competitors, because it's a Microsoft product. I think the secret there is in the way they update their report consistently. The platform is being updated every month, so all the needs of the developers are being met.

It's scalable. You can be a junior developer and work on your mini projects or your supporting mini team, and you can create your own presentation with Power BI, as simple as that. You can also handle multi-database projects and huge enterprise level data and combine all the different systems, get all the data, and put it into Power BI. Power BI has the capability and the power to cater that.

There are times when I can't resolve certain problems, and of course I'll exhaust all my resources. I would talk to my colleagues as well. Aside from that, there are BI groups or BI developer groups on Facebook, wherein I just post a question and then we all help each other. But if there are problems that can't be resolved, we go to Microsoft and create a ticket.

You don't need any technical support for BI because you have a very big community. There's Google, and then there are a lot of people who are very willing to help.  Adam, from Guy in a Cube, is very popular. He's part of Microsoft, and he's popular on YouTube. He answered one of my questions, and it's a very hard question. I think a lot of the problems that I encountered were resolved.

I have also used Active Directory. I was a service desk analyst, which is a level one IT. For Active Directory, I use that to support the organization's directory, IT concerns like internet error issues, their profile, if they can't access a certain website, their password needs to be reset, et cetera. 

Power BI has different kinds of setups, so one setup would be connecting to an SQL server database. I have experience connecting to SQL databases, and I do basic SQL coordinates because normally it's done in collaboration with SQL administrators.

I'm a seasoned BI developer, so it's easy for me, especially if it's not a very complicated project. There are different setups, depending on the project and depending on the organization. There are really complicated ones. For example, if you are going to connect to SSA live connection, a cube has to be built, there will be expenses, et cetera. There are requirements that would involve different teams and different people because of the expenses, et cetera. There are also simple ones like when you're just connecting to Big Data, or SharePoint, or SAPI, or local, or databases. It depends on projects, but for me as a seasoned developer, I think it's going to be easy.

I would rate this solution 10 out of 10, against all the other competitors and as a BI tool.

It's a 10 because of the price. It's not that expensive compared to other BI tools. It's also with regard to maintainability. It's easier to understand, easy to manage, and it's very flexible. You can create projects, you can create a website, et cetera. It also has accessibility. It can be integrated with a lot of systems and applications. It's the leading BI tool in the market.

We use Microsoft BI to fetch data from one server in SSMS to another server.

I find many of the features of Microsoft BI valuable, in particular, I use the data flow tasks, look up and incremental loading of data. They have also introduced Hadoop in the control flow task.

I have created particular dashboards for a specific project so that I can show the clients the data related to their needs. Being able to show them a visual of the percentages in a pie chart has been very effective.

The only concern I have faced with Microsoft BI is the time it takes to find out an issue and rectify it.

In my last project, I worked with SSMS as my source and Oracle as my destination. This meant that there were certain compatibility issues between the two. I recommend for incremental load that Microsoft BI can include one task to overcome this concern.

I have been working with Microsoft BI for six years.

Most of my experience was with MS BI, with Power BI the difference is mainly in the report sections. It is more user-friendly compared to SSRS.

If you are not comfortable with SSIS, SSRS, and SSAS, there are many tutorials available for MS BI, especially if you are new to the solution.

I would rate Microsoft BI an 8 out of 10.

We are impressed with Microsoft Power BI. The tools seem very easy to use and very interactive. People love to see us reinforcing it, especially the top management. They're okay with that. We are exploring Supersets. 

It's user-friendly.

The most important thing is the developing version is free. Only the online version you have to purchase. That is one of the key advantages we are getting. We can reduce the internal costs that way. 

It can take in all kinds of data to analyze. 

It's very comparable to other solutions on the market.

The initial setup is relatively simple. 

Power BI doesn't support some open-source data sources that are new, such as SnowSQL, Iceberg, or ClickHouse. Those are the data sources I didn't find in Power BI. Those data sources cannot be connected to Power BI. You need third-party support for that. This is the one key problem I have with Power BI right now.

We have various departments in our company. While some departments have used it for maybe two years, my particular department has only used it for about a year. 

This is a stable product. I found, once, in the middle of the work, it shut down or something. However, it is stable. When I put some of the reports in the Power BI cloud version, everything worked fine. I was able to get the report data. 

As long as I can scale my data, I can scale the product. I just put my data into Power BI and do what I need to do. 

The data solution we have is open source. The whole team is working on it, and that's a team of 15 people. The number of people that are actively writing and reporting is maybe six or seven people. Maybe two or three people seeing are seeing report deposits and getting the outcomes. 

We don't have any technical contract with anyone, whatever the problem comes up, we can solve it ourselves. In my country, I personally don't know anyone who is actually, is smart enough to show us anything extra that we don't already know.

We are exploring Power BI, Microsoft Synapse Analytics, and some BI features on Azure. 

We previously used Oracle BI. It's a good tool. Oracle BI is more for the enterprise, big enterprise, for big control of data security and can get into how you control your people, who can see what, et cetera. The downside is, it is very old. You will not get the very latest tools or visuals in Oracle BI. That, we can easily find in Power BI.

The implementation process is relatively easy. One the junior developer can learn the process in maybe one or two days. He can catch up on Power BI and how it works. It is straightforward, I would say.

We do have a license for the product. 

We purchased a few licenses for the top bosses who want to see the reports on the run, on their own PC, laptop, or mobile. We purchased a few licenses for the developers as well. other than that, no need to purchase a license.

We have both on-premises and cloud versions. The advanced team who has actually been using it for around two years have an online version. They're putting the data online and showing it. I cannot say exactly what they do. However, on our side, we do not use an online version. We have the three versions that we are using now that are on-prem. 

Overall, it's a good solution. However, there are a lot of other really great similar solutions you can use as well.

I'd rate the solution at a seven 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.

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.

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.

We have SharePoint in our company and then we just wanted to visualize that list and it connects to the Check Point list.

We like the drag and drop interactability visualization. We really like that. It's user-friendly.

If I have to update data automatically, where I have to pin the gateway, it doesn't update. There is a scheduled refresh functionality so that it refreshes automatically, but I find it very hard to make it work. Even though it's supposed to connect seamlessly, it's a bit complicated to make it refresh automatically.

My company has been using Microsoft BI for a few years but I've been using it since January 2020.

It's very stable.

I think it's very scalable. I don't even foresee that as a challenge. 

We have five or six users who view the reports. There are other departments who might be using it as well but we have five or six in my department. It's expected to rise to 15, 20.

The users are managers who want to look at some of the resources.

I haven't interacted with Power BI before. If I get stuck at someplace, I just go online and I search in the forums and I find my way.

There isn't really a setup involved. It's just download Power BI desktop and publish it.

We have a premium Power BI license in-house that's quite an expensive license. It's $10 a month for four users and then I think 35,000 at the premium rate.

Ensure that you use Sharepoint. If you are within the Microsoft system and want to have a similar experience to Microsoft Teams, then Microsoft Power BI is a very good solution for that.

I would like to have the ability to run the scheduled refresh for R and Python on the server. Right now, it's not possible.

I would rate it a seven out of ten.