Access requirements
| Pre-Requisites | Status | Comment |
|---|---|---|
| Paid dev account | ✅ Not required | Free, self-signup for a Microsoft account and Azure account. |
| Paid test account | ✅ Not required | Free Microsoft account can be used for testing. |
| Partnership | ✅ Not required | |
| App review | ⚠️ Conditional | Required only if you want to publish your app to the Microsoft commercial marketplace or if your app needs admin consent for certain permissions. |
| Security audit | ✅ Not required |
Setup guide
1
Create a Microsoft account and Azure account
If you don’t already have them, sign up for a Microsoft account and an Azure account.
2
Register an application in Microsoft Entra ID
- Sign in to the Microsoft Entra admin center as at least an Application Developer.
- If you have access to multiple tenants, use the Settings icon in the top menu to switch to the tenant in which you want to register the application.
- From the search bar at the top of the Azure portal, search for App registrations and select it. Then choose New registration. Or from your left navigation tab, navigate to Applications > App registrations then choose New registration.
- Enter a meaningful name for your application, for example “Nango Integration”.
- Under Supported account types, select the appropriate option based on your needs:
- Accounts in any organizational directory - For multitenant apps that you want users in any Microsoft Entra tenant to be able to use.
- Accounts in any organizational directory and personal Microsoft accounts - For multitenant apps that support both organizational and personal Microsoft accounts.
- Leave the Redirect URI section blank for now; we’ll configure it in a later step.
- Click Register to complete the app registration.
3
Note your application (client) ID
After registration, you’ll be taken to the application’s Overview page. Record the Application (client) ID, which uniquely identifies your application and is used in your application’s code as part of validating security tokens.
4
Add a redirect URI
- In the left sidebar, select Authentication.
- Under Platform configurations, select Add a platform.
- Select Web as the platform type.
- Enter
https://api.nango.dev/oauth/callbackas the Redirect URI. - Under Implicit grant and hybrid flows, check the boxes for Access tokens and ID tokens if your application needs them.
- Under Advanced settings, set Allow public client flows to No for web applications.
- Click Configure to save your changes.
5
Add API permissions
- In the left sidebar, select API permissions.
- Click Add a permission.
- Select Microsoft Graph to integrate with OneNote.
- Choose the type of permissions:
- Delegated permissions - Your app accesses the API as the signed-in user.
- Application permissions - Your app accesses the API directly without a signed-in user.
- Select the specific permissions your app requires, Please refer to the table below for some of the commonly used scopes.
- Click Add permissions.
- If your application requires admin consent, click Grant admin consent for [tenant] to pre-authorize the permissions.
6
Create a client secret
- In the left sidebar, select Certificates & secrets.
- Under Client secrets, click New client secret.
- Enter a description for the secret and select an expiration period (6 months, 12 months, 24 months, or custom).
- Click Add.
- Important: Copy the secret value immediately and store it securely. You won’t be able to see it again after you leave this page.
7
Configure token settings (optional)
- In the left sidebar, select Token configuration.
- Here you can configure optional claims to be included in the ID and access tokens issued to your application.
- Click Add optional claim if you need to include additional information in your tokens.
8
Configure app visibility (optional)
If you want users to see your app on their My Apps page:
- From the search bar at the top of the Azure portal, search for Enterprise applications, select it, and then choose your app.
- On the Properties page, set Visible to users? to Yes.
9
Next
Follow the Quickstart.
Common Scopes
| Scope | Description |
|---|---|
Files.Read | Read the signed-in user’s OneDrive files |
Files.Read.All | Read all OneDrive files the user can access |
Files.ReadWrite | Read and write the signed-in user’s OneDrive files |
Files.ReadWrite.All | Read and write all OneDrive files the user can access |
Files.Read.Selected | Read selected OneDrive files the user provides access to |
Files.ReadWrite.AppFolder | Read and write files in the application’s special OneDrive folder |
offline_access | Access to refresh tokens for offline access |
User.Read.All | Read user profiles in the organization (useful for file ownership mapping) |
SharePoint and Graph tokens
Each connection now issues two tokens:-
Main Token (Graph Token):
Used for standard Microsoft Graph API operations, such as making proxy calls to the Graph API at
https://graph.microsoft.com. -
SharePoint Token (
sharepointAccessToken): Available underconnection_configand required when interacting with SharePoint-specific components, such as the latest File Picker (v8.0).
To obtain the
sharepointAccessToken, your integration must include and request the Sites.Read.All scope during authorization. Without this scope, the SharePoint token will not be issued — only the Graph token will be available for your connection. sharepointAccessToken is only available for new connections. If it’s missing from your connection_config, please reauthorize your connection to obtain and include the token.