Skip to main content

Microsoft 365: Upcoming Changes

Retirements

Aug 15- Classic Stream Retirement

As part of the Classic Stream retirement process, users will no longer be able to create new Stream (Classic) web parts. This change is a step towards the complete retirement of Classic Stream.

 You can start to use Stream in SharePoint

Functionality Changes:

Late Aug 2023- Microsoft 365 Apps: Encryption Algorithm Changes to AES256-CBC for Encrypting Emails and Files

Microsoft 365 Apps, Exchange Online, and SharePoint Online will use AES256 in cipher block chaining (CBC) mode as the default encryption method for emails and documents when using Microsoft Purview Information Protection.

New Features:

Early-Sep 2023- Discover and Co-author Documents Labeled with User-defined Permissions.

SharePoint and OneDrive will support discovery and coauthoring of files labeled with user-defined permissions. These files can be easily accessed, edited, co-authored, and benefit from the AutoSave feature in Word, Excel, and PowerPoint apps across all platforms.

Mid Sep 2023 – Twitter Web Part Retirement

Due to a change in Twitter’s terms of use for third-party access, the Twitter web part in SharePoint in Microsoft 365 will no longer be supported. Users may see error messages in pages that have Twitter web part.

SharePoint administrators can remove the Twitter web part from their SharePoint pages via the page authoring.

Sep 15, 2023- Disable Video Upload to Stream (Classic)

As part of Classic Stream retirement, you can’t upload video to Stream (Classic)

You can start to use Stream in SharePoint

Deprecations

Jan 2024- Wiki Retirement in Teams Channels

Wikis tab and wiki App wouldn’t be able to accessible in Teams and users wouldn’t be able to export.      

Your data is accessible from SharePoint as per retention policy even after Wiki is deprecated. You can download wiki content from SharePoint.


Apr 02, 2024- SharePoint 2013 Workflow Retirement   

Starting April 2nd, 2024, SharePoint 2013 workflows will be turned off for newly created tenants.  Starting April 2nd, 2026, SharePoint 2013 workflows will no longer be supported for existing tenants.

 

Apr 02, 2026- SharePoint 2013 Workflow Retirement

SharePoint 2013 workflows will no longer be supported.

You can move to Power Automate or other supported solutions.

July 14, 2026- InfoPath 2013 Client and InfoPath Forms Services in SharePoint Online will be Retired.

InfoPath Client 2013 will reach the end of its extended support period on July 14, 2026, and to keep an aligned experience across Microsoft products, InfoPath Forms Service will be retired from SharePoint Online.

To understand the usage of InfoPath within your organization, you can utilize the Microsoft 365 Assessment tool to scan your tenant and analyze InfoPath usage. If you are currently using InfoPath, you can initiate the migration process to modern alternatives such as Power Apps, Power Automate, or Forms.


Hope this helps!
Keyur Pandya

Comments

Popular posts from this blog

Business Data Connectivity

I came to a requirement wherein I was supposed to get data from an 3 rd party portal using API’s and then bring them to SharePoint server. The first approach that I finalized was just to make BDC solution that will get data from 3 rd party portal and will deploy it to SharePoint. How to Create BDC solution in SharePoint? I found below link that is having really great description about hot to create and deploy the BDC solution to SharePoint. http://www.c-sharpcorner.com/uploadfile/hung123/creating-business-data-connectivity-service-using-visual-studio-2010/ After creating an POC I came to know that BDC model cannot be deployed on Multi tenant farm. So what can be done next? After some amount of googling I came to know that we can create BDC solution using WCF services also. So I created a WCF service solution that acted as a wrapper that used to fetch data from the portal. We can them publish that service to IIS or Server and use the servic...

OneDrive Sharing Report: A Comprehensive Guide

OneDrive Sharing Report Managing and monitoring the sharing permissions of files stored in OneDrive can be a critical task for organizations. This guide provides a step-by-step walkthrough of how to create an Azure AD application with specific permissions, generate a client secret, and use a PowerShell script to retrieve and report the sharing permissions of OneDrive files. By following these steps, you will be able to audit and control file sharing across your organization, ensuring security and compliance. Step 1: Creating an Azure AD Application To get started, you'll need to create an Azure AD application that will allow you to interact with the Microsoft Graph API and retrieve information about users' OneDrive files and sharing settings. Specifically, you need to set the following permissions: Directory.Read.All Directory.ReadWrite.All Files.Read.All ...

SharePoint Server continuously prompting for Credentials

Sometimes it is the case when your SharePoint server keeps on prompting for credentials. After some amount of googling and going through some reliable blogs I found following solution. Open Run Type “regedit”.                                                                  In the registry window left panel find HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > LSA                                                                                                                      Now right clic...