A blue analytics dashboard connects securely to database and cloud services in a modern digital network.
Power Apps generative pages have mostly worked with Dataverse data so far. Microsoft is now changing that. Roadmap item 576283, "Power Apps: Use Power Platform connectors in generative pages," lets makers pull connector data into AI-generated pages in model-driven apps. A page can show data from a SharePoint list, a SQL source or any other connected service without that data first being copied into a Dataverse table.

The roadmap lists the feature as In development, with preview set for September 2026 and general availability for December 2026. Microsoft's own publications show that the preview part has already started.

A blue analytics dashboard connects securely to database and cloud services in a modern digital network. Preview is already live​

Microsoft's September 2026 feature update for Power Platform announced the change under the heading "Public preview: generative pages can now use data from Power Platform connectors." The post explains that to date, generative pages have been built on Dataverse tables, but now they can reach further. It adds that if the data your scenario needs already lives in SharePoint, SQL, or any other connected service, you can build a page against it directly.

This closes a gap that early testers noticed straight away. When the first generative pages preview appeared in July 2025, Power Platform MVP Diana Birkelbach wrote that pages could use only Dataverse tables. Not something else. No connectors for now. About fifteen months later, that has changed, though for now only in preview.

Roadmap fieldValue
Roadmap ID576283
StatusIn development
Preview targetSeptember 2026
GA targetDecember 2026
VersionGen page v302
Applies toModel-driven apps (web)
AudienceAdmins or makers
Clouds listedWorldwide (Standard Multi-Tenant), GCC, GCC High

Microsoft's roadmap describes its dates as estimates that can change. The December GA date is a target, not a promise. The roadmap also lists GCC and GCC High, but that doesn't mean those clouds have the preview today.

Section summary: Connector support is in public preview now. The roadmap targets GA for December 2026.

What actually changes​

Generative pages work like this: you describe a page in plain language, and the app agent writes React code for both the interface and the business logic. Microsoft Learn now says makers specify which Microsoft Dataverse tables, Power Platform connectors (preview), or Dataverse custom APIs (preview) to reference. The documented limits match. In both authoring experiences, supported data sources are Dataverse tables and (preview) Power Platform connectors.

Connector support is built on a familiar Power Platform object. According to Microsoft's blog, connector support works in both authoring experiences by targeting existing connection references in the environment. This matters for governance, because connection references are already solution-aware and admins already manage them.

How to set it up in the browser designer​

Before you start, check the region requirement. For the in-browser experience, the Power Platform environment must be located in one of the following regions: United States, Great Britain, Australia, or Singapore. Outside those regions, use the AI code-generation tool path described further down.

Prepare the connector:

  1. If your page uses a Power Platform connector (preview), create and authenticate a connection.
  2. Then open Solutions > Default Solution and create a connection reference that uses the connection.

Build the page:

  1. Sign in to Power Apps.
  2. Open a model-driven app for editing.
  3. In the app designer, select Add page > Generative page. In the dialog that opens, choose Describe a page.
  4. To use data from a Power Platform connector (preview), select Add data > Connectors, select the prepared connection reference, and choose the connector data that the page should use.
  5. In your prompt, describe how the page should use the selected data, for example as a document gallery, a filtered list or a dashboard.
  6. Select Generate page. Then check the result on the Preview and Code tabs, refine it through chat or by editing the code directly, and finish with Save and Publish.

What success looks like: the page shows live data from the connector in the Preview tab, and users can see it in the app once you publish. If there's no connection reference to pick under Add data > Connectors, go back to the Default Solution step. The designer only lists references that were prepared ahead of time.

Two documented details in the browser designer are easy to miss. GPT-4.1 is currently the only model available there, and only US English is supported for prompts.

Section summary: Prepare the connection and connection reference first, then pick them in the designer. If the reference is missing, it won't appear in the list.

The AI plugin route​

The roadmap also names a second entry point, the generative pages AI plugin. Microsoft Learn calls this code-first route the recommended path for building generative pages, because it gives you access to the latest frontier AI models, works worldwide on public clouds, and can build several pages in one run.

You need these prerequisites:

  • Node.js 18 or later
  • The latest Power Platform CLI
  • GitHub Copilot CLI, Claude Code or another code-generation tool
  • A Power Platform environment with a model-driven app to deploy pages.
  • An authenticated PAC CLI session connected to your target environment.
  • For connector-backed pages (preview), an existing authenticated Power Platform connection for each connector you want to use.

To install just this plugin in GitHub Copilot CLI or Claude Code, add the marketplace with /plugin marketplace add microsoft/power-platform-skills, then run /plugin install model-apps@power-platform-skills. Start the skill with /genpage, or simply describe the page you want.

During planning, the agent lists the connections and connection references in the environment and asks you to pick one. If that connection has no reference yet, the agent creates one. It then asks which data to use, such as a dataset and table or a connector operation, and adds the binding to the page before deployment. Microsoft says all Power Platform connectors are supported.

The tool's "worldwide on public clouds" availability is a separate claim from the roadmap's GCC and GCC High listing. Don't treat one as proof of the other.

What admins should check​

Microsoft's guidance comes down to a few warnings worth reading closely:

  • It's a preview. Microsoft says preview features aren't meant for production use and might have restricted functionality.
  • Test as your users, not as yourself. Microsoft says to review the connector data source in the plan before approving the build, then test the page with the identities and permissions your users will have. A page that works with the maker's account proves only that the maker has access.
  • Generated code needs review. Microsoft is clear that you, not the agent, are responsible for checking that the code meets your organization's standards and compliance requirements. Its FAQ also says makers are always required to publish generative pages before they're made available to users. Extensive testing of any code before making it available to users in an app is always encouraged.
  • One maker at a time. Generative pages don't support collaboration, so two makers working on the same page can cause conflicts.

The documented limits also apply: up to six Dataverse tables per page, prompts of up to 50,000 characters, and a fixed list of supported data types. Microsoft hasn't published a full list of connector-specific limits. Expect some connectors to behave differently from others until GA.

Analysis: a big change with fine print​

This is an important step, judging from what Microsoft has documented. Many real business apps depend on data that isn't in Dataverse, such as SharePoint document libraries, line-of-business SQL databases and SaaS systems. Until now, generative pages either left that data out or needed a separate integration project first.

Building on connection references was a sensible choice, because admins can keep using their existing DLP policies, solution-aware deployment and connection ownership practices. Microsoft also added Dataverse custom API support to generative pages in preview, tracked as roadmap item 576284, so pages are moving beyond read-only displays.

Two cautions remain. First, an AI generating code against external systems makes testing more important, not less. Second, the browser designer is still limited to four regions and one model, which is why Microsoft keeps pointing makers to the CLI route.

Bottom line​

Connector support for generative pages is in public preview now, with GA targeted for December 2026. To try it:

  1. Prepare an authenticated connection and a connection reference in a non-production environment.
  2. Build a test page in the browser designer if your region is supported, or with the CLI plugin otherwise.
  3. Test the page using real end-user identities before letting it anywhere near production.
 

References

  1. Power Apps: Use Power Platform connectors in generative pages Microsoft 365 Roadmap 2026-10-23T21:59:27.914792Z
  2. Generate a page using natural language with model-driven apps in Power Apps - Power Apps learn.microsoft.com
  3. Generate a page using natural language with model-driven apps in Power Apps - Power Apps | Microsoft Learn learn.microsoft.com