Microsoft Teams (and Office 365, Outlook, OneDrive)

​

Overview

​

Pre-built tooling

​

Pre-built integrations

​

Access requirements

​

Setup guide

No setup guide yet.

​

Useful links

• How to register an Application
• OAuth-related docs
• List of OAuth scopes

This endpoint supports all Microsoft APIs available via the Graph API endpoints, which includes:

• Microsoft 365 core services: Bookings, Calendar, Delve, Excel, Microsoft 365 compliance eDiscovery, Microsoft Search, OneDrive, OneNote, Outlook/Exchange, People (Outlook contacts), Planner, SharePoint, Teams, To Do, Viva Insights
• Enterprise Mobility + Security services: Advanced Threat Analytics, Advanced Threat Protection, Azure Active Directory, Identity Manager, and Intune
• Windows services: activities, devices, notifications, Universal Print
• Dynamics 365 Business Central services

​

API gotchas

• Make sure you request the offline_access scope to get a refresh token and keep access with your integration.
• Microsoft has a unified OAuth system for their various APIs. This provider should work for most of them (e.g. Microsoft EntraID, OneNote, Onedrive, Outlook, Sharepoint Online, Microsoft Teams etc.).
• Microsoft offers a tool that allows you to construct and perform Graph API queries and see their response for any apps on which you have an admin, developer, or tester role. For more information you can check Microsoft Graph Explorer.
• You can find permissions required for each API call in their corresponding API methods section, i.e, to retrieve a list of notebook objects from Onenote, you can have a look at List Notebooks permissions.
• Please be aware that the Microsoft Graph API implements throttling to manage the volume of requests. For more information on handling throttling, refer to the Microsoft Graph Throttling Guidance.
• You can set the .default scope documentation to ensure the permissions remain the same as those granted at the organization level.
• The .default scope can’t be combined with the scopes registered in the Azure portal. So either just use the .default scope or remove it to list out explicit parameters that are required. If you attempt to combine them you’ll receive the following error

.default scope can't be combined with resource-specific scopes

• If you require a user to reauthenticate and force them to accept scopes that have been updated or changed you can force a prompt via the authorization_params:

const { data } = await nango.createConnectSession({
  [...],
  integrations_config_defaults: {
    "<provider-name>": {
      authorization_params: {
        "prompt": "consent"
      }
    }
  }
});