Power Apps
What is Power Apps?
Quick answer
Microsoft Power Apps is a low-code application development platform for building business applications on data from Dataverse, SharePoint, SQL Server, and hundreds of connectors. Canvas apps give makers full control over layout and formulas; model-driven apps generate consistent data-management UI from Dataverse tables, forms, and views; Power Apps Code opens the same platform to professional React and TypeScript development with source control.
Key takeaways
- Canvas for custom UX, model-driven for Dataverse data ops, Code for pro-code.
- SharePoint starts simple; Dataverse scales with governance.
- Check premium-connector and capacity licensing per scenario.
Detailed Explanation
Microsoft Power Apps is a low-code application development platform for building business applications on data from Dataverse, SharePoint, SQL Server, and hundreds of connectors. Canvas apps give makers full control over layout and formulas; model-driven apps generate consistent data-management UI from Dataverse tables, forms, and views; Power Apps Code opens the same platform to professional React and TypeScript development with source control.
How it works
Pick the path by need: custom task UX → canvas with Power Fx formulas; structured data management → model-driven on Dataverse; full code control → Code apps via PAC CLI. All three share environments, solutions, connectors, and Dataverse where used.
Limitations and considerations
Canvas apps over SharePoint hit delegation and scale ceilings on large lists; model-driven apps require Dataverse with its licensing and ALM discipline; premium connectors and Dataverse capacity change the cost picture — verify current licensing per scenario.
This Q&A page is the short-answer layer for “What is Power Apps?” Use the related guides below when you need implementation steps, architecture trade-offs, or troubleshooting detail.
For broader context, visit the Power Apps Code Hub. It connects this topic to surrounding Microsoft 365, Power Platform, SharePoint, Copilot Studio, Dataverse, migration, and Dynamics 365 guidance.
When to use it
Use canvas for focused departmental tools, model-driven for CRM-style data operations, and Code when the team needs components, testing, and pipelines beyond the studios.
Practical example
A facilities team ships a canvas room-booking app on a SharePoint list in weeks, then graduates the asset register to a model-driven app on Dataverse when relationships and security outgrow lists.
Related Questions
Related nextM365 Guides
Sources
- Microsoft Learn: Power Apps documentation, Microsoft
- Microsoft Learn: Code Apps, Microsoft
- Microsoft Learn: Powerapps Overview, Microsoft