Skip to main content
Connect Microsoft Teams to message Sammy for opportunity searches and pipeline questions, receive pursuit notifications as Teams messages, and schedule meetings with pursuit contacts.
This is a shared, org-wide integration. Connecting Microsoft Teams applies to your entire SamSearch organization; every team member shares the same connection and can see synced data. Connecting or disconnecting it requires the owner or admin role. SamSearch strongly recommends connecting with a dedicated work account (e.g. ops@yourcompany.com) rather than a personal account, so the connection and credentials persist if an individual leaves.
Microsoft Teams integration card in Account > Integrations showing the Connect Microsoft Teams button

​
What this integration does

  • Get pursuit alerts and @mentions in Teams, as direct messages
  • Notify your team on status changes, task/pursuit assignments, and amendment updates
  • Post a new leads digest and proposal/outline-ready alerts to two separate Teams channels
  • Chat with @Sammy directly from Teams
  • Schedule and join meetings with a pursuit contact directly from the contact row
Setup has three parts, and the middle one is the step most often missed. Part 1 authorizes SamSearch against your Microsoft 365 tenant. Part 1B — a separate, one-time admin consent step — is what lets the bot recognize your teammates; skipping it is the most common cause of “SamSearch doesn’t recognize my account” in Teams. Part 2 installs the SamSearch app inside Teams. All three are required before Sammy or notifications will work.

​
Part 1: Authorize SamSearch

1

Open Integrations

In the left sidebar, scroll to Account and click Integrations.
2

Find the Microsoft Teams card

Scroll to the Messaging & Notifications section. The Microsoft Teams card shows your current connection status.
3

Click Connect Microsoft Teams

Click Connect on the Microsoft Teams card. A dialog confirms this is a shared, org-wide connection — click I understand connect Microsoft Teams to proceed.
'This is a shared integration' confirmation dialog, warning that connecting Microsoft Teams applies to the entire organization and recommending a dedicated work account
4

Sign in and grant permissions

You’re redirected to Microsoft to sign in. Microsoft then shows a Permissions requested screen for SamSearch Teams Bot — it’s flagged unverified because the app hasn’t gone through Microsoft’s publisher verification. Review the requested permissions and click Accept.
Microsoft 'Permissions requested' screen for SamSearch Teams Bot (unverified), listing sign-in and profile access, with Cancel and Accept buttons
5

Confirm connected status

You’re returned to SamSearch and the Microsoft Teams card now shows Connected, along with a Configure button.
Microsoft Teams integration card showing Connected status, its feature bullets, and a Configure button
The sign-in in Part 1 only authorizes your account. For the SamSearch bot to recognize teammates when they DM it, or to deliver notifications and channel posts, a Microsoft 365 Global Administrator for your tenant needs to separately approve a one-time, tenant-wide consent — this is a Microsoft requirement for app-level bot access, not something SamSearch can skip.
1

Get the consent link

Ask your SamSearch contact for your tenant’s admin-consent link, or build it yourself if you’re the Global Admin: https://login.microsoftonline.com/{tenant}/adminconsent?client_id=0b04f91e-fe9c-4bb5-8f7c-00e0b4fe8ab9 — replace {tenant} with your Microsoft 365 tenant ID or domain (e.g. contoso.onmicrosoft.com).
2

Have a Global Administrator open it

Whoever holds the Global Administrator role in your Microsoft 365 tenant should open the link and sign in. If that isn’t you, forward the link to whoever is.
3

Click Accept

Microsoft shows a permissions screen for the SamSearch app requesting read access to basic user profiles — this is what lets Teams users be matched to SamSearch accounts. Click Accept.
After clicking Accept, the confirmation page can look like a browser TLS/certificate error. This is a known cosmetic issue and is harmless — as long as you clicked Accept, the consent was recorded. Don’t retry the flow repeatedly because of this page; it won’t undo the consent, but it also won’t tell you anything new.
If the bot still shows “I don’t recognize your SamSearch account yet” after admin consent has been granted, reconnect the Teams integration from the Integrations page. If that doesn’t resolve it, contact support with your Microsoft 365 tenant name.

​
Part 2: Install the SamSearch app in Teams

Click Configure on the connected Microsoft Teams card to open the Set up SamSearch for Teams wizard. It walks itself forward as you complete each step.
Set up SamSearch for Teams wizard showing the 4-step progress list and Step 1 of 4: Download the app package
1

Step 1 of 4 — Download the app package

Click Download package (.zip) — a small file (5 KB) your team adds to Microsoft Teams in the next step.
2

Step 2 of 4 — Upload it to Teams

  1. Open Microsoft Teams and click Apps in the far-left sidebar.
  2. At the bottom, click Manage your apps.
  3. Click Upload an app, then Upload a custom app.
  4. Select the samsearch-teams.zip file you just downloaded.
3

Step 3 of 4 — Get it approved

A quick check that whoever manages your Teams has SamSearch Allowed. New uploads are usually allowed automatically, so this is often just a look.If that’s you:
  1. Click Open Teams Admin Center.
  2. In the left sidebar, go to Teams apps → Manage apps.
  3. Search SamSearch and open it.
  4. Check its status shows Allowed. If it says Blocked, open the Actions menu (top-right) and click Allow.
Not seeing SamSearch in the list? Sign out of the Teams Admin Center and back in — Microsoft only refreshes it on a new sign-in.
If someone else manages Teams: click Copy exact steps for your IT admin to copy this step’s instructions to send them, then click It’s approved, next once they’ve confirmed it.
4

Step 4 of 4 — Add SamSearch in Teams

  1. In Microsoft Teams, click Apps in the far-left sidebar.
  2. Open Built for your org.
  3. Find SamSearch and click Add.
SamSearch detects this automatically — the wizard’s Waiting for SamSearch to appear in your Teams message flips to done on its own once it’s added, with no need to come back and confirm.

​
Part 3: Configure notifications

The same Configure panel (scroll down past the 4-step wizard) controls how notifications reach Teams.
Notification settings in the Configure panel: Direct messages toggle, Interactive buttons toggle, Events to send checkboxes, and Channel Posts section with two Teams channel link fields

​
Direct messages (personal, to each user)

  • Direct messages — toggle on to DM people their own mentions, assignments, replies, and reactions.
  • Interactive buttons — toggle on to add Reply and Mark read buttons to those notification DMs.
  • Events to send — checkboxes for exactly which events trigger a DM: Mentions, Replies, Reactions, Pursuit assignments, Task assignments, and Amendment updates. All are on by default; uncheck any you don’t want.

​
Channel Posts (shared, to a specific channel)

Unlike the DM events above, these two post to a Teams channel you choose — and each can go to a different channel: For each one, paste a Teams channel link into its field (in Teams: right-click the channel → Get link to channel), then click Save.
Channel posts also need SamSearch added to that channel’s team — in Teams: Manage team → Apps — separately from the org-level install in Part 2. The Part 2 install makes SamSearch and @Sammy usable across your Teams tenant; each individual channel you want posts delivered to needs the app added to it directly.

​
Part 4: Chat with @Sammy in Teams

Once connected, Sammy is available directly in Teams:
  • Direct message: open a chat with Sammy in Teams and ask it to find opportunities, start a journey, or answer questions about your pipeline.
  • Channel mention: type @Sammy in any channel it’s been added to, followed by your question or request.
Sammy responds in the same thread, so the rest of the channel can follow along.

​
Part 5: Schedule meetings with contacts

Microsoft Teams is the only messaging integration that supports scheduling meetings directly from SamSearch.
  1. Open a pursuit and go to its Contacts section.
  2. Find the contact row for the person you want to meet with.
  3. Click Schedule meeting.
  4. Choose a time and confirm — the Teams meeting is created and a calendar invite is sent to the contact.
  5. To join later, click Join meeting on the same contact row.

​
Troubleshooting

Sammy says “I don’t recognize your SamSearch account yet”
  • This almost always means the admin consent in Part 1B hasn’t been granted yet, or was granted but the connection needs a refresh. Confirm a Global Administrator has completed Part 1B, then reconnect the Teams integration from the Integrations page.
  • Also confirm your Teams sign-in email matches your SamSearch login email.
  • Still stuck after both? Contact support — a handful of cases have needed an engineering-side fix.
The admin-consent page looks like a TLS/certificate error
  • This is expected and harmless as long as Accept was clicked before the page appeared. It doesn’t mean consent failed.
SamSearch is stuck on “Blocked” in the Teams Admin Center
  • Open Teams apps → Manage apps, find SamSearch, open its Actions menu (top-right), and click Allow.
SamSearch isn’t in the admin center’s app list at all
  • Sign out of the Teams Admin Center and back in — it only refreshes the list on a new sign-in.
I don’t see Sammy in Teams
  • Confirm the integration shows Connected on the Integrations page (Part 1), that admin consent is granted (Part 1B), and that you completed Step 4 of the Configure wizard — adding SamSearch under Apps → Built for your org in Teams (Part 2). All three are required.
Notifications aren’t arriving as DMs
  • Check the Direct messages toggle and the Events to send checkboxes under Configure.
  • Confirm admin consent (Part 1B) is granted — this is a common root cause for missing DMs, not just the “don’t recognize your account” error.
Channel posts (new leads digest / proposal ready) aren’t arriving
  • Confirm a channel link is saved for that specific post type under Configure.
  • Confirm SamSearch has been added to that channel’s team via Manage team → Apps in Teams — the org-level install alone doesn’t add it to every channel.
Schedule meeting doesn’t create a Teams event
  • Confirm Part 1 (Connected) is complete — calendar access depends on the initial Microsoft authorization, not the Configure wizard.
  • Confirm the contact has a valid email address on file in the pursuit.
Still stuck? Contact support@samsearch.co with your SamSearch account email and your Microsoft 365 tenant name.