AB-410: Building Intelligent Applications with Microsoft Power Platform
16-lesson course preparing learners for the AB-410 Intelligent Applications Builder Associate certification. Build Dataverse data models, canvas + model-driven apps, Power Pages portals, cloud flows, AI prompts, and Copilot Studio agents through the Contoso Service Hub scenario.
Exam Preparation Included
Practice with real exam-style questions for the AB-410 certification. AI-powered feedback helps you understand every answer.
About This Course
Build AI-powered solutions on Microsoft Power Platform with Copilot, natural language prompts, and low-code tools. This course prepares learners for the AB-410 Microsoft Certified: Intelligent Applications Builder Associate exam through 16 lessons covering Dataverse data modeling, security roles, model-driven and canvas apps, Power Pages portals, cloud flows, business process logic, AI Hub prompts, AI Builder prebuilt models, and Copilot Studio agents.The course is anchored by a single scenario Contoso Service Hub a 4-audience, 4-app service-management platform. Service agents handle customer cases; field technicians track service orders; employees submit self-service requests; operations managers approve asset requests. A customer-facing Power Pages portal exposes case submission; an FAQ Copilot and an internal Service Assistant layer in generative AI.Each lesson advances the Contoso Service Hub arc while mapping directly to AB-410 exam objectives: foundation (25-30%), creating intelligent applications (25-30%), and building business application logic and automation (40-45%).
Course Curriculum
31 Lessons
Lesson 1: Course Overview and Prompt Engineering Foundations
Orientation to the AB-410 exam, the Contoso Service Hub scenario, and the four prompt-engineering techniques (specificity, persona + context, output constraints, few-shot examples) that unlock Copilot across Power Platform. By the end, learners can diagnose a weak prompt, apply each technique to strengthen it, and name where Copilot shows up across Power Apps, Power Automate, Power Pages, Dataverse, Copilot Studio, and AI Hub.
Lesson 2: Dataverse schema design and the Plans experience
Before you build the Contoso Service Hub data model, you need to think about it. This teaching lesson introduces the Plans experience as an AI-driven solution designer, explains the Dataverse building blocks (tables, columns, relationships, publishers and prefixes, solutions), and sets up the design decisions you will execute in Lesson 2 hands-on. By the end: name the four exam objectives Create and modify tables and Configure table relationships touch; justify why the course picks a custom contoso_case over the standard Dynamics 365 incident; and read a Plans output critically.
Lesson 2: Design the Solution with Plans and Build the Dataverse Data Model - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Design the Contoso Service Hub solution with the Power Apps Plans experience, then build the Dataverse data model that every subsequent lesson relies on. Learners create a solution with a contoso publisher prefix, add the Account and Contact standard tables (pre-seeded with sample Contoso customers), build the custom contoso_case table with 11 columns (including an autonumber Case Number and a formula SLA Due), and configure the one-to-many relationships that chain Account → Case, Contact → Case, and User → Case. This is the schema baseline every subsequent lesson's env template rolls forward.
Lesson 3: Prompt columns and row summaries explained
Two Dataverse AI features sound similar but solve different problems. This teaching lesson draws the distinction: prompt columns are persisted AI-generated values that run on insert/update of referenced columns; row summaries are rendered-at-form-open paragraphs that appear in the Insights bar. Learners cover the trigger model, when each fires, Copilot Credit cost patterns, and the gotchas of filter clauses + LanguageCode inputs. By the end: pick the right feature given a business requirement, size the Copilot Credit cost of a 10,000-row table, and name why row summaries don't work on the Dynamics 365 Case table.
Lesson 3: AI-enabled columns — Prompt columns and Row summaries - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Add AI-powered Dataverse columns to the Contoso Service Hub Case table. Learners import the Lesson 2 schema solution to bootstrap the contoso_case table, then enable AI features on their per-student env, create two prompt columns (AI Summary + AI Suggested Priority) that run generative AI against row data on save, apply a Status filter so the summary skips closed cases, configure a Row Summary that renders a Copilot-generated at-a-glance paragraph on the Case main form (with LanguageCode input for multi-language users), and build a new contoso_faq table plus the many-to-many relationship contoso_case to contoso_faq. By the end of the lesson, opening any Case row shows an AI summary, a model-suggested priority, and a dedicated insights bar — plus FAQ articles can be associated with cases bidirectionally. Covers exam objectives Configure prompt columns and Configure row summaries, both weighted on the current AB-410 exam blueprint.
Lesson 4: Security roles and business rules
Access control in Dataverse is scope-based, not just role-based — a security role grants privileges at User, Business Unit, Parent-Child BU, or Organization scope. This teaching lesson walks the four scopes, the eight privilege types, and when to use a business rule versus a formula column versus a cloud flow for enforcing logic. By the end: pick the right scope for a given role, name the eight privileges (Create/Read/Write/Delete/Append/AppendTo/Assign/Share), and distinguish Entity vs All Forms vs Specific Form scopes on business rules.
Lesson 4: Security roles and business rules - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Lock down the Contoso Service Hub Case table with security roles that scope what agents and managers can do, then declaratively enforce business logic without writing code. Learners build two custom security roles (Contoso Service Agent at User scope, Contoso Service Manager at Organization scope with Assign + Share), add two business rules to contoso_case (Priority Critical requires Assigned Agent; Status Resolved auto-sets Resolved On to today), and finish with a rollup column on Account that counts open child cases. Covers exam objectives Configure security and Configure business rules + rollups — both weighted on the current AB-410 blueprint and not covered by the Microsoft AB-410T00 labs.
Lesson 5: Model-driven app composition
Model-driven apps are composition — you point at tables, Dataverse builds UI. This teaching lesson explains the modern app designer, sitemap concepts, main form structure (sections, tabs, Insights bar), the three view types (public/personal/system), classic charts, and how dashboards compose views + charts. By the end: structure a sitemap that respects user mental models; pick a public view over a personal view; and choose a pie, bar, or line chart for a given metric.
Lesson 5: Build the model-driven Customer Service App - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Compose the Contoso Service Hub Case table, Account, Contact, and the AI columns from Lesson 3 into a working model-driven app that agents and managers use day to day. Learners build the Contoso Customer Service model-driven app, customize the Case main form to surface AI Summary + AI Suggested Priority prompt columns and a Resolution tab, create two views (My Open Cases and Critical Cases), build two classic charts (Cases by Priority pie and Cases by Status bar), assemble a Service Agent Dashboard, and finish by sharing the app with the Contoso Service Agent and Contoso Service Manager roles from Lesson 4. Covers exam objectives Create model-driven apps, Configure forms and views, Create charts and dashboards, Configure app access.
Lesson 6: Canvas apps + AI flow integration
Canvas apps are pixel-level, form-factor-specific — phone vs tablet, portrait vs landscape — and give the author control over every control's placement. This teaching lesson covers canvas composition (screens, galleries, forms, variables), calling cloud flows from canvas (manual trigger + Return action), and the AI Builder prompt-action pattern that classifies text server-side. By the end: compose a phone-form canvas app shell; invoke a flow with text input and read the response; use Copilot in the formula bar.
Lesson 6: Build the Service Request Tracking App (canvas) with AI priority - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Build the Contoso Technician App — a phone-form canvas app that field technicians use to view and update service orders tied to open cases, with an AI-powered priority suggestion backed by a cloud flow. Learners create the contoso_serviceorder table, build List and Detail screens bound to it, author a SuggestPriorityFlow that calls AI Builder's text-generation prompt action to infer priority from on-site notes, wire the flow to a Suggest priority button on the Detail screen, and use the Copilot-in-formula-bar to generate Power Fx for the Save button. Covers exam objectives Create canvas apps using data, Automate business processes from canvas apps, Integrate AI prompts/models.
Lesson 7: Responsive canvas apps, named formulas, and user-defined functions
Canvas's modern patterns — containers for responsive layout, App.Formulas for named shared values, user-defined functions for parameterized reusable logic — are the exam-weighted techniques that separate novice from intermediate canvas authors. This teaching lesson covers responsive container patterns, the difference between App.Formulas and variables, UDFs with typed parameters + return, and the Accessibility checker.
Lesson 7: Build the Employee Self-Service App with accessibility, responsiveness, and UDFs - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Build the Contoso Employee Self-Service App — a responsive tablet-form canvas app that employees use to submit HR, IT, and facility requests, then track their own request history. The build teaches the modern canvas patterns the exam weighs: responsive containers, accessibility labels and tab order, named formulas (App.Formulas) for shared values, user-defined functions (App.Formulas with parameters), collections for client-side scratch state, and the Monitor tool to catch delegation warnings. Learners create the contoso_employeerequest table, build Submit + My Requests screens with responsive containers, define App.Formulas.CurrentUserDisplayName and an UrgencyColor UDF, pass an accessibility audit, and use Monitor to find and fix one delegation issue. Covers exam objectives Design apps for accessibility/performance/responsiveness, Create reusable components (named formulas + UDFs), Test canvas apps using Monitor.
Lesson 8: Component libraries and error handling
Component libraries package reusable canvas controls across apps in the same env; error-handling functions (IfError, IsError, Error, Notify) wrap writes to surface failures gracefully. This teaching lesson covers component authoring, custom properties (Input/Output/Behavior), library versioning, and the IfError + Notify pattern. By the end: pick when a component belongs in a library vs inline, choose the right custom-property type, and implement a safe Patch wrapper.
Lesson 8: Build the Asset Request App with component libraries and error handling - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Build the Contoso Asset Request App alongside a reusable component library that every subsequent app can import. Learners create the contoso_assetrequest table, publish a Contoso Shared UI component library containing a branded header, a Status badge, and a confirmation dialog, build the Asset Request App Submit/My Requests/Approvals screens using those components, wrap all Patch calls in IfError + Notify error-handling patterns, and finish by swapping the shared Header into the Employee Self-Service App from Lesson 7 — proving library reuse. Covers exam objectives Create reusable components, Create component libraries, Implement error handling.
Lesson 9: Monitor, performance patterns, and testing
Measuring canvas-app performance separates authors who ship fast apps from those who ship slow ones. This teaching lesson covers Monitor during authoring + from published apps, the common performance anti-patterns (per-row flows, non-delegable filters, Set-in-loop), delegation vs client filtering, and Application Insights instrumentation. By the end: capture a Monitor session, diagnose a delegation warning, pick a delegable filter rewrite.
Lesson 9: Monitor, performance, and testing canvas apps - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Capstone to the Create-intelligent-apps section — teach the student how to measure canvas app performance and systematically fix the common anti-patterns. Learners open the Service Request Tracking App from Lesson 6 in Monitor, identify slow Dataverse calls and non-delegable formulas, refactor one gallery filter to be delegable, capture a Monitor session from the published app, add Azure Application Insights telemetry via an instrumentation key, and submit a short written performance review that assesses what they changed and why. Covers exam objectives Test canvas apps using Monitor, Performance patterns, Instrument canvas apps with telemetry.
Lesson 10: Cloud flow fundamentals — triggers, connectors, actions
Cloud flows are the Power Automate workhorse. This teaching lesson covers the three trigger families (automated/instant/scheduled), the connector catalog (standard vs premium), expression basics (triggerOutputs, body, OData), conditions, loops, error handling in flows, and how to read run history. By the end: pick a trigger for a given scenario, write an OData filter against a Dataverse lookup column, diagnose a failed run from run history.
Lesson 10: Cloud flows I — triggers, connectors, and Dataverse automation - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Shift from Power Apps to Power Automate. Build the first cloud flow of the course — a Case Created audit log that triggers when a contoso_case row is added, posts to a Teams channel, and extends to a condition (only post for High+ priority), a loop (iterate related service orders), and a run-history diagnostic (fix a deliberately broken OData filter). Covers exam objectives Recommend cloud flow triggers, Evaluate connectors, Configure actions, Implement conditions and loops, Test and troubleshoot flows.
Lesson 11: Child flows and the notification-framework pattern
Child flows are callable sub-flows that let you encapsulate reusable automation (notify a user, create a case, send approval). This teaching lesson covers child-flow prerequisites (must live in a solution), Switch-based channel routing, parent-child invocation, and the User-table preferred-channel pattern. By the end: author a child flow, invoke it from a parent, route by a user's preferred channel.
Lesson 11: Notification framework with child flows and channel routing - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Build a reusable notification framework — a Notify Agent child flow that accepts an agent user ID, a case ID, and a preferred channel, then internally sends an email, a Teams DM, or both based on the channel parameter. The parent flow Case Assigned Notification fires on Assigned Agent change and invokes the child. Covers exam objectives Configure cloud flow actions, Recommend connectors, Child flow reuse patterns.
Lesson 12: Approvals and parallel-approver patterns
The Approvals connector pauses a flow and waits for human responses. This teaching lesson covers the four approval types (Approve/Reject - First to respond, Everyone must approve, Custom responses - Wait for all / Wait for one), parallel vs sequential approvers, Switch on outcome, and the Responses array that carries per-approver detail. By the end: pick the right approval type for a scenario, read a Responses array, understand what happens when one of N approvers rejects.
Lesson 12: Approval process with parallel approvers - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Build the Asset Request Approval flow — automated trigger on contoso_assetrequest created, filtered to requests over $500, uses the Approvals connector with Approve/Reject Everyone must approve assigned to the requestor's manager and a Finance approver, Switch on outcome updates the request status and emails the requestor with the result. Covers exam objective Manage approvals by using cloud flows.
Lesson 13: Business Process Flows and customer onboarding automation
Business Process Flows (BPFs) are visual guided-process layers on top of Dataverse tables — stages + per-stage required columns + Next-stage gating. Different from cloud flows: BPFs enforce an in-form user journey, flows run server-side background. This teaching lesson covers BPF concepts, when to pick BPF vs cloud flow, and the customer onboarding automation pattern that combines Account trigger with Contact + Case + Teams + Email actions.
Lesson 13: Customer onboarding and the Business Process Flow - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Build the customer onboarding automation and the Case Lifecycle Business Process Flow. The onboarding flow fires when a new Account is created, provisioning a placeholder Primary Contact, a welcome email, a Teams post, and a kickoff Case so the sales handoff to service is automatic. The Business Process Flow drives Case Lifecycle through five stages (Intake, Triage, In Progress, Resolution, Closed) with required fields per stage. Covers exam objectives Implement business and process logic via Business Process Flows and Configure cloud flow actions.
Lesson 14: AI Hub prompts and prebuilt AI Builder models
AI Hub is Power Platform's reusable prompt library. Prebuilt AI Builder models (sentiment, invoice, business card, receipt) are ready-to-use without training. This teaching lesson covers AI Hub prompt authoring (knowledge grounding, inputs, variants), consumption from apps + flows, and the prebuilt model catalog. By the end: design a Dataverse-grounded prompt, consume it from a flow, pick the right prebuilt model for a document.
Lesson 14: AI Hub prompts — Case Summarization and Sentiment Analysis - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Shift from standalone prompt columns to a reusable AI Hub prompt library. Build a Case Summarization prompt grounded on contoso_case data, consume it from a model-driven app page via a cloud flow, and layer in prebuilt Sentiment Analysis that enriches new cases with a sentiment score. Covers exam objectives Create prompts and models in AI Hub, Build prompts from templates or blank, Consume a prompt in apps and cloud flows, Add knowledge to a prompt, Add inputs to a prompt, Consume an AI model.
Lesson 15: Document processing — prebuilt and custom models
Document AI pattern: prebuilt handles common formats; custom models handle layouts the prebuilt misses. This teaching lesson covers the Invoice Processing prebuilt output shape, when + how to train a custom document model, and chaining prebuilt + custom in a single flow. By the end: pick the right model for a format, understand the training workflow (5+ labeled samples), chain two models with conditional execution.
Lesson 15: Document Processing with prebuilt and custom AI Builder models - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM, a per-student Power Platform environment, and a per-student SharePoint site (with the Contoso-Invoices document library) at start — allow up to 15 minutes for the environment to become ready before beginning the exercises. Your Contoso Invoices site URL appears on the Environment tab under Lab Resources.
Automate invoice intake with the prebuilt Invoice Processing AI Builder model and layer in a custom document-processing model trained on Contoso's own Service Report PDF layout. Learners create the contoso_invoice table, build an Invoice Processing flow that triggers on new files in the per-student Contoso-Invoices SharePoint library, calls the prebuilt model, writes extracted fields to Dataverse, trains a custom document model on 5 sample Service Report PDFs, and chains the custom model after the prebuilt via vendor filter. Covers exam objectives Consume an AI model in cloud flows, Customize prompt settings (parallels model inputs), Add inputs to a prompt.
Lesson 16: Power Pages, Copilot Studio, and the capstone architecture
The capstone combines two external-facing surfaces: Power Pages (customer-facing portal) and Copilot Studio (conversational agents for customers + internal managers). This teaching lesson covers Power Pages structure (sites, pages, forms, table permissions, anonymous vs authenticated), Copilot Studio composition (topics, generative orchestration, knowledge sources, channels), and the capstone architecture that composes every previous lesson's artifact. By the end: pick anonymous vs authenticated table permissions; distinguish topics from generative answers; identify when to split into two agents vs unify.
Lesson 16: Capstone — Power Pages portal, Copilot Studio FAQ, and Service Assistant - Lab Exercises
Note: This lab pre-provisions a Windows 11 VM and a per-student Power Platform environment at start — allow up to 15 minutes for the environment to become ready before beginning the exercises.
Capstone lesson. Build the customer-facing Contoso Support Portal with Power Pages, the FAQ Copilot that answers knowledge-base questions on that portal, the Service Assistant that briefs internal agents on cases, and test the full flow end-to-end: anonymous customer submits a case from the portal, FAQ Copilot escalates when asked for a human, the case lands, Service Assistant summarizes it for the agent, and the notification + approval flows from Lessons 11-12 fire. Covers exam objectives Create portal + Copilot experiences, Add knowledge to prompts, Copilot Studio agent from a canvas app pattern (adapted to portal entry).