Yes, Copilot in SharePoint reads the columns that come from content types published through the Content Type Hub. In my test it answered questions from a hub content type’s columns exactly as it did from columns added straight to a library, including a question that needed two columns at once. I didn’t have to rebuild or re-tag anything for Copilot to use the hub columns.
I get this question a lot from people who’ve invested in a proper content type setup and want to know whether they have to start again for AI. I recorded the test in January 2026, when the floating button in the corner of the library was called the Knowledge Agent. That preview is now Copilot in SharePoint, and everything below applies to it under the new name.
What did I test, and how was it set up?
Two document libraries on the same demo site, each holding a few documents tagged with a category and an industry.
- Library one had columns added directly to the library, a Category choice column and an industry column. No content type involved.
- Library two, the CT hub knowledge library, used a simple content type I’d created in the Content Type Hub, published, and then added to the library. Its two columns, Knowledge category and Industry relevance, came from that content type rather than from the library itself.
I asked each library the same two questions through the Copilot button in that library: a single-column question (“get me the case studies”) and a two-column question (a case study in the construction industry).
Does Copilot answer from ordinary library columns?
It did, as the baseline. Asked to list the case studies, it returned the Microsoft 365 transformation case study with a citation and a link to the file. Asked what we had in the construction industry, it returned the two documents tagged Construction: the case study and a commercial and pricing assumptions document. Both matched what the library’s own filters showed.
Does it answer from Content Type Hub columns?
Yes. In the hub library, “get me the case studies” returned the two documents with Case study in the Knowledge category column. The two-column question returned the one case study with Industry relevance set to Construction. Copilot treated the hub content type’s columns no differently from the columns I’d added by hand.
My reading of why: when you add a published content type to a library, SharePoint copies its columns into that library, so by the time Copilot looks at the library they’re library columns like any other. Microsoft doesn’t document it in those terms, so test your own setup with the same two questions.
Combining columns isn’t limited to two choice columns either. In an earlier demo on a résumé library, Copilot pulled everyone with a typing speed above 80, then narrowed that to the people with Tableau in their skills column.
What didn’t I test?
Nothing failed, but it was a small test: one content type, two columns and a handful of documents. I didn’t test managed metadata columns, a library with several content types in it, a content type inheriting from a parent, or a library with thousands of items. I also didn’t change a content type in the hub and republish it to see how quickly Copilot picked up the change. If your setup leans on any of those, try it on a real library before you tell anyone it works.
Keep building columns once, centrally
Since Copilot read the hub columns like any others, I wouldn’t change how I design metadata for it. This is how I’d keep approaching it.
- Use the hub for columns that mean the same thing everywhere. If contracts live in libraries across several sites, a published content type gives every library the same Contract type, Renewal date and Owner columns, so a question that works in one library has the same columns to work from in the next.
- Name columns for the question people ask. Industry relevance and Knowledge category told Copilot exactly what the values meant. I haven’t tested a vague name like Field1 against a clear one, but I wouldn’t give Copilot the chance to guess.
- Keep choice values tight. A hub content type is the easiest place to stop “Construction”, “construction” and “Constr.” appearing side by side, because the choices are set once for every library that uses it.
- Remember who can change it. Publishing happens in the SharePoint admin centre, so a site owner can’t fix a hub column on their own. Agree who owns the content type before people start asking Copilot questions that depend on it.
- Start with metadata people will fill in. Content types don’t fill themselves. Pair them with defaults or autofill columns so the columns Copilot reads aren’t half empty.
For the wider case on columns, SharePoint folders vs metadata covers why they beat folders, and turning SharePoint into a Copilot knowledge base with metadata shows which questions columns let Copilot answer. My free Copilot-ready library checklist walks through choosing the columns for one library.
Where Copilot in SharePoint stands now
Copilot in SharePoint needs a Microsoft 365 Copilot licence and began rolling out to general availability on 30 September 2026. It shows as a floating button in the bottom right of pages and libraries, and it doesn’t appear on SharePoint sites opened inside Teams.
Published content types are managed from the Content type gallery in the SharePoint admin centre, or from the hub at /sites/ContentTypeHub. You need SharePoint admin permissions to publish.
Frequently asked questions
Do I need to republish content types for Copilot in SharePoint to use them? No. In my test I published the content type the normal way and added it to the library. Nothing extra was needed for Copilot. Republish only when you’ve changed the content type and want sites to get the update.
What happens to Copilot answers if I unpublish a hub content type? Unpublishing makes the content type unavailable to new sites, and copies already in use are converted to local content types. The columns stay in the libraries that use them, so the metadata is still there to filter on. I haven’t tested Copilot after an unpublish.
Can a site owner add a hub content type to a library? Yes, once it’s published. A published content type has to be added to each library separately, which you can do from Add column, then Content type, in the library.
