Microsoft Power Automate is primarily used to update some legacy systems for our client, as well as government compliance systems and web-based reporting systems that don't have APIs. Microsoft PowerApps has the same use case. It's the front end and is the part that is interacting with the client and interacting with the collected data.
CEO at Vertical Symmetry
Mature, fast development, allows you to build sophisticated business logic
Pros and Cons
- "When compared with Microsoft Power Automate, it is a bit more mature, and we're able to build things pretty rapidly."
- "We really like Microsoft PowerApps, and we've been able to build some fairly sophisticated business logic inside of it."
- "It definitely has room for improvement, but when I give it a seven, I mean it's functional. I can get the job done, but it's far from ideal."
What is our primary use case?
What is most valuable?
We really like Microsoft PowerApps. When compared with Microsoft Power Automate, it is a bit more mature, and we're able to build things pretty rapidly.
It's a different paradigm to build around, and it's a different programming paradigm. It's more like Excel in that you build formulas and pieces, but we've been able to build some fairly sophisticated business logic inside of it. As a result, we believe that is much more mature. I'd say that's around an eight, eight and a half, out of ten.
What needs improvement?
I believe, Microsoft PowerApps is still in its early stages. I believe it is far more mature and integrated. I would say the programming language, because the drag and drop, low code, no code, its nice to get started, but you really want to be able to work as a programmer with an IDE and real code, and we've been able to start to do that a little bit and integrate a lot of JavaScript with RPA, with Power Apps I haven't been able to do that. I believe there is a way to do it by putting the data into Git. I just haven't used it yet, and haven't needed to.
As it's a cloud-based app, the development environment has some really nice parts and some that are a little clunky, but overall, I'd say it's a good product.
For how long have I used the solution?
We have been using Microsoft PowerApps a bit longer than we have been using Microsoft Power Automate.
Buyer's Guide
Microsoft Power Apps
March 2026
Learn what your peers think about Microsoft Power Apps. Get advice and tips from experienced pros sharing their opinions. Updated: March 2026.
885,264 professionals have used our research since 2012.
What do I think about the scalability of the solution?
We haven't fully launched a product yet, but I will say that development is quick and we can make changes quickly. I can't speak to the app's scalability just yet.
Which solution did I use previously and why did I switch?
I've only used it through an RPA. We either did it for many years, or we did it by hand with JavaScript. We would use some tools to actually grab for web-based things, not desktop-based. We wrote tools that would allow us to take control of the website and then modify it on the fly while automating these processes.
We did it all with secure JavaScript, which is a lot of work and custom code, and it's difficult to maintain, so having a tool like an RPA tool, where we can take that business logic, put it in there, and then somebody who knows the stuff can come around after us and go, okay, I see what they did there, would be great.
We believe we have exploited the tool and pushed it to its limits, and we are still learning about its strengths and weaknesses. It definitely has room for improvement, but when I give it a seven, I mean it's functional. I can get the job done, but it's far from ideal.
When I say Java, what I mean is that when we were doing automation, we were primarily working on web automation. My phone is dying, so that's why I cut off.
We would write a lot of JavaScript code to automate, automate, and update these external websites that didn't have APIs, that we would read from. We are now reading from spreadsheets and updating data for them, then retrieving data from the results, and this simplified things significantly.
Which other solutions did I evaluate?
We wanted to see what people were doing with UiPath. I'm not really using it yet. I've looked into it a little bit, but it just hasn't been a driver for this project yet.
What other advice do I have?
I am just using the product. I evaluated a problem and a solution set for a client, and I just evaluated these tools and said, despite their youth, these tools look like they are good. We looked at UiPath, but the price tag was expensive for a nonprofit, so money was an issue. We had a very limited budget from a grant, so we had to work with a toolset that wasn't on par with the Fortune 500. So far, we're pleased with the solution, and it's working. There are days when it is frustrating, but I've been doing this for 40 years and there are always challenges with tools. We do not have a relationship with Microsoft.
I would rate Microsoft PowerApps an eight 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.
Solution Architect at Avanade
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."
- "I like how fast I can develop an application and put it in production with PowerApps, and I think the integration is also excellent because the platform is growing and 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."
- "Microsoft could streamline monitoring and management. In addition, it should be easier to put the solution in different environments."
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
Buyer's Guide
Microsoft Power Apps
March 2026
Learn what your peers think about Microsoft Power Apps. Get advice and tips from experienced pros sharing their opinions. Updated: March 2026.
885,264 professionals have used our research since 2012.
Vice President - Information Systems at a media company with 1,001-5,000 employees
Easy to create and deploy apps, but needs more RPA capabilities
Pros and Cons
- "The initial setup is very simple."
- "The solution is pretty easy to create and deploy apps."
- "There are occasional performance challenges."
- "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.
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."
- "As an IT company, I would strongly recommend this solution to anyone who is interested, as it is one of the best tools available."
- "When it comes to PowerApps, debugging can be difficult at times. It would be beneficial to simplify it."
- "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.
IT Senior General Manager at Abdul Latif Jameel
Stable with good technical support but doesn't integrate with non-Microsoft products very well
Pros and Cons
- "The initial setup is not complicated."
- "I'd advise people to consider working with the product; it works very well with the other products of Microsoft in general and integrates with Microsoft Teams and other apps, which is helpful if you use a lot of Microsoft."
- "Microsoft is not cheap. The pricing could be lowered for their customers."
- "Microsoft is not cheap. The pricing could be lowered for their customers."
What is most valuable?
From an architecture point of view, the architectural criteria are the most valuable aspect of the solution.
The solution is quite stable.
The product integrates well with other Microsoft products.
Technical support is very helpful
The initial setup is not complicated.
What needs improvement?
Microsoft is not cheap. The pricing could be lowered for their customers.
It's not easy to integrate the solution with other products that aren't Microsoft-related.
For how long have I used the solution?
I've been using the solution for about two to two-and-a-half years.
What do I think about the stability of the solution?
The solution has proven to be quite stable. There are no bugs or glitches and it doesn't crash or freeze. I find the solution to be reliable.
What do I think about the scalability of the solution?
We have about 1,000 users on the solution currently.
How are customer service and technical support?
Technical support has been very good. It's definitely helpful. We are a big, big, big company. We have a relationship with them, and we find that the service is good. We get pretty much good support from them. We're satisfied with the amount of attention we have when there are issues.
Which solution did I use previously and why did I switch?
We also use Appian. We use both products simultaneously.
How was the initial setup?
The initial setup was very easy and quite straightforward. I would not describe the process as overly complex or difficult. A company shouldn't have any issues with the implementation.
What about the implementation team?
We have a Microsoft partner we deal with. They assisted us with the implementation.
What's my experience with pricing, setup cost, and licensing?
The pricing could definitely be lowered.
We pay an annual license fee to Microsoft. We do not pay monthly.
I cannot speak to the exact cost our company pays yearly in order to be able to use this product.
What other advice do I have?
We have a Microsoft partner that we work with.
I'm not sure which version of the solution we're using.
I'd advise people to consider working with the product. It works very well with the other products of Microsoft in general and integrates with Microsoft Teams and other apps, which is helpful if you use a lot of Microsoft. I'd highly recommend it. It's easy to integrate.
Overall, I would rate it at a seven out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer. partner
Digital Transformation Project Manager at a wholesaler/distributor with 5,001-10,000 employees
Useful application making platforms, good performance, and excellent support
Pros and Cons
- "The most valuable feature of this solution is the Model-driven or Canvas application-making platforms. The power of the two gives us exactly what we are looking for."
- "The most valuable feature of this solution is the Model-driven or Canvas application-making platforms, and the power of the two gives us exactly what we are looking for."
- "In an upcoming release, I would like to see custom APIs, better integration with other solutions, and more connectors available."
- "In an upcoming release, I would like to see custom APIs, better integration with other solutions, and more connectors available."
What is our primary use case?
This is a low-code solution that I am using for making applications.
What is most valuable?
The most valuable feature of this solution is the Model-driven or Canvas application-making platforms. The power of the two gives us exactly what we are looking for.
What needs improvement?
In an upcoming release, I would like to see custom APIs, better integration with other solutions, and more connectors available.
For how long have I used the solution?
I have been using this solution for approximately eight months.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
We have plans to scale the solution in the future and it is very scalable.
We have approximately 35 people users using the solution in my organization and we plan to increase that number to 75.
How are customer service and technical support?
The customer service has been very responsive and has always given us the help we required. Alternatively, there is a large PowerApps community that can help anyone find a solution for their problems. The overall support is excellent.
How was the initial setup?
The initial setup was easy, we had no problems.
We have a small team that does the maintenance of the solution.
What's my experience with pricing, setup cost, and licensing?
I pay nine dollars monthly for the subscription to this solution and the price of the is reasonable.
What other advice do I have?
My advice to others is to review their use case and if it fits then I would recommend they try this solution.
I rate Microsoft PowerApps a ten out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
IT Operations Section Head at Toyota Motor Philippines Corporation
Generates reports quickly and is stable and scalable
Pros and Cons
- "Generating reports is very fast with Microsoft PowerApps. It's stable and scalable as well."
- "Generating reports is very fast with Microsoft PowerApps; it's stable and scalable as well."
- "The price could be lower."
- "The price could be lower."
What is our primary use case?
We migrated all the applications to the PowerApps Server and are sending some to other users.
What is most valuable?
Generating reports is very fast with Microsoft PowerApps. It's stable and scalable as well.
Also, the technical support is good.
What needs improvement?
The price could be lower.
For how long have I used the solution?
We've been using it since last year.
What do I think about the stability of the solution?
Microsoft PowerApps is stable.
What do I think about the scalability of the solution?
It is scalable.
How are customer service and technical support?
I am satisfied with the technical support for Microsoft PowerApps.
How was the initial setup?
The installation was very easy because it's already in the cloud. It took about 20 minutes to install PowerApps.
What about the implementation team?
You can install Microsoft PowerApps by yourself.
What's my experience with pricing, setup cost, and licensing?
The cost for licensing could be lower.
What other advice do I have?
I rate this solution at nine on a scale from one to 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.
Principal at a consultancy with 1-10 employees
Great for quickly making apps, with reasonable pricing, but doesn't scale well externally
Pros and Cons
- "The solution is excellent at figuring how to build an application in three months. It makes it very quick and easy."
- "From my perspective, it was a great place to start and a great place to sit and test the waters."
- "The documentation isn't great. It's only 75% of what you need to know. If you go beyond that and run into issues, it's really not going to help you."
- "They get expensive when you start to go to non-internal users."
What is our primary use case?
I primarily use the solution for its business application. My business needed an application and so that's what we're using Power Apps for.
How has it helped my organization?
We've been pleased with it. I would say that it has improved the way our organization functions. It makes app-building faster and easier.
What is most valuable?
The solution is excellent at figuring how to build an application in three months. It makes it very quick and easy.
The pricing is very reasonable. it's not overly expensive.
What needs improvement?
I can't recall any missing features. Currently, the solution is doing a good job of meeting my needs.
My target is to have an application that I can use for clients. I don't see Power Apps as being the long-term solution. They get expensive when you start to go to non-internal users. If there were to be external users, the solution would get expensive.
The documentation isn't great. It's only 75% of what you need to know. If you go beyond that and run into issues, it's really not going to help you.
For example, the software is almost guilty of being too powerful. The particular problem I had was that they recommended that I use Azure to do the login, to do the user authentication. Therefore, I set it up. However, it didn't work. I could not find the solution via documentation or online at all. Without knowing I could access technical support, I paid someone a couple of hundred dollars to try and figure it out for me and they couldn't figure it out. Eventually, I was just looking around and I came across one setting hidden away and it was set to false. I instinctively realized that it looked like it might be related and so I set it to true and all of a sudden everything worked. However, that whole issue could have been mitigated if the documentation just took that extra step and got into the nuances of the product.
What I'd love to see them do is to sit down and clean up the interfaces. There are three different ways that you can program. I'm particular to using a Power Apps portal. There are three different ways I can edit my Power Apps portal website. Each of them kind of does a better job of doing some things than the other ones do. Therefore you're kind of in this in-between realm of having to choose between certain things if you decide to go with a specific approach. They really need to clean up the development environment so that t's straightforward and predictable across the different ways to program.
It does things, such as, if you want to delete a particular field or table, you get this message that says you can't due to the fact that it has dependencies. It's really hard to find what those dependencies are. Items like that need to be clarified.
The application is working great now, however, every once in a while it gets complicated and it's hard to navigate.
For how long have I used the solution?
I've recently delved into using the product. I've been using the solution for at least the last seven or eight months or so. It's been less than a year. I haven't used it that long just yet.
What do I think about the stability of the solution?
The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. its performance is reliable.
What do I think about the scalability of the solution?
The scalability is limited if you want to scale externally. A company needs to keep that in mind.
I only launched my first application sometime around Christmas, or just after. It's still quite new. I have about a dozen or so people that move in and out of it. It's just a small app.
As a company, we are quite small. All of our users would be external. And, due to the fact that the solution gets expensive for external users, it's not a solution we plan to expand upon or use for the long term.
How are customer service and technical support?
The technical support is not easy to find. It's a bit of a well-kept secret. However, once you locate them, they are quite helpful and responsive.
Truthfully, they are hard to find due to the fact that you just don't realize they're there. I had spent a month, six weeks phoning around trying to find internet solutions to problems and resources and paying people to help me, and nobody knew the answer.
This was done without ever realizing that there was a very capable tech support resource available in Power Apps through the subscription. Once we found them, they were able to fix all of the issues we were struggling with very quickly.
How was the initial setup?
The initial setup is quite straightforward. A company shouldn't have any issues with the setup process. It's not overly complex.
What's my experience with pricing, setup cost, and licensing?
The pricing is excellent. It's not too expensive.
However, once you get into adding non-internal users, the solution can get pricey. It's only reasonable if you are trying to create internal team-based apps.
Which other solutions did I evaluate?
I haven't looked at any other low-code development platform.
What other advice do I have?
We're just customers and end-users.
We are using the latest version of the solution.
From a perspective of me doing a full test of the application and how I want it to run, it just met all of my needs and there are other storage locations for data. That said, the data is sitting in the CDS.
From my perspective, it was a great place to start and a great place to sit and test the waters. I'm looking to migrate it into something else in a little while. I won't stay with it forever. That's not the plan.
I'd rate the solution at a seven 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.
Buyer's Guide
Download our free Microsoft Power Apps Report and get advice and tips from experienced pros
sharing their opinions.
Updated: March 2026
Popular Comparisons
ServiceNow
Pega Platform
Salesforce Platform
OutSystems
Oracle Application Express (APEX)
GitHub CoPilot
Hyland OnBase
SS&C Blue Prism
QuickBase
Microsoft Azure App Service
ServiceNow Now Platform
Buyer's Guide
Download our free Microsoft Power Apps Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Would you choose ServiceNow over Microsoft PowerApps?
- How suitable is Microsoft Power Apps for complex applications?
- Would you choose Microsoft Azure App Service or PowerApps?
- What are the key factors to select between low-code platforms: Microsoft PowerApps vs ServiceNow?
- Which app builder do you use in Microsoft Power Apps and is it worth paying for?
- Is Microsoft Power Apps for businesses or for developers?
- How would you choose between Microsoft PowerApps and Salesforce Platform?
- Looking for recommendations for a no-code backend database for 500,000+ users - looking at CASPIO
- Help to migrate IBM Lotus Domino to another platform
- When should you use rapid application development and what are the most suitable projects for it?


















