PL-7001: Create and Manage Canvas Apps with Power Apps
Design, build, and ship canvas apps in Microsoft Power Apps — data sources, galleries, forms, Copilot-assisted authoring, and app lifecycle. Aligned to the Microsoft PL-7001 Applied Skills assessment.
View badge details
About This Course
Build production-ready canvas apps in Microsoft Power Apps from an Excel file, from Dataverse tables, or from a Copilot-generated starting point. By the end of the course you will be able to design and ship a mobile-friendly canvas app that connects to Excel, OneDrive, SharePoint, SQL Server, and Dataverse, presents data through galleries and detail screens, captures new data through validated forms, and gets published, shared, and version-controlled the exact skill set assessed by the Microsoft PL-7001 Applied Skills credential.
Course Curriculum
14 Lessons
Welcome to Power Apps — the Ridgefield scenario, data sources, and Copilot
Get oriented to Microsoft Power Apps and the low-code app-building discipline. You'll learn what canvas apps are and how they differ from model-driven apps, where they fit in the Microsoft Power Platform, how canvas apps reach their data through connectors (Excel, SharePoint, Dataverse, SQL, REST), and how Copilot in Power Apps changes the maker experience. You'll finish able to explain the Power Platform architecture to a colleague, choose the right data source for a business scenario, and describe the Ridgefield Property Services app you'll build across this course.
Set up your Power Apps environment and build your first Ridgefield apps - Lab Exercises
Sign in to make.powerapps.com as your Ridgefield lab user, confirm your dedicated environment is selected, and tour the maker Home page — then build your first two Ridgefield canvas apps. You'll upload a pre-built work-orders Excel workbook to OneDrive and generate an app from it (the fast prototype path), then generate a second app from a natural-language Copilot prompt (the modern first-draft path). You'll finish having proven the tenant is ready, compared the two starting points hands-on, and be ready to design real Ridgefield Dataverse tables in the next lesson.
Dataverse fundamentals — tables, columns, relationships, security
Learn Microsoft Dataverse — Microsoft's business-database platform underneath the Power Platform. You will understand what a Dataverse table is, how columns and choices and lookups work, when to reach for a relationship, and how row-level security through security roles lets Ridgefield give each field tech only their own work orders. By the end of this lesson you will be able to design a small Dataverse data model on paper and explain the tradeoffs against Excel and SharePoint.
Build the Ridgefield work-order Dataverse data model - Lab Exercises
Build the Ridgefield Dataverse data model from scratch. You'll create the Technician and WorkOrder tables with a lookup relationship, add Choice columns for Priority and Status, seed rows into both tables, define a Field Tech security role that limits row visibility, and add a business rule. You'll finish with the exact data model every downstream lab in this course builds on.
Canvas app screens, controls, and navigation
Learn the anatomy of a canvas app — screens, controls, control properties, the tree view, and the Power Fx formula language that binds it all together. You will understand galleries, forms, buttons, labels, and how to move between screens with Navigate() and Back(). By the end of this lesson you will be able to describe the control tree of any canvas app and know which control belongs on which screen.
Build the Ridgefield work-order canvas app from Dataverse - Lab Exercises
Build the Ridgefield Work Order mobile canvas app from scratch against the Dataverse tables. You'll create a browse screen with a sorted gallery, a detail screen bound to the selected item, wire navigation between the two, and add a floating action button for a New Order flow. You'll finish with your first hand-built canvas app on the real Ridgefield data model and be ready to brand it in the next lesson.
Canvas app UI — themes, icons, images, personalization, and form factors
Learn how to make a canvas app look like a Ridgefield app rather than a generic Power Apps default. You'll understand theming through App.OnStart global-variable patterns, using icons and images (including SVGs and base64), personalizing labels with User() functions, and designing responsive layouts that work on phone and tablet form factors. By the end of this lesson you will be able to plan the branding pass for any canvas app you build.
Brand the Ridgefield app with themes, icons, and mobile-first layout - Lab Exercises
Apply the Ridgefield brand to the canvas app you built in the previous lesson — green and gold color palette via App.OnStart global variables, the Ridgefield logo, priority-badge icons, a personalized welcome using User().FullName, and a phone-tablet responsive layout. You'll finish with the before-and-after muscle memory that turns generic Power Apps output into a branded business app.
External data — SharePoint, SQL Server, connectors, and delegation
Learn how canvas apps talk to data beyond Dataverse — SharePoint lists, SQL Server databases, and the wider connector ecosystem. You will understand the standard-vs-premium license split, how connections and connection references work, and the crucial concept of delegation: which Filter/Sort/LookUp calls Power Apps can push down to the source vs which run in-memory (breaking at scale). By the end of this lesson you will be able to add a SharePoint list and a SQL table to a canvas app and reason about whether your queries will still perform at 100,000 rows.
Integrate SharePoint properties list and Office 365 Users into the app - Lab Exercises
Extend the branded Ridgefield Work Order app with external data. You'll add a SharePoint list of properties as a data source for a browse-by-property view, use the Office 365 Users connector to show technician photos, trigger a delegation warning on a SharePoint filter, and fix it. You'll finish able to add standard or premium connectors to any canvas app and diagnose delegation issues.
Forms in canvas apps — modes, controls, validation, and submit patterns
Learn how canvas-app forms turn tables into fillable interfaces — display forms, edit forms, view mode vs edit mode vs new mode, DataCard controls, field-level validation, and the SubmitForm-Success-Failure lifecycle. By the end of this lesson you will be able to design a form flow that gracefully handles new records, existing-record edits, validation failures, and unsaved-changes prompts — the core interaction pattern of every business app.
Build the work-order intake form with validation and submit - Lab Exercises
Build the New Work Order intake form. You'll add an Edit Form control bound to the WorkOrder table, configure DataCard required flags and defaults, add custom validation for Critical priority, wire Submit and Cancel buttons with OnSuccess and OnFailure handlers, and add an unsaved-changes discard prompt on Back. You'll finish with production-quality form patterns you'll reuse in every canvas app you build.
Publishing canvas apps — sharing, versions, solutions, ALM
Learn how to ship a canvas app from your maker environment out to the actual people who will use it. You will understand Save vs Publish, the versions timeline, sharing scopes (user, group, everyone-in-tenant), solution packaging for dev→test→prod deployment, and the .msapp offline archive format. By the end of this lesson you will be able to hand a canvas app off to a real team and know how to update it without breaking their access.
Ship the Ridgefield app — publish, share, export, and hand off - Lab Exercises
Ship the Ridgefield Work Order app end-to-end in this course capstone. You'll run App Checker, publish the app, share it with a Ridgefield security group and a test user, export it as an unmanaged solution, download an .msapp offline backup, and practice rolling back to a prior version. You'll finish having taken the app from your maker environment all the way to a real hand-off — the exact pattern the Applied Skills credential validates.