Domain 2 of 3

Create intelligent applications

Domain · 27.5% of the AB-410 exam

Ask who decides the layout before anything else

Building a warranty-claims app? First ask who decides the layout. In a model-driven app, the components you add to tables in Microsoft Dataverse (a structured store of rows and columns) decide much of the interface: forms (the editor for one row), views (a saved list of rows: columns, sort and filters), charts and dashboards. Those components use Dataverse only. In a canvas app you design every screen yourself and can use data outside Dataverse through connectors (Microsoft's comparison of the two app types). The trap is the hybrid case: canvas-authored content running inside a model-driven app, as a custom page (a full page, dialog or side pane) or an embedded canvas app (a canvas app placed on a model-driven form), is part of that app, not a standalone canvas app. Both can still reach other data (custom pages through connectors, embedded canvas apps through many data sources). The decision tree below walks this choice for canvas-authored content; a generative page (a page an AI agent generates as React code from your description) also belongs to the model-driven app and can use connectors (preview).

Two pages, one per app type

Reach for Create model-driven apps when a scenario names forms, views or dashboards, and for Create canvas apps when it names screens, controls or formulas in a standalone canvas app; canvas-authored content inside a model-driven app belongs to the first. The model-driven page covers composing an app in the app designer, choosing form types and views, deciding which forms and views each security role (a Dataverse bundle of privileges) is offered, sharing the app, building charts and dashboards, and extending the app with custom pages, embedded canvas apps and generative pages, which the app agent, an AI agent in the app designer, generates as React code from your description. The canvas page covers building on data with Power Fx formulas, designing for accessibility, performance, responsiveness and usability, calling Power Automate cloud flows, reusing logic and controls, managing variables and collections, handling errors, testing, and turning the app into a Microsoft Copilot Studio agent with agent builder (not the app agent).

Configure what the platform already provides before you build around it

When two answers both work, prefer the one that uses the platform's own mechanism. In a model-driven app that means the right component and setting: Microsoft recommends a custom page over an embedded canvas app in most cases, for tighter integration and better performance (overview of custom pages); the tree marks the exception, content that must sit on a model-driven form. In a canvas app it means letting formulas derive values, since most formulas recalculate automatically as values change, like an Excel spreadsheet, and writing queries the data source can run in full itself (delegation), because a nondelegable query processes only the first records up to the app's Data row limit setting (delegation in a canvas app).

Model-driven app vs canvas app: who decides the layout

App typeWho decides the layoutDataWhat you build withAI feature covered in this domainDrill into
Model-driven appThe components you add to Dataverse tables decide much of itDataverse only for table-based forms, views, charts and dashboards; custom pages and embedded canvas apps can use other data, and generative pages support connectors (preview)Forms, views, charts, dashboards and commands, plus custom pages and embedded canvas apps for canvas-authored contentGenerative pages, which the app agent generates as React code from your descriptionCreate model-driven apps
Canvas appYou design every screen yourselfDataverse and data outside it through connectorsControls whose properties hold Power Fx formulas, plus variables, collections, reusable canvas components and cloud flow callsCreate agent from app, where agent builder turns the app into a Copilot Studio agentCreate canvas apps

Decision tree

Design everyscreen yourself,or data outsideDataverse?NoModel-drivenappYesCanvas-authoredcontent inside amodel-driven app?NoStandalonecanvas appPart of a model-driven appYesMust sit on amodel-drivenform?YesEmbeddedcanvas appNoCustom page(full page,dialog or side pane)

Subtopics in this domain