EPISODE · Oct 26, 2025 · 20 MIN
Generative Pages low‑code safety: why clicking “Edit Code” turns your Power App into a pro‑code risk
from M365.FM - Modern work, security, and productivity with Microsoft 365 · host Mirko Peters - Founder of m365.fm, m365.show and m365con.net
Generative Pages low‑code safety: in this episode of M365.fm, Mirko Peters explains why Microsoft’s Generative Pages feel like the final victory for low‑code—type a sentence, get a working React page—but in reality smuggle full pro‑code risk into environments that were never designed to carry it. He starts with the illusion: you describe a dashboard, GPT‑5 assembles a beautiful page that talks to Dataverse, and it all lives inside Power Apps, so it feels governed, sandboxed, and “safe by default.”Mirko then shows where that illusion breaks the moment you click Edit Code. At that point, the page stops being managed configuration and becomes source code: React, JSX, npm dependencies, and custom logic that Microsoft no longer maintains for you. The declarative safety net of low‑code—type checks, platform‑level upgrades, centralized patching—vanishes, and you suddenly own version drift, security updates, and every subtle bug that comes with imperative UI code. The app still looks like Power Apps on the surface, but underneath it has switched from governed metadata to unmanaged JavaScript.He walks through the technical debt that quietly appears: React version mismatches when the platform upgrades its renderer, npm packages that need patching for CVEs, Dataverse schema changes that no longer auto‑propagate, and custom logic that bypasses platform‑level guardrails. The result is a two‑layer app: a friendly low‑code shell for makers, hiding a growing pile of pro‑code complexity that only experienced developers can safely touch. Instead of eliminating the need for devs, Generative Pages often create stealth projects that IT inherits only when something breaks in production.Throughout the episode, Mirko argues that Generative Pages are powerful—but must be treated as pro‑code projects the moment code editing is enabled. That means Git repos, code reviews, CI/CD, dependency management, and security scanning, not “we’ll let the agent fix it later.” He gives you a simple rule of thumb: if a page stays within the generated, metadata‑only model, it behaves like safe low‑code; if you ever open the React layer, it belongs under the same governance as any custom web app.You’ll also hear how to talk about this with stakeholders: low‑code as a managed city with zoning laws, pro‑code as open construction that demands architects and inspectors. Generative Pages are the zoning exemption—useful when you truly need it, dangerous when handed out casually to citizeWHAT YOU WILL LEARNWhy Generative Pages feel like safe low‑code while quietly introducing full procode risk.What really happens when you click Edit Code and your page becomes unmanaged React and npm dependencies.How version drift, schema changes, and security updates turn AI‑generated React into technical debt.When Generative Pages must be treated as full software projects with Git, reviews, and CI/CD.How to explain to makers and leaders that “describe your page” is not the same as “no developers needed.”THE CORE INSIGHTGenerative Pages didn’t kill low‑code—they killed the illusion that low‑code is always safe. The moment you unlock React, you’re no longer in a protected Power Apps sandbox but in full‑blown application development, and only real engineering practices—not AI magic—can keep that code secure, maintainable, and compliant.WHO THIS EPISODE IS FORThis episode is ideal for Power Platform admins, solution architects, pro devs, and COE leaders who are piloting Generative Pages and need to understand where low‑code safety ends and custom‑code responsibility begins. It is especially valuable if citizen makers are already clicking Edit Code and you need a governance stance before those “harmless experiments” become production liabilities.ABOUT THE HOSTMirko Peters is a Microsoft 365 and Power Platform consultant focused on building governed, scalable solutions with Power Apps, Dataverse, GitHub Copilot, and modern low‑code/pro‑code architectures. Through M365.fm, he shares practical governance patterns, AI‑assisted development stories, and platform guidelines that help organizations use Generative Pages without turning low‑code into an untracked risk layer.Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
What this episode covers
Generative Pages low‑code safety: in this episode of M365.fm, Mirko Peters explains why Microsoft’s Generative Pages feel like the final victory for low‑code—type a sentence, get a working React page—but in reality smuggle full pro‑code risk into environments that were never designed to carry it. He starts with the illusion: you describe a dashboard, GPT‑5 assembles a beautiful page that talks to Dataverse, and it all lives inside Power Apps, so it feels governed, sandboxed, and “safe by default.”Mirko then shows where that illusion breaks the moment you click Edit Code. At that point, the page stops being managed configuration and becomes source code: React, JSX, npm dependencies, and custom logic that Microsoft no longer maintains for you. The declarative safety net of low‑code—type checks, platform‑level upgrades, centralized patching—vanishes, and you suddenly own version drift, security updates, and every subtle bug that comes with imperative UI code. The app still looks like Power Apps on the surface, but underneath it has switched from governed metadata to unmanaged JavaScript.He walks through the technical debt that quietly appears: React version mismatches when the platform upgrades its renderer, npm packages that need patching for CVEs, Dataverse schema changes that no longer auto‑propagate, and custom logic that bypasses platform‑level guardrails. The result is a two‑layer app: a friendly low‑code shell for makers, hiding a growing pile of pro‑code complexity that only experienced developers can safely touch. Instead of eliminating the need for devs, Generative Pages often create stealth projects that IT inherits only when something breaks in production.Throughout the episode, Mirko argues that Generative Pages are powerful—but must be treated as pro‑code projects the moment code editing is enabled. That means Git repos, code reviews, CI/CD, dependency management, and security scanning, not “we’ll let the agent fix it later.” He gives you a simple rule of thumb: if a page stays within the generated, metadata‑only model, it behaves like safe low‑code; if you ever open the React layer, it belongs under the same governance as any custom web app.You’ll also hear how to talk about this with stakeholders: low‑code as a managed city with zoning laws, pro‑code as open construction that demands architects and inspectors. Generative Pages are the zoning exemption—useful when you truly need it, dangerous when handed out casually to citizeWHAT YOU WILL LEARNWhy Generative Pages feel like safe low‑code while quietly introducing full procode risk.What really happens when you click Edit Code and your page becomes unmanaged React and npm dependencies.How version drift, schema changes, and security updates turn AI‑generated React into technical debt.When Generative Pages must be treated as full software projects with Git, reviews, and CI/CD.How to explain to makers and leaders that “describe your page” is not the same as “no developers needed.”THE CORE INSIGHTGenerative Pages didn’t kill low‑code—they killed the illusion that low‑code is always safe. The moment you...
NOW PLAYING
Generative Pages low‑code safety: why clicking “Edit Code” turns your Power App into a pro‑code risk
No transcript for this episode yet
Similar Episodes
Mar 26, 2026 ·1m
Mar 19, 2026 ·34m
Feb 18, 2026 ·11m
Feb 11, 2026 ·45m