SharePoint Online (v2)
Overview
Pre-built tooling
Pre-built integrations
Access requirements
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ❓ | |
Paid test account | ❓ | |
Partnership | ❓ | |
App review | ❓ | |
Security audit | ❓ |
Setup guide
No setup guide yet.
Useful links
API gotchas
-
To get refresh token, you will need to add
offline_access
to the list of your scopes. -
You can find permissions required for each API call in their corresponding API methods section.
-
Nango supports both SharePoint Online v1 and v2, providing flexibility for integrations depending on your requirements. SharePoint v1 refers to the older REST API, which uses legacy authentication methods like SharePoint Online (SPO) or older OAuth implementations. Its endpoints follow the pattern
https://<your-tenant>.sharepoint.com/_api/
, and it supports basic SharePoint operations. However, v1 lacks modern features such as delta queries for incremental sync and deep integration with Microsoft 365. -
Sharepoint Online v2, on the other hand, is a modernized version aligned with the Microsoft Graph API. It uses OAuth 2.0 with the Microsoft Identity Platform (formerly Azure AD) for secure and scalable authentication. Endpoints for v2 are primarily accessed through
https://graph.microsoft.com/v1.0/sites/...
, and it offers advanced capabilities like delta queries for incremental sync, enhanced performance, and seamless integration with Microsoft 365 services. -
If you are developing an app for users within your own organization and the app has already been granted adequate permissions at the organization level with user consent turned off, you must override the integration config when calling the create connect session method:
- Override
authorization_params
by setting onlyscope: '.default offline_access'
and"prompt": ""
to remove the consent screen. Note that if consent is required it will prompt the user for consent due to the “.default” scope. - Set the
.default
scope documentation to ensure the permissions remain the same as those granted at the organization level.
- Override
If this is not done, the app will show a consent screen prompting the user to grant permissions which the user will be unable to do without admin access.