01Use the Agent Registry as your inventoryVerified

Agents > All agents > Registry in the Microsoft 365 admin center lists Microsoft, partner, org-published and creator-shared agents.

Steps
  1. Open Agents > All agents > Registry in the Microsoft 365 admin center
  2. Filter by Publisher Type and Platform to find in-house agents
  3. Check the Agents without owners and Unmanaged agents counts
  4. Export to CSV for periodic inventory reviews
Caution

Total agents doesn't change with filters. Only Copilot Studio drafts are currently visible. The Microsoft Graph API for the registry is in preview.

Availability
Generally available (some metrics and risk views depend on Agent 365 or other licenses). Graph API in preview. Checked 2026-09-12.
Source
Microsoft Learn, "Agent Registry in Microsoft 365 admin center"
Microsoft Learn, "Agent overview in Microsoft 365 admin center"
Verified
2026-09-12 (v1)
Supporting passage from the source
The agent registry in Microsoft 365 admin center provides a centralized view of all agents available for your organization. This list helps you monitor, manage, and govern agents for your organization.

02Route org-wide publishing through request and approvalVerified

Agents for the whole organization reach the Agent Store only after admin approval; admins choose Publish to store or Reject submission.

Steps
  1. Open the Pending Requests card in Agent overview, or All agents > Requests
  2. Review the creator, knowledge sources and requested permissions
  3. After internal review (security and business owner), select Publish to store
  4. If requirements aren't met, select Reject submission and tell the creator why
Caution

Only AI Administrator or Global Administrator can approve requests or assign owners; other roles can only monitor.

Availability
Generally available. Checked 2026-09-12.
Source
Microsoft Learn, "Manage agents in the Microsoft 365 admin center"
Microsoft Learn, "Governance and Lifecycle actions for agents available in Microsoft 365 admin center"
Microsoft Learn, "Agent overview in Microsoft 365 admin center"
Verified
2026-09-12 (v1)
Supporting passage from the source
However, before users can access these agents, each agent must undergo a streamlined process of submission and approval.

03Blocking reach depends on how the agent was builtVerified

Blocking Agent Builder and Copilot Studio agents affects Copilot and host products such as Outlook and Teams. Blocking SharePoint or Microsoft Foundry agents affects only Copilot Chat.

Steps
  1. Select the agent in Agents > All agents
  2. Choose Block, then Block agent, and save
  3. For SharePoint or Foundry agents, check whether you also need to stop them in those products
  4. Researcher and Analyst can't be scoped per user; block tenant-wide if needed
Caution

Admin-center actions fail for agents in environments with Power Platform IP firewall in active enforcement; use the Power Platform API instead.

Availability
Generally available. Checked 2026-09-12 (page updated 2026-08-31).
Source
Microsoft Learn, "Governance and Lifecycle actions for agents available in Microsoft 365 admin center"
Verified
2026-09-12 (v1)
Supporting passage from the source
However, blocking an agent that you created by using SharePoint or Microsoft Foundry only impacts its availability in Microsoft Copilot Chat.

04Assign a new owner to ownerless agentsVerified

Shared agents become ownerless when the creator's account is deleted. Admins can assign new owners to Agent Builder and Copilot Studio agents; Agent Builder supports multiple owners.

Steps
  1. Filter with the Agents without owners card in the Registry
  2. Select Assign new owner in the details pane
  3. Enter the new owner and select Assign
  4. For Agent Builder agents, add extra owners with Add owner
  5. If no successor is found, consider blocking or deleting
Caution

After reassignment the previous owner loses all access, including read, and the new owner gets the previous owner's uploaded files. Groups can't be Agent Builder owners.

Availability
Generally available. Checked 2026-09-12.
Source
Microsoft Learn, "Governance and Lifecycle actions for agents available in Microsoft 365 admin center"
Microsoft Learn, "Agent Registry in Microsoft 365 admin center"
Verified
2026-09-12 (v1)
Supporting passage from the source
Multiple owners reduce reliance on a single person and help teams continue to edit and maintain an agent when responsibilities change.

05Retire agents knowing deletion is irreversibleVerified

Agent Builder agents can be deleted from the admin center, along with associated files and the SharePoint Embedded container. Deletion is irreversible.

Steps
  1. Pick retirement candidates by usage and ownership
  2. Block first and watch for impact
  3. Save needed records (instructions, knowledge list), e.g., via Export
  4. Filter Platform = Agent Builder in Microsoft Copilot, then … > Delete
  5. Tell users it can take up to 24 hours to take effect
Caution

Deleted agents can't be restored. Follow your records policy for what to keep and for how long.

Availability
Generally available. Checked 2026-09-12.
Source
Microsoft Learn, "Governance and Lifecycle actions for agents available in Microsoft 365 admin center"
Verified
2026-09-12 (v1)
Supporting passage from the source
This deletion process is irreversible. Once you delete an agent, it might take up to 24 hours for the deletion to reach all users who had access to the agent.

06Pin the agents you want people to useVerified

Admins can pin up to three deployed agents for everyone or for specific users/groups. Users can't unpin admin-pinned agents.

Steps
  1. Open Manage pinned agents from the … menu on All agents
  2. Select a deployed agent with Pin agent
  3. Choose scope (all deployed users or specific users/groups) and save
  4. Order them with Move up / Move down
Caution

It can take up to six hours to show. Undeployed or blocked agents can't be pinned.

Availability
Generally available (requires AI Administrator). Checked 2026-09-12.
Source
Microsoft Learn, "Agent Registry in Microsoft 365 admin center"
Verified
2026-09-12 (v1)
Supporting passage from the source
Administrators can pin up to three agents in Microsoft 365 admin center for end-users using Microsoft Copilot in the organization.

07What's included for licensed users, and the exceptionsVerified

Employee-facing Copilot Studio agent usage is not charged in Copilot Credits when the user has a Microsoft 365 Copilot license and the agent runs under that user's identity, with exceptions.

Steps
  1. Check whether agent users hold Microsoft 365 Copilot licenses
  2. Check whether agent flows use triggers other than "When an agent calls the flow"
  3. Check whether Computer-Using Agents are used
  4. Estimate consumption for unlicensed users with Microsoft's agent usage estimator
Caution

Rates (table updated 2026-08-03): classic answer 1, generative answer 2, agent action 5, tenant graph grounding 10, agent flow actions 13 per 100 actions (Copilot Credits). Fair-use limits apply. Microsoft's pricing page lists packs of 25,000 Copilot Credits at $200.00/pack/month (checked 2026-09-12).

Availability
Generally available. Checked 2026-09-12.
Source
Microsoft Learn, "Billing rates and management - Microsoft Copilot Studio"
Microsoft, "Microsoft 365 Copilot Pricing – AI Agents | Copilot Studio"
Microsoft Learn, "Standard harness licensing - Microsoft Copilot Studio"
Verified
2026-09-12 (v1)
Supporting passage from the source
Employee-facing usage scenarios (Business to Employee) of Copilot Studio agents and Copilot Studio tools and features that these agents invoke are included in the Microsoft 365 Copilot USL when the user of the agent is licensed with Microsoft 365 Copilot

08When capacity overage stops agents, and per-agent capsVerified

At 125% of prepaid capacity, custom agents are disabled. Agent flows stop new runs once capacity is used up. You can set monthly caps per agent in the Power Platform admin center.

Steps
  1. Check consumption under Licensing > Copilot Studio in the Power Platform admin center
  2. Set monthly limits per agent in Manage Agents
  3. Allocate capacity to environments with critical agents
  4. Decide in advance how to respond (reallocate, buy more, pay-as-you-go)
Caution

After enforcement, users see messages such as "There is a billing issue." Unused Copilot Credits don't carry over. Environments on pay-as-you-go aren't subject to the overage stop.

Availability
Generally available. Checked 2026-09-12.
Source
Microsoft Learn, "Billing rates and management - Microsoft Copilot Studio"
Microsoft Learn, "Standard harness licensing - Microsoft Copilot Studio"
Verified
2026-09-12 (v1)
Supporting passage from the source
Enforcement is triggered when a tenant reaches 125% of their prepaid capacity.

09Set up pay-as-you-go for unlicensed Copilot Chat usersVerified

Unlicensed Copilot Chat users can use work-data agents once pay-as-you-go is set up: create a billing policy, then connect it to a Copilot service.

Steps
  1. Create a billing policy with an Azure subscription and target users in the Microsoft 365 admin center
  2. Add a budget limit and alert percentages
  3. Connect the policy to Microsoft Copilot Chat or SharePoint agents
  4. Review costs on the Cost Management page
Caution

Creating a policy alone doesn't finish setup; pay-as-you-go is off by default. Agent Builder is free for web-only agents. Cowork and Work IQ API billing is managed separately under Copilot > Cost management.

Availability
Generally available (Microsoft Copilot Retrieval API is in preview). Checked 2026-09-12.
Source
Microsoft Learn, "Microsoft Copilot Pay-as-You-Go Service Overview"
Microsoft Learn, "Choose between Agent Builder in Microsoft 365 Copilot and Copilot Studio to build your agent"
Microsoft Learn, "Usage-Based Billing and Cost Management for Copilot Credits"
Verified
2026-09-12 (v1)
Supporting passage from the source
As an admin, when you use the pay-as-you-go service, you set up billing and users access declarative agents on a usage basis. You can manage billing, view costs, set spending budgets, and turn off services as needed.

10Restrict features per environment with data policiesVerified

Power Platform data policies can block unauthenticated publishing, knowledge sources, HTTP requests, event triggers and channels per environment. Enforcement applies to all tenants since early 2025.

Steps
  1. Open Security > Data and privacy > Data policy in the Power Platform admin center
  2. Select the environments
  3. Block Chat without Microsoft Entra ID authentication in Copilot Studio to stop unauthenticated agents
  4. Block or endpoint-filter Knowledge source with public websites and data in Copilot Studio and HTTP as needed
  5. Confirm Copilot Studio shows the policy violation
Caution

Connectors in different data groups can't share data. Blocking the Microsoft Copilot Studio connector also blocks automated evaluations with authenticated accounts.

Availability
Generally available. Checked 2026-09-12 (page updated 2026-09-10).
Source
Microsoft Learn, "Configure data policies for agents - Microsoft Copilot Studio"
Verified
2026-09-12 (v1)
Supporting passage from the source
Data policies let you govern how agents connect and interact with data and services, both within and outside your organization. Administrators can configure Copilot Studio and Power Platform data policies in the Power Platform admin center.

11Track agent use in Purview audit logsVerified

Copilot and agent interactions are logged automatically in Audit (Standard), including AgentId, AgentName and AccessedResources.

Steps
  1. Confirm auditing is on
  2. Search CopilotInteraction under Audit in the Microsoft Purview portal
  3. Export and filter by AgentId or AppIdentity
  4. Check SensitivityLabelId in AccessedResources for labeled content
  5. Check AISystemPlugin.Id = BingWebSearch for web use
Caution

Apps built with Copilot Studio and Microsoft Foundry are included in Audit Standard. Auditing non-Microsoft AI apps is pay-as-you-go with 180-day retention.

Availability
Generally available. Checked 2026-09-12.
Source
Microsoft Learn, "Audit logs for Copilot and AI applications"
Verified
2026-09-12 (v1)
Supporting passage from the source
The system automatically logs these activities as part of Audit (Standard). If your organization enables auditing, you don't need to take extra steps to configure auditing support for Copilot and AI applications.

12Review quality regularly in Copilot Studio MonitorVerified

The Monitor page shows usage and outcomes for conversational and trigger-based (autonomous) agents. Data is kept up to 360 days; session details and transcripts for 28 days.

Steps
  1. Open the agent and select Monitor
  2. For conversational agents check resolved/escalated/abandoned; for triggered agents check run outcomes and tool use
  3. Look for periods where satisfaction dropped
  4. Share view-only access with the Analytics Viewer role
  5. Do transcript-based analysis within 28 days
Caution

Active user metrics require authentication to be set on the agent. Test-panel activity isn't counted.

Availability
Generally available (customer comments summary is in preview). Checked 2026-09-12.
Source
Microsoft Learn, "Monitor overview - Microsoft Copilot Studio"
Verified
2026-09-12 (v1)
Supporting passage from the source
Monitoring is available in all geographies. Monitor data is available for up to 360 days. Session details and transcript information are available for the last 28 days.

13Separate what Entra Agent ID and Agent 365 coverVerified

Microsoft Entra Agent ID is available to all Entra customers for creating and managing agent identities. Extending Entra security features (e.g., Conditional Access) to agents requires Microsoft Agent 365.

Steps
  1. Check whether your licenses include Microsoft Agent 365 (included in Microsoft 365 E7)
  2. Record an accountable owner or sponsor per agent
  3. Review risks such as no owner or excessive permissions on the Agents at risk card
  4. Investigate details in the Entra, Defender and Purview portals
Caution

Agent overview usage metrics start when Agent 365 licenses are activated. Risk counts may lag the security portals by up to an hour.

Availability
Entra Agent ID is available to all Entra customers. Agent 365 is a separate license (included in E7 or as an add-on to E5 and others). Checked 2026-09-12.
Source
Microsoft Learn, "What is Microsoft Entra Agent ID?"
Microsoft Learn, "Agent overview in Microsoft 365 admin center"
Microsoft Learn, "Agent Registry in Microsoft 365 admin center"
Verified
2026-09-12 (v1)
Supporting passage from the source
Microsoft Entra Agent ID is a product within Microsoft Entra that provides the platform for creating and managing agent identities and agent identity blueprints. Agent ID is available for all Microsoft Entra customers.

14Admins control preview, experimental, and external model access per environmentVerified

Admins can independently allow or block preview/experimental models and external models (Anthropic, xAI, Mistral) per environment; the two settings are separate and can overlap or diverge.

Steps
  1. Turn on the Preview and experimental AI models setting for the environment to allow preview/experimental models
  2. Check the Move data across regions setting, since experimental models may process data outside the org's region
  3. Turn on external models in the Power Platform admin center for the environment or environment group
  4. Allow access to each external model provider (Anthropic, Mistral, xAI) in the Microsoft 365 admin center
Caution

Experimental/preview and some external models may process or store data outside the organization's region (cross-geo). For environments handling confidential or patient data, confirm data-movement and external-model settings with IT/compliance beforehand.

Availability
Admin-level settings in the Power Platform admin center and Microsoft 365 admin center, configured per environment or tenant.
Source
Microsoft Learn, "Select a primary AI model for your agent (Copilot Studio)"
Verified
2026-09-18 (v1)
Supporting passage from the source
Administrators can choose to allow or block preview and experimental models in an environment. To use these models, the Preview and experimental AI models setting must be turned on for your environment.

15Check your own credit balance and usage history inside CopilotNeeds check

A capability is rolling out that lets end users view their own usage-based billing (UBB) credit usage directly within Microsoft Copilot, including remaining credits and usage history.

Steps
  1. Check the credit usage display within Microsoft Copilot
  2. Review the remaining credit count
  3. Look at usage history to see which work is consuming credits
Caution

This is a rolling-out addition and will not appear unless usage-based billing (UBB) is enabled for the organization. Note that UBB itself is not billed until an admin creates a spending policy for the tenant.

Availability
For organizations using usage-based billing (UBB). Part of a set of capabilities rolling out after an admin sets a spending policy in the Microsoft 365 admin center.
Source
Microsoft Tech Community — Microsoft Copilot Blog, "Evolution of the Copilot pricing model"
Verified
2026-09-27 (v1)
Supporting passage from the source
Spend visibility for end users: Your people can view credit usage, remaining credits, and usage history directly within Microsoft Copilot to manage their own use.

16Track agent makers with the Users by creator type metric in the usage reportNeeds check

To measure Agent Builder adoption, use the Users by creator type metric in the Microsoft 365 Copilot Agents Usage Report in the Microsoft 365 admin center.

Steps
  1. Open the Microsoft 365 Copilot Agents Usage Report in the Microsoft 365 admin center
  2. Check Users by creator type and record the values before and after rollout
Caution

The source does not give the menu path to the report, so confirm it in Microsoft's documentation. Read the numbers for both makers and users. Usage data relates to individuals, so limit who can view it in line with company policy.

Availability
The source says Agent Builder is included in Microsoft 365 Copilot. The admin role needed to view the report is not stated.
Source
Microsoft Tech Community — Microsoft Copilot Blog, "Change Management Best Practices to Drive Value with Agent Builder"
Verified
2026-10-01 (v1)
Supporting passage from the source
Focus on the Users by creator type metric in the Microsoft 365 Copilot Agents Usage Report in the Microsoft 365 admin center.

17Enable, disable, block or assign plugins in the Microsoft 365 admin centerVerified

Admins can review plugins in the Microsoft 365 admin center, enable or disable them, and block or assign them to users or groups.

Steps
  1. In Agent 365 in the Microsoft 365 admin center, open Agents > Tools
  2. Review Microsoft, custom-built, and partner plugins
  3. Enable or disable which plugins are available
  4. Block or assign plugins to users or groups
Caution

The text says some connectors are still rolling out. Before approving, check the data a plugin connects to against internal information-governance rules.

Availability
The plugin registry is rolling out. Basic registry and management capabilities are included with qualifying Microsoft cloud subscriptions.
Source
Microsoft Tech Community — Microsoft Copilot Blog, "Introducing the plugin registry - one place to discover and govern plugins for Microsoft Copilot"
Verified
2026-10-02 (v1)
Supporting passage from the source
Through the Agent 365 experience in the Microsoft 365 admin center, under Agents > Tools, admins can review Microsoft, custom-built, and partner plugins, enable or disable which plugins are available, block or assign them to users or groups.

18Give Dataverse agents least-privileged roles via Entra agent identityNeeds check

With Microsoft Entra agent identities, agents can be provisioned as Dataverse agent users. Each gets a least-privileged security role matching its purpose, and agent-driven actions are audited.

Steps
  1. Provision the agent as a Dataverse agent user by using a Microsoft Entra agent identity
  2. Assign a dedicated, least-privileged security role based on the agent's intended capabilities
  3. Confirm that agent-driven actions are covered by auditing
Caution

The source text gives no click-by-click procedure. Check the linked Power Platform admin documentation on agent users for the setup steps. Keep roles to what the purpose requires and have an admin review them after assignment.

Availability
The Microsoft 365 Roadmap lists it as Launched and General Availability, with a GA date of August CY2026 and a preview date of June CY2026. It is stated as enabled automatically for admins, makers and marketers.
Source
Microsoft 365 Roadmap, "Microsoft Dataverse: Activate Enterprise Data in Copilot - Create Dataverse agent users with Microsoft Entra agent identity"
Verified
2026-10-17 (v1)
Supporting passage from the source
This feature enables agents to be provisioned as Dataverse agent users with dedicated, least‑privileged security roles based on their intended capabilities.

19Enable Agent feedback sharing in the Microsoft 365 admin centerVerified

Admins decide whether makers can see ratings and verbatim comments for their agents: all agents, selected agents, or none.

Steps
  1. In the Microsoft 365 admin center, go to Agents > Settings > Agent feedback sharing
  2. Choose All agents or Selected agents, or No agents to disable sharing
  3. If you choose Selected agents, select the agents whose feedback you want to share
  4. Select Save to apply your choice
Caution

Set the scope to match your organization's policy. Comments contain user-written text, so admins should confirm who can read them. The feature that relies on this setting is an early-access preview.

Availability
Part of Insights Agent V2 (Frontier), an early-access preview; access depends on organization configuration and Microsoft Frontier program requirements.
Source
Microsoft Copilot Blog (Tech Community), "Explore user feedback with Microsoft 365 Insights Agent"
Verified
2026-10-24 (v1)
Supporting passage from the source
In the Microsoft 365 admin center, go to Agents > Settings > Agent feedback sharing. Choose All agents or Selected agents to allow sharing according to your organization's requirements, or No agents to disable sharing.

20Read ratings and comments on your agent with Insights AgentVerified

Ask Insights Agent V2 (Frontier) in Copilot Chat about ratings, verbatim comments and themes for an agent you own.

Steps
  1. Confirm your admin has enabled feedback sharing for the agent
  2. In Microsoft 365 Copilot Chat, search for Insights Agent V2 (Frontier) in the agent picker and choose Add
  3. Ask for recent verbatim comments or ratings over a period
  4. Ask for feedback themes, then review the original comments before deciding what to change
Example prompt

Show me recent verbatim comments for [Agent Name]. How many thumbs up and thumbs down did [Agent Name] get this week? Summarize the feedback themes for [Agent Name].

Caution

A theme summary is an AI-generated synthesis, not a substitute for reading the feedback. Do not treat usage counts alone as a measure of quality or business value. Test changes and review later feedback.

Availability
Insights Agent V2 (Frontier) is an early-access preview and subject to change; it requires Frontier program eligibility and admin-enabled feedback sharing for the agent.
Source
Microsoft Copilot Blog (Tech Community), "Explore user feedback with Microsoft 365 Insights Agent"
Verified
2026-10-24 (v1)
Supporting passage from the source
open Microsoft 365 Copilot Chat, search for Insights Agent V2 (Frontier) in the agent picker, and choose Add.

21Query Power Platform assets in natural language with the Cowork admin pluginNeeds check

The Power Platform Admin plugin for Copilot Cowork lets IT admins ask about usage and ownership of apps, flows and agents in their tenant in natural language, and reshape the findings into tables, summaries or HTML reports.

Steps
  1. Set up the plugin by following the Power Platform Admin in Cowork documentation.
  2. Ask a question that states the environment, time period, threshold and output format.
  3. Narrow the findings with follow-up questions and identify the items that need checking.
  4. Ask Cowork to reshape the results into a one-page briefing or an HTML report with filterable, sortable tables.
  5. Where your Cowork setup supports scheduling, reuse a question that proved useful as a recurring review.
Example prompt

Which apps in the default environment were used by more than 10 people in the last 30 days? Give me a table with the owner and a link to each app.

Caution

Answers are AI-generated and can be wrong. Validate important findings against the source admin data before changing policies, and make changes through an authorized admin workflow. Review report contents and sharing permissions before distributing.

Availability
For IT admins. Cowork requirements, licensing and availability are not stated in the source text; check the documentation.
Source
Microsoft Tech Community — Copilot Studio Blog, "Introducing the Power Platform Admin Plugin in Cowork: Agentic Governance with Natural Language"
Verified
2026-10-27 (v1)
Supporting passage from the source
It brings tenant-specific Power Platform data and governance context into Cowork, so IT admins can ask questions in natural language and get answers grounded in their environments.

22Review connector write/delete tools in the admin center and disable connectorsNeeds check

As create, update and delete tools are unblocked for Federated Copilot connectors (MCP type), admins can view each connector's read and write/delete tools. Connectors that do not meet the organization's policies can be disabled.

Steps
  1. Open the list of Federated Copilot connectors in the Microsoft 365 admin center.
  2. Review the read tools and the write/delete tools of each connector.
  3. Disable connectors that do not meet your organization's policies.
Caution

The source states only that admins can view the tools and disable connectors; it does not name the menu in the admin center, so confirm the location in your own tenant. User actions run with the user's own permissions in the third-party service and require explicit confirmation before they run.

Availability
Generally available (GA). The Microsoft 365 Roadmap lists October CY2026, Worldwide (Standard Multi-Tenant), Desktop and Web. It applies to Federated Copilot connectors of the MCP type.
Source
Microsoft 365 Roadmap, "Microsoft Copilot (Microsoft 365): Federated Copilot Connectors will support write, update and delete actions"
Verified
2026-10-31 (v1)
Supporting passage from the source
Admins can view each connector's read and write/delete tools in the Microsoft 365 admin center and disable connectors that don't meet their organization's policies.