Office 365 & Access Integration

Microsoft Office Access database data can be integrated and synchronized codeless with 100+ external systems and applications, on premises or in the cloud, using the Layer2 Cloud Connector, for example with Microsoft Office 365, SharePoint, Dynamics, Exchange and Azure. Please take a look here for supported systems and applications.​​​​


Integrate Azure  and Office 365

Features and Benefits of Microsoft Access Data Integration


​Integrating Microsoft Access data sets with other systems and applications via the Layer2 Cloud Connector has the following features and benefits:



  • Connect and sync your Microsoft Access data with 100+ other data sources codeless: The synchronization runs as a Windows service in background keeping the data up-to-date at both sides.
  • High speed of implementation: No programming required. Predefined sample connection templates included. Setup in a few minutes guided by wizards. Remote setup support if required (30 minutes free).
  • Low risk in project: No installation or customizing for the data source and the data destination required. Just install the connector on a computer in your network, in the cloud, or even your laptop. You don't need your IT to approve and install any specific SharePoint or Dynamics app. Read or write access rights to lists or libraries are enough.
  • Fully compatible with 3rd-party data providers: Data providers of application vendors (e.g. Oracle, MySQL, IBM), 3rd-party data providers (e.g. from CDATA), or included Layer2 data providers can be used to connect to 100+ data sources.
  • One-way and two-way connections supported: If provided by driver. Several options are built in to solve possible replication conflicts. Flexible sync options.
  • 100% compatible with all Office 365, OneDrive and SharePoint editions and plans: Including on-premises, remotely hosted, sandboxed, (e.g. Microsoft SharePoint Online / Microsoft Office 365 (ALL plans) or OneDrive for Business (1TB/User)). Uses the CSOM Web Services API model for sync with SharePoint. Several authentication methods supported, e.g. Windows Live, ADFS federated (corporate or organizational account). MFA (multi-factor authentication) via app password supported.
  • Highest Security: Connection via secure web services (SSL). Disconnected systems: A connection is only required for data sync– not for list or library usage. Users do not have direct access to external corporate data sources. You don't have to open your network for the Internet. The application runs where your data resides today - on a server or client inside your corporate network. No data is exposed to 3rd-parties or clouds.
  • Highest performance: Can manage very large data sets, lists and libraries. No 5,000 items limit. Can scale-out to multiple servers or to the Microsoft Azure Cloud, if required.
  • Virtually any data sources supported: ODBC, OLEDB, OData, SOAP, Microsoft .NET based providers, Files (Excel, XML, CSV, Text), RSS / XML feeds, SQL databases like MS SQLSQL Azure, Oracle, MySQL, IBM DB2, IBM AS/400, IBM Informix; Notes, SharePoint, Office 365 (lists and libraries), local file systemcloud-based file storesExchangeActive DirectoryDynamics NAV/CRM, Navision, SAP, and many more. More complex data sources, REST-based web services, custom COM, or .NET objects can be connected using 3rd-party add-ons. Cloud-to-cloud connections, e.g. to salesforce.comTwitter, Facebook, Google, Amazon, BOX.NET and others are also supported.
  • Layer2 CSOM Data Provider included: You can connect and sync your Capsule CRM data with SharePoint lists and libraries on-premise or in the Office 365 / OneDrive for Business cloud.
  • Layer2 OData Data Provider included: You can connect your Capsule CRM data to all OData sources, e.g. Microsoft CRM/ERP or SAP via NetWeaver.
  • Layer2 XML Data Provider included: You can connect your Capsule CRM data to any XML-based files and web requests, and filter results by using XPath query language.
  • Layer2 RSS Data Provider included: Please note that this provider is also included as sample source code to build your own provider.
  • Layer2 Exchange Data Provider included: You can sync Capsule CRM data like contacts, tasks, calendar events, notes, and email to Exchange using Exchange Web Services (EWS). Exchange 2007, 2010, and 2013 are supported as well as Exchange Online. Shared & Site Mailboxes supported.
  • Layer2 SOAP Web Services Provider included: Connect Capsule CRM to to SOAP-based web services codeless with flexible parameters.
  • Very flexible sync options: Uni- and bi-directional sync are supported. Start a specific connection sync scheduled in background (Windows Service) or on demand (e.g. by command line). Sync all data or pre-selected subsets only. Select source and target folders, make use of additional no-delete, no-insert, no-update options.
  • Data type conversion included: Sync Access data with SharePoint links, lookups, managed metadata, and more with advanced options.


  • Process integration: Raise change notifications and start workflows in the cloud, triggered on external data changes. Find your external data changes in Delve via Office Graph. All features of native SharePoint lists and libraries are supported, e.g. views, sorting, filtering, grouping, search, mobile and offline access, social features like tagging and enterprise metadata, RSS feeds, change notifications per email, or workflows in the cloud on external data change. You can also add your own business logic.
  • Flexible logging and alerts: You can log to files, databases, and Windows Event Log via NLOG.
  • Free Shareware Edition: You can test the free Shareware Edition as long as you want or you can use in production with limited features. You can upgrade an evaluation / Shareware version to a licensed version at any time without new installation.
  • Flexible, cost-effective licensing: Personal or Professional Edition, depending on requirements. Licensing per installation (no user CALs, not bound to any connected system, just a one-time fee - no data volume-related costs). Easy to setup and maintain. Optional annual Software Assurance for free updates.

Microsoft Access Specific Configuration Settings


​In the Layer2 Cloud Connector the data source or destination entity must be configured as follows to connect to Microsoft Office Access.


Connection configuration sample for OLEDB Integration

Fig.: Sample data entity configuration to connect to Microsoft Office Access.


Please note the following about settings, features and possible issues.


  • Data Providers can be OLEDB (preferred) and ODBC (both included in package).
  • In both cases the Microsoft ACE OLEDB 12 provider must be installed. It must fit to the Layer2 Cloud Connector architecture installed (32- or 64-bit). More information here.
  • The data source path can be both, local (e.g. C:\databases\mydb.accdb) or on file share (e.g. \\myShare\databases\mydb.accdb). In both cases please make sure that the database can be accessed from current user context. The user context is the currently logged in user (in case of the Layer2 Cloud Connector Connection Manager is used) or the service account (in case of scheduled background updates).


Do you have any issues to connect? Please contact [email protected] for next steps.

Microsoft Access Data Integration - Known Issues and Workarounds


​We have found the following issues and workarounds for Microsoft Access data integration:


  • In many cases a local account is used for the Cloud Connector Windows Service with no access to attached file shares. You can change, if required to access Access databases not only locally, but also on file shares. if you have any issues, please start with a file on a local disk and go step-by-step.
  • You can use Access SQL to query, but only syntax that is supported by the Microsoft data provider.
  • Access primary key(s) are not automatically set. Enter your primary key (e.g. an Access counter field ID) to the data entity definition as a primary key. If not set, records are deleted and re-inserted with each sync.
  • Bi-directional sync is supported.
  • Please take care with table names that include a "-" sign like "customer-contacts". Looks like there are issues in some Microsoft data provider versions leading to errors on insert.

Specific Microsoft Access Integration Scenarios


​You will find more information about specific scenarios here:



Can't find what you are looking for? Please contact [email protected] for any help.


Learn more about similar solutions for data migration, backup, integration, and synchronization by vendor and topic.

Ready to go Next Steps?

Register for free download.

Keep your SharePoint in sync. Download and try today.

Questions? Contact us.

We are here to help. Contact us and our consulting will be happy to answer your questions.