Power Apps Widgets Bring Interactive App UI Into Copilot Chats
Diesen Beitrag auf Deutsch lesen
Built-in Model-driven App MCP widgets and custom Power Apps widgets bring forms, grids and Dataverse data into Copilot conversations.
TL;DR
Power Apps can expose Model-driven App views and forms as MCP Apps in M365 Copilot Chat. Developers can also define custom tools with prompt instructions, Dataverse inputs and optional self-contained HTML widgets that receive JSON output and communicate with the chat host.
Original on Dianamics PCF Lady. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Activate the App MCP capability for a Model-driven App to expose built-in record and data tools, then download its app package for deployment.
- Makers: Define clear custom tool names, descriptions and instructions, because M365 Copilot uses them to decide when to call a tool.
- Admins/IT: Plan for Teams or M365 deployment rights, since developers without the required permissions may need organizational approval before uploading the app.
- BI/Data teams: Check Dataverse fields, JSON output and linked-table behavior carefully, because the examples show useful filtering alongside some lookup and related-data limitations in preview.
Frequently asked questions
How do Model-driven App MCP widgets work in M365 Copilot Chat?
They expose Model-driven App views and forms as interactive MCP Apps, allowing users to view, create and edit records within the conversation.
How do I activate built-in MCP tools for a Power Apps Model-driven App?
Open the app in the maker portal, select App MCP, and choose Set up MCP. The app then provides built-in record and data tools.
What does a custom Power Apps UI widget need to contain?
It needs self-contained HTML that consumes the custom tool’s JSON output and communicates with the MCP host. The UI definition is optional.