PL-900 Objective 5.1: Describe the Capabilities of Power Pages
PL-900 Exam Focus: This objective covers Power Pages as the Power Platform component for creating external-facing websites. Understanding use cases distinguishing Power Pages from internal Power Apps, methods for creating sites including templates and design studio, and security concepts including authentication methods, web roles, and table permissions are essential exam topics. Focus on when to use Power Pages versus other Power Platform components and how security controls protect organizational data.
Power Pages Overview
Microsoft Power Pages enables organizations to create secure, professional external-facing websites that extend business data and processes to audiences outside the organization. Unlike Power Apps that primarily serve internal users within an organization, Power Pages creates portals accessible to customers, partners, vendors, community members, or the general public. These data-driven websites integrate directly with Microsoft Dataverse, enabling external users to view, submit, or update business information through intuitive web interfaces without requiring internal system access or specialized software installations.
Power Pages follows the low-code paradigm familiar across Power Platform, enabling business users and professional developers to create sophisticated websites without extensive web development expertise. The platform provides pre-built templates for common scenarios, visual design tools for customizing appearance and layout, declarative security models controlling access, and extensibility options for advanced requirements. Sites built with Power Pages are responsive by design, automatically adapting to mobile phones, tablets, and desktop computers. The platform handles hosting, scaling, security patching, and infrastructure management, allowing organizations to focus on content and functionality rather than technical operations.
Power Pages Use Cases
Customer Self-Service Portals
Customer self-service portals represent one of the most common Power Pages use cases, enabling customers to access account information, track orders, submit support requests, and manage their relationship with organizations independently. These portals reduce support costs by deflecting routine inquiries to self-service options while improving customer satisfaction through 24/7 access to information and services. Customers log in using various authentication methods, view their personal data, update profile information, download invoices or statements, track shipment status, and submit cases or requests without calling support teams or sending emails.
Self-service capabilities include knowledge bases where customers search articles answering common questions, case management enabling customers to create, track, and update support tickets, product catalogs displaying available offerings with specifications and pricing, order history showing past purchases and delivery status, and document libraries providing access to contracts, policies, or product documentation. Integration with Dataverse ensures portal information stays synchronized with internal systems, so customers see current data. Automated workflows can trigger when customers submit requests, ensuring timely routing and processing without manual intervention from support staff.
Partner Collaboration Portals
Partner portals facilitate collaboration with business partners, distributors, resellers, or suppliers by providing secure access to shared resources, information, and collaboration tools. Organizations use partner portals to distribute marketing materials, share product roadmaps, coordinate joint initiatives, manage deal registrations, track partner performance, and facilitate communication. Partners access dedicated portal areas with content and features relevant to their relationship type and tier, creating differentiated experiences for different partner categories like platinum, gold, or silver partners.
Common partner portal features include resource libraries with sales enablement materials, training and certification programs, deal registration systems preventing channel conflict, lead distribution mechanisms, performance dashboards showing sales metrics, incentive tracking displaying earned rewards, and collaboration spaces for joint projects. Partner portals create transparency and alignment between organizations and their partners, reducing friction in collaborative relationships and enabling partners to more effectively represent and sell organizational offerings. The centralized information repository ensures partners always access current materials rather than outdated content.
Community and Forum Sites
Community sites foster engagement among customers, enthusiasts, or members sharing common interests related to organizational products, services, or causes. These sites enable peer-to-peer support where experienced users help newcomers, reducing organizational support burden while building engaged communities. Features include discussion forums organized by topics, user profiles showcasing expertise and contributions, reputation systems rewarding helpful members, content voting mechanisms surfacing high-quality contributions, and moderation tools ensuring appropriate content and behavior.
Community portals benefit both organizations and members by creating spaces where customers connect, share experiences, solve problems collaboratively, and provide feedback on products or services. Organizations gain insights from community discussions, identifying common pain points, feature requests, or misconceptions requiring clarification. Active communities increase customer loyalty and product adoption by providing social proof, peer recommendations, and collective knowledge surpassing what organizational documentation alone could provide. Gamification elements like badges, points, and leaderboards incentivize participation and recognize valuable contributors.
Event Management and Registration
Event registration portals streamline the process of promoting events, collecting registrations, managing attendees, and communicating event information. Organizations create event pages describing conferences, training sessions, webinars, or community gatherings, collect attendee information through registration forms, process payments if applicable, send confirmation and reminder emails, and provide event materials or resources. Registered attendees access event schedules, speaker information, session descriptions, venue details, and networking opportunities through the portal.
Event portals support various scenarios including large conferences with hundreds of sessions and thousands of attendees, training programs with multiple courses and certification tracking, recurring webinar series with ongoing registrations, and exclusive events with invitation-only access. Integration with Dataverse enables comprehensive event management including session capacity limits, waitlist management, attendee check-in tracking, and post-event survey collection. Automated communications keep attendees informed throughout event lifecycle from registration through post-event follow-up, reducing manual coordination effort while ensuring consistent attendee experiences.
Job Application and Recruiting Portals
Career portals enable organizations to post job openings, collect applications, track candidates through hiring pipelines, and maintain talent pools for future opportunities. Job seekers browse available positions filtered by location, department, or role type, review detailed job descriptions, submit applications including resumes and cover letters, and track application status. The portal provides professional, branded experiences reflecting organizational culture and attracting quality candidates while simplifying application processes and reducing friction that might cause candidate drop-off.
Recruiting portals integrate with Dataverse to store candidate information, application history, interview feedback, and hiring decisions in centralized systems accessible to recruiting teams through Power Apps or model-driven applications. Automated workflows route applications to hiring managers, schedule interviews, send status updates to candidates, and generate offer letters. Advanced portals include skills assessments, video interview capabilities, referral program management, and employee testimonials providing authentic insights into organizational culture. These portals create positive candidate experiences while enabling efficient, organized recruiting processes.
Creating Power Pages Sites
Template-Based Creation
Power Pages provides pre-built templates offering complete starting points for common portal scenarios. These templates include page structures, sample content, forms and lists connected to Dataverse tables, navigation menus, and styling reflecting typical use cases. Available templates address scenarios like starter portals providing basic functionality makers extend, scheduling portals for appointment booking, after-school portals for educational programs, building access portals for facility management, and other specialized scenarios. Templates accelerate time-to-value by eliminating the need to design site architecture from scratch, instead providing proven patterns makers customize for specific needs.
Creating sites from templates involves selecting appropriate templates from the template gallery, naming the site, choosing the web address, and clicking create. Power Pages provisions the complete site including all necessary Dataverse tables, security roles, and configurations. Makers then customize templates by replacing sample content with actual information, adding organizational branding including logos and color schemes, configuring authentication providers, modifying forms to collect required data fields, adjusting page layouts and navigation, and publishing to make sites accessible. Template customization requires no coding for common modifications, though developers can extend templates with custom code when needed.
Design Studio Visual Tools
Power Pages design studio provides comprehensive visual tools for creating and customizing sites through intuitive interfaces without extensive technical knowledge. The pages workspace enables makers to create new pages, modify existing pages, arrange content sections using drag-and-drop, and preview changes before publishing. The styling workspace controls site appearance including color schemes, fonts, button styles, and responsive behavior across device sizes. The data workspace configures connections to Dataverse tables, defines forms for data collection or display, creates lists showing filtered records, and sets up detail pages for comprehensive record views.
Design studio's component-based approach enables makers to add pre-built components like text sections, images, videos, forms, lists, breadcrumbs, and navigation menus to pages through simple selection and placement. Each component has configurable properties controlling appearance and behavior without requiring code. For example, form components connect to Dataverse tables, select which fields to display, configure validation rules, and define success messages shown after submission. List components specify which table to query, what filters to apply, which columns to show, and whether to enable sorting or searching. This declarative configuration approach enables sophisticated functionality through visual tools.
Site Configuration and Management
Beyond visual design, Power Pages sites require configuration of authentication, permissions, and operational settings. Makers configure which authentication providers are available, whether users can self-register or require invitations, what information registration forms collect, and email templates for account verification and password reset. Security configuration includes creating web roles defining site permissions, assigning table permissions controlling data access, and mapping users to appropriate roles. Site settings control search functionality, caching behavior, content delivery network options, and custom domain mapping for branded URLs.
Site management tools enable makers to monitor site usage through analytics showing page views, popular content, and user activity. Version control maintains site change history enabling rollback if modifications cause issues. Progressive publishing allows testing changes in development or staging environments before deploying to production sites accessible to external users. Multi-language support enables creating content in multiple languages with automatic language detection or user language selection. These management capabilities ensure sites remain secure, performant, and aligned with organizational requirements throughout their lifecycle.
Power Pages Security Concepts
Authentication Methods
Power Pages supports multiple authentication methods enabling flexible access control appropriate for different user types and security requirements. Anonymous access allows anyone to view public content without signing in, suitable for marketing pages, product information, or public knowledge bases where content restriction isn't necessary. This accessibility maximizes reach while reserving authentication for areas requiring identity verification or personalization. Anonymous users have extremely limited data access controlled through specific Dataverse table permission configurations allowing read-only access to designated public information.
Local authentication creates user accounts managed directly by Power Pages with credentials stored in Dataverse. Users register providing email addresses, usernames, and passwords, then sign in with those credentials. This method provides complete control over user lifecycle and doesn't depend on external identity providers, but requires organizations to manage password policies, account recovery, and credential security. External authentication integrates with identity providers including Azure Active Directory B2C for customer identities, Azure Active Directory for employee or partner access, Microsoft accounts, LinkedIn, Google, Facebook, Twitter, or custom OAuth/OpenID Connect providers. External authentication leverages existing user credentials, improves security through identity provider features like multi-factor authentication, and simplifies user experience by eliminating additional password management.
Web Roles and Page Permissions
Web roles represent collections of permissions assigned to authenticated users controlling site functionality access. Each web role defines which pages users can view, which site features they can access, and which forms or components they can interact with. For example, an "Authenticated Users" web role might grant access to profile management pages and support case submission, while a "Premium Member" role additionally grants access to exclusive content or advanced features. Web roles create hierarchical permission structures where specialized roles inherit baseline permissions and add additional capabilities.
Page-level security uses web roles to control visibility and access. Makers assign required web roles to pages, so only users with appropriate roles see those pages in navigation or can access them via direct URLs. This content restriction ensures sensitive information remains private while public pages stay universally accessible. Child page permissions can inherit from parent pages, simplifying permission management for page hierarchies. The combination of authentication requirements and web role assignments creates granular control over site content access, enabling organizations to create differentiated experiences for anonymous visitors, authenticated users, and privileged members.
Table Permissions (Entity Permissions)
Table permissions control the most critical security aspect: what Dataverse data users can access and modify. Each table permission configuration specifies a Dataverse table, privilege level (read, write, create, delete, append, append to), and access scope determining which records users can interact with. Global access grants privileges across all table records, suitable for public reference data or administrative roles. Contact-scoped access restricts privileges to records related to the authenticated user's contact record through defined relationships, enabling scenarios like customers viewing their own orders or cases. Account-scoped access grants privileges to records related to the user's parent account, useful for business-to-business scenarios where multiple users from one company should access shared organizational data.
Table permissions associate with web roles, so users inherit all table permissions from their assigned web roles. This relationship enables role-based access control where customer roles grant access to customer data, partner roles access partner resources, and administrator roles manage portal content. Makers can configure parent-child relationships where access to parent records automatically grants access to related child records, simplifying permissions for complex data models. For example, access to a case record might automatically grant access to related case comments or attachments without separate permission configurations. Table permissions provide defense-in-depth ensuring external users only access data appropriate for their roles, preventing unauthorized information disclosure even if page-level restrictions were bypassed.
Security Best Practices
Implementing robust Power Pages security requires following established best practices beyond basic permission configuration. Apply the principle of least privilege by granting users minimum permissions necessary for their roles rather than broad access that might expose unnecessary data. Default to denying access, explicitly granting permissions where needed rather than starting with open access and attempting to restrict. Regularly audit web roles and table permissions ensuring they remain aligned with business requirements and removing unnecessary permissions that accumulated over time.
Enable multi-factor authentication for sensitive portals requiring strong identity verification, particularly those handling financial information, personal data, or valuable resources. Implement appropriate password policies for local authentication including minimum length, complexity requirements, and periodic rotation. Monitor portal audit logs identifying unusual access patterns, failed authentication attempts, or suspicious activities that might indicate security incidents. Test security configurations thoroughly using different user personas to verify permissions work as intended and data remains protected. These proactive security measures protect organizational data and maintain user trust in portal security.
Power Pages and Dataverse Integration
Data-Driven Portal Functionality
Power Pages' deep integration with Dataverse distinguishes it from traditional content management systems by enabling dynamic, data-driven functionality rather than static content. Forms on portal pages directly create or update Dataverse records, providing external data collection interfaces that feed into organizational systems. For example, a customer portal contact form creates Dataverse case records that support teams process using model-driven apps or Power Automate workflows. Lists display live Dataverse data with automatic updates as records change, ensuring portal information stays current without manual content updates. Detail pages show comprehensive information about individual Dataverse records including related data from connected tables.
This data-driven approach means portal content reflects current business state rather than requiring manual synchronization or content duplication. Customer portals show actual account balances, order statuses, and support ticket details from operational systems. Partner portals display real-time performance metrics, available leads, and earned incentives calculated from transaction data. Event portals show current session availability, attendee counts, and schedule changes from event management systems. The single source of truth in Dataverse ensures consistency across internal applications, external portals, and automated processes, eliminating data discrepancies that plague traditional multi-system approaches.
Business Logic and Automation
Portal data operations trigger Dataverse business logic including calculated fields, rollup fields, business rules, and workflows, ensuring data consistency and automating processes without portal-specific code. When portal users submit forms creating records, Dataverse calculates derived values, validates data against business rules, updates related records through workflows, and sends notifications to internal teams. For example, submitting a support request through a portal might automatically assign the case to appropriate support queues, send acknowledgment emails to customers, and create follow-up tasks for support agents through Power Automate flows.
This integration enables sophisticated scenarios like approval workflows where portal submissions route through internal approval processes before final commitment, inventory checks ensuring portal orders don't exceed available stock, credit limit validations preventing customers from placing orders beyond their terms, and document generation creating PDFs from submitted portal data. Power Automate flows can monitor portal submissions and orchestrate complex multi-step processes spanning multiple systems while portal users receive status updates through automated emails or portal notifications. The tight integration creates seamless experiences where portal actions trigger appropriate business processes without custom integration code.
Real-World Power Pages Scenarios
Scenario 1: Customer Support Portal
Business Need: Manufacturing company receives hundreds of support calls daily with customers asking about order status, submitting warranty claims, and requesting technical assistance.
Power Pages Solution:
- Site creation: Start with customer self-service portal template, customize branding and navigation
- Authentication: Azure AD B2C for customer authentication with self-service registration
- Key features: Knowledge base with searchable articles, order tracking showing status and shipping details, case submission form for support requests, download center for product manuals and warranty information
- Security: Contact-scoped table permissions ensuring customers view only their orders and cases
- Outcomes: 40% reduction in support call volume, improved customer satisfaction through 24/7 access, support team focuses on complex issues requiring expertise
Scenario 2: Partner Enablement Portal
Business Need: Software vendor works with channel partners requiring access to sales materials, training resources, deal registration, and performance tracking.
Power Pages Solution:
- Site creation: Build from starter template, create specialized sections for different partner tiers
- Authentication: Azure AD for corporate partner users, Microsoft accounts for individual partners
- Key features: Resource library with sales collateral and marketing materials, training portal with video courses and certifications, deal registration system preventing channel conflict, performance dashboards showing partner metrics
- Security: Multiple web roles (Gold Partner, Silver Partner, Registered Partner) with differentiated content access, account-scoped permissions enabling all users from one partner company to access shared deals
- Outcomes: Partners always access current materials, deal registration reduces channel conflict by 80%, partner satisfaction improves through transparent performance visibility
Scenario 3: Event Registration Portal
Business Need: Professional association hosts annual conference with thousands of attendees requiring registration, session selection, and attendee networking.
Power Pages Solution:
- Site creation: Custom site built with design studio for conference branding
- Authentication: Local authentication for attendees, optional social authentication via LinkedIn
- Key features: Event overview and speaker information, registration form collecting attendee details and dietary requirements, session catalog with descriptions and capacity limits, attendee directory enabling networking, mobile-responsive design for on-site access
- Security: Anonymous access for event information, authenticated access for registration and attendee features, organizer web role for content management
- Outcomes: Streamlined registration process increases conversion, session capacity management prevents overcrowding, attendee networking drives engagement and future attendance
Exam Preparation Tips
Key Concepts to Master
- Power Pages purpose: Creates external-facing websites for customers, partners, and public audiences
- Use cases: Customer self-service, partner portals, communities, event registration, job applications
- Site creation: Template-based starting points, design studio visual tools, no-code customization
- Authentication: Anonymous, local, or external identity providers (Azure AD, social providers)
- Web roles: Define page access and site feature permissions
- Table permissions: Control Dataverse data access with global, contact-scoped, or account-scoped privileges
- Dataverse integration: Forms, lists, and pages directly connect to business data
- Power Pages vs Power Apps: Power Pages for external users, Power Apps for internal users
Practice Questions
Sample PL-900 Exam Questions:
- Question: A company wants customers to access account information and submit support cases through a secure website. Which Power Platform component should they use?
- A) Canvas app
- B) Model-driven app
- C) Power Pages
- D) Power Automate
Answer: C) Power Pages - External customer access requires Power Pages, while Power Apps serve internal users.
- Question: What determines which Dataverse records a Power Pages user can view or modify?
- A) Web roles only
- B) Authentication provider
- C) Table permissions
- D) Page permissions
Answer: C) Table permissions - Table permissions control Dataverse record access and operations.
- Question: Which authentication method enables users to sign in with their existing Google or LinkedIn credentials?
- A) Anonymous authentication
- B) Local authentication
- C) External authentication
- D) Windows authentication
Answer: C) External authentication - External identity providers include social authentication options.
- Question: What defines which pages an authenticated user can view in a Power Pages site?
- A) Table permissions
- B) Web roles
- C) Authentication type
- D) Site template
Answer: B) Web roles - Web roles control page access and site navigation visibility.
- Question: A company wants to create a Power Pages site quickly for a partner portal. What approach should they use?
- A) Traditional web development
- B) Template-based creation
- C) Custom coding
- D) Desktop flows
Answer: B) Template-based creation - Templates provide quick starting points for common scenarios.
- Question: Which table permission scope restricts users to viewing only records related to their contact record?
- A) Global
- B) Account-scoped
- C) Contact-scoped
- D) User-scoped
Answer: C) Contact-scoped - Contact-scoped permissions restrict access to records related to the user's contact.
- Question: What tool provides visual page editing and component placement for Power Pages?
- A) Power Automate designer
- B) Form designer
- C) Design studio
- D) Solution explorer
Answer: C) Design studio - Design studio provides visual tools for Power Pages customization.
- Question: Which authentication type allows visitors to view public content without signing in?
- A) Local authentication
- B) Azure AD authentication
- C) External authentication
- D) Anonymous access
Answer: D) Anonymous access - Anonymous access enables viewing public content without authentication.
PL-900 Success Tip: Remember Power Pages creates external websites for customers and partners, while Power Apps serves internal users. Site creation uses templates and design studio without coding. Authentication supports anonymous, local, and external providers. Web roles control page access, while table permissions control Dataverse data access. Contact-scoped permissions restrict users to their own data. Focus on understanding when to use Power Pages versus other Power Platform components and how security layers protect organizational data.
Hands-On Practice Lab
Lab Objective
Explore Power Pages capabilities by creating a simple site, configuring authentication, setting permissions, and connecting to Dataverse. This lab requires Power Platform environment access with Power Pages enabled.
Lab Activities
Activity 1: Create Power Pages Site from Template
- Navigate to Power Pages: Go to make.powerpages.microsoft.com and sign in
- Create site: Click "Create a site" and browse available templates
- Select template: Choose starter portal or customer self-service template
- Name and create: Provide site name, web address, and create the site
- Wait for provisioning: Site creation takes several minutes, observe progress
- Open design studio: Once created, open the site in design studio to explore
Activity 2: Explore Design Studio
- Pages workspace: View site pages, click to edit, observe page structure
- Add section: Add new content section to a page using plus button
- Edit text: Click text to edit content, change headings and descriptions
- Styling workspace: Explore color themes, font options, and responsive settings
- Data workspace: View configured Dataverse connections, explore available tables
- Preview site: Click preview to see site as visitors would experience it
Activity 3: Configure Authentication Providers
- Open settings: Navigate to site settings or security settings
- Review authentication: Examine configured authentication providers
- Configure provider: Enable Microsoft account or other social authentication if available
- Registration settings: Review whether open registration is enabled or invitation-only
- Test authentication: Preview site and attempt to sign in or register (in test environment)
Activity 4: Explore Web Roles and Permissions
- View web roles: Navigate to security settings and view existing web roles
- Examine role: Click on "Authenticated Users" or similar role to see its configuration
- Review page access: See which pages this role can access
- Table permissions: View associated table permissions showing data access
- Understand scopes: Note whether permissions are global, contact-scoped, or account-scoped
Activity 5: Add Form to Collect Data
- Create page: Add new page to site through design studio
- Add form component: Insert form component on the page
- Configure form: Select Dataverse table (like Contact or custom table)
- Select fields: Choose which fields to display on the form
- Test form: Preview site, submit test data, verify record creation in Dataverse
Activity 6: Add List to Display Data
- Add list component: Insert list component on a page
- Select table: Choose Dataverse table to display (Account, Contact, or custom table)
- Configure columns: Select which columns to show in the list
- Add filtering: Configure filter to limit which records appear
- Test list: Preview site and verify records display correctly
Lab Outcomes
After completing this lab, you'll have hands-on experience with Power Pages site creation from templates, design studio customization tools, authentication configuration, security role examination, and data integration through forms and lists. This practical knowledge demonstrates core Power Pages capabilities tested in the PL-900 exam and provides foundation for creating external-facing websites extending organizational data and processes to external audiences.
Frequently Asked Questions
What is Microsoft Power Pages and what is it used for?
Microsoft Power Pages is a low-code platform for creating secure, data-driven external-facing websites that enable organizations to share information and interact with audiences outside their organization. Unlike Power Apps that target internal users, Power Pages creates public or authenticated websites accessible to customers, partners, vendors, or community members. Common use cases include customer self-service portals where customers access account information or submit support requests, partner portals providing access to resources and collaboration tools, event registration sites, community forums, knowledge bases, job application portals, and case management systems. Power Pages sites integrate directly with Dataverse, enabling external users to view, create, or update business data through secure web interfaces.
What are the methods for creating Power Pages sites?
Power Pages sites are created through multiple approaches depending on organizational needs and technical expertise. Template-based creation provides pre-built site templates for common scenarios like customer self-service portals, partner portals, or community sites, offering complete starting points makers customize with their branding, content, and data. Design studio provides visual tools for creating sites from scratch or extensively modifying templates through drag-and-drop page editing, component placement, styling customization, and form configuration. Makers configure data connections to Dataverse tables, add web pages, create forms and lists displaying data, apply themes matching brand identity, and publish sites to custom domains. The low-code approach enables business users to create professional websites without traditional web development skills while providing extensibility for developers needing advanced customization.
How does authentication work in Power Pages?
Power Pages supports multiple authentication methods enabling flexible access control for different user types. Anonymous access allows anyone to view public content without signing in, suitable for marketing pages or public knowledge bases. Local authentication uses Power Pages-managed user accounts with username and password credentials stored in Dataverse. External authentication integrates with identity providers including Azure AD B2C, Azure AD, Microsoft accounts, LinkedIn, Google, Facebook, or custom OAuth providers, enabling users to sign in with existing credentials without creating separate accounts. Organizations configure which authentication providers are available, whether registration is open or invitation-only, and what information is collected during registration. Multi-factor authentication can be enforced through identity providers for enhanced security. After authentication, users receive specific permissions determining what data they can access and what actions they can perform.
What are web roles in Power Pages?
Web roles define collections of permissions assigned to authenticated users controlling what they can access and do within Power Pages sites. Each web role specifies which web pages users can view, what site features they can access, and which forms or lists they can interact with. Users can have multiple web roles, with their effective permissions being the union of all assigned roles. Common web role patterns include anonymous users accessing public content, authenticated users viewing restricted pages, administrators managing site content, and specialized roles like premium members or partners accessing exclusive resources. Web roles integrate with table permissions determining data access, creating comprehensive security models controlling both site navigation and data operations. Organizations typically create web roles matching business user types like customers, partners, employees, or community members.
What are table permissions in Power Pages?
Table permissions (formerly entity permissions) control which Dataverse table records authenticated users can access and what operations they can perform. Each table permission defines scope (global access to all records, contact-scoped to records related to the authenticated user, or account-scoped to records related to the user's parent account) and privileges (read, write, create, delete, append, append to). Table permissions associate with web roles, so users inherit table permissions from their assigned web roles. Organizations configure table permissions matching business requirements, like customers viewing only their own cases and orders, partners accessing shared resources, or administrators managing all records. Complex scenarios use parent-child relationships where access to parent records automatically grants access to related child records. Table permissions provide granular data security ensuring external users see only appropriate information.
How does Power Pages integrate with Dataverse?
Power Pages integrates natively with Dataverse as its primary data source, enabling sites to display, collect, and modify business data stored in Dataverse tables. Forms on Power Pages create or update Dataverse records, lists display filtered Dataverse records, and detail pages show complete record information. This integration enables external users to interact with organizational data through secure web interfaces without direct Dataverse access. Changes made through Power Pages sites trigger Dataverse business logic including workflows, calculated fields, and business rules, maintaining data consistency across all applications. Power Pages respects Dataverse security through table permissions, ensuring external users only access authorized data. The deep integration means Power Pages sites, model-driven apps, canvas apps, and Power Automate flows all work with the same data, creating unified business solutions spanning internal and external users.
What types of content can Power Pages sites include?
Power Pages sites include diverse content types supporting various business scenarios. Web pages provide information through text, images, videos, and formatted content using rich text editors. Forms collect or display Dataverse data with validation, conditional logic, and multi-step wizards guiding users through complex processes. Lists show collections of Dataverse records with filtering, sorting, searching, and pagination enabling users to find relevant information. Detail pages display complete information about individual records. File attachments enable document uploads and downloads. Navigation menus guide users through site structure. Search functionality helps users find content quickly. Advanced content includes charts and dashboards visualizing data, calendars showing events, maps displaying locations, and embedded Power BI reports. Sites are responsive, automatically adapting layouts for mobile phones, tablets, and desktop computers, ensuring consistent experiences across all devices.
What is the difference between Power Pages and Power Apps?
Power Pages creates external-facing public or authenticated websites accessible to audiences outside the organization including customers, partners, or community members, while Power Apps creates internal business applications for employees and known internal users. Power Pages sites are web-based, accessed through browsers without requiring app installation, optimized for anonymous or lightly authenticated external users. Power Apps includes canvas and model-driven apps that typically require organizational licenses and authentication. Power Pages emphasizes information sharing, data collection from external sources, and self-service scenarios, while Power Apps emphasizes internal business process automation and operational applications. Both integrate with Dataverse and can be used together, with Power Pages providing external interfaces and Power Apps handling internal workflows. Organizations use Power Pages when they need to expose data or functionality to external audiences and Power Apps for internal employee productivity.
Written by Joe De Coppi - Last Updated November 14, 2025