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

Keyur Pandya

Labels

Labels:
Location: Vadodara, Gujarat, India

Comments

Post a Comment

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...
2 comments
Read more

Identity client runtime library (IDCRL) did not get a response from the login server.

Recently I was doing some testing with a background PowerShell and encountered a weird error. “Identity client runtime library (IDCRL) did not get a response from the login server”. The error that you might encounter while working with PowerShell. This error is very misleading when it comes to identifying what could go wrong. After doing quite a good amount of research below are the probable causes for the error. Invalid Credentials MFA (Multi-Factor Authentication) Manage security defaults. Solutions Invalid Credentials Check if your credentials are wrong. Especially if you are using variables. MFA (Multi-Factor Authentication) Check if MFA is enabled on the account which you are using. These only affect you badly if you are developing PowerShell for a background Job. Go to Microsoft 365 admin center Users -> Active users -> Select the user -> Manage multifactor authentication -> Select the user -> Disable multi-factor authentication. M...
2 comments
Read more

Copying Footers Between SharePoint Sites Using PnP PowerShell

Recently, I have been extensively working with SharePoint and the Patterns and Practices (PnP) PowerShell module. PnP has significantly simplified various tasks by providing easy-to-use command sets and thorough documentation. One particular task that PnP has made straightforward is copying a footer from one SharePoint site to another. This process can be achieved with just a few commands. Why Use PnP PowerShell? PnP PowerShell is a set of cmdlets designed to work with SharePoint Online and SharePoint on-premises. It simplifies the management and automation of common tasks and provides commands for nearly every aspect of SharePoint administration. The PnP module is especially useful for tasks that would otherwise require complex scripting or manual intervention. Copying a Footer with PnP PowerShell To copy a footer from one SharePoint site to another, follow these steps. This process involves exporting the footer template from the source site in XML format and...
Post a Comment
Read more