A glowing website builder interface connects users worldwide with GitHub workflows and digital reward tokens.
Microsoft plans to give Power Apps' in-browser generative page designer two things makers have asked for: more choice of AI model, and availability outside the handful of regions where it works today. The catch is that both arrive through a GitHub account connection, and that connection uses the maker's own GitHub credits.

The change is listed on Microsoft's AI at Work roadmap as item 576285, titled "Power Apps: Expand model access and Maker Studio availability for generative pages via GitHub." It is marked In development. It is not live yet.

A glowing website builder interface connects users worldwide with GitHub workflows and digital reward tokens. What the roadmap says​

The roadmap entry bundles two changes:

  1. More models through GitHub. Makers will be able to connect a GitHub account and get additional model options for the built-in generative page coding agent. The choice sits inside the generative page designer in Maker Studio, so makers can create and refine pages without leaving Power Apps.
  2. More regions for Maker Studio authoring. The same integration is meant to bring in-browser generative page authoring to regions that don't have dedicated Power Apps GPU capacity.

Microsoft adds two warnings in the entry. Model availability through GitHub "may evolve over time," and requests made through the connection use the maker's GitHub credits.

Roadmap fieldValue
Roadmap ID576285
StatusIn development
Target GANovember 2026
Release channel / versionWeekly, 2611.1
Applies toModel-driven apps
Feature scopeAdmins or makers
PlatformWeb
CloudWorldwide (Standard Multi-Tenant)

Microsoft says roadmap dates are estimates and can change. Treat November 2026 as a target, not a promise.

Summary: The built-in agent gets a GitHub connection for more models, and the browser experience is meant to reach more regions. Both are planned for November 2026 and are not shipped yet.

Why it matters: one model, four regions​

The size of this change only makes sense against how generative pages work today.

Microsoft documents two ways to build them, and both produce the same kind of page:

  • The code-first route, which Microsoft recommends. Microsoft's guide on AI code generation tools describes building pages with AI code generation tools, such as GitHub Copilot CLI, to create and edit generative pages for model-driven apps. Microsoft says this route gives you access to the latest frontier AI models, works worldwide on public clouds, and lets you build multiple pages with supporting Dataverse tables in one run.
  • In-browser authoring at make.powerapps.com. This conversational designer is aimed at makers who want to stay in Power Apps and skip a local development setup. The current documentation, last updated September 28, 2026, limits it to environments in the United States, Great Britain, Australia and Singapore. It also says GPT-4.1 is currently the only model available in the Power Apps maker experience for generative pages, and it points anyone who wants newer models to the code-first tools.

So browser-based makers have so far had one model and four regions. The roadmap item goes at both limits. The fix runs through the same GitHub ecosystem that already powers the code-first route.

The code-first route has had a head start. An item tracked by the M365 Admin roadmap site HANDS ON tek said that capability reached public preview in US regions on February 25, 2026, and will reach general availability on April 2, 2026. Microsoft now describes it as the recommended path. This roadmap item looks like an attempt to bring the browser experience closer to it.

Summary: This is not the first worldwide way to build generative pages. The code-first tools already work worldwide. It's the first planned expansion of the browser designer's models and regions.

The credit question​

Microsoft's generative pages FAQ says the maker experience needs no additional AI or message credits. That statement covers the existing experience. The roadmap says plainly that requests sent through the GitHub connection use the maker's GitHub credits. Don't mix the two up.

The roadmap entry does not say:

  • which GitHub plan or subscription is needed
  • how many credits a request costs
  • which models will appear in the picker
  • whether admins can allow, block or audit the GitHub connection

The "Admins or makers" scope hints that admins may have some role, but Microsoft hasn't described any controls. Until it does, expect budget and governance questions. In particular: who pays when one maker's personal GitHub credits fund a page that ships in a company app?

How "more regions" should be read​

The roadmap says "regions without dedicated Power Apps GPU capacity." That is not the same as "every region." The entry doesn't list the new geographies, and it doesn't say whether every worldwide region is included.

The likely mechanism is that model work happens on the GitHub side instead of on Power Apps GPU capacity, which is why regions without that capacity become possible. That is our reading of the wording, not something Microsoft has stated. Data-residency teams should wait for Microsoft's documentation on where prompts and generated code are processed before approving it.

What stays the same​

More model choice doesn't remove the current platform limits. According to Microsoft Learn:

  • Generative pages work only in model-driven apps, not canvas apps.
  • A page can link up to six Dataverse tables.
  • Power Platform connectors, Dataverse custom APIs and Application Insights telemetry are still preview features.
  • In-browser prompts are supported only in US English, up to 50,000 characters.
  • Collaboration isn't supported. Only one maker should work on a page at a time.

Responsibility for the output doesn't change either. Microsoft says the agent makes a best effort at production-ready code, but makers must check that it meets their organization's standards and compliance rules. A stronger model may write better React. It doesn't remove the need to review the code.

Using the current in-browser flow​

If your environment is in a supported region, the documented process is:

  1. Sign in to Power Apps.
  2. Open a model-driven app for editing.
  3. In the app designer, select Add page > Generative page. Then choose Describe a page.
  4. Describe the page you want, including functional requirements and any layout details.
  5. Add data with Add data > Add table. You can also attach a sketch or reference image.
  6. You can pick a model, though GPT-4.1 is the only option today. This is where the GitHub-connected models are expected to appear.
  7. Select Generate page, then review the result on the Code and Preview tabs. Refine it by chatting with the agent or by editing the code yourself.
  8. Run the Accessibility assistant, then choose Save and Publish.

If generative pages don't appear: Microsoft's FAQ says to check that your environment is in one of the four supported regions. If it isn't, use the code-first tools. That may change once this roadmap item ships.

Analysis​

This is a sensible move. Microsoft has been telling browser makers that the best models are in a CLI they may never install. Putting GitHub-hosted models inside the designer closes that gap without asking a business analyst to learn Node.js or the PAC CLI.

It does shift costs and governance onto GitHub accounts. Organizations with central GitHub Copilot licensing may find this simple. Organizations where makers have personal or no GitHub accounts will need a policy before November.

What to do before November​

  • Power Platform admins: List which environments are outside the four current regions. They are the most likely to benefit, but wait for Microsoft to publish the actual region list.
  • Finance and licensing teams: Work out how GitHub credits are bought and assigned in your organization before makers start using them.
  • Makers: Keep using GPT-4.1 in the browser, or the code-first tools if you need newer models now.
  • Everyone: Check the generative pages documentation around the 2611.1 weekly release for the actual model list and admin controls.

The bottom line: browser-based generative page authoring is planned to get more models and more regions in November 2026, paid for with GitHub credits. The region list, credit costs and admin controls are still unannounced.

 

References

  1. Power Apps: Expand model access and Maker Studio availability for generative pages via GitHub 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