When Copilot says agents are disabled, an admin opens Agents > Settings > User access in the Microsoft 365 admin centre and chooses All users or specific groups, then checks Agent and plugin access and whether the agent itself is blocked. Before switching it on, decide who should get agents: start with a small pilot group, not the whole firm.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowMicrosoft says agents are enabled by default in Copilot-licensed tenants, so a block usually means someone changed a setting, the person lacks a licence or pay-as-you-go access, or one agent is blocked or waiting for approval. Researcher and Analyst aren't affected either way: Microsoft keeps them outside agent settings.
Agent administration is one of the fastest-changing corners of the admin centre. The paths below match Microsoft's pages as they stood on 22 November 2026, and a setting that has moved since will usually still sit somewhere on the Agents pages.
Why does Copilot say agents are disabled in my organisation?
Copilot shows agents as disabled or blocked when an admin setting excludes the person, their licence doesn't cover the agent, or that particular agent has been blocked, rejected or not yet published by an admin.
Staff rarely see the same wording twice. Some see that agents are turned off, some see a message such as "Your organization has prevented this agent from being installed", and some simply can't find an agent a colleague uses. The cause is almost always one of the rows below, so work through them in order.
| What staff notice | Likely cause | Where the admin checks |
|---|---|---|
| No agents at all, for everyone | User access set to No users | Agents > Settings > User access |
| Some people have agents, others don't | User access limited to specific users or groups | Agents > Settings > User access, then the group's members |
| Agents built by colleagues don't appear in the Agent Store | Agents built by your own organisation switched off | Agents > Settings > Agent and plugin access |
| Microsoft agents visible but can't be installed | Microsoft-built agents switched off, or that agent blocked | Agent and plugin access; Agents > All agents > Registry |
| One named agent won't install | That agent is blocked | Agents > All agents > Registry, filter by status |
| A colleague's published agent is missing | It's waiting for admin approval or was rejected | Agents > All agents > Requests |
| Agent opens but won't use company files | Copilot Chat user without a licence or pay-as-you-go access | Billing > Licenses; pay-as-you-go billing policies |
| Can't share an agent with the whole firm | Sharing set to No users or specific users | Agents > Settings > Sharing |
| No option to create an agent on one SharePoint site | Restricted Content Discovery on that site | SharePoint admin centre, the site's Settings tab |
The last row surprises people. Microsoft's page on Restricted Content Discovery says that when a site is restricted, users no longer see AI entry points there, including the AI actions menu used for creating agents. An owner who restricted the HR site during a permissions review may have removed agent creation from it without meaning to.
Who should be allowed to use Copilot agents?
Copilot agents should go first to a small pilot group with a real, repeated task, tidy file permissions and a Copilot licence or pay-as-you-go budget; widen access after a month of evidence.
This is the owner's decision, and it comes before any toggle. Agents act with each person's own permissions, so an agent is only as safe as your SharePoint sharing; agents built in Agent Builder can be shared, so one well-meant agent can spread a folder further than intended; and agents grounded in company data cost money for people without a licence. The User access setting gives you three choices: All users (the default), No users, or Specific users or groups.
| Choice | Pick it when | Watch out for |
|---|---|---|
| All users | Permissions are clean, most staff hold licences, and you have an agent people already ask for | Every agent anyone shares reaches everyone allowed to install it |
| Specific users or groups | You want evidence before a wider rollout, or only one team has a use for agents | People outside the group see agents as unavailable; tell them why |
| No users | A data incident is under review, or permissions are known to be overshared | Staff build workarounds; set a date to revisit |
For most firms under 30 people, a named security group of four to six people is the sensible start. Pick people with a repeated task an agent could help with (answering staff questions from a policy library, drafting from templates, checking a price list), at least one person without a licence so you learn the pay-as-you-go side, and someone who will report what goes wrong. Before you widen access, the files those agents will read need the attention described in which files and sites a Copilot agent can use as knowledge.
If you want help fitting an agent pilot into how your firm already works, I offer one-to-one AI consultations for small businesses.
How does an admin turn Copilot agents on, step by step?
An admin turns Copilot agents on under Agents > Settings in the Microsoft 365 admin centre: set User access, allow the right agent types, set Sharing, then unblock or publish individual agents in the registry.
Use an account with the AI Administrator or Global Administrator role. Then:
- Sign in to the Microsoft 365 admin centre and select Agents > Settings. (The same controls are linked from Copilot > Settings > Data access > Agents.)
- Open User access. Choose All users, No users or Specific users or groups; for a pilot, pick specific groups and add your security group. Select Save.
- Open Agent and plugin access and decide on each type: agents and plugins built by Microsoft, built by your own organisation, and built by external publishers. Switching a type off hides those agents from the Agent Store; Microsoft-built agents stay visible but can't be installed. Plugins here include tools, MCP servers, connectors and skills.
- Open Sharing and choose All users, No users or Specific users. This covers agents built in Agent Builder.
- Go to Agents > All agents > Registry. Use the Status filter to find blocked agents, select one, and choose Unblock agent if it should be available. Clear any old filters first if the list looks short.
- Go to Agents > All agents > Requests. For each pending agent, read its description, owner, data sources and actions, then choose Publish to store and pick who can install it, or Reject submission.
- Optionally install an agent for people so they don't have to find it: in the Registry, filter Status to Available, select the agent, choose Install, pick all users or specific groups, review the permissions and grant admin consent if appropriate, then Finish deployment.
- Optionally pin one or two agents so they appear prominently: use Manage pinned agents in the Registry. Microsoft allows three pinned slots per user and says a new pin can take up to six hours to show.
When agents are built and requested by staff, the requests flow is where most small firms' approvals happen. A request shows as Pending review, Pending update or Pending activate. Until you approve an update, users keep the previous version of the agent, which is useful when a builder changes an agent's knowledge sources and you want to look first.
A before-and-after of the settings page for a firm returning from a full block might look like this:
| Setting | During the block | Pilot settings |
|---|---|---|
| User access | No users | Specific group: "Agents pilot" (5 people) |
| Microsoft-built agents | Allowed | Allowed |
| Agents built by the firm | Off | Allowed |
| External publishers | Off | Off until each publisher's terms are read |
| Sharing | No users | Specific users: office manager |
| Blocked agents in the registry | 2 | 1 unblocked, 1 left blocked (it used an uploaded client file) |
If your tenant uses unified agent and app management, Microsoft says changes to organisation-wide settings sync between the Microsoft 365 admin centre and the Teams admin centre, so a change made in one appears in the other.
Do staff need a Copilot licence to use agents?
Staff don't need a Copilot licence for agents grounded in instructions or public websites, but agents that use company files or other work data need a Microsoft 365 Copilot licence or pay-as-you-go billing.
Microsoft's licence comparison puts it in three lines. Copilot Chat (Basic), included with eligible Microsoft 365 plans, gets agents that use web data, with work-data agents on pay-as-you-go. Microsoft 365 Copilot (Premium), the paid add-on, includes agents that use web and work data. And agents in SharePoint can be used without a Copilot licence only if the organisation has set up pay-as-you-go billing. On Microsoft's business page, the Copilot Business add-on lists at $21 a user a month paid yearly, shown at $18 under a first-year promotion running from 1 July to 31 December 2026.
| Who | Agents on instructions or public websites | Agents on SharePoint or other work data |
|---|---|---|
| Copilot Chat user, no pay-as-you-go | Yes, no extra cost | No |
| Copilot Chat user, pay-as-you-go set up | Yes, no extra cost | Yes, metered per use |
| Microsoft 365 Copilot licence holder | Yes | Yes, no metered charge when the agent runs as them |
One detail catches admins out: for agents that use SharePoint files, Microsoft says the pay-as-you-go billing policy must be connected to the SharePoint agents service, and the users must be in the security group assigned to that policy. A pilot member left out of that group sees the agent but gets no answers from company files.
What will metered agents cost if Copilot Chat users get them?
Metered agents for Copilot Chat users are billed through an Azure subscription at $0.01 per Copilot Credit, and Microsoft's own example shows one reply grounded in company data using 12 credits.
Pay-as-you-go is off by default. Turning it on takes two steps: create a billing policy linked to an Azure subscription and a set of users, then connect that policy to a Copilot service such as Copilot Chat or SharePoint agents. You can add a budget to the policy with email alerts as spending passes percentage milestones, and disconnecting the policy removes those users' access to metered agents. Microsoft's meter page bills $0.01 per Copilot Studio message, the unit Microsoft renamed Copilot Credits in September 2025 without changing the pay-as-you-go rate. Its billing-rates page charges 2 credits for a generative answer, 10 for grounding in the tenant's Microsoft Graph and 5 for an agent action, and gives the 12-credit example for a complex reply grounded in company data. Licensed Microsoft 365 Copilot users aren't charged for these when the agent runs under their own identity.
A quick sum shows where licences and metering cross over. Two support staff on Copilot Chat each ask a policy agent 15 questions a working day, about 630 replies a month across 21 days. At 2 credits a reply that is 1,260 credits, or $12.60; at 12 credits a reply it is 7,560 credits, or $75.60. Two Copilot Business seats at the $21 list price cost $42 a month. Light use favours metering; heavy use of data-grounded agents favours licences. Set the budget a little above the low estimate, watch the first month's figures, and decide then. The detail of each meter is in how Copilot agent credits and metered billing work.
The same arithmetic, per person, shows the crossover point. The table assumes 21 working days, $0.01 a credit, 2 credits for a reply that only needs a generative answer and 12 for a reply grounded in company data, against the $21 list price of one Copilot Business seat. The figures are illustrative.
| Agent questions per Chat user | Replies a month | Metered at 2 credits | Metered at 12 credits | One Copilot Business seat |
|---|---|---|---|---|
| 5 a working day | 105 | $2.10 | $12.60 | $21 |
| 15 a working day | 315 | $6.30 | $37.80 | $21 |
| 30 a working day | 630 | $12.60 | $75.60 | $21 |
At 12 credits a reply, a $21 seat matches metered spend at about 175 replies a month, roughly 8 data-grounded questions a working day. At 2 credits a reply, metering stays cheaper up to about 1,050 replies, around 50 a day. A seat also brings the full Copilot experience in Word, Excel, PowerPoint and OneNote, so for anyone near the crossover the licence is usually the better buy; for occasional users, metering with a budget keeps the cost small and visible.
What should staff be told when agents are switched on?
Staff should hear who has agents, why others don't yet, how to ask for one, and three safety rules: no uploaded client files, no company-wide sharing, and report wrong answers.
A short note from the owner stops the "is mine broken?" messages and sets expectations before anyone builds something risky. This one is written for the pilot set-up above; adapt the names and groups.
Subject: Copilot agents are back on (for a pilot group first)
Hi all,
From today, five of us can use Copilot agents: [names].
Everyone else will see agents as unavailable for now. That's
deliberate, not a fault. We'll review in four weeks and widen
access if the pilot goes well.
If you're in the pilot:
- Build agents from SharePoint files, not files uploaded from
your computer. Anything uploaded to an agent can be read by
everyone who uses it.
- Share agents with named colleagues only. Ask [office manager]
if you think one should go to the whole team.
- If an agent gives a wrong or odd answer, send a screenshot
to [office manager] the same day.
If you're not in the pilot and have a task an agent could help
with, reply and tell me what it is.
Researcher and Analyst in Copilot Chat work as before.
[your name]
Two things are worth adding for staff who see a blocked Microsoft agent in the store. They can select Request on it; the request reaches the admin under Agents > All agents > Requests with the state Allow user to install, and the admin unblocks and approves it. That route exists only for Microsoft-built agents. Third-party agents can't be requested or approved through it.
Worked example: a 12-person financial advice practice
Here is the whole fix for one illustrative business. A financial advice practice has 12 staff: five advisers with Copilot Business licences, and seven support staff on Copilot Chat. Last year an adviser shared an agent built on an uploaded client spreadsheet with the whole practice, and the outside IT contractor set User access to No users. Ten months later, advisers ask why agents are disabled.
The owner's decision. The owner names a pilot group of five: three advisers, the paraplanner and the office manager. The last two are Copilot Chat users, so the pilot needs pay-as-you-go for any agent grounded in the practice's SharePoint. External publishers stay off; sharing goes to the office manager only. Before anything changes, the office manager checks that the client-files library isn't readable by everyone, using the steps in cleaning up SharePoint permissions before turning on Copilot.
The toggles. User access moves from No users to the "Agents pilot" group; agents built by the practice are allowed again; sharing is set to specific users. In the registry, two agents are blocked. One is a Microsoft agent the advisers want, so it is unblocked. The other is last year's agent, and the registry's Data source filter, which can pick out agents with embedded knowledge from uploaded files, confirms it still carries the client spreadsheet. It stays blocked, and the owner deletes it, which Microsoft says starts a 30-day recovery window.
The billing. The admin creates a billing policy for the paraplanner and office manager, connects it to Copilot Chat and to the SharePoint agents service, and sets a $40 monthly budget with email alerts, just above the light-use estimate. Advisers need nothing extra because their licences cover agents run as them.
The time. As a rough planning figure, the decision meeting takes 30 minutes, the permission check an hour, the settings and registry clean-up 30 minutes, billing set-up 20 minutes, and the staff note 10 minutes: under three hours in all.
Four weeks later. The pilot has used two agents: a compliance-manual question agent and a meeting-notes template agent. Metered spend for the two Chat users came to $18. Three support staff have asked for access. The owner adds them to the pilot group and to the billing policy's security group in the same sitting, raises the budget to $70, and books the next review for eight weeks out.
Which mistakes turn an agent fix into a new problem?
The common mistakes when re-enabling Copilot agents are opening access to all users before checking sharing and permissions, allowing every publisher type at once, and forgetting the billing group.
- All users on day one. An agent built on a broad "Team" folder starts answering questions about pay rates for anyone who asks, because the folder was readable by everyone all along. Start with a pilot group, and check permissions on every source an agent uses before access widens.
- Every publisher type switched on together. A third-party agent from the store asks for permission to act on staff mailboxes. Microsoft warns that data processed by non-Microsoft services isn't covered by Microsoft's agreements, so keep external publishers off until someone has read each publisher's terms.
- The forgotten billing group. Two Copilot Chat users in the pilot can open the policy agent but get nothing from SharePoint. They were added to the pilot group but not to the pay-as-you-go policy's security group, and the policy wasn't connected to the SharePoint agents service. Add both in the same sitting.
- Unblocking the agent that caused the block. Last year's problem agent is unblocked with the rest, and its uploaded client file is readable again by everyone who can use it. Filter the registry by data source for embedded knowledge before unblocking anything, and delete agents that carry files they shouldn't.
- Approving updates unread. A builder's update swaps the agent's knowledge from one folder to a whole site, and the admin selects Update in store without opening the details. Read the data sources on every Pending update request; users keep the old version until you approve.
- No users with no end date. After an incident, agents are switched off "for now", and a year later staff are pasting files into consumer AI tools instead. Put a review date on any full block and tell staff what it is.
What if Copilot agents still show as disabled after the change?
Copilot agents still showing as disabled usually means the person isn't in the right group, the agent is blocked or unpublished, the licence or billing group is missing, or the app hasn't caught up.
- Check the person, not the setting. Open the group named under User access and confirm the person is a member. Someone added through a nested group, or to a group created that day, is easy to miss.
- Check the agent in the registry. Find it under Agents > All agents > Registry, clear any filters, and look at its status and who it is deployed to. A deployed agent reaches only the users or groups chosen during deployment.
- Check Requests. A colleague's agent submitted to the organisation stays invisible until someone selects Publish to store.
- Check the licence or billing group. A Copilot Chat user needs to be in the pay-as-you-go policy's security group, and for SharePoint-based agents the policy must be connected to the SharePoint agents service.
- Check the agent type switch. If agents built by your own organisation are off, every colleague-built agent stays hidden however the other settings look.
- Allow time. Microsoft says a newly pinned agent can take up to six hours to appear. Ask the person to sign out of the Copilot app and back in before you change anything else.
- Test as the person. Have them open the Agent Store, search for the agent, and screenshot the exact message. The wording tells you whether it's an access, licence or block problem.
Once agents are flowing again, export the registry to a CSV file each quarter and read it with the owner: who built what, which agents use embedded knowledge, and which have no owner. If reviewing that export in a spreadsheet is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.
The registry also shows an "Agents without owners" card. Shared agents become ownerless when their creator's account is deleted, and the card filters straight to them so you can assign a new owner, block or delete each one. For the four other settings an owner should check around agents, see the five Copilot admin centre settings to check first. Microsoft's description of every option on the settings page is on its agent settings page on Microsoft Learn.
Turning Copilot agents back on: common questions
Does turning off agents also turn off Researcher and Analyst?
No. Microsoft says Researcher and Analyst are part of the core Copilot Chat experience, listed under Tools, and don't fall under any agent-related settings. Blocking agents in Agents > Settings leaves both tools available to the people who can already use them, so if your aim is to stop all AI research features, agent settings alone won't do it.
Can staff use agents without being able to share them company-wide?
Yes. Set Agents > Settings > Sharing to No users or Specific users. With No users, nobody can share an agent with the whole organisation, though people can still share directly with named individuals. Microsoft notes that this sharing control applies only to agents built with Agent Builder, so check agents made in Copilot Studio through the agent registry instead.
Can a member of staff ask for a blocked agent?
Yes, for Microsoft-built agents. In the Agent Store, the person opens the blocked agent and selects Request, and it appears under Agents > All agents > Requests with the state Allow user to install. The admin must unblock the agent before approving. Microsoft says third-party agents can't be requested or approved through this workflow.
Who can change Copilot agent settings?
Microsoft says governance actions such as approving agent requests or assigning owners can only be done by an AI Administrator or Global Administrator; other roles can monitor but not act. On the Copilot settings page, a Global Reader can view but not change settings. Pay-as-you-go billing can be managed by a Global, Billing or AI Administrator. Keep Global Administrator for emergencies and use the narrowest role that works.
Why can a colleague use an agent that I can't?
Usually because of one of four things: the colleague is in the group named under Agents > Settings > User access and you aren't; the agent was deployed only to certain users; the colleague holds a Microsoft 365 Copilot licence or sits in the pay-as-you-go security group; or the agent's SharePoint sources include files only the colleague can open.
Further reads
- Copilot Chat Turned Off by Your Organisation? How Admins Fix It — When Copilot Chat itself is switched off, not just agents.
- How to Set Up Copilot Studio Pay-As-You-Go With an Azure Budget — Setting the Azure budget behind metered agents.
- How to Roll Out Microsoft 365 Copilot to a Small Team — A rollout plan for the people in your pilot group.
- Can You Build a Leave-Policy Agent in Copilot Without a Licence? — A first agent a Copilot Chat user can build.
- How to Write a Weekly Planner Status Report With Copilot — Generate a weekly Planner status report with Planner Agent, add Teams decisions and blockers, then check it, with a filled-in template for a small team.
- How to Use the Copilot Researcher Agent to Compare Suppliers — A cited supplier comparison with Copilot Researcher: the brief to paste, a garage's three-supplier example, source checks and web search settings.
Browse all AI-for-business tutorials
Sources: Microsoft Learn pages on agent settings, managing agents, the agent registry, agent requests, governance and lifecycle actions for agents, Copilot settings in the Microsoft 365 admin centre, the Copilot overview licence comparison, agent capabilities and licensing models, Copilot pay-as-you-go and its meters, Copilot Studio billing rates and licensing, and Restricted Content Discovery; Microsoft 365 Copilot business plans page. All read 22 November 2026.
