How to connect Microsoft To-Do with SharePoint

This "how-to-connect" documentation will explain the initial configuration of an example connection from Microsoft To-Do to a SharePoint Online List in Office 365. We will be synchronizing data stored in Microsoft To-Do.

This guide presupposes that you have installed the Layer2 Cloud Connector and that you are familiar with its basic functionality. The Layer2 Cloud Connector User Documentation will provide you with all necessary information.

Contents

1. Configuring Microsoft To-Do

2. Configuring the Layer2 Cloud Connector

2.1 Creating a new connection

2.2 Configuring the Data Entity 1

2.3 Configuring the Data Entity 2

2.4 Running your connection

3. Hints and known issues

3.1 Connection direction

3.2 Data model

1. Configuring Microsoft To-Do

In order to connect to Microsoft To-Do, you are going to need the server address where your Exchange is running in and a username with access to the Exchange with the password. Ask your administrator for this information.

2. Configuring the Layer2 Cloud Connector

2.1. Creating a new connection

Create a new connection by using the Create New Connection option in the Actions pane (right-hand side). The new connection will appear at the bottom of the Connection Manager List (left-hand side). Click on your newly created connection to open the connection configuration settings.

Choose a meaningful name for your connection and replace the current "New Connection" Connection Title with it.

Connections to Microsoft To-Do can be bi-directional. An initial connection should always be uni-directional to assure that both data entities are identical before switching to bi-directional. Therefore, choose Left to Right as Direction. You can change this setting after your initial synchronization finished successfully.

2.2. Configuring the Data Entity 1

We will now set up our Data Entities. Go to the data entity “Data Entity 1” to open the configuration settings.

Choose a Data Entity Title. It is recommended to give your entities meaningful names to maintain an overview when you decide to set up multiple connections.

Select the Data Provider for Exchange from the data provider list. You can search for Exchange by typing into the selection box.

For the Connection String, we need the information mentioned in step 1. You can copy the below connection string and adjust it to match your gathered information. Use the Verify Connection String option to evaluate if the provided connection string is valid.

Server=https://outlook.office365.com/EWS/Exchange.asmx;Usales@layer2.pro;" this property should describe the user you wish to connect to SharePoint to. 
 
Enter the password that belongs to the user account used in the connection string into the Password field. Save your changes by using the right-hand pane option Save Changes.
 
 
In the next step, we will configure our mapping settings. Click on the Mappings option on the left-hand pane. If your fields from SharePoint are named identical to the fields from your source system, the Enable Auto Mapping option will match those columns. Disabling this option allows you to match your columns as needed. We enabled auto-mapping in our setup. Save your changes by using the right-hand pane option Save Changes. 
 
 
2.4. Running your connection
To run your connection switch back to the main connection configuration node and use the Run Now Button located on the bottom of the setup page. The Run Synchronization Toolbox will also display the synchronization process. 
 
 
Below is a data preview of the information we have access in our source entity:
 
 
This will be the result in our SharePoint Online list after our initial successful synchronization:
 
If you want to use a bi-directional synchronization, you can now switch your connection direction after our first initial synchronization run finished successfully. See section 3.1 for further information.

3. Hints and known issues
 
3.1. Connection direction
As far as tested, this connection supports uni-directional as well as bi-directional synchronizations. 
 
After adjusting the direction to bi-directional, you should check your Mappings settings again because some systems might include read-only columns that cannot be mapped directly.
 
 
We also recommend choosing a Conflict Resolution that matches your environment's needs. You can find out more about the different conflict resolutions in our Layer2 Cloud Connector User Documentation.
 
 
 
↑Top