Skip to main content
Nintex Community Menu Bar

You may start to see a notice when accessing your K2 for SharePoint integration in a SharePoint Online list or library. This notice states that SharePoint add-ins will be retired for SharePoint in Microsoft 365 in April 2026. Rest assured, our developers are hard at work and have already made strides in keeping your SharePoint Online integration working with your Nintex Automation (fka K2 Five) and K2 Cloud environments.

With the 5.7 release earlier this year, new installs that integrate with SharePoint Online will use the new SharePoint Framework (SPFx) integration path. This includes a new way to manage your SharePoint Online integration in the Management site, and has updated the integration points per Microsoft’s guidance. 

What about all our existing SharePoint integrations that use the add-in?

The team is currently working on a migration tool, to help you move your existing add-in based integrations for forms and workflows to the new SPFx model. This will allow customers who have previously activated the add-in integration to move over to the new supported model. We are aiming to have this available in the middle of 2024, with plenty of time for you to migrate your solutions before Microsoft fully deprecates the add-in model in April 2026. You must be on 5.7 or greater. If you are on an older version, start planning your upgrades today so you are ready to migrate your SharePoint Online solutions.

Once we’ve got the migration tool ready, we will then release SPFx support for K2 Cloud environments as well. As always, we’ll have full documentation guides available to help you move your SharePoint Online solutions. 

What if I’m using SharePoint on-premises?

If you are a Nintex Automation (K2 Five) customer and have integrated with SharePoint on-premises servers, nothing will change. All your solutions will continue to work. Microsoft is only deprecating the add-in model for SharePoint in Microsoft 365 (SharePoint Online).

 

As we get closer to releasing the migration tool, watch for more information to be posted here. And as always, if you have any questions, reach out to your Nintex account representative. 

Hi 

Can you confirm if it is only “app-i-fied” forms/views that are predominantly required to be migrated to SPFx equivalents, and not the smart objects tied to SharePoint constructs, e.g list/library data.

Thanks

Sheldon


Correct, we are migrating from the SharePoint Remote Event Receivers to Webhooks (for starting workflows based on SharePoint events) and the Forms URL (for displaying SmartForms as item or list views within SharePoint). All SmartObjects that are currently based on SharePoint lists or libraries go through the CSOM API which is not being deprecated. 


Thank you for the reply, Codi!


Any time!


Reply