Power Pages SPAs: Custom React code with platform security
Diesen Beitrag auf Deutsch lesen
A practical preview tutorial shows how to upload a React single-page application to Power Pages while retaining authentication and table permissions.
Posted 
Governance card: A Power Pages SPA still needs authentication and table permissions. Preview code belongs outside production.
By Power Platform Governance
1 min read
TL;DR
Power Pages preview supports React, Angular and Vue single-page applications uploaded with the PAC CLI. The tutorial connects to a Dataverse environment outside production, uploads compiled code, reactivates the inactive site, and notes that authentication and table permissions remain available even though page editing and default styling templates are unavailable.
Original by Nick Doelman, on The ReadyXRM Blog. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Build and test the SPA with the Power Platform tools extension, then upload compiled code through the PAC CLI; the preview feature supports custom React, Angular or Vue interfaces.
- Admins/CoE: Require deployment to a non-production Dataverse environment and review the uploaded site before reactivation; the tutorial explicitly warns against connecting to production.
- Security/Compliance: Configure authentication and table permissions for the SPA because custom code does not replace Power Pages security controls.
This post is licensed under CC BY 4.0 by the author.