SharePoint connection

If you will be creating datasets that process SharePoint data, you must complete additional tasks to enable processing by the processing agent.

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.

IMPORTANT: When interacting with SharePoint Online (SPO), two-factor authentication must not be enabled for the service user provided for either the source or the target. If you use a single SharePoint user as the service user for all SharePoint activity, the user must not have two-factor authentication enabled.

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.

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

Update the logon account for Fusion services

On each processing agent host machine in a cluster assigned to process SharePoint documents, the log on account for the FAS services must be in the host's Administration group and can logon as a service.

Complete this task after the agent is installed on the host machine and the necessary SharePoint requirements are in place.

To update the logon account for Fusion services

On a machine hosting the processing agent in a cluster assigned to process SharePoint documents, stop all the Micro Focus Fusion services.
For all FAS services, change the Log On account for all the services to a local or domain account that is in the Administrators group and has Logon as a service permission.

If utilizing a web proxy, log into the agent host machine as the specified user and configure the system proxy information as appropriate. You can do so using Internet Explorer network connection settings, Chrome network connection settings, or “Internet Options” in the control panel.
Run AccessHandler.exe and provide the requested information.

TIP: For details about the entries you will make when running the credential utility, run the credential utility from a command line with the help option.

Example: AccessHandler.exe /h
Start the Micro Focus FAS-Agent Api service
Start all other Micro Focus FAS services.
Repeat for each agent host machine in a cluster assigned to process SharePoint documents.

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.