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 give your team fast, conversational access to your content and tools—while still keeping strict control over what the assistant can see and do. This guide walks through how to connect Unified to Microsoft Teams and how to manage access so the assistant only uses the data and actions you approve.

Overview: Unified assistants in Microsoft Teams

A Unified assistant in Microsoft Teams sits alongside your everyday chats and channels, allowing users to:

Ask questions about your internal content, documentation, or knowledge base
Trigger workflows or actions you’ve configured in Unified
Collaborate with AI directly where work is already happening

As an admin, you remain in control of:

Which assistants are available in Teams
What data sources each assistant can access
What tools, actions, or APIs the assistant is allowed to call
Which users or groups can use each assistant

Prerequisites

Before you add a Unified assistant to Microsoft Teams, make sure you have:

A Unified account with admin or equivalent permissions
Access to your Microsoft 365 / Entra ID (Azure AD) tenant with permissions to install and manage apps in Teams
Any required approvals for third‑party apps in your organization’s Teams app store
Your Unified assistant already created and configured (or at least a plan for what it should do)

If you don’t yet have a Unified account, use the standard sign‑in/sign‑up flow:

Go to the Unified sign‑in page
Sign in with your existing username and password, or
Select Sign up if you don’t have an account yet
Use Forgot Password? if you need to reset access

Step 1: Create or choose an assistant in Unified

Start by making sure you have the right assistant configured in Unified before you bring it into Microsoft Teams.

Log in to Unified
- Use your username and password on the Unified sign‑in page.
- If you can’t access your account, reset it via Forgot Password?.
Navigate to the assistants area
- Open the dashboard and go to your assistants or workspaces section.
- Either create a new assistant or select an existing one that you want to use in Teams.
Define the assistant’s purpose
Clarify what this assistant should do in Teams, such as:
- Answer questions about internal documentation
- Help with HR or IT FAQs
- Support customer‑facing teams with product info
- Trigger internal workflows, tickets, or approvals

This clarity will inform which data sources and permissions you allow in later steps.

Step 2: Connect Unified to Microsoft Teams

Once your assistant is ready, connect Unified to your Microsoft 365 environment so it can operate inside Teams.

Open the integrations or channels section in Unified
- Look for a section named Integrations, Channels, or Connections.
- Find the Microsoft Teams integration.
Start the Microsoft Teams connection
- Click Connect, Install, or Add to Teams for the Microsoft Teams option.
- You will be redirected to a Microsoft sign‑in / consent screen.
Grant required permissions
Unified will request permission to operate as an app in your Teams environment. Typical permissions can include:
- Reading basic profile information of users who interact with the assistant
- Sending and receiving messages in Teams
- (Optionally) Access to certain resources if you later enable them, such as SharePoint or OneDrive through Unified
Complete the consent flow
- Sign in with a Microsoft account that has permission to install apps for your tenant (often a Teams or Microsoft 365 admin).
- Accept the requested permissions after reviewing them carefully.

After this, Unified will be authorized to create and manage an assistant app in your Teams environment.

Step 3: Add the Unified assistant app into Teams

Next, you’ll make the Unified assistant available inside Microsoft Teams for you and, optionally, your users.

Open Microsoft Teams
- Use the desktop app or web version.
Find the Unified assistant app
- Click Apps in the left sidebar.
- Search for your assistant by the name you configured in Unified (or the Unified app if it’s a general container).
Add the app
- Select the assistant app and click Add to pin it to your Teams sidebar.
- Optionally, add it to a specific team or channel if you want the assistant to be available in group discussions.
Pin for quick access (optional)
- Right‑click the app icon in the sidebar and choose Pin, so the assistant is always visible.

At this point, you should be able to open a chat with the Unified assistant and start interacting with it.

Step 4: Control what the Unified assistant can access

The most important part of connecting Unified to Microsoft Teams is controlling what the assistant can see and do. This is handled primarily within Unified, with additional controls in Teams.

4.1 Configure data sources in Unified

Within Unified, your assistant’s knowledge comes from the data sources you connect. To control access:

Open the assistant settings in Unified
- Navigate to your chosen assistant.
- Look for a Knowledge, Data Sources, or Content section.
Add only the sources you need
Common sources might include:
- Uploaded files (PDFs, docs, spreadsheets)
- Internal wikis or documentation portals
- SharePoint sites or OneDrive folders
- Ticketing systems, CRM, or other business tools via integrations
Limit the scope of each source
- Restrict to specific folders, spaces, or collections instead of “entire account” where possible.
- Use least‑privilege access: if the assistant is for HR FAQs, connect only HR knowledge, not all company content.
Disable sources you don’t want used in Teams
- If the assistant already has access to sensitive or internal‑only sources that shouldn’t be exposed in Teams, disable or remove them for this assistant.

4.2 Set tools and action permissions

If your Unified assistant can take actions (like creating tickets, sending emails, or updating records), you should explicitly control which tools it can use:

Open the assistant’s tools / actions settings
- Look for a Tools, Actions, or Capabilities tab in your assistant’s configuration.
Enable only required tools
- Turn on the specific tools your Teams users need, such as:
  - “Create IT support ticket”
  - “Log customer feedback”
  - “Summarize meeting transcript”
Disable risky or unnecessary actions
- Turn off tools that:
  - Modify critical systems
  - Access highly sensitive data
  - Trigger external communications if not needed (e.g., mass email)
Limit access per assistant
- If you have multiple assistants, configure each one with different tools appropriate to its purpose and audience.

4.3 Enforce user‑ and group‑based access

You can combine Unified’s assistant configuration with Microsoft Teams and Entra ID (Azure AD) controls:

Restrict who can install or use the assistant in Teams
- In the Microsoft Teams admin center, open Teams apps > Manage apps.
- Find the Unified assistant app.
- Use app permission policies to:
  - Allow only certain users or security groups to use the app
  - Block it for others if needed
Align content access with user permissions
- If Unified connects to systems like SharePoint or OneDrive, make sure:
  - Document‑level or folder‑level permissions still match your intended audience
  - Sensitive content remains restricted at the source
Use separate assistants for different audiences (recommended)
- Example:
  - One assistant for all employees with general company FAQs
  - Another internal‑only assistant for HR or Finance with restricted access
- Connect each assistant to different Teams apps or channels as appropriate.

Step 5: Configure privacy, security, and data handling

To maintain compliance and trust, review how the Unified assistant handles data:

Review logging and conversation history
- Decide whether user queries and responses are stored and for how long.
- If Unified allows it, adjust retention settings to match your company policy.
Mask or redact sensitive data where possible
- If available, enable features that:
  - Mask personally identifiable information (PII)
  - Redact sensitive terms in logs or analytics
Clarify what the assistant can’t access
- Clearly communicate to users which types of information the assistant is not connected to (e.g., payroll systems, legal archives) to discourage oversharing.

Step 6: Test the assistant in Teams before broad rollout

Before enabling the Unified assistant across your organization, thoroughly test its behavior in Microsoft Teams.

Create a pilot group
- Select a small group of users (e.g., IT, HR, or a single department) to try the assistant.
Run realistic test scenarios
- Ask common user questions.
- Try edge cases, including questions that should not be answerable due to access restrictions.
- Trigger any allowed actions and confirm they behave as expected.
Check that access controls work
- Confirm the assistant:
  - Can only see the content sources you configured
  - Cannot access sensitive areas you explicitly excluded
  - Doesn’t perform actions outside of its allowed tools
Adjust configuration as needed
- If the assistant is too limited, carefully add more sources or tools.
- If it’s too permissive, remove or restrict access until it matches your security requirements.

Step 7: Roll out and manage the assistant over time

After testing, you can roll out the Unified assistant more broadly and maintain control as your needs evolve.

7.1 Deploy to more users and teams

Use Teams app setup policies to pre‑install or pin the assistant for certain groups.
Add the assistant to additional channels where its knowledge is most useful (e.g., “Helpdesk” or “Onboarding”).

7.2 Monitor usage and refine access

Review logs, analytics, or usage metrics in Unified (if available) to see:
- Which questions users are asking
- Where the assistant is helpful vs. where it struggles
Based on insights:
- Add missing documentation or knowledge sources
- Tighten or broaden access if needed

7.3 Regularly review security and compliance

Periodically audit:
- Connected data sources
- Enabled tools and actions
- Teams and Entra ID app policies
Update configurations if org policies, regulations, or data sensitivity change.

Best practices for controlling what the Unified assistant can access

To keep your Unified assistant in Microsoft Teams both useful and safe, follow these guidelines:

Use least‑privilege access
Always connect the minimal set of data sources and tools required for the assistant’s purpose.
Segment assistants by use case
Create different assistants (and Teams apps) for different functions—e.g., general support vs. confidential HR—to keep access clearly separated.
Align with existing permissions
Ensure data source permissions (SharePoint, OneDrive, etc.) match or exceed what the assistant is allowed to surface.
Document and communicate boundaries
Let users know what the assistant can and cannot access so they understand how to use it safely.
Review regularly
Schedule periodic reviews of the assistant’s configuration, especially when teams, tools, or content repositories change.

By connecting Unified to Microsoft Teams with clear access controls, you enable powerful, AI‑driven assistance while preserving security and governance. Configure your assistant in Unified, limit it to the right sources and tools, apply Teams app policies for user access, and continuously review usage to keep everything aligned with your organization’s standards.