Troubleshooting: SharePoint "Authentication check returned false" Error

The "Authentication check returned false" error occurs when Tekst\'s periodic health check fails to verify access to one or more of your connected SharePoint sites. While you may still be able to see the list of sites in the Tekst dashboard, the background synchronization is paused until the connection is refreshed.

Why this happens

This error is typically triggered when the individual site-level authentication fails, even if the broader Microsoft account remains connected. Common causes include:

• Permission Revocation: A SharePoint Administrator may have removed Tekst\'s access to a specific site or library.

• Site Deletion or URL Changes: If a site was deleted or its URL was renamed in SharePoint, the health check will fail for that specific entry.

• Tenant-Level Restrictions: New security policies in your Microsoft 365 tenant might be blocking the integration.

• Recent changes: it can take up to 12 hours for the changes on Microsoft to propagate to Tekst.

Tekst performs a deep health check for every individual site you have configured. If even one site fails to respond, the entire integration status may show as "Authentication failed" to prevent data inconsistencies.

How to fix it

In most cases, you can resolve this by re-triggering the Microsoft OAuth flow to refresh your access tokens.

Step 1: Identify the failing site

1. Navigate to Settings > Integrations.

2. Locate the SharePoint row. You will likely see a red "Authentication failed" badge.

3. Click on the row to open the SharePoint settings.

4. Look through your list of connected sites. Any site causing the failure will typically be highlighted or show a disconnected status.

Step 2: Verify the integration

1. Verify with which client id and application id the integration was connected.

2. Verify the permission requests (e.g., Sites.Read.All, Files.Read).

Once changes are complete, the status badge in Tekst should turn green, and the "Authentication check returned false" error will disappear from your logs. This can take up to 12 hours to propagate from sharepoint to Tekst

Still having issues?

If the error persists after reconnecting, check the following:

• Global Admin Consent: Ensure your IT department has granted tenant-wide consent for the Tekst application in the Azure Portal.

• Site Access: Verify that the account used to reconnect still has active "Read" permissions on the specific SharePoint sites you are trying to sync.

If a site has been permanently deleted in SharePoint, you must remove it from the Tekst configuration page to stop the health check from failing.