Microsoft Power BI Reviews

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.

I'm a call center consultant and I use Microsoft BI to receive in-depth metrics. I download the metrics from the contact center and then I can figure out what's going on in the contact center. Additionally, if we integrate it with other tools and databases, et cetera, we can receive a better understanding of what is happening. For example, we had a customer that made products for Costco and Walmart and if they had an engineering issue or a problem, they don't find out about it until they saw the orders from the engineering team explaining what the issue was.

We added a screen to the agent's desktop and listed the model numbers of the products and then used Microsoft BI analytics to see what particular problem happened to what product. The executive could drill down and hear the calls as to what the customer was saying about the issue.

The executives liked the data, the engineers liked hearing what the customers were saying about the certain product that had an issue.

Microsoft BI is easy to use and to design. I found Microsoft BI a lot easier than Tableau.

You can set Microsoft BI up for administration to use it and then you can set up views for your end-users to look at. For example, if you are a report analyst you could have your marketing person wants Microsoft BI to report on how many widgets the East Coast sold in five years, if you set Microsoft BI up the right way, they can retrieve that information themselves. You save manpower from your IT staff.

Microsoft BI is a lot easier to analyze data than with other solutions, such as Excel.

I am taking a course to be able to use the solution better. Some aspects of the solution are not straightforward.

I have been using Microsoft BI for approximately one year.

I have found Microsoft BI is stable. 

I have not had any issues. I am a new user myself, and I typically suggest an application that I have found good and then somebody else that I work with, would set it up.

The solution has been scalable for what I use it for.

I have not used technical support.

I have used Tableau.

The initial setup is very easy because it is on the cloud. You only need to have your database and connect it to Microsoft BI. They have different connectors in order to make it easy to do.

I have not had a customer suggest the solution is too expensive. There are licenses to use the solution.

The solution has all the features I need, I do not use large data sets.

I rate Microsoft BI a ten out of ten.

We're a retail hospitality chain spread throughout India, operating over 330 outlets across the country in various formats, ranging from a coffee chain to fast food restaurants through our in-house bespoke brands. All these brands run out of travel hubs like airports, railway stations, and highways stops. We needed a solution to manage both the multiple SKU levels and in terms of individual dynamics, the profitability of each store. We constantly track the various types of back-end raw materials, specifically on our prediction modeling where we use Power BI. We also use Power BI analytics to drive those results with regard to the day-to-day dashboarding, reporting in terms of collection, on sales trends per hour, manpower and the like. We are customers of Microsoft and I'm the CIO. 

I like that the interface is very fluid in the sense that you can upload via Excel or you can attach via connectors, any software you like.

The challenge of this product is in truncating the table data. It would be great if Microsoft would include a naming convention which has the advantage of enabling a VLOOKUP on top of it, so two tables can be merged more seamlessly. Currently, the time it takes to merge two tables in Power BI makes the entire analysis quite complex because it requires common numbering in one table and then creating another common indicator in another table in order to merge the two. It wastes precious time. 

Secondly, while they talk about visual analytics, sometimes the challenge is when you're looking for more in terms of geovisual analytics, such as city maps which requires a functionality whereby you can upload transactions. For example, if I want to visually present my data on an airport map, showing which stores are generating what revenue dependent on the traffic heat map, I am unable to do that because I cannot upload drawings. Ideally, I'd like to show each store as a bar map with waves explaining the sales in each location. It allows me to pinpoint which locations are more profitable. 

I'd like to see a degree of variability so I have the flexibility of putting those variable components in my predictive modeling, and I can get a feel for the trends. It requires a common input database. You can do it in Excel, but you can't do it in Power BI, which I find surprising.

We've been using this solution for nine months. 

The product is fairly stable, it doesn't get too many upgrades or updates from that perspective so it's fairly straightforward in terms of implementation and our entire ecosystem was on Microsoft which helped us. The only area that can be problematic is when you're trying to create relationships between two databases and you're trying to link it with your Power BI solution, sometimes that mapping takes considerable time.

The solution is scalable. We are a cluster of eight legal entities and we've been able to expand to all of them. We started with 20 outlets and today we have 350 outlets. We are more granular and today Power BI allows us to drill down to the last voucher. We have around 14 users from the finance and operations teams.

We haven't needed to call Microsoft, because we worked with one of their gold partners in India. So we are on an AMC model with them in terms of manpower. If there are any problems or upgrades we need, we reach out to the partner. 

The initial setup was straightforward for the simple reason that our entire ecosystem was on Microsoft and we use Azure Web Services in terms of hosting. We split the entire project into two parts to simplify things. The first part was more about the granular analysis of sales and various other elements, which took considerable time due to the many external stakeholders involved. Phase two was relatively simple, because it was department specific and we created a split team, which led to the creation of a better platform.

Licensing is on an annual basis. We have a complete Microsoft Ecosystem license. I think there is room for improvement with the licensing, specifically during the pandemic when it would have been reasonable to offer a discount. Many other companies, SAP and Oracle, for example, gave waivers to the MSME sector. Microsoft traditionally is used by smaller or medium-sized companies so I was expecting some sort of discount on the pricing, but unfortunately that didn't happen. We managed to avoid an escalation in cost, but frankly speaking, a discount would have been much appreciated.

It's important to understand your entire ecosystem in terms of your tables; the kinds of tables your back-end database has and the elements of analysis that you are looking at. If you are looking at predictive modeling, you need to have at least two to three years of data, because that allows you to define the trajectory of the predictive modeling. Otherwise, it doesn't serve any purpose. Secondly, be very specific with your implementation partner, as to how you'd like a particular visualization tool to look, otherwise you may not get what you want. Finally, it's important to invest in people and create a center of excellence made up of people who know Power BI well, or who will get trained and certified on it. You'll need an in-house team which can do the small tweaks and changes as you require, otherwise you'll get stuck each time you need to do something.

I rate this solution an eight out of 10. 

In general, we use it to have access to the data that we have processed from the HCM system and also to deploy it to the teams. Because it has low-level security features, I can guarantee that only selected people have access to the information seamlessly. We don't take a lot of steps to create, for example, different profiles and ensure the data security that I need.

It is on the cloud because we have pro accounts. Usually, we have the desktop version for designing and using ourselves here, but when we deploy this, it is usually on the Microsoft cloud; it is not on-premises. We are using the most updated version because they release monthly updates.

The querying capabilities are the most valuable because they allow me to build many automations. We have many workflows and many databases that we work on a daily basis. They need to be updated quite quickly. In order to not to take much of our time doing these updates manually, I have set up these automations using the systems. The process is just to ingest the data and reprocess it. Every time I click a button, everything is updated in almost real time.

It is by far the easiest system not only for querying but also for data modeling, data visualization, and deployment. It is light years ahead of Tableau and even Microsoft Excel to do these kinds of things. It is very easy to use and set up, and it has a lot of videos on the internet.

I would like it to be a little bit more secure when I'm using the design feature on my desktop. For example, to have the ability to set up security passwords for opening the file. Currently, they don't have that.

Tableau, for example, has a visual way of doing data processing steps, whereas the Power BI system still has some code, although it is very low code. It would be great to have the kind of view that Tableau has.

I have been using this solution for around two and a half years. I am currently using it, and I have also used it in the previous company.

It is very stable and very reliable. It is by far the most reliable system I have used for deploying many things.

It is very scalable, especially because the pricing was great. Right now, they are integrating a lot with Microsoft Power Apps and the Power Platform as a whole. Power Ultimate and other things are being integrated into the system as well.

In my previous company, more than 200 to 300 people were using it on a daily basis. In my current company, we have less than ten people using it because we are still a very confined team.

The technical assistance is great, and I have never had any problems with them. Their support to communities is also great. I would rate them a ten out of ten.

The initial setup was very easy. It took a little bit less than a month to get everything designed, tested, and deployed after we got the licenses.

Its pricing is great.

The first piece of advice is to become very clear about licensing and the data governors. Always get the licenses and get them right. You must also be clear about who is going to control these accesses. The second piece of advice is to understand a lot about the low-level security to create profiles and data access features to allow the specific data to be seen only by a specific public.

Currently, in my organization, the greatest challenge is getting proper licensing. We have a little bit of resistance from our IT department who would like us to use Tableau more. It is not Microsoft's problem. It has more to do with the vendor of choice of the company, and they say that we have to use Tableau, but I don't want to use Tableau.

I would rate this solution a ten out of ten. It deserves this rating.

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.

I mostly work in the oil and gas industry. Microsoft BI is primarily associated with surveillance, optimization, product, and forecasting-related items. While I am not currently using Microsoft BI, I have prior experience, and in my current position, I am guiding the team on a larger scale. I don't use it myself frequently, but I am the lead for that team, and when I do use it, I use it for reporting purposes.

Microsoft BI has a multitude of additional features. Overall it's an EDA tool, from which you can extract, transform, and load data. You can pull reports, visualize them in real-time, and connect them to a variety of other data sources.

When I compare other analytical tools to Microsoft BI, I believe Microsoft BI is far more accurate, and the frequency is also better.

It has additional features, which are very much useful. The most important thing I like is that it is just a data platform connecting to the overall process and it can be utilized in any sector.

Integrating it with the physics build model or the engineering model should be included. When we use engineering models linked to Microsoft BI or Salesforce, the engineering models are from a third-party application.

I have been working with Microsoft BI for the last three and a half years.

We are using the latest update.

I have used it both on-premises and on the cloud.

In terms of stability, I have seen some cases where it is difficult as well as some cases where it is very easy. Overall, it is a stable and reliable product.

It is easy to scale Microsoft BI.

We have a larger team. Microsoft BI specifically, is not limited to any subset or any team. I believe we have 1,000 plus users in my company currently who are using this application.

I have been in touch with the technical team, but not specifically for Microsoft BI. Based on my experience with Microsft technical support, I would rate them a four out of five.

Technical support is pretty decent.

I use a variety of tools, including Salesforce, and I have developed a number of Python-based tools.

The initial setup was simple. However, when I did it the first time, it was complex. Once I understood the process it was simple.

My field was small due to the type of setup required. I scheduled it for one week, during which we also tested.

Definitely, it requires maintenance in terms of quality checking of the data, as well as whether or not the run times or schedules are working properly.

I had some assistance when I deployed the first time, but I am now able to complete the deployment on my own.

In terms of licensing, I've never worked on the contractual side of their license. However, I believe that the number of licenses currently in use is appropriate for our organization. It also adds value to the team. I have never worked on licensing, but I have heard that it is reasonable.

I have not used it on the mobile app. I'm not sure how Microsoft BI works on a mobile app. 

Mobile apps are sometimes third-party apps that are difficult to configure and use. As a result, mobile apps are something that will be required in the future, upcoming data transformation.

Before implementing Microsoft BI or any other analytical tool, we must first understand the domain. Basically, how the data is linked, what data you want to transform, and what output you need for the finished product. Then you proceed with your deployment in a sequential manner. It will be very simple.

I would rate Microsoft BI an eight out of ten. I haven't explored many other items that are feasible or possible, or the analytical part of Microsoft BI's functionality, which I haven't personally used, so there's a gap. Otherwise, I would have given it a ten.

Currently, I'm working with an insurance company. Whenever they book any kind of policy, we have a certain rule where we have one predictive loss cost against that particular policy. For example, if you buy one pen, we can predict how much, if the pen got broken, how much premium you're going to pay for this particular pen. Based on that, we identify the risk area and we control the entire policy and the policy sourcing. This is the one interesting use case where we are basically controlling our entire government force.

Microsoft provides internal training and they have open forums. Normally, if we have any query on any part of the product, they'll be very responsive to our needs. 

The alert features are great.

The initial setup is pretty simple. It's a straightforward setup in our industry in particular.

The solution can scale.

We've found the solution to be stable. 

I learned data management and also visualizations on this product, and they are very interactive. Those two things are very strong points for Power BI.

There needs to be more flexibility in terms of handling the data. Data computation is not very good in PowerBI. It's a little bit of a heavier tool.

There are some limitations with the data models needed to build the report. I can't use multiple data models. You can handle lots of data, with higher volume in other tools.

We need some kind of flexibility with the objects, the graphs. We need more control over the data manipulations and data designing parts. That is a big thing from my side.

Some sort of SMS feature that could send alerts would be great for teams that work in the field. It would help, for example, if you forget to access the report. If it was over SMS it would be a game-changer.

I've used the solution over the course of the last year.

The solution is stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The product can scale. It's not a problem.

We currently have 300 company employees using the solution.

We're getting pushed to use the solution even more. In the next few months, we're likely to increase usage.

Technical support, in terms of security, is good. Microsoft Power BI is very good at responding and the follow-ups are very strong. I'm happy with Microsoft.

I also use SAS Visual Analytics. It's a little bit cheaper, however, it's not that much different in terms of price.

It's a straightforward setup. The deployment took hardly one day. It was quite a short period.

The implementation part varies, however, in our organizations, the deployment is very easy as we have a central team who looks at all the deployment parts. Normally we follow the standard guidelines and then we push further. My internal team is controlling this kind of information. It's much easier for me that way. 

It's easy for my industry. I don't know about the other companies, how the deployment part will go. I can only say that, in the insurance sector and in my organization, it's very easy.

While it depends on the team and the size of the deployment, in our case, we only needed one person to handle the initial setup. He was an operations person.

I have an internal team who deployed the entire thing. We did not use any integrators or consultants. 

We've seen a good ROI. It's a reporting tool that we can use on different platforms like mobile. We can integrate the report with the website. It provides good accessibility. You can access it from anywhere, anytime, and it's scalable. 

We're charged a monthly subscription fee of 500 rupees per person.

I explored Tableau, however, I found Power BI more stable.

I'm not sure which version of the solution we're using. It's above version six.

We are using on-prem. All the development is happening in the development environment and we are pushing to production. It is completed on Azure infrastructure. While production is on the cloud, development is happening on the on-premises server.

Microsoft is a very desirable product and they already have provided extensive support. 

I'd rate the solution at a seven out of ten. If the data models were more robust, I would rate it higher. 

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.