Microsoft Power BI Reviews

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.

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.

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.

I largely work with the engineering and R&D teams. Typically, the data insights and data teams use Power BI for business-related data visualization. However, for me and my customers, most of the tools like Power BI and Tableau are used to do data visualization for the engineering data. That could be even predicting the behavior of a machine, meantime between failure, or tracking of an IoT center data or even the behavior of the fleet management and things like that. In all the engineering use cases where we need data visualization, we use this product.

We have 16,000 to 17,000 or more people who are trained in insights and data. This group uses all the data analytics tools, data visualization tools, BI tools, and all the other tools from a business use cases perspective. It could be market basket analysis, sales reports, and all those kinds of other business reporting.

The solution has been stable.

We've found that the scalability meets our current needs.

It's good for data visualization and analysis. 

My understanding is that the initial setup is pretty easy.

Technical support has always been great for us, as strategic partners. 

There could be more scalability.

Microsoft should offer additional features for visualization and have additional features for slicing and dicing that data. Those would be good to have.

We've been using the solution since Microsoft introduced the solution to the market.

The product is more or less stable. Power BI doesn't have any problem with the stability aspect.

The solution can scale. It meets our needs.

We are dedicated partners. We have a couple of Microsoft architects that are dedicated to us. We have fairly decent support. I don't have any problem with them. If you ask a commercial end-user what kind of Microsoft support they get, in that case, you might get a disappointing answer. For us, we are satisfied.

I work with a services company and we work with a lot of different customers. So depending on which customer, what is that ecosystem, we'll end up using a lot of different BI tools. That includes both licensed and open-sourced software as well. For example, we've used Tableau and Microsoft Power BI.

I am personally not involved in the implementation process, however, my understanding is it's not that difficult to set up.

I don't oversee day-to-day operations. I just have a team that does that for me.

I cannot speak to the exact pricing. Sometimes we, for example, resell some licenses. We are strategic partners with Microsoft. It entirely depends on how the contract with the customers is. Sometimes the customer procures all the licenses and gives them to us and sometimes we resell the licenses. It completely varies from customer to customer.

We have a strategic partnership with Microsoft and a lot of our customers also are Microsoft shops.

We use both cloud and on-prem deployments. It's a mixed kind of a situation, depending on the customer scenario and situation. We have some implementations that are on the cloud and there are some older installations, legacy installations, which are on-prem. That is also giving us an opportunity to move them to the cloud. Most of our customers are looking to move to the cloud slowly and gradually. I anticipate that we will be seeing more cloud-based installations going forward.

There are one-off scenarios where the customer has an interesting mix of cloud platforms. They might have an IoT platform that is deployed on AWS, and that data is coming to the data lake and being visualized using Power BI, however, not necessarily on Azure.

I would rate the solution at a nine out of 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.