Fusion 24.1.0 Connect Help Center

# SharePoint connection

If you will be creating sources and datasets that process SharePoint or SharePoint Online (O365) data, you must complete additional tasks to enable processing by the processing agent.

Complete the tasks for SharePoint or SharePoint Online as appropriate for the data to be managed by Fusion. If you will process data by both SharePoint and SharePoint Online, complete the tasks for both implementations.

For the SharePoint version supported, see the supported data resources under "Agent installation and configuration".

## SharePoint connection tasks

Complete the following to process data from SharePoint.

1. Create SharePoint service user

   Fusion performs processes in SharePoint through a SharePoint service user. The SharePoint service user is used by the processing agent to connect to and perform actions in your SharePoint environment related to processing data. A SharePoint service user is also necessary to send data managed by Fusion to a defined location in SharePoint.

   The exact level of permissions required depends on the actions you will be performing through Fusion.

   - To process and collect items from SharePoint source, the SharePoint service user must have a minimum permission of Reading.

   - To delete items from a SharePoint source, the SharePoint service user must have a minimum permission of Collaboration.

   - To process, collect, and delete items from OneDrive, the SharePoint service user must be added to the Site Collection Administrators for the OneDrive site to be processed.

   - To send items to a SharePoint target, the SharePoint service user must have a minimum permission of Collaboration.

   When creating a source, you will define the credentials for the SharePoint service user that will be used to process data (read, collect, delete). When creating a target, you will define the credentials for the SharePoint service user that will be used to send data to SharePoint. For auditing in SharePoint, you can choose to create two separate service users—one for processing and one for sending to targets.

2. Update the logon account for Fusion services

## SharePoint Online connection tasks

Fusion requires non-user based SharePoint Online access using the “SharePoint app-only” access method. Familiarize yourself with the guidance from Microsoft regarding Accessing SharePoint using an application context, Granting Access to SharePoint App-Only, and Add-in permissions in SharePoint. This information will assist in understanding the tasks necessary to complete the connection between Fusion and SharePoint Online.

Complete the following to process data from SharePoint Online (O365).

1. Create or identify an O365 user with, at a minimum, "SharePoint Administrator" permission at the O365 level. Fusion requires this user in order to access your SharePoint Online environment.

   You must perform the remainder of these tasks as this user.

2. Create a “SharePoint app-only” definition at either the SharePoint Online tenant level or at the SharePoint site level.

   - To create a “SharePoint app-only” definition at the SharePoint Online tenant level

     1. Open `https://<O365Tenant>.sharepoint.com/_layouts/15/appregnew.aspx`, where `<O365Tenant>` is your O365 tenant name.

     2. Complete the App Information options.

        Option | Description
        --- | ---
        Client Id | Click the Generate button. IMPORTANT: Make note of the generated Client Id. This is needed later.
        Client Secret | Click the Generate button. IMPORTANT: Make note of the generated Client Secret. This is needed later.
        Title | Type a descriptive title for the App-Only principal.
        App Domain | Type a placeholder domain URL, such as `www.localhost.com`.
        App Redirect URL | Type a placeholder redirect URL, such as `https://www.localhost.com/`.

     3. Click Create.

   - To create a “SharePoint app-only” definition at the SharePoint site level

     The user performing this must be an admin of the specific SharePoint site.

     1. Open `https://<O365Tenant>.sharepoint.com/sites/<site>/_layouts/15/appregnew.aspx` where,

        - `<O365Tenant>` is your O365 tenant name.

        - `<site>` is the SharePoint site name.

     2. Complete the App Information options.

        Option | Description
        --- | ---
        Client Id | Click the Generate button. IMPORTANT: Make note of the generated Client Id value. This is needed later.
        Client Secret | Click the Generate button. IMPORTANT: Make note of the generated Client Secret value. This is needed later.
        Title | Type a descriptive title for the App-Only principal.
        App Domain | Type a placeholder domain URL, such as `www.localhost.com`.
        App Redirect URL | Type a placeholder redirect URL, such as `https://www.localhost.com/`.

     3. Click Create.

3. Grant permission to the created “SharePoint app-only” definition at either the SharePoint Online tenant level or at the SharePoint site level, as appropriate for the definition created.

   - To grant permission to the definition at the SharePoint Online tenant level

     1. Open `https://<O365Tenant>-admin.sharepoint.com/_layouts/15/appinv.aspx`, where `<O365Tenant>` is your O365 tenant name.

     2. On the App Information page, type the generated Client Id value in the App Id field.

        The Title, App Domain, and Redirect URL fields populate based on the Client Id defined.

     3. Type a valid Permission Request XML.

        Syntax

            <AppPermissionRequests AllowAppOnlyPolicy="true">

            <AppPermissionRequest Scope="http://sharepoint/content/tenant" Right="<ReadOrManage>"/>

            </AppPermissionRequests>

        - To allow Fusion to collect from a SharePoint Online source, the `Read` right is required.

        - To allow Fusion to send to a SharePoint Online target, the `Manage` right is required.

          Fusion creates a new SharePoint list for output. This requirement correlates with the regular SharePoint user permission “designer”.

        - To allow Fusion collect from SharePoint Online and send to a SharePoint target, the `Manage` right is required.

        Example: allow collect and send to target

            <AppPermissionRequests AllowAppOnlyPolicy="true">

            <AppPermissionRequest Scope="http://sharepoint/content/tenant" Right="Manage"/>

            </AppPermissionRequests>

     4. Click Create.

        In the consent confirmation dialog, click Trust It to grant permission.

   - To grant permission to the definition at the SharePoint site level

     1. Open `https://<O365Tenant>.sharepoint.com/sites/<site>/_layouts/15/appinv.aspx` where,

        - `<O365Tenant>` is your O365 tenant name.

        - `<site>` is the SharePoint site name.

     2. On the App Information page, type the generated Client Id value in the App Id field.

        The Title, App Domain, and Redirect URL fields populate based on the Client Id defined.

     3. Type a valid Permission Request XML.

        Syntax

            <AppPermissionRequests AllowAppOnlyPolicy="true">

            <AppPermissionRequest Scope="http://sharepoint/content/sitecollection/web" Right="<ReadOrManage>"/>

            </AppPermissionRequests>

        - To allow Fusion to collect from a SharePoint Online source, the `Read` right is required.

        - To allow Fusion to send to a SharePoint Online target, the `Manage` right is required.

          Fusion creates a new SharePoint list for output. This requirement correlates with the regular SharePoint user permission “designer”.

        - To allow Fusion collect from SharePoint Online and send to a SharePoint target, the `Manage` right is required.

        Example: allow collect and send to target

            <AppPermissionRequests AllowAppOnlyPolicy="true">

            <AppPermissionRequest Scope="http://sharepoint/content/sitecollection/web" Right="Manage"/>

            </AppPermissionRequests>

     4. Click Create.

        In the consent confirmation dialog, click Trust It to grant permission.

     NOTE: If you want to process data from multiple sites, create a permission grant for each site.

When you create SharePoint Online (O365) sources in Fusion, you will need to provide the Client Id and the Client Secret.

## SharePoint processing

When processing Microsoft Office items from SharePoint, Fusion uses the last modified date in the de-duplication calculation. Due to the way modified dates are handled in Office items and in SharePoint (including OneDrive), Fusion will not identify documents with different dates as duplicates.

- When an Office item is uploaded to a SharePoint or OneDrive site web interface, the item's modified date is changed.

- When an Office item is added to a local system and is then synchronized to the SharePoint site, the item's modified date is not changed.

SharePoint Lists are comprised of form records, called items in SharePoint, that contain various text fields and can have attachments. When deleting SharePoint files, Fusion does not delete attachments to items from SharePoint Lists.

## SharePoint item counts

The document and item counts in Fusion may differ from the "item" count as seen in the SharePoint site interface. This difference relates to the following.

- In Fusion, a document is an original file processed by Fusion and an item is an attachment to an original file. In SharePoint, an item is a row in a table, or a record in a database and a document is a type of item.

- In SharePoint, item counts are derived from the total number folders, documents, and items (each entry in a SharePoint Item List). In Fusion, document counts are derived from the total number of documents from SharePoint Document Libraries and attachments in a SharePoint Item List. Fusion does not process the field, or entry, in an Item List, only the attachments from the Item List.

  For example, if SharePoint Item has zero attachments, SharePoint records this as one item. If a SharePoint Item has 10 attachments, SharePoint also records this as one item.

- The item count listed on the SharePoint Site Contents page for libraries includes all items in the library, including folders. Folders in which files exist in SharePoint are not included in counts in Fusion.

- When processing SharePoint content, Fusion does not process SharePoint library items that include the `UIVersion` field. These SharePoint items are SharePoint UI elements and are skipped. For example, the Form Templates and List Template Gallery library items are UI elements and therefore not processed by Fusion. However, when viewing the SharePoint Site Contents page, these SharePoint items are included in the item count.

## SharePoint deletion tracking

Fusion tracks the deletion of managed SharePoint items using the SharePoint change logs. Each time processing is run on a dataset—on a schedule, or on demand—Fusion checks the SharePoint logs for deleted items. For each managed item that is deleted in SharePoint, Fusion deletes that item from the Fusion index. If an item within a container file (such as ZIP) is deleted in SharePoint, the item is removed from the index as part of updating the container file when the Fusion job run occurs.

To ensure accurate tracking of items deleted from SharePoint, ensure that the SharePoint datasets in Fusion are updated more often than the maximum number of days SharePoint logs are kept. For example, if your SharePoint logs are configured to be stored for 60 days, verify that your SharePoint datasets are updated at least every 59 days.

Copyright 2019-2024 Open Text
Version 24.1.0 | Last updated December 2023
Connect
Marketplace
Learn
Support portal
Documentation
Contact
Submit or view service request