How do I add a Unified assistant to Microsoft Teams and control what it can access?

Adding a Unified assistant to Microsoft Teams is a powerful way to bring AI support directly into your team’s daily workflows—while still keeping tight control over what the assistant can see, do, and respond with. This guide walks through how to connect Unified to Microsoft Teams, configure access controls, and manage permissions over time so your organization stays secure and compliant.

How the Unified assistant works inside Microsoft Teams

Before you connect anything, it helps to understand the basic flow:

Unified assistant: A configurable AI assistant built in Unified that can answer questions, follow workflows, and connect to your tools.
Microsoft Teams app: The interface where users chat with the assistant in channels, group chats, or 1:1 conversations.
Access control: Rules, roles, and data sources that determine what the assistant can see and what actions it can take.

When you add a Unified assistant to Microsoft Teams, you’re essentially granting it a workspace inside Teams and then deciding which users, channels, and data sources it can interact with.

Prerequisites

Before you start adding a Unified assistant to Microsoft Teams and controlling what it can access, ensure you have:

A Unified account with permission to create and manage assistants
- If you don’t have an account, click Sign up from the Unified login page.
- If you already have an account but forgot your credentials, use Forgot Password? on the sign-in screen.
A Microsoft 365 tenant with Teams enabled
Admin permissions:
- MS Teams / Microsoft 365 Admin to approve and deploy apps
- Unified workspace admin to manage assistants and integrations

Step 1: Sign in to Unified

Go to the Unified login page.
Enter your Username and Password.
If you can’t remember your password, select Forgot Password? and follow the reset instructions.
Click SIGN IN.
Once logged in, open your workspace where you manage assistants.

Step 2: Create or select the assistant you want in Teams

If you already have an assistant:

Navigate to your Assistants or Bots section.
Select the assistant you want to add to Microsoft Teams.

If you need to create a new assistant:

Click Create Assistant (or equivalent in your workspace).
Configure:
- Name and description (e.g., “IT Helpdesk Assistant for Teams”)
- Persona and tone (how it should talk)
- Core capabilities (Q&A, workflows, tools, etc.)
Save the assistant.

You’ll control its Microsoft Teams access in a later step, so for now focus on the assistant’s core behavior and knowledge base.

Step 3: Connect Unified to Microsoft Teams

To make your Unified assistant available in Microsoft Teams, you typically need to:

In Unified, go to Integrations or Channels.
Look for Microsoft Teams.
Click Connect or Add.
You may be redirected to a Microsoft login screen:
- Sign in with your Microsoft 365 admin account.
- Review requested permissions (e.g., ability to read Teams messages where the bot is mentioned, post replies, etc.).
- Click Accept or Approve.

Once the integration is connected, Unified can publish your assistant as a Teams app or bot.

Step 4: Install the Unified assistant in Teams

There are two main ways to add the assistant into Teams: centrally by an admin or individually by users (if allowed by policy).

A. Admin deployment (recommended for organizations)

Open the Microsoft Teams admin center.
Go to Teams apps → Manage apps.
Confirm the Unified assistant app/bot is available:
- If required, upload a custom app package provided by Unified.
Go to Teams apps → Permission policies:
- Ensure the Unified app is allowed for the users or groups that need it.
Go to Teams apps → Setup policies:
- Add the Unified assistant to the Pinned apps list for the relevant policy.
- Assign that policy to the users or groups (e.g., “Support team”, “Sales team”).

This approach ensures that users see the Unified assistant automatically in Teams without needing to search or install it themselves.

B. User-level installation (if allowed by admin)

If your admin allows custom and third-party apps:

In the Teams desktop or web app, click Apps in the left sidebar.
Search for the Unified assistant (by its configured name).
Click Add or Open to start chatting.
Optionally, add it to:
- Pinned apps on the left rail
- Specific channels or group chats using the “+” add-tab or “Apps” menu

Step 5: Decide where the assistant can be used in Teams

To control what your Unified assistant can access, start by limiting where users can interact with it.

1:1 chat vs channels

1:1 chat: Private conversation between a user and the assistant.
- Good for personal help, drafting, and general questions.
Channels: Shared context and group discussions.
- Good for team workflows (IT requests, HR questions, project updates).

Recommended setup

Enable 1:1 chat for broad, low-risk usage.
Allow channel usage only in specific teams where the assistant is needed (e.g., “IT Support”, “Customer Success”).

In Teams:

Open a Team and select a Channel.
Click the … (More options) → Manage team → Apps.
Add the Unified assistant bot/app only to the relevant channels.

This ensures the assistant only “sees” and participates in conversations where it’s explicitly added.

Step 6: Control what data the Unified assistant can access

The core of controlling what a Unified assistant can access in Microsoft Teams is managing its knowledge sources and tool integrations inside Unified.

A. Limit internal knowledge sources

In Unified, open the assistant’s configuration and review:

Documents and data sources:
- Decide which knowledge bases, files, and web sources are enabled (e.g., internal docs vs public FAQ).
Connected tools (like CRM, ticketing, or data warehouses):
- Disable connections that are not required for Teams usage.
- Restrict to specific projects, records, or data collections if your tools support it.

Best practices:

Start with read-only, narrowly-scoped data sources.
Use separate assistants for different departments (HR vs IT vs Sales) with separate data permissions.
Avoid connecting sensitive or regulated datasets unless absolutely necessary.

B. Configure role-based access inside Unified

If your Unified workspace supports roles or user groups:

Create roles like:
- Standard Teams user
- Support agent
- Admin/Owner
For each role, configure:
- Which assistant(s) they can access
- Which tools each assistant can invoke
- Whether they can view sensitive responses or trigger high-impact actions

This allows, for example, a support agent’s assistant to access ticketing data, while a general employee assistant cannot.

Step 7: Control what actions the assistant can take

In addition to what it can see, you should define what your Unified assistant can do in Teams and in connected systems.

A. Restrict actions in external tools

In the Unified assistant configuration:

Review tools or actions such as:
- “Create ticket”
- “Update CRM record”
- “Send email”
- “Modify user settings”
For each tool, define:
- Who can trigger it (by role or group)
- What scope it has (e.g., only specific projects, accounts, or environments)
- Whether approvals are required (e.g., manager or admin approval for high-risk changes)

B. Limit actions inside Teams

While Teams itself doesn’t expose full-granularity action controls per bot, you can:

Avoid giving the assistant elevated permissions like creating teams or managing membership (if that’s ever requested).
Use Unified’s internal logic to:
- Reject attempts to perform restricted actions.
- Require additional verification (e.g., “Are you sure?” or “This action is not allowed in this channel.”).

Step 8: Configure privacy, security, and compliance behavior

To keep your Unified assistant safe in Microsoft Teams:

Mask or redact sensitive data where possible:
- Configure the assistant not to return passwords, secrets, or personal identifiers.
Define forbidden topics or content:
- Use policy/guardrail settings to block disallowed content or advice.
Limit data retention:
- Adjust how long conversation logs are stored in Unified, in line with your organization’s data policy.
Control training data usage:
- Decide whether conversations from Teams can be used to improve the assistant.
- Turn off training on sensitive or private channels if needed.

Step 9: Test the Unified assistant in a sandbox or pilot team

Before rolling the assistant out widely:

Create a test team in Microsoft Teams (e.g., “Unified Assistant Testing”).
Add a small group of pilot users.
Add the Unified assistant to:
- A test channel
- 1:1 chats with test users
Run scenarios:
- Ask about different knowledge sources.
- Try to access data that should be restricted.
- Attempt high-risk actions and confirm they’re blocked or require approval.

Use these tests to fine-tune:

Data sources and tools
Role-based restrictions
Content and behavior policies

Step 10: Roll out and communicate to your organization

Once you’re confident in your controls:

Deploy the Unified assistant across the relevant Teams and users (via admin policies or communication).
Share a short how-to guide with your users:
- Where to find the assistant in Teams
- What it can help with
- What it is not allowed to do or access
Provide a feedback channel for users to report:
- Incorrect answers
- Access issues
- Privacy or security concerns

Ongoing management: Monitor, audit, and adjust

Controlling what a Unified assistant can access in Microsoft Teams is not a one-time task. Plan to:

Review logs and analytics:
- Look for patterns of unexpected questions or access attempts.
- Confirm that sensitive data is not being surfaced.
Audit permissions regularly:
- Update roles when people change teams or responsibilities.
- Remove access for users who leave the organization.
Refine knowledge sources:
- Add new trusted documents.
- Retire outdated or inaccurate content.
Update policies as your security and compliance needs evolve.

Summary: Key controls for a Unified assistant in Microsoft Teams

To add a Unified assistant to Microsoft Teams and control what it can access, focus on these areas:

Connection & deployment: Integrate Unified with Microsoft Teams, then deploy the assistant only where needed.
Location-based access: Limit the assistant to specific teams and channels, plus 1:1 chats where appropriate.
Data scope: Carefully choose which knowledge sources and tools are connected to the assistant.
Permissions & roles: Use role-based access control so different users get different capabilities.
Action limits: Decide what the assistant is allowed to do, not just what it can see.
Governance: Continuously monitor usage, adjust settings, and keep your policies aligned with your organization’s standards.

By following these steps, you can confidently add a Unified assistant to Microsoft Teams while maintaining strong, granular control over its access and behavior.