Microsoft Teams 用の Rovo を設定する
Rovo を Microsoft Teams に接続して、チームがチャンネルやグループ チャットでアトラシアンの AI アシスタントを使用できるようにします。
Microsoft Teams 向けの Atlassian Rovo アプリは、Rovo との 1:1 のチャット、グループ チャットでのコラボレーション、チーム チャンネルでの作業など、日々の業務が行われている会話の中に Rovo の高度な AI 機能を直接もたらします。Rovo を活用することで、Microsoft Teams から離れることなく、回答をすばやく見つけたり、複雑なドキュメントを要約したり、Jira や Confluence の作業を作成、更新したりできます。
始める前に、次のものが揃っていることを確認してください。
Microsoft Teams アカウント: 組織によって Rovo アプリのインストールが許可されている Microsoft Teams テナントのアカウントです。
Atlassian アカウント: アクティブな Jira Cloud または Confluence Cloud のアカウント。
Rovo アクセス: Rovo が有効になっている 1 つ以上のアトラシアン サイト (例: your-site.atlassian.net) へのアクセス。組織で Rovo が有効になっているかどうかわからない場合は、アトラシアン管理者に問い合わせてください。
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.
After you install the app, you can use it in direct message, group chats and channels.
Microsoft Teams を開きます。
左側のサイドバーの [アプリ] に移動します。
Rovo を検索します。
追加 を選択します 。
Open Rovo. Rovo will send you a welcome card and automatically connect to your Atlassian site.
複数のアトラシアン サイトにアクセスできる場合は、ウェルカム カードの [サイトを切り替える] を選択します。
Choose your organization's site (for example, your-site.atlassian.net) and select Save.
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.
セットアップするには、次の手順に従います。
Add Rovo to the group chat or channel.
Mention Rovo, @Rovo, and ask a question.
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.
Rovo answers the original question.
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.
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.
機能 | 可能なこと |
自然言語検索 | Ask questions about your work in plain language. for example, "What is the status of the Apollo project?" or "Find the Q3 release notes." Rovo can search across Jira, Confluence and your connected third-party tools (such as, SharePoint, Figma, Google Drive) using your own permissions. |
プロジェクトの詳細と接続されたコンテンツの表示 | Describe a project or topic and Rovo will pull related Jira work items, Confluence pages and content from connected tools. See the full list of connectors. |
コンテンツの要約 | Confluence ページ、長いドキュメント、またはプロジェクトの更新情報をわかりやすい言葉で要約するよう Rovo に依頼できます。 |
Jira 作業項目の作成 | Ask Rovo to create work from your conversation. For example, "Create a bug for the login timeout in the Apollo project." Rovo will confirm the details before creating the work item. |
Jira 作業項目の更新 | Ask Rovo to update the status, assignee, priority, or other fields of a work item. Rovo will confirm the changes before applying them. |
Confluence ページの作成 | Ask Rovo to draft and publish a page. For example, "Write a meeting summary page for today's standup and publish it to the Team space." Rovo will preview the content and ask for confirmation before publishing. |
コンテンツの下書き | Ask for a structured draft you can copy into Confluence, an email, or a document. |
Act in connected tools | Ask Rovo to run supported actions in your connected third-party tools, using your own credentials. |
Learn how to use Rovo in group chats and team channels.
機能 | 可能なこと |
検索と Q&A | Ephemeral mode: @mention Rovo ask a question about your team’s work in across Jira, Confluence and your connected third-party tools Shared account mode: @mention Rovo ask a question about your team’s work in Jira and Confluence. |
チャット スレッドの要約 | @mention Rovo in a conversation or thread and ask for a summary. Grant read permission the first time you do this. |
Jira 作業項目の作成 | @mention Rovo to create work from the discussion. For example, "@Rovo create a task for the portal redesign discussion." Rovo confirms before creating it. |
Jira 作業項目の更新 | @mention Rovo to update work item details, status, assignee or priority from the conversation. |
Confluence ページの作成 | @mention Rovo draft and publish a Confluence page . For example, “Turn this discussion into a page. Rovo will confirm the page content before publishing. |
Refine and share an answer | In ephemeral mode, refine the reply or ask Rovo to clarify it, then select Post to chat to share it with everyone. |
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
Refer to this table to understand the actions supported by Rovo in the various modes.
操作 | モード |
|---|---|
検索と Q&A | Supported in direct messages, ephemeral mode, and shared account mode. |
要約 | Supported in direct messages, ephemeral mode, and shared account mode. |
Jira and Confluence actions | Supported in direct messages, ephemeral mode, and shared account mode. |
Third-party search | Supported in direct messages and ephemeral mode. |
Third-party actions | Supported in direct messages and ephemeral mode. |
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.
Use these text commands:
場所 | コマンド |
|---|---|
Direct message |
|
Group chat or channel |
|
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.
Microsoft 365 管理者がユーザーの組織向けに Rovo アプリを承認する必要がある場合があります。インストール方法の詳細については、こちらをご確認ください。
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 が対象の項目を返すには、ソース アプリ (Jira、Confluence、SharePoint など) でその項目を表示する権限が必要です。
具体的に指定する: 対象の URL をそのまま貼り付けるか、より具体的なキーワードを使用してみてください。
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 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.
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.
この内容はお役に立ちましたか?