Microsoft's product lifecycle communication is notoriously easy to miss. Announcements go out to the Microsoft 365 Message Centre, admins read (or don't read) them, and before anyone has a chance to act, the tool is gone — or worse, still working but completely unsupported. You're now running compliance risk on something Microsoft stopped maintaining months or years ago.
This post is a definitive list of the Microsoft tools that are officially retired, the ones most likely still running in your tenant, and what to use instead. If you have a Microsoft 365 admin reading this, at least two items on this list will directly apply to your organisation.
| Tool | Retired | Status in M365 Today | Replacement |
|---|---|---|---|
| Microsoft InfoPath 2013 | Apr 14, 2026 | No security patches | Power Apps, Microsoft Forms |
| SharePoint Designer 2013 | Jan 13, 2026 | Unsupported | Power Automate, SPFx |
| SharePoint 2013 Workflows | Nov 1, 2024 | Removed from SPO | Power Automate |
| SharePoint Add-ins (2010/2013) | Apr 2, 2026 | Removed from SPO | SPFx Extensions |
| Microsoft Stream (Classic) | Apr 15, 2024 | Redirects to Stream on SPO | Microsoft Stream (on SharePoint) |
| Skype for Business Online | Jul 31, 2021 | Fully decommissioned | Microsoft Teams |
| Microsoft Kaizala | Aug 31, 2023 | App shut down | Microsoft Teams |
| Access Web Apps (SharePoint) | Apr 2018 | Removed from SPO | Power Apps, Dataverse |
1. Microsoft InfoPath 2013
Microsoft InfoPath 2013
Form design and data entry tool for SharePoint
End of Support
April 14, 2026 (extended support)
Risk Level
High — no security patches from Microsoft
InfoPath was Microsoft's form designer from the early 2000s. Used primarily to customise SharePoint list forms, build multi-step data entry forms, and create XML-based data submission workflows. Microsoft announced it would be discontinued back in 2014, removed InfoPath Forms Services from SharePoint Online in 2019, and finally ended extended support in April 2026. Any organisation still running InfoPath Filler on managed devices or using InfoPath-customised SharePoint list forms is now on unsupported software. See our full InfoPath migration guide for the complete remediation steps.
Replace with: Power Apps (list form customisation, multi-step approvals) or Microsoft Forms (simple surveys and feedback)
2. SharePoint Designer 2013
SharePoint Designer 2013
No-code workflow and site customisation tool
End of Support
January 13, 2026 (extended support)
Risk Level
High — unsupported, no patches
SharePoint Designer was the primary tool for building no-code SharePoint workflows before Power Automate existed. It could also modify SharePoint site structure, master pages, and page layouts in ways that aren't possible through the browser. Microsoft ended extended support on January 13, 2026 — two months before InfoPath. The tool still works for on-premises SharePoint customers, but receives no security updates. Workflows built in SharePoint Designer that target SharePoint Online were already broken in many cases after Microsoft removed the 2013 Workflow Platform from SharePoint Online in November 2024.
Replace with: Power Automate (for workflows) and SPFx web parts/extensions (for UI customisation)
3. SharePoint 2013 Workflows (and 2010)
SharePoint 2013 & 2010 Workflows
Legacy workflow platforms built into SharePoint
Removal from SPO
November 1, 2024
Risk Level
Medium — already broken in SPO, on-premises still works
This is the one most organisations got caught out on. SharePoint 2013 workflows relied on the Workflow Manager service, which Microsoft shut down in SharePoint Online on November 1, 2024. If you had active 2013 Platform workflows on your SharePoint Online lists and libraries that hadn't been migrated, they stopped running on that date — silently. Many organisations discovered this when a business process that had been running automatically for years simply stopped and nobody noticed until a downstream problem surfaced. SharePoint 2010 workflows were removed from SharePoint Online even earlier (in 2020). Workflows still run on SharePoint Server on-premises, but without Microsoft support beyond the server's own lifecycle.
Replace with: Power Automate — the SharePoint trigger connector provides equivalent functionality with vastly more action options
Go to SharePoint Admin Center → Active Sites → select a site → Site Contents → look for items with a workflow column still showing "In Progress" or "Failed". These are 2013 workflows that were running when the platform was removed. You can also use the SharePoint Workflows report in the SharePoint admin centre (under Reports → Workflow usage) which still shows historical workflow data for active tenants.
4. SharePoint Add-ins (2010 / 2013)
SharePoint Add-ins (Apps)
The old SharePoint app model — provider-hosted and SharePoint-hosted
Removal from SPO
April 2, 2026
Risk Level
High if your SharePoint has Add-ins — they stopped loading
SharePoint Add-ins (previously called SharePoint Apps) were the extensibility model introduced with SharePoint 2013, designed to replace the earlier Farm Solutions model with a more isolated, cloud-friendly approach. Microsoft deprecated the SharePoint Add-in model in 2021 when SPFx reached maturity, then began the hard removal process, completing it in SharePoint Online on April 2, 2026. Provider-hosted add-ins (which host their own infrastructure outside SharePoint) are still technically callable but are not supported and will lose access to SharePoint contexts as the ACS (Access Control Service) authentication method is also being deprecated. SharePoint-hosted add-ins simply stopped loading after April 2026. We covered this in detail in our SharePoint Add-ins retirement post.
Replace with: SPFx Web Parts and Extensions — the modern SharePoint extensibility model with full support and Wave 2 2026 improvements
5. Microsoft Stream (Classic)
Microsoft Stream (Classic)
The original Stream video platform — pre-SharePoint integration
Retirement Date
April 15, 2024
Risk Level
Medium — embedded links broke, content redirected or lost
The original Microsoft Stream was a standalone video hosting service inside Microsoft 365. Microsoft rebuilt Stream entirely on top of SharePoint and OneDrive (now called "Stream on SharePoint"), and shut down the classic version on April 15, 2024. Content was automatically migrated for most users, but embedded Stream Classic video links in SharePoint pages, Teams tabs, and Viva Connections cards were broken by the migration — those links pointed to the old URL structure which no longer exists. If you have SharePoint pages with embedded Stream videos that stopped playing in mid-2024, this is why. The fix is to re-embed the video using the new Stream on SharePoint URL.
Replace with: Stream on SharePoint — videos stored in SharePoint/OneDrive, accessible via the Stream web app or directly in SharePoint document libraries
6. Skype for Business Online
Skype for Business Online
Enterprise messaging and conferencing platform
Retirement Date
July 31, 2021
Risk Level
Low — fully decommissioned and replaced, but on-premises SfB Server has its own lifecycle
Skype for Business Online (the cloud service) was fully decommissioned on July 31, 2021. All tenants were migrated to Microsoft Teams. The on-premises version — Skype for Business Server 2019 — remains supported until October 14, 2025 (mainstream) and October 14, 2028 (extended). Organisations running Skype for Business Server 2019 on-premises still have time, but Teams is the clear strategic direction and hybrid migrations are straightforward. Skype for Business Server 2015 mainstream support ended October 13, 2020 — if you're still on 2015, you're on extended support only.
Replace with: Microsoft Teams — chat, meetings, calling, files, and apps in one platform. Hybrid migration tools available for on-premises SfB customers.
7. Microsoft Kaizala
Microsoft Kaizala
Mobile-first messaging app for frontline and field workers
Retirement Date
August 31, 2023
Risk Level
Low — app shut down, content not recoverable
Kaizala was acquired by Microsoft from an Indian startup in 2018 and was marketed as a WhatsApp-like messaging tool for frontline workers, particularly in markets like India and Africa where PSTN connectivity was more common than broadband. Microsoft integrated core Kaizala features into Teams and shut down the Kaizala app on August 31, 2023. If your organisation was using Kaizala for field team communication, surveys, or job card management, that data is no longer accessible through Kaizala. The replacement is Microsoft Teams — particularly Teams for Frontline Workers which targets the same use case with walkie-talkie, shift management, and task publishing features.
Replace with: Microsoft Teams for Frontline Workers — walkie-talkie, task publishing, shift management, and Viva Connections for deskless employees
8. Access Web Apps (SharePoint-Hosted)
Access Web Apps (SharePoint)
Microsoft Access databases hosted in SharePoint Online
Retirement Date
April 2018 (SharePoint Online) — data deleted Jun 2018
Risk Level
Historic — if data wasn't exported in 2018, it is gone
Access Web Apps were a feature that let users publish Microsoft Access databases to SharePoint Online, with SharePoint rendering the forms and reports in a browser. Microsoft removed this feature from SharePoint Online in April 2018 and deleted associated databases in June 2018. This is the oldest entry on this list but it's still worth mentioning because we regularly encounter organisations that "lost data in 2018 when SharePoint changed something" — this was usually Access Web Apps. The data is irrecoverable if it wasn't exported at the time. Newer Microsoft Access desktop databases (.accdb) still work locally, but no cloud-hosted Access Web App feature exists today.
Replace with: Power Apps + Dataverse for app-with-database scenarios, or SharePoint Lists for simpler structured data needs
What to Do With This Information
Reading a list like this is useful. Acting on it is the point. Here are the three concrete things any Microsoft 365 admin should do after reading this:
- Run a tenant audit for the top 3 risks. Check for active InfoPath form libraries (search your SharePoint farm or Online tenant for .xsn files). Check for SharePoint Designer workflows that are still listed as active in workflow history. Check for SharePoint Add-ins in your App Catalog that are still deployed to sites.
- Check the Microsoft 365 Message Centre. Filter by "Retirements" and "Deprecations" — this is where Microsoft announces upcoming end-of-support dates. Set a calendar reminder to read it monthly. Most retirement surprises are avoidable with two to three months of advance notice.
- Prioritise by active usage. Retired tools that nobody is actively using are cosmetic problems. Retired tools with active user-facing functionality are operational risks. Start with the ones people use daily.
SharePoint Server 2019 mainstream support ends October 14, 2025 (already past) with extended support running until October 14, 2028. If you're running SharePoint on-premises on 2019, you're now in extended support — security patches only. SharePoint Server Subscription Edition (SSSE) is the current on-premises version; if you're planning an on-premises-to-cloud migration, the window before extended support ends is the time to plan it.
The 2026 Microsoft Retirement List — Key Takeaways
InfoPath and SharePoint Designer both ended in early 2026. If they're on managed corporate devices, remove them — running unsupported software is a compliance finding that auditors look for specifically.
SharePoint 2013 Workflows silently stopped running in SharePoint Online in November 2024. If a business process unexpectedly broke around that time, check whether it was driven by a 2013 workflow.
SharePoint Add-ins were removed from SharePoint Online in April 2026. Any Add-in still deployed to a SharePoint site stopped loading. Check your App Catalog for deployed Add-ins and plan SPFx replacements.
The pattern is consistent: Microsoft retires tools, replaces them with Power Platform equivalents. InfoPath → Power Apps. SharePoint Designer → Power Automate. Add-ins → SPFx. The replacement tools are better in every measurable way.
Monitoring the M365 Message Centre prevents surprises. Every retirement on this list was announced 12–24 months in advance. The organisations that got caught had the information available — they just weren't reading it.