TL;DR: Building a Copilot agent in Microsoft 365 takes minutes. After a few months of rollout, most tenants hold dozens of agents: duplicates, orphans, and sleeping agents whose permissions are still wide open. Agent Control Pro is an AI agent that reads your Microsoft Agent 365 data and turns it into ranked governance decisions in plain English, directly inside Copilot. This guide explains what it does, how to use it step by step, and what every IT admin needs to know before they start.
The governance gap nobody planned for
Creating Copilot agents is easy. Too easy, sometimes. One team builds an HR FAQ agent. Another team builds the same thing. A third adapts it for their own department. Nobody coordinates. Six months later, your tenant holds 40+ agents and nobody has a clear picture of what's actually running.
The admin center lists all of them. It does not tell you which ones matter, which have active permissions on data nobody uses, or which five are doing the same job.
That data does exist, though. Microsoft Agent 365 is the unified registry that tracks every agent in your tenant: identity, lifecycle, usage signals, permissions. It is the control plane Microsoft built for exactly this problem. The challenge is that raw data is not a decision.
Agent Control Pro reads that data and turns it into clear, ranked recommendations, directly in your Copilot.
What is Agent Control Pro?
Agent Control Pro is a Microsoft 365 Copilot agent that connects to Microsoft Agent 365 and transforms raw usage signals into ranked, actionable governance recommendations. You interact with it in plain English. You ask a question, it answers with evidence.
Think of it as a governance analyst who has already read every signal in your tenant and is ready to answer the moment you open Copilot.
What it is not
Agent Control Pro is read-only. It cannot delete agents, revoke permissions, or reassign ownership on your behalf. Every action it recommends requires a deliberate human decision. Governance decisions should never be automated away from the people responsible for them.
Requires Microsoft Agent 365: the unified agent registry for your M365 tenant. Available at approximately $15/admin/month or included in M365 E7.
The four governance questions it answers
Every IT team managing a Copilot-enabled Microsoft 365 tenant eventually arrives at the same four questions. Ask them to Agent Control Pro in plain English, directly inside Copilot.
1. How many agents do we have, and who built them?
Getting an accurate inventory sounds trivial. In practice it requires cross-referencing Agent 365 data across build types, ownership records, and deployment scopes. Agent Control Pro delivers a structured count with build-type breakdown without manual enumeration or PowerShell scripting.
What you get:
2. Which agents should be promoted to the whole organization?
Some agents start as shared-link experiments and become genuinely business-critical. Agent Control Pro surfaces promotion candidates ranked by usage evidence, so you promote with confidence rather than guesswork.
What you get:
3. Which agents are dormant but still have active permissions?
An agent nobody uses is harmless, unless its permissions are still active. Dormant agents with open OAuth connections, SharePoint access, or Teams messaging permissions represent a real security surface area.
What you get:
4. Which agents are duplicates, and how should we consolidate them?
Duplicate agents emerge when teams build independently, when agents are copied without coordination, or when the same use case gets solved multiple times. Agent Control Pro identifies overlapping agents and recommends which to keep, which to retire, and which capabilities to merge.
What you get:
The six classification labels
Every agent in your tenant gets a label based on its usage signals, permissions, and deployment scope. These six categories turn raw registry data into a prioritized action list.
In regular use, healthy ownership, appropriate scope. No action needed.
High usage relative to limited deployment. Recommended for org-wide promotion.
No recent activity, but permissions remain active. Flagged for retirement review.
Overlapping scope with another active agent. Consolidation recommended.
Duplicate with no active owner. Priority cleanup candidate.
Same agent deployed across multiple scopes without coordination. Merge recommended.
How to use Agent Control Pro: step by step
Step 1: Export your usage data
Agent Control Pro ingests data from the Microsoft 365 Copilot usage report, exported as a CSV from the admin center.
Go to the Microsoft 365 admin center → Reports → Usage
Select Microsoft 365 Copilot → Agent usage
Export as CSV
The CSV includes agent names, usage counts, active user counts, last-activity timestamps, and deployment scopes. Everything Agent Control Pro needs.
Step 2: Upload the CSV to Agent Control Pro
Open Agent Control Pro inside Microsoft 365 Copilot and upload the CSV file. The agent parses the data and maps each agent to its Agent 365 record, enriching it with ownership, permissions, and deployment metadata. Takes a few seconds.
Step 3: Ask your governance questions
Now you ask. In plain English. No query language, no filters, no dashboards. The agent responds with ranked lists, evidence for each recommendation, and suggested next steps.
Step 4: Act on the recommendations
Agent Control Pro recommends. You decide. Each recommendation includes the evidence behind it, so you can validate before acting.
Promotion candidates: deploy org-wide from the Microsoft 365 admin center and assign a formal owner.
Dormant agents: review the permissions list, revoke OAuth connections and SharePoint access, then archive.
Duplicates: coordinate with team leads to migrate users to the primary agent, then disable the duplicate.
Security and trust model
Agent Control Pro is built for enterprise environments where data residency, permission scoping, and tenant isolation are non-negotiable.
The agent reads Agent 365 data only. It cannot write, modify, delete, or reassign anything in your Microsoft 365 environment.
Uses on-behalf-of authentication. Acts as the signed-in admin with only the permissions that admin already has. No service principals.
Data is isolated at the storage layer. No tenant's agent data is ever accessible from another tenant's context.
The CSV you upload is processed for the session only. Agent Control Pro does not retain agent usage data between sessions.
Who is Agent Control Pro for?
Agent Control Pro is designed for Microsoft 365 IT administrators and governance teams in organizations that have passed the initial Copilot adoption phase, typically tenants with 1,000+ seats and active Copilot usage.
It is most relevant when:
Your tenant has more than 20 to 30 Copilot agents in deployment
Security or compliance teams are asking questions about agent permissions
You are planning a structured Copilot governance review
You are preparing a Copilot Center of Excellence rollout and need a baseline inventory
You have had agent-related incidents: orphaned agents, permission creep, duplicate confusion
If you are early in your Copilot journey with fewer than 10 agents, a manual review is probably sufficient. Agent Control Pro becomes genuinely valuable at scale, when the volume of agents makes manual governance impractical.
Frequently asked questions
Does Agent Control Pro work without Microsoft Agent 365?
No. Microsoft Agent 365 is the data source that provides agent identity, lifecycle, and usage signals. It is required for Agent Control Pro to function.
Can Agent Control Pro delete or disable agents?
No. Agent Control Pro is read-only. All actions (retirement, promotion, consolidation) are performed by your IT team using standard Microsoft 365 admin tools.
How often should I run a governance review?
For most tenants, a monthly review is sufficient during active Copilot rollout. Quarterly reviews work well for mature, stable environments. Agent Control Pro does not require a scheduled cadence; you can query it whenever a governance question arises.
What if an agent is missing from the inventory?
Agents appear in Agent 365 once they have been deployed and have recorded at least one interaction. Agents created but never used may not appear in the usage report CSV. You can ask Agent Control Pro about gaps in the registry and it will flag agents that appear in deployment records but have no usage history.
Is the data shared with Witivio or any third party?
No. Your usage data stays within your Microsoft 365 tenant. Witivio does not have access to the CSV you upload or the results of your governance queries.
Ready to take stock of your tenant?
Agent Control Pro turns your Microsoft Agent 365 data into ranked governance decisions. No scripting, no dashboards, no manual enumeration. Just ask.
Get Agent Control Pro → Book a demo