Study guide
9.3 Standard Connectors, Custom Connectors & Connection References
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
9.3 Standard Connectors, Custom Connectors & Connection References
Key Takeaways Explain This Topic AI
Connectors wrap RESTful APIs into declarative triggers and actions, categorized into Standard (included in M365 seed licenses) and Premium (requiring standalone Power Automate licenses).
Custom Connectors allow organizations to integrate proprietary or legacy REST APIs by importing OpenAPI (Swagger 2.0/3.0) specifications, Postman collections, or configuring endpoints manually.
Custom Connectors support four primary authentication schemes: No Authentication, Basic Authentication, API Key, and OAuth 2.0 (including Microsoft Entra ID and generic OAuth providers).
Policy Templates inside Custom Connectors enable no-code request/response transformations such as header injection, URL rewriting, and JSON property mapping.
Connection References decouple flow definitions from user-specific credentials, serving as solution proxies essential for healthy Application Lifecycle Management (ALM) across Dev, Test, and Prod environments.
Last updated: August 2026
Standard Connectors, Custom Connectors & Connection References
Connectors are the fundamental architectural bridges that enable Microsoft Power Platform applications and flows to communicate with external services, databases, cloud platforms, and on-premises systems. Operating as declarative wrappers around RESTful APIs, connectors translate underlying HTTP endpoints, OpenAPI specifications, and JSON schemas into user-friendly triggers and actions. For the PL-200: Microsoft Power Platform Functional Consultant exam, you must understand connector tier classifications, author and secure Custom Connectors, and implement Connection References to ensure healthy, enterprise-grade Application Lifecycle Management (ALM).
1. Power Platform Connector Architecture & Tiers
A Connector is a proxy wrapper around a RESTful web service that exposes the service's API endpoints as structured Triggers and Actions in Power Automate and Power Apps. +-----------------------------------------------------------------------------+
- | POWER PLATFORM CONNECTOR ARCHITECTURE |
- | |
- | +-------------------+ +--------------------+ |
- | | POWER AUTOMATE / | ----> | CONNECTOR | |
- | | POWER APPS | | (OpenAPI Proxy) | |
- | +-------------------+ +--------------------+ |
- | | |
- | +-------------------+-------------------+ |
- | | | |
- | v v |
- | +--------------------+ +--------------------+ |
- | | STANDARD CONNECTORS| | PREMIUM CONNECTORS | |
- | | - Office 365 / M365| | - Dataverse | |
- | | - SharePoint Online| | - SQL Server | |
- | | - OneDrive / Teams | | - Salesforce / SAP | |
- | | - Forms / Planner | | - HTTP / Webhooks | |
- | | - Included in seed | | - Premium license | |
- | +--------------------+ +--------------------+ |
- | | |
- | v |
- | +--------------------+ |
- | | CUSTOM CONNECTORS | |
- | | - Proprietary APIs | |
- | | - OpenAPI / Postman| |
- | | - Premium license | |
- | +--------------------+ |
- +-----------------------------------------------------------------------------+
- Connector Classification Tiers
Classification Representative Connectors Licensing Requirement
Standard Connectors SharePoint Online, OneDrive for Business, Office 365 Outlook, Microsoft Teams, Microsoft Forms, Microsoft Planner, Excel Online (Business), RSS, World Time. Included with standard Microsoft 365 seed licenses and base Power Apps licenses.
Premium Connectors Microsoft Dataverse, SQL Server, Oracle Database, Salesforce, SAP ERP, Azure DevOps, Azure Blob Storage, Service Bus, HTTP , HTTP with Microsoft Entra ID . Requires standalone Power Apps (per user/app) or Power Automate (Premium/Process) licensing.
Custom Connectors Bespoke connectors authored for internal line-of-business REST APIs, proprietary third-party cloud services, or on-premises endpoints. Treated as Premium ; requires standalone Power Apps or Power Automate licensing.
Important
The HTTP Connector Rule for PL-200: Adding a generic HTTP or HTTP with Microsoft Entra ID action to any flow immediately elevates the entire flow to Premium , even if all other triggers and actions use Standard connectors (like SharePoint or Outlook). Organizations cannot bypass Premium licensing by calling external APIs via raw HTTP actions without standalone licenses.
Data Loss Prevention (DLP) Connector Categorization
Power Platform Administrators govern connector usage across environments using Data Loss Prevention (DLP) policies, grouping connectors into three compliance buckets:
Business (Confidential): Connectors permitted to share business data (e.g., Dataverse, SharePoint, ERP).
Non-Business (No Business Data Allowed): Personal and consumer connectors (e.g., Twitter/X, Facebook, Gmail).
Blocked: Connectors completely prohibited from running in the environment.
Rule: Connectors in the Business group cannot share data with connectors in the Non-Business group within the same flow or app.
2. Custom Connectors Architecture & Development
When prebuilt connectors do not exist for an internal microservice, proprietary ERP, or niche SaaS platform, functional consultants and developers author a Custom Connector . +-----------------------------------------------------------------------------+
- | CUSTOM CONNECTOR AUTHORING METHODS |
- | |
- | [1. OPENAPI SPECIFICATION] ---> Import Swagger 2.0 or OpenAPI 3.0 |
- | (JSON or YAML definition file) |
- | |
- | [2. POSTMAN COLLECTION] ---> Import Postman Collection (v1 / v2) |
- | with preconfigured request samples |
- | |
- | [3. MAKER PORTAL WIZARD] ---> Define Host, Base URL, Endpoints, |
- | and JSON Request/Response schemas |
- | |
- | [4. AZURE SERVICE EXPORT] ---> Direct 1-click export from Azure |
- | API Management or Azure App Service |
- +-----------------------------------------------------------------------------+
- Custom Connector Authentication Types
When provisioning a Custom Connector, you must select one of four security authentication protocols: +-----------------------------------------------------------------------------+
- | CUSTOM CONNECTOR AUTHENTICATION SCHEMES |
- | |
- | [NO AUTHENTICATION] ---> Public endpoints, open weather/stock APIs |
- | |
- | [BASIC AUTHENTICATION] ---> Username & Password (Base64 encoded) |
- | |
- | [API KEY] ---> Static token passed in Header, Query, |
- | or Custom Header (e.g., X-API-Key) |
- | |
- | [OAUTH 2.0] ---> Enterprise Identity Providers: |
- | - Microsoft Entra ID (Azure AD) |
- | - Google, GitHub, Salesforce, Generic |
- | - Authorization Code Grant |
- | - Client Credentials Grant |
- +-----------------------------------------------------------------------------+
- Configuring OAuth 2.0 with Microsoft Entra ID
Integrating an internal REST API secured by Microsoft Entra ID requires standard OAuth 2.0 handshake configuration:
Identity Provider: Select Azure Active Directory .
Client ID & Client Secret: Generated during App Registration in Microsoft Entra admin center.
Login URL: Default is https://login.microsoftonline.com .
Tenant ID: common (multi-tenant) or specific Tenant GUID (single-tenant).
Resource URL: The Application ID URI of the backend API (e.g., api://contoso-inventory-service ).
Redirect URL: Automatically generated by Power Automate after saving the connector (e.g., https://global.consent.azure-apim.net/redirect ). Must be copied and pasted into the Entra ID App Registration's Redirect URIs .
Policy Templates (No-Code Request/Response Transformation)
Policy Templates allow makers to modify outbound HTTP requests and inbound responses without writing custom middleware code:
Set HTTP header : Injects static or dynamic headers (e.g., injecting an authorization token or tenant identifier).
Set query parameter : Appends mandatory URL query string parameters.
Route request : Redirects requests dynamically to different base paths or hosting servers.
Set property / Convert array to object : Modifies JSON payload structures on the fly to match flow requirements.
3. Connection References & Enterprise ALM
In early Power Platform architectures, cloud flows stored hardcoded connection references pointing directly to individual user connection instances ( /connections/shared_sharepointonline/a1b2c3... ). This created severe Application Lifecycle Management (ALM) failures:
Exporting a solution from Dev and importing into Test/Prod failed because the developer's personal connection did not exist in target environments.
Flows were imported in a disabled state, requiring administrators to manually open every flow and re-authenticate each connection.
Breached security compliance by embedding developer identities in production assets. +-----------------------------------------------------------------------------+
- | CONNECTION REFERENCE ALM ARCHITECTURE |
- | |
- | [DEVELOPMENT ENVIRONMENT] |
- | +---------------------------------------------------------------------+ |
- | | FLOW DEFINITION: References 'cr123_SharePoint_ConnRef' (Proxy) | |
- | | | | |
- | | v | |
- | | CONNECTION REFERENCE: Points to -> [Dev User Connection] | |
- | +---------------------------------------------------------------------+ |
- | | |
- | v (Export Solution as Managed) |
- | +---------------------------------------------------------------------+ |
- | | SOLUTION ZIP: Contains Flow JSON + Connection Reference Metadata | |
- | | (NO HARDCODED PERSONAL CREDENTIALS OR CONNECTION GUIDS!) | |
- | +---------------------------------------------------------------------+ |
- | | |
- | v (Import Solution into Production) |
- | [PRODUCTION ENVIRONMENT] |
- | +---------------------------------------------------------------------+ |
- | | FLOW DEFINITION: Unchanged! References 'cr123_SharePoint_ConnRef' | |
- | | | | |
- | | v | |
- | | CONNECTION REFERENCE: Bound to -> [Production Service Principal / | |
- | | Service Account Connection] | |
- | +---------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------+
- How Connection References Function
A Connection Reference is a Dataverse solution component ( connectionreference ) that acts as an abstraction proxy between a cloud flow action and the actual physical connection in the environment:
Solution Component: Connection references reside natively inside solutions with a publisher prefix (e.g., cr123_shared_dataverse_89abc ).
Flow Decoupling: Inside the flow JSON definition, actions call the Connection Reference Logical Name rather than a hardcoded connection GUID.
Target Binding: During solution deployment to Test or Production, automated deployment pipelines (or the solution import wizard) prompt administrators to map the Connection Reference to an existing connection in the target environment—such as a dedicated Service Principal connection.
Deployment Automation with deploymentSettings.json
In enterprise DevOps pipelines (using Azure DevOps Power Platform Build Tools, GitHub Actions, or Power Platform CLI pac ), connection references are bound automatically without manual intervention using a deployment settings configuration file: {
- "ConnectionReferences": [
- {
- "LogicalName": "cr123_shared_sharepointonline_45a67",
- "ConnectionId": "prod-sharepoint-service-account-guid",
- "ConnectorId": "/providers/Microsoft.PowerApps/apis/shared_sharepointonline"
- },
- {
- "LogicalName": "cr123_shared_dataverse_89b01",
- "ConnectionId": "prod-service-principal-connection-guid",
- "ConnectorId": "/providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps"
- }
- ],
- "EnvironmentVariables": [
- {
- "SchemaName": "cr123_SharePointSiteUrl",
- "Value": "https://contoso.sharepoint.com/sites/ProductionOperations"
- }
- ]
- }
Command-line execution via Power Platform CLI: pac solution import --path MySolution_managed.zip --settings-file deploymentSettings.json --activate-plugins
Tip
ALM Best Practice (PL-200 Exam): Always create Connection References inside a solution before creating cloud flows. When adding actions in the modern flow designer, ensure the action uses the solution Connection Reference rather than an ad-hoc personal connection. This ensures flows remain 100% solution-aware and deploy cleanly via automated CI/CD pipelines.