Microsoft 365 Apps 1712 · Version Status
Microsoft 365 Apps 1712 End of Life Date
Microsoft 365 Apps 1712 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (learn.microsoft.com); the source of each date is on the product page.
⚠
Microsoft 365 Apps 1712 is past end of life. This version no longer receives security patches. Past EOL — migrate to a supported version immediately.
EOL Date
date not published
Past EOL
Latest Release
1712
Standard release
Release Date
Jan 17, 2018
Microsoft 365 Apps 1712 series
Where these dates come from
ReleaseJan 17, 2018Vendor's own page, read by our adapter · learn.microsoft.com · checked Oct 25, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Microsoft 365 Apps 1712 was released on January 17, 2018.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA 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 →
Extended Support
Extended Microsoft 365 Apps 1712 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All Microsoft 365 Apps Versions
| Version | Latest | EOL Date | Status |
|---|
| 1612 |
1612 |
Supported |
EOL |
| 1701 |
1701 |
Supported |
EOL |
| 1702 |
1702 |
Supported |
EOL |
| 1703 |
1703 |
Supported |
EOL |
| 1704 |
1704 |
Supported |
EOL |
| 1705 |
1705 |
Supported |
EOL |
| 1706 |
1706 |
Supported |
EOL |
| 1707 |
1707 |
Supported |
EOL |
What does Microsoft 365 Apps 1712 end of life mean?
When Microsoft 365 Apps 1712 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 Microsoft 365 Apps 1712 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Microsoft 365 Apps 2610 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Microsoft 365 Apps 1712 reach end of life?
Microsoft 365 Apps 1712 has already reached end of life, though the vendor has not published an exact date.
Is Microsoft 365 Apps 1712 still supported?
No. Microsoft 365 Apps 1712 reached end of life on date not published and is no longer receiving security patches.
What should I upgrade to from Microsoft 365 Apps 1712?
The recommended upgrade from Microsoft 365 Apps 1712 is
Microsoft 365 Apps 2610 — the latest actively supported version. Check the
Microsoft 365 Apps full timeline for all supported versions.
What are the security risks of running Microsoft 365 Apps 1712 past EOL?
Since Microsoft 365 Apps 1712 reached end of life, the maintainers no longer issue 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 Microsoft 365 Apps should migrate immediately or implement compensating controls.