Power Pages - Connectivity to Microsoft Dataverse (Full Explanation)

Power Pages – Connectivity to Microsoft Dataverse (Full Explanation)

Understand how Power Pages securely connects to Dataverse using Azure AD, S2S authentication, Application Users, and backend integration.

1. Server-to-Server (S2S) Connection Overview

When a Power Pages site is created, an Azure AD (Microsoft Entra) application is automatically provisioned. This application uses a secure X.509 authentication certificate to request tokens and communicate with Dataverse.

  • The Azure AD app name usually follows: Portals - portalid
  • Never delete or modify this app - the website will stop functioning
  • The authentication certificate key expires every 2 years and must be rotated
Connectivity Diagram:

Microsoft provides a visual diagram showing how Power Pages securely communicates with Dataverse through Azure AD.

View Dataverse ↔ Power Pages Connectivity Diagram

2. Dataverse Integration Through Application User

Earlier, portals used the SYSTEM user to perform all operations. Now, Power Pages uses a dedicated Application User in Dataverse. This improves tracking, auditing, and overall security.

  • View S2S App Users in Admin Center → Environment → Settings → Users + Permission → Application Users → #Portals -SiteName
  • These users have specific roles like:
    • Portal Application User
    • Service Writer
    • Service Deleter
  • Never remove these roles-they control Dataverse access
Application User Screenshot:

Microsoft provides a screenshot that shows how the application user appears in Dataverse.

View Application User Screenshot

3. Migration & Customization Checks

Microsoft is migrating older portals to the new Application User model. Before migration, verify your customizations to prevent authentication issues.

Important Items to Review

  • Update FetchXML or Liquid that filters by SYSTEM user
  • Check workflows owned by SYSTEM - reassign if needed
  • Always validate changes in a sandbox before production deployment

Comments

Post a Comment

Popular posts from this blog

Part 1: Creating Code Apps in Power Apps - A step-by-step guide (with real errors I faced & how I fixed them)

Image
Intro In this post I’ll walk you through how I set up a code-based app for Power Apps (React/Vite front-end + Power Platform CLI for packaging/deployment), the exact errors I ran into, and how I solved them. If you want a hands-on, copy-paste able guide that covers Node versions, pac auth, environment issues, and packaging tips, this is for you. Prerequisites Microsoft 365 account with access to a Power Platform environment Node.js ( 20.19+  recommended LTS) VS Code Install power platform tools extension in VS Code. Steps: Step 1 : Open Visual Studio Code and launch the integrated terminal. Step 2: In the terminal, run the following commands one by one.   mkdir D:\CodeApps - Force cd D:\CodeApps npm create vite @latest myfirstapp -- -- template react - ts cd D:\CodeApps\myfirstapp npm install Initially, I ran the command: npm create vite@latest MyFirstApp -- --template react-ts This gave the error: Invalid package.json name The issue was caused because package...
Read more

Calling Microsoft Graph API from Power Automate Using Azure App Services – Step-by-Step Guide

Image
Step 1: You should have an Azure subscription, or if you have access to the Microsoft Entra Admin Center, you can create an app from there. This app can then be used in Power Automate to connect to Microsoft Graph API. Step 2: Click on "New registration" , provide a name for your app, assign the required API permissions (such as Microsoft Graph permissions), and then click "Register" to complete the app registration process. Step 3: After registration, you'll be redirected to the app's overview page. From there, navigate to the API permissions tab and click "Add a permission" to assign the necessary Microsoft Graph API permissions. Step 4: Select Microsoft Graph as the API, and based on your requirements, choose the appropriate permissions. In my case, I selected Application permissions , which do not require user sign-in and are suitable for background services or automation. Step 5: Select the required Microsoft Graph API permissions. Yo...
Read more

Step-by-Step Guide: Power Automate Custom Connector Using Graph API from Azure App Service

Image
Step 1: Open Power Automate, navigate to the Custom Connectors tab, and select Create from blank as shown in the image below. custom connector(click image for better resolution) Step 2: In the General tab, upload an icon (less than 1MB), add a description, select the correct scheme (in my case, HTTPS ), and provide the host name. For example, if your API URL is https://graph.microsoft.com/v1.0/users/{email} , the host name will be the highlighted part — graph.microsoft.com . Step 3: Go to the Security tab. Here, you need to select the authentication method. Choose OAuth 2.0 as the authentication type, as shown in the image below. Step 4: Select the Identity Provider as Azure Active Directory . Check the box Enable Service Principal Support . This option allows you to create a connection using a Client ID and Client Secret instead of using the user's own authentication. Next, provide the Client ID , Client Secret , Tenant ID , and other required details as shown in t...
Read more