Introduction
Microsoft Teams integration requires specific Graph API permissions, and some organizations require IT admin approval. This guide explains Teams permission errors and how to resolve them.
Understanding Teams Permissions
Teams integration uses Microsoft Graph API with OAuth 2.0 authentication.
Required permissions (scopes):
- User.Read - Basic user profile access
- OnlineMeetings.Read - Read meeting details from your calendar
- OnlineMeetingRecording.Read.All - Access meeting recordings (requires admin consent)
Admin Consent Required
User Consent vs Admin Consent
There are two types of authorization flows for Teams integration:
Basic permissions (User.Read, OnlineMeetings.Read) that individual users can approve themselves when connecting Teams.
Organization-wide permissions (recording access) that require IT admin approval in Azure AD portal or Microsoft 365 admin center.
Admin Approval Required Error
If you see "Admin approval required" or "Need admin approval," your organization requires IT admin consent.
Steps to resolve:
- Contact your IT department or Microsoft 365 administrator
- Explain that you need NoteWave approved for Teams integration
- Provide the app name: "NoteWave" and required scopes (listed above)
- Admin approves the app in Azure AD Enterprise Applications
- Once approved, try connecting Teams again in NoteWave
For IT Admins
Personal vs Work/School Accounts
NoteWave Teams integration works with both Microsoft account types, but permissions differ.
Individual users have full control and can approve all permissions without admin consent.
Managed by organization IT. May require admin approval for recording access and other advanced permissions.
Reconnecting Teams Integration
If your Teams connection stops working or shows "Disconnected," try reconnecting:
Reconnection steps:
- Go to Settings → Integrations
- Click "Disconnect" next to your Teams connection
- Wait 5 seconds for disconnection to complete
- Click "Connect Teams" and sign in with your Microsoft account
- Approve all requested permissions (or request admin approval if needed)
NoteWave automatically refreshes access tokens with a 5-minute buffer before expiry. Manual reconnection is only needed if auto-refresh fails or permissions are revoked.
Delegate Calendar Issues
Meetings on delegated or shared calendars may not sync properly.
Use Primary Calendar
External User Meetings
Meetings organized by external users may have limited API access.
If you're invited to a Teams meeting by someone outside your organization, NoteWave may have limited access to the meeting details or recording.
Workaround: Use the "Link Meeting" option to manually join the bot with the Teams meeting URL instead of relying on calendar sync.
Webhook Subscription Errors
NoteWave uses Microsoft Graph webhooks to receive meeting updates in real-time.
How webhooks work:
- NoteWave subscribes to your calendar change notifications
- Subscriptions auto-renew every 2.9 days
- If renewal fails, calendar sync stops working
- Reconnecting your Teams integration creates a new subscription
Webhook issues are handled automatically in most cases. If calendar sync stops, try reconnecting Teams to reset the webhook subscription.
Microsoft Graph API Errors
NoteWave uses circuit breaker patterns to handle temporary Graph API failures gracefully.
Automatic Retry
Still Blocked by Permissions?
If you've contacted your IT admin and still can't connect Teams:
Contact Support
We can provide your IT team with detailed documentation about NoteWave's security model and required permissions to help with approval.
Was this article helpful?
Your feedback helps us improve our documentation.