Microsoft Power BI Reviews

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.

A client used Power BI mainly for banking reports. Another client was working in the field of laboratories, and they requested Power BI for the analysis of laboratory-related data for COVID-19. There were also some use cases where we used predictive analytics or utilized the power of Power BI services in the cloud.

It can be deployed on-premises and on the cloud.

It helps in automating the process of filling the data or refreshing the data to give you timely calculations for all the aspects of the dashboards that you have built. You can easily see all the real-time data with Power BI.

The good part of it is that you can do whatever you want with it when it comes to building BI. In terms of languages, it supports Python, and it also natively supports R.

You can integrate it with the cloud. On the desktop level, you just install the desktop installer, which is about a hundred megabytes or something like that, and it connects to the cloud. So, on the desktop, you can utilize the cloud power for AI and machine learning to help you with predictive analytics.

Most of the dashboarding tools have prebuilt graphs. So, you have to stick with them, unless you are going to use a third-party tool to create them, and then you are going to upload them to the BI tool. In Power BI, they started supporting this functionality and created a tool for that, but it isn't yet complete and mature. It is still exceeding the expectations and is better than most of the BI tools when it comes to creating custom graphs, but it needs more enhancement and simplification. It would be good to have a design tool provided by Power BI to design the graphs that we want and set the figures that we want on them.

I have been using this solution for six years.

It is stable. Solving dashboard issues on other products, such as Oracle, took us a lot of time, whereas solving issues in Power BI was so simple. The language they're using is also easy. In Power BI, you use the DAX language, which is derived from Excel. So, anyone who knows how to write Excel code would know how to deal with Power BI. It is going to be so simple.

The cloud version is scalable.

It is super easy to set up. I've been giving training on this to new employees, and they quickly learn how to work with the whole product. It doesn't take them more than one or two sessions.

The installation of Power BI Desktop on a computer takes a maximum of 10 minutes. You just have to install it on the computer, and that's it. Most of the services are over the cloud. When you do the subscription, you just connect or sign in with your company email address that has been registered, and that's it.

The on-premises version requires extra staff. It requires an engineer who knows how to implement AI algorithms and then connect them to the offline Power BI solution.

Power BI is subscription-based, and you have three options. The Pro edition, which is the standard one, is about $9 per user. The Premium edition, which provides AI and cloud capabilities but at a limited size, is for small to medium enterprises. It is about $20 per user. For large enterprises, such as manufacturing facilities, there is an option for the capacity. The capacity subscription is about $4,000 per capacity level.

They also have an option for the on-premises version, but it is not common to see someone going for the on-premises version. The on-premises version requires a specific license that is attached to SQL Server. I believe it is about $17,000, but I'm not sure about it.

It has an on-premises version as well as a cloud version. I usually recommend people to work with the cloud version. In the on-premises version, if they want it to go with the artificial intelligence part, they are going to require engineers to configure it, whereas it is already there in the cloud version. It is already configured and affordable. The cloud version costs between $9 to $20 per user, which makes it very affordable, and you also have the capacity option, which costs about $4,000 per month per capacity. The capacity option is usually for huge enterprises. Regular companies, even banks, can work efficiently with the cheapest option, which is $9 to $20 per user.

After working with Power BI, I would rate it an eight out of 10. There is huge competition in the market when it comes to BI tools, and there are fractional differences between Power BI and some of its competitors.

We have many use cases, from creating full ETL workloads for supporting some dashboards to only building dashboards by themselves. For example, there is one stage where we had to do some data integration from several sources to assess the quality of the data that we are consuming for our projects. We had to ingest data and convert it using Power BI, which is useful but isn't the best ETL tool, and I understand that that is not its purpose. Finally, we built out a schema model and built reports upon that. It's a full project. 

We also have another project, where we are attempting to do some incremental refresh because we are ingesting a lot of data from lake sources and SQL sources. We are doing direct query and applying some optimization from Synapse.

I am currently using the latest version of Power BI.

The most valuable feature is definitely the visual aspect and the DAX capabilities to virtually do anything.

Something that everyone has suggested and that we are currently implementing and testing is the ability to export tables with the same format. That is something many customers were seeking, and right now it is possible to do that. Focusing on table support is a huge opportunity.

One opportunity for improvement would be on the Power Query side. As a consultant, I know Power Query is not the main strength of Power BI. It is not where Power BI shines, but many customers use Power Query to do full ETL workloads for deliverable cookies.

When you try to process a lot of data from one million records, it breaks. The computer runs out of CPU and memory. It's terrible, but I know it's not its main purpose, so that would be my suggestion.

It's stable, but the desktop is not so stable. I have experienced several crashes. I would say there is a lot of opportunity for improvement on that.

A couple of people are needed for deployment and maintenance. You always need a developer who is proficient on Power Query and maybe some other DevOps guy who sets up the pipeline. So, maybe two people at most. It's very easy.

Scalability on the ETL side is not so good. When you run the workloads on service, you can fail almost anything, but it's not exactly the best for scaling.

On the virtualization side, I would say it's good.

I haven't actually needed much technical support. I know there are forums and people respond, but I haven't really sought that out. There is so much documentation online, there are books online, and there are YouTube channels from guys that provide solutions to issues and to some other stuff. The community is very proficient.

It is very easy. Even non-IT professionals use it and deliver value to the company.

I would rate this solution 8 out of 10. 

My advice is to just jump right into it, download the Power BI desktop and start looking at YouTube channels. There are lots of people who have made wonderful things on YouTube.

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 built a BI system to provide clients with access to the data that we collect. They can access the data report and various reports by using Power BI.

It is built into the Azure cloud. You can't deploy it otherwise.

We have a product called ED Tracker, and we allow clients to subscribe to this product, and they use it through Power BI. It enables us to offer new services to clients and basically allows them to work on the data or report themselves, rather than sending them data with PowerPoint decks, PDF reports, etc. So, we work with our clients through this platform. They need to have the license. If they want to access the system, we just tell them that they need to get a license. The license is very cheap. It is $10 a month per user. It is not very expensive, and once they have the license, they can access our cloud solution.

Its connectivity with other Office applications, mostly with Excel, and the ability to deploy it very easily are the most valuable features. It comes sort of bundled with the cloud, so you don't need to set up a server and a standalone infrastructure. So, getting into the system or building something that you can deploy is very easy and very cheap. With other systems, you need to have a server, and you need to have a license for the server. The initial setup is very costly.

It is an evolving solution. So, it still has some rough edges. As compared to Tableau or QlikView, there are some things that you can't do when you want to. For example, giving specific access to some reports for users. You can get it up and running very fast, but some things are a bit trickier, and for some of the things, you need to actually write code. 

It is sort of a work in progress. They're catching up on the competition, but it still takes time. Other solutions are more mature, and they have been in the market much longer, but it is catching up. It has come a long way in terms of how it was working two years ago, but there are some things that you still can't do with it. For example, permission management and user access management are still a bit limited. It is basically based on the idea that everybody from the organization can see everything or limit the type of data they can see. If I want you to see only one report and the other guy to see another report, I can't do it. There should be a better way to manage permissions and users. It should also support external users much better.

There should be the ability to export to PowerPoint or PDF. It should be more efficient. It's rather clunky right now. Sometimes, the system is inconsistent in the way it does things. 

I have been using this solution for two years.

It is adequate in terms of speed and stability. It is very stable. Sometimes, it is a bit slow. It can be faster, but you need to subscribe and purchase additional packages or resources, and then it becomes more expensive.

We haven't scaled yet, but you have the ability to have a dedicated server on Azure with CPU. You can increase and have an SQL Server, so you can scale it.

As of now, we have around 10 to 12 users internally and externally. Some are internal, and some are external clients. We do have plans to increase the usage because we're trying to sell and market the product to other clients as well. So, we do have plans to increase the number of users. One of the benefits is that it doesn't matter if we have 10, 20, or 50 users. It doesn't inflict any costs on us because they go directly to the cloud. They don't come to us. It is very indirect, but we do plan to extend the usage of that system. We might also extend it internally.

Their technical support is absolutely magnificent. A week ago, we had an issue related to permissions, and we couldn't find out how to do that. My colleague contacted the support of Power BI. They not only answered us by mail; they also had a half an hour session with us on Teams to better understand what our issues were. They wanted us to send them the files. They reviewed them and told us that there were still some limitations, but they were working on them, and they will let us know.

We were stunned that someone from Microsoft is interested in what we're doing and someone is willing to go online and have a half an hour session with us so that we can explain what we're doing and what is our issue, and they can think about how to resolve it. We're a small client. We're not a big company. So, we were stunned by their support. Their support is amazing.

A few years ago, we've tested QlikView and Qlik Sense. Their deployment costs were rather high, so we decided to use Power BI.

It was very easy and straightforward. It was rather quick because you can launch it. It is very easy to publish. They give you direct access to their cloud. For small solutions or datasets like ours, the initial setup was a matter of days. We started with the desktop on-premise, and then we published it to the cloud. It was rather easy. It was a matter of days to a week or two.

We used our own team. Its deployment and maintenance are taken care of by a PM and a colleague of mine. It is very easy. You just press publish, and it's off to the cloud.

In terms of ROI, it is a 10 out of 10.

Its price is very low. It is like $10 per user, per month. The clients pay for their own licenses. It is not on us. 

There are no costs in addition to the standard licensing fees. That's the beauty. With other systems, you need to spend a couple of thousand dollars just to get started, and then you need to spend $500 per year for the license, which becomes much more costly. You have a system here where for $120 to $140 a year, you can start with two people and start developing and deploying. You can see why the cost difference is huge, especially when you are on a low scale, like us, and you're not building something very huge.

We didn't evaluate other options because we have had some past experience with other solutions. We knew that QlikView might be good, but you need to spend a couple of thousand dollars just to get started if you want to do something. We knew the costs, and the entry cost was much higher. So, we decided to go with Power BI. It is also integrated with Office and Excel, so it's very easy to go along and do some of the things that you can do in Excel. It is very easy to transition between them.

If you are looking for a good BI solution for a small business that is very easy to deploy and not costly and that can use the cloud in terms of security, Power BI is probably the best solution in the market.

I would rate it a nine out of 10. There are other solutions that might be better than this, but they're more costly. It is the cheapest BI solution in the market. It is not the best in terms of features, but it is the best in terms of value for money. For the volume of work that we have, there is absolutely no competition.

The data is captured by transaction processing systems, and even when the data is captured by a very sophisticated enterprise resource planning system, or ERP system, such as SAP. We'll find that that data is organized in a manner that is suited for the data updated. Therefore, when data has to be used for decision making, it has to be reoriented and organized in a manner that is suitable for data analysis and further for predictive analytics also. What we do is pull out data from multiple data sources, either on SAP or somewhere else.

There could be a certain budget or plan or target-related data on some other platform or on a Microsoft Excel spreadsheet. The data is stored at different places. Some data could be on your internet platforms. Wherever it is, we pull out the data. Then we get that into the SQL server and we organize it in a manner that's suitable for further creation of dashboards and analytics applications, which can be used for better decision making.

The company has been able to make better decisions, due to the fact that, when we prepare business intelligence or data analytics applications, they are used by very similar decision-makers, as well as middle-level management decision-makers. From the same infrastructure, the data is used by even the report consumers. You can consider three layers of users, report consumers, mid-level use, as in, those who do interactive analysis of data, and decision-makers. Right at the top, those who would like to see the key performance indicators and use them for deciding a course of action can do so. All of our applications have been providing functionality for all these types of needs, including risk and compliance.

The solution offers many features, however, just the way in which that product is designed is quite useful for us. 

The way in which it can connect to multiple data sources is also very useful. The way in which data can be manipulated by using data analysis expressions has also been a good feature for us.

The solution is stable.

The solution is quite scalable. 

Our clients seem to be happy with the level of technical support they receive.

With our experience, the initial setup is straightforward.

Microsoft is often updating the solution adding new helpful features.

I'm not a product expert as such, however, I am aware that Microsoft comes out with a newer version, which is really downloadable and it's replaced every month. Therefore, the improvement is continuous. Since Microsoft provides a free downloadable desktop version of our BI. That desktop portion gets a new version which comes every month, we can replace the older version. 

Their ecosystem is quite good in terms of adding new features, in terms of adding custom visuals or adding many more interfaces or reporting features and more functionality within existing reporting and graphs. We don't have much to complain about except that they can always add many more features as they go.

Microsoft has got a very large repository of all change suggestions which have been raised by the BI community. They keep on adding features that are very widely sought after by the community. We don't focus on product features. We focus on business requirements. To use the solution, we find that existing features are good enough and offer us a very effective solution.

We've used the solution since its inception. We've used it for a very long time. We have been in this domain for the past 30 years.

The solution is quite stable. That's why it is right at the top, of Gartner's quadrant. We have deployed it with hundreds of users and it's withstood the test of time.

The solution is quite scalable. Of course, it requires data strategy just like any solution or any tool.

We tend to have 100 to 200 users at a minimum using the solution.

The solution is extensively deployed. We have plans to use it on an ongoing basis. They come out with new versions and new features every month, and this constant updating and iteration of the product have really been very helpful for us to provide more advanced solutions.

In terms of technical support, we don't really deal with it. Normally, our clients have a contract with Microsoft, however, my understanding is that their experience is good. 

We were using a CA tool and we have done work on Oracle. We have done work on many such platforms. However, since 2008 or 2009, we have been focusing on Microsoft as the total cost of ownership has been quite reasonable.

The initial setup is quite straightforward.

Our implementation strategy involved a business requirement phase where we sought out to understand exactly the expectations for a particular project. Then there is was a design phase where we decided on a data strategy of pulling data from multiple data switches. After that, there was a dashboard design phase, which includes wireframing of dashboards and then designing the dashboards according to those wireframes. Finally, we deploy and in that phase, we put in role level security, et cetera, and deploy it at an enterprise level. The entire process tasks three to four months in total, end-to-end.

We don't require much maintenance due to our maturity in design and development. We have been monitoring sites without having to add too many resources at our end as we have a robust design and maybe one person can handle four to five.

We do the implementation on our own. We have deep experience in this area, and we have developed two types of processes that we use to deploy our solutions. One is the data approach, where you know all best practices and methodologies are embedded into that thing. That framework gives a hundred percent assurance in terms of the success of that project. We have also developed a presentation layer framework whereby different subject areas are designed with very indicative dashboards and those dashboards can be quickly adapted to any data. That way, rather than starting from scratch, we use this framework which helps us to deploy our solution quite successfully. It's very fast also. We save around 50% to 55% of the time this way.

We don't deal directly with licensing. That said, certainly, we are aware in terms of what the Microsoft BI license costs. If it has to be applied on the cloud, then it costs around $10 per month per user. For a pro license and for a premium license it's around $20 per month per user. If it has to be applied on-premises then, depending on the course of your server, you have to buy a software assurance version of the database.

They don't charge for additional features. If you want a premium capacity to handle your work or job, then there is a separate license available. That is a premium license, which is available with the entire product managed by Microsoft and you can use lot more features, including Azure, et cetera.

We are Microsoft partners.

We have two deployment options. Some of our clients have deployed the cloud solution. Some are deployed on-premises.

Anybody who has worked on existing spreadsheet-based solutions can quickly adapt to Microsoft BI and the data visualization and interactive data features, they'll find it very exciting to use and very fast to adapt to it. It's a very effective solution.

I'd rate the solution at a nine out of ten.

I would describe myself as more of a casual user, only because I have so many other things that I have to get done. I wish I could be more of a user, but it's hard. Right now, I have two different main use cases. I use it for teaching. At another institution, I use it for demonstrating how easy it is to build dashboards. It was really to show to all my users the benefit of business analytics. I use it to demonstrate how easy it is to generate your own analytics versus having a department run reports for you then putting it in Excel and making graphs. 

I like the fact that Power BI lets me use Excel data. At least 90% of my state data is in Excel spreadsheets. Having the ability to just attach a spreadsheet as a data source is very, very important. It's also good for training and teaching. Sometimes you don't always have access to a live production database, so having a spreadsheet with sample data is always nice.

The Microsoft BI interface should be simpler and more user-friendly. I find it very difficult to move between their data sources and their analytics section. It's probably designed by data analysts that typically get the data from somewhere else. So, one person logs into Power BI, moves the data around and puts it in the proper form then somebody else goes in from the dashboard. What I'm finding more and more is that the person playing with the data is also going to be the person building the dashboard, so the interface needs to be more seamless and dumbed down for the average user. 

Tableau is much better at that, which is probably why it's more expensive. The days where one person works on the data and someone else does the analytics are coming to an end. In the past, larger organizations usually had a dedicated analytics team and a dedicated data team. Now we buy data as a service, so we got rid of our data team and we don't have analysts per se. Instead, we have smart users. So I think Microsoft BI needs to move on to the next iteration of truly user-friendly solutions.

I've been using Microsoft BI for about three years.

Microsoft BI has never crashed on me.

I honestly can't comment on how scalable Microsoft BI is because I've never taken it beyond training or simple use. But I would imagine, if it's on Azure, that it's scalable. I haven't had the pleasure of scaling it, so I don't know, but it doesn't strike me as a solution that would have problems with scalability.

I have not had to contact technical support, but I've actually downloaded and taken three Power BI courses for free and they're very good.

I was using Tableau but the licensing cost went up when Salesforce required them to raise the price. But if the price hadn't changed, I would've absolutely stuck with Tableau because I like it. I do not know about the cost of the licenses. We buy it from the state and when it went up, our CIO at the time said no more Tableau licenses. I had to scramble to find a replacement, and fortunately, I discovered that Power BI is included in Microsoft 365. However, I prefer Tableau's interface. Microsoft BI's user interface is convoluted in terms of how you attach a data source. You have a separate screen for defining your data and then you have to jump to a different screen to model the results. In other words, there are two separate interfaces for data and analytics. In Tableau, it's more seamless. 

Setup is very easy. You click on the icon, download the MSI, and it loads itself. It takes about a couple of hours to deploy overall.

I'd rate Microsoft BI as an eight out of 10. The biggest drawback is the user interface. From what I'm seeing, Windows 11 is going to have a more user-friendly interface. Even Microsoft Edge is adopting a more user-friendly interface. I'm hoping that Power BI follows this trend as well. 

My advice for anyone who is thinking about adopting Microsoft BI is to understand what you're trying to do with it. If you're trying to do analytics with it, then it depends on the kind of analytics. If you're want to do statistical analytics, it's not the tool for you. It's a tool that's better suited for visual analytics than it is for straight-up analytics. If you're dealing with patterns and data, it's great. If you're working with numbers and data, it's not so good. You're better off with a statistical package.

We are using it for financial analytics and reporting. We are using it to keep a track of projects and being able to degrade the projects. We are also using it for contract closeout.

My technical guy has been using the first version of it since it came out, but we are getting ready to upgrade to the newer version. It comes along in a bundle with the 365 Enterprise version.

It is on the cloud. We're probably going to run a hybrid because we want to be able to move around. If anything happens or if needed, we can move from platform to platform.

We can see things from a bird's eye view. We can do predictive analytics. I can tell who's capable, who's doing what, when and how much money they're spending, and how fast they're burning. So, it gives us a bird's eye view over the financials and the money. It basically gives us the ability to collaborate and keep track of everything that's going on in an organization. We were able to bring all the collaboration and tasks right into Power BI.

It is easy to use. It has got a desktop where people can develop their own dashboards. Basically, we have figured out how to connect finance contracts and all programs for the government agency. So, they can see everything in a dashboard. So, it is very easy to use from a technical standpoint of view. We publish a report every morning for the government, and we got all the data into one place. The data can be refreshed. We are using the API to connect to various systems, such as the financial system, contract writing system, and workflow. We are able to bring things from NIPA, which is their budget and where they keep all their money. There are a lot of features, but the most important thing is it is very easy to use. It is not like Tableau. With Tableau, you've almost got to be a rocket scientist.

On the user side, it is quite simple. If you know how to run a pivot table, and then you can do almost anything. All the data is right there in the database. So, if you understand pivot tables and know how they are run, and you know the reports that you are looking for, then everything becomes very easy to run in your organization.

Its desktop tool is a little bit memory CPU intensive, and it can be improved, but the machines nowadays come with a lot of memory. For the desktop users who are using it on the desktop, we recommend that they do an upgrade. It is a minor issue. We can fix it on the desktop.

We've been using Microsoft BI for about four and a half years.

Its stability is pretty good. It is pretty stable.

I would rate it an eight out of 10 in terms of scalability. Currently, we are running a pilot. We're doing a pilot for army headquarters. They dictate what happens and what they use. Currently, there are 10 users, but I'm looking to go up to at least a hundred. 

We got an architect and an assistant administrator. We got a staff of three and a half people because people take vacations or sick leaves. The good part about it is that these people can work from anywhere.

We are a Microsoft reseller. We have partnered with Microsoft. We have developed a relationship with their technical folks over the years. So, we kind of go directly to them. My partner came from Microsoft, so he has a very good relationship with a few technical folks. So, we, kind of, have some special privileges that a couple of other vendors don't have.

As a matter of fact, we had built a tool, but it took so long to get it vetted and get it through to ATOs. That's when we decided to convert to Microsoft Power BI. It has already been vetted and approved in the army environment. It is an approved government site for cloud services. We were looking for the easiest path, and that's why we worked with Microsoft BI. They've already been embedded into the government. It is bundled with Office 365.

If my technical person had to rate it, he would say very easy. All we need is to have the software.

It was done in-house.

They are charging us by users in storage, and there is a license fee. My financial people handle all that. The client has already worked out a contract with Microsoft, and basically, we're getting government prices.

The backend is the most important part. We understand its backend. We implemented the on-time system for an airport. We don't find its modeling complicated. We set up the back offices and get all the modeling done and everything connected. The customer doesn't even see that. They only see the part where they're running their reports and doing the analytics or whatever they need to do. We give them all the information at their fingertips.

Everybody is going to Business Analytics. A lot of people don't understand the difference between analytics and coding, but that's something for me to teach and educate them on.

I would advise doing your testing and environment setup. You should evaluate your product very well and figure out what platform your organization is running on. You should be careful and look at how well it integrates with other products. If you're not in a Microsoft environment, it is going to be quite difficult. Oracle and Microsoft are competitive. So, you go with one or the other. The reason why I like Microsoft is that they integrate with all applications. Microsoft controls 99% of the desktops.

I would rate Microsoft BI a nine out of 10.