You have used the Synchronization Editor to set up a synchronization project for initial synchronization with SharePoint Online. You can use this synchronization project to load SharePoint Online site collections into the One Identity Manager database. If you manage sites, users and groups with One Identity Manager, the changes are provisioned to the SharePoint Online environment.
You must customize the synchronization configuration in order to compare the One Identity Manager database with the SharePoint Online regularly and to synchronize changes.
To specify which SharePoint Online objects and One Identity Manager database objects are included in the synchronization, edit the scope of the target system connection and the One Identity Manager database connection. To prevent data inconsistencies, define the same scope in both systems. If no scope is defined, all objects will be synchronized.
To synchronize additional schema properties, update the schema in the synchronization project. Include the schema extensions in the mapping.
Add your own schema types if you want to synchronize data, which does not have schema types in the connector schema. Include the schema extensions in the mapping.
For detailed information about configuring synchronization, see the One Identity Manager Target System Synchronization Reference Guide.
The synchronization project for initial synchronization provides a workflow for initial loading of
To create a synchronization configuration for synchronizing SharePoint Online
Open the synchronization project in the Synchronization Editor.
Creates a workflow with Target system as its synchronization direction.
Run a consistency check.
All the schema data (schema types and schema properties) of the target system schema and the One Identity Manager schema are available when you are editing a synchronization project. Only a part of this data is really needed for configuring synchronization. If a synchronization project is finished, the schema is compressed to remove unnecessary data from the synchronization project. This can speed up loading the synchronization project. Deleted schema data can be added to the synchronization configuration again at a later point.
If the target system schema or the One Identity Manager schema has changed, these changes must also be added to the synchronization configuration. Then the changes can be added to the schema property mapping.
To include schema data that have been deleted through compressing and schema modifications in the synchronization project, update each schema in the synchronization project. This may be necessary if:
A schema was changed by:
Changes to a target system schema
Customizations to the One Identity Manager schema
A One Identity Manager update migration
A schema in the synchronization project was shrunk by:
enabling the synchronization project
saving the synchronization project for the first time
compressing a schema
To update a system connection schema
Select the category Configuration | Target systems.
- OR -
Select the category Configuration | One Identity Manager connection.
Select the view General and click Update schema.
This reloads the schema data.
To edit a mapping
Select the category Mappings.
Select a mapping in the navigation view.
Opens the Mapping Editor. For more detailed information about mappings, see the One Identity Manager Target System Synchronization Reference Guide.
|NOTE: The synchronization is deactivated if the schema of an activated synchronization project is updated. Reactivate the synchronization project to synchronize.|
Memberships, for example, user accounts
Memberships are saved in the target system as an object property in list form
Memberships can be modified in either of the connected systems.
A provisioning workflow and provisioning processes are set up.
If a membership in One Identity Manager changes, the complete list of members is transferred to the target system by default. Memberships, previously added to the target system are removed by this; previously deleted memberships are added again.
To prevent this, provisioning can be configured such that only the modified membership is provisioned in the target system. The corresponding behavior is configured separately for each assignment table.
To allow separate provisioning of memberships
In the Manager, select SharePoint Online | Basic configuration data | Target system types.
Select SharePoint Online in the result list.
Select Configure tables for publishing.
Select the assignment tables for which you want to allow separate provisioning. Multi-select is possible.
This option can only be enabled for assignment tables that have a base table with XDateSubItem or CCC_XDateSubItem column.
Assignment tables that are grouped together in a virtual schema property in the mapping must be marked identically.
Click Enable merging.
For each assignment table labeled like this, the changes made in One Identity Manager are saved in a separate table. During modification provisioning, the members list in the target system is compared to the entries in this table. This means that only modified memberships are provisioned and the members list does not get entirely overwritten.
|NOTE: The complete members list is updated by synchronization. During this process, objects with changes but incomplete provisioning are not handled. These objects are logged in the synchronization log.|
For detailed information about provisioning memberships, see the One Identity Manager Target System Synchronization Reference Guide.