Microsoft SharePoint (on-premises) FAQs

When configuring SharePoint 2013 or SharePoint 2016 web applications to use Okta authentication, do I have to run a script to convert the user accounts in SharePoint to Okta-formatted claims?

Yes, that is required if you want to keep the same permissions previously assigned to Windows accounts. Okta doesn't provide this script because the structure of the Okta ID claim doesn't map easily from the structure of the NTLM ID claim.

Does Okta support SharePoint 2010?

No. Okta supports SharePoint 2013, 2016, 2019, and SharePoint Subscription Edition (SE).

When browsing to a SharePoint web application with both NTLM and Okta authentication enabled, do users see a prompt to choose an authentication method?

Yes, by default.

Does Okta support SharePoint Server Subscription Edition (SE)?

Yes. Okta supports SharePoint SE through the SharePoint (on-premises) app with Okta claims provider agent version.

Do I need to migrate to a new farm to use SharePoint SE with Okta?

Yes. SharePoint SE requires a new farm using Microsoft's database-attach upgrade. There's no in-place upgrade path from SharePoint 2016 or 2019. After migrating, reconfigure the Okta integration on the new farm, including the trusted identity provider and the Okta claims provider agent. See Microsoft documentation for the migration steps.

Does migrating to SharePoint SE cause downtime?

Expect some downtime. During Microsoft's migration process, the existing farm becomes read-only while Microsoft builds the new SE farm, so write access pauses. Reconnecting Okta happens as part of standing up the new farm and doesn't add significant downtime.