Power Pages: Design studio - Unify Power Pages authorization by merging web role with Dataverse security role
This feature merges Power Pages web roles and site users with Dataverse security roles and system users, creating a unified authorization model. User Mapping : Each Power Pages user is stored in both the System User table and the Contact table. The System Managed User Type column
DIGITAL SKILL WORKS LTD / 12 PANES
What it is
Power Pages: Design studio - Unify Power Pages authorization by merging web role with Dataverse security role is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.
What it does
This feature merges Power Pages web roles and site users with Dataverse security roles and system users, creating a unified authorization model. User Mapping : Each Power Pages user is stored in both the System User table and the Contact table. The System Managed User Type column in the User table identifies Power Pages users as C2 User . Role Mapping : Each Power Pages web role is represented in both the Security Role table and the Web Role table. No Migration Required : Existing contact and web role records automatically sync with system user and security role tables. Configuration : No changes required for makers; existing data security configurations remain intact. Business Value: You'll strengthen security and simplify user management by centralizing authorization in Dataverse. This means fewer redundant checks in Power Pages, reducing complexity and improving performance. Businesses gain consistent access control, enhanced auditing for compliance, and faster data operations, all without additional configuration or migration. The result is lower operational overhead, improved governance, and better scalability. Enabled for: Enabled by admins/makers/marketers for end users
Why you should care
Board
Security/compliance control — fund Steady before more seats.
CISO
Prioritise as Steady control; wire into IR and GRC evidence paths.
CFO
Map licence or consumption impact to the frozen value case; avoid seat spray.
Adoption
Pilot with a named cohort and measure changed work, not vanity clicks.
Suggested action
Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Add to Horizon watchlist with an owner. Pilot only after Steady controls for the affected surface are in place.
12 Panes: 03 Horizon · 04 Security · 05 GRC · 08 Adoption
Communication needed
- Security: Lead review; confirm control mapping before enablement.
- GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
- FinOps: Forecast seat or credit impact; align to frozen value case.
- Adoption: Plan cohort messaging, clinics, and success measures.
- Comms: One story for board and staff — what changes, what does not, who owns risk.
Benefits
- May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
- Roadmap visibility helps Horizon planning without guessing dates.
Risks
- Status and dates change; treat MRC as directional, not a contract.
- Enabling without Steady controls can amplify overshare or cost leakage.
- Preview or rolling features can change behaviour; fence exploration on Pane 12 Frontier.
Source
- MRC id: 576750
- Status: In development
- Products: Power Pages
- GA / disclosure: November CY2026
- Preview: July CY2026
- Platforms: Web
- Cloud instances: Worldwide (Standard Multi-Tenant)
- moreInfoUrls: https://learn.microsoft.com/en-us/power-pages/security/unify-pages-security-with-dataverse
- Open on Microsoft 365 Roadmap
Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.