Overview
This guide is for workspace admins setting up the Microsoft Teams integration for their team in Revo. If you're looking for how to use the bot once it's installed, see "Using Revo in Microsoft Teams" instead.
You'll need:
Workspace admin rights in Revo.
Permission to install apps in your Microsoft Teams tenant (or the ability to ask a Teams admin to do it).
About 5 minutes.
Step 1 — Install the Revo app in Microsoft Teams
In Microsoft Teams, open the Apps panel and search for Revo.
Click Add to install the app to your Teams tenant.
When prompted, choose the team and channel where Revo should live. You can add Revo to more channels later.
Your tenant administrator will be asked to approve the permissions Revo needs. Approve the consent dialog.
What Revo asks for:
The ability to receive and reply to messages it's addressed in.
The sender's display name and Teams user identifier so conversations can be attributed.
Revo does not ask for access to user calendars, files, OneDrive, SharePoint, mail, or directory data.
Step 2 — Open the Microsoft Teams integration in Revo
Sign in to the Revo web app.
Open Settings from the left sidebar.
Under Connectivity, click Integrations. You'll see the full list of integrations for your workspace.
Find Microsoft Teams in the list and click the row to open its settings panel.
From here you configure three things: which notifications Revo sends, which channel they land in, and what the bot is allowed to do per channel.
Notification Settings
Under Notification Settings — "Choose which notifications to send to Teams" — turn on the event types you want Revo to post into your default notification channel:
Toggle | Fires when |
New project created | A new project is created in your Revo workspace. |
Issue created | A new issue is opened. |
Comment added to an issue | Someone comments on an issue. |
Issue is assigned to someone | An issue is assigned (or re-assigned). |
Notifications are one-way. Replying to a notification post in Teams does not feed back into Revo unless the reply also @-mentions the bot.
Default notification channel
Use the Default notification channel dropdown to pick the Teams channel where Revo should post notifications. All the event types you enabled above land in this one channel.
You can change this at any time — the next notification will respect the new setting. If no channel is selected, notifications will not be sent.
Channel Permissions
Under Channel Permissions — "Configure read, write, and workflow permissions for each channel" — Revo shows every Teams channel it's been added to. For each channel you control three independent toggles, represented by the three icon buttons:
Icon | Permission | What it controls |
👁️ Read | Read | Whether the bot will respond at all in this channel. If off, the bot replies with a short "I don't have access" message and a link back to this settings page. |
✏️ Write | Write | Whether the bot is allowed to create or modify things in Revo (issues, projects, comments, statuses) based on requests from this channel. Turn this off for channels where you want Revo to answer questions but not take action. |
🔀 Workflows | Workflows | Whether Revo workflows (automations) can be triggered by activity in this channel. |
When all three are on, the row shows "Full access: Read, Write, and Workflows". You can mix and match — e.g., Read on and Write off for a read-only channel.
Common patterns:
Read-only channel: Read on, Write off. Good for broadcast or customer-facing channels where the team wants answers but not bot-initiated changes.
Full-access engineering channel: all three on. Revo can answer questions, create issues, and trigger workflows.
Paused channel: Read off. Bot won't respond at all.
Channels only. These permissions apply to channel messages where the bot is @-mentioned. Revo in Microsoft Teams is used via channel @-mentions — not via 1:1 chats.
Adding Revo to additional channels
When you install the Revo app in a new channel in Microsoft Teams, the channel shows up under Channel Permissions in the integration settings. Set the three toggles for that channel and you're done.
If a channel isn't listed right after you add the bot in Teams, mention the bot once in that channel — the first mention registers the channel with Revo.
What your users will see
In channels: the bot responds only when someone @-mentions it. Microsoft Teams does not forward silent channel traffic to the bot, so Revo cannot read messages it was not addressed in.
In threads: Revo replies in the same thread. It remembers the thread's conversation so follow-up questions work naturally.
When the bot lacks permission in a channel: Revo posts a short "I don't have access" message in the conversation, with a link back to this settings page. Microsoft Teams bots cannot send ephemeral/private messages, so that reply is visible to others in the thread.
Point your users at the "Using Revo in Microsoft Teams" article for the end-user walkthrough.
Disconnecting and offboarding
Two ways to disconnect, depending on how complete you want the removal to be:
Disconnect from the Revo web app. In Settings → Integrations, open the Microsoft Teams row and disconnect. Revo immediately stops responding to or receiving Teams traffic for your workspace. The connection is marked deleted; historical conversation data is removed per your contracted retention schedule.
Remove the app from Microsoft Teams. In the Microsoft Teams admin center (or as a tenant admin inside Teams), uninstall the Revo app. This revokes the consent Microsoft has on file for the bot.
Doing both is the cleanest offboarding. Doing either one by itself is sufficient to stop the bot from acting on your tenant.
Disconnecting the integration does not delete the work your team has created inside Revo (issues, projects, documents). To fully terminate your Revo account, contact Revo support.
Troubleshooting
Symptom | Likely cause / fix |
The bot doesn't respond when mentioned in a channel. | Read is off for that channel, or the channel isn't registered yet. Open the integration settings and enable Read, or mention the bot once to register the channel. |
The bot says it doesn't have write access. | Write is off for that channel. Flip it on if you want the bot to create or modify items from that channel. |
Expected notification never arrived. | Check that the notification toggle for that event type is on, and that a Default notification channel is selected and accessible to the bot. |
Notifications are landing in the wrong channel. | Change the Default notification channel from the Microsoft Teams integration settings. |
Users say the "no access" message is visible to the whole channel. | Correct — Microsoft Teams bots cannot send ephemeral/private messages, unlike Slack. To avoid the message entirely, turn Read off for that channel (the bot simply won't respond) or enable the needed permission. |
Bot was working; stopped working recently. | Check that the Microsoft OAuth token hasn't been revoked in your tenant (Azure AD → Enterprise applications → Revo). Reconnect from the Revo web app if needed. |
Something else. | Contact Revo support. |
Security & privacy
For a full security and privacy overview (authentication, data handling, subprocessors, retention, offboarding commitments), see the Data Privacy & Security article or ask your Revo account team for the Revo for Microsoft Teams — Security & Privacy Overview document.
Highlights:
Microsoft authenticates every inbound message to the bot using a signed token. Revo rejects anything that fails validation.
The bot can only post into conversations that initiated the interaction — it cannot broadcast into arbitrary channels.
Revo does not access files, calendars, email, OneDrive, SharePoint, or directory data.
All traffic is over TLS 1.2+; conversation history is stored encrypted at rest.