How Microsoft 365 Copilot invokes Azure-hosted logic

AB-100 By islever Editorial Last updated

Design extensibility of AI solutions Design AI and agents for business solutions

Short answer

B Include Microsoft Power Platform connectors so Microsoft 365 Copilot actions can invoke Azure-hosted APIs and external logic.

Question

A company has an AI business solution.
You need to extend the solution so that Microsoft 365 Copilot can invoke external logic hosted in Azure services.
What should you include in the solution?
  1. Microsoft Copilot Studio skills
  2. Microsoft Power Platform connectors Correct Answer
  3. custom engine agents

Key Takeaways

The question tests the distinction between an agent type and the connector/action layer that actually invokes external Azure logic, with Copilot Studio skills as the main terminology trap.

Microsoft 365 Copilot extensibility relies on Power Platform connectors to expose Azure-hosted APIs as callable actions; this page explains why option B is the correct inclusion.

Common mistake: Selecting Microsoft Copilot Studio skills because they sound like the Copilot extension mechanism; skills are self-contained reusable capabilities, whereas Azure-hosted logic must be exposed through a connector-backed action.

Expert Analysis

The request path Microsoft 365 Copilot does not call an Azure endpoint just because the endpoint exists. A Copilot action/plugin must describe the operation, and that action is backed by a Power Platform connector. At runtime, Copilot resolves the user intent to the action, the connector authenticates and sends the request to the Azure-hosted API or workflow, and the response returns to Copilot. The connector is the layer that makes the Azure logic invokable.

Why B fits Option B, Microsoft Power Platform connectors, is the integration layer named in that path. A custom connector can wrap an Azure Functions endpoint, Logic Apps workflow, or REST API; a prebuilt connector can be used where one exists. The connector supplies the operation metadata and authentication that Copilot needs, so the solution can invoke external logic without embedding Azure credentials or HTTP details in the Copilot prompt.

Why A is a trap Option A, Microsoft Copilot Studio skills, sounds plausible because Copilot Studio is an extensibility surface. Current Copilot Studio guidance describes skills as reusable, self-contained capabilities; tools/connectors are what connect to external services. Comments on this question reflect that confusion: some learners treat skills as another name for actions/plugins, while others point out that connectors are the plumbing. The safer exam reading is that a skill alone does not expose an Azure-hosted API to Microsoft 365 Copilot.

Why C is not the best answer Option C, custom engine agents, is an agent type for scenarios that need a custom orchestrator or proprietary model. It can be surfaced in Microsoft 365 Copilot and can call external services, but the question does not ask for custom orchestration; it asks for the mechanism that lets Copilot invoke Azure-hosted logic. Choosing C adds an agent architecture where a connector-backed action is the direct fit. If a later requirement mentions full control of orchestration or Azure AI Foundry models, custom engine agents become relevant.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

When an AB-100 question asks how Copilot reaches external logic, separate the agent type from the integration layer. Look for the option that exposes the Azure endpoint as a callable action or connector; do not pick a Copilot Studio feature just because it has "Copilot" in the name. If the scenario emphasizes custom orchestration or proprietary models, then consider custom engine agents; if it only asks for external invocation, choose the connector/action path.

Frequently Asked Questions

Why can't Microsoft Copilot Studio skills invoke Azure-hosted logic directly?

Skills are reusable self-contained capabilities in Copilot Studio. To reach Azure Functions, Logic Apps, or a REST API, the agent needs a tool or action backed by a Power Platform connector.

When should a custom engine agent be used instead of a connector?

Use a custom engine agent when you need custom orchestration, proprietary models, or full control of the agent runtime. A connector is enough when the goal is simply to expose an Azure API as a Copilot action.

Can Microsoft 365 Copilot call an Azure Function without a connector?

Not directly in the supported extensibility path described here. The Azure Function must be described as an operation in an action/plugin, typically through a custom Power Platform connector or an OpenAPI-based API plugin.

More AB-100 FAQ →

Community Votes

B
53%
A
40%
C
7%

53% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 18 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 18

  1. madimad 👍 5 Answered B
    To allow Microsoft 365 Copilot to invoke external logic hosted in Azure, you use skills created in Microsoft Copilot Studio. Copilot Studio skills allow: Calling external APIs Integrating Azure-hosted services Exposing business logic to Microsoft 365 Copilot Examples: Calling Azure Functions Accessing custom APIs Executing backend business workflows These skills act as extensions that Copilot can invoke when needed.
  2. rveney 👍 4 Answered B
    Power Platform connectors are the supported and required mechanism for exposing external services to Microsoft 365 Copilot. They can wrap: Azure Functions Logic Apps REST APIs Once exposed as a connector, Copilot can invoke the external logic securely and decoratively. These connectors are then consumable by: Microsoft 365 Copilot Copilot Studio skills Power Automate flows
  3. K_in_the_Cloud 👍 3 Answered A
    Skills (also called "actions" or "plugins") are the mechanism specifically designed to extend Microsoft 365 Copilot's capabilities by allowing it to call external APIs and Azure-hosted logic (Azure Functions, REST endpoints, Logic Apps). When you build a skill in Copilot Studio, it becomes directly discoverable and invocable by Microsoft 365 Copilot. This is the intended extensibility pattern for connecting M365 Copilot to external Azure services.
  4. Xabia 👍 3 Answered A
    Microsoft 365 Copilot cannot directly invoke connectors-> Connectors must be wrapped in a Copilot Studio skill to be callable by Copilot
  5. Newb007 👍 3 Answered A
    "hosted in Azure service" must be A. Unless I'm missing something?
Show 13 more comments
  1. Sathish_PP 👍 3 Answered B
    I think option B to connect External
  2. Ninashnash 👍 2 Answered B
    the ask is: Extend the solution so that Microsoft 365 Copilot can invoke external logic hosted in Azure services To Invoke external logics (integration with other systems) in Power Platform you need Connectors (either OOTB connectors, or Custom Connectors). Full stop!
  3. Newb007 👍 2
    Ya I'm Going with B. PP connectors ... Was thinking Bot Framwork skills which is being phased out
  4. Vinz572 👍 2 Answered B
    AI Can integrate flow and from that it can use Power Platform connectors.
  5. omath 👍 1 Answered A
    Correct answer: A. Microsoft Copilot Studio skills. 🎯 Takeaway To let Microsoft 365 Copilot invoke external logic hosted in Azure services, you must expose that logic as skills built in Microsoft Copilot Studio. Skills act as extensions that Copilot can call during grounding and orchestration, enabling it to trigger APIs, workflows, or Azure‑hosted logic. Why the other options don’t fit Power Platform connectors These extend Power Apps/Power Automate, not Microsoft 365 Copilot. Custom engine agents These are for Copilot Studio agent orchestration, not for extending Microsoft 365 Copilot itself.
  6. Srikantha 👍 1 Answered A
    Explanation: To extend Microsoft 365 Copilot so that it can invoke external logic hosted in Azure services, you must expose that logic using Microsoft Copilot Studio skills (frequently referred to as plugins or actions). Skills serve as the specific extensibility mechanism that Copilot uses during grounding and orchestration, enabling it to securely discover and trigger custom APIs, backend workflows, or external Azure-hosted logic directly from user prompts.
  7. HaCha 👍 1 Answered B
    The correct option is B. Microsoft Power Platform connectors. To let Microsoft 365 Copilot interact with external logic hosted on Azure services (such as Azure Functions or Azure Logic Apps), you must wrap the Azure-hosted logic using a Microsoft Power Platform custom connector. These connectors translate the Copilot requests into API calls the Azure services understand, creating a secure bridge for data and workflow actions.
  8. zamper 👍 1 Answered B
    Skills are reusable capabilities that extend what your agent can do. Unlike tools, which connect to external services, skills are self-contained sets of instructions and logic that you can create, share, and reuse across agents. https://learn.microsoft.com/en-us/microsoft-copilot-studio/agents-experience/skills-overview
  9. K_in_the_Cloud 👍 1
    Power Platform connectors are the plumbing used within Power Automate flows and Power Apps to connect to services. They don't directly extend Microsoft 365 Copilot to invoke external logic. They're a component you might use inside a skill or flow, but they're not the answer to "how do you extend M365 Copilot."
  10. a5f05ea 👍 1 Answered A
    Why: The question asks about extending Microsoft 365 Copilot so that it can invoke external logic hosted in Azure services. Microsoft’s extensibility model supports adding reusable instructions/workflows as skills/plugin capabilities inside Microsoft 365 Copilot experiences.
  11. krunal0000001 👍 1 Answered C
    Custom engine agents are designed for this scenario because they allow organizations to bring their own orchestration, AI services, and external logic, including Azure-hosted services, and surface those capabilities through Microsoft 365 Copilot.
  12. QueenShi 👍 1 Answered B
    https://community.dynamics.com/blogs/post/?postid=9cff6025-c80b-f011-bae2-000d3a990cc2 PP connectors enable connection to external services
  13. Newb007 👍 1
    So you agree on A then? says you selected B

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Customizing Microsoft Copilot Opportunity Summary Presentation

S-grade

Prerequisites for Prebuilt Copilot in Dynamics 365 Finance

S-grade

Dynamics 365 Copilot Studio Knowledge Sources for In-App Help

S-grade

Microsoft Copilot Studio Agent Language Model Selection

S-grade

← Back to AB-100 Study Guide