Prerequisites
- The account used must be a SharePoint administrator — or have been granted permission by an administrator.
- You must have a tenant configured in SharePoint.
- You will need to provide the Tenant Name and, optionally, the SharePoint Subsite.
How to connect
Open the connector and enter the credentials
In the Connectors panel, locate SharePoint and click to connect. The credentials form opens.
- Keep the Authentication method as
OAuth 2.0. - In Tenant Name, enter only the tenant name (for example,
your-companyforyour-company.sharepoint.com). Do not paste the full URL. - In SharePoint Subsite (optional), enter the subsite name that appears in the URL after
/sites/(for example,https://tenant.sharepoint.com/sites/<subsite-name>). Leave it blank to use the root site.

Grant the permissions (admin consent)
If the account is not an administrator, Microsoft displays an Admin approval required screen. In that case, sign in with an administrator account or ask an administrator to grant permission to the application.
If the account is an administrator (or already has the permission), Microsoft shows the Permissions requested screen. Review the permissions and confirm to authorize access.


Connection confirmation
After authorizing, the Tess callback window shows the Connected successfully! message and closes automatically after a few seconds.

Troubleshooting
The connection keeps loading and ends in a timeout
The connection keeps loading and ends in a timeout
Check that Tenant Name was filled in with only the tenant name (for example,
your-company) and not the full URL (your-company.sharepoint.com). An incorrect value can cause Microsoft to return an invalid resource error during OAuth.The admin approval required screen appears
The admin approval required screen appears
The application needs permissions that only an administrator can grant. Ask the SharePoint administrator to sign in first through the connector and grant authorization; after that, other users can connect.
Environment with federated SSO, IP allowlist, or client certificate
Environment with federated SSO, IP allowlist, or client certificate
In organizations with an additional federated domain after SSO (with IP blocks or a client certificate requirement on the device), the connection may fail due to corporate environment restrictions. In these cases, a technical alignment with the infrastructure team is required to validate the IdP, federated domains, IP allowlist, and certificates.
Connectors involve access to external systems. Only connect accounts and apps that are appropriate to the usage context, and review permissions carefully.
