Troubleshooting SharePoint Integrations

Use the checks below to diagnose sign-in failures, inaccessible SharePoint content, and interrupted Syncs. For a new connection, first follow the SharePoint setup and authentication guidance.

Authentication Issues

Start by checking whether the Remote Server uses Sign In With Microsoft or Microsoft Entra ID App. They use different credentials and permissions, so a user-account change will not resolve an app credential or consent problem.

Sign In With Microsoft

If the sign-in window displays this message, Files.com could not verify the email domain returned for the Microsoft account:

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

Confirm that you selected the intended Microsoft account. Ask your Microsoft Entra administrator to check that the account's email address is populated and meets the email-domain requirements. The check concerns the account's email and sign-in domains, not the SharePoint server's sharepoint.com address. The message alone does not establish that a Microsoft 365 license is missing.

If sign-in succeeds but you cannot browse or transfer files, sign in directly to SharePoint with the same account and try the affected site, library, and folder. Check the account's SharePoint permissions and license. A successful Microsoft sign-in does not by itself grant access to SharePoint content.

For a previously working connection that requires a new sign-in, follow Re-authenticating Remote Servers.

Missing Microsoft 365 License

For an account in your Microsoft 365 organization, have an administrator check its license and enabled services. Confirm that SharePoint Online is included and enabled for that account, rather than assuming any Microsoft 365 license is sufficient. After correcting the assignment, verify access to the affected SharePoint content with the same account and retry the connection.

These user-license checks apply to Sign In With Microsoft. App-only connections use the app's credentials, consent, and site permissions instead.

Microsoft Entra ID App

If app authentication fails, confirm the configured tenant ID and client ID, then check whether the client secret or certificate has expired or been replaced. Update the credentials in the Remote Server or its shared credential entry as applicable.

If authentication succeeds but SharePoint access fails, confirm that an administrator granted consent to the required Microsoft Graph Application permission. For Specific Site, also verify the configured site URL and the app's separate permission assignment for that site. Consent to Sites.Selected alone does not grant site access.

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.