Dynamics 365 Contact Center - Information regarding the end of support for Customer Intent Agent in Voice
Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.
Action date
Microsoft tags this a retirement but gives no action date in the notice metadata. Any date is in the text below.
- Microsoft's start date
- 23 Jul 2026
- Last changed by Microsoft
- 23 Jul 2026
- First seen here
- 19 Oct 2026
- Versions seen
- 1
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedOn July 17, 2026, the Customer Intent Agent in Voice feature in Dynamics 365 Contact Center reached end of support. How does this affect me? Voice interactions that previously relied on this feature for AI-driven customer intent detection will no longer benefit from its capabilities, and no new data will be generated by this feature following the end-of-support date. What action do I need to take? We have developed the Realtime Voice capability of the Customer Assist Agent, which is our recommended path for voice self-service scenarios in Dynamics 365 Contact Center. Realtime Voice is designed to support more natural, responsive conversations while giving organizations a better foundation for combining structured business logic with AI-powered voice experiences. If you currently use Customer Intent Agent for Voice, we recommend reviewing your existing scenarios and recreating the experiences that you wish to continue using Realtime Voice agents.
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.