While the feature remains listed as "In development" on the Microsoft 365 roadmap, it is slated for General Availability in October 2026 via weekly release channel version 2610.2 for web-based model-driven apps across Worldwide (Standard Multi-Tenant), GCC, and GCC High cloud instances. As with all Microsoft roadmap entries, these timelines and scope details represent current projections rather than a finalized rollout guarantee.
What Is Changing in Version 2610.2?
The update detailed in Roadmap ID 576178 focuses on two distinct areas: visual hierarchy and grid-level accessibility for first-party Dynamics 365 summaries.
- A Refreshed Visual Layout: Microsoft is redesigning the row summary container so AI-generated insights do not blend into the surrounding form fields. The updated treatment introduces clearer spacing, distinct background and border styling, status indicators, and explicit generation labels. Borrowed from the design language of AI-powered experiences across Microsoft 365 apps, this styling gives users a familiar visual cue that they are reading synthesized content. Microsoft also notes that this layout lays the groundwork for combining insights from multiple sources into a unified summary experience in the future, though no timeline has been set for that multi-source expansion.
- First-Party Dynamics 365 Summaries in Grid Views: Previously, out-of-the-box summaries provided by Dynamics 365 applications—such as those for Customer Service and Sales—were restricted to main forms. You had to open an individual record to read the AI summary. With this update, users can view those Microsoft-provided summaries directly from model-driven app view pages, inspecting record insights inline from a grid without clicking into each row one by one.
Section Summary: Version 2610.2 separates AI summaries from standard form fields using Microsoft 365-style visual borders and labels, while unlocking inline grid-view access for built-in Dynamics 365 Sales and Customer Service summaries.
Custom Row Summaries vs. Built-In Dynamics 365 Summaries
To understand why the grid-view update matters, it helps to look at how Microsoft divides the row summary ecosystem in Dataverse and Power Apps. According to Microsoft Learn documentation on configuring and using row summaries, there are two separate tracks at play:
| Feature Aspect | Maker-Configured Row Summaries | Built-in Dynamics 365 Summaries |
|---|---|---|
| Supported Tables | Most standard and custom Dataverse tables | Reserved tables like Case, Lead, and Opportunity |
| Configuration Method | Custom prompt via Tables > Customizations > Row summary | Managed through Dynamics 365 Customer Service or Sales settings |
| Where It Appears | Collapsible Insights bar on main forms and modal popups from view grids | Previously main forms only; expanding to model-driven app view grids in 2610.2 |
When a table already has a configured summary, users can view it from the collapsible Insights bar at the top of a main form or trigger an inline Summary action from a view page, which opens the summary in a modal popup and allows users to copy text, regenerate the output, or leave feedback. However, Microsoft blocks standard maker-configured row summaries on tables like Case, Lead, and Opportunity to prevent conflicts with the native summaries shipped by Dynamics 365 Customer Service and Sales. Bringing those first-party Dynamics 365 summaries into view grids closes an annoying usability gap between custom tables and core CRM tables.
Practical Guide: Prerequisites and Maker Configuration
Because the visual refresh in version 2610.2 is scoped to users as "always enabled" once a summary is present, administrators and makers should verify how their environment and tables are configured ahead of the rollout.
1. Environment and Security Prerequisites
- AI Insight Cards: Before any row summary can be configured or displayed, a Power Platform administrator must turn on the AI insight cards toggle in the environment's feature settings.
- Customer Service Privilege: Microsoft Learn documentation notes a specific gotcha for Dynamics 365 Customer Service: any user who needs to view summaries configured through the Customer Service app must hold a security role that includes the
prvReadLanguageLocaleprivilege. Furthermore, Microsoft’s broader 2026 release wave plans highlight efforts to let makers assign security roles to individual summaries to prevent missing-privilege errors.
2. Configuring a Custom Table Row Summary
If you are building a custom summary for a standard or custom table (outside of the locked Dynamics 365 tables), Microsoft Learn outlines the following workflow:
- Sign in to the Power Apps maker portal (
make.powerapps.com), select Tables from the left navigation pane, and open your target table. - Under Customizations, select Row summary. (Note: If the option is disabled, hover over the label to see why—for instance, a table must contain at least one row of data before you can configure a summary.)
- In the Prompt box, click Add or type
/to insert the specific columns you want Copilot to summarize. Specify your desired format (such as bullet points or a concise paragraph). - Ensure localization is handled: newly created summaries automatically include the
LanguageCodeinput and the instruction"You must respond in language <LanguageCode>."If you are editing an older, pre-existing summary, you must add that instruction manually; otherwise, Copilot generates the output in the language of the prompt itself rather than the user's preferred UI language (falling back to English if a user's language is unsupported). - Select Test prompt to preview the output using the table's most recently edited row, then click Apply to main forms.
Once applied, the summary automatically takes effect across all views and main forms for that table. Makers can verify which forms carry the summary by navigating to Tables > Data experiences > Forms, where an AI icon appears beside affected form names.
3. Moving Summaries Across Environments (ALM)
Row summaries are solution-aware, but moving them between development, test, and production environments requires care. In your solution, navigate to Add existing > More > Other > AI Skill Config and select only the rows corresponding to the tables where you created summaries. Microsoft explicitly warns makers not to include AI Skill Config rows owned by System, as those do not represent maker-created summaries and can cause solution imports to fail.
Known Technical Limitations to Keep in Mind
A sharper border and an explicit AI label will make summaries easier to spot, but they do not change what the underlying language model is good—and bad—at doing. If you are designing prompts to take advantage of the refreshed UI, Microsoft Learn documents several strict boundaries for row summaries:
- No Math or Date Logic: Row summaries do not perform arithmetic calculations on numeric columns, nor are they designed to calculate durations, compare dates, or derive statuses from date fields. Use Dataverse calculated or formula columns for math, and keep in mind that even formula and calculated column values may not always be reflected accurately by the summary generator.
- Metadata and Links: Choice (option set) labels, related-table associations, and hyperlinks to related records might not interpret or render as expected inside the summary block.
- Plain Structure: Rich formatting, footnotes, and citations are not supported inside the generated summary.
By aligning Power Apps forms with the broader Microsoft 365 Copilot aesthetic and eliminating the need to open individual Sales and Customer Service records just to get the gist of an account or case, version 2610.2 is a welcome quality-of-life upgrade. Just make sure your prvReadLanguageLocale privileges and AI Skill Config solution components are in order before your users start asking where their shiny new summary cards are.