The October/November 2026 feature update brings an AI authoring agent into Power Apps canvas studio, powered by GitHub. Makers connect a GitHub account, describe what they want, approve a plan, and the agent writes screens, controls, and Power Fx into the open app. Microsoft’s Learn article, Build canvas apps with the authoring agent in Power Apps canvas studio, last updated October 27, 2026, documents it as a preview.
This is separate from the canvas authoring agent plugin that reached general availability in September, which lets external coding agents edit apps through MCP. The new feature lives inside Studio. What makes it different from other Copilot features in Power Apps is not what it does, but whose terms and whose bill it runs under.
Data goes to GitHub, under GitHub terms
The in-product notice quoted in the documentation is direct: “Your prompts and application context will be sent to GitHub to be processed and stored under the GitHub terms applicable to your or your organization’s GitHub account and either the GitHub General Privacy Statement or GitHub DPA.”
Application context can include screen names, formulas, data source names, and business logic. For many organizations that is fine, particularly where GitHub is already an approved processor under an enterprise agreement. For others, it means a new data flow to a service outside the Power Platform data boundary, which their privacy or vendor risk process has not reviewed. Which GitHub account the maker signs in with also matters: a personal account and an organization-managed account fall under different terms.
GitHub bills the usage
The documentation says “Usage is billed through your existing GitHub billing plan,” and “GitHub bills that account for usage.” Microsoft’s blog adds that manual edits in Studio use no tokens. This cost will not appear in Copilot Credits reporting or Power Platform capacity. If makers use personal GitHub accounts, it may not appear in any company report at all. Decide whether makers must use organization-managed GitHub accounts so that usage is visible and paid for centrally.
The tenant setting is the control
The feature requires a tenant administrator to turn on Agentic Coauthoring in Power Apps using GitHub under Manage, Tenant Settings in the Power Platform admin center. The documentation notes that enabling it indicates acceptance of the feature’s terms. It does not state the default, so check your tenant rather than assuming.
Before turning it on, settle four things:
- Whether your privacy and vendor risk process has approved GitHub as a processor for app prompts and context.
- Which GitHub accounts makers may use, and who pays.
- How agent-built changes are reviewed before they reach production; the agent cannot save, publish, or share, so publishing remains a human step you can attach review to.
- Which makers are told about the preview’s limits: United States only, English only, no images, no data edits, and AI output that may be incorrect.
For a related decision on Copilot Studio, see Copilot Studio Can Now Build Apps. Admins Should Decide a Few Things First.
What the documentation does not cover yet
As of November 10, 2026, the article does not state the tenant setting’s default, which GitHub plan or product the usage is billed against, or whether the setting can be scoped below the tenant. Microsoft’s blog describes the agent as editing existing apps, while Learn describes building and editing; test both in your tenant.
Sources
- What’s new in Power Platform: October/November 2026 feature update, Microsoft Power Platform Blog, November 10, 2026
- Build canvas apps with the authoring agent in Power Apps canvas studio, Microsoft Learn, last updated October 27, 2026