Skip to main content

Troubleshooting SharePoint Integrations

SharePoint connection issues typically come from incorrect SharePoint access permissions or incorrect SharePoint configuration.

Authentication Issues

For authentication to succeed, your SharePoint site must use a verified domain, as required by Microsoft. Instructions for verifying your domain are on the Microsoft Learn site: https://learn.microsoft.com/en-us/entra/identity/users/domains-manageExternal LinkThis link leads to an external website and will open in a new tab.

Verify your SharePoint domain before attempting to authenticate.

The user account used to authenticate must have a valid email address associated with the verified domain. By default, the domain of the email address matches the verified domain. Microsoft Entra can be configured to allow email addressesExternal LinkThis link leads to an external website and will open in a new tab with domains that differ from the verified domain.

The following error is logged when the user's email domain does not match the SharePoint domain:

Ensure your user's email domain is registered and matches the user's principal domain name.

If your email domain matches the verified SharePoint domain and you still see that message, confirm that the user account has a Microsoft 365 license assigned.

Missing Microsoft 365 License

An OAuth connection to SharePoint Online typically fails when the user account does not have a Microsoft 365 (formerly Office 365) license that includes SharePoint Online. Plans without SharePoint Online do not support the integration, and the connection fails.

When no license has been assigned to the user, the following error appears:

Ensure your user's email domain is registered and matches the user's principal domain name.

If you have assigned a license to the user and still see that message, verify your SharePoint domain and confirm that the user's email address matches the domain. Also confirm that the user has proper SharePoint access permissions.

Remote Resync Failures

A sync to SharePoint performs a remote resync when SharePoint modifies a delivered file. Files.com writes SharePoint's version of the file back to the sync source so both sides match, and the sync run log records a sync_remote_resync event.

That resync requires write access to the source location. When the source location does not have write permission, the resync fails, and the failure appears in the sync run log.

To resolve this, apply write permission to the source location so that the resync can complete, endless sync loops are prevented, and excess transfer charges are avoided.

Rate Limit Throttling

A Sync or Automation targeting a SharePoint remote server with large quantities of files can produce this error in the logs:

Sharepoint errored while trying to Connect: 'Activity Limit Reached: The request has been throttled'

This error means Microsoft's rate limiting is in effect. Files.com automatically slows down and retries, and you can configure your Syncs and Automations to avoid triggering the limits.