Configure Rovo for Microsoft Teams

Rovo for Microsoft Teams works in 1:1 direct messages without any admin setup. To use Rovo in group chats and channels, an Atlassian org admin must complete a one-time configuration. This involves three steps: connecting your Atlassian site to a Microsoft tenant, granting Microsoft Teams permissions, and installing the app from the Microsoft Marketplace.

はじめる前に

Make sure you have the following before starting:

• Atlassian organization admin access

• Rovo enabled on your Atlassian site

• Access to admin.atlassian.com

• A Microsoft 365 account to connect your tenant (Microsoft Entra admin permissions are required for this)

• A Microsoft Teams admin available to grant consent (this can be you, or a separate person)

How users notify you to set up Rovo

When a user adds Rovo to a group chat or channel that hasn't been configured, Rovo automatically sends a message in the chat letting the group know it hasn't been set up yet. Users will see two options:

• Notify Admin — Rovo sends an email to all Atlassian org admins across every org the user belongs to. The user sees a confirmation once the email is sent.

• Admin Setup — opens the admin consent flow directly (useful if you're both a user and an admin).

The admin notification email has the subject: “Admin setup required — Enable Rovo for Microsoft Teams”. It contains two links:

• Configure — takes you directly into the admin consent flow in Microsoft Teams.

• Install for myself — installs the Rovo app for your own personal use in Teams.

Configure Rovo

Select Configure in the email (or the Admin Setup button from within a Teams conversation) to open the admin consent flow. You'll land on a homepage listing all the Atlassian orgs you're an admin for. Select the org you want to configure.

You'll see a setup page with three steps to complete.

Step 1: Connect your Atlassian site to a Microsoft tenant (mandatory)

This step links your Microsoft 365 tenant to your Atlassian organization and sets up the service account Rovo uses to read Jira and Confluence data in group conversations.

1a. Connect your Microsoft tenant

1. Select Start on Step 1. An intro screen outlines the required permissions and links to this support doc.

2. Select Next. You'll be prompted to sign in to your Microsoft tenant.

   • If you're already signed in, you can switch to a different account if needed.

   • Select Sign in to connect, complete the Microsoft login flow, and select Accept to authorize the connection.

3. Once signed in successfully, select Next.

4. Select the Atlassian site you want to connect. Only sites with Rovo enabled will allow you to proceed. Select Next.

1b. Create a service account

Rovo uses a service account in channels and group chats to search and surface information from Jira and Confluence on behalf of the team. You need to create this account in your Atlassian org and generate OAuth credentials for it.

1. Go to admin.atlassian.com and select your org.

2. In the left navigation, select Directory, then select Service accounts.

3. Select Create a service account and give it a recognizable name (e.g. Rovo Teams Bot).

4. Under Select app roles, assign the service account a User role for each Atlassian app you want Rovo to access (e.g. Jira, Confluence).

1c. Create OAuth credentials

1. From Service accounts, open the service account you just created.

2. Select Create credentials, then select OAuth 2.0.

3. Give the credential a name (e.g. rovo-teams).

4. Under Select scopes, select the filter Scope type: Classic

5. The 14 following scopes at a minimum must be enabled:

   • read:account

   • read:confluence-content.all

   • read:confluence-content.permission

   • read:confluence-content.summary

   • read:confluence-groups

   • read:confluence-props

   • read:confluence-space.summary

   • read:confluence-user

   • read:jira-user

   • read:jira-work

   • read:me

   • read:servicedesk-request

   • readonly:content.attachment:confluence

   • search:confluence

6. Review and select Create.

7. Save your Client ID and Client Secret. You will need both values in the next step. These are shown only once.

1d. Enter credentials in the consent flow

1. Return to the Rovo admin consent flow in Microsoft Teams.

2. Paste your Service Account Email, Client ID and Client Secret into the provided fields.

3. [完了] を選択します。

Once the credentials are accepted, the mapping between your Microsoft tenant and your Atlassian site is created.

Step 2: Grant Microsoft Teams permissions (mandatory)

For Rovo to summarize chats and perform actions in channels and group chats, it requires additional permissions from Microsoft. These are user delegate permissions and must be approved by a Microsoft Teams admin for the entire tenant.

1. Select Start on Step 2. A modal appears explaining the permissions Rovo requires (e.g. reading chat messages for summarization).

2. Choose the appropriate option based on your role:

Once permissions are granted, Rovo can respond in group chats and channels.

Step 3: Install (mandatory)

The final step in the setup makes the Rovo app available for users across your Microsoft Teams organization.

Option A: Org-wide/group installation (recommended)

Installing Rovo org-wide gives your users instant access, eliminates individual setup, and reduces admin support overhead. To set up:

1. In the Microsoft Teams Admin Center, go to Teams App and select Manage Apps.

2. Select Rovo, then select Users and groups.

3. Under 'Select to manage who this app...' select Installs.

4. Select the button Install app.

5. In the side menu that appears, under 'Install to' select Everyone (or specific users/group).

Option B: Per-user installation

If you’d prefer users to install the app individually, you will first need to ensure that Rovo is unblocked. To do this:

1. In the Microsoft Teams Admin Center, go to Teams App and select Manage Apps.

2. Select Rovo, then select Users and groups.

3. Select Edit availability.

4. Change the availability to 'Everyone' and select Apply. If you want to make Rovo for Teams only available to select users or groups, choose 'Specific users or groups'.

5. Confirm that Rovo's availability is set to Available to everyone.

Step 4: Pin the app (optional)

Although not mandatory for setup, we recommend pinning Rovo to the app bar to ensure users can easily find it, reducing confusion and minimizing admin support requests after rollout.

To pin the Rovo app to the app bar for your users:

1. Log in to the Microsoft Teams Admin Center.

2. Select Teams Apps, then select Setup policies.

3. Select Global (Org-wide default) to edit the policy.

4. Scroll to the Pinned apps section and select Add apps.

5. Search for Rovo and then select Add.

6. Drag the Rovo app to your desired position.

7. At the bottom of the screen, select Save.

Verify Rovo is working

After completing all three steps, go to any group chat or channel in Microsoft Teams and send a message mentioning @Rovo. Rovo should respond within a few seconds.

If you still see a "not configured" message, check the following:

• The Atlassian site you selected in Step 1 has Rovo enabled.

• The Client ID and Client Secret were entered correctly (re-enter them if unsure).

• Microsoft Teams permissions were successfully granted.