Study guide
8.3 External Identity Providers & Authentication Configuration
Microsoft Power Platform Functional Consultant PL-200
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Dataverse Tables, Relationships & Core Columns
1.1 Dataverse Table Types, Properties & Ownership 1.2 Table Relationships & Cascading Rules 1.3 Column Types, Formats, Primary Keys & Alternate Keys 1.4 Rollup, Calculated & Formula Columns with Power Fx
2 Chapter 2: Dataverse Data Management & Governance
2.1 Dataverse Search, Quick Find & Relevance Indexing 2.2 Auditing Configuration & Log Management 2.3 Duplicate Detection Rules & Settings 2.4 Bulk Record Operations, Data Import, Export & Templates
3 Chapter 3: Dataverse Security Model & Access Control
3.1 Business Units, Ownership Models & Modern BU Matrix 3.2 Security Roles, Privileges & Depth Levels 3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams 3.4 Column-Level Security & Hierarchy Security Models
4 Chapter 4: Model-Driven App Fundamentals & Information Architecture
4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer 4.2 Form Types: Main, Quick Create, Quick View & Card Forms 4.3 View Configuration, System Views, Personal Views & Filters
5 Chapter 5: Advanced Model-Driven App Components & Custom Pages
5.1 Custom Pages & Modern Commanding with Power Fx 5.2 Form Component Controls & Specialized UX Elements 5.3 Embedding Canvas Apps in Model-Driven Forms 5.4 Embedding Power BI Reports, Dashboards & Tiles
6 Chapter 6: Canvas Apps Structure, Formulas & Data Operations
6.1 Canvas App Architecture, Screens, Containers & Controls 6.2 Power Fx Formulas, Delegation & Data Source Limits 6.3 Variables (Context, Global), Collections & State Management 6.4 Triggering Power Automate Cloud Flows from Canvas Apps
7 Chapter 7: Power Pages Site Design, Navigation & Content
7.1 Power Pages Design Studio & Site Structure 7.2 Power Pages Templates, Styling & Responsive Layouts 7.3 Web Pages, Navigation Menus & Content Snippets
8 Chapter 8: Power Pages Data Integration, Forms & Web Roles
8.1 Power Pages Lists, Basic Forms & Advanced Forms 8.2 Table Permissions, Web Roles & Page Access Security 8.3 External Identity Providers & Authentication Configuration
9 Chapter 9: Power Automate Cloud Flow Fundamentals & Triggers
9.1 Cloud Flow Types: Automated, Instant, Scheduled & Desktop Overview 9.2 Dataverse Connector Triggers & Operational Filters 9.3 Standard Connectors, Custom Connectors & Connection References
10 Chapter 10: Cloud Flow Actions, Expressions & Logic Controls
10.1 Logic Controls: Conditions, Switches, Apply to Each & Do Until Loops 10.2 Variables, Data Operations & Dynamic Content Manipulation 10.3 Power Automate Expression Language (WDL / Functions) 10.4 Error Handling, Configure Run After & Scope Controls
11 Chapter 11: Business Process Flows & Guided Processes
11.1 Business Process Flow Architecture, Stages, Steps & Data Steps 11.2 Branching Rules & Multi-Entity Business Process Flows 11.3 BPF Action Steps, Workflows & Cloud Flow Execution 11.4 BPF Security Roles, Order & Process Lifecycle
12 Chapter 12: Classic Workflows, Business Rules & Modern Logic Extensibility
12.1 Classic Dataverse Workflows: Real-Time vs. Background (Async) 12.2 Business Rules: Scope & Actions 12.3 Low-Code Plug-ins in Dataverse: Automated vs. Instant 12.4 Troubleshooting Automations, Run History & Analytics
13 Chapter 13: Power Platform Environment Architecture & Security
13.1 Environment Types: Default, Sandbox, Production, Trial, Developer 13.2 Environment Governance, Groups, Routing & Capacity Management 13.3 Data Loss Prevention (DLP) Policies & Connector Classifications
14 Chapter 14: Application Lifecycle Management (ALM) & Solutions
14.1 Unmanaged vs. Managed Solutions & Solution Layering Mechanics 14.2 Solution Components, Dependencies, Publishers & Prefixes 14.3 Exporting, Importing, Upgrading & Patches 14.4 Solution Checker, App Checker & ALM Best Practices
15 Chapter 15: Enterprise Interoperability & Service Integration
15.1 Exchange / Server-Side Synchronization & Email Integration 15.2 SharePoint & OneDrive Document Management Integration 15.3 Microsoft Word & Excel Document Templates
16 Chapter 16: Copilot, AI Capabilities & Exam Strategy
16.1 Copilot Studio & Generative AI across Power Platform 16.2 AI Builder Prebuilt & Custom Models in Apps and Flows 16.3 PL-200 Exam Strategy, Time Management & Question Analysis
8.3 External Identity Providers & Authentication Configuration
Key Takeaways Explain This Topic AI
Power Pages external authentication decouples external user access from internal Dataverse user licenses: every authenticated portal user maps directly to a 1:1 Contact record in Dataverse.
External identity provider tokens (subject GUIDs/object IDs) are persisted in the adx_externalidentity table, linking external claims to the corresponding Dataverse Contact record.
Power Pages natively supports modern identity providers including Microsoft Entra ID, Microsoft Entra External ID (Azure AD B2C), Google, LinkedIn, Facebook, and standard OpenID Connect (OIDC) / SAML 2.0 protocols.
Portal registration workflows are governed by Site Settings: Authentication/Registration/OpenRegistrationEnabled enables public sign-ups, while InvitationEnabled restricts access to pre-issued invitation codes.
Portal Invitations (adx_invitation) allow organizations to onboard users by pre-assigning Web Roles, pre-populating Contact attributes, and delivering single-use secure redemption URLs.
Last updated: August 2026
External Identity Providers & Authentication Configuration
A critical value proposition of Microsoft Power Pages is its ability to provide secure, authenticated access to external stakeholders without requiring expensive internal Microsoft 365 or Power Apps per-user licenses. To achieve this, Power Pages implements a standards-based authentication architecture that integrates with enterprise identity providers (IdPs), social networks, and customer identity solutions.
For the PL-200: Microsoft Power Platform Functional Consultant exam, you must master how external users are mapped to Dataverse Contact records, how to configure external Identity Providers (including Microsoft Entra ID and Entra External ID / Azure AD B2C), how to control registration behaviors using Site Settings , and how to execute secure Portal Invitation onboarding workflows.
1. Portal Authentication Architecture & Contact Mapping
Power Pages strictly separates internal staff (who authenticate as systemuser records using internal Entra ID organizational accounts) from external portal visitors. Every external authenticated portal user is represented as a Contact ( contact ) record in Dataverse. +-----------------------------------------------------------------------------------+
- | POWER PAGES IDENTITY MAPPING ARCHITECTURE |
- | |
- | [EXTERNAL USER / BROWSER] |
- | │ |
- | ▼ 1. Authenticates against external IdP (Entra ID, B2C, Google, OIDC) |
- | [IDENTITY PROVIDER] ───> Issues Identity Token (Issuer + Subject OID / Claim) |
- | │ |
- | ▼ 2. Token passed to Power Pages Portal Engine |
- | [adx_externalidentity TABLE] |
- | ├── Identity Provider Key (e.g., https://login.microsoftonline.com/...) |
- | ├── Username / Subject ID (e.g., 8f7b2c14-55d6-4a92-...) |
- | └── Lookup to Contact (contactid) |
- | │ |
- | ▼ 3. Resolves 1:1 Contact Record |
- | [DATAVERSE CONTACT RECORD] ───> Linked to Web Roles & Table Permissions |
- +-----------------------------------------------------------------------------------+
- The adx_externalidentity Table
When a user signs in through an external identity provider, Power Pages does not store their password in Dataverse. Instead, the portal engine queries the External Identity ( adx_externalidentity ) table to map the external identity claim to a Dataverse Contact:
Identity Provider (Issuer): Stores the unique URI identifier of the IdP (e.g., Azure AD B2C authority or Google issuer).
Username / Subject ID: Stores the unique Object Identifier (OID) or sub claim provided in the IdP's JWT token.
Contact Lookup: Links directly to the matching contact record.
Note
Multi-Provider Linking: A single Dataverse Contact record can have multiple linked adx_externalidentity records. This allows a customer to sign in interchangeably using their corporate Entra ID account, Google account, or LinkedIn profile while maintaining a single unified portal profile and transaction history.
2. Supported Identity Providers & Protocols
Power Pages supports modern authentication protocols configurable through the Set up workspace in Power Pages Design Studio or via Site Settings in the Power Pages Management app: +-----------------------------------------------------------------------------------+
- | SUPPORTED IDENTITY PROVIDERS |
- | |
- | [ENTERPRISE DIRECTORIES] [CUSTOMER IDENTITY (CIAM)] |
- | - Microsoft Entra ID (Azure AD) - Microsoft Entra External ID (Azure AD B2C) |
- | - Single & Multi-Tenant - Custom User Flows & MFA |
- | |
- | [STANDARD PROTOCOLS] [COMMERCIAL & SOCIAL] |
- | - OpenID Connect (OIDC) - Google, LinkedIn, Microsoft Account (MSA) |
- | - SAML 2.0 - Facebook, Twitter (X) |
- | - WS-Federation |
- +-----------------------------------------------------------------------------------+
- Identity Provider Types & Characteristics
Identity Provider Type Primary Protocol Best Use Case Key Configuration Parameters
Microsoft Entra ID OpenID Connect B2B partner portals, vendor access where external partners already have Microsoft organizational accounts. Authority , ClientId , ClientSecret , RedirectUri
Microsoft Entra External ID (Azure AD B2C) OpenID Connect Recommended for B2C customer portals. Highly scalable consumer identity management with self-registration, password reset, and MFA user flows. Authority , ClientId , RedirectUri , SignUpSignInPolicyId , ResetPasswordPolicyId
OpenID Connect (Generic) OIDC / OAuth 2.0 Integrating with third-party enterprise IdPs like Okta, PingFederate, Auth0, or custom OAuth servers. MetadataAddress , ClientId , ClientSecret , Scope
SAML 2.0 SAML 2.0 WebSSO Legacy enterprise SSO federations (e.g., Active Directory Federation Services - ADFS, Shibboleth). MetadataAddress , ServiceProviderEntityId , AssertionConsumerServiceUrl
Social Providers OAuth 2.0 Public citizen portals, consumer feedback sites (Google, LinkedIn, Facebook). ClientId (App ID), ClientSecret (App Secret)
3. Site Settings for Registration & User Lifecycle
Authentication behavior in Power Pages is governed by key Site Settings stored in Dataverse. These settings control whether registration is public, invitation-only, or disabled, and enforce credential security standards. +-----------------------------------------------------------------------------------+
- | PORTAL REGISTRATION SITE SETTINGS |
- | |
- | [Authentication/Registration/Enabled] ─────────────────> Master registration on |
- | |
- | [Authentication/Registration/OpenRegistrationEnabled] ─> Allow public sign-up |
- | without invitation |
- | |
- | [Authentication/Registration/InvitationEnabled] ───────> Allow redeeming |
- | invitation codes |
- | |
- | [Authentication/Registration/LocalLoginEnabled] ────────> Allow local username/ |
- | passwords in Dataverse |
- | (RECOMMENDED: FALSE) |
- +-----------------------------------------------------------------------------------+
- Key Authentication Site Settings
Site Setting Key Default Value Functional Impact & Best Practice
Authentication/Registration/Enabled true Enables or disables all registration workflows on the portal. If false , no new users can register under any mechanism.
Authentication/Registration/OpenRegistrationEnabled true If true , any visitor can register and create a portal account. For private or restricted portals, set to false to prevent unauthorized sign-ups.
Authentication/Registration/InvitationEnabled true Enables the /Register?invitation= endpoint, allowing users to redeem secure invitation codes.
Authentication/Registration/LocalLoginEnabled false (modern) Controls whether users can create a local username and password stored in Dataverse. Security Best Practice: Set to false in production to eliminate local credential storage risks and mandate modern IdPs with MFA.
Authentication/Registration/RequiresConfirmation false When set to true , requires the user to click a confirmation link sent to their email before their account is activated.
Authentication/Registration/RequiresUniqueEmail true Enforces that no two Contact records can register using the same email address.
Authentication/Registration/RememberBrowserEnabled true Allows persistent authentication cookies across browser sessions.
4. Portal Invitation Onboarding Lifecycle
When organizations need to onboard specific external partners, contractors, or VIP clients into a secured portal, they utilize Portal Invitations ( adx_invitation ). This ensures that only pre-approved individuals can access the site, while automatically granting them the correct Web Roles and linking to existing Dataverse records. +-----------------------------------------------------------------------------------+
- | PORTAL INVITATION REDEMPTION LIFECYCLE |
- | |
- | [1. CREATE INVITATION RECORD] |
- | ├── Target Contact: Links to existing Contact (Jane Doe) |
- | ├── Pre-Assigned Web Roles: Assigns 'Partner Admin' role |
- | ├── Type: Single-Use (Individual) or Group Invitation |
- | └── Generates unique Invitation Code (e.g., A7X9-K2M4-P8Q1) |
- | │ |
- | ▼ |
- | [2. DELIVER INVITATION EMAIL] |
- | └── Sends link: https://portal.contoso.com/Register?invitation=A7X9-K2M4-P8Q1 |
- | │ |
- | ▼ |
- | [3. USER REDEEMS INVITATION] |
- | ├── Clicks link and selects external IdP (e.g., Entra ID / B2C) |
- | ├── Authenticates successfully with external credentials |
- | ├── System creates adx_externalidentity record linked to Jane Doe |
- | ├── System assigns 'Partner Admin' Web Role to Jane Doe |
- | └── Invitation record status transitions to 'Redeemed' |
- +-----------------------------------------------------------------------------------+
- Invitation Configuration Options
Single-Use vs. Group Invitations:
Single-Use (Individual): Linked to a specific pre-existing Contact record. Can only be redeemed once. Once redeemed, its state changes to Redeemed and cannot be reused.
Group Invitation: Not linked to a pre-existing Contact. Allows a specified maximum number of redemptions, creating a new Contact record for each user who redeems the code.
Automatic Web Role Assignment:
Consultants associate one or more Web Roles directly to the Invitation record.
The moment the invitation is redeemed, the portal engine automatically writes the association to the adx_webrole_contact table, immediately granting the user their authorized permissions.
Account Association:
If the target Contact is already linked to a parent account (e.g., "Fabrikam Inc"), all Account-scoped Table Permissions become active immediately upon redemption.
5. Portal User Profile & Lifecycle Management
Once registered, external user accounts must be maintained throughout their lifecycle:
Profile Page Management:
Power Pages includes a built-in Profile web page ( /profile ) where authenticated users can view and update their personal information (First Name, Last Name, Email, Phone Number, Preferred Language).
Changes made on the Profile page update the underlying Dataverse contact record in real time.
Profile completion can be made mandatory before accessing other site pages via the Authentication/Registration/ProfileRedirectEnabled setting.
Deactivating / Revoking Portal Access:
To immediately revoke a user's portal access without deleting historical transaction data:
Method 1 (Deactivate Contact): Deactivating the contact record in Dataverse immediately blocks all authentication and table access.
Method 2 (Revoke Web Roles): Removing the user's custom Web Roles restricts them to baseline Authenticated Users permissions.
Method 3 (Delete External Identity): Deleting the corresponding row in adx_externalidentity breaks the link between their external IdP and the Dataverse Contact record.