Integrating with Dynamics 365

Microsoft Power Pages (formerly Power Apps Portals) is designed to work seamlessly with Dynamics 365, making it easy to expose Dynamics 365 data and business logic to external users through a secure and customizable website. This integration empowers businesses to offer self-service portals, partner and vendor collaboration sites, customer support centers, and more—using real-time Dynamics 365 data from within the portal.

Below is a complete and detailed guide on how to integrate Power Pages with Dynamics 365, including setup steps, data modeling, authentication, and best practices.

Why Integrate Power Pages with Dynamics 365?

Power Pages provides a low-code website platform built directly on Microsoft Dataverse, which is also the underlying data platform for Dynamics 365 apps such as:

Dynamics 365 Sales
Dynamics 365 Customer Service
Dynamics 365 Field Service
Dynamics 365 Marketing
Dynamics 365 Project Operations

Since both Power Pages and Dynamics 365 use Dataverse, integration is native and real-time. This allows for:

Displaying and submitting Dynamics 365 records on the portal
Exposing customer service cases to customers
Allowing vendors to view and update project data
Automating approvals and workflows with Power Automate
Tracking interactions and telemetry in Dynamics 365 apps

Integration Approaches

There are three main ways to integrate Power Pages with Dynamics 365:

Using Entity (Table) Forms and Lists – Expose Dataverse tables used by D365
Using Web APIs or Virtual Tables – Extend integration to external sources
Embedding Dynamics 365 Apps – Integrate parts of D365 UI via iframe or APIs

Step-by-Step Integration Process

Step 1: Verify Your Dynamics 365 and Power Pages Environments

Both Power Pages and Dynamics 365 should be deployed in the same environment or Dataverse instance.
This ensures shared access to tables, workflows, and security roles.

Go to Power Platform Admin Center to confirm.

Step 2: Identify Tables (Entities) to Expose

In Dynamics 365, decide which tables you want to expose through Power Pages, such as:

Contact – For user profiles
Case – For support ticket tracking
Opportunity – For partner sales leads
Work Order – For field service
Custom tables – For industry-specific use cases

All standard/custom tables in D365 are available for use in Power Pages.

Step 3: Configure Table Permissions in Power Pages

Use Table Permissions to securely expose Dynamics 365 data:

In Power Pages Studio:
- Go to Data > Table Permissions
- Create new permission set for each table (e.g., Case_ReadOnly)
- Set the scope: Global, Contact, Account, or Self
- Assign appropriate Web Roles
Associate the Table Permission with:
- List (to display multiple records)
- Form (to display a single record)

Step 4: Use Entity Lists and Entity Forms

Entity Lists:

Display multiple records from Dynamics 365
Can include sorting, filtering, search, and links to forms

Entity Forms:

Display/edit individual Dynamics 365 records
Use for record submission, updates, or read-only display

You can configure both using Power Pages Studio or the legacy Portal Management App.

Step 5: Create Web Roles and Control Access

Power Pages uses Web Roles to manage user access, similar to Dynamics 365 security roles.

Go to Portal Management > Web Roles
Create roles like Authenticated Customer, Partner, Technician
Assign appropriate Table Permissions
Users are granted roles upon login (based on contact record)

Map external users to Dynamics 365 Contact or Account records.

Step 6: Set Up Authentication

Allow portal users to sign in using:

Azure AD B2C – Recommended for external users
Microsoft Entra ID (Azure AD) – For internal use
Social providers – Google, Facebook, LinkedIn

Link external users to their Contact entity in Dataverse, enabling CRM-specific interactions such as ticket submission and updates.

Step 7: Trigger Business Logic with Power Automate

Integrate Dynamics 365 workflows into Power Pages actions:

Trigger Power Automate flows on form submission
Automate approvals, create related records, or send notifications
Use HTTP steps to connect to Dynamics 365 APIs if needed

Use Case Examples

Customer Service Portal

Display cases (from Case table)
Enable support request submission
Let customers view case status and updates

Partner Collaboration Portal

Allow access to Opportunities and Quotes
Submit documents or project updates
Role-based visibility for leads and contracts

Vendor Management Portal

Track work orders or inventory
View payment history
Submit invoices or proposals

Security and Compliance

Power Pages includes enterprise-grade security:

Role-based access with Web Roles and Table Permissions
Audit logs for access and data changes
GDPR compliance tools built into Dataverse
Secure data storage via Dataverse encryption

Best Practices

Always use least-privilege access when creating roles
Keep portal pages and lists lightweight for faster performance
Use custom plug-ins or Power Automate to replicate Dynamics 365 behavior in portals
Test using different user roles and permissions

Licensing Considerations

Licensing is based on Power Pages authenticated user plans. Dynamics 365 licenses are not enough for external portal access.

Scenario	Required License
Internal user accessing D365	Dynamics 365 license
External user accessing portal	Power Pages license
Embedded Dynamics 365 UI	Not directly supported – use data only

Each authenticated external user needs a Power Pages capacity license.