Microsoft shows Power Apps acting as Copilot agent screens
Reviewed by Helen Jones
Microsoft 365 Developer highlighted a demo in which a model-driven Power App becomes the interface for a Microsoft 365 Copilot agent. The build uses the Power Apps MCP server so the agent can work with interactive grids, forms, and Dataverse updates inside the app experience. Related Power Apps MCP work also covers closed-loop learning. When users correct the agent in the feed, those fixes can be stored as structured memory and reused on later runs, with patterns consolidating over time. Coverage so far centers on data-entry style tools, and the features still sit behind normal preview, licensing, and governance limits.
For most internal makers, Power Apps still means a canvas app on a SharePoint list: galleries, forms, Patch, and maybe a Power Automate approval. Agents, MCP servers, and model-driven shells lived in a separate Copilot conversation that did not change how you ship a request tracker next week. That split is starting to blur on paper. Microsoft is treating the app itself as the place people correct and complete agent work, not only as a form they open after chat. The catch for non-developers is the stack: this path assumes model-driven apps and Dataverse, not the SharePoint canvas pattern most departmental apps use today.
Analysis
Treat this as a trend to watch, not a reason to rebuild your current SharePoint canvas app. Watch the April Dunnam demo once, confirm whether your tenant even has Dataverse and Copilot agent access, and only then decide if any future app should be model-driven instead of another list-backed canvas screen.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Microsoft shows Power Apps acting as Copilot agent screens", Collab365 Spaces. 3 sources referenced.