Hybrid SharePoint 2016/2019 Environment
The following section discusses specific integration preparation steps required for a SharePoint 2016/2019 hybrid environment and product system prior to the installation of product and deployment of Nintex K2 for SharePoint 2016/2019.
It is increasingly common for organizations to have a mixture of SharePoint on-premises and SharePoint Online. A single product server can support both of these environments at the same time however there are some slight differences to the configuration if your SharePoint on-premises environment is setup in Hybrid mode. You can find more details on enabling Hybrid mode for SharePoint 2016/2019 in the Hybrid for SharePoint 2016/2019 TechNet article. Follow the steps in the SharePoint Server 2016/2019 Hybrid section below if this applies to your environment. If you are not configured for Hybrid authentication then the requirements are simply a combination of the two sections listed above for SharePoint on-premised and SharePoint Online.
SharePoint Server 2016/2019 Hybrid
In organizations with both SharePoint on-premises and SharePoint Online there is a configuration mode available to allow these two environments to work more closely together known as Hybrid mode. The excerpt below from the Hybrid for SharePoint 2016/2019 TechNet article describes the high level features of enabling Hybrid mode.
“A SharePoint Server hybrid environment enables trusted communications between SharePoint in Microsoft 365 and SharePoint Server. When you have established this trust framework, you can configure integrated functionality between services and features such as Search, Follow, and user profiles.”
When Nintex K2 for SharePoint is deployed in a SharePoint Server 2016/2019 hybrid environment, the deployment experience is a combination of on-premises and online experiences . The Nintex K2 for SharePoint app is deployed to the on-premises and online app catalogs. However, users across different labels (such as the product and AAD), even if they are the same physical user, are not the same user from an identity management perspective. It is important to be aware of this limitation, as it typically means that you will have two distinct sets of users. Even if they are the same users in each set, the system cannot equate them so it means that assigning tasks requires you to assign to the same users in each label, and users, when working with their worklists, see only the tasks for the identity they're currently logged in as.