With the Cloud Connector Connection Manager (a MMC snap-in) you have to setup:
1. the connection (uni-directional in this case, scheduling etc.),
2. the data source (your Active Directory) and
3. the data destination (in SharePoint on-premise, SharePoint Online or Office 365. The list must be created manually before. Lets use a contact list in this case).
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 Active Directory to Office 365 uni-directional connection.
- Bi-directional connections are not supported by the Microsoft OLEDB ADSI provider used.
- 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 Microsoft ADSI Provider is used to connect to the data source with a connection string.
- Please select the OleDb Data Provider in this case and refer to ADSDSOObject later on.
- See here for more information about ADSI connection strings. Please verify the connection.
- Please note the page size parameter in connection string for longer lists. In some cases it must set for the AD as well to work as expected.
- See here for more about ADSI queries. A valid query can look like this:
SELECT displayname, title, name, objectSID, ADSPath, givenName, sn, cn, company, department, l, mail, telephoneNumber From 'LDAP://myserver.mydomain.lokal/OU=MyOU,OU=Users,OU=MySubOU,DC=MyDomain,DC=lokal' WHERE objectClass='user' AND objectCategory='Person'
Please verify the select statement. If there are any issues, please check your access rights first. Start with a very basic query and increase complexity step-by-step.
- Select as few fields as required to increase performance.
- Use the data preview to check out the result of your query.
- Include the unique ADSPath field in your query and use it as a "primary key".
- Please verify all settings before save.
Next you have to define your data destination:
Fig.: Data destination sample, a list "AD-Phonebook" in the Office 365 cloud.
- 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. Please use a contact list in this case to benefit from default fields and Office integration later on.
- 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 SQL databases, as well.
- 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 should map manually in this case because of the different field names in source and destination.
Fig.: Sample field / column mapping of data source and data destination.
- Please note the mapping of SN to Title, as a SharePoint contact list requires a Title field.
- 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.