This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Answer the following questions to check your understanding of the concepts covered in this module.
A newly built agent immediately gains the ability to query a live financial database, because a tool that does exactly that is already listed as Available in the tenant's Agent Tools registry, and nobody had reviewed it. What does this scenario demonstrate?
The agent bypassed Copilot's permission model by exploiting a configuration bug
A tool being present in the Registry and a tool being safe to use are two different things until it's actually reviewed
Blocking the agent in the Registry would have been the correct fix before this happened
An administrator blocks a specific financial-database tool that several agents were using. What happens to the agents that were using it?
Only the agent that most recently used the tool loses access to it
The agents are automatically removed from the Registry along with the tool
The agents remain in the Registry, but none of them—or any other agent tenant-wide—can invoke that tool anymore
A developer at Relecloud wants to register an internally built MCP server so agents can invoke its tools. Which sequence correctly reflects the Bring Your Own MCP server flow?
The security team approves the server first, then the developer registers it, then an IT admin monitors ongoing activity
The developer registers the server directly in Copilot Studio, and it becomes immediately usable by any agent without admin review
The developer registers the server via the Agent 365 CLI, an IT admin reviews and approves it in the Microsoft 365 admin center, then supported clients can use it while security monitors activity
An administrator wants to reassign the owner of an agent that's built on Microsoft Foundry and currently has an active owner who left the team. What's the correct outcome?
Reassigning ownership of a shared agent isn't supported for this agent type—it's only supported for Agent Builder and Copilot Studio agents
The reassignment requires the Azure AI Owner role instead of AI Administrator
The reassignment proceeds normally, since Assign new owner works for any active agent in the Registry regardless of platform
Relecloud's security team wants to confirm exactly which non-Microsoft agents are currently usable in Microsoft Teams. What's the most efficient way to answer this in the Agent Registry?
Scroll the full Registry list and manually check each agent's publisher and channel
Filter by Status only, since Available agents are always usable in Teams
Combine the Publisher type filter with the Channel filter, scoped to Teams
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?