Microsoft Copilot
Take control of Copilot Studio agents
Anyone can build an agent in Copilot Studio. Rencore inventories every one with its owner, status and environment, flags the agents that are ownerless, stale or open to everyone, and sends the cleanup to the owner for approval.
Copilot Studio agents multiply faster than anyone governs them
The questions are the ones you already ask of a Team or a SharePoint site: who created it, who can use it, what data it draws on, and who cleans it up.
Who owns it
Agents are built faster than they are governed, so unapproved, orphaned and stale agents turn up in an audit instead of before deployment.
What it knows
An agent answers from its knowledge sources. A public website or outdated documents as a source bring uncontrolled outside content and old answers into a business process.
Who can use it
Copilot Studio has its own access policy, and an agent can be left open to everyone in the tenant without anyone deciding that.
Whether anyone still needs it
An agent built for one project stays published after the project ends, with nobody assigned to retire it.
What Rencore sees and does in Copilot Studio
Every Copilot Studio agent, with an owner
Rencore inventories the Copilot Studio agents in your tenant, so the list a governance lead needs exists before an auditor asks for it. An agent without a named owner is flagged for review.
- Agents with their owner, status and environment
- The number of agents per environment
- The knowledge sources each agent draws on
- Agents with no named owner
- Agents open to everyone in the tenant
Policies for the agents nobody should be running
Policies run over the agent inventory as they run over Microsoft 365, ranked by severity, so you start with the agents that carry the most risk. The policies on this page belong to the AI & Agents module.
- Agents that use a public website as a knowledge source
- Agents whose knowledge was last modified long ago
- Agents with no activity in 90 days
- Agents unpublished for 30 days
- Agents with no owner
Cleanup the owner approves
A policy finding goes to the person who built the agent, in Microsoft Teams, not into an IT queue. The action waits for the owner's approval, so nothing is removed before the owner has had a say.
- Quarantine an agent, and lift the quarantine
- Reassign an agent to a new owner
- Delete an agent
- Approval goes to the agent owner
- Owners answer in Microsoft Teams
Where this coverage stops
What Rencore reads in Copilot Studio, and what stays out of scope.
Copilot Studio agents only
Agent Builder agents, declarative agents and Agent 365 are not part of this connector.
No creating or publishing
Rencore does not create agents and has no publish or unpublish action. Governance starts at detection.
No spend cap
Rencore has no consumption cap or throttle for Copilot Studio. A hard cap lives in Microsoft billing.
No runtime inspection
Rencore does not sit in the path of prompts and does not block them as they are sent.
AI & Agents
Claude Enterprise
Inventory Claude Enterprise users, projects and token spend, joined to Microsoft 365 identity. Metadata only.
View the Claude Enterprise connectorPreviewChatGPT Enterprise
Inventory ChatGPT Enterprise custom GPTs, projects and connectors, with sharing joined to Microsoft 365 identity.
View the ChatGPT Enterprise connectorSharePoint Agents
Inventory SharePoint agents next to the sites and knowledge they use, and govern those sites with the same policies and owners.
View the SharePoint Agents connectorCopilot Studio questions, answered
Which agents does Rencore cover?
Copilot Studio agents. Agent Builder agents, declarative agents and Agent 365 are not part of this connector. SharePoint agents are covered by their own connector.
What does Rencore need to read the agents?
Dataverse consent in your tenant is a prerequisite for the agent data. The policies on this page are part of the AI & Agents module.
Can Rencore stop an agent?
It can quarantine an agent, lift the quarantine, reassign it to a new owner or delete it, with the approval going to the agent owner. It has no action to publish or unpublish an agent. Rencore acts after a policy finding, not in the path of a conversation.
Can Rencore cap what Copilot Studio costs?
No. Rencore has no consumption cap or throttle for Copilot Studio. A hard cap lives in Microsoft billing.
Does Microsoft already cover Copilot Studio governance?
Only in part, and Rencore complements it. The Power Platform admin center holds a tenant-wide inventory of apps, flows and agents with Delete and Block actions, and the Microsoft 365 admin center lists agents with a count of agents without owners. Microsoft Purview and Entra bring data protection and identity to agents. Monitor and the full set of actions in the Power Platform admin center need Managed Environments, which carry a premium license for every active user.
What those tools do not do is the operational layer: a policy for each agent that reads a public website or has gone stale, the owner deciding in Microsoft Teams whether to keep or retire it, and the same ownership and lifecycle rules across the Teams, sites, apps and flows around the agent. That is what Rencore adds, with the Microsoft tools keeping their roles.
How is Copilot Studio coverage licensed?
It is included in the AI & Agents module, the optional paid module on the Premium and Enterprise plans, alongside the Microsoft Copilot and agent coverage. There is no separate add-on for Copilot Studio. The pricing page has the full plan comparison.