Governing SharePoint Skills and Agents: Your Webinar Questions Answered
Years ago, fellow Microsoft MVP Drew Madelung and I did an Ignite session on managing self-service and oversharing, and those problems feel easy now. Today any licensed site member can just ask Copilot in SharePoint to change things, so our webinar started there, with what a member can do by default. Most of your questions were about the governance controls that secure it, and you can watch every demo in the recording if you missed any of it.
Key takeaways
- Copilot in SharePoint runs as the person using it, so whoever has Edit on a site, members included by default, can change its columns, autofill prompts, skills and the instructions Copilot follows there.
- Everyday Copilot in SharePoint is on for everyone with a Microsoft Copilot (formerly Microsoft 365 Copilot) license, while advanced work stays off until a spending policy covers it.
- Making the Agent Assets library read-only for members still lets them run site skills, as of our testing the week of the webinar.
- Restricted Content Discovery keeps a site out of organization-wide search and Copilot while you review who has access, and searches from inside the site keep working.
- Separate spending policies give each service its own limit, so one big Copilot Cowork task can’t use up the limit you set for Advanced work in SharePoint.
- Agents in SharePoint aren’t going away, only the .agent file format, and those files stop responding after March 2027, so plan each agent’s upgrade now.
Everything below is as of November 12, 2026, the day of the webinar and the week before Ignite, and this part of SharePoint changes fast.
What site members can do with Copilot in SharePoint
Members get the Edit permission level (opens in a new tab) by default, and Edit lets someone add, edit and delete lists and libraries, including their columns and public views, on top of working with the files. Copilot in SharePoint runs as the person using it, so anything a member could change by hand, they can now change by asking.
Does the site owner get notified when someone runs a skill?
No. Nothing tells the site owner that a member ran a skill or changed an autofill prompt, and there’s no audit event that says this person ran this skill at this time. Microsoft Purview still records the changes themselves, like a column or a folder being created. It also keeps audit records for every Copilot interaction (opens in a new tab), with who used Copilot in SharePoint, when, and which files and sites it read or changed. The text of the prompt isn’t in those records, but you can find it with eDiscovery or Data Security Posture Management for AI.
That helps after something goes wrong, but site owners don’t open the Purview audit log for fun, and most SharePoint admins only go there once they know something happened. The closest thing to day-to-day visibility is the Site skills page (Settings > Site skills), which lists every site skill with its creator and last modified date, and lets owners turn each one on or off.
Can I let only trusted people make library-wide changes, like editing an autofill prompt?
Not inside Copilot in SharePoint itself. There’s no switch that gives one group library-wide changes and keeps everyone else to the basics, and I’d love a way to block a single tool, like deleting items, while leaving the rest on. Even when you lock down a skill, someone can still ask Copilot for the same steps with the right prompt.
SharePoint permissions can do the split you’re after, though. Changing a column, including its autofill prompt, needs the Manage Lists permission, which is part of Edit but not Contribute. Autofill also processes every new file uploaded to the library (opens in a new tab), whether or not the person uploading it has a Copilot license. So give the people you trust Edit, give everyone else Contribute, and autofill keeps working on every upload.
A member who reorganizes a library also breaks the shortcuts people created to it, and most organizations think of members as contributors more than designers. If that’s how you think of yours too, Contribute is the permission level that matches. Try it on one site first, though, because Contribute also takes away creating and deleting lists and libraries, which some teams rely on.
Can Copilot show me what it will do before it does it?
For autofill, yes. When you ask Copilot in SharePoint to create autofill columns, it shows the columns it suggests, highlighted and marked as AI-generated, with the metadata it pulled from the library’s recent files. Nothing is saved until you select Save changes and confirm with Apply changes. That confirmation also asks whether to update the current view or save the result as a new view. When you edit an autofill prompt yourself, you test it on files from the library before you save it.
Skills don’t work that way. A skill makes its changes for real, and Copilot asks you to approve them as it goes, so reading those approvals is your only preview. I expect plenty of people to click through them without reading.
Locking down skills and SHAREPOINT.md
Site skills are SKILL.md files in the site’s Agent Assets library, under Agent Assets/Skills, and the site’s SHAREPOINT.md file sits in the same library. Copilot in SharePoint reads SHAREPOINT.md before every conversation on the site, so whoever edits it changes how Copilot behaves for everyone there. Those instructions also run with the permissions of the person asking, not the person who wrote them, and you can see what a member can do with that in the recording. By default, anyone with Edit can create, change or delete both the skills and SHAREPOINT.md.
Why do sites have an Agent Assets library nobody turned on?
Because nobody has to turn it on anymore. Copilot creates the Agent Assets library itself. Microsoft documents that it happens the first time someone creates a site skill, and it also shows up when someone just asks Copilot about skills.
You can’t delete it, because the product manages it, and there are no separate admin controls to turn skills on or off. If a site shouldn’t have Copilot in SharePoint at all, Restricted Content Discovery removes it from that site. Otherwise, treat Agent Assets like any other library and decide who can edit it.
If I make the skills folder read-only, can members still run skills?
Yes, as of our testing the week of the webinar. With read-only access to the Agent Assets library, a member account couldn’t create or change a site skill, but it could still run the site’s skills. Microsoft documents the same approach (opens in a new tab), breaking permission inheritance on the Agent Assets library and applying more restrictive permissions.
You can go one level further and remove members’ access to a single skill’s folder, which hides that skill from them in /skills. I’d make SHAREPOINT.md editable by owners only too. The cost is one more broken permission inheritance, which admins and site owners hate, so decide site by site.
Give your helpdesk a heads-up when you lock down the Agent Assets library, because I’ve seen Copilot start building a skill and only fail when it tries to save it. I also covered protecting skill files in my SharePoint skills FAQ.
Is there one place to govern skills across SharePoint, Copilot and other tools?
Not today. Skills now live in Copilot in SharePoint, in the agents people build with Agent Builder and in other tools across your organization, and each comes with its own storage and its own lifecycle. Someone on LinkedIn already joked that we need a Skills365 to manage it all.
The Enterprise skills group in /skills tells you Microsoft is working on something, but we don’t know what it is yet. Skills are also about to reach further, because plugins that let Copilot in SharePoint connect to external systems are already in preview.
In the meantime, I’m building PowerShell scripts that inventory what’s out there across a tenant. The skills report lists every skill by site and flags the ones that aren’t valid. It also finds duplicates on the same site, and catches skills with the same name on several sites that have drifted apart and now do different things. A second report lists every autofill column with its prompt, and a third inventories agents, with an upgrade view for the .agent retirement.
Everyone who attended gets them first, in the next week or two, and if you’d like to help test them, message me on LinkedIn (opens in a new tab).
Keeping content out of Copilot and search
Does Restricted Content Discovery stop a site from being searchable?
Only from organization-wide search. Restricted Content Discovery (opens in a new tab) (RCD) doesn’t remove anything from the Microsoft 365 search index. It keeps the site’s content out of organization-wide search, like SharePoint home and Office.com, and out of Microsoft Copilot responses. Searches that start from the site itself keep working, permissions don’t change, and Purview features like eDiscovery and auto-labeling keep running, so if you know the site exists, you can still search it.
Microsoft designed it as a temporary control for sites you’re still reviewing, and asks you to use it selectively. Every site you restrict takes its content out of Copilot’s answers. It also removes Copilot from the site completely. With it on, nobody sees the Copilot button, the AI actions menus or Create pages with AI on that site, and it wins over every other setting, Site AI settings included. It works on SharePoint sites only, not OneDrive, and your tenant needs Copilot licenses and SharePoint Advanced Management to use it.
By default, only SharePoint admins can change it, and you can delegate it to site admins with Set-SPOTenant -DelegateRestrictedContentDiscoverabilityManagement $true. Delegating it makes sense when no SharePoint admin can know what’s on 10,000 sites, but I’d be careful with it, because I don’t want a site owner switching it off just to get Copilot back. It helps that a site admin has to give a justification for every change, and Purview audits each one. Start-SPORestrictedContentDiscoverabilityReport generates a report of every site where it’s on, and I covered more of its edges in my post on SharePoint agent governance.
Can I keep files in search but out of Copilot answers?
Yes, file by file, with sensitivity labels, and there are two ways to do it. The first is a label with encryption: when a label lets people view a file but doesn’t give them the EXTRACT usage right, Copilot won’t summarize it and only links to it. That works, but encryption follows the file everywhere, including email and partners, and autofill can’t analyze encrypted files, so plan it carefully.
The second way doesn’t need encryption. A Microsoft Purview data loss prevention policy for Copilot (opens in a new tab) can use a sensitivity label as its condition, in the Microsoft Copilot, Copilot Chat, and Copilot Cowork location. Copilot then doesn’t use those files’ content in its answers, though they can still show up as citations. Microsoft lists where that applies, including Microsoft Copilot, Copilot Chat, Cowork, Copilot in Word, Excel and PowerPoint, and agents in SharePoint. Copilot in SharePoint isn’t on that list, so I’d test it there before relying on it.
Either way, get the permissions on the site right before you start labeling file by file.
Is my content protected while Restricted Content Discovery is still applying?
Yes, as long as your permissions are right, because Restricted Content Discovery was never a permission boundary. A change can take more than a week to fully apply on a site with more than 500,000 items, but Copilot won’t use any file the person asking can’t already open. So the risk during that week is the same one you have all year, which is people having access they shouldn’t, and most companies don’t have their permissions 100% right.
Files people have already opened are the gray area. The Restricted Content Discovery page says it limits recently interacted files too, but the Copilot Search admin documentation (opens in a new tab) says a restricted site can still surface for someone who owns or recently interacted with its content. One organization that ran it on every site for a month saw Copilot still use items people had already opened.
It also doesn’t affect content already in use, like summarizing a document someone has open. So if a site holds content people shouldn’t see, fix who can open it, with permissions or Restricted Access Control, instead of relying on discovery.
How do I show regulators that we manage and monitor Copilot use?
There’s no one-click answer, and Microsoft Agent 365 isn’t the missing piece, because it has no connection to Copilot in SharePoint features. What you can show today comes from Microsoft Purview:
- Audit records for every Copilot interaction, with who used it, when, where, and which files and sites it accessed, including their sensitivity labels.
- The prompts and responses themselves, which you can search with eDiscovery, review with Communication Compliance and keep or delete with retention policies.
- Data Security Posture Management for AI, where you can also view the text of prompts and responses.
- Your data loss prevention and sensitivity label policies, which Copilot respects before anything reaches the user.
That’s a toolbox rather than a ready-made compliance report, and if you’d rather not build that reporting yourself, third-party governance tools can help. Unlicensed users are the easy part, because Copilot in SharePoint needs a Microsoft Copilot license, so people without one don’t get it at all.
Copilot Credits and budgets
Everyday Copilot in SharePoint work is included with the Copilot license. Advanced work, like real-time autofill, working at scale and generating images, uses Copilot Credits. I’ll be honest, where one ends and the other starts is still confusing, so I covered it in my Copilot in SharePoint FAQ.
What keeps it under control is that advanced work stays off until a spending policy covers it, and site-wide real-time autofill also has to be turned on for each site, which it isn’t by default. When a request needs credits someone doesn’t have, Copilot says so instead of running it. Asked for an image of a tiger, it answered that it couldn’t because the request needs Copilot credits, which aren’t available or approved.
Can I give Copilot Credits to a specific team or person?
You can control who spends credits and how much, but a spending policy (opens in a new tab) is a limit, not a reservation, so it doesn’t set credits aside for anyone. In the Microsoft 365 admin center, under Copilot > Cost management, each spending policy for people sets:
- Who it applies to: all users, or specific security groups.
- Which services it covers, such as Advanced work in SharePoint, Advanced work in OneDrive, Copilot Cowork and Copilot Code.
- A monthly limit for the whole policy, and optionally a monthly limit per person, so one person can’t spend everything.
- The billing method, which a Global or Billing administrator can point at a different Azure subscription to bill a department separately.
For agents, resource-based spending policies put a monthly limit on specific Copilot Studio agents or environments instead of people. If you buy prepaid capacity packs, admins allocate those credits in the Power Platform admin center. As for which team, Microsoft’s guidance for Copilot in SharePoint (opens in a new tab) is to start with the people who manage sites and content at scale, like content managers and site managers. Most other SharePoint users likely don’t need credits.
Give each service its own policy. If Copilot Cowork and Advanced work in SharePoint share one, a single big Cowork task can use up the monthly limit the whole department was counting on. Also check whether your existing policies add new services automatically (the Auto-apply new services setting). It’s on by default, so a policy you created for Cowork may already cover Advanced work in SharePoint. And when someone falls under several policies for the same service, the one with the highest per-person limit applies in full, without combining the others.
How do I set a budget when nobody knows next year’s AI usage?
You set limits first and learn from the usage. Nobody has visibility into next year’s usage yet, so the policy limits are what keep you safe. For an HR team, for example, you could cap the whole policy at $1,000 a month and each person at $20 a month. That’s 2,000 credits at the pay-as-you-go rate, which is also the minimum per-person limit Microsoft asks for.
Then give people a way to step up. When someone has 20% of their monthly limit left, Copilot warns them, and they can request more credits right from the prompt, so you decide who gets more instead of raising everyone’s limit. The Overview tab in Cost management shows total consumption and the policies and people getting close to their limits. It refreshes every 4 hours, which gives you real numbers for next year’s budget.
So far, the dollar amounts we’ve seen have been small. You’d have to do a lot of things wrong to spend a million dollars on autofill, and if you manage it, come on our next webinar and tell us how.
How do I track prepaid credits as they burn down?
Each kind of prepaid credit shows up in a different place, which is probably why yours aren’t where you expect. Microsoft’s comparison of the dashboard views (opens in a new tab) breaks it down:
- Prepaid capacity packs appear on the Prepaid Capacity pack credits usage card on the Overview tab in Cost management, and in the Power Platform admin center, but not in Azure Cost Management.
- Copilot Credit pre-purchase plans (P3) are counted inside the Pay-as-you-go credit used card in the Microsoft 365 admin center, and they show up in Azure Cost Management as a reservation benefit, with an amortized cost view.
So capacity packs won’t show up in Azure, and P3 doesn’t get a card of its own in the Microsoft 365 admin center.
Agents after the .agent file
Agents in SharePoint aren’t going away, only the .agent file format is. Microsoft is upgrading them to fit the rest of the Copilot extensibility ecosystem, with a place in the Copilot app and the Microsoft plugin registry. From mid-November 2026, new agents built from SharePoint use Microsoft Copilot Agent Builder instead of .agent files.
Every existing .agent file needs a decision before March 2027. You have four options for each one: move it to Copilot in SharePoint, convert it to a skill, upgrade it to a full agent, or delete it. For the skill route, Copilot in SharePoint gets a convert-agent-file-to-skill skill in mid-November 2026.
Will a Copilot Studio agent published to a SharePoint site keep working?
The agent will, but the .agent file that publishing created won’t. Existing .agent files keep working until the end of March 2027 and then stop responding, in SharePoint, Teams and the Copilot app. Microsoft’s upgrade guidance (opens in a new tab) says you don’t need to recreate a Copilot Studio agent because of this. Publish it to the Microsoft Copilot app and Teams so it can go on a page in the Agent Chat web part, which Microsoft lists as coming soon. Then delete the .agent file once the agent is on a page.
The .agent file also gets an upgrade path when you open it in SharePoint, but nothing upgrades automatically, so start with an inventory. Admins can run the agent insights report (opens in a new tab) from the SharePoint admin center or with Start-SPOCopilotAgentInsightsReport. Agent owners can check Owned by you in Build in SharePoint, and anyone can search a site for *.agent. My scripts will add an upgrade view once they’re out. Then delete what nobody uses, and agree on a path with the last person who modified each of the rest.
What will the Copilot icon open once .agent files are gone?
Copilot, and only Copilot. Once .agent files go away, site owners lose the setting that picks which agent the icon opens. After March 2027, Copilot is the only main agent on a site (opens in a new tab), and Microsoft is removing that setting. Upgraded agents can’t be used in the site’s chat pane, so Microsoft’s guidance puts them, and Copilot Studio agents published to SharePoint, on pages through the Agent Chat web part instead.
For a sensitive site, the control that covers every kind of agent is Restricted Content Discovery. It stops any agent, from SharePoint agents to Agent Builder and Copilot Studio agents, from using the site’s content in its answers. Microsoft also documents that people can’t add a restricted site’s content to other agents.
Can guests use Copilot on our sites with their own tenant’s license?
No. A Copilot license doesn’t carry over from one tenant to another, because what matters is what’s assigned in your tenant. So a guest licensed at home still can’t use Copilot in SharePoint on your site.
What this means for you
The governance controls aren’t the same as they were five or six years ago, or even six months ago. The everyday features are already on for licensed users, so the real question is who can change what on each site, and advanced work stays off until a spending policy covers it. On Monday, start here:
- Decide which sites need Restricted Content Discovery, and whether it’s there for oversharing or to keep Copilot in SharePoint off a site until you’ve cleaned up who’s a member. The SharePoint Admin Agent and data access governance reports can help you find them.
- Open your spending policies, decide whether Advanced work in SharePoint belongs in them, and give it its own policy or uncheck it.
- Decide who should edit skills and SHAREPOINT.md on your important sites, and set permissions on the Agent Assets library there.
- Find your .agent files, delete the ones nobody uses, and agree on a path for the rest with the last person who modified them, before March 2027.
Most of that list is SharePoint permissions work, and in my opinion, if your SharePoint permissions are perfect, that solves 99% of your Copilot problems. The 1% can still break everything, though, so don’t skip the rest of the list.
What’s there today isn’t enough yet, and the feedback from sessions like this one goes back to Microsoft to help shape the right governance model. We show what’s possible because we care about this too, and we want it to get better.
Ready to spend a full day on SharePoint AI governance? Drew and I are running our full-day workshop, The AI-Era SharePoint Administrator: Governance, Skills, and Agents for the Modern Admin, at ESPC in Amsterdam on November 30, and again in May at the Microsoft 365 Community Conference in Las Vegas. Save 15% on ESPC with my code VladSpecial.
Frequently asked questions
Is Copilot in SharePoint turned on by default?
Yes, for the everyday features. General availability started rolling out on September 30, 2026, and once it reaches your tenant, everyone with a Microsoft Copilot license gets them with no opt-in step, while advanced work waits for a spending policy. The preview PowerShell settings that kept tenants or sites out were honored until November 1, 2026, and now you manage availability with Site AI settings and Restricted Content Discovery.
Can I turn off Copilot in SharePoint for specific people?
Yes, through licensing. In the Microsoft 365 admin center, you can turn off the Microsoft Copilot for SharePoint service plan on a person's Copilot license, which also turns off Copilot in OneDrive and the Copilot that helps author SharePoint pages for them. It works, but you end up building separate groups to manage who gets it.
Can I hide Copilot in SharePoint from site visitors?
Yes. In Settings > Site AI, site owners can hide the Copilot button on site pages for visitors only. It only helps if the site actually uses its Visitors group, so people who should only read the site need to be visitors, not members.
Can I restore a site skill that a member changed or deleted?
Usually, yes. Open the skill from Settings > Site skills, and its Versions tab restores an earlier version as a new current version without losing the history. A deleted skill goes to the recycle bin, and even if a member empties it from there too, a site collection admin can still restore it from the second-stage recycle bin, within 93 days of the original deletion.
Can people run skills on my site that I can't see?
Yes. Personal skills live in each person's OneDrive, so they never appear on your site's Site skills page, but their owners can still run them on your site. Typing /skills in the Copilot in SharePoint chat shows each person every skill they can run there, including the built-in ones from Microsoft. A personal skill still runs with its owner's permissions, so your site's permissions decide what it can change.
