Microsoft Power BI Reviews

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.

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.

In my project, I have an integration with Microsoft Power BI: I bring the lock from Azure Monitor to Microsoft Power BI, then create a dashboard from there. In the morning, we have a screenshot of the dashboard, and it can show you if there's a failure or not, based on the locking, so I combine the data which we get from the on-premises system, Azure Monitor, and other tools.

What I find most valuable in Microsoft Power BI is that it gives users detailed error messages. The lock I bring from Azure Monitor into Microsoft Power BI shows us detailed error messages which is helpful, and this is something you can't get from Azure Monitor, unless you do a custom query.

With Microsoft Power BI, I just need to put everything into a table, so people can filter the data, then they can see the error messages which they find useful. In the morning, if we see some failure in our solution, we can go to the "Detail" tab to see detailed error messages.

Microsoft Power BI can be confusing, because it has two languages that you need to learn if you want to use it. This is its area for improvement. First, you have to learn DAX (data analysis expressions), then you also have to learn Power Query M. You need to learn two languages simultaneously. If they can combine and make it just one language, it will be easier for nontechnical users.

We've dealt with Microsoft Power BI for six months.

Microsoft Power BI is very stable, and it's a nine out of ten for me.

I'm rating the scalability of Microsoft Power BI a nine out of ten. Its scalability is really good, because Microsoft has put in a lot of effort. They have a lot of connectors that let us bring in a lot of data, and even if we don't have enough data, we can use HTTP and REST API code to get data, so that's good.

The way Microsoft Power BI is used, particularly its Cleaner tool, should be improved. I just started using the solution and I use the PowerBI Cleaner with all the BI tools, and we need to have a dedicated data warehouse for that. PowerBI Cleaner would just be plugged directly to the data, and that's not good when you use your analytics solution, plugging it directly to the online transaction database.

We should have an OLAP (online analytical processing) software that's dedicated only for that solution, but we don't do that yet. If we have time, we should do that, but the PowerBI Cleaner would just stop at that stage, because it serves it purpose, e.g. it serves us what we need.

We use this solution for all of our self-service analytics. 

We have the analysis services on-prem and Power BI Pro in the cloud. We are using the latest version of Microsoft BI.

It's the analytic engine in terms of the interface on the Power BI environment, as opposed to pivot tables, and it's a mobile solution.

They have a new update every month. It seems to be pretty dynamic in terms of improvement every year.

Right now, their premium pricing is keeping us out of the premium market. The premium price per user just doesn't make sense for us, but we haven't reached the limit of 500 users to justify the premium.

The stability is good.

We could scale up to premium or Azure. We're fine.

I haven't really used it other than going on their documentation and seeing posts. I have never had to call for technical support.

The initial setup was straightforward. I would rate it a 5 out of 5. 

Deployment was completed in-house.

I would rate them 4 out of 5 for their current pricing. There are no additional costs to the standard licensing fees.

I would rate this solution 9 out of 10. 

They're a market leader. They're the best in class, so I would definitely use them over any analytic tool.

We are using Power BI for reporting.

It is very good, and it supports the Microsoft ecosystem, including Excel, etc.

We have been using it only for a couple of months, and we are at the beginning of our learning. The area of improvement is difficult to say. The handling of the workspaces can be made more granular for user access rights. It can be managed a little bit better in terms of the connection to Active Directory so that we have more granular access rights. I am not sure if this is really possible or if we can solve it differently, but we need a lot of workspaces, and we are not sure how we can deal with it from the access rights perspective.

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

It is stable.

We are not sure because we currently have a simple installation on the PC, but the idea is to scale it via Office 365 cloud implementation.

It seems suitable for small, medium, and large enterprises. It should be able to scale up. Based on the marketing slides, it should be able to handle all kinds of enterprises.

We have not had any problems, so we had no requirement to use technical support. 

It is quite easy. You just need to install a program and use the connectors and drivers, and that's it. 

I did it myself.

We are end-users, and we don't take care of the prices and accounting. We get a product and pay the fee to our internal service provider, but its price should be reasonable. Otherwise, they wouldn't have bought it.

We are not very experienced in it. So, I don't know if I can recommend it, but we are using it because it is very good.

I would rate it an eight out of 10.

The solution is very powerful and very flexible. 

It is very easy to set up and you can connect it to multiple systems very easily.

They keep on upgrading, performance-wise. 

Power BI is very fast; they have improved Power BI a lot in general over time. YOu can see the difference. 

The stability is great and continues to get better and better.

The pricing is pretty good.

They should provide some kind of extra visual. There are a lot of third-party companies that provide these visuals, however, it would be better if, instead of relying on a third party, they could have their own. We should have by default in the package itself, some good visuals.

Technical support could be a bit better.

The performance could be enhanced in the sense that there is a limitation of the volume of data that it can hold. 

While they have some different options out there, they did not improve anything when you connect to any dataset, when you have to import. You need to connect online, meaning live.  

You cannot create so many things on the Power BI side, such as adding a new column, which is not possible in your live reporting, direct query option. In contrast, with the import method, you can do so many things. They need to improve on the direct query option side.

The product is stable. I have seen a lot of improvements in the stability of their application lately. If you compare what's available now to the last three to four years back, you can see it's more stable.

It's scalable and it scales quickly. Nowadays, being on the cloud, expanding is very easy.

While support is okay, they need to improve it a lot. Of course, they're improving as we speak, yet, I would say, if you can ask me the ratings, I would still say it's still rather low and good - not great.

I'm also familiar with SAP, which doesn't scale as well. SAP also is much more expensive. SAP is a big product, whereas Microsoft BI is much smaller. They only overlap in terms of the analytics cloud and the SAP goes above and beyond and offers many, many more things. 

The pricing is fair. They give you many options by splitting up the licensing. They have multiple types of licenses out there based on your usage. You can increase your pricing if you use it a bit more, however, it's still quite reasonable as compared to SAP. 

We are a customer and end-user. We are not a Microsoft (or SAP) partner.

I would rate the solution at a seven out of ten.

We are providing BI services to clients in India who are using Microsoft BI. We are able to provide the clients with data-driven decisions by the use of the reports that we are creating using Microsoft BI. The reports are usually graphical and intuitive.

When we are introducing Microsoft BI to our clients, if they're familiar with Excel, the transition phase will be much easier for them. They can easily switch from Microsoft Excel to Microsoft BI. The core foundation or the base technology is the same in both tools. There are a few limitations in Microsoft Excel, and this is where Microsoft BI comes in.

Microsoft BI can improve some of the visual level filters or visual functionality, that are available in other BI tools, such as Tableau or Qlik Sense.

I have used Microsoft BI within the past 12 months.

The stability of Microsoft BI is stable.

Microsoft BI is a scalable solution. Here in India, it is a popular tool for people to implement.

The client that we are working with has approximately 500 to 600 users.

The support from Microsoft is helpful. If you're facing any sort of issue or error, you can raise it to the Microsoft BI community.

We work on a very concise team of three to four members for the deployment. We will be requiring only a data engineer, Microsft BI developer, business analyst, and project manager. 

If the user requirement is high, we can increase the number of members in the team. However, if you have a team of four, then you can deploy the project. A minimum of four people is required.

For its maintenance of Microsoft BI, you require only two people. If there are some backend data issues, then you will require a data engineer. However, if the issue is related to the frontend or BI report, then you only need one developer for that.

My advice is for the companies who want to make data-driven decisions or to share the report with the security feature in it, they should opt for Microsoft BI services.

I rate Microsoft BI a nine out of ten.

We use Microsoft Power BI for production testing. We're not using it for production automation. It's being used for testing and testing themes. We have a testing requirement, so we want to mimic automated workflows on production to be validated on regular intervals, and this is how we use this solution.

One valuable feature of Microsoft Power BI is that it's user-friendly. It also has good connectivity between multiple source systems. It's also a good data analysis tool.

The UI looks awkward once the graphs have been generated in the console. This is what Microsoft can work on. They should make the graphs more user-friendly, because other parts of Microsoft Power BI are user-friendly, but the graphical representations aren't.

We've been dealing with Microsoft Power BI for five to ten years now. We were early adopters of cloud solutions, e.g. AWS and Azure, which we adopted from the start. We are a complete cloud company.

Microsoft Power BI is a stable solution.

I find Microsoft Power BI scalable.

It's very easy to deploy Microsoft Power BI.

Microsoft Power BI has reasonable pricing.

We evaluated Microsoft Azure.

We use Microsoft Power BI. We also use AWS, but what we primarily use is Microsoft Power BI.

We're using a combination of deployment models for this solution, because the model will depend on the customer need.

We don't procure this solution and other Microsoft tools for ourselves. It's the customer who procures them, and there is not much issues for us to contact support. We are a Microsoft company, e.g. we are partners with Microsoft, so we have good rapport with them.

We recommend Microsoft Power BI even for large enterprises. It's a tool that could be used even by smaller enterprises and by end customers.

My rating for Microsoft Power BI is an eight out of ten.

The use case is mainly creating the dashboard for the organization's data transaction and its data project. We create dashboards on top of this data for the top management.

I am using the latest version.

The solution can be deployed on cloud or on-premises. It depends on what the client wants and if it's available.

We have around 10 to 15 people using this solution in our organization.

Microsoft BI provides insights about the normal day-to-day work from operations or different transactions. It depends on the organization's business. It provides insights for top management to help them make more accurate decisions.

The user experience is easy. Users get familiar with it quickly.

Sometimes while developing, the front end is not easily customizable and it has limitations. We cannot go and do any UI we want. We have to stick to the limitations of the product.

It's user friendly, but it does have its limitations. A designer cannot dream of anything they want to do and just go and do it. The dashboard has to look a specific way. If we can make the front end more flexible, that would be good because it's on the server. Clients are asking for a better UI, but it has its limitations.

I have been using this solution for five years.

The stability is good. The solution is being used daily, on a moderate to high level in our organization.

The solution is scalable.

Technical support is good.

Sometimes I work with Qlik Sense, which is another BI tool.

Initial setup was straightforward.

Our technical team completed the deployment. It was all done in-house. Deployment only required two people.

I would rate this solution 8 out of 10.

The solution is reliable, maintainable, and scalable. It has good performance. The security is good. The only thing would be improving the front-end limitation, which prevents us from designing a UI that can match what the client wants. Be aware of the product's limitations so you don't promise the clients anything that the product itself cannot do.

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 deal with government agencies that compile stats and data. For instance, the use cases for the department of education are all school-related. They need to know the number of schools in a given region, attendance, etc. They also need to monitor monthly changes in the data, so they run analytics to see where enrollment and attendance are dropping or how schools are performing. 

Recently, we developed an application for the South African statistical bureau. They use Power BI for their dashboards to show precisely how many people were counted in which areas, and where they have the challenges. We have different use cases depending on the project and the client's requirements.

It's deployed in the cloud because Microsoft has switched to offering Power BI as a service. Most of our clients are doing all of their business intelligence primarily on the cloud, but we still have clients that are running SQL who prefer to do their own intelligence internally instead of using cloud solutions.

The one feature most of our customers like is data visualization. When we were doing BI directly from SQL, most users found it challenging to create their own reports. Power BI has self-serve analytics that the end-users can do themselves. On most projects, people are primarily using data visualization and self-serve analytics. 

There are probably several other useful intelligent tools included with Power BI that we never use, but they might be good for other use cases. For instance, if you're selling consumer products, you might benefit from Power BI's ability to track sales performance. But our government customers mostly use data visualization internally to make decisions. 

I'm not a heavy Power Bi user. I use it as my CRM, and it gives me all the information that I need. I haven't found anything that isn't useful for what I'm working on at the moment. Maybe later, I might think of something and find that Power BI doesn't have. It's quite an improvement compared to using Microsoft SQL for business intelligence. 

We've been working with Power BI for many years. Before we started using Power BI, we were on SQL SSIS and SSRS. We've been in the BI business launched back in 2003. Most of our business was business intelligence even though we didn't have a lot of analytics. 

We do quite a lot of data warehousing, business intelligence, etc., but when we started, we were mainly dealing with data manipulation. I would say it has been more than 15 years.

I don't have any complaints because we used to be a partner of a company that set up our environment. They are a sales partner, and our sales are very good, but there were always issues with the technical support. At the moment, I would still recommend everyone to move to Microsoft Power BI regardless of their environment.

It's highly scalable and stable. 

One of the vendors we used to work with was Qlik, but we found that Qlik's support wasn't as good as what we're getting from Microsoft. With IBM, the biggest challenge was that companies didn't have the analytics skills to use their solution. Customers would complain that it didn't do what they wanted it to do, but it is not the tool. It's the skill that you have on the market. 

Microsoft made sure they certified competent solution implementers. It was great. We were privileged to be one of those companies that Microsoft picked, and they helped us train some of our technicians to be adept at some of these solutions.

All of our technicians are certified, so Microsoft refers certain organizations to us locally for help implementing their solutions. We have a solid technical team, especially around the Microsoft Power Apps, including Power BI.

Deploying Power BI is straightforward because they've made it so easy with cloud solutions when they came out with the Microsoft Power Apps. Power Apps includes Power BI, Microsoft Flow, and some others. I do everything myself, so I can do my workflows in the background of Power BI on all the applications even though I'm not an everyday applications development person. I haven't done development in years.

With Power Apps, you don't necessarily need to install anything because it's already there on the cloud. You customize it and point it to your data sources. Within a couple of minutes, you're done. Then from there on, you can customize your reports however you want. I think it's effortless to work with.

The number of people needed for deployment depends on the size of the organization, and the scope of what you're trying to do. You may have a small organization with fewer than 500 people, but they might deal with a lot of data. That means the project is going to be very big. 

Conversely, you could have an organization with about 2,000 people, but they are not a data-intensive organization. Then you will need just a few people. For much larger organizations, you'll find that you might need to have the whole applications development team of between five to 10 people for the actual implementation, including your project manager, business analysts, and various technical support personnel.  

For a big organization, you would maybe have five technical guys, including your lead as well as two senior technical people and two juniors. Then as the project grows, you can add four more. At the end of the day, we're looking at about five to 10 people for a bigger project.

However, it's not the same as an on-prem deployment. Most of the work is customization because everything else has been done on Azure. Generally, with things like your standard Power BI deployment, you need just about five people. That includes the project manager and the business analysts plus two or three technical people. 

You do an installation and all the customization a client wants, but from there on, you run out of work to do because everything is running smoothly. I've heard some say that it's making people lazy because if you do everything correctly the first time around, you won't have anything to do for a couple of months except maybe change a couple of things for users. From the technical point of view, you find that you have absolutely no work to do until you move on to the next client. The deployment is quick versus how long it used to take as before we went on to Azure.

You don't need a large team for maintenance because somebody else takes care of it. At most, you need two or three technical people and then an account manager. Probably about three. You're not managing the service or the infrastructure. You are just managing the environment.

The management is much easier compared to how we used to do it before. You needed maybe six or seven people, with some managing the environment and others the infrastructure. For example, the department of education has a user base of more than 500,000 people, but the whole environment is managed by two people. With the Azure infrastructure, everything running in the background is taken care of. 

The return on investment with Microsoft is quite good. The value of the product is far higher than the price you pay. The most significant added value with Microsoft products is their ease of use. If you buy things like Power BI, you become a Microsoft partner and gain access to some customer training, so you learn to optimize everything related to Power BI.

They go the extra mile. They have the training online, so when you get stuck, you can go through the training and know exactly where you made a mistake instead of going out to a training institution and spending a lot of money for precisely the same training. The licenses you pay over five years don't even make a dent in some companies' budgets.

For instance, one of our customers was running a Software AG solution analytics solution. Even though we are a Software AG partner, we suggested they go with a different solution because of their budget. We implemented Power BI, and now they don't want to go back to the previous product because they're saying this one is much more user-friendly than before.

Most of the customers we work with go for volume licenses. Some pay annually or get a more extended license for three to five years. All of the licenses are on an annual basis, but Microsoft will amortize it to an extent. If it's five years, they'll include the possible interest they might have the following year. Ideally, their licensing scheme is an annual license, but they make it easier for some of our clients to take a five-year license but package everything inside for them to buy the license for five years.

I think that's helpful because most government institutions budget on a five-year basis. They have a five-year plan broken down into an annual OPEX. The CAPEX will be five years, and everything else would be OPEX. Most of these licenses get put on an OPEX whereby the client pays once. Then for the five years, they don't necessarily have to worry about anything with Microsoft.

These licenses are in US dollars. With a long-term license, the client is unaffected when the exchange rate goes up. However, if the exchange rate goes down, you don't get refunded from the excess money you've paid. I guess that is a risk you take in business.

I would rate Microsoft BI nine out of 10. We buy from a couple of vendors, and Microsoft is always at the top of the list for ease of use, simplicity, and cost. I've used the other vendors, but I'm still in love with Microsoft.