Copilot in Customer Service vs. Service Agent in Microsoft 365 Copilot
Just when you thought you had all the Microsoft Copilot names figured out, even with their tricky use of prepositionsā¦here comes another change. The Copilot experience for service is evolving, with Service Agent in Microsoft 365 Copilot becoming the service-specific agent for customer service.
But this is more than a name change. There is an important distinction between the Copilot functionality available inside Dynamics 365 Customer Service and the broader Service Agent in Microsoft 365 Copilot.
Copilot in Dynamics 365 Customer Service
The Copilot functionality inside Dynamics 365 Customer Service is focused on helping a customer service representative while they are actively working cases and conversations. These features are included with your Dynamics 365 Customer Service Enterprise or Premium license and are primarily focused on work and data within Customer Service.
- Ask questions about a case
- Summarize cases and conversations
- Draft emails
- Generate resolution notes
- Create knowledge drafts
Copilot is primarily grounded in the current Dynamics 365 Customer Service experience and the knowledge configured for that environment. For many service teams, that is exactly what they need: AI assistance directly inside the application where they are already working.
Service Agent in Microsoft 365 Copilot
Service Agent in Microsoft 365 Copilot (that is a mouthful of a product name!) takes things further. Instead of focusing only on the current Customer Service experience, Service Agent can bring together Dynamics 365 Customer Service data with Microsoft 365 context and connected knowledge sources such as SharePoint. This gives the customer service representative a much broader assistant with deeper knowledge outside of Dynamics 365.
It can help review and prioritize cases, summarize interactions, retrieve knowledge and, importantly, take actions on cases.
For example, Service Agent can:
- Update a case status
- Add notes
- Create child cases
We are moving beyond AI that simply tells you something or writes something for you and toward agents that can (and do!) take action.
The Difference
I think the easiest way to remember this is:
- Copilot in Customer Service helps you work inside Customer Service.
- Service Agent helps you work across your broader service ecosystem, including inside Dynamics 365 Customer Service.
The in-app Copilot capabilities are not disappearing. They remain an important part of Dynamics 365 Customer Service.
But Microsoft is positioning Service Agent as the service-specific agent within Microsoft 365 Copilot, with access to deeper organizational context and the ability to perform service actions.
Why It Matters
For organizations using Dynamics 365 Customer Service with Microsoft 365 apps (like Outlook, Teams, and SharePoint), this could be a significant shift.
Customer service representatives often need information that does not live neatly inside one case record, or even inside Dynamics 365. Giving an agent access to approved CRM, knowledge, and Microsoft 365 context means fewer places for the representative to search and, ideally, fewer clicks to get work done.
And perhaps most importantly, we are starting to see the transition from Copilot as an assistant to Copilot as an agent that can take action.
