Understanding Power Apps Components
Start course

Microsoft Power Apps is a low-code/no-code solution that allows professional developers and non-IT professionals to create powerful applications much faster than with regularly developed applications. In this course, we will look at the core capabilities of Power Apps and how they help businesses automate and enhance repetitive, mundane, and time-consuming tasks.

We will cover canvas apps, model-driven apps, and portals, as well as their use cases and the differences between them. We'll also walk you through how to build each one. Finally, we'll take a look at the Power Apps Component Framework and how this allows developers to add even more functionality to standard Power Apps.

Learning Objectives

  • Get a foundational understanding of canvas apps, model-driven apps, and portals, including their use cases and features
  • Use data sources, controls, and formulas to build, share, and publish your own canvas apps
  • Plan, build, share, and publish model-driven apps
  • Create and customize your own portal and monitor user behavior on your portal
  • Learn about the Power Apps Framework and how it can enhance the user experience of your apps

Intended Audience

This course is intended for both IT professionals and non-technical professionals looking to automate and enhance business processes for mobile and desktop users.


There are no prerequisites for this course but any computer coding knowledge and even basic Excel knowledge would be beneficial when learning about Power Apps.


Power Apps components are reusable app pieces that can be integrated into other Power Apps applications. They are especially useful when creating multiple applications that are similar and allow all app creators in the same company to standardize their applications with less effort. For example, if I built a header component inside one of my apps, instead of trying to recreating it multiple times in that same app, in any other app I create, or trying to have other app makers replicate my header control, I could simply reuse this component inside of other applications that I build as well as share it with other app creators in my company.

This next concept is very important to understand. If the same component is being used inside of multiple different applications, I CAN'T just change one component and it will change all of the same components being used inside of DIFFERENT applications. That kind of global instance where all of my Power Apps are just looking at one version of the component doesn't exist in Power Apps. When app makers export or import components, they are creating local versions or copies of the original component within the app. This does mean that if the same component is being used multiple times inside of the SAME application, any changes made to it will show in all instances or places where the component is being used inside of that particular application.

In the next section, we'll create a Power Apps component.

About the Author

Ben is a Power Apps and Power Automate Specialist for Sovereign SP and has been using Power Apps, Power Automate, and SharePoint since 2017. Since then, he has built 100+ solutions using these amazing Microsoft tools. He loves helping others realize what technology can do and how it helps automate and enhance business processes. Most of all, though, he loves how these tools help make people’s jobs easier. The phrase, “This will make things so much easier!” is why he's in the IT business.

Ben Fetters lives in South Ogden, Utah, with his amazing wife and brand-new baby girl. A Weber State University Business Administration graduate, he loves to create businesses and help current businesses improve.