Handling Delegated vs. Application Scopes in Microsoft Integrations
December 9, 2025
Microsoft Graph offers two fundamentally different permission models — Delegated and Application scopes. Understanding how these scopes behave is important when connecting Microsoft integrations through Unified.
Some Microsoft APIs only support delegated permissions, while others require strictly application-level permissions. Mixing them in a single OAuth flow will cause failures.
In Unified, you can create separate Microsoft connections so you can cleanly target the scopes required for the endpoints you plan to use.
This guide explains the difference between the permission types, why certain Unified endpoints require one or the other, and how to configure your Unified connections correctly.
1. Delegated vs. Application Permissions
Delegated Permissions
Delegated permissions are used when a signed-in Microsoft user is present in the OAuth flow.
Use delegated permissions when:
- The API needs to act on behalf of a user
- You want to access data the user normally has permission to view
- The Microsoft Graph endpoint explicitly supports delegated scopes
Application Permissions
Application permissions are used when no user is logged in, and the app accesses Microsoft Graph directly as itself.
Use application permissions when:
- A Microsoft endpoint does not support delegated scopes
- The API involves system-level or tenant-wide data
- The OAuth token must come from the client_credentials flow
Examples of Unified endpoints that only support application scopes:
uc_call(MS Teams call records API) anduc_recording(recordings)- Microsoft Graph requires
CallRecords.Read.AllandCallRecordings.Read.Allas application permissions, not delegated.
- Microsoft Graph requires
2. Why You Cannot Mix Delegated and Application Scopes
Microsoft Graph enforces strict separation between permission types:
- Delegated scopes must be requested during a user login OAuth flow
- Application scopes must be requested using client credentials
- A single OAuth authorization cannot request both delegated and application permissions
If you request an application-only permission in a user sign-in flow, the request fails. For example, OnlineMeetings.Read.All has no delegated form, so in a user sign-in Microsoft treats it as a scope that doesn't exist and returns AADSTS650053, which Microsoft's error reference describes as: "The application '{name}' asked for scope '{scope}' that doesn't exist on the resource '{resource}'." No token is issued, and the Unified connection fails to authenticate.
Because of this, selecting both scope types for the same Unified connection will not work.
3. How to configure a Microsoft Teams connection
Microsoft Teams uses delegated permissions for Messaging, HRIS and Calendar, and application permissions for call records and recordings (uc_call, uc_recording). Before your end users can authorize a Microsoft Teams connection, register an app in Microsoft Azure and add the permissions for the objects you plan to use.
- Register the app. Register an application in Azure and get its Client ID and Client Secret (registration guide).
- Add delegated permissions. In the app, open API Permissions, click Add a permission, select Microsoft Graph, then Delegated permissions, and add the permissions for the Messaging, HRIS and Calendar objects you need.
- Add application permissions for call records. Repeat the steps with Application permissions and add
CallRecords.Read.All,OnlineMeetingRecording.Read.All,OnlineMeetingTranscript.Read.All,CallRecordings.Read.AllandCallTranscripts.Read.All. Application permissions need admin consent in the customer's tenant. - Create the connection. In Unified, enter the Client ID and Client Secret and click Activate.
Call records work on a sign-in connection or an app-only one. With the OAuth 2 method, the connection your end user authorizes by signing in covers Messaging, HRIS and Calendar, plus call records and recordings once a tenant admin approves the application permissions above. Unified exchanges your app's Client ID and Client Secret, plus the user's tenant, for an app-only token, so no second connection is needed. Without that admin approval, the user won't get call records. The integration also has an app-only method (as of 8 October 2026) for call records and recordings only, where each customer enters their own app's Client ID, Client Secret and Tenant ID. Authentication Method is one setting per workspace integration, so a workspace offers one method or the other; offering both takes a second workspace.
Use your own Azure app in production. Unified's own credentials are for testing; in production, the consent screen your customers see should be your app's.
The full steps, with screenshots, are in How to create a Connection in Microsoft Teams.
Bot-based messaging. Microsoft Teams (bot) is a separate Unified integration for channels, messages and message events. It uses delegated permissions only, and the bot has to be packaged and installed in the right team, channel or chat before API calls work; see How to Set Up a Microsoft Teams Bot with Unified.