​You can keep SharePoint or Office 365 list data and documents in sync cross site collections or even cross tenants via the Layer2 Cloud Connector. This could solve typical requirements such as connecting different SharePoint sites, site collections, SharePoint 2010/2013/2016 on-prem installations (local or hosted by providers), and on-premises sites to Office 365, e.g. to publish pre-selected items or documents from intranet to extranet. You can sync one-way, or even two-way. Documents in Office Groups are supported as well as in Microsoft Teams. For any questions please use the FAQ Web Form or contact [email protected] directly.

SharePoint Cross-Site Collection and Cross-Tenant Data and Document Synchronization

​It's fairly easy to build extranets for your clients, vendors or other partners with SharePoint Online or Office 365, e.g. for collaboration or mobile access. Compared to adding your partners securely to your internal infrastructure (e.g. Active Directory), a cloud-based extranet could be the better approach.

But take care about new data islands! You can easily connect some pre-selected parts of your locally existing data and documents with the new extranet in the cloud using the Layer2 Cloud Connector for Office 365 and SharePoint Online. The connector keeps the data and documents up-to-date automatically in background. It just needs a simple Windows Service to run on a local machine or in Azure. Note that syncing documents with an Extranet is just one example, there are much more use cases for this.

Prepare Your Intranet SharePoint Document Library as a Data Source for Publishing to Office 365

Perhaps you don't want to publish all your documents to the external cloud. You can use an additional field to mark documents for publishing to the cloud-based Extranet and create a view for this.  You don't want to publish all your documents to the external cloud. You can use an additional field to mark documents for publishing to the cloud-based Extranet and create a view for this. In our sample we use a view "ToExtranet" that only shows documents with the additional field "Extranet" = True.


Fig. Example showing documents in your local Intranet document library. An additional flag "Extranet" was added to mark some documents for transfer to external cloud, for example, all PDFs - but not the original PowerPoint files in that the example.


You can create a view to filter the documents to transfer.


Fig. The view uses a flag "Extranet" = True to filter documents for transfer to Extranet. 


Setup Your Intranet-to-Extranet Cloud Connection with the Cloud Connector

​With the Cloud Connector Connection Manager (a MMC snap-in) you have to setup:

1. The connection (e.g. uni-directional with overwrite, scheduling etc.),

2. The data source (your Intranet view ToExtranet), and

3. The data destination (in Extranet, the library must be created manually before).

You can use auto-mapping to connect the fields of both data entities or map fields manually.

See here for example connection settings:

Fig. Example of a Intranet-to-Extranet one-way connection.

Please note:

  • Bi-directional connections are supported as well, if required.
  • If Overwrite Destination is enabled, non-matching entries in the destination will be removed with initial sync.
  • Please enable scheduling later on, when all settings are verified and you have an idea of replication duration. Duration time depends on bandwidth, performance of source and destination, document size, and number of documents. Only changes are transferred.

Before running the connection, you have to define the data source and destination.

Fig. The CSOM Provider is used to connect to the data source, e.g. a SharePoint on-premises.

Please note:

  • The view "ToExtranet" is given as data source in connection string.
  • Windows authentication is used to connect to the Intranet.
  • You don't have to enter a primary key, SharePoint document IDs are used by default.
  • Please verify all settings before saving.
  • The data source could also be in the cloud. Cloud-to-Cloud connections are supported as well.

Next you have to define your data destination:

Fig. Data destination example with a library "Extranet" in the Office 365 cloud.

Please note:

No installation required on either side, source and destination. The Cloud Connector runs somewhere in your network as a Windows service, e.g. on any Windows Server or Client. Alternatively you can run it in your Microsoft Azure. No 3rd party cloud involved in the sync.

Last, set up and verify your Mappings between the source and destination. The easiest way is to click Enable Auto Mapping in the Mappings UI.

Fig. Example using the Auto Mapping feature.

If you wish to use custom mapping, disable Auto Mapping, and then you can add / remove fields using the green plus and red minus.

Please note:

  • In order to properly transfer files between the two sources, IsFolder and FileContent MUST be set! FileName and FilePath are also recommended.

If all settings are verified, please go to connection root and run the connection manually first. Please note that it could take some time to transfer all documents. You can take a look in your cloud library to see the progress.

See Your Selected Documents in the Office 365 Extranet

​Now take a look at your extranet. The pre-selected documents are in there, after running the connection.

Fig. Example data destination in the Office 365 cloud.

Please note:

  • Only the selected documents are transferred in case views are used.
  • Metadata, like date / time of creation or last modification can be transfered to the extranet, if required, by updating the field mapping.
  • The user mapping is more complicated. It would only work if the user information like "Created by or "Last modified by" also exists in extranet with the same tokens. If it does not (more likely), you can create another custom column for the purpose of storing the user name (e.g. "Originally created by") and map the fields to this column for information. You can also "translate" user tokens between source and destination using "Dynamic Columns" in C#.
  • Changed files are transferred only on update. That means, you can define change notifications per-email or workflows in SharePoint without any restrictions. 

Next steps: Download a FREE shareware edition of the Layer2 Cloud Connector

​You can download a free shareware edition of the Layer2 Cloud Connector for Office 365 and SharePoint after registration here.
Share this site on Xing
Share this site on Google+
Share this site on LinkedIn

"Extranets are easy to build with SharePoint Online & Office 365. To share some parts of your intranet with your external partners in the cloud, the Cloud Connector could help."

Frank Daske

Frank Daske

Business Development Manager
+49 (0) 40 28 41 12 - 30
[email protected]

Please note that the 011 exit code must be dialed first for all international calls made from the USA, Canada and Australia.

Related News

Layer2 now connects 100+ commonly used IT systems with Twitter via its Layer2 Cloud Connector

The Layer2 Cloud Connector is now able to connect Twitter to integrate data to a wide range of IT backend systems including Office 365, SharePoint, SQL, ERP/CRM.

New Microsoft Teams Connectors: Layer2 adds 100+ typically used backend systems

​The Layer2 Cloud Connector is now able to connect to Microsoft Teams to quickly integrate more than 100 IT backend systems including local SQL, ERP/CRM.
Related Downloads
PDF Image

Cloud Connector Instruction

Download this step-by-step instruction to connect and sync your corporate or cloud data sources bi-directional to any native SharePoint 2010/2013/2016 list or library, including Microsoft Office 365.
PDF Image

Feasibility Study: Connecting local SQL Server to SharePoint Online

The study compares different approaches for SharePoint Online data integration regarding performance, features, security and investment.
PDF Image

Flyer: Layer2 Partner Program

Partner with us as a software distributer, reseller or SharePoint, Office 365 or Azure service provider. We are offering a free Partner Program with up to 30% Discount, free NFR licenses etc. Please download for more.
PDF Image

Layer2 Case Study: Cloud Connector helps ChemWerth to integrate the Microsoft Office 365 Cloud

"The Cloud Connector’s interface is easy to understand and use. Anyone familiar with utilities in the Microsoft stack will be productive immediately. Our recommendation: The Layer2 Cloud Connector is a no brainer.”
NoDoc Image

Layer2 Cloud Connector PAD File

This XML-based PAD file offers a Layer2 Cloud Connector product description for resellers to download and publish.
PDF Image

Office 365: How to sync with MS Dynamics CRM

You can sync any CRM data with native lists in SharePoint on-prem or online to make it available offline with Outlook.
PDF Image

Office 365: How to sync with SAP?

You can connect SharePoint and Office 365 with SAP via NetWeaver and OData.
PDF Image

Office 365: How to sync your local file share?

When you are moving to the cloud, there are a lot of reasons to keep your local file system. But you don't have to miss the benefits of the cloud.
PDF Image

Product Flyer: Cloud Connector for Microsoft SharePoint & Office 365

Flyer with features, benefits & pricing info for download as PDF.
PDF Image

Product Flyer: SharePoint Online Local File Server Sync

You can centrally migrate, synchronize, or backup your local file server department shares and home drives very flexible with SharePoint Online to close known gaps and overcome limitations of the Microsoft OneDrive for Business client.
PDF Image

Solutions Flyer: Data Integration with SharePoint, Office 365 and 100+

FileMaker can be integrated with 100+ other sources codeless using the Layer2 Cloud Connector.
Related Links

Layer2 Cloud Connector Community Group @ LinkedIn

​Are you already @ LinkedIn? Please join the Cloud Connector Community Group to share your experience.

Microsoft Partner Story Book for Office 365 about Cloud Connector

​Know more about a Layer2 Cloud Connector customer reference at the Microsoft Office web site.

Purchase Layer2 Cloud Connector via ComponentSource

​ComponentSource has offices in the USA, UK and Japan supporting over 125,000+ Customers, in over 180 Countries. They are also an approved Federal Government supplier through the GSA Schedule.



Sign Up for Layer2 Product Newsletter

We keep you up-to-date about new Layer2 product releases, added features and fixed issues.