Dynamics 365 Customer Engagement (on-premises) 9.1 · Version Status
Dynamics 365 Customer Engagement (on-premises) 9.1 End of Life Date
Dynamics 365 Customer Engagement (on-premises) 9.1 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
Dynamics 365 Customer Engagement (on-premises) 9.1 is actively supported. EOL date: January 9, 2031.
📅 Get reminded before Dynamics 365 Customer Engagement (on-premises) 9.1 reaches EOL on January 9, 2031 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Jan 9, 2031
1552 days remaining
Latest Release
—
Standard release
Release Date
Jun 7, 2021
Dynamics 365 Customer Engagement (on-premises) 9.1 series
Lifecycle detail
Dynamics 365 Customer Engagement (on-premises) 9.1 was released on June 7, 2021 and support is scheduled to end on January 9, 2031 — a planned supported lifespan of 9 years and 7 months.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
All Dynamics 365 Customer Engagement (on-premises) Versions
| Version | Latest | EOL Date | Status |
|---|
| 9.0 |
— |
Jul 11, 2023 |
EOL |
| → 9.1 |
— |
Jan 9, 2031 |
Active |
What does Dynamics 365 Customer Engagement (on-premises) 9.1 end of life mean?
When Dynamics 365 Customer Engagement (on-premises) 9.1 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Dynamics 365 Customer Engagement (on-premises) 9.1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Dynamics 365 Customer Engagement (on-premises) 9.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Dynamics 365 Customer Engagement (on-premises) 9.1 reach end of life?
Dynamics 365 Customer Engagement (on-premises) 9.1 reached end of life on January 9, 2031. That is 1552 days remaining.
Is Dynamics 365 Customer Engagement (on-premises) 9.1 still supported?
Yes, Dynamics 365 Customer Engagement (on-premises) 9.1 is currently supported. The EOL date is January 9, 2031.
What should I upgrade to from Dynamics 365 Customer Engagement (on-premises) 9.1?
What are the security risks of running Dynamics 365 Customer Engagement (on-premises) 9.1 past EOL?
When Dynamics 365 Customer Engagement (on-premises) 9.1 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Dynamics 365 Customer Engagement (on-premises) should migrate immediately or implement compensating controls.