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?
Select an option, then click Submit answer.
Reference / correct answer:
Microsoft Power Platform connectors
Most accepted answer: B. Microsoft Power Platform connectors
Community votes: A=4, B=6
Selected Answer: 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. upvoted 1 times
Selected Answer: 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. upvoted 1 times
Selected Answer: B I think option B to connect External upvoted 2 times
Selected Answer: A Microsoft 365 Copilot cannot directly invoke connectors-> Connectors must be wrapped in a Copilot Studio skill to be callable by Copilot upvoted 3 times
Selected Answer: 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. upvoted 3 times K_in_the_Cloud 4 months, 1 week ago 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." upvoted 1 times ...