You need to design a Microsoft Copilot Studio agent for customer support.

The requirement is to build a Microsoft Copilot Studio agent that can securely retrieve product warranty data from a REST API while minimizing development effort.

The best choice is D. Create a custom connector in Copilot Studio and use the connector to call the API.

Why this is correct:

A custom connector is the standard low-code way to integrate Copilot Studio with a REST API. It lets the agent call the external warranty service securely, using supported authentication methods, without requiring heavy custom development. This directly satisfies both key requirements:

secure retrieval of warranty data

minimal development effort

Why the other options are incorrect:

A. Use a Microsoft Power Automate desktop flow to screen scrape the warranty data.Screen scraping is brittle, less secure, and unnecessary when a REST API already exists.

B. Export the agent as a managed solution and customize the agent in Power Apps.This does not directly solve secure API access and adds unnecessary complexity.

C. Add the warranty data to the Fallback topic.The Fallback topic is for unclear user input, not for live secure retrieval of external data.