Today, we’re taking the first step to bring your Power Apps directly into Microsoft 365 Copilot—so key parts of your model‑driven apps can show up right where your users already work, powered by your app’s MCP server.

Think about the last time you needed business data mid-flow—building a PowerPoint and needing the latest account details or drafting a follow-up email and wanting to confirm a record before hitting send.  You had to open a separate tab, navigate to the right view, find what you needed, and switch back – unnecessary context switching. That’s the gap we’re closing.

Starting today in preview, you can engage your model-driven apps in Microsoft 365 Copilot — giving users conversational access to their business data and giving makers a way to bring their app’s value into the flow of work. The connection is made through your app’s MCP server—a lightweight setup in Power Apps that’s automatically created and configured for your model‑driven app, registering it as an agent in Copilot and making its data available as conversational capabilities. The experience is built around three capabilities: out‑of‑the‑box grids and forms available now, and custom tools coming soon.

Ask Copilot a question about your business data — “Show me open accounts in the West region” or “Which cases were escalated this week?”— and it responds with an interactive grid drawn directly from your Power Apps data. Users can filter, sort, and scan records using the same views and permissions as the app itself. 

Selecting a record opens it inline, where users can review details, make edits, or keep the conversation going — asking follow-up questions, comparing records, or taking the next step without starting over. And when users need a full screen experience, a deep link is always available — one click takes them directly to the relevant view or record in the full app. 

Forms go beyond read-only access. Users can create new records, view existing ones, or update fields—all directly in Copilot. Imagine receiving a supplier email and asking Copilot to create a new account record from it, or reviewing a contract in Word and logging the key details into your CRM without switching apps. 

Copilot surfaces the right form and, using the same underlying technology as the data entry agent in Power Apps model‑driven apps, intelligently predicts field values based on the context at hand — reducing manual input and making data entry feel effortless.

These experiences aren’t limited to the Copilot chat canvas. They’re available in the Copilot surfaces across Microsoft 365—Word, Excel, PowerPoint, and more—so users can access and act on their business data right alongside the document, spreadsheet, or presentation they’re working in.

Imagine drafting a proposal in Word, opening Copilot directly within the application, and creating a new account record with fields prefilled from the document—without switching apps, without copy and pasting, without losing context.

Need to go deeper? Both grids and forms include a deep link into the full model-driven app. One click takes users directly to the relevant record or view—no navigation, no searching, context preserved. It’s not a context switch; it’s a handoff to exactly where they need to be.

For scenarios where a grid or form isn’t sufficient, makers can build custom tools — defining their own logic and UX to meet the specific needs of their users. 

Grids, forms, and custom tools are the foundation. As we learn from this preview, we’ll expand the ways makers can extend their apps into Copilot — across more surfaces, more scenarios, and deeper integrations with the Microsoft 365 ecosystem.  

Your model-driven apps are now available in Microsoft 365 Copilot in public preview. Once a maker activates their app’s MCP server for a model-driven app, grids and forms will light up in Copilot automatically – no redesign required.

How to get started

1. Activate your app’s MCP server in Power Apps. This exposes your app’s data and experiences as callable capabilities in Microsoft 365 Copilot, with grids and forms surfacing automatically from your existing configuration. 

2. Download the app package generated by your app’s MCP. This package contains the agent definition and configuration needed to deploy your app’s experience to Microsoft 365. 

3. Deploy to Microsoft Teams or Microsoft 365. Upload the package to your tenant, and your users can immediately start interacting with your app’s data through Copilot—no further setup required on their end. 

Requires a Power Apps model‑driven app with Dataverse. This preview requires a Microsoft 365 Copilot license and a Power Apps Premium license. Custom tools—for exposing app‑specific actions beyond grids and forms—will be available in the coming weeks. Stay tuned!