Marcus is building a customer service agent for Meridian Retail using Copilot Studio. The IT team has already set up a certified Power Platform connector to the company's inventory management system. Marcus wants the agent to be able to look up stock levels in real time when a customer asks. How should Marcus make the existing Power Platform connector available as an action in the agent?
Select an answer to reveal the explanation.
Short Explanation and Infographic
An existing Power Platform connector is like a toolbox already sitting in your workshop — you don't build it again, you just pick up the tool. Marcus goes to the agent's Actions area, chooses Power Platform connector, finds the inventory connector, and maps the operation he needs. Answer: C.
Full explanation below image
Full Explanation
Copilot Studio is designed to consume existing Power Platform connectors directly. When the connector is already certified and available in the environment, the developer does not need to recreate or export it — they simply reference it when adding an action to the agent.
Option C is correct because the 'Power Platform connector' action type in Copilot Studio surfaces all connectors available in the current environment. Marcus selects the inventory connector, picks the specific operation (such as 'Get stock level by SKU'), maps any required input parameters (like product ID), and the connector handles authentication and the API call automatically at runtime.
Option A is incorrect because exporting a Swagger file and routing through Azure API Management is an unnecessary and overly complex path when the connector already exists in Power Platform. This approach might be used to build a new custom connector from an external API, not to reuse one that is already registered.
Option B is incorrect because recreating the connector from scratch defeats the purpose of having a prebuilt connector. Duplicating the definition introduces maintenance debt and potential configuration drift. The correct approach is to reference the existing connector.
Option D is incorrect because publishing a connector to the Microsoft commercial marketplace is a process for independent software vendors (ISVs) who want to distribute connectors broadly. An internal enterprise connector does not need marketplace publication — it is already available within the organization's Power Platform environment.
Exam tip: Copilot Studio actions distinguish between three sourcing patterns: Copilot connectors (prebuilt gallery items), Power Platform connectors (existing environment connectors), and custom connectors (newly built). Match the action type to the connector's origin to avoid re-creation mistakes.