In development MRC 572682

Power Apps: Control information density in model-driven apps

Model-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options: Comfortable (default) Cozy Compact ​ Each density setting adjusts layout spacing while main

Power Apps 03 Horizon08 Adoption

DIGITAL SKILL WORKS LTD / 12 PANES

GA / disclosure November CY2026
Preview September CY2026
Platforms Web

What it is

Power Apps: Control information density in model-driven apps is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.

What it does

Model-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options: Comfortable (default) Cozy Compact ​ Each density setting adjusts layout spacing while maintaining accessibility target-size requirements. Administrators and makers can configure default density settings at the environment and app level, while individual users can personalize the experience by selecting their preferred density. User preferences take precedence over administrator-configured defaults. ​ Display density requires the Header and Navigation Refresh experience to be enabled, and will be enabled by default for apps that have Header and Navigation Refresh enabled. Makers can disable display density for their apps using the app setting if needed. ​ Some controls and components may not yet support display density. These controls will continue to render using their standard spacing regardless of the selected density setting. Custom component developers can add support for display density by adopting Fluent design spacing tokens. Learn more in the documentation. ​ Availability Field Value Applies to Model-driven apps Release channel Weekly Version 2609.1 Dependencies Header and navigation refresh enabled Feature scope Users (enabled by default)

Why you should care

Board

Track as Horizon signal; decide whether it changes Wave 0 priority or stays on the watchlist.

CISO

Confirm identity, data access, and overshare exposure before enabling for broad cohorts.

CFO

Map licence or consumption impact to the frozen value case; avoid seat spray.

Adoption

Pilot with a named cohort and measure changed work, not vanity clicks.

Suggested action

Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Add to Horizon watchlist with an owner. Pilot only after Steady controls for the affected surface are in place.

12 Panes: 03 Horizon · 08 Adoption

Communication needed

  • Security: Assess exposure, Conditional Access, and agent/tool permissions.
  • GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
  • FinOps: Forecast seat or credit impact; align to frozen value case.
  • Adoption: Plan cohort messaging, clinics, and success measures.
  • Comms: One story for board and staff — what changes, what does not, who owns risk.

Benefits

  • May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
  • Roadmap visibility helps Horizon planning without guessing dates.

Risks

  • Status and dates change; treat MRC as directional, not a contract.
  • Enabling without Steady controls can amplify overshare or cost leakage.
  • Preview or rolling features can change behaviour; fence exploration on Pane 12 Frontier.

Source

Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.

Back to roadmap intel