Do you know the right Copilot Lingo?
Last updated by Jean Thirion [SSW] about 1 month ago.See history“I asked Copilot to pull the sales deck, but nothing happened.”
Sounds familiar? Chances you were using the personal Copilot, while the deck lives in your Office 365 tenant. In the Microsoft world, not all Copilots are equal. Add Agents and Connectors to the mix and you can easily get lost.
Know your Copilots
Type | Where to find it | ✅ What it can reach | Typical ask |
---|---|---|---|
Personal Copilot |
|
|
“What’s the best way to do XYZ?” |
Microsoft 365 Copilot |
|
|
“What happened on Project XYZ while I was on leave?” |
Product Copilots |
|
|
“How do I snapshot a VM?” |
Agents ≠ Copilots
Agents are not the same as Copilots. In fact, Office 365 Copilot can invoke Agents. There are task-specific AIs with their own memory.
There are 3 main types of Agents within the Microsoft world:
- Built-in Agents – Research, image creation, and more
- SharePoint Agents – Pointed at sites or libraries for focused intelligence
- Custom Agents – Fully customized Agents with custom prompts, behaviours and knowledge (O365 Data or External)
Copilot Connectors
Copilot Connectors (aka Graph Connectors) are gateways to access data from custom Agents. By default your tenant is configured for SharePoint Copilot Connectors (that's how SharePoint Agents access your data) but you can also roll your own connectors to access external Enterprise Data (SQL, Jira, Zendesk, etc.).
Use precise language
“Just get Copilot to pull the latest bug list.”
Figure: Bad example – Unclear which Copilot and where the bugs live
“Ask Microsoft 365 Copilot to summarize the Bugs list in SharePoint→Northwind→Dev.”
Figure: Good example – Specifies the flavor and the data source