Microsoft Teams Integration
'Connect Microsoft Teams to Supervity, authorize access, and use Teams data and actions in operators and workflows.'
This guide explains how to connect Microsoft Teams to Supervity, what data is available after connection, how operators can use Teams data and actions within workflows, and how to remove the integration when needed.
Overview
The Supervity Microsoft Teams integration allows your workspace to securely connect Teams as a governed platform capability.
Once connected, operators and workflows can use Teams data and actions to automate collaboration, manage channels, organize group chats, schedule meetings, sync documents, and query organizational directories.
With the Teams integration, Supervity can:
- Manage Teams, channels, and member roles (create, archive, list, add/remove members)
- Automate messaging (send direct chats, post channel messages, reply to threads, retrieve history)
- Coordinate online meetings (schedule, list, retrieve transcripts, participants, and chat details)
- Access and transfer files (list shared files, download files, read file metadata and permissions)
- Execute directory searches and synchronization (list users, search messages/files, run delta syncs)
All Teams access is governed through Supervity's security, permissions, and audit controls.
Prerequisites
Before connecting Teams, ensure you have:
- An active Supervity workspace
- A Microsoft account with an active Teams license
- Permission to authorize applications on your Microsoft account
- Access to the specific teams, channels, and chats you want to manage
Depending on your Microsoft tenant configuration, some operations (such as list users or tenant-wide message search) may require administrator approval or specific user permissions within your organization.
Adding the Teams Integration
Follow these steps to connect Microsoft Teams to Supervity. If you encounter any issues during setup, refer to the Troubleshooting section of this guide.
Step 1: Open Integrations
Log in to Supervity. From the left navigation bar, click the Integrations icon.
This opens the Integrations page, where all available integrations are listed. Connected integrations and available integrations can both be managed from this page.
Step 2: Select Microsoft Teams
Locate Microsoft Teams in the available integrations list. Click Connect.
Step 3: Authorize Access
You will be redirected to Microsoft's secure authorization page. Review the requested permissions and click Accept to grant Supervity access to your Microsoft Teams account.
Supervity uses Microsoft's standard OAuth 2.0 authorization flow. Your Microsoft password is never shared with or stored by Supervity.
Step 4: Complete Connection
After authorization, you will be redirected back to Supervity. The Microsoft Teams integration will appear as Connected on the Integrations page. Your workspace can now securely access Teams capabilities according to the permissions granted.
Having trouble? See the Troubleshooting section for step-by-step help with common setup issues.
How Teams Works in Supervity
After connection, Microsoft Teams becomes available as a governed platform tool.
Operators can use Teams capabilities when planning and executing tasks, while workflows can automate actions using Teams data.
Common use cases include:
- Syncing user directories and onboarding new employees by automatically adding them to Teams
- Building outage channels and posting real-time incident reports or system status updates
- Querying historical channel transcripts and personal chats to ingest knowledge base summaries
- Scheduling client meetings and syncing participant lists with CRMs
- Automating file transfers and backup operations between Teams document spaces and internal servers
- Keeping conversation and file records synchronized via incremental delta sync workflows
Using Teams in Operators
Connected Teams capabilities become available to operators automatically. Operators determine when Teams data or actions are required to complete a task and execute accordingly, while remaining governed by workspace permissions, security controls, and approval policies.
What Operators Can Do with Teams
Operators can perform the following actions using Teams:
- Query, list, and create teams, channels, and direct group chats
- Add or remove team members and channel participants
- Send direct chat messages, post channel announcements, and reply to threads
- Retrieve chat history, meeting transcripts, and participant lists
- Search for specific messages, files, and users across Teams
- Download files shared in chats and read file permissions or metadata
- Execute incremental delta syncs on messages and files to maintain audit logs
Typical Operator Use Cases
| Use Case | Example |
|---|---|
| Member Onboarding | Add new staff to the workspace directory, lookup their profile, and invite them to teams |
| Outage Management | Create a dedicated emergency channel, invite responders, and post status cards |
| Direct Alerts | Send direct personal chat messages to users regarding pending task approvals |
| Knowledge Ingestion | Fetch meeting transcripts and chat history to generate project retrospectives |
| File Synchronization | List shared files in a channel, check metadata, and download them for archiving |
| Audit Compliance | Execute delta syncs on channel messages to capture conversations for compliance logs |
Features & Prerequisites
For each Teams capability available in Supervity, the following describes the use case and the prerequisites required before use.
Team & Member Management
Use Case: List teams, get team details, create new teams, archive inactive teams, list team members, and add or remove members from teams.
Prerequisites:
- Microsoft Teams account connected to Supervity
- The connected account must have permissions to manage groups and teams in the tenant
Channel Operations
Use Case: List channels within a team, retrieve channel details, create new channels, update channel names or descriptions, and delete obsolete channels.
Prerequisites:
- Microsoft Teams account connected to Supervity
- Connected user must have permissions to manage channels inside the target team
Chat & Messaging
Use Case: Create direct personal chats, establish group chats, list chats, send direct messages, send channel posts, list channel messages, reply to threads, retrieve historical messages, and fetch message metadata/threads.
Prerequisites:
- Microsoft Teams account connected to Supervity
- Connecting user must be a participant in the target chat, team, or channel
Meeting Operations
Use Case: List scheduled meetings, get meeting details, retrieve participant lists, access in-meeting chat logs, and fetch post-meeting transcripts.
Prerequisites:
- Microsoft Teams account connected to Supervity
- Teams meetings and cloud recording/transcription features enabled on the tenant
File Operations
Use Case: List files shared in Teams chats, download file content, retrieve file metadata, and get file permissions.
Prerequisites:
- Microsoft Teams account connected to Supervity
- The file must exist and be shared in a location accessible by the user
Search & Sync
Use Case: Search organizational users, retrieve user profiles, search messages or files, and run delta syncs on files and messages to capture updates incrementally.
Prerequisites:
- Microsoft Teams account connected to Supervity
- Graph API permissions and tenant index policies enabled for search functions
Permissions Requested
Supervity only requests the permissions required for enabled Teams capabilities.
Depending on the features used in your workspace, permissions may include:
| Permission Type | Purpose |
|---|---|
| User Profile | Associate Teams data and read tenant user profiles |
| Team Management | Create, retrieve, archive, and manage teams and members |
| Channel Management | Manage channels and retrieve channel configurations |
| Messaging | Send and read direct chats, group chats, and channel posts |
| Meeting Transcripts | Retrieve transcripts and details of online meetings |
| Calendar | Schedule, edit, and read meeting events |
| Files Access | Download, upload, and read metadata for files shared in Teams |
| Offline Access | Maintain integration connectivity without requiring constant re-authentication |
Supervity follows least-privilege principles and only accesses data necessary to provide requested functionality.
Authentication & Security
The Microsoft Teams integration uses OAuth 2.0 authentication.
Security controls include:
- Encrypted credential storage (AES-256)
- Scoped access policies
- Token refresh and rotation support
- Immediate revocation capabilities
- Workspace-level governance controls
- Complete audit logging
- TLS 1.3 for all connection pipelines
All Teams access remains subject to Supervity security policies and role-based permissions.
Managing the Integration
View Connection Status
From the left navigation bar, click the Integrations icon.
For Microsoft Teams you can view:
- Connection status
- Granted permission categories
- Last usage information
- Associated workflows and operators
Reconnect Teams
If Teams authorization expires or security policies change: Open the Integrations page from the left navigation bar. Select Microsoft Teams. Click Reconnect. Complete authorization again through the Microsoft portal.
Existing workflows and operators do not need to be recreated.
Removing the Teams Integration
You can remove the Teams connection from your Supervity workspace at any time directly from within the Supervity platform.
Steps to Remove
Log in to Supervity. From the left navigation bar, click the Integrations icon. Locate and select Microsoft Teams from the integrations list. Click Disconnect. Confirm the action when prompted.
Implications of Removal
Once removed:
- Supervity immediately loses all access to your Teams account and associated data
- No new Teams data will be read or posted after removal
- All active Teams connections within your Supervity workspace are terminated
- Scheduled or active workflows that depend on Teams will stop executing
- Teams-dependent workflow steps will fail safely with clear error messages
- Existing workflow definitions within Supervity are not deleted — only the active connection is terminated
- Historical execution logs remain available for auditing purposes
Disconnecting Teams does not delete workflow definitions, operators, or previously generated outputs.
How Your Data Is Handled After Removal
Data Handling on Removal:
- Supervity immediately loses access to your Teams account upon removal
- No new Teams conversations or data will be collected or processed after disconnection
- Temporary files processed during workflow execution are deleted after execution completes
- Teams access tokens and all account-related data are permanently deleted from Supervity's platform within 15 minutes of disconnection — no background access continues after removal
Auditing & Observability
All Teams activity performed through Supervity is logged.
Audit records include:
- Which operator requested access
- Which workflow executed the action
- Timestamp of execution
- Success or failure status
- Relevant inputs and outputs (sensitive values are redacted)
This supports compliance, troubleshooting, governance, and operational visibility.
Troubleshooting
If you encounter issues at any stage, refer to the steps below. For issues not covered here, contact the Supervity support team.
Authorization Failed During Setup
Likely Cause: Incorrect Microsoft account used, or corporate tenant policies restricting third-party applications.
Resolution:
- Ensure you are signed in to the correct Microsoft or Teams account.
- Verify with your organization's IT administrator that your account is allowed to authorize third-party applications (Admin Consent may be required).
- Return to Supervity → Integrations → Microsoft Teams and click Connect to retry.
- If the issue persists, contact your IT administrator.
Teams Shows Connected but Elements Are Missing
Likely Cause: Insufficient team memberships or Microsoft Graph scopes not fully authorized.
Resolution:
- Verify that the target channels, teams, or chats exist in Teams and that you are an active member.
- Confirm the account connected to Supervity has read/write permissions for the target team.
- Reconnect the integration via Integrations → Microsoft Teams → Reconnect to refresh permissions.
Connection Expired or Token Invalid
Likely Cause: Microsoft security policies may force token expiration or revocation.
Resolution:
- Go to Integrations → Microsoft Teams → Reconnect.
- Complete the Microsoft authorization flow again.
- Existing workflows do not need to be reconfigured after reconnection.
Workflow Cannot Access Teams
Likely Cause: Teams may have been disconnected, or workspace governance policies may restrict access.
Resolution:
- Confirm Microsoft Teams is still connected under the Integrations page.
- Verify the workflow has permission to use Teams within your workspace governance settings.
- Check that workspace policies allow Teams execution for the relevant operators or workflows.
Posting Messages Fails
Likely Cause: Channel moderation settings restrict posting, or the channel/chat has been deleted or archived.
Resolution:
- Verify that the target channel or group chat has not been archived or deleted in Microsoft Teams.
- Check channel settings to confirm that member postings are allowed and not limited by moderator-only options.
- Ensure you are not attempting to post messages with invalid attachments or formatting.
File Download or Sync Fails
Likely Cause: Target file does not exist, or permissions are restricted, or file size exceeds Microsoft Graph API limits.
Resolution:
- Verify the file path and file name are correct and still exist in your drive directory.
- Ensure the connected account has download privileges for the target file.
- Verify that the file size is within supported download limits.
Frequently Asked Questions
Q: Is my Microsoft password shared with or stored by Supervity?
No. Supervity uses Microsoft's standard OAuth 2.0 authorization flow. Your Microsoft password is never shared with or stored by Supervity. Only scoped access tokens are stored, and these are encrypted at rest using AES-256.
Q: What type of Microsoft accounts are supported?
Work or School accounts that have active Microsoft Teams licenses and API permissions enabled are supported. Personal Microsoft accounts may have limited support.
Q: Will I need to reconfigure my workflows after reconnecting Teams?
No. If you reconnect Teams due to token expiry or permission updates, existing workflow definitions and operators do not need to be recreated or reconfigured.
Q: What happens to my workflows if I disconnect or remove Teams?
Workflow definitions are not deleted when Teams is disconnected or removed. However, any workflow steps that depend on Teams will fail safely with clear error messages until Teams is reconnected.
Q: How do I authorize the Supervity Teams integration?
Log in to Supervity at Supervity, navigate to the Integrations page from the left navigation bar, locate Microsoft Teams, and click Connect. You will be redirected to Microsoft's authorization page where you can review and approve the requested permissions. After authorization, you will be redirected back to Supervity automatically. See the Adding the Teams Integration section above for full step-by-step instructions.
Q: Can I limit which channels Supervity can access?
Supervity requests only the permissions required for enabled capabilities, following least-privilege principles. You can review all requested access types during the OAuth authorization step before approving.
Q: Who do I contact if I have an issue with the integration?
Contact the Supervity support team. See the Support section below for full contact details, support hours, and SLA information.
Support
If you need assistance with the Microsoft Teams integration, visit the Support page.
Support Hours
- Monday to Friday, 9:00 AM – 6:00 PM IST
- Requests submitted outside business hours will be addressed on the next business day
First Response SLA
- All support requests receive an initial response within 24 business hours
Contact Information
| Contact Type | Details |
|---|---|
| Support | Support & Contact |
| Sales Inquiries | sales@supervity.ai |
| Contact Form | https://www.supervity.ai/contact-us |
| Website | https://www.supervity.ai |
| Privacy Policy | https://supervity.ai/privacy-policy |
| Terms of Service | https://www.supervity.ai/terms-of-service |
| Acceptable Use Policy | https://supervity.ai/acceptable-use-policy |
When Contacting Support, Please Provide
- Workspace name
- Account type used for authorization (Personal vs Work/School)
- Relevant workflow or operator information
- Error messages or screenshots when available
This helps the support team investigate and resolve issues more quickly.