Rather than introducing brand-new AI functionality, this update is a housekeeping and governance overhaul designed to make existing capabilities easier to find, understand, and administer. Here is a full breakdown of what is moving, where it is going, and why IT administrators need to prepare for the retirement of the old environment switches.
Two Complementary Surfaces for Makers and Admins
The core problem Microsoft is addressing is split-brain administration. Previously, an app maker looking for AI options in the Power Apps designer had to sift through general feature lists, while an environment administrator had to hunt under legacy environment settings pages using labels that did not always clearly map to what the maker was seeing.
Under Roadmap ID 574104, Microsoft is consolidating these controls across two complementary web surfaces:
- Maker Studio (Model App Form Designer): The Settings dialog within the model-driven app form designer is getting a new top-level Copilot and AI tab. Instead of hunting through a broader list of general app features, makers will be able to view and adjust all available AI options for that specific application in one dedicated pane.
- Power Platform Admin Center: On the governance side, model-driven app AI switches are moving out of Environment > Settings and into Copilot Hub > Power Apps. This gives administrators a single dashboard for high-level controls such as Generative pages, Copilot in apps, and built-in in-app AI skills.
Just as importantly, Microsoft notes that the naming conventions, labels, and descriptions are being aligned across both Maker Studio and the Copilot Hub. When a maker asks an administrator to enable a specific skill for an environment, both parties will actually be looking at the same terminology.
How In-App AI Skills Are Grouped
Within the consolidated settings, Microsoft is organizing the built-in model-driven app AI skills into three functional categories. These mirror the way Microsoft Learn's Power Apps documentation already categorizes end-user AI capabilities:
| Skill Category | Included Capabilities |
|---|---|
| Data entry | Form fill assistance |
| Summary | Row summaries |
| Data analysis | AI-generated charts; natural-language search and filtering |
In practical terms, these categories cover the everyday inline tools business users interact with. As documented on Microsoft Learn, data entry tools include form fill assistance and smart paste toolbar options; summary tools provide custom and inline row summaries in forms and views; and data exploration and analysis tools allow users to query grid views with natural language or generate visuals on the fly.
Section Summary: App-level AI toggles are moving to a new Copilot and AI tab in Maker Studio, while environment-level administrative switches are migrating to Copilot Hub > Power Apps under unified labels and three clear skill groupings.
The Catch: Legacy Environment Switches Are Being Retired
Consolidation is rarely just about adding a shiny new menu; it also means cleaning out the old ones. As part of this update, Microsoft states that the older model-driven app AI switches located under Environment > Settings in the Power Platform admin center will be retired and removed.
Microsoft Learn's Power Platform feature settings documentation confirms that this transition is already taking shape: admin controls for AI form fill assistance, for instance, are shifting their primary administrative home to Copilot > Settings > Power Apps > Data entry, with legacy toggles being stripped out of the old Environment > Settings > Features page. According to that documentation, shifting these controls into the Copilot area also lays the groundwork for broader administrative capabilities, such as environment group management and Microsoft Entra group support for specific settings.
Why does the removal of the old switches matter so much for day-to-day IT operations? Because enterprise governance relies heavily on muscle memory and internal documentation. If your organization maintains onboarding runbooks, change-management checklists, or compliance documentation that instructs junior admins to navigate to Environment > Settings > Features to lock down AI features in a new production environment, those guides are about to hit a dead end.
Rollout Schedule, Scope, and Platform Details
According to Microsoft AI at Work Roadmap entry 574104, published on October 13, 2026, this update is currently listed as In development with a targeted general availability window of October 2026. The rollout parameters specified in the roadmap record include:
- Product & Platform: Power Apps (Web)
- Applies To: Model-driven apps
- Release Channel & Version: Weekly channel, Version 2610.3
- Feature Scope: Admins and makers
- Cloud Instances: Worldwide (Standard Multi-Tenant), GCC, and GCC High
As always with the Microsoft AI at Work Roadmap, release timelines represent current estimates for features undergoing development and testing and remain subject to change until deployment completes. However, because Microsoft Learn's feature settings documentation published in early October 2026 already warns administrators that form fill assistance controls are moving to the Copilot settings area in the coming weeks, organizations should treat this transition as imminent.
Section Summary: Scheduled for general availability in October 2026 (Version 2610.3 on the Weekly channel) across commercial and US government clouds, this update will permanently remove the legacy model-driven app AI switches from the old Environment Settings menu.
Broader Governance Context: What This Change Does (and Doesn't) Do
While having a cleaner UI is a welcome quality-of-life improvement, veteran Power Platform administrators know that moving a toggle does not magically simplify the underlying permission matrix. Based on Microsoft Learn's Power Apps and Power Platform documentation, there are several critical boundaries to keep in mind as these consolidated menus appear:
- Prerequisites Still Apply: Consolidating app-level and admin-level switches does not bypass baseline requirements. As Microsoft Learn outlines, using AI features in model-driven apps still requires Copilot to be enabled for the tenant and environment, and individual apps must have the modern "new look" turned on alongside their specific AI feature settings.
- Maker Copilot vs. End-User Copilot: Turning off a high-level switch does not always do what its name implies at first glance. For example, Microsoft Learn's feature settings documentation explicitly warns that turning off "Copilot in Power Apps" at the tenant level disables Copilot for makers, not the Copilot control in canvas apps, Copilot for model-driven apps, or Copilot in Dynamics 365 Sales. Moving model-driven app switches into Copilot Hub > Power Apps should make it much easier for admins to distinguish end-user app skills from maker tools.
- User-Level Access Controls Remain Separate: Microsoft's Copilot Hub documentation also details a preview capability that lets admins restrict who inside an environment can use specific model-driven app AI skills (such as Copilot chat, form fill assistance, smart paste, row summary, Visualize with Copilot, and natural-language search) via inclusion or exclusion lists. However, that user-scoping control is restricted to Managed Environments. The roadmap item for consolidated settings does not claim to lift the Managed Environments requirement for user-level targeting.
- Pairing Settings with Analytics: Moving these switches into Copilot Hub > Power Apps places configuration right next to telemetry. As documented on Microsoft Learn, the Power Apps page inside the Copilot Hub already tracks monthly active users and action counts over a 28-day lookback period for both the data entry agent (measuring forms where Copilot provided assistance) and the data exploration agent (measuring natural-language grid queries). Having the on/off switches in the same administrative neighborhood as the usage metrics makes it much easier to see whether anyone is actually using a feature before deciding whether to keep it enabled.
Practical Checklist for Makers and IT Admins
How can you make sure your team isn't caught off guard when the old switches vanish? Here is a straightforward game plan:
- Audit Your Internal Runbooks: Search your internal IT wiki or SharePoint governance docs for references to
Environment > Settings > Featuresregarding model-driven app AI controls, and update those paths to point toCopilot > Settings > Power Apps(Copilot Hub). - Brief Your App Makers: Let your Power Apps makers know that when their environment reaches version 2610.3 on the Weekly channel, app-specific AI switches will relocate to the top-level Copilot and AI tab inside the model app form designer's Settings dialog.
- Verify Environment Group Rules: Because most settings in the Copilot Hub can be applied across environment groups as well as individual environments, check whether your existing environment group rules cover the newly migrated Data entry, Summary, and Data analysis categories.
In the grand scheme of enterprise software, moving settings tabs around isn't as flashy as launching a new frontier AI model. But for the makers and systems administrators who actually have to govern these tools across commercial, GCC, and GCC High tenants, a logical, synchronized control plane is long overdue. When both the people building the apps and the people securing the tenant can look at the same labels in predictable places, everyone spends less time hunting for switches and more time getting actual work done.