Using Rovo for Microsoft Teams

The Atlassian Rovo app for Microsoft Teams brings Rovo's AI-powered intelligence directly into the conversation where work happens - whether you're chatting 1:1 with Rovo, collaborating in group chats, or working in team channels. Rovo helps you quickly find answers, summarize complex docs, and create and update work in Jira and Confluence, all without leaving Microsoft Teams.

Requirements

Before you begin, make sure you have the following:

• Microsoft Teams account: An account in a Microsoft Teams tenant where your organization allows the Rovo app to be installed.

• Atlassian account: An active Jira or Confluence Cloud account.

• Rovo access: Access to at least one Atlassian site (for example, your-site.atlassian.net) where Rovo is enabled. If you're unsure whether Rovo is enabled for your organization, contact your Atlassian administrator.

• Admin setup (for shared account replies only): An Atlassian org admin must complete the Microsoft Teams to Atlassian tenant connection and create a service account. Rovo works in channels and group chats without this, using ephemeral replies.

Install Rovo

After you install the app, you can use it in direct message, group chats and channels.

• Open Microsoft Teams.

• Go to Apps in the left sidebar.

• Search for Rovo.

• Select Add.

Set up Rovo for direct messages

• Open Rovo. Rovo will send you a welcome card and automatically connect to your Atlassian site.

• If you have access to multiple Atlassian sites, select Switch site in the welcome card.

• Choose your organization's site (for example, your-site.atlassian.net) and select Save.

Set up Rovo for group chats or channels

Bring Rovo into any group chat or team channel to work with your team. Each group chat and channel is set up independently, so different conversations can use different sites or reply modes.

To set up:

1. Add Rovo to the group chat or channel.

2. Mention Rovo, @Rovo, and ask a question.

3. The first person to @mention Rovo sees a private setup card.
   Choose the Atlassian site and how Rovo replies (ephemeral or shared account), then select Save.

4. Rovo answers the original question.

Choose how Rovo replies

You choose one of the following modes:

• Ephemeral (default): Rovo replies privately to the person who asked, using that person's own Atlassian access. They can refine the answer or ask Rovo to clarify it, then select Post to chat to share it with everyone. You may want to choose this mode for everyday team work, when people need answers based on their own access, or when they want to check an answer before sharing it.

• Shared account: Rovo replies publicly using a shared account, so everyone in the conversation sees the same answer. An admin sets this up by configuring Rovo for Microsoft Teams. Select this mode when you want everyone to get the same answer from the same content, such as a support or help channel.

You can always change this later, by typing @Rovo configure in that conversation.

What can I use Rovo for in Microsoft Teams?

1:1 direct messages with Rovo

The simplest way to interact with Rovo is through a direct message (DM). Rovo acts as a unified AI assistant, pulling answers from Jira, Confluence, SharePoint, Figma, Google Drive, and other tools you’ve connected to Rovo. Replies are private to you and use your own permissions.

Rovo in group chats and team channels

Learn how to use Rovo in group chats and team channels.

Access and visibility

Rovo replies are visible to:

• Only you in direct messages

• Only you in ephemeral mode (until you post it to the chat)

• Everyone in the conversation when using the shared account mode

Rovo uses the following access:

• Your access in direct messages

• Your access in ephemeral mode

• Access of the shared account in shared account mode

Supported actions

Refer to this table to understand the actions supported by Rovo in the various modes.

Rovo always respects your organization's existing access controls. Direct messages and ephemeral replies use your own permissions, no service account is involved. Shared account replies use the shared account's permissions to search and plan, and the individual user's permissions to run actions.

If your team uses shared account replies, make sure the service account has read access to all relevant Atlassian apps (Jira spaces, Confluence spaces, and other connected Atlassian tools such as Loom). How to set up the service account.

Commands and configuration

Use these text commands:

Safety and permissions

• Your access always applies: Rovo only returns content the account in use is allowed to see, and never runs an action you don't have permission to perform.

• Nothing is shared without your permission: In ephemeral mode, only you see the reply until you select Post to chat.

• Confirmation before actions: Rovo shows a preview and asks for confirmation before creating or updating any Jira work item or Confluence page. You are always in control.

Troubleshooting

Can't find the Rovo app in Microsoft Teams?

Your Microsoft 365 admin may need to approve the Rovo app for your organization. Read the Install instructions detailed here.

Getting wrong or missing answers?

You may be connected to a different site. Type configure in the Rovo DM chat to switch sites. Each group chat and channel has its own site setting, mention @Rovo configure in that conversation to change it there.

Rovo says it can't find something?

• Check your site: Make sure you're connected to the site where the content exists.

• Check your permissions: You must have permission to view the item in the source app (Jira, Confluence, SharePoint, etc.) for Rovo to return it.

• Be specific: Try pasting the direct URL or using more specific keywords.

Other people can’t see Rovo’s answer

The conversation may be using ephemeral mode where replies are private to the person who asked. Select Post to chat to share the answer, or mention @Rovo configure to switch to a shared account.

Third-party search or actions aren't working in a group chat or channel?

Third-party search and actions aren't available with a shared account. Mention @Rovo configure and switch to ephemeral mode, or ask Rovo in a direct message instead.

Rovo can't plan actions when using a shared account?

The service account needs read (Browse) access to the corresponding Jira spaces or Confluence spaces. Ask your Atlassian admin to verify the service account's permissions and scopes. This doesn't affect ephemeral replies, which use your own access.