In development MRC 574104

Power Apps: Manage model-driven app AI features from consolidated settings

Consolidated AI settings make it easier for makers and admins to find and manage AI capabilities for model-driven apps across two complementary surfaces. In Maker Studio, the Settings dialog in the model app form designer adds a new top-level Copilot and AI tab. Makers can see an

Power Apps 03 Horizon04 Security

DIGITAL SKILL WORKS LTD / 12 PANES

GA / disclosure October CY2026
Platforms Web

What it is

Power Apps: Manage model-driven app AI features from consolidated settings is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.

What it does

Consolidated AI settings make it easier for makers and admins to find and manage AI capabilities for model-driven apps across two complementary surfaces. In Maker Studio, the Settings dialog in the model app form designer adds a new top-level Copilot and AI tab. Makers can see and adjust all available AI options for the app in one place instead of finding them scattered among all the other settings. In the Power Platform admin center, model-driven app AI settings are consolidated from Environment > Settings into Copilot Hub > Power Apps . This provides a central location for settings such as Generative pages, Copilot in apps, and the in-app AI skills. The in-app skill settings are organized into these groups: Data entry: Form fill assistance. Summary: Row summaries. Data analysis: AI-generated charts and natural-language search and filtering. Labels and descriptions are aligned across Maker Studio and Copilot Hub so makers and admins can understand how the controls relate. As part of this consolidation, the old model-driven app AI switches under Environment > Settings will also be retired and removed. Availability Field Value Applies to Model-driven apps Release Channel Weekly Version 2610.3 Feature Scope Admins or makers

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 · 04 Security

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

  • MRC id: 574104
  • Status: In development
  • Products: Power Apps
  • GA / disclosure: October CY2026
  • Preview: —
  • Platforms: Web
  • Cloud instances: Worldwide (Standard Multi-Tenant), GCC, GCC High
  • moreInfoUrls: —
  • Open on Microsoft 365 Roadmap

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