Summary
Governing what agents can invoke, and curating the agent estate as it grows, keeps Relecloud's agents accountable long after they're first onboarded.
What you learned
- Reviewing and approving a tool request requires the AI Administrator or Global Administrator role, and blocking a tool is a tenant-wide action distinct from blocking an individual agent.
- A Bring Your Own MCP server follows a structured developer-to-admin-to-security flow, and is currently a preview feature with specific supported client surfaces.
- Ongoing Agent Registry curation includes uploading a custom agent from a ZIP package, reassigning an already-active agent's owner (supported only for Agent Builder and Copilot Studio agents), deleting an agent no longer needed, and starting or stopping a Microsoft Foundry agent using the Azure AI Owner role.
- Filtering the agent estate by publisher type and channel answers specific governance-review questions faster than scrolling the full Registry, and the filtered list can be exported to Excel for compliance reporting.