Skip to main content

Troubleshooting SharePoint setup for Microsoft 365 administrators

This article covers common issues Microsoft 365 administrators may run into when granting CoLab access to SharePoint. If you haven't started setup yet, see Enabling SharePoint for your team members.

Errors during consent

"Selected user account does not exist in tenant … and cannot access the application"

The tenant ID in the consent link doesn't match the tenant of the account you signed in with. Confirm you replaced <tenant_id> with your own tenant ID, then try again. If you're signed in to more than one Microsoft account, open the link in a private or incognito window.

"Need admin approval"

The account you signed in with doesn't have permission to grant consent. Sign out and sign back in with a Global Administrator or Privileged Role Administrator account. If you aren't an administrator, forward the consent link to someone in your organization who is.

AADSTS50011: redirect URI mismatch

The redirect URI in the consent link doesn't match the one registered on CoLab's application. This usually means the link was edited. Use the link exactly as provided, changing only the tenant ID. If you still see this error, contact CoLab support.

Sign-in is blocked, or an error mentions a policy

A Conditional Access policy that targets all cloud applications may be blocking the sign-in. In the Microsoft Entra admin center, check Sign-in logs to find the blocked attempt and the policy responsible. You can then exclude CoLab's application ID from that policy or adjust the policy as appropriate.

Consent is blocked even when using an admin account

Check Microsoft Defender for Cloud Apps → App governance. If your organization has policies that flag or block applications from unverified publishers, one of them may be preventing consent. Review any app governance alerts related to CoLab.

You may also notice the setting Enterprise applications → Consent and permissions → User consent settings. This controls whether non-admin users can grant consent themselves. It doesn't block admin consent, but it explains why regular users can't complete this setup on their own.

Issues after consent

CoLab doesn't appear under Enterprise applications

Consent was most likely cancelled or not completed. Run the consent link again and make sure you're redirected to www.colabsoftware.com after selecting Accept. Then check Enterprise applications → All applications for CoLab.

Permissions look incomplete

If fewer than three delegated Microsoft Graph permissions appear under Enterprise applications → CoLab → Permissions, consent may have been granted with a role that has restrictions on Microsoft Graph permissions, such as Application Administrator or Cloud Application Administrator. Run the consent link again using a Global Administrator or Privileged Role Administrator account.

Issues after setup is complete

Users are asked for consent after setup was already done

This happens when CoLab requests a permission that wasn't included in the original grant, typically after an integration update. An administrator running the consent link again resolves it for all users.

Team members can't connect SharePoint in CoLab

If consent has been granted in Microsoft 365 but team members still can't connect, check that a CoLab company admin has turned on Enable SharePoint for Team Members under Settings → Integrations → File Storage → SharePoint.

Guest users can't connect SharePoint, regardless of this setting.

Did this answer your question?