Try our new research platform with insights from 80,000+ expert users
reviewer1777569 - PeerSpot reviewer
Senior Consultant at a tech services company with 10,001+ employees
Real User
Low-code, stable solution for creating applications in a more simplified way, and can be easily scaled up
Pros and Cons
  • "Microsoft PowerApps allows you to simplify business processes and user experience. You can also create responsive applications and canvas apps through this solution. It's an easy to scale, stable, and low-code solution."
  • "Microsoft PowerApps can be more costly for small teams or organizations."

What is our primary use case?

In the complete Microsoft Power platform, there are four components: PowerApps, Power Automate, Power Virtual Agents, and Power BI. We use all these four so we can make a complete solution, e.g. a visualization dashboard, automated chat bots, and the rest we can achieve using PowerApps.

Microsoft PowerApps has three types of applications. One is the canvas app. Another one is the model-driven app that is business specific and data specific. Another type of app we can use is open source, e.g. open projects that are called "portals". We can achieve the same thing when developing a website and when doing it in the portal. These are what we can achieve using Microsoft PowerApps and the Power Platform.

Microsoft PowerApps provide the user interface and functionality, e.g. we can create a normal app that is used on web or mobile. Microsoft PowerApps is similar to a form where you perform whatever you want to do. Some look and feel controls are also found in this solution.

Power Automate, on the other hand, is where we automate the backend processes, e.g. the notifications, data extractions, etc. For something that needs calculation, we use Power Automate, while building the user interface and user experience, we use Microsoft PowerApps.  

What is most valuable?

What we like about Microsoft PowerApps is that it allows us to simplify business processes and user experience. We can also create responsive applications and canvas apps through this solution.

If we need an app that is more specific to what the business requires, we can create model-driven apps through Microsoft PowerApps. We can also create a reusable component which we can use in this solution, through the power component framework, which is a recent development model from this product.

We also love that this product is a low-code tool which has drag and drop controls, so building apps is simplified.

What needs improvement?

This solution can be more costly for small teams or organizations.

What do I think about the stability of the solution?

Both Microsoft Power Automate and Microsoft PowerApps are stable products.

Buyer's Guide
Microsoft Power Apps
August 2025
Learn what your peers think about Microsoft Power Apps. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
867,370 professionals have used our research since 2012.

What do I think about the scalability of the solution?

Microsoft PowerApps is a solution that can be easily scaled up.

How are customer service and support?

I had no issues with the technical support for this product.

What's my experience with pricing, setup cost, and licensing?

The pricing of Microsoft PowerApps is neutral, because it's completely based on user requirement. If your requirement is simple or less complex, then the basic licensing model can work, e.g. the free model, or else, you need to go for some premium features or model. The cost will be completely based on your product, and what app license is going to work for you. If per user license is going to work, then you can go for that.

Microsoft PowerApps is not that expensive, but for a small organization, getting the license could be tough, because if you have a team of five people, then it's going to cost you.

What other advice do I have?

I'm working as a developer, particularly the main power platform developer with Microsoft technology as a senior consultant. I'm working with Microsoft PowerApps and Power Automate.

Every automation nowadays is using Microsoft PowerApps and Microsoft Power Automate.

Microsoft PowerApps is best for medium to large enterprises.

I'm recommending Microsoft PowerApps for low-code projects. In the past, developers have to work a lot. They needed to use their technical skills, e.g. for developing codes. They needed to learn different languages to perform a simple mission. For web development, they need to use HTML, CSS, and JavaScript. Today, it's about using the Microsoft Power Platform, as it has low-code, no-code tools.

Microsoft PowerApps is a low-code solution, which means that we can now simplify things through drag and drop controls. We can also use different rebuild models through this solution. We can use different rebuild connectors that calculate to connect to different systems easily. Earlier, only developers were responsible for developing apps. Now, citizen developers can also make apps with the help of Microsoft Power Platform, because it's a low-code, no-code solution.

My rating for Microsoft Power Automate is an eight out of ten. I'm giving the same rating for Microsoft PowerApps: eight out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer. partner
PeerSpot user
reviewer1767510 - PeerSpot reviewer
Project Manager at a tech company with 5,001-10,000 employees
Real User
Incredible community support, easy to use, and easy to set up
Pros and Cons
  • "It is easy to use."
  • "Most of my training for what I do has been by watching or learning in the community. There needs to be better training on either one of these."

What is our primary use case?

We're using it for our business processes. We have applications for expenditure requests, travel requests, and accident reporting.

I am using the latest version of the solution.

What is most valuable?

It is easy to use.

What needs improvement?

Most of my training for what I do has been by watching or learning in the community. There needs to be better training on either one of these. 

For how long have I used the solution?

We started implementing it in February 2020.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

It is scalable. About 150 to 200 people are using it. 

In terms of our plans to increase its usage, I'm moving to a different department and starting over. We might be scaling up in my new department. In the current department, they still need to figure out what they're trying to do.

How are customer service and support?

If I'm dealing with the community, technical support is incredible.

Which solution did I use previously and why did I switch?

We were paper-based before switching to PowerApps.

How was the initial setup?

It was easy. We started in February, and everything had to be up and running in March because of the pandemic of 2020.

What about the implementation team?

I did it, and there was no reseller. We're a university, and the university was not going to pay for us to have this deployed by an outside partner.

I also take care of its maintenance.

What's my experience with pricing, setup cost, and licensing?

I don't have that information. We work with a procurement office that deploys it for our university.

Which other solutions did I evaluate?

We looked at ServiceNow because some of the departments in our organization were using ServiceNow.

What other advice do I have?

Deployment has to be supported from the top down because if you're trying to get things supported from the bottom up, you run into a lot of interference. This has not been the easiest.

PowerApps is incredible, so I would give it a nine out of 10.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Microsoft Power Apps
August 2025
Learn what your peers think about Microsoft Power Apps. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
867,370 professionals have used our research since 2012.
Jaime López - PeerSpot reviewer
Solution Architect at Avanade
MSP
Top 10
I like how fast you can develop an application and put it into production
Pros and Cons
  • "I like how fast I can develop an application and put it in production with PowerApps. I think the integration is also excellent. The platforms is growing, so they are constantly adding more connectors on all these things."
  • "Microsoft could streamline monitoring and management. In addition, it should be easier to put the solution in different environments. For example, you should be able to move from a dev environment to a production environment seamlessly."

What is our primary use case?

I belong to a consulting company that develops applications using PowerApps.

What is most valuable?

I like how fast I can develop an application and put it in production with PowerApps. I think the integration is also excellent. The platforms is growing, so they are constantly adding more connectors on all these things.

What needs improvement?

I would like it if PowerApps stored the code differently. For example, it would be nice if it were held in our GitHub repo or some other place, and we could version it to evolve it more easily. Another thing I'd like to see is more collaborative features so that more than one person could develop several things in PowerApps at once. For example, you could have creative technologies doing stuff for the visual design while the developers are doing the different things that they have to do to make the application run.

Microsoft could streamline monitoring and management. In addition, it should be easier to put the solution in different environments. For example, you should be able to move from a dev environment to a production environment seamlessly. 

For how long have I used the solution?

We've been using PowerApps for three years give or take. 

What do I think about the stability of the solution?

PowerApps is totally stable. 

What do I think about the scalability of the solution?

I don't have so much experience at this point, but I don't think we can do much about its scalability. I believe it scales by itself, but we cannot modify many properties or configurations to allow that. We are a multinational that operates globally, but I work at a regional office in Iberia. There are 700 people working in the company here in our region, but my company has around 20,000 employees globally.

How was the initial setup?

Setting up PowerApps is easy, and I can do it by myself.

What other advice do I have?

I rate PowerApps eight out of 10. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. partner
PeerSpot user
Vice President - Information Systems at a media company with 1,001-5,000 employees
Real User
Easy to create and deploy apps, but needs more RPA capabilities
Pros and Cons
  • "The initial setup is very simple."
  • "There are occasional performance challenges."

What is our primary use case?

We use the solution as part of Dynamics 365 Online. Within that, we use Power Apps and we've integrated something on the on-prem database.

The app is located within Dynamics 365 Online. It draws data from an on-prem data source. We use it to perform certain actions in Teams, so we have Dynamics 365 and Teams integration.

We've created an email reader using Power Apps.

What is most valuable?

The solution is pretty easy to create and deploy apps.

You don't need a very high level of technical knowledge. Of course, you do need some level of technical knowledge, however, a normal developer can easily learn and deploy Power Apps.

The initial setup is very simple.

The solution scales well. 

What needs improvement?

They need a bit of RPA functionalities. There are other competitive products such as ServiceNow and Automation Anywhere. They offer exhaustive functionalities. Power Apps as a platform maybe need some ready-made templates that could be deployed. That would help.

There are occasional performance challenges. 

The product could do some integrations with third-party providers. That can be still expanded. They do have a decent number of integrations and connectors available, however many of those connectors only offer the basic functionalities. I'd like to see better, wider connectivity.

For how long have I used the solution?

I've used the solution for six to eight months at this point. It's been less than a year.

What do I think about the stability of the solution?

In general, the product works fine. That said, there are occasional challenges in performance and when you actually have Power Apps working with other products on Power Platform, such as the Power Automate, et cetera. By and large, however, it's pretty stable. 

What do I think about the scalability of the solution?

We have about 300 users on the solution currently. We do have approximately 700 plus users on Dynamics 365, however, not all of them are using Power Apps.

The solution is pretty easy to scale. 

We pretty much use this solution on a daily basis. It's used a lot.

How are customer service and support?

We reached out to technical support just once where Power Automate wasn't actually triggering an event. Apart from that one ticket, it's been working fine. We haven't really dealt with technical support too much.

We have normal support. We don't have Premier Support. Of course, the response time was about average when we used them. In the end, the issue was something to do with the core product, so they have actually had to take it up with the product engineering team at Microsoft as well.

Which solution did I use previously and why did I switch?

I'm aware of ServiceNow and Automation Anywhere. 

How was the initial setup?

The initial setup is very straightforward and simple. It's not complex or difficult. 

There was some background development involved during the deployment process. 

The is no maintenance required.

What about the implementation team?

We did not need any outside assistance from consultants or integrators. We handled it in-house ourselves.

What's my experience with pricing, setup cost, and licensing?

The pricing is pretty good. Microsoft offers very good value for money.

Apart from the licensing, storage is actually the costliest part. One needs to actually look at how to optimize the use of storage as ultimately it's on the cloud. It's part of the Dataverse storage now, with Dynamics 365, Power Apps, et cetera. That bit of the offering is the costliest part.

The product license and platform licensing are good. That's definitely value for money compared to some of the other vendors. Microsoft is placed well. It's just the storage, as I said, that's costly. 

What other advice do I have?

We are customers and end-users.

We are using the cloud version, and therefore we are going with whatever is the latest available functionality.

At least for the regular day-to-day work, one can build very useful apps with minimal investment. One can start fast. The only thing is, you need to have people actually experiment on this. Other than that, it's a good platform.

Currently, I'd rate the solution at a seven out of ten right now, as there's continuous improvement that's happening and, once that happens, in the future, I will likely be rated even higher.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Executive Director at Ali 4 Solutions FZE
Real User
Creates applications quickly, is simple to use, has competitive pricing, and is easy to scale
Pros and Cons
  • "When I am developing any user UI, it gives me complete flexibility. I can manage in any way I want."
  • "When it comes to PowerApps, debugging can be difficult at times. It would be beneficial to simplify it."

What is our primary use case?

We are an IT consulting company. We provide IT solutions to other companies.

We have had a few different requirements, one requirement was to create a simple online form that can be used by the clinics. When patients arrive, they will be given a TAB, to complete the form, which will be printed directly to the receptionist, once they complete the form.

Another application was supply chain management. Using PowerApps, we replicated the entire supply chain management. The corporate users will send the requisition to the purchasing department for review and approval, after which it will be distributed to prospective vendors.

Vendors will then submit their quotes for review. Multiple quotes can also be reviewed concurrently. This is all done with PowerApps. After they have reviewed them, they can select a vendor and process the PO.

In the third scenario, we developed a public relations system that you would find here in the UAE.

PROs must manage and obtain visa permissions in the United Arab Emirates. We have documentation with a two-year expiration date. As a result, we've developed a document management system that uses a Power Automated workflow system to view the alert and process the documents for all employees.

These are the workflows that we have worked on recently and have been created using Microsoft PowerApps and Power Automate.

What is most valuable?

Because there is no need for lengthy code, applications can be created quickly. That's the beauty of PowerApps in general, whether I'm using Power Automate or PowerApps for UI development. And the UI is very user-friendly.

When I am developing any user UI, it gives me complete flexibility. I can manage in any way I want.

It is constantly being improved. I've been using it for three years and have noticed that upgrades are happening on a regular basis, and it's becoming more and more user-friendly, both for developers and for users.

We can now also share it on Microsoft Teams. As a result, it is becoming increasingly powerful.

It is very easy to use.

What needs improvement?

A web interface is one thing that I don't see. I can create an interface for mobiles and tabs but only for PowerApps.

If you can have something like Power Web with it, that will be a classic because we are developing user interfaces, but we cannot access those user interfaces using a browser.

If we can get into that mode of publishing for the public users, which is something different, and I am not sure how that can be done, but I'm sure we can come up with something.

We occasionally have some issues where we can't grant access until and unless a user is created in Active Directory. This is something that should be worked on, and when it is, it will be powerful.

When it comes to PowerApps, debugging can be difficult at times. It would be beneficial to simplify it.

For how long have I used the solution?

I have been working with Microsoft PowerApps for three years.

We are working with the latest version.

What do I think about the stability of the solution?

We have not had any performance issues, or any other issues, because it is on the cloud.

We are completely satisfied with Microsoft PowerApp's stability.

What do I think about the scalability of the solution?

Because almost everyone uses Office 365, it is very simple to scale Microsoft PowerApps.

Our company has five developers among its users. Our clients, on the other hand, vary; we have one client who has over 500 users.

How are customer service and support?

I've spoken with technical support, and they're fantastic. They provide you with a very good response from the moment you launch your ticket.

On a few occasions, when I launched a ticket, I receive full support and they were able to help me with everything.

Which solution did I use previously and why did I switch?

We use Office 365 online which includes Microsoft PowerApps, Power Automate, and Power BI.

How was the initial setup?

The initial setup is extremely simple for me. I am an IT professional, but it is easy, even for others.

I have worked with many who have been using other tools and when they were introduced to PowerApps, they expressed that it is amazing.

It didn't take long for me to install, only a couple of minutes, because I've been using Office 365 since 2013, but I've never used PowerApps before. I started only recently, in 2018.

One of my clients asked me to create a small app in PowerApps for him. That's where we began. I had a PowerApps application ready in a week.

We don't require any maintenance as it is on the cloud.

What's my experience with pricing, setup cost, and licensing?

Microsoft's pricing is comparable with other similar solutions.

Which other solutions did I evaluate?

I had evaluated Mendix. We prefer Microsoft, we have used Microsoft from the beginning.

What other advice do I have?

I am a VB developer. I began my career in 1995 or 1996. I'm a die-hard VB developer, and I love PowerApps because, I used to write a lot of code, but now with PowerApps, things are so simple and easy, we can have customized applications for end users in no time at all.

Aside from standard ERP and solutions, businesses still have a high demand for customized or tailor-made user interfaces. That is where I believe PowerApps is extremely useful.

As an IT company, I would strongly recommend this solution to anyone who is interested. It is one of the best tools available. If you are a Microsoft fan, you will definitely enjoy this product.

As IT consultants we have provided support and trained a couple of customers who are using it and also enjoying it.

I would rate Microsoft PowerApps a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Senior Programmer Analyst at Immigration and Refugee Board of Canada
Real User
Great cloud aspects and good integration potential but does work differently on different types of devices
Pros and Cons
  • "The cloud aspect has been great. We don't have to do a lot of research in order to begin integrations. It's so easy to integrate with other solutions."
  • "We're not in production yet, so we're still working through some issues."

What is our primary use case?

We're not in production yet. We're still very much in the early stages of this solution.

What is most valuable?

The cloud aspect has been great. We don't have to do a lot of research in order to begin integrations. It's so easy to integrate with other solutions.

The solution works well with Microsoft Teams. We used to use Skype for Business, and now we rely on Microsoft Teams Enterprise E5. 

There's great integration with Dynamics 365, Office 365, and more. It's great that everything is easily connected.

We can use the solution from cell phones, tablets, or computers. It works on every platform and in every environment. 

What needs improvement?

The solution does work a bit differently on cell phones and tablets.

We still have information on our SQL server and we need to migrate things over. The timing of doing that is going to be a little tight.

We're not in production yet, so we're still working through some issues. However, by the time we are in production, I'm confident this solution will be ready.

For how long have I used the solution?

I've been working with the solution for about six months at this point.

What do I think about the stability of the solution?

The stability of the solution is quite good. Of course, if we run into any issues, technical support is right there to help us, and they are very helpful.

What do I think about the scalability of the solution?

We have more than 1,500 users in our organization. There are other users that will also be able to access the solution from the outside. With this particular solution, in terms of maintenance and direct work on it, we started off as a team of four, however, now we are a team of ten. We needed some more people to maintain the surrounding software. However, overall, it's been good.

We're not a small organization. We're pretty big. It's easier to focus on smaller projects rather than trying to implement something that's large scale.

How are customer service and technical support?

We've found the technical support to be very good. They are always right there, ready to assist. We can open tickets 24 hours a day. If they are critical, they are dealt with quickly.

How was the initial setup?

Our company is quite large. With 1,500 or so people, changes take a while to implement. It's not like a small organization where you can do everything quickly. You need to make sure people know how to use it.

In general, the full deployment took a few months.

What's my experience with pricing, setup cost, and licensing?

I don't have too much information on licensing It is likely per application we use, or per machine. I don't deal directly with billing and therefore don't have the exact pricing.

What other advice do I have?

We have a very good and very close relationship with Microsoft.

I started working more on PowerApps as we were making a comparison with Salesforce. We decided on PowerApps mostly due to the fact that Salesforce would not work. 

We have to maintain our current environment, so at some point, it's not that we are 100% in these new tools. Right now we have more than 60% of our time in these new tools and try to not develop any coding. We do make some code in JavaScript, however, it isn't too much.

It's a good solution. There is some coding needed for customization aspects, however, it's a pretty solid product.

There's still a lot that I need to learn about the solution. Therefore, currently, I'd rate it at a seven out of ten. We're not in production yet, and therefore it's hard to gauge many aspects of the solution.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Senior Product Manager Data Science at a insurance company with 1,001-5,000 employees
Real User
Great UI and an easy initial setup, however, users are limited to 2,000 records
Pros and Cons
  • "There's a lot of online knowledge on the solution, to the point where new users can basically teach themselves how to use the solution."
  • "One of the major problems with it is what PowerApps calls the delegation warning. Regardless of what platform, data source, et cetera, that you're using, you can't retrieve more than 2000 records."

What is our primary use case?

We primarily use the solution as a general business process improvement. We use it as more of a digital transformation to eliminate some archaic manual processes that the business has built up over time. We're working to make everything more streamlined.

How has it helped my organization?

The solution has allowed us to remove a lot of manual redundancies and to update and streamline our processes.

What is most valuable?

It's easy to use due to expert UI. It is great.

The initial setup is easy.

There's a lot of online knowledge on the solution, to the point where new users can basically teach themselves how to use the solution.

What needs improvement?

The solution is limited in a very specific way. One of the major problems with it is what PowerApps calls the delegation warning. Regardless of what platform, data source, et cetera, that you're using, you can't retrieve more than 2000 records.

I connect to an Oracle server that has well over 150,000 records that business users want to see or could use at any given time. The only thing that I could surface in the app is a portion of up to 2000 records at one data call.

Due to this limitation, I have to build in options for the user to refine the search, to go back out to the server, and then pull back records that match that search as opposed to offering all 150,000+ records. You need to filter quite extensively. Microsoft refers to is as a "delegation issue".

For how long have I used the solution?

I've only been using the solution for about a year. It hasn't been too long as of yet.

What do I think about the stability of the solution?

The stability has been very good. We've been pretty satisfied with it. It's not buggy. It doesn't crash.

What do I think about the scalability of the solution?

You cannot scale with PowerApps. PowerApps is still very much a point solution. The size is the size.

How are customer service and technical support?

We've dealt with technical support in the past. Everybody that we've worked with at Microsoft is phenomenal. They are always willing to help troubleshoot and get to the bottom of issues. That said, with PowerApps and even Power Automate, sometimes the teams at Microsoft still don't know why some issues occur or how to work around them.

Which solution did I use previously and why did I switch?

I joined the company a year ago in September. I don't think they used anything prior to that beyond the citizen developer level. There might have been a solution that the actual coders used, however, I can't recall the product's name. It was a pretty standard Microsoft application in any case. It may have been Visual Studio.

How was the initial setup?

The initial setup is not complex. It's quite straightforward.

For me, just using it on my own, I just used Google searches or YouTube to figure out how do this or fix and tie items together. After about a month of learning and experimenting, I had a pretty good handle on how PowerApps works.

What about the implementation team?

The company as a whole used Microsoft consultants to set up a center of excellence. 

What's my experience with pricing, setup cost, and licensing?

The solution is free if you have a Teams account, or Office 365. 

If you start to use any premium connectors that are not stored in a SharePoint list or on an Excel workbook, then it costs $4 per user per month. If you want unlimited, it's about $16 per month for unlimited apps and unlimited connectors.

There might potentially be a few other extra fees, however, I'm not sure what they are. Microsoft is one of those organizations that manage to nickel and dime its customers on everything.

What other advice do I have?

We're just a customer. We don't have a business relationship with Microsoft.

We are most likely using the most recent or updated version of the solution, however, I'm unsure of the exact version number.

While Microsoft is an option, I'd recommend users check out OutSystems first and see if it makes sense for them to use that before looking into Microsoft.

Overall, I'd rate the solution six out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Hardland Moncayo - PeerSpot reviewer
Head of Software Engineering Department at a tech services company with 51-200 employees
Real User
A good data development and connectivity tool, that would benefit from a longer period of availability for historical data
Pros and Cons
  • "We like that this solution allows us to fully define our test environments, and link them using different code. This means we can do different tests, but with one basic structure, and then export the data and use it in other platforms."
  • "We would like to see the period for viewing executions within this solution to be extended beyond its current limit of 28 days. We would prefer to be able to offer our customers an infinite amount of history to search."

What is our primary use case?

We use this solution to integrate our apps, and send processed data via the different connectors it provides.

How has it helped my organization?

This solution has allowed us to offer our customers to integrate with our platform platform to send documents, and for them to be processed with a digital key network solution, without having to use the platform directly.

What is most valuable?

We like that this solution allows us to fully define our test environments, and link them using different code. This means we can do different tests, but with one basic structure, and then export the data and use it in other platforms.

What needs improvement?

We would like to see the period for viewing executions within this solution to be extended beyond its current limit of 28 days.  We would prefer to be able to offer our customers an infinite amount of history to search.

For how long have I used the solution?

We have been using this solution for nearly a year.

What do I think about the stability of the solution?

We have found this to be a generally stable solution, and have only experienced issues when there are a large amount of registers involved.

What do I think about the scalability of the solution?

This is a very scalable solution.

Which solution did I use previously and why did I switch?

We did not previously have a single solution, but instead we used a component that worked using Java.  We switched to this software because it was less complex to maintain.

How was the initial setup?

The initial set up of this solution is fairly straightforward.

What about the implementation team?

We implemented this solution using our in-house team.

What's my experience with pricing, setup cost, and licensing?

We would advise organizations that this solution has a high-price point. However, the cost is justified for how comprehensive the package is, and all components of the solution are available under the standard license plan; there are no hidden costs involved.

What other advice do I have?

We would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. partner
PeerSpot user
Buyer's Guide
Download our free Microsoft Power Apps Report and get advice and tips from experienced pros sharing their opinions.
Updated: August 2025
Buyer's Guide
Download our free Microsoft Power Apps Report and get advice and tips from experienced pros sharing their opinions.