The July/August 2026 Power Platform update ships the data grid control to general availability for canvas apps and introduces flow groups to Power Automate. MSPs managing client environments and IT admins governing internal low-code deployments need to decide now whether to migrate classic table controls and consolidate automation licensing before client environments drift into inconsistent control frameworks and over-provisioned flow capacity.
What’s changing
Microsoft’s July/August 2026 Power Platform update centers on three operational shifts. First, the data grid modern control reached general availability for canvas apps. It is a Fluent UI-based successor to the classic table and data table controls, adding built-in search, sorting, multiple selection modes, richer column types, and accessibility improvements. Microsoft provides a table-to-data-grid update path but explicitly frames this as a distinct new control, not a forced deprecation — classic controls remain supported. Second, Power Automate now supports flow groups: a single process license (or 250,000 actions per day) shared across up to 25 solution-aware cloud flows. Flows needing more capacity can still get a dedicated process license. Third, modern controls across canvas apps gained consistent property names, a true read-only view, and improved checkbox and toggle behavior, standardizing how makers configure UI elements. A Power Pages security agent preview also appears in this update, providing site security guidance and configuration assistance, though it remains early-stage.
Why operators should care
The data grid GA changes how you sequence canvas app maintenance. Any app displaying dense tabular data with search or sort requirements is a migration candidate, but the update path requires testing in a dev environment first — property names and behaviors differ enough that a straight swap will break some apps. Apps using classic tables for simple display can stay as-is; there is no deprecation clock forcing action. For MSPs, this means auditing client environments for classic table usage and prioritizing migration only where the data grid’s capabilities justify the effort. Flow groups have a more immediate licensing impact. If you are running multiple small client flows each on its own process license, you can now consolidate up to 25 solution-aware cloud flows under one license and share the 250,000 daily action pool. That cuts licensing costs for moderate, predictable workloads — but only if you monitor shared capacity, because one heavy flow can exhaust the pool and starve the other 24. Keep dedicated licenses for high-volume flows.
Flow groups allow one process license (or 250,000 actions per day) to be shared across up to 25 solution-aware cloud flows.
The missed signal
The non-obvious story here is the quiet standardization of modern controls alongside the data grid GA. Microsoft is not just shipping one new control — it is aligning property names, read-only behaviors, and interaction patterns across the modern control family. That means apps you migrate to the data grid today will be easier to maintain alongside other modern controls tomorrow, but apps you leave on classic controls will increasingly diverge from the baseline. The operational risk is not forced obsolescence; it is gradual inconsistency. Client environments with a mix of classic and modern controls become harder to support, harder to document, and harder to hand off between engineers. The flow groups feature has a similar hidden dynamic: it rewards environments where flows are already solution-aware and punishes those where they are not. If your client flows are not solution-aware, flow groups are invisible to you until you fix that.
What to do next
Audit canvas apps across client and internal environments for classic table and data table controls. Identify which apps have dense tabular data, search, or sort requirements — those are your migration candidates. Test the data grid control in a dev environment for at least one complex app to understand the property-name and behavior differences before committing to broader rollout. Skip migration for simple display-only apps where the classic table works fine; there is no deprecation pressure.
Review your Power Automate licensing across all clients. Identify flows currently on individual process licenses that run at moderate, predictable volumes. Consolidate up to 25 solution-aware cloud flows under a single flow group and shared process license. Verify that all candidate flows are solution-aware — non-solution-aware flows cannot join a group. Move high-volume or unpredictable flows to dedicated process licenses to prevent capacity exhaustion.
Set up monitoring for the 250,000 daily action limit on any shared flow group. One runaway flow can consume the entire pool and silently throttle the other flows in the group. Alert on daily action consumption above 70% of capacity.
Flag the Power Pages security agent preview for awareness but do not deploy it in production environments yet. It is early-stage and not a migration item. The Power Automate plugin for AI coding agents (GitHub Copilot CLI, Claude Code) is likewise preview-stage — worth a look, not a rollout decision.
Sources
- Power Platform July/Aug 2026: GA Data Grid Now Available (Microsoft Power Platform Blog)
