Microsoft Power BI Reviews

We have some monitoring data from turbines, and we want to plot the data to monitor the health state of turbines in different time stamps. I tried to download some data from the Postgres database and then do some plotting with that. I also tried to link different plots with each other to filter them and things like that.

I liked that Microsoft Power BI handles a large amount of data. I can handle hundreds of rows from Postgres in a few minutes. I also like how it detects the relationship between the tables without explicitly saying that. It just detects the relationship automatically. That made it easier to work with the data.

It's not really complicated, but I didn't find the things I was looking for. The ones I used to work with within Dash are more open, and there are more choices. But with Power BI, there are only limited types of plots that I can use.

For example, when I wanted to put the plots in Power BI, there was no extendable space. You have a limited page where you can place a maximum of three plots in that, and you can't do more than that on a single page. You have to create a new page, a different page for that. That made it a bit annoying, and the filtering part is limited, with basic functions. If you want to make custom filtering or custom functions, you can't do that.

Suppose you want to code a plot, Python available. You can code the plot you want, and you don't have to use a predefined one. But when you want to plot it and you want to import like five or ten packages in Python, there are limitations. It doesn't support all the libraries that Python has. Microsoft BI only supports a few, like three or four libraries at most. When I want to use my old code in Power BI, it doesn't handle it, and that was also annoying.

In the next release, it'll help if they added a coding area where you are more open to make custom things. Especially for a developer, it needs to be improved. For a Power BI person, it's fine, I think, because it doesn't require much technical knowledge, but a developer will need it. Maybe they should create a space for that.

I have been using Microsoft BI for the last three months. 

It's stable, but it's so slow. Sometimes it takes some time to respond, especially when you put two or three plots with big data. It becomes very slow.

I didn't contact technical support as I used the support on the internet. I'm satisfied with the documentation, but I didn't find what I was looking for.

I was using Dash Open Source, but when I discovered that it would take a lot of time, I wanted to define a platform for that. So, Power BI was the solution. Now I want to try Tableau, but I haven't had a chance to do that yet.

I used a two months free trial to see if it had what I needed. I can pay later for a full license, but I don't think I will do that.

On a scale from one to ten, I would give Microsoft BI a six.

The ease of implementation and reliability of SQL Server Reporting Services far exceeded the solution originally implemented with Crystal Report. The Crystal Report Servers (3 of them) were crashing on a weekly basis at one of the companies where I worked.

We were able to reduce costs by consolidating the 3 Crystal Report Servers down to just one server running SSRS (with one backup just in case). The time it took to run some reports in Crystal were exceeding 5 minutes. The same report in SSRS not only was significantly faster (down to 30 seconds) and the licensing cost savings allowed for a quicker return on investment (less than one year).

The build in Report Builder for end users needs improvement. But for someone that has some training on SSRS, its very straightforward.

The solution was implemented and still in use to this day to my knowledge.

No. Following the installation guide was a help with setting up SSRS to use single sign on as well as SQL accounts. The overall setup of the server took about an hour. The conversion of over 200 Crystal Reports to SSRS took some more time but was done with one user and completed within 3 months.

No. SSRS has been rock solid and the server never needed rebooting unlike the Crystal Report Servers.

No. In fact we were able to decommission servers and switch to using a virtual server for SSRS.

Never had to use their support. But, the few times I have had to contact Microsoft, there were very knowledgeable and able to resolve the problem quickly.

9, see above.

Yes. We used Crystal Reports, see above.

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.

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.

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

We are using the product for some data tasks such as data binding and reporting. That's it.

The customization and management are very easy. 

We have found that the reporting and publishing are great. Sometimes people like to use the report for their teams.

The initial setup is quick and easy.

The solution is scalable.

It's reliable and the performance has been good.

The cost of the product is not too high.

You need to purchase upgraded support separately.

The marketing will need to increase more now. Power BI is a good product, however, from Microsoft, and I'm not getting too much marketing information about new features or anything like that. People don't know the capabilities and they really should.

We find the solution to be stable. There are no bugs or glitches. It doesn't crash or freeze. it's reliable.

The product can scale. It's not an issue.

You do need to purchases specific support in order to get a good amount of attention. If you are a company that needs 24/7 support, you need to pay for it.

The basic support is good, although it is a little slow. 

The Microsoft support model has it set up so that a first call will only get a user to their ambassador. Okay. Their ambassador will not have too much knowledge. They just identify what is the issue then they escalate to their team. Microsoft support could improve their services to attempt to have a first call resolution. Right now, in most cases, the first call resolution is not possible.

We did not use a different solution previously.

Power BI is a fast application. Therefore, the setup is very, very easy. You just license it, sign up, and you can use it.

The pricing is reasonable. It's not overly expensive, although you will need to pay for extra support if you think you will need assistance regularly.

We only looked at Microsoft. We did not consider other options. 

We are Microsoft partners.

I would rate the solution at an eight out of ten.