SharePoint Feature Retirements and Deprecations: Everything Ending by 2026

SharePoint Feature Retirements and Deprecations: Everything Ending by 2026

Microsoft is accelerating its modernization of SharePoint and Microsoft 365 by retiring legacy technologies that were once central to classic SharePoint environments. Between 2025 and 2026, multiple long-standing features will reach end of support or be fully removed from Microsoft 365 and SharePoint Online.

The most significant retirements include:

• InfoPath Forms Services and the InfoPath 2013 client (end July 14 2026), ending browser-based form support.

• SharePoint Add-Ins and SharePoint 2013 workflows (April 2 2026), replaced by Power Automate and SharePoint Framework (SPFx).

• SharePoint Alerts (classic “Alert Me”), Secure Store Service, and Power BI list integration, all phased out by late 2025–mid 2026.

• On-premises products—SharePoint Server 2016/2019, Designer 2013, and Office Online Server—will also reach end of extended support by mid-to-late 2026.

These changes reflect Microsoft’s focus on modern, cloud-based, and low-code technologies: modern pages, Power Platform tools, and SPFx-based customizations.

The next few months mark a crucial transition period for organizations still relying on legacy SharePoint features. While many classic components will continue to function temporarily, Microsoft’s roadmap makes it clear that modernization is no longer optional — it’s essential for compatibility, security, and long-term sustainability.

To prepare:

1. Inventory all classic pages, InfoPath forms, workflows, and add-ins.

2. Prioritize migrations based on confirmed end dates (especially anything ending by mid-2026).

3. Adopt Power Apps, Power Automate, and SPFx for modern replacements.

4. Communicate and train users early, so change is smoother when retirements take effect.

By planning now, organizations can ensure a controlled, strategic modernization rather than a last-minute rush as these legacy services go dark in 2026.

Timeline (now → end of 2026)

2026-01 (rolling)

SharePoint Alerts (“Alert Me”)
What happens: Creation of new alerts turned off for all tenants.
Replacement: Use Power Automate / SharePoint rules / Teams notifications.
Reference: TECHCOMMUNITY.MICROSOFT.COM+1

2026-04-02

SharePoint 2013 Workflows (SharePoint Online)
What happens: Removed from existing tenants (already off for new tenants since 2024-04-02).
Replacement: Power Automate.
Reference: Microsoft Support+1

2026-06-30

SPFx Field Customizers (specific scenarios)
What happens: Microsoft signaled retirement by June 2026.
Replacement: Prefer Column JSON formatting / Power Apps.
Reference: voitanos.io

2026-07-14

InfoPath Forms Services (SharePoint Online)
What happens: Removed from SharePoint Online; InfoPath browser forms stop working.
Replacement: Power Apps / other modern form solutions.
Reference: TECHCOMMUNITY.MICROSOFT.COM

2026-07-14

InfoPath 2013 client
What happens: Product reaches end of extended support.
Reference: Microsoft Learn

2026-07-14

SharePoint Server 2016 (on-prem)
What happens: End of support (no updates/support).
Replacement: Migrate to SPSE / M365.
Reference: Microsoft Learn

2026-07-14

SharePoint Server 2019 (on-prem)
What happens: End of extended support (Mainstream ended 2024-01-09).
Replacement: Migrate to SPSE / M365.
Reference: Microsoft Learn

2026-07-14

SharePoint 2010 workflows (SP Server SE note)
What happens: SP2010 workflows no longer supported in SPSE after this date.
Replacement: 2013 workflows / Power Automate (per scenario).
Reference: Microsoft Learn

2026-07-14

SharePoint Designer 2013
What happens: End of extended support.
Replacement: Use Power Automate/Power Apps; Designer is legacy.
Reference: Microsoft Learn

2026-07 (Month)

SharePoint Alerts (classic)
What happens: Microsoft removes ability to use Alerts; existing alerts stop working.
Replacement: Power Automate / SharePoint rules.
Reference: Microsoft Support+1

SharePoint List Column Styling 102

Column Styling 101 only shows you a single option for colour formatting.

For this example, I want it to only be red if the date is past AND the item is not competed.

So like before you need to open the column formatting properties.

• Click the drop-down arrow next to the column you want to see.
• Select “Column settings”
• Click “Format this column”

• This opens the column formatting properties
• Untick “Format dates” and Select “Conditional formatting”

• Then click “Manage rules”

• Now we add our new Rules:
• Click “Show all values as”

• Then add the new rules:

• Click “Save”, and back
• Add all 3 conditional rules

• The view will now not show the colour if the task is completed

SharePoint List Column Styling 101

 If you want to see the format:

1. Click the drop-down arrow next to the column you want to see.
2. Select “Column settings”
3. Click “Format this column”

4. This opens the column formatting properties
5. The “Edit styles”

6. This shows you the format

 

 

SharePoint Classic Video Player

SharePoint Classic Video Player taken directly off backend SharePoint Classic, so it just works.

Add this to a script editor web part

Here is the code:

The yellow is the link location to the video

The pink in the link location to the preview image of the video

<div class="mediaPlayerContainer"><video class="mediaPlayerVideoObject" id="FilePreviewID-1-MediaPlayer" onloadstart="" poster="/_layouts/15/images/videopreview.png" width="350px" height="197px" data-init="1" controls=""><source src=https://mysite.sharepoint.com/SiteAssets/video.mp4 data-label="undefined" type="video/mp4"><a href="javascript:Silverlight.getSilverlight(&quot;2.0&quot;);" style="text-decoration: none;"><img src=http://go2.microsoft.com/fwlink/?LinkID=108181 alt="Get Microsoft Silverlight" style="border-style: none" data-themekey="#"></a></video><div class="mediaPlayerFullScreenEsc"><span></span></div><div class="mediaPlayerInitialPlayButton" style="display: none;"><a href="javascript:;" title="Play"><span></span></a></div><img src="/_layouts/15/images/hig_progcircle_loading24.gif" class="mediaPlayerLoadingIndicator" title="Buffering... Please wait" alt="Buffering... Please wait" data-themekey="#" style="display: none;"></div>

2019 Modern SharePoint sites

I finally found the link (and the time) to create the new Modern SharePoint site templates. Woohoo! I just wanted to share with you the options and how they look.

There are 2 options:

• Communication Site
• Team Site

1.       The Communication Site has 3 options:

1.       Topic

2.       Showcase

3.       Blank

Looks funky and the first two option look quick different from each other. You can't create Communication subsite, so if you do create some kind of team site, the look and feel (and especially the navigation) doesn't match. 

2.       The Teams Site has only 1 options

This Team site is not to be confuse the Team site (OG), this is the Modern Team site. “Modern” being the new styling word to describe this new look and feel.

I personally don’t like this one so much, the global navigation menu isn’t there, and if you force it on, it looks bad. Have a look, and you decide. You are welcome to make changes, these are just for use to play with.

Screenshots

Communication Topic Site

Communication Showcase Site

Communication Blank Site

Team Site

Enjoy J

Mapped crawled properties for "URL"

Getting the right URL information from the "URL" column within your SharePoint Content Search Web Part (CSWP). This would be the OOTB (Out of the Box) SharePoint "URL" column.

Mapped crawled properties for "URL"

ows_URL

results = {URL}
example = http://www.google.com

ows_q_URLH_URL

results = {URL}, {Description}
example = http://www.google.com, Google

RefinableString for Title

Just had some fun and games with the SharePoint Content Search Web Part (CSWP). I create some content, list and pages, all with there own content type. I was able to view the column "Title" content in the CSWP display, but not able to Sort by "Title" or have it as a Refiner.

So...
I used one of the RefinableString Managed Property. It was tricky to figured out which Mapped crawled property was the correct "Title". These are the ones that worked for me, for my current project.

Mapped crawled property for:
List - Basic:displaytitle
Page - ows_Title