Microsoft Power BI Reviews

During my internship, I used Microsoft Power BI to create reports for a project we were working on. I also made a dashboard to help a company grow its business.

What I liked most about the tool is that we can use text queries to create projects and modify columns according to our needs. There are hundreds of YouTube courses on how to use it. 

I found data cleaning in the solution to be quite difficult. If I could add a feature, I'd include Excel's Flash Fill function. This allows you to set a formula for one row and column and automatically apply it to thousands of rows, making data sorting much easier.

I found the tool to be a stable product. One of my favorite features is connecting a SQL database to the tool to generate real-time reports. I was part of a group of 80+ students, but only five of us, including me, were offered internships and could use Microsoft Power BI.

I haven't contacted the solution's support yet. 

Installing Power BI is easy—there are free and paid versions available. I used the free version, which you can download from the Microsoft Store and install, similar to installing an app on your phone.

I used the tool's free version. 

I'd recommend Microsoft Power BI for report generation - it's great software. I rate it a nine out of ten. 

I use the solution in my company for data analysis and visualization.

The advantages of Microsoft Power BI stem from the fact that it is really easy to use. The drag and drop facilities provided by the product are good.

I only face problems when I want the product for free to help prepare for some of the demos for my company.

From any improvement perspective, I want the product to be made available to users free of cost. The product should not require any subscriptions.

The stability and scalability of the product can be better.

I have been using Microsoft Power BI for six months. My company is a customer of the product.

Stability-wise, I rate the solution a seven out of ten.

Scalability-wise, I rate the solution a seven out of ten.

I don't have any experience with the solution's technical support. I rate the technical support a five out of ten.

Neutral

The product's initial setup phase was easy.

I rate the product price an eight on a scale of one to ten, where one is low price and ten is high price.

The product improved my company's decision-making project when I was involved in a project where I had to do an analysis involving LinkedIn and other social media accounts.

The product's maintenance phase is easy.

My company can share and manage Microsoft Power BI across different teams in the company since we have only opted for the subscription for a single person. In my company, we do exchange web URLs, and it helps us exchange reports with different teams.

My experience with the real-time dashboard updates of the product has been good.

I rate the overall tool a seven out of ten.

In January, I successfully published my application on AppSource, specifically targeting retail customers. Recently, I received positive feedback from a customer, which was truly gratifying. It seems that my application is Microsoft's preferred choice as it effectively addresses the majority of customer requirements and is tailored to their specific requests. 

Apart from retail applications, I have also developed solutions for BigChange, an organization dedicated to driving significant changes. Additionally, I have worked on creating reports focusing on production efficiency within my company. These reports have been well-received and have provided valuable insights. Lastly, I have recently worked on an application that involves managing IT resources and has developed a multi-dimensional model including SSIS and Power BI.

For the last project, I worked on creating data flows and implementing incremental refresh functionality. However, there was an issue we encountered regarding the date field in the tables. The existing portal dates were incorrect as they did not reflect changes in the records. To address this, we collaborated with the developers to introduce an additional column that accurately captures modified data in the system. This improvement has proven to be significant, and it can be implemented using the pro license, rather than relying on the premium license, as the premium license covers different aspects.

The Pro license offers great features such as incremental refreshing, which is highly beneficial. While it doesn't include direct query capabilities, I believe that many customers don't actually require direct query functionality. 

Currently, the developers in my company are busy adding a column in the API as part of our transition to BC Start. Our intention is to gradually migrate our customers to SQL Server, and that's why we are using the app.

In a simplified manner, when working on-site, you cannot directly connect to the regular table without using APIs. That's why the APIs need to be modified to include an additional column, making it suitable for incremental refreshing. Apologies for any disruption caused, but I hope this explanation clarifies the situation.

They find Power BI's data pull mechanism to be sufficient and cost-effective, especially considering the stability it provides. In comparison with other solutions, Power BI stands out as a fantastic choice. Therefore, I would definitely recommend sticking with the Pro license.

I believe there is room for improvement in terms of authentication and certain functionalities in Power BI. For instance, adjusting the width of columns is not easily done, as there is only an option to enable or disable automatic adjustment. 

This can be a significant drawback for clients who desire more flexibility.

Additionally, changing styles and formatting options for numbers require external tools, which can be inconvenient and time-consuming. Ideally, Power BI should incorporate these features within its platform to enhance user experience and eliminate the need for external tools.

I understand your frustration with the lack of automation and dynamic features in Power BI, particularly regarding the assignment of dynamic titles and content titles. While there are some options available for creating dynamic titles, they may not fully meet your specific requirements. It would be ideal to have more flexibility in manually assigning the desired typography for each call and dynamically setting content titles. Although it is possible to find workarounds for these limitations, I believe Microsoft will likely address these issues in future updates to improve the user experience. Despite these shortcomings, Power BI remains a powerful and highly capable application, and I would rate it an eight out of ten.

I have a strong belief that within the next couple of years, or even sooner, significant advancements will be made in Power BI. These advancements will make it even more powerful and I am confident it will become truly exceptional. I have complete faith in the future development and potential of this platform.

I have been working with Microsoft BI since the start of 2020.

I am working with the latest version.

Microsoft BI is very stable.

Microsoft BI offers scalability, particularly with the availability of premium capacity. With premium capacity, whether it's per user or a dedicated resource, Microsoft BI can effectively handle increased data volumes and accommodate growing user needs. 

Microsoft BI offers scalability in specific areas, but it is important to note that scalability options are limited to certain aspects and may come at a higher cost. For instance, the premium package, which starts at around $5,000 or more, provides enhanced scalability features. However, if you opt for the per-user licensing model, the scalability may be constrained as it is tied to the number of licensed users. Therefore, in terms of scalability, the per-user option may have limitations compared to other packages.

I wrote to Chris Web, and he replied to me immediately. He is the principal program manager at Microsoft.

I have him I have him working And, usually, I don't contact them, only when it is something serious. top expert and experts, and they reply, you know, has been one for us. It's great

In my professional experience, I have primarily worked with AS (Analysis Services), Power BI, and SSIS (SQL Server Integration Services).

Last week, I worked on creating SSRS (SQL Server Reporting Services) reports and integrated them with SSAS (SQL Server Analysis Services). Additionally, I hold a Microsoft certification in this field.

The initial setup is straightforward. It is very easy to set up. it is very intuitive.

Perhaps it's because of my experience and expertise in the field that I approach things with caution. I don't take things for granted. Just because I obtain a certain result doesn't automatically mean it's correct, as there may be errors that are not displayed.

It's important to carefully check the measurements and ensure their accuracy, especially for beginners who may not be familiar with these nuances.

Maintaining the system is not difficult due to the availability of the admin platform. When it comes to permissions and access, it becomes straightforward as long as the customer's requirements are clear. 

You can easily define the level of access they need, whether it's building, reviewing, sharing, or restricting data access for online viewing. Depending on their specific needs, setting up gateways and configuring other settings is also simple. 

It's important to have a clear understanding of their security requirements and engage in discussions with the customer to determine the best approach. 

Often, customers may not be fully aware of what they want to achieve, and it's our job to help them identify their needs.

Especially for clients, it's important to understand that achieving the desired outcome is not as simple as just completing the task and generating the report.

There are several factors and considerations that come into play. Careful attention needs to be given to the creation process by different stakeholders if you truly want to achieve an exceptional result. 

Even small changes, such as removing certain elements from the selection or adjusting formatting, can have a significant impact on the report. Users may perceive the tool as being the same regardless of these details, but the difference between a subpar report and a high-quality one lies in the expertise and knowledge of the creator.

There are various options available for creating reports, particularly focusing on online reports. However, the foundation of the process lies in Power BI Desktop. Whatever we develop in Power BI Desktop can be published and accessed through a unified platform and tool. 

Data flows enable us to make necessary modifications, similar to working with Power Query and related functionalities. Personally, I find working with Power BI Desktop easier due to its comprehensive features and user-friendly interface.

You can gather data from various sources, including data flows, RBI databases, and SharePoint, among others, and then create and publish your report. While you do have the option to connect to online sources directly, I personally find that working with local data feels faster, at least for now.

Microsoft BI is considered to be competitively priced when compared to other similar solutions in the market.

I haven't had the opportunity to work with other tools as I found Power BI to be excellent. No one has specifically asked me to explore other tools.

However, I did purchase some tools on my own for personal learning purposes, particularly for tabular data. I may consider exploring other tools after June 15th, once I have completed my Microsoft exam DP-500 for Synapse.

Power BI is a complex tool that should not be taken for granted.

Its capabilities and functionalities are multi-layered, and the more you delve into it, the more you realize how much there is to learn. 

It can be both challenging and fun to explore the different features and unlock the full potential of Power BI.

As a BI developer, I joined the company without prior experience in BI. Since December 2021, I have been working on establishing a BI deployment in collaboration with a partner. My main focus is to create and enhance internal and external applications for app stores. Currently, my task primarily involves developing a new deployment strategy.

I would rate Microsoft BI an eight out of ten.

Enterprise reporting and digitization of dashboards using Microsoft Power BI, SSRS and Azure Reporting DB by integrating several applications to establish single version of truth.

Microsoft BI stack is very easy to use and most of the developer versions are free such as Power BI, DAX, SQL Server Development Edition. This helped us quick prototyping to generate value of data resting in silos. 

What I like most is that I can do everything in Power BI that I can do in Excel. It is very compatible with Excel tools, and anybody who works with Excel can learn and use Power BI quickly. 

Writing formulas and data transformation are good features.

The only challenge I have found is that they do not have a Mac version of Power BI. They should have versions for both Apple and Unix because you cannot install the desktop version for these operating systems.

In the future, I would like to see them add more AI and machine learning features, as well as self-service analytics.

You can use R and Python, but it would be helpful if they had some no-code machine learning options that you find in other tools.

The UI/UX can be improved. Products such as Tableau and QlikView are very good in terms of the user interface.

I have been using Microsoft BI for five years, on and off.

I have not found any issues with respect to stability. Microsoft has invested a lot and they are continuing to invest in Power BI.

Given that there is a server version for services that can be used to implement and roll out reports at the organizational level, it's scalable.

In my current organization, I am training 15 people on how to use it and I am looking to expand to 50 users.

Microsoft support is quick. We also have a dedicated partner for support, and they are good.

Positive

Prior to incorporate Power BI in the stack, we were using Microsoft SQL Server Reporting Services(SSRS) only. They do not have any visualization interface, but you can do static reporting. This is the reason that we are switching. Probably, we will use SSRS and Azure SQL at the backend, but there won't be used as the visualization tool.

For visualization, we used to use Excel. Which not reliable. 

The installation is easy. The download takes perhaps five minutes, depending on the bandwidth. Overall, it can be downloaded and installed within half an hour and no training is required.

The desktop version is used for development and the cloud version is used to submit a report. Essentially, it is Power BI Desktop and Power BI Services. The desktop version is what is on-premises.

You can deploy yourself but of course, in an office, you require an administrator.

The cost of this product is very low, at approximately $8 or $9 per month for a developer. It is the cheapest of all of the visualization tools. They have a 30-day trial available for you to try it.

For personal use, this product is free to use.

Tableau is a little bit expensive, although it is good if they want a very sophisticated solution. Both Tableau and QlikView are a little better in terms of the user interface.

You need a technical team to operate the solution. You need people for the administration of the data connection and data integration. They should be skilled in SQL, data management, and so forth. Typically, these are data engineers.

We plan to continue using Microsoft BI. We are onboarding and implementing organization-wide for our long-term strategy, and the entire organization will be using Power BI.

My advice for anybody who is considering this product is that it is easy to learn, especially for somebody who is good at Excel. Other tools are easy to use as well but if you are a Windows user then Power BI is a good option.

I would rate this solution an eight out of ten.

The main use cases that we see for Power BI are financial reporting, network analysis, structured and unstructured reporting, and self-service. We have just recently completed a pilot phase of Power BI and Qlik Sense, evaluating them against each other. In this pilot, we have had about 50 users in our company use Power BI, but eventually we envision having up to 300 concurrent users.

There is a lot of variety in Power BI. In particular, the visuals are quite rich and the feature set has been growing rapidly in the last two years. Possibly the best part for me is that there are a lot of ways to connect with data sources.

There's also support for integration of Microsoft 365, which enhances collaboration with all these interwoven tools including email, Teams, SharePoint, and so on.

My main complaint is that the error messages need to be made more clear. Currently, they are either too generic or outright misleading, and finding the real problem is like searching for a needle in a haystack.

Along with that, whenever you encounter an issue and you need to do some troubleshooting, it is really hard to isolate the problem. For example, is it related to your data? Is it related to your report design or your construct? Or is it related to the visuals? Power BI is really not that helpful when it comes to troubleshooting.

My suggestion is that there should be some kind of design validator that says, "Hey, warning! This report (or this set of queries) cannot run fast." There may be a long list of restrictions you need to take into account when it comes to optimization.

I have been using Power BI for nine months now.

It's not exactly as stable as I would like. We have had several service reliability issues as well as service degradation issues, which of course are typical to a sales based context. During those moments, though, it has been pretty inconvenient, especially for the users. Luckily we have not been confronted with that situation in production yet, as it was a non-production pilot setup.

It's not easily scalable for us, in the way that we consider scalability. You have to be careful when considering an upgrade to your capacity plan, which comes with an extra cost. Alternatively, you need to simplify the reports that you have designed with your plan and eventually remodel them to accommodate further usage without unnecessary cost.

Even then, you are confronted with various product limitations or scalability constraints. For example, there is a maximum amount of queries that you can launch simultaneously. Ultimately, you need to remain cautious because it's not a one-size-fits-all approach especially when it comes to the price.

I've used the Power BI support from various locations multiple times and I am satisfied with the help I received.

The current deployment we have relies on SAP BO (Business Objects) which is a vintage version and an aging solution, over approximately 10 years old now. SAP does have a more innovative replacement product, of course, namely SAP Analytics Cloud, or SAC.

We discussed our needs, requirements, report layouts, and so on with SAP and following further deeper analysis, SAP came back and confirmed that they could not realize it in the short term using SAP Analytics Cloud. It would require much more effort, including the integration of a data warehouse and more to reach our goals. And hence, as per SAP's recommendation, we dropped that scenario from our considerations.

It's a sales-based offering so, by nature, it is simple and straightforward. However, the integration options are quite fuzzy and relatively complex when you start to connect to the variety of data sources.

It took a relatively long time of about three months to get everything up and running. The setup took longer than expected, to be honest, but the reason is not only related to the product as such. It was also related to the existing knowledge and capabilities of the IT delivery provider, where multiple gaps were identified.

I designed the implementation of Power BI myself as the enterprise architect. I've been supervising the entire deployment and together with Microsoft product support, we've encountered various issues and discussed various situations on how to manage Power BI.

An example of the trouble we faced was that there were various middleware components that we needed to deploy as well. They were deployed but they were not up to the standards that I had identified. We had to upgrade and then patch them up to avoid that happening again.

As of today, we have a team of eight staff, including managers, engineers, and administrators, who handle deployments and maintenance.

Our license is paid yearly and we have found that we have to be careful not to over-extend our usage in order to avoid upgrading our capacity plan.

Whether I can recommend Power BI depends on what you are searching for with this type of tool. It is not a one-size-fits-all solution.

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

We are Microsoft resellers.

We use it for clients to extract and analyze data from ERP systems. Then, we basically put it in on-premise Power BI, and once we have the reports and visuals that we want, we publish it to different members of whoever has access to see the reports. Basically, we publish it to their Power BI in the Cloud.

For one client, it gives all sales reps across all geographic regions access to sales data, so they know who's purchasing what product in what part of the country, and that sort of thing. It shows them overtime when sales are high and low, as well as what types of customers are buying. We occasionally connect it to external data. We link it to some demographic data, such as population figures in different provinces in Canada, to see how sales are doing.

It is beneficial. It's one of the applications we use for a client's sales reps all over the country to get all kinds of sales data. It also benefits them. They can ask, "Why isn't this customer purchasing this specific product?" So they know which customers are genuine or who are purchasing and may try to push a different line with them. It provides a wealth of useful information to the salespeople.

It gives us, the ability to do a lot of analysis quickly, similar to ad hoc analysis. People want to know, for example, which customers are purchasing which products over what time period. It's very simple to make visuals for them. We create a matrix that resembles a spreadsheet and then link it to various graphic visuals, pie charts, and other types of charts. They also get a visual sense of what's going on. Those features are fantastic.

One of the more difficult things to do is to export some of the data from Power BI to Excel. It is getting better. It's better than it was six, eight, or nine months ago, but it's still not quite there. They could probably improve that a little bit. 

The only disadvantage of how we're using it is that it can be difficult to get the data into Excel at times. A lot of users are very familiar with Excel, so having a seamless interface into Excel would be a big plus for a lot of people, in my opinion. Otherwise, it's an excellent product.

I have been selling Microsoft BI for two years.

I am using the most recent version.

It can be deployed both on the cloud and on-premises.

For us, the stability has been great. We have no issues with the stability of Microsoft BI.

I believe it is a scalable product. I'm aware that they have other products on the market, but I haven't tried them. To analyze data, it appears to be scalable to fairly large businesses. Scalability is quite good.

It is not a single organization. It's amongst a few clients of mine. I would estimate the number of users to be about 20, 25, or something along those lines. Their roles vary a lot. Several users are salespeople and people in purchasing. There are also people in management who use it and people in the accounting area as well. There are also one or two more technical users who use it to export data to Excel PivotTables. These are the people who make use of it.

For one client, it's very extensively used. Others, I wouldn't say that it is used as extensively. They could use it a lot more.

I have not had any interaction with technical support.

Before using Power BI, we used a lot of Excel, Power Pivot, and other similar tools. We transitioned a lot of our data models from Excel and Power Pivot to Power BI, including the PivotTables. It was a Microsoft solution. It was Excel, from Excel and Power Pivot to Power BI.

The initial setup went quite well. It was a fairly straightforward process. There were no major hiccups.

It took approximately four to five hours to configure.

I have one client who has an administrator who updates the system. He updates the product and his data on a regular basis. I believe the data must be updated once a month. Other clients' updates are handled by me.

We did not need assistance, we completed it in-house.

Yes, I believe so. I haven't actually measured it, but based on one particular client, I believe their company is expanding at a rapid pace. I believe a large portion of it is or a good deal of it is based on the information they receive. I believe there will be a return.

It's straightforward licensing. I would guess we pay $300 to $400 per month for everyone or something along those lines.

Depending on where they're coming from, one thing is that if you want to get deeply involved in it, you have to learn the programming language, which I believe is DAX. It is not difficult to become involved in and learn. Microsoft, in my opinion, has done a good job of making it simple. That's one area I believe people should look into if they want to learn more than just the fundamentals of the DAX programming language. Which we have done in part. Again, we are not experts, but we have looked into it.

I would rate Microsoft BI a nine out of ten. It does almost everything we require.

We are using this solution for analytic dashboards.

The solution integrates with other Microsoft solutions very well. 

When it comes to security Microsoft BI can integrate well with Microsoft Domain Services, you are able to make it as secure as you want.

There are useful visualizations available in the dashboards.

If you are having millions of rows of data or you have a large database, Microsoft BI's performance depends upon how powerful your hardware is. When I am handling large amounts of data I do not use Microsoft BI or Tableau because of this, I use D3.

In a future release, they need to have better integration to allow any visualization that is done in other solutions, such as D3 or Tableau, to be able to be imported in Microsoft BI easily.

I have been using Microsoft BI for approximately five years.

The solution is stable when the database is reasonably sized. If you have large databases of 20 million rows it can begin to have difficulties requiring a purchase of more hardware.

The scalability is good. If you have a direct query, Microsoft BI can run on billions of rows of data.

Microsoft BI is available to the 70,000 users in my organization.

This solution is used extensively because everyone has access to it, not because it is the best.

The support from Microsoft could improve.

The solution is easy to install.

We did the implementation of the solution.

For those customers we have that use Microsoft BI on a dedicated server, we have a technical team that does the maintenance.

I have evaluated Tableau and D3.

I would recommend Microsoft BI over Tableau if you are comfortable with Microsoft solutions. Additionally, understand your use case and choose the best solution that fits your needs.

I rate Microsoft BI a six out of ten.

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

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

In general, we are pretty pleased.

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

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

The initial setup is straightforward.

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

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

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

The solution could be quicker at rendering data.

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

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

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

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

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

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

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

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

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

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

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