A location you can pick in retention policies and in Communication Compliance to capture what people ask Microsoft-built Copilots and what those Copilots answer, covering, for example, Copilot Studio, Security Copilot, Copilot in Fabric and Microsoft Copilot. Copilot messages used to fall under the older Teams chats and Copilot interactions location.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Microsoft Copilot experiences in context, with comparison tables and the common traps.
Terms in this definition
- Communication Compliance
Purview insider-risk tool that flags messages in email, Teams or Copilot interactions that may be inappropriate or breach regulations so reviewers can respond; DLP policies sit elsewhere.
- Copilot Studio
Microsoft's low-code tool for building workflows and AI agents. Its generative agents may hand each tool call they intend to make to an external threat detection service, Microsoft Defender for example, for checking.
- Microsoft Security Copilot
Security assistant powered by generative AI, used in its own portal or embedded in Intune, Entra, Defender and Purview, and extensible with agents and plugins.
- Copilot in Fabric
Built on Azure OpenAI, this AI assistant in Power BI and Fabric takes plain-language prompts and produces KQL, SQL or DAX code, summaries and visuals. Whatever it does is charged against Fabric capacity CUs.
- Microsoft Copilot
Licensed users get this workplace AI assistant, which grounds large language models in organisational data from Microsoft Graph and the Microsoft 365 apps. It respects existing permissions, so people see only what they could already open; without the licence, people use the web-grounded Microsoft Copilot Chat instead.
- Agents (classic) API
First-generation Foundry Agent Service API, based on threads, messages and runs. It is deprecated, replaced by conversations and responses, and retires on 31 March 2027.