Microsoft's Sales and Service Agents go GA. Own the workflow, not the agent.

On July 7, Microsoft flipped Sales Agent and Service Agent to general availability inside Dynamics 365 and Microsoft 365 Copilot. These aren't summarizers anymore. Per Microsoft's own announcement, Service Agent now takes action across the whole service workflow — updating cases, drafting customer-ready emails, recommending next steps — without a human leaving the conversation. If you run sales or support and you're already paying for Microsoft's stack, an autonomous agent just showed up inside the tools your team already uses. The question isn't whether it works. It's what you're renting.

What actually happened

Microsoft's Service Agent GA post says it "moves from answering and summarizing to taking action across the entire service workflow," powered by a Model Context Protocol server shipping 70+ new MCP tools alongside 20+ core product enhancements. Sales Agent and Service Agent now run consistently across Dynamics 365, Copilot, Outlook, and Teams, so the same agent works wherever your reps do.

Microsoft frames the direction with a Gartner number: by 2029, agentic AI will "autonomously resolve 80% of common customer service issues without human intervention, cutting operational costs by 30%." Whether or not that year is right, the trajectory is clear — the routine half of your support and sales follow-up is becoming agent work, and the platform vendors want it running inside their box.

Why it matters for your business

The MCP detail is the tell. Microsoft built Service Agent on the same Model Context Protocol standard we wrote about this week — 70+ tools the agent uses to touch your data. That's good engineering. It also means the agent's usefulness is exactly the reach of those tools, and those tools live in Microsoft's platform, priced and governed by Microsoft.

For a small business the calculus is simple. If you already live in Dynamics and Copilot, turning these on is a real shortcut — take it, but scope it: decide what the agent may touch, what it may send on its own, and where a human signs off. If you don't live in that stack, the answer isn't to migrate your whole company to rent an agent. The durable move is to own the workflow — your customer data, your case rules, your handoff logic — behind an MCP interface you control, and let whichever agent you choose connect to it. Microsoft's agent is a strong option. It shouldn't be the reason your customer relationships live on someone else's platform.

Sources: Microsoft — Moving sales and service organizations forward with agentic CX, Microsoft — Service Agent reaches general availability.