This post is a part of the AB-620: Designing and Building Integrated AI Agent Solutions in Copilot Studio Exam Prep Hub.
This topic falls under these sections:
Integrate and extend agents in Copilot Studio (40–45%)
   --> Connect to enterprise knowledge sources
      --> Connect to Microsoft Power Platform connectors

Note that there are 10 practice questions (with answers) at the end of each section to help you solidify your knowledge of the material. Also, there are 4 practice tests with 30 questions each available from the hub's main page below the exam topics section.

Introduction

Microsoft Power Platform connectors are one of the most important integration capabilities available in Microsoft Copilot Studio. They allow agents to securely connect to hundreds of Microsoft services, third-party SaaS platforms, on-premises systems, and custom business applications without requiring developers to write extensive integration code.

For the AB-620 exam, you should understand:

• What Power Platform connectors are
• The difference between connectors and Copilot connectors
• Standard versus Premium connectors
• Built-in versus custom connectors
• Authentication methods
• How connectors are used within topics, tools, and actions
• Best practices for connector selection and configuration

Unlike Copilot connectors, which primarily expose enterprise knowledge for AI grounding and search, Power Platform connectors allow agents to perform actions, retrieve live data, and interact with business applications.

What Are Microsoft Power Platform Connectors?

A connector is a reusable component that enables applications and workflows to communicate with an external system.

Think of a connector as a translator that understands:

• Authentication
• API requests
• Data formats
• Error handling
• Responses

Without connectors, developers would need to manually build and maintain API integrations.

With connectors, Copilot Studio can communicate with external systems through a graphical interface.

How Connectors Work

The typical process is:

User
   ↓
Copilot Studio Agent
   ↓
Power Platform Connector
   ↓
External Service
   ↓
Response
   ↓
Agent
   ↓
User

Example:

User:

“Show me today’s support tickets.”

The agent:

1. Receives the request.
2. Calls a ServiceNow connector.
3. Retrieves ticket information.
4. Formats the response.
5. Displays the results.

Benefits of Power Platform Connectors

Connectors provide several advantages:

Low-Code Development

Developers avoid writing custom REST API code for common services.

Benefits include:

• Faster development
• Easier maintenance
• Reduced complexity
• Consistent authentication

Hundreds of Prebuilt Integrations

Microsoft provides connectors for many enterprise platforms.

Examples include:

Microsoft services

• SharePoint
• Outlook
• Teams
• Excel
• OneDrive
• Dataverse
• SQL Server
• Azure DevOps
• Dynamics 365
• Microsoft Forms

Third-party services

• Salesforce
• ServiceNow
• Dropbox
• Google Drive
• GitHub
• Slack
• Jira
• SAP
• Adobe
• DocuSign

Secure Authentication

Connectors manage:

• OAuth
• API keys
• Basic authentication
• Microsoft Entra ID authentication
• Service principals (where supported)

Users typically authenticate once, after which the connection can be reused.

Consistent Experience

Regardless of the external system, connectors provide:

• Standardized configuration
• Uniform authentication
• Predictable inputs
• Predictable outputs

This simplifies development.

Standard vs. Premium Connectors

One of Microsoft’s favorite certification topics is connector licensing.

Standard Connectors

Standard connectors are included with many Microsoft Power Platform licenses.

Examples include:

• Outlook
• OneDrive
• Microsoft Teams
• Excel Online
• SharePoint
• Office 365 Users
• Microsoft Forms

These connectors commonly support Microsoft 365 productivity scenarios.

Premium Connectors

Premium connectors require additional licensing.

Examples include:

• Salesforce
• ServiceNow
• SAP
• Oracle
• Azure DevOps
• SQL Server (certain scenarios)
• Adobe Sign
• DocuSign

Premium connectors often provide access to enterprise business applications.

Exam Tip

Know that connector licensing affects solution deployment.

If a solution uses Premium connectors, users may require Premium licensing.

Built-In vs. Custom Connectors

Built-In Connectors

Microsoft maintains built-in connectors.

Advantages include:

• Supported by Microsoft
• Regular updates
• Reliable authentication
• Easy configuration
• Extensive documentation

Whenever possible, use a built-in connector.

Custom Connectors

A custom connector is created when no existing connector supports the required API.

Custom connectors expose any REST API as a reusable Power Platform connector.

Typical scenarios include:

• Internal business systems
• Proprietary applications
• Legacy APIs
• Industry-specific services
• Custom cloud applications

Example:

A company has an internal inventory API.

Instead of calling the REST API directly throughout multiple agents, developers create one custom connector that everyone can reuse.

Connector Components

A connector consists of several important elements.

Connection

The authenticated relationship between Power Platform and the external system.

A connection stores:

• Credentials
• Tokens
• Authentication settings

Example:

An authenticated SharePoint connection.

Actions

Actions perform operations.

Examples:

• Create record
• Update customer
• Delete item
• Send email
• Create Teams message
• Start approval

Actions typically change data.

Triggers

In Power Automate, connectors may include triggers that initiate flows when an event occurs.

Examples:

• New email arrives
• File uploaded
• Row added
• Ticket created

Although Copilot Studio primarily invokes actions, understanding triggers helps when integrating with Power Automate.

Parameters

Actions require inputs.

Example:

Create calendar event

Parameters:

• Subject
• Start time
• End time
• Location

The agent supplies these values.

Outputs

The connector returns information.

Examples:

• Customer ID
• Ticket number
• Order status
• Email address
• Document URL

Outputs can populate variables and drive subsequent conversation steps.

Authentication Methods

Authentication is an important AB-620 exam objective.

OAuth 2.0

Most Microsoft services use OAuth.

Advantages:

• Secure
• Token-based
• No password stored
• Industry standard

Common examples:

• SharePoint
• Outlook
• Teams
• Microsoft Graph
• Dynamics

Microsoft Entra ID Authentication

Many enterprise connectors authenticate through Microsoft Entra ID.

Benefits:

• Single sign-on
• Central identity management
• Conditional Access support
• MFA support

API Keys

Some external services require API keys.

Example:

Weather APIs

Configuration generally includes:

• Key
• Endpoint
• Authentication header

Basic Authentication

Some older APIs still use username/password authentication.

Although supported in some scenarios, Microsoft generally recommends more secure authentication methods whenever possible.

Anonymous Authentication

Rarely used in enterprise environments.

Appropriate only for:

• Public APIs
• Public data feeds
• Open information services

Using Connectors in Copilot Studio

Connectors can be invoked from several places within Copilot Studio.

Topics

Within a topic, connector actions allow agents to retrieve or update external information.

Example:

Customer asks:

“What is my current order status?”

The topic:

• Collects the order number.
• Calls the Order connector.
• Retrieves the status.
• Displays the response.

Agent Flows

Flows frequently use connectors.

Example:

Agent Flow:

Receive request
        ↓
SharePoint connector
        ↓
SQL connector
        ↓
Teams connector
        ↓
Return confirmation

Tools

Tools frequently expose connector functionality.

Examples:

• Create support ticket
• Lookup customer
• Update CRM
• Retrieve invoice
• Submit expense report

The agent selects the appropriate tool during the conversation.

Common Microsoft Connectors Used in Copilot Studio

SharePoint

Common uses:

• Retrieve documents
• Read lists
• Update lists
• Store files
• Search content

Typical scenarios:

• Employee handbook
• Knowledge base
• Project documentation

Dataverse

Dataverse is Microsoft’s primary business data platform.

Common operations:

• Read records
• Create rows
• Update rows
• Delete records
• Query business data

Many Power Apps solutions use Dataverse.

Outlook

Common actions:

• Send email
• Retrieve calendar events
• Create meetings
• Read messages

Microsoft Teams

Frequently used for:

• Send chat messages
• Post channel messages
• Create teams
• Retrieve team information
• Notify users

Excel Online

Useful for:

• Reading worksheets
• Updating tables
• Reporting
• Importing structured information

SQL Server

Often used for:

• Customer databases
• Inventory systems
• Sales reporting
• Operational data

SQL connectors are common in enterprise scenarios.

OneDrive

Supports:

• File storage
• File retrieval
• Document creation
• File updates
• Shared content

Azure DevOps

Useful for development teams.

Actions include:

• Create work items
• Update bugs
• Read projects
• Retrieve pipelines

Best Practices for Choosing Connectors

When selecting connectors:

• Prefer Microsoft-supported connectors whenever possible.
• Reuse existing connectors instead of creating duplicates.
• Use the least privileged authentication required.
• Avoid unnecessary Premium connectors if Standard connectors meet the business need.
• Validate licensing requirements before deployment.
• Document connector usage and dependencies.
• Monitor connector health and authentication status.
• Test connectors in development environments before moving to production.

Common Exam Scenarios

You should be able to identify the appropriate connector for scenarios such as:

Key Takeaways from the topics covered so far

• Power Platform connectors enable Copilot Studio agents to interact with external applications and services.
• They simplify integration by abstracting API complexity.
• Standard connectors are included with many Power Platform licenses, while Premium connectors may require additional licensing.
• Built-in connectors should generally be used before creating custom connectors.
• Common authentication methods include OAuth 2.0, Microsoft Entra ID, API keys, and, in limited cases, Basic Authentication.
• Connectors can be used in topics, agent flows, and tools to retrieve information or perform business actions.
• Microsoft provides connectors for hundreds of Microsoft and third-party services, making them a foundational capability for enterprise Copilot Studio solutions.

Advanced Connector Scenarios

Enterprise Copilot Studio solutions often require more than simply connecting to Microsoft 365 services. Organizations frequently integrate with custom business systems, multiple environments, and external APIs while maintaining security and governance.

For the AB-620 exam, expect scenario-based questions that require selecting the appropriate connector strategy based on business requirements.

Custom Connectors

When no Microsoft-provided connector exists, Power Platform allows you to create a Custom Connector.

A custom connector wraps an external REST API into a reusable Power Platform connector that behaves like any built-in connector.

Common Uses

• Internal HR systems
• Custom CRM applications
• Manufacturing systems
• Inventory applications
• Industry-specific SaaS platforms
• Legacy business applications
• Proprietary cloud services

Instead of writing HTTP requests throughout every topic, developers create a single custom connector that can be reused by multiple agents and Power Automate flows.

Components of a Custom Connector

A custom connector generally includes:

• Connector name
• API host URL
• Base path
• Authentication configuration
• Operations (actions)
• Request definitions
• Response definitions
• Sample payloads
• Error responses

Well-designed connectors provide descriptive parameter names and clear documentation for reuse.

Connection References

A connection stores authentication information for a connector.

A connection reference points to a connection and allows solutions to remain portable across environments.

For example:

Development Environment

↓

Connection Reference

↓

Development SQL Connection

Production Environment

↓

Same Connection Reference

↓

Production SQL Connection

This allows solutions to be imported into another environment without modifying every topic or flow.

Benefits

• Easier deployments
• Environment portability
• Reduced maintenance
• Better Application Lifecycle Management (ALM)
• Improved solution management

Environment Strategies

Most organizations maintain multiple Power Platform environments.

Typical environments include:

• Development
• Test
• User Acceptance Testing (UAT)
• Production

Each environment should maintain its own:

• Connections
• Credentials
• Connection references
• Environment variables
• Security roles

This prevents developers from accidentally accessing production data while developing.

Environment Variables

Environment variables eliminate hardcoded configuration values.

Examples include:

• API URLs
• Tenant IDs
• Storage account names
• SQL Server names
• Azure resource names
• Queue names

Instead of changing topics after deployment, administrators update the environment variable.

Example

Development:

https://dev-api.contoso.com

Production:

https://api.contoso.com

The topic itself never changes.

Security Best Practices

Security is one of the most heavily tested areas of enterprise Copilot Studio implementations.

Principle of Least Privilege

Grant only the permissions required.

Avoid:

• Global administrators
• Highly privileged service accounts
• Shared administrative credentials

Prefer:

• Read-only permissions when appropriate
• Dedicated service accounts
• Microsoft Entra ID identities
• Managed identities (where applicable)

Secure Authentication

Prefer:

• OAuth 2.0
• Microsoft Entra ID
• Modern authentication

Avoid:

• Hardcoded passwords
• Plain text credentials
• Shared accounts

Credential Management

Rotate credentials regularly.

Monitor:

• Expired credentials
• Disabled accounts
• Revoked permissions
• Authentication failures

Data Loss Prevention (DLP) Policies

DLP policies are a major governance feature within Power Platform.

They control how connectors can be used together.

Purpose

Prevent sensitive organizational data from moving into unauthorized systems.

Example

Allowed

Dataverse

↓

SharePoint

↓

Teams

Blocked

Dataverse

↓

Twitter

↓

Personal Dropbox

The policy prevents accidental data leakage.

Business Connectors

Business connectors contain trusted organizational data.

Examples

• SharePoint
• SQL Server
• Dataverse
• Dynamics 365
• SAP

Non-Business Connectors

These may include consumer or public services.

Examples

• Twitter
• Dropbox Personal
• Gmail
• Consumer cloud storage

Many organizations separate Business and Non-Business connectors.

Blocked Connectors

Administrators may completely disable certain connectors.

Reasons include:

• Compliance
• Security
• Industry regulations
• Corporate governance

Governance

Large organizations often manage hundreds of connectors.

Governance ensures:

• Standardization
• Compliance
• Security
• Lifecycle management

Naming Standards

Use meaningful connector names.

Good examples:

• HR Employee API
• Customer CRM Connector
• Inventory Management API

Avoid names like:

• TestConnector
• API2
• NewConnector

Documentation

Document:

• Authentication method
• Owner
• Purpose
• Supported operations
• Dependencies
• Required permissions
• Version history

Ownership

Each connector should have:

• Technical owner
• Business owner
• Support contact

This improves maintenance and accountability.

Performance Optimization

Good connector design improves user experience.

Return Only Required Data

Avoid retrieving unnecessary information.

Instead of:

Return every customer record.

Use:

Return only the requested customer.

Smaller responses improve performance.

Minimize Connector Calls

Avoid making repeated requests for identical information.

Instead:

Retrieve once

↓

Store in variable

↓

Reuse throughout the conversation

Use Appropriate Filtering

Instead of retrieving an entire database:

Filter by:

• Customer ID
• Ticket number
• Date
• Status

Filtering reduces processing time.

Reuse Existing Connectors

Avoid creating duplicate connectors that perform identical operations.

Benefits include:

• Easier maintenance
• Fewer authentication issues
• Better governance
• Simpler documentation

Troubleshooting Connector Issues

Authentication Failures

Possible causes:

• Expired OAuth token
• Password change
• Disabled account
• Invalid API key
• Revoked permissions

Resolution:

• Reauthenticate
• Verify permissions
• Refresh credentials
• Review authentication settings

Connector Not Appearing

Possible causes:

• Wrong environment
• DLP policy restriction
• Licensing limitation
• Connector not installed

Access Denied

Possible causes:

• Insufficient permissions
• Security role limitations
• Missing API permissions
• Conditional Access policies

Incorrect Data Returned

Possible causes:

• Wrong parameters
• Incorrect filtering
• Invalid environment
• Stale data
• Mapping errors

Slow Performance

Possible causes:

• Too many connector calls
• Large datasets
• Poor filtering
• Network latency
• External API performance

Comparing Connector Types

AB-620 Exam Tips

Remember these key concepts:

• Power Platform connectors are primarily used to perform actions and retrieve live business data.
• Copilot connectors are primarily used for grounding AI responses with enterprise knowledge.
• Use built-in connectors before creating custom connectors.
• Connection references improve solution portability across environments.
• Environment variables eliminate hardcoded configuration values.
• OAuth 2.0 and Microsoft Entra ID are the preferred authentication methods.
• DLP policies control how connectors can be combined to protect sensitive data.
• Minimize connector calls and retrieve only the required data for better performance.
• Use the principle of least privilege when configuring connector permissions.
• Test connectors thoroughly in development environments before deploying to production.

Practice Exam Questions

Question 1

A company needs to integrate Copilot Studio with a proprietary inventory management REST API that has no Microsoft-provided connector.

What is the BEST solution?

A. Create a Custom Connector.

B. Use a Copilot connector.

C. Replace the API with SharePoint.

D. Store the API documentation in Dataverse.

Correct Answer: A

Explanation:
Custom connectors allow organizations to integrate unsupported REST APIs into Power Platform solutions.

Question 2

Why are connection references recommended when deploying solutions between environments?

A. They eliminate authentication.

B. They automatically upgrade connector versions.

C. They allow solutions to use different connections without modifying topics or flows.

D. They improve AI response quality.

Correct Answer: C

Explanation:
Connection references separate solution components from environment-specific connections, simplifying deployment.

Question 3

An administrator wants to prevent confidential Dataverse information from being copied into personal cloud storage services.

Which Power Platform feature should be configured?

A. Adaptive Cards

B. Environment Variables

C. AI Builder

D. Data Loss Prevention (DLP) policies

Correct Answer: D

Explanation:
DLP policies govern which connectors can exchange data and help prevent unauthorized data movement.

Question 4

A topic retrieves customer information three separate times during one conversation.

What is the BEST optimization?

A. Replace Dataverse with Excel.

B. Store the retrieved information in a variable and reuse it.

C. Create three separate connectors.

D. Disable authentication.

Correct Answer: B

Explanation:
Caching retrieved data in variables reduces unnecessary connector calls and improves performance.

Question 5

Which authentication method is recommended for most Microsoft enterprise services?

A. Anonymous authentication

B. Basic authentication

C. OAuth 2.0 with Microsoft Entra ID

D. API keys only

Correct Answer: C

Explanation:
OAuth 2.0 integrated with Microsoft Entra ID provides secure, modern authentication with support for enterprise identity features.

Question 6

What is the primary purpose of environment variables?

A. Increase API speed.

B. Store configuration values that differ between environments.

C. Replace connectors.

D. Encrypt connector traffic.

Correct Answer: B

Explanation:
Environment variables store configurable values, such as API endpoints, without requiring changes to solution logic.

Question 7

An organization has separate Development, Test, and Production environments.

Which practice is recommended?

A. Use one shared production connection in every environment.

B. Disable connector authentication in development.

C. Maintain separate connections and credentials for each environment.

D. Copy production data into every environment.

Correct Answer: C

Explanation:
Each environment should have its own connections and credentials to support safe development and deployment practices.

Question 8

A connector returns thousands of unnecessary records when only one customer is requested.

What should be improved?

A. Increase the AI model temperature.

B. Disable connector caching.

C. Use broader queries.

D. Apply filtering to retrieve only the required records.

Correct Answer: D

Explanation:
Filtering reduces response size, improves performance, and minimizes unnecessary processing.

Question 9

Which statement correctly distinguishes Power Platform connectors from Copilot connectors?

A. Both are used only for enterprise search.

B. Power Platform connectors perform actions and retrieve live data, while Copilot connectors primarily provide grounded enterprise knowledge.

C. Copilot connectors replace Power Automate.

D. Power Platform connectors cannot interact with Microsoft services.

Correct Answer: B

Explanation:
Power Platform connectors are action-oriented, whereas Copilot connectors are designed primarily for indexing and grounding enterprise knowledge.

Question 10

A security review finds that a service account used by a connector has Global Administrator permissions, although it only needs to read SharePoint documents.

What should be recommended?

A. Leave the permissions unchanged.

B. Create another Global Administrator account.

C. Grant the minimum permissions required according to the principle of least privilege.

D. Replace the connector with a custom connector.

Correct Answer: C

Explanation:
The principle of least privilege reduces security risk by granting only the permissions necessary to perform required operations.

AB-620 Exam Readiness Checklist

By the time you finish this topic, you should be able to:

• ✔ Explain the purpose of Microsoft Power Platform connectors.
• ✔ Distinguish between Power Platform connectors, Copilot connectors, and Custom connectors.
• ✔ Choose between Standard and Premium connectors based on licensing and business needs.
• ✔ Configure secure authentication using OAuth 2.0 and Microsoft Entra ID.
• ✔ Understand the role of connections, connection references, and environment variables in Application Lifecycle Management (ALM).
• ✔ Design connector implementations that follow the principle of least privilege.
• ✔ Explain how Data Loss Prevention (DLP) policies govern connector usage and protect organizational data.
• ✔ Optimize connector performance by minimizing calls, filtering data, and reusing variables.
• ✔ Troubleshoot common authentication, permission, environment, and performance issues.
• ✔ Recommend governance and deployment best practices for enterprise-scale Copilot Studio solutions.

Go to the AB-620 Exam Prep Hub main page