AB-620, Microsoft Certification

Plan integration with enterprise systems (AB-620 Exam Prep)

 
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%)
   --> Plan an agent solution
      --> Plan integration with enterprise systems

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

Modern AI agents are most valuable when they can interact with enterprise systems rather than simply answer questions. In Microsoft Copilot Studio, enterprise integration enables agents to retrieve business data, perform actions, automate workflows, and collaborate with existing applications across an organization.

For the AB-620 exam, you should understand how to plan an integration strategy before building the agent. The exam focuses less on memorizing specific connectors and more on selecting the appropriate integration approach based on business requirements, security, scalability, maintainability, governance, and user experience.

Planning enterprise integration involves determining:

  • Which systems the agent must access
  • Whether the agent should read data, perform actions, or both
  • Which integration technology is most appropriate
  • How authentication and authorization will work
  • How enterprise knowledge should be grounded
  • How the solution will be governed and monitored

A well-designed integration strategy produces secure, scalable, maintainable AI solutions.

Why Enterprise Integration Matters

Without enterprise integration, an AI agent typically provides only general conversational capabilities.

Enterprise integration enables an agent to:

  • Retrieve customer information
  • Create support tickets
  • Update CRM records
  • Access ERP data
  • Search internal documentation
  • Submit approvals
  • Trigger workflows
  • Query databases
  • Interact with line-of-business applications
  • Coordinate work between multiple AI agents

The agent becomes an active participant in business processes rather than a passive chatbot.

Enterprise Systems Commonly Integrated

Organizations often connect Copilot Studio agents to:

Microsoft 365

Examples include:

  • Outlook
  • Teams
  • SharePoint
  • OneDrive
  • Planner

Example:

A user asks:

“Schedule a meeting with the finance team.”

The agent retrieves calendars and creates the meeting.

Dynamics 365

Examples include:

  • Customer Service
  • Sales
  • Finance
  • Field Service

Example:

“Show open opportunities for Contoso.”

The agent retrieves CRM data.

Power Platform

Including:

  • Power Automate
  • Power Apps
  • Dataverse

Example:

The agent launches an approval workflow using Power Automate.

External SaaS Applications

Examples include:

  • Salesforce
  • ServiceNow
  • Workday
  • SAP
  • Oracle
  • Jira
  • Zendesk

These are often accessed through connectors or REST APIs.

Custom Applications

Organizations frequently have internal systems.

Integration methods include:

  • REST APIs
  • Custom connectors
  • MCP servers
  • Azure services

Databases

Examples include:

  • Azure SQL
  • SQL Server
  • Oracle
  • PostgreSQL

Agents typically access these through APIs or Power Automate rather than direct database queries.

Types of Enterprise Integration

Integration generally falls into three categories.

1. Read Data

The agent retrieves information.

Examples:

  • Product inventory
  • Employee directory
  • HR policies
  • Customer orders
  • Knowledge articles

These operations are generally lower risk.

2. Perform Actions

The agent updates external systems.

Examples:

  • Create a support case
  • Approve a request
  • Submit an expense report
  • Update a customer record
  • Send an email

These operations require stronger security controls.

3. Hybrid

Most enterprise agents both:

  • Retrieve information
  • Perform actions

Example:

User:

“Book vacation for next Friday.”

The agent:

  • Checks vacation balance
  • Verifies manager
  • Submits leave request
  • Sends confirmation

Integration Options in Copilot Studio

Several technologies are available.

Understanding when to use each one is an important exam objective.

Power Platform Connectors

Best for:

  • Standard business systems

Examples:

  • SharePoint
  • Outlook
  • Dynamics 365
  • SQL
  • Salesforce

Advantages:

  • Low-code
  • Easy authentication
  • Microsoft-managed
  • Hundreds of built-in connectors

Use connectors whenever an existing connector meets business requirements.

Power Automate Flows

Best for:

  • Multi-step automation

Example:

Agent receives:

“Create a new employee.”

Power Automate then:

  • Creates HR record
  • Creates Microsoft account
  • Assigns licenses
  • Sends welcome email
  • Notifies manager

Flows are ideal for orchestrating multiple systems.

REST API Tools

Best for:

  • Custom applications
  • Systems without connectors

Advantages:

  • Flexible
  • Supports nearly any web service
  • Supports standard HTTP operations

Requires:

  • API endpoint
  • Authentication
  • Request definitions

Custom Connectors

Best when:

  • REST APIs are reused frequently

Advantages:

  • Encapsulates API logic
  • Easier maintenance
  • Reusable across Power Platform

Model Context Protocol (MCP)

MCP provides a standardized way for AI agents to interact with external tools and services.

Benefits include:

  • Standardized communication
  • Tool discovery
  • Rich AI interactions
  • Cross-platform interoperability

MCP reduces the need for custom integrations between agents and enterprise systems.

Azure AI Search

Azure AI Search is commonly used for:

  • Enterprise knowledge retrieval
  • Retrieval-Augmented Generation (RAG)
  • Grounding AI responses

Instead of simply searching documents, the agent retrieves relevant content before generating a response.

Selecting the Correct Integration Method

When planning an integration, ask:

Is a built-in connector available?

If yes:

Use the connector.

If no:

Consider:

  • REST API
  • Custom connector
  • MCP

Is business logic required?

If yes:

Power Automate is often the best choice.

Does the agent need enterprise knowledge?

Use:

  • SharePoint
  • Azure AI Search
  • Knowledge connectors

Does the system expose APIs?

REST APIs are often the preferred integration.

Will multiple agents share tools?

Consider:

  • MCP
  • Shared connectors
  • Reusable APIs

Authentication Planning

Authentication determines how the agent proves its identity.

Common approaches include:

  • Microsoft Entra ID
  • OAuth
  • API keys
  • Service principals
  • Managed identities

The exam focuses on choosing appropriate authentication methods rather than configuration details.

Authorization Planning

Authentication answers:

Who are you?

Authorization answers:

What are you allowed to do?

Examples:

  • HR agent can view employee records.
  • Sales agent cannot modify payroll.
  • Managers approve leave.
  • Employees submit requests.

Least privilege is a core security principle.

Data Governance Considerations

Enterprise integration must align with organizational governance.

Consider:

  • Data residency
  • Compliance
  • Data classification
  • Data loss prevention (DLP)
  • Audit logging
  • Connector governance
  • Environment strategy

Sensitive data should only be accessible through approved integrations.

Error Handling Strategy

Enterprise systems occasionally fail.

Examples:

  • API unavailable
  • Authentication expired
  • Timeout
  • Network issues
  • Invalid data

A good integration strategy includes:

  • Retry logic
  • User-friendly error messages
  • Logging
  • Monitoring
  • Graceful failure

Performance Planning

Enterprise integrations introduce latency.

Good planning includes:

  • Minimize API calls
  • Cache data where appropriate
  • Avoid unnecessary requests
  • Use asynchronous workflows
  • Optimize search indexes

Fast responses improve user experience.

Scalability Considerations

Consider future growth.

Questions include:

  • How many users?
  • How many API calls?
  • Peak workloads?
  • Multiple regions?
  • Future integrations?

A scalable architecture minimizes redesign later.

Multi-Agent Integration

Large organizations increasingly use multiple specialized agents.

Examples:

  • HR Agent
  • IT Agent
  • Finance Agent
  • Sales Agent

Instead of one agent doing everything, specialized child or connected agents collaborate.

Benefits include:

  • Better maintainability
  • Separation of responsibilities
  • Easier governance
  • Improved scalability

Enterprise Knowledge Integration

Many agents primarily answer questions using organizational knowledge.

Knowledge sources include:

  • SharePoint
  • Dataverse
  • Websites
  • Azure AI Search
  • Files
  • Microsoft Graph

Good grounding reduces hallucinations and improves response accuracy.

Monitoring Enterprise Integrations

Planning includes monitoring:

  • Failed API calls
  • Authentication failures
  • Response times
  • Flow failures
  • Connector usage
  • User activity

Monitoring helps maintain reliability and identify opportunities for optimization.

Common Planning Mistakes

Avoid these common mistakes:

  • Choosing REST APIs when a connector already exists
  • Giving excessive permissions
  • Ignoring governance policies
  • Forgetting authentication requirements
  • Integrating directly with databases unnecessarily
  • Not planning for failures
  • Creating one oversized agent instead of multiple specialized agents
  • Ignoring future scalability

Exam Tips

Remember these principles:

  • Prefer built-in connectors before custom integrations.
  • Use Power Automate for business workflows and orchestration.
  • Use REST APIs when no connector exists.
  • Use custom connectors for reusable APIs.
  • Use MCP for standardized tool integration and cross-platform scenarios.
  • Use Azure AI Search for grounding enterprise knowledge.
  • Follow least privilege security.
  • Plan for governance, monitoring, and scalability from the beginning.
  • Separate authentication from authorization.
  • Choose the simplest integration that satisfies business requirements.

10 Practice Exam Questions

Question 1

A company wants an AI agent to create approval requests, notify managers, and update multiple business systems in sequence. Which integration option is most appropriate?

A. Azure AI Search

B. Power Automate

C. Direct SQL queries

D. Adaptive Cards

Correct Answer: B

Explanation: Power Automate is designed to orchestrate multi-step workflows across multiple systems, making it the ideal solution for approval processes and sequential business actions.

Question 2

An organization already has a Microsoft-supported connector for its CRM system. During solution planning, what should be recommended?

A. Build a custom REST API

B. Use Model Context Protocol (MCP)

C. Use the built-in connector

D. Build a custom connector

Correct Answer: C

Explanation: Built-in connectors are the preferred option because they are supported, easier to configure, and require less maintenance than custom integrations.

Question 3

An agent needs to retrieve information from a proprietary internal application that exposes REST endpoints but has no existing Power Platform connector. What is the best integration approach?

A. Azure AI Search

B. Adaptive Cards

C. REST API tool

D. Dataverse

Correct Answer: C

Explanation: REST API tools are appropriate when integrating with applications that expose web APIs but do not have existing connectors.

Question 4

Which principle should guide permission assignment when integrating an AI agent with enterprise systems?

A. Grant full administrative access

B. Allow anonymous access whenever possible

C. Share one account across all users

D. Apply the principle of least privilege

Correct Answer: D

Explanation: Least privilege ensures the agent has only the permissions necessary to perform its intended tasks, reducing security risks.

Question 5

An organization wants AI-generated answers to reference internal company documentation stored across multiple repositories while minimizing hallucinations. Which technology best supports this requirement?

A. Azure AI Search

B. Power Automate

C. Microsoft Teams

D. Adaptive Cards

Correct Answer: A

Explanation: Azure AI Search enables retrieval-augmented generation (RAG), grounding responses in trusted enterprise content.

Question 6

What is the primary purpose of authentication in an enterprise integration strategy?

A. Determine what data users can modify

B. Verify the identity of the caller

C. Optimize API performance

D. Format responses consistently

Correct Answer: B

Explanation: Authentication verifies identity, while authorization determines what actions or resources the authenticated identity may access.

Question 7

A solution architect expects multiple AI agents across different platforms to share common enterprise tools using a standardized communication protocol. Which technology best fits this requirement?

A. Power BI

B. Power Automate

C. Model Context Protocol (MCP)

D. SharePoint lists

Correct Answer: C

Explanation: MCP provides a standardized way for AI agents to discover and use tools across platforms, promoting interoperability and reuse.

Question 8

During planning, which consideration most directly supports long-term maintainability of enterprise integrations?

A. Selecting the integration method that requires the most custom code

B. Ignoring governance because it can be added later

C. Allowing every connector in every environment

D. Choosing reusable connectors and standardized integration patterns

Correct Answer: D

Explanation: Reusable connectors and standardized integration approaches simplify maintenance, governance, and future enhancements.

Question 9

An AI agent primarily needs to retrieve customer order information without modifying records. Which type of enterprise integration is being planned?

A. Read-only integration

B. Action-oriented integration

C. Workflow orchestration

D. Hybrid integration

Correct Answer: A

Explanation: Read-only integrations focus on retrieving information without performing updates or transactions.

Question 10

When planning enterprise integrations, why should architects include monitoring and logging?

A. To replace authentication

B. To eliminate API latency

C. To detect failures, troubleshoot issues, and improve reliability

D. To reduce the number of enterprise systems

Correct Answer: C

Explanation: Monitoring and logging help identify authentication problems, failed API calls, performance issues, and other operational concerns, enabling proactive maintenance and continuous improvement.

Go to the AB-620 Exam Prep Hub main page

Leave a comment