Microsoft Teams
Org-level connection
Microsoft Teams is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
How to connect
Click "Connect with OAuth" below to authorize On Belay to access your Microsoft Teams workspace. You'll be redirected to Microsoft to approve the connection — no credentials to copy or paste.
If your Microsoft 365 admin restricts user app approvals, you'll see a "Need admin approval" message from Microsoft. Share the consent link Microsoft shows you with your IT admin to complete the connection. The connection only allows access to the teams, channels, and chats you personally belong to — On Belay does not read tenant-wide data.
Ready to connect?
Sign in to On Belay and open the Integrations page to add Microsoft Teams.
Permissions (scopes)
These are the data scopes On Belay can be granted for Microsoft Teams. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
offline_access | Maintain offline access | Read only |
User.Read | Read my profile | Read only |
Presence.Read | Read my presence | Read only |
Team.ReadBasic.All | Read teams I belong to | Read only |
Channel.ReadBasic.All | Read channels | Read only |
Channel.Create | Create channels | Read / Write |
ChannelMessage.Read.All | Read channel messages | Read only |
ChannelMessage.Send | Send channel messages | Read / Write |
Chat.ReadBasic | Read chat membership | Read only |
Chat.Read | Read chat messages | Read only |
ChatMessage.Send | Send chat messages | Read / Write |
User.ReadBasic.All | Read users in my org | Read only |
Files.Read.All | Read files | Read only |
Troubleshooting
"redirect_uri_mismatch" error during OAuth
https://app.onbelay.ai/api/oauth-callback/microsoft_teams to the allowed redirect URIs in your OAuth app settings."invalid_scope" error
Connected but Claude can't access data
Still stuck? We're happy to help.
Contact support →