Identity Manager 8.2.1 - Administration Guide for Connecting to Microsoft Teams

Related topics

• Users and permissions for synchronizing with Microsoft Teams

• Setting up the synchronization server for Microsoft Teams

To set up an initial synchronization project for Microsoft Teams

1. Start the Launchpad and log in on the One Identity Manager database.

   NOTE: If synchronization is run by an application server, connect the database through the application server.

2. Select the Target system type Azure Active Directory entry and click Start.

   This starts the Synchronization Editor's project wizard.

3. On the System access page, specify how One Identity Manager can access the target system.

   • If access is possible from the workstation on which you started the Synchronization Editor, do not change any settings.

   • If access is not possible from the workstation on which you started the Synchronization Editor, you can set up a remote connection.

     Enable the Connect using remote connection server option and select the server to be used for the connection under Job server.

4. On the Azure Active Directory tenant page, enter the following information:

   • Deployment: Select your cloud deployment. Select from Microsoft Graph global service or Microsoft Cloud for US Government (L4) .

   • Application ID: Enter the application ID. The application ID was generated when registering the One Identity Manager application in the Azure Active Directory tenant.

   • Login domain: Enter the base domain or a verified domain of your Azure Active Directory tenant.

5. On the Authentication page, select the type of login and enter the required login data. The information is required depends on how the One Identity Manager application is registered with the Azure Active Directory tenant.

   • If you have integrated One Identity Manager as a mobile device and desktop application in your Azure Active Directory tenant, select Authenticate as mobile device or desktop application and enter the user account and password for logging in.

   • If you have integrated One Identity Manager as a web application in your Azure Active Directory tenant, select the option Authenticate as web application and enter the value in the secret.

     The secret was generated when the One Identity Manager application was registered with the Azure Active Directory tenant.

6. On the last page of the system connection wizard, you can save the connection data.

   • Set the Save connection locally option to save the connection data. This can be reused when you set up other synchronization projects.

   • Click Finish, to end the system connection wizard and return to the project wizard.

7. On the One Identity Manager Connection tab, test the data for connecting to the One Identity Manager database. The data is loaded from the connected database. Reenter the password.

   NOTE:

   • If you use an unencrypted One Identity Manager database and have not yet saved any synchronization projects to the database, you need to enter all connection data again.

   • This page is not shown if a synchronization project already exists.

8. The wizard loads the target system schema. This may take a few minutes depending on the type of target system access and the size of the target system.

9. On the Select project template page, select the Microsoft Teams (via Azure Active Directory) template.

10. On the Restrict target system access page, specify how system access should work. You have the following options: Read-only access to target system.

    Table 4: Specify target system access

    Option	Meaning
    	Specifies that a synchronization workflow is only to be set up for the initial loading of the target system into the One Identity Manager database. The synchronization workflow has the following characteristics: Synchronization is in the direction of One Identity Manager. Processing methods in the synchronization steps are only defined for synchronization in the direction of One Identity Manager.
    Read/write access to target system. Provisioning available.	Specifies whether a provisioning workflow is set up in addition to the synchronization workflow for the initial loading of the target system. The provisioning workflow displays the following characteristics: Synchronization is in the direction of the Target system. Processing methods are only defined in the synchronization steps for synchronization in the direction of the Target system. Synchronization steps are only created for such schema classes whose schema types have write access.

11. On the Synchronization server page, select the synchronization server to run the synchronization.

    If the synchronization server is not declared as a Job server in the One Identity Manager database yet, you can add a new Job server.

    1. Click to add a new Job server.

    2. Enter a name for the Job server and the full server name conforming to DNS syntax.

    3. Click OK.

       The synchronization server is declared as Job server for the target system in the One Identity Manager database.

    4. NOTE: After you save the synchronization project, ensure that this server is set up as a synchronization server.

12. To close the project wizard, click Finish.

    This creates and allocates a default schedule for regular synchronization. Enable the schedule for regular synchronization.

    This sets up, saves and immediately activates the synchronization project.

    NOTE:

    • If enabled, a consistency check is carried out. If errors occur, a message appears. You can decide whether the synchronization project can remain activated or not.

      Check the errors before you use the synchronization project. To do this, in the General view on the Synchronization Editor‘s start page, click Verify project.

    • If you do not want the synchronization project to be activated immediately, disable the Activate and save the new synchronization project automatically option. In this case, save the synchronization project manually before closing the Synchronization Editor.

    • The connection data for the target system is saved in a variable set and can be modified in the Synchronization Editor in the Configuration > Variables category.

Related topics

• Users and permissions for synchronizing with Microsoft Teams
• Information required for Microsoft Teams synchronization projects
• Setting up the synchronization server for Microsoft Teams
• Configuring the synchronization log
• Customizing the synchronization configuration for Microsoft Teams
• Running synchronization
• Tasks following synchronization
• Default project template for Microsoft Teams

All the information, tips, warnings, and errors that occur during synchronization are recorded in the synchronization log. You can configure the type of information to record separately for each system connection.

To configure the content of the synchronization log

1. To configure the synchronization log for target system connection, select the Configuration > Target system category in the Synchronization Editor.

   - OR -

   To configure the synchronization log for the database connection, select the Configuration > One Identity Manager connection category in the Synchronization Editor.

2. Select the General view and click Configure.

3. Select the Synchronization log view and set Create synchronization log.

4. Enable the data to be logged.

   NOTE: Some content generates a particularly large volume of log data. The synchronization log should only contain data required for error analysis and other analyzes.

5. Click OK.

Synchronization logs are stored for a fixed length of time.

To modify the retention period for synchronization logs

• In the Designer, enable the DPR | Journal | LifeTime configuration parameter and enter the maximum retention period.

Related topics

• Displaying synchronization results

Having used the Synchronization Editor to set up a synchronization project for initial synchronization of a Notes domain, you can use the synchronization project to load Microsoft Teams objects into the One Identity Manager database. Changes are provisioned in Microsoft Teams.

You must customize the synchronization configuration to be able to regularly compare the database with the Microsoft Teams environment and to synchronize changes.

• To use One Identity Manager as the primary system during synchronization, create a workflow with synchronization in the direction of the Target system.

• You can use variables to create generally applicable synchronization configurations that contain the necessary information about the synchronization objects when synchronization starts. Variables can be implemented in base objects, schema classes, or processing method, for example.

• Use variables to set up a synchronization project for synchronizing different Azure Active Directory tenants. Store a connection parameter as a variable for logging in to the Azure Active Directory tenants.

• To specify which Microsoft Teams objects and database objects are included in 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.

• Update the schema in the synchronization project if the One Identity Manager schema or target system schema has changed. Then you can add the changes to the mapping.

• To synchronize additional schema properties, update the schema in the synchronization project. Include the schema extensions in the mapping.

For more information about configuring synchronization, see the One Identity Manager Target System Synchronization Reference Guide.

Detailed information about this topic

• How to configure Microsoft Teams synchronization
• Changing system connection settings of Microsoft Teams
• Updating schemas
• Configuring single object synchronization
• Accelerating provisioning and single object synchronization