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.

Grids — explore your data without leaving the conversation 

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 — create, view, and update records without leaving Copilot 

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.

Available across the Microsoft 365 apps you already use 

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.

Custom tools — coming soon 

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.  

Available now — get started today 

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!

The post Public Preview: Your business apps, now part of every conversation appeared first on Microsoft Power Platform Blog.

Imagine needing to find opportunities that should be reviewed this week. Simply type the query “Opportunities closing in the next 3 months” and let Copilot do the rest! This feature allows you to shift your focus from manually filtering and crafting views to analyzing data and obtaining valuable insights.

Try it now! The data exploration agent is available immediately via manual opt-in and is being rolled out through the Monthly Channel using the “Natural Language Grid and View Search” admin setting. 

For more details, visit Find records and filter views using natural language | Microsoft Learn and Explore data on a grid page – Power Apps | Microsoft Learn 

We are excited to see how your daily workflows improve with this new feature and look forward to hearing your feedback as we continue to evolve the data exploration agent. Stay tuned for future enhancements! 

The post Introducing the data exploration agent to quickly find records using natural language in model-driven apps! appeared first on Microsoft Power Platform Blog.

Visit overview of modern controls to learn more about all modern controls.  

As part of this milestone, we would like to highlight the following: 

• Text input has a trigger output property which can be used to control its onChange behavior 

• Date picker’s custom format can be achieved by editing the “format” property with a valid date format, i.e. format = “dd/mm/YY”, format = “MM/YY” 

• Combobox has a default limit of 800 records when using the dataset directly. However, makers can leverage PowerFX formulas in junction with the control’s searchText property to achieve dynamic searching and filtering on larger datasets, i.e.: Filter(<Dataset>, StartsWith(<Column name>, Combobox.SearchText)) 

• When a Number input is used standalone (outside of a form), its value will never exceed the max or min boundaries and will always round values to either one of the closest boundaries 

We look forward to hearing your feedback and seeing the amazing apps that will be created with these controls!  

The post GA announcement: 6 additional modern controls in Canvas!  appeared first on Microsoft Power Platform Blog.

Once a code component has been enabled on a form field or added to a webpage in the Pages workspace, you can contextually edit the corresponding properties for this component without leaving the workspace. Expand these properties by using the new “Edit code component” button from the component’s toolbar. In addition, you can preview the code components directly in the canvas within the Pages workspace. 

To learn more, check out “Edit code component properties on form fields” and “Edit code components in webpages” in the Power Pages documentation.  

Try out the experience in make.powerpages.microsoft.com! We look forward to hearing from you! 

The post Configure code components in the design studio available in public preview! appeared first on Microsoft Power Platform Blog.

Makers can now strike a balance between complex web templates and the ability for low-code makers to edit and configure them. With the release of the {% manifest %} liquid tag for web templates into public preview makers can specify which variables are to be exposed in the design studio along with a few relevant properties.  

With this addition, web templates can be extended, by using the {% manifest %} tag, to define the following properties:  

• Type (functional or layout): determines the web templates’ placement in the design studio for the “add” scenario in the future. 

• Description: allows makers to write a brief description of the web template for ease of collaboration.

• Display name: a friendly name to be used for the web template.

• Tables: an array of tables’ logical names that makers can define so that the low code editing experience is full circle where makers have a connection (through “Edit data”) from the Pages workspace to the tables directly, where they can edit the corresponding data records sourcing the data for the component.

• Params: an array of objects that bridge the gap between pro-devs and low-code editors when working with variables in a web template. Each param object contains: an id, matching exactly the variable being used in the source code and liquid tag in the page copy, a display name and description for ease of collaboration.

The gap in collaboration between the pro-dev and low-code makers regarding complex web templates editing has been significantly reduced with this approach. As a pro-dev, you can now format your source code in a way that allows low-code makers to configure variables and dictate the component’s functionality. This empowers makers through re-usability and ease of maintenance. Anywhere on the site where a component could be re-used with slight modifications would be a good candidate for this approach. Pro-devs can now empower low-code makers to have total control over the resulting UI elements on the page – based on the logic written and variables exposed by pro-devs. 

Think about creating a set of robust components, pulling data from the Dataverse, and having complex layouts that can be maintained in a single place while being re-used across the site. No need to duplicate and re-create web templates for slight changes, rather template the code and leverage variables through its manifest! 

To learn more about this feature, visit Web templates as components | Microsoft Learn and follow the sample How to: Create a web template component | Microsoft Learn, which showcases a basic but powerful scenario. As usual, we are looking forward to hearing your feedback and excited to see what amazing components result from this new addition! 

The post Low-code editing of web templates from the design studio now available in public preview!  appeared first on Microsoft Power Platform Blog.

Changes made in the Edit site header experience persist across the site and reflect in the Styling workspace. As makers make changes in the new experience, they can preview their changes instantly without having to switch between workspaces. 

Title + logo 

Makers can set their site title and logo along with alt text for accessibility. We are also providing makers flexibility to show/hide the logo to match their brand requirements. 

Styling 

Makers can set up their brand colors directly from this experience, allowing them to update their header styling and meeting brand requirements easily. The following styling configurations are now available from the site’s header: 

• Brand colors 
• Header background color 
• Title and navigation links styling 

Visit make.powerpages.microsoft.com to get started.  You can learn more about this new feature in the article “Edit site header”. As usual, we look forward to hearing from you! 

The post Set up your site’s brand: title, logo, brand colors, and more appeared first on Microsoft Power Platform Blog.

Color palette and using it from the Pages workspace 

The color palette has been re-organized to provide makers with a clear understanding and distinction between their brand colors and the rest of the colors in the site. Makers can now leverage the color palette from the Pages workspace without having to jump back and forth to the Styling workspace.  

Custom CSS for advance site styling 

If you want to take a step further and use advance CSS to style your site, you can use the ‘Manage CSS’ option to provide advance site styling to your site. Makers can upload multiple CSS files. Move up and down the CSS files to decrease or increase the precedence and even disable a file, with a preview of the site reflected right next in canvas. Custom CSS files can also be edited using VS Code. 

Visit the articles Style your pages site and Manage CSS files in Power Pages to find detailed information on these features and how you can start using them today to style your sites. As usual, we look forward to hearing from you! 

The post Styling the site to meet your needs: updated color palette and custom CSS   appeared first on Microsoft Power Platform Blog.