Bien Nguyen
Optimizely
Nov 10, 2026
visibility 19
star star star star star
(0 votes)

The SharePoint Connector for Optimizely CMS 11 is Now Open-Source

Hello everyone,

Today we are announcing that we have open-sourced Optimizely Connect for SharePoint, the connector that enables integration between Microsoft SharePoint and Optimizely CMS 11.

For years, this tool has helped organizations bridge the gap between their SharePoint document libraries and their Optimizely CMS-powered websites. It has enabled content teams to seamlessly synchronize documents, images, videos, and list items from SharePoint into the CMS asset system -- eliminating manual file transfers and keeping content in sync across platforms.

With the recent release of Optimizely CMS 13, our platform has taken a significant step forward. The SharePoint Connector was built for CMS 11 and has never been ported to CMS 12 or 13. Rather than let the project go dark, we believe the best path forward is to place it in the hands of the community that uses it. The connector has a mature codebase, a well-defined feature set, and a strong foundation for anyone looking to continue its development -- including a potential port to newer CMS versions.

As we transition stewardship to the community, two factors stand out:
  • There are customers that rely on the connector today to power their SharePoint-to-CMS content workflows.
  • The developer community has expressed interest in extending the connector -- whether that means adding support for new SharePoint APIs, customizing content mappings, or adapting the tool for their specific deployment scenarios.
This makes the connector an ideal candidate to continue life as a community-supported project.

What's in the box?

The connector provides a rich set of capabilities out of the box:
  • Document and media synchronization: Import files, images, and videos from SharePoint document libraries directly into the Optimizely CMS media system, preserving folder structures and metadata.
  • List item integration: Sync SharePoint list items into CMS content with configurable field mappings, supporting a variety of list types including document libraries, picture libraries, announcements, and contacts.
  • Modern authentication: Full support for Microsoft Entra ID (formerly Azure AD) OAuth 2.0, including both client secret and certificate-based authentication for SharePoint Online.
  • On-premises support: NTLM authentication for organizations running SharePoint Server on-premises.
  • Admin configuration UI: A built-in administration interface for configuring connections, selecting lists and views, mapping destination folders, and testing connectivity -- available in 12 languages.
  • Message-driven processing: An extensible, asynchronous architecture for content synchronization operations.

What happens next?

  • The source for the connector is now open and available at optimizely/sharepoint-connector. Fork the repository to add, update, or replace capabilities as it's relevant to your projects.
  • With this release, Optimizely's official contributions to the project come to an end. The connector will no longer receive updates or support from Optimizely.
  • The source will remain available to the community and free to use or modify as you see fit. We encourage anyone interested in porting the connector to CMS 12 or CMS 13 to fork the repository and take it forward.
We're excited to see what the community does with this project. Whether you're porting it to CMS 13, extending it to support the Microsoft Graph API, adding new content type mappings, or adapting it for a novel integration scenario -- the code is yours to build on.

Happy connecting!
Nov 10, 2026

Comments

error Please login to comment.
Latest blogs
From Zero to App Directory: Building an Optimizely SaaS CMS App with OCP

A hands-on guide to extending the SaaS CMS editor with Optimizely Connect Platform (OCP): a sidebar extension, a secure backend function, the CMS...

Chirag Khanna | Nov 9, 2026 |

A note on using async computed fields with Optimizely Graph

Computed fields can be async, but do they work smoothly with the Graph C# SDK?

Johan Kronberg | Nov 9, 2026 |

Visual Builder without Next.js, Part 2: The Routing Decision Travels, the Engine Contract Doubles

One content tree, two engines, one edge: a strangler for Astro and Next.js on CMS 13. The same routing decision in a Next.js proxy and in a...

Piotr | Nov 8, 2026 |