Generative pages let makers describe a page for a model-driven app and have AI generate the code. Until now they were mostly a fast way to build data views and forms. The October/November 2026 feature update adds two previews that move them closer to full applications: calling Dataverse custom APIs for server-side business logic, and exporting telemetry to Azure Application Insights.
Both are documented in the generative pages article on Microsoft Learn, last updated September 28, 2026.
Custom APIs: server-side logic on demand
A custom API lets a page run logic at a specific moment, such as approving an order, recalculating a price, or validating a transaction. In the designer, the maker selects Add, then Custom API, picks an API in the current environment, and describes in the prompt when to call it and how to use the response. Global and table-bound actions and functions are supported, and a form page can pass the current record to a table-bound API.
The security model is stated in one line: “Custom APIs run in the context of the signed-in user and are subject to Dataverse security.” That is the right default. It also means the custom API itself is the control point. If a plug-in behind an API elevates privileges or writes to tables the user cannot otherwise touch, any generative page can now trigger it. Inventory which custom APIs exist in each environment and which ones change data, before makers can add them to AI-generated pages.
Two limits are documented: APIs that use the EntityCollection binding type or Entity parameters are not supported, and the feature is in preview, which Microsoft says is not meant for production use.
Application Insights: telemetry without code
Once an administrator sets up Application Insights data export for the environment in the Power Platform admin center, published generative pages export telemetry automatically, with no SDK or connection string in the page. The documentation lists what is captured:
| Activity | Table | Captured |
|---|---|---|
| Page load | pageViews | Page ID, page name, app, host type, load duration, navigation origin |
| Unhandled error | exceptions | Page rendering errors and unhandled promise rejections |
| Data operation | dependencies | Duration and result of create, update, delete, retrieve, and query operations |
| Navigation | pageViews | Source and target page |
This is a real improvement for operations teams. AI-generated code that fails silently is hard to support, and page-level errors and data call durations are exactly what a support team needs. Two cautions apply. Only published pages are covered, so problems during authoring are not visible. And error messages can include content, so check what lands in the exceptions table before routing it to a workspace with broad access.
The bar for review just went up
The same article states that “you’re ultimately responsible for validating the code.” A generated page that only reads data is low risk. A generated page that calls server-side logic which approves orders or changes prices is application code, and it deserves the same review and ALM path as any other. Put generative pages that use custom APIs through your solution and pipeline process; The One Switch That Decides Whether Your Pipelines Are Governed covers the setting that keeps promotion under control. For an introduction to the feature, see Generative pages in model-driven apps.
What the documentation does not cover yet
As of November 10, 2026, the article does not say whether custom API calls appear in telemetry, does not confirm whether user identifiers are included in exported events, and does not describe an admin control specific to custom API use in generative pages. Confirm the telemetry payload before enabling export in regulated environments.
Sources
- What’s new in Power Platform: October/November 2026 feature update, Microsoft Power Platform Blog, November 10, 2026
- Generative pages in model-driven apps, Microsoft Learn, last updated September 28, 2026