​The Cloud Connector for Microsoft Office 365 and SharePoint connects almost any on-premise data source, e.g. ODBC, OLEDB, OData, Microsoft .NET based providers, Files content (Excel, XML, CSV), File shares, SQL databases like SQL Server, Oracle, MySQL, IBM DB2, IBM AS/400, IBM Informix, Notes, SharePoint, Exchange, Active Directory, Navision, SAP, PowerShell and many more directly to native SharePoint lists and libraries in the Microsoft Office 365 cloud - or any other Microsoft SharePoint on-premise installation - in just minutes without any programming. The step-by-step intro below is about connecting to SQL Server.

For any questions please use the FAQ Web Form or contact [email protected] directly.

Office 365: How to sync external SQL data with native SharePoint lists?

Integrating external SQL data sources (e.g. from SQL Server, Oracle, DB2, Informix, MySQL) with native SharePoint lists (e.g. news, contacts, tasks or custom lists) in Office 365, SharePoint Online or SharePoint 2010/13/16 can close some gaps using Microsoft SharePoint, on-premise or in the cloud. Please note: It's not only about displaying external SQL data - it's about full integration with search, lookups, change notifications, workflows, enterprise metadata, attachments etc.

This FAQ gives a step-by-step example with MS SQL how to do this. It works in the same way for any other database. You will find specific connection strings here.

Prepare your external SQL data source to integrate with Office 365

Let's take a sample SQL table, the well-known Northwind product catalog in SQL Server.

Fig.: The screen shows a sample SQL table to connect with a native SharePoint list.

Please note:

  • You can use existing tables or views, or create direct queries in the Cloud Connector.
  • The table should have a primary key defined, one or more unique fields. If not, you can create, e.g. using a GUID or counter (depending on features of your database system).

Setup your SQL to SharePoint connection

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

1. the connection (e.g. uni-directional or bi-directional, scheduling etc.),

2. the data source (your SQL database) and

3. the data destination (in SharePoint on-premise, SharePoint Online or Office 365. The list must be created manually before).

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

See here for sample connection settings:

Fig.: Sample SQL to Office 365 bi-directional connection.

Please note:

  • Bi-directional connections require appropriate access rights on database. Use uni-directional connections if you want to push SQL data only to the cloud.
  • 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, and number of fields and records in SQL. Only changes are transferred later on.

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

Fig.: The pre-installed SQL Provider is used to connect to the data source with a connection string.

Please note:

  • Select the SQL Provider that fits to your database. If it's not in list, it must be installed. Take care about 64-Bit and 32-Bit. The Cloud Connector can run in both modes, but it can connect only to those providers, that fits.
  • Enter a valid connection string for your database system. See www.connectionstrings.com to know.
  • The provider offers the possibility to enter direct queries, depending on database system. Select as few fields as required to increase performance.
  • For most systems you can use aliases in field names to fit to your SharePoint Online list, e.g. Select Productname as Title from products.
  • Use the data preview to check out the result of your query.
  • For most systems a "primary key" is set automatically. 
  • Please verify all settings before save.

Next you have to define your data destination:

Fig.: Data destination sample, a list "Products" in the Office 365 cloud.

Please note

  • Use the Layer2 SharePoint CSOM Provider to connect to SharePoint on-premise, SharePoint Online or Office 365.
  • You have to create the destination list manually with all columns required to host your query data.
  • Read more about connection strings to connect to Office 365, SharePoint Online or SharePoint on-premise here. Please note that you can connect to any other type of data destination, e.g. to other SQL databases.
  • There is no need to enter a primary key, the provider automatically uses the SharePoint item ID.

As a last step you have to setup the column / field mapping. You can use the auto-mapping feature (by field / column names) or map manually.

Fig.: Sample field / column mapping of data source and data destination.

  • Please note the mapping of ProductName to Title, as SharePoint required a Title field.
  • In this case we have included the SourceID to have a clear reference to the original record.
    That is not a requirement, but advised as best practice.
  • Please note the difference in data types. The Cloud Connector tries to match as close as possible.

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 nodes. You can take a look in your cloud list to see how it goes on.

Manage your SQL data in the Office 365 SharePoint list

​Now take a look at your list. All items are in there, after running the connection. You can hide the Source ID from you, if not required.

Fig.: Sample data destination in the Office 365 cloud.



Fig.: Sample data destination in Microsoft SharePoint 2013 / Office 365.

Please note:

  • Changed items are transferred with the next scheduled update. That means, you can setup change notifications per-email or workflows in the cloud without any restrictions.
  • You can add additional "SharePoint only" data, e.g. attachments or managed metadata. It will be kept while items are updated (via primary key).
  • You can do anything you can generally do with a native SharePoint list - without any restrictions (e.g. search).
  • Don't forget to setup the scheduled background update, to keep data current in connection settings, e.g. with scheduled updates every hour or daily.

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 on-premise after registration here.
Share this site on Xing
Share this site on Google+
Share this site on LinkedIn

We are very happy with the Layer2 product. It synchronises our Microsoft Office 365 SharePoint Online data perfectly to our onsite Microsoft SQL Server 2008 R2 database.


 Download & Evaluation

Please register now to receive your free personal download link via email to your valid company email address.
Yes, I accept the licensing terms and conditions
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.