# Agent Control Pro Q&A

Quick answers to the questions administrators ask most about Agent Control Pro. If you are just setting it up, start with the Agent Control Pro Get Started guide.

# Licensing and subscription

# What licenses does Agent Control Pro require?

Two, both per user:

A Microsoft Agent 365 license for every user who calls Agent Control Pro
An active Microsoft 365 Copilot license

The Agent Control Pro subscription itself is bought once per tenant on Microsoft AppSource and covers your whole tenant regardless of how many agents you govern. The per-user licenses are separate and come from Microsoft.

Microsoft applies the Agent 365 requirement at the API level too: access to the Copilot Package Management API that Agent Control Pro reads requires an Agent 365 license. Without it, no catalog answer can be produced for that user.

# Is there a free trial?

Yes. During an AppSource free trial you can ask the same questions, with two differences: every catalog answer is capped at five agents, and each response carries a banner showing that the trial is active and when it ends. Subscribing lifts the cap.

# Where do I buy or manage my subscription?

On Microsoft AppSource (the Microsoft Commercial Marketplace). After activation, your tenant's Agent Control Pro portal has a Subscription status page showing your current plan, state, trial countdown, and subscription details.

Both the Agent Control Pro assistant and the admin portal are gated on an active subscription, paid or trial. Until you activate on AppSource, requests to either surface are rejected.

# Data and privacy

# What data does Agent Control Pro analyze?

Three sources:

Your Copilot agent catalog, read live from Microsoft Graph (/copilot/admin/catalog/packages)
The Copilot usage report CSV you upload from the Microsoft 365 admin center
The Power Platform consumption report CSV you upload for cost analytics

Catalog data is read on demand and never persisted. Usage and billing rows are stored tenant-isolated until your next upload replaces them.

# Does Agent Control Pro read the content of my Copilot conversations?

No. Agent Control Pro never reads conversation transcripts, prompts, or responses. It reads agent definitions (name, description, instructions, deployment metadata) and counts (active users, response volumes) from the usage report.

# Where is my data stored?

Tenant-isolated in a PostgreSQL database operated by Witivio. The data persisted is limited to the usage report rows and billing report rows you uploaded, the identity of the administrator who uploaded them, marketplace subscription metadata, and your tenant identifier. Catalog data and user or group lookups are read live and never written to durable storage.

No customer data is used to train any AI or machine-learning model. See Architecture and security for the full data-management table.

# Why do I need to upload a CSV instead of it pulling live?

Microsoft Graph does not yet expose the Copilot usage report as a live API surface, and the same is true of Power Platform consumption data. Until it does, the manual upload is the most reliable path. Live ingestion is on the roadmap; today, re-uploading the latest CSV monthly is the recommended cadence.

Agent Control Pro emails the subscription purchaser twice a month (the first and third Monday, 8:00 AM UTC) to say how old your current upload is, so you can let the reminder drive your cadence.

# Detection and analysis

# How are duplicates detected?

Agent Control Pro compares agent names, descriptions, and instructions across the tenant catalog using deterministic matching. The default thresholds are conservative, so you see fewer false positives at the cost of some near-duplicates being missed. Multilingual and embedding-based matching is on the roadmap.

# What is the difference between a "shared" and an "LOB" agent?

Shared agents are user-published with a link, and discoverability depends on the sharing settings the publisher chose. LOB (line of business) agents are admin-deployed, available tenant-wide, and discoverable in the Agent Store. Promoting a popular shared agent to LOB is the primary org-wide candidate workflow.

# What does cost analytics show?

Consumption from your uploaded Power Platform report, in the report's native credits with no currency conversion. You can ask for the cost of a single agent, all agents ranked by credits, or a tenant-wide rollup broken down by environment, product, and feature.

# Access and administration

# Can Agent Control Pro modify or delete agents in my tenant?

No. Agent Control Pro is read-only by design. Every output is a recommendation; you decide and act in the Microsoft 365 admin center. There is no API path for Agent Control Pro to modify, delete, or share an agent.

# Who in my tenant can use Agent Control Pro?

Any authenticated administrator in a tenant that has consented to the Agent Control Pro Entra application, and who holds the required licenses. There is no per-user role configuration; every authorized administrator sees the same governance view of the same tenant. Authentication uses Microsoft Entra ID with on-behalf-of delegated permissions.

# Is there a per-user dashboard, or only the admin chat?

The conversational agent inside Microsoft 365 Copilot is the primary surface; that is where governance questions are asked and answered. A thin admin portal sits alongside it for three specific tasks: uploading the Copilot usage CSV, uploading the billing CSV, and viewing your subscription status. There is no per-user dashboard or report. Agent Control Pro is a tenant-level governance tool for administrators.

# Can I use it outside Copilot Chat?

Yes. Agent Control Pro is also registered as a host-agnostic agent connector, so the same tools work in Microsoft 365 Copilot Cowork and the Teams Channel Agent. See the fundamentals overview for what each surface offers.

← Fundamentals Limits →