A practical reference for developers building portal solutions with Microsoft Power Pages, Dataverse, and Dynamics 365.
This repo is intended as a quick working guide rather than formal documentation. It focuses on the areas that usually matter most in real projects:
- authentication and external user access
- Dataverse integration
- table permissions and web roles
- Liquid templates
- portal security
- troubleshooting and delivery tips
This cheat sheet is aimed at:
- developers new to Power Pages
- Dynamics 365 / Dataverse developers moving into portal work
- solution architects designing external-facing Power Platform solutions
- teams delivering secure government or enterprise portals
graph TD
U[External User] -->|signs in via| IDP[Identity Provider<br/>Entra ID / B2C / SAML]
IDP -->|token| PP[Power Pages Portal]
PP -->|resolves| C[Contact Record]
C -->|assigned to| WR[Web Role]
WR -->|grants| TP[Table Permissions]
TP -->|scopes access to| DV[(Dataverse Tables)]
DV -->|data surfaced via| PG[Pages / Forms / Lists]
PP -->|page access controlled by| PPERM[Page Permissions]
PPERM --> WR
Power Pages is Microsoft's low-code / pro-code portal platform for exposing Dataverse-backed data and processes to external users through secure web applications.
Dataverse is the underlying data platform used by Dynamics 365 and Power Platform applications.
Power Pages security typically combines:
- authentication provider configuration
- contacts
- web roles
- table permissions
- page permissions
- external user registration and sign-in
- secure access to Dataverse data
- surfacing Dynamics 365 processes through web pages
- integrating portal pages with Power Automate and Azure services
- customising front end behaviour with HTML, CSS, JavaScript and Liquid
This repo is based on practical implementation experience. Always validate production decisions against Microsoft's official documentation and your organisation's security requirements.
Issues and pull requests are welcome.
Maintained by Matthew Brunsdon.