Microsoft Integration Scopes

Many Microsoft integrations use delegated Microsoft Graph permissions. Azure DevOps, Azure Resource Manager, Power BI, Microsoft Fabric, and Dynamics 365 use provider-specific scopes or permissions described on their respective pages. Standard SharePoint content permissions use tenant wide .All scopes such as Sites.Read.All and Sites.ReadWrite.All. Some delegated permissions require administrator consent in your Microsoft Entra tenant. Common examples include User.Read.All, Group.Read.All, GroupMember.Read.All, ChannelMessage.Read.All, OnlineMeetingTranscript.Read.All, and Application.ReadWrite.All. This list is illustrative, not exhaustive, and whether consent is required can depend on your tenant’s consent settings.

Graph-based Microsoft integrations are built for standard .All scopes. Azure DevOps, Azure Resource Manager, Power BI, Microsoft Fabric, and Dynamics 365 use provider-specific scopes or permissions instead. You can configure Graph-based integrations to use Sites.Selected, but Langdock does not guarantee their full functionality.This affects a variety of actions across several Microsoft integrations:

SharePoint
Microsoft OneDrive
Microsoft OneNote
Microsoft Teams

When actions are affected, they are flagged clearly on the respective integration’s page.

Microsoft integration scopes

Select an integration to review its minimum scopes. Each page lists the exact action, a short description, and every scope in its current mapping.