SunPath Insurance has built a custom AI agent using Microsoft Copilot Studio that helps claims adjusters look up policy coverage. A developer has submitted this agent for organizational deployment. Before users can access it from Microsoft Teams and Microsoft 365 Copilot Chat, what step must the Microsoft 365 administrator complete?
Select an answer to reveal the explanation.
Short Explanation
You need to review and approve the agent submission in the Microsoft 365 admin center's agent registry. Until you publish it there, the agent stays out of Microsoft Teams and Microsoft 365 Copilot Chat. That admin approval is the governance gate the exam expects.
Full Explanation
The Microsoft 365 agent registry, accessible via the Microsoft 365 admin center under Agents, serves as the centralized governance point for AI agents in the organization. When a developer submits a custom agent built in Copilot Studio or another platform, it enters a pending review state. An administrator, typically with the AI Services Administrator or Global Administrator role, must review the agent's metadata, capabilities, and data access requirements, then publish it to make it available to users. This publish action makes the agent discoverable and usable within Microsoft 365 Copilot experiences.
The option that says to upload the agent's manifest file to SharePoint and share the link with all claims adjusters is incorrect because SharePoint is a file storage platform, not an agent distribution mechanism. There is no mechanism for users to 'install' an agent from a SharePoint link. Agent distribution requires going through the official agent registry workflow.
The option that says to assign a Microsoft 365 Copilot license to the agent's service account in Microsoft Entra ID is incorrect because AI agents do not consume Microsoft 365 Copilot user licenses directly. Agents are service-level capabilities; it is the users who interact with Copilot, and by extension agents, who need Copilot licenses, not the agents themselves.
The option that says to configure the agent in the Microsoft Teams admin center as a custom app policy deployment is incorrect because while the Teams admin center handles Teams app deployment policies for regular apps and bots, the governance of Copilot-native agents goes through the Microsoft 365 admin center agent registry, not the Teams admin center. These are related but distinct deployment pathways.
Exam tip: Remember the agent publication workflow: Copilot Studio build, submit for review, admin reviews in the Microsoft 365 admin center agent registry, then publish or reject. The exam may test that publishing happens in the Microsoft 365 admin center, not the Teams admin center.