The old SharePoint Search Query Tool is still pinned on my taskbar. It has been there for years. Last time I wanted to confirm that items from a Copilot connector were actually reaching the search index, and the old tool just sat there. It talks to the SharePoint search REST endpoint, which is a different…
You checked the connectors gallery, and your system is not in it. Documentum. iManage. An OpenText archive. An on-premises SharePoint farm nobody wants to talk about. So the plan forms: we will have to build a custom connector. Stop for a moment. Between “Microsoft does not have one” and “we build our own” sits a…
Sooner or later, the prebuilt catalogue runs out. You go looking for a connector to bring some system into Copilot, and it is not there because the system is homegrown, or niche, or something a vendor built for you a decade ago. Now you have a choice: build a custom connector, or find another way…
Copilot is only as useful as the content it can reach. Out of the box, it reaches your Microsoft 365 — SharePoint, mail, Teams. But most organisations’ knowledge does not all live in Microsoft 365. It is in ServiceNow, in Salesforce, in a Confluence wiki, on a file share, in some homegrown app the finance…