Microsoft Teams Integration

The raia Microsoft Teams integration lets employees communicate with their organization’s raia AI agents from Microsoft Teams — in team channels, personal chats, or group chats. A successful deployment has two required layers: the raia Microsoft Teams app must be installed or published in Teams, and a raia administrator must add and configure the Microsoft Teams Skill on one or more raia agents. Installing the Teams app alone does not assign an agent to a channel or authorize personal conversations.

App package version 1.0.2 defines a conversational bot for personal chats, team channels, and group chats, with file support enabled. Calling and video are not enabled.

The package advertises four commands in personal and group chats. These commands are not declared for team-channel scope.

• Approved raia Teams app package (.zip) — do not unzip it before upload.
• Microsoft Teams desktop or web, signed into the intended Microsoft 365 tenant.
• Custom app permission (required when an individual user sideloads the app).
• Active raia account — sign in to raia.
• A configured raia agent that should serve Teams users.
• Microsoft connection authorized on the agent’s Teams Skill.
• An access design: which teams, channels, group chats, or personal users may use each agent.

1. 01

   Choose the deployment method — user sideload or Teams admin publish.

2. 02

   Deploy the Teams app: upload package version 1.0.2 to the intended users.

3. 03

   Prepare the raia agent — create a new agent or open an existing one in the raia dashboard.

4. 04

   Add the Microsoft Teams Skill to the agent and connect the appropriate Microsoft account or tenant.

5. 05

   Authorize access — select the teams and channels the agent serves and, when permitted, the personal users who may contact it.

6. 06

   Save or publish the agent configuration so the latest is active.

7. 07

   Run acceptance tests in one configured channel and one personal or group chat.

8. 08

   Communicate availability to users: where the agent is available, what it does, and how to get support.

Use this procedure when your organization permits individual custom app uploads. The current Teams flow is Apps → Manage your apps → Upload an app → Upload a custom app.

1. 01

   Obtain the approved raia app package, e.g. raia-teams-app-v1.0.2-clean.zip.

2. 02

   Open Microsoft Teams (desktop or web) and sign in with your organization account.

3. 03

   Select Apps from the left navigation.

4. 04

   Select Manage your apps near the bottom of the Apps page.

5. 05

   Select Upload an app, then Upload a custom app.

6. 06

   Choose the .zip file — do not unzip the package first.

7. 07

   Review the app name, publisher, and requested access, then select Add or Install.

8. 08

   Select Open for personal use, or choose the appropriate team, chat, or channel when Teams offers a scope selector.

9. 09

   Optionally pin raia to the Teams app bar for frequent personal use.

Organization-wide publication is appropriate when sideloading is restricted or when administrators want centralized governance. An admin-uploaded app can take a few hours to become available to users.

1. 01

   Sign in to the Microsoft Teams admin center (admin.teams.microsoft.com).

2. 02

   Open Teams apps → Manage apps.

3. 03

   Select Upload new app, or Actions → Upload new app.

4. 04

   Upload the approved raia .zip package.

5. 05

   Open the app details and verify publisher, app ID, version, scopes, and availability.

6. 06

   Allow raia for the intended users or groups using your tenant’s app-management controls.

7. 07

   Optionally use an app setup policy to install or pin raia for selected users.

8. 08

   Wait for policy and catalog propagation, then test with a representative user account.

1. 01

   Sign in to the raia dashboard (raia2.com/auth/signin).

2. 02

   Create a new agent or open the agent that should communicate through Teams.

3. 03

   Open the agent’s skills or integrations area and add Microsoft Teams.

4. 04

   When prompted, connect the Microsoft account associated with the intended tenant.

5. 05

   Configure channel access — select the teams and channels this agent should serve.

6. 06

   If one-to-one use is allowed, enable personal chat and authorize the users who may message the agent.

7. 07

   If group-chat options are available, enable them only for the intended audience.

8. 08

   Review the selected agent, tenant, conversation scopes, and user/channel assignments.

9. 09

   Save, publish, or activate the updated agent configuration.

10. 10

    Test from Teams using the acceptance tests below.

Team channel

Open an authorized channel, start a new post, type @raia and select the raia app from the mention suggestions. After the mention, enter a clear request and send. Continue in the same thread to preserve conversational context.

Personal chat

Open Apps, search for raia, and select Open. Send a normal message to begin — an @mention is generally unnecessary in a one-to-one conversation. Use /status to inspect the active agent or /change-agent to switch.

Group chat

Add raia to the group chat, then mention @raia when addressing the bot. The /help, /status, /change-agent, and /start-new-conversation commands are declared for group-chat scope as well.

Working with files

Attach a file with the normal Teams attachment control and explain what you want the agent to do with it. File types, size limits, and processing behavior depend on the agent and organizational policy. Do not upload confidential or regulated information unless your organization has approved that use.

For updates, use a package with the same app ID and a higher semantic version. End users see Update in Apps → Manage your apps when an update is available; if Teams does not detect the replacement, remove the app from its installed scopes and upload the new .zip. For organization-published apps, open raia in Teams admin center → Teams apps → Manage apps and upload the newer package from the app details page.

To remove, an end user opens Apps → Manage your apps, expands raia, and removes it from each applicable scope. Removing and reinstalling a personal bot does not necessarily erase the prior bot conversation. An administrator can remove raia from the organization catalog from the app details page in the Teams admin center — notify users and raia administrators first, and record affected agent mappings.

Only grant raia access to the teams, channels, chats, users, and agents required for the approved business purpose. Apply least-privilege access, test with non-sensitive information, and review agent mappings when teams or responsibilities change. The app’s responses are governed by the organization’s raia configuration and permissions. Users should follow their organization’s data-classification, acceptable-use, retention, and AI policies when entering messages or sharing files.