Microsoft Power BI Reviews

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.

The visualization part and its inclusion in a cloud-based application are valuable features. 

The solution is somewhat costly in comparison with MSBI tools. 

In MSBI, when it comes to mobile and maps-related applications, we are always looking for some support with the reporting tools. Once we click on the region, then automatically it goes to the two area maps. Based on the map, it will reinforce our data values. There is constant change involved and new updates and enhancements are coming out as needed in new versions. 

The solution performs well and is stable. 

The scalability is very good and use of the application is flexible. 

We can create certain tickets, contact them and explain our requirements and they will look into the issue and help us to find a workaround for us to implement. They will address the issue in the next version. 

We are very satisfied with their support. 

We are implementers of this solution and maintain the visualization on the reporting parts, as well as fulfill the business requirements. 

The solution is less expensive than other PowerBI tools, but more so than those of MSBI. 

The solution is less expensive than other PowerBI tools, which is why most people go with it, although it does cost more than MSBI tools. It has good feasibility for fulfilling one's business needs. PowerBI is very strong in the market at the moment and we are creating visualization that works. It is a stable tool, as well. 

While PowerBI is cloud-based, it can be used both on-and-off-premises. MSBI can also be implemented on-premises. PowerBI mostly involves visualization. 

I rate Microsoft BI as an eight out of ten. 

Compared to Cognos, Tableau and Power BI are pretty fast. 

The initial setup is very quick. Connectivity, installation, and configuration are pretty fast and seamless compared to Cognos. Power BI eradicated dependency on a framework model. 

Power BI is cheaper than Tableau and Cognos.  Power BI Desktop comes free and the Pro license is $10 per month whereas Tableau desktop would cost you $70 per month. Cognos is mostly suited for large and medium size companies 

For someone who is new, I think that Power BI can be a little complicated. Overall, on a scale from one to ten, I would give Power BI a rating of seven. 

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.

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.

I use Power BI primarily for generating reports, analyzing data, and supporting data-driven decisions across various functions within the organization.

The solution's data integration capabilities are beneficial because they allow us to seamlessly integrate data from multiple sources, simplifying the analysis process and providing a comprehensive view for better decision-making.

There is room for improvement in terms of customization and configuration options, particularly for more advanced users.

I have been using Power BI for quite some time now.

The product is scalable. Expanding its use across different teams within the organization has been relatively easy.

We are seeing a good return on investment with Power BI, particularly in terms of how it has streamlined our reporting and analytics.

The solution's costs are quite reasonable given the range of features provided.

We receive real-time reporting with Power BI, which greatly impacts our decision-making process by allowing us to respond more quickly to changes in the data.

The data visualization tools particularly strong. The ability to create custom dashboards and reports tailored to different

It is highly user-friendly and cost-effective. However, it may lack certain advanced features present in other solutions.

Overall, I rate it a seven out of ten.