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:
Plan and configure agent solutions (30–35%)
--> Create and monitor agent flows in Copilot Studio
--> Configure actions and 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
One of the greatest strengths of Microsoft Copilot Studio is its ability to connect AI agents with business applications, enterprise data sources, cloud services, and custom APIs. Rather than simply answering questions, an agent can perform meaningful work on behalf of users by executing actions through connectors.
Actions allow agents to retrieve information, update records, create tickets, send emails, approve requests, trigger workflows, and interact with virtually any connected business system.
Connectors provide the communication bridge between Copilot Studio and external services such as Microsoft 365, Microsoft Dynamics 365, Microsoft Dataverse, Microsoft Fabric, Azure services, Salesforce, ServiceNow, SAP, SQL Server, SharePoint, and thousands of other systems.
For the AB-620 certification exam, you should understand how actions and connectors work together, how to configure them securely, when to use different connector types, and how they support enterprise automation.
What Are Actions?
An action is a task that an AI agent performs in response to user input or workflow logic.
Unlike conversational responses, actions interact with external systems to accomplish business tasks.
Examples include:
- Creating a support ticket
- Looking up customer information
- Sending an email
- Updating a CRM record
- Creating a calendar event
- Starting an approval workflow
- Creating a purchase order
- Retrieving inventory levels
- Executing a REST API
- Running a Power Automate flow
Actions transform an AI agent from an information provider into an intelligent business assistant.
What Are Connectors?
A connector is a communication interface that allows Copilot Studio to securely connect to an external service.
Connectors manage:
- Authentication
- Authorization
- API communication
- Data formatting
- Request execution
- Response handling
Instead of writing code to interact with APIs, developers can configure connectors that expose operations as reusable actions.
How Actions and Connectors Work Together
The overall process typically follows these steps:
- User submits a request.
- Agent understands the intent.
- Agent selects an appropriate action.
- Action uses a connector.
- Connector authenticates with the external service.
- External system performs the requested operation.
- Results are returned to the agent.
- Agent presents the response to the user.
Example:
User:
“Schedule a meeting with Sarah tomorrow.”
Agent:
- Identifies scheduling intent.
- Uses the Outlook connector.
- Creates a calendar event.
- Confirms success to the user.
Types of Connectors
Copilot Studio supports several connector types.
Standard Connectors
Standard connectors provide access to many Microsoft and third-party services.
Examples include:
- Outlook
- SharePoint
- OneDrive
- Excel
- Microsoft Teams
- SQL Server
- Azure DevOps
- Planner
These connectors require little or no custom development.
Premium Connectors
Premium connectors typically connect to enterprise applications.
Examples include:
- Salesforce
- ServiceNow
- SAP
- Oracle
- Adobe
- Azure AI Search
- Dynamics 365
Organizations usually require appropriate licensing for premium connectors.
Custom Connectors
When no built-in connector exists, organizations can create custom connectors.
Custom connectors expose:
- Internal APIs
- Legacy applications
- Proprietary services
- Industry-specific platforms
They allow Copilot Studio to integrate with virtually any REST-based service.
REST API Tools
Copilot Studio can invoke REST APIs directly.
REST API actions require configuration of:
- Endpoint URL
- HTTP method
- Parameters
- Headers
- Authentication
- Request body
- Response schema
REST tools are ideal for integrating with modern web services.
Common Microsoft Connectors
Frequently used connectors include:
| Connector | Common Purpose |
|---|---|
| Outlook | Send emails, manage calendars |
| Microsoft Teams | Send chat messages and notifications |
| SharePoint | Read and update documents |
| Dataverse | Store and retrieve business data |
| SQL Server | Query relational databases |
| Azure AI Search | Ground agent responses with enterprise knowledge |
| Dynamics 365 | CRM and ERP operations |
| Power Automate | Execute workflows |
| Excel | Read and update spreadsheets |
| OneDrive | Manage files |
Configuring an Action
Creating an action generally involves these steps:
- Select the connector.
- Authenticate.
- Choose the operation.
- Configure required parameters.
- Configure optional parameters.
- Test the action.
- Save and publish.
Once configured, the action becomes available within conversations and workflows.
Authentication
Every connector must authenticate before accessing external resources.
Common authentication methods include:
- Microsoft Entra ID (Azure AD)
- OAuth 2.0
- API keys
- Basic authentication (legacy scenarios)
- Service principals
- Managed identities (supported scenarios)
Authentication should follow organizational security policies.
Authorization
Authentication identifies the user or application.
Authorization determines what resources may be accessed.
Examples:
- Read customer records
- Update inventory
- Create invoices
- Delete documents
Authorization should always follow the principle of least privilege.
Connection References
Power Platform environments often use connection references.
Connection references:
- Separate solution components from connection details.
- Simplify deployment between environments.
- Reduce manual configuration.
- Improve Application Lifecycle Management (ALM).
They are especially useful when moving solutions from development to testing and production.
Using Power Automate Actions
Many Copilot Studio actions invoke Power Automate flows.
Typical scenarios include:
- Multi-step approvals
- Document generation
- Database updates
- Email notifications
- Scheduled processing
- Enterprise orchestration
Power Automate allows complex business logic to remain outside the conversational layer.
Input Parameters
Actions often require user input.
Examples:
- Customer ID
- Order number
- Email address
- Product SKU
- Invoice number
- Employee ID
Copilot Studio can collect missing information during the conversation before invoking the action.
Output Parameters
After execution, actions return information to the agent.
Examples:
- Success status
- Customer details
- Ticket number
- Invoice total
- Order status
- Error message
The agent can use this information to continue the conversation naturally.
Error Handling
Actions should gracefully handle failures.
Examples include:
- Authentication failure
- Network timeout
- Invalid input
- API unavailable
- Permission denied
- Resource not found
- Rate limiting
Well-designed agents provide helpful guidance rather than exposing technical errors.
Example:
Instead of:
“HTTP 403 Forbidden.”
Respond:
“I don’t have permission to complete that request. Please contact your administrator or try again using an account with the required permissions.”
Retry Logic
Some failures are temporary.
Examples:
- Network interruption
- API timeout
- Temporary service outage
Retry logic can automatically attempt the operation again before reporting failure.
Security Best Practices
When configuring connectors:
- Use secure authentication methods.
- Protect credentials.
- Avoid hardcoded secrets.
- Apply least-privilege permissions.
- Use approved enterprise connectors.
- Follow Data Loss Prevention (DLP) policies.
- Monitor connector usage.
- Rotate secrets when required.
- Audit access regularly.
Data Loss Prevention (DLP)
Power Platform administrators can define DLP policies that control how connectors are used.
DLP policies help prevent:
- Sensitive data leakage
- Unauthorized data movement
- Mixing business and personal connectors
- Compliance violations
For example, an organization may prohibit copying data from Dataverse into personal cloud storage services.
Monitoring Connector Usage
Administrators should monitor:
- Failed actions
- API latency
- Authentication failures
- Connector health
- Rate limits
- Usage frequency
- Error rates
- Flow performance
Monitoring improves reliability and troubleshooting.
Performance Considerations
Efficient actions improve user experience.
Recommendations include:
- Minimize unnecessary API calls.
- Request only required data.
- Reuse existing connectors.
- Cache data when appropriate.
- Reduce sequential operations.
- Handle pagination efficiently.
- Optimize Power Automate flows.
Governance Considerations
Organizations should establish governance for connectors by:
- Approving supported connectors
- Managing custom connector lifecycle
- Reviewing permissions
- Monitoring usage
- Auditing actions
- Documenting integrations
- Applying environment strategies
- Following change management procedures
Common Design Mistakes
Avoid:
- Granting excessive permissions
- Ignoring DLP policies
- Hardcoding API credentials
- Failing to validate user input
- Poor error handling
- Creating duplicate connectors
- Ignoring connection references
- Returning technical error messages to users
Best Practices
- Choose the simplest connector that satisfies the business requirement.
- Prefer built-in connectors when available.
- Use custom connectors only when necessary.
- Secure authentication using Microsoft Entra ID or OAuth whenever possible.
- Validate inputs before invoking actions.
- Design user-friendly error messages.
- Monitor connector health and usage.
- Apply least-privilege access.
- Test actions thoroughly before deployment.
- Document all external integrations.
Exam Tips
For the AB-620 exam, remember these key points:
- Actions perform business operations, while connectors provide access to external systems.
- Standard connectors require minimal configuration and support many Microsoft services.
- Premium connectors often require additional licensing and connect to enterprise applications.
- Custom connectors enable integration with proprietary or unsupported REST APIs.
- Power Automate is commonly used to orchestrate complex business processes from Copilot Studio.
- Connection references simplify solution deployment across environments.
- Always secure connectors using appropriate authentication and least-privilege permissions.
- DLP policies govern how connectors can exchange data.
- Validate inputs and handle connector errors gracefully.
- Monitor connector performance, failures, and usage after deployment.
Practice Exam Questions
Question 1
A Copilot Studio agent needs to create a customer support ticket in an external help desk application. What enables the agent to communicate with that application?
A. A connector
B. A conversation topic
C. A knowledge source
D. A variable
Correct Answer: A
Explanation: Connectors provide the communication interface between Copilot Studio and external services, allowing actions such as creating support tickets.
Question 2
Which statement best describes an action in Copilot Studio?
A. A conversation greeting
B. A reusable business operation performed by an agent
C. A deployment environment
D. A security role
Correct Answer: B
Explanation: Actions execute business tasks such as creating records, sending emails, retrieving data, or calling APIs.
Question 3
An organization must integrate with an internal REST service that has no existing Power Platform connector. Which approach should be used?
A. Use an Adaptive Card
B. Create a Dataverse table
C. Create a custom connector
D. Use conversation variables only
Correct Answer: C
Explanation: Custom connectors expose proprietary or unsupported REST APIs so they can be used as actions within Copilot Studio.
Question 4
Why are connection references recommended when deploying solutions between development and production environments?
A. They eliminate authentication.
B. They permanently embed credentials into solutions.
C. They replace Power Automate.
D. They separate connection details from solution components, simplifying deployment.
Correct Answer: D
Explanation: Connection references improve application lifecycle management by allowing connections to be updated without modifying solution components.
Question 5
Which authentication method is most commonly used with Microsoft cloud services?
A. FTP authentication
B. Microsoft Entra ID (Azure AD)
C. Anonymous authentication
D. Telnet authentication
Correct Answer: B
Explanation: Microsoft Entra ID provides secure identity and access management for Microsoft cloud services and many enterprise integrations.
Question 6
Which Power Platform feature helps prevent sensitive business data from being shared with unauthorized connectors?
A. Conversation history
B. Adaptive Cards
C. Data Loss Prevention (DLP) policies
D. Session variables
Correct Answer: C
Explanation: DLP policies classify connectors and restrict data movement between approved and unapproved services.
Question 7
A connector returns an HTTP timeout while retrieving customer information. What should the agent do?
A. Display the raw HTTP error to the user
B. Retry the operation when appropriate and provide a friendly message if it still fails
C. Ignore the error
D. Delete the connector
Correct Answer: B
Explanation: Temporary failures should be handled gracefully using retry logic and user-friendly error messages.
Question 8
Why should organizations follow the principle of least privilege when configuring connectors?
A. To maximize API usage
B. To eliminate authentication
C. To reduce licensing costs
D. To grant only the permissions required to perform the intended business tasks
Correct Answer: D
Explanation: Least-privilege access minimizes security risks by limiting permissions to only those necessary for the connector’s purpose.
Question 9
Which service is commonly invoked from Copilot Studio to orchestrate multi-step business workflows such as approvals and notifications?
A. Microsoft Paint
B. Microsoft Visio
C. Power Automate
D. Windows Task Scheduler
Correct Answer: C
Explanation: Power Automate is frequently used to execute complex workflows, approvals, notifications, and integrations initiated by Copilot Studio actions.
Question 10
What is the primary benefit of using a built-in standard connector instead of creating a custom connector?
A. It removes all authentication requirements.
B. It generally requires less configuration and maintenance while providing supported integration with common services.
C. It automatically bypasses DLP policies.
D. It can only connect to Microsoft Dataverse.
Correct Answer: B
Explanation: Standard connectors are prebuilt, tested, and supported, reducing development effort and simplifying maintenance compared to custom connectors.
Go to the AB-620 Exam Prep Hub main page
The Data Community 