Q
A company has a customer support agent built in Microsoft Copilot Studio. The agent generates responses grounded in product documents, securely calls an external Order API over HTTPS to perform lookups and refunds, and invokes a custom generative AI model hosted as an API in Microsoft Foundry.
You need to recommend an extensibility approach to make the agent available directly from Microsoft 365 surfaces, such as Microsoft Teams and SharePoint Online, without building a custom UI or hosting model infrastructure in the tenant.
What should you recommend?
Question Info
Choose the Best Option
Click any option to instantly check if you're correct.
Explanation
Objective:
2.2 Design extensibility of AI solutions
What This Item Tests:
Design AI solutions by using custom models in Microsoft Foundry
Additional Reading:
Approach 1: Surface your data and services into Microsoft's Copilots
Pattern A: Create plugins to enhance an existing Copilot's functionality
Rationale:
Microsoft 365 Copilot plugins enable Copilot to invoke external APIs and custom model endpoints, while reusing Microsoft 365 surfaces, such as Teams and SharePoint, as the UI. This approach avoids building a custom UI or hosting model infrastructure. The other options require custom experiences, misuse indexing for transactional actions, and bypass Copilot extensibility patterns.
Share This Question
Challenge a friend or share with your study group.