Microsoft Teams bot setup guide

Agents read conversations and write messages for your company. Anything a customer or the public sees, such as a sent email or a posted message, is tier 3, so it asks first unless you decide otherwise.

Ways to connect

Company admins connect apps, on the Integrations page in Everdeck: open Microsoft Teams bot, choose one of the ways below, follow its steps and fill in its fields. Everdeck checks what you enter before it saves anything, and asks you to confirm it’s you (your second factor) before you type any secret. How connecting works.

Your Azure bot registration (single tenant)

Your OAuth app.

This way uses the client ID and secret of an OAuth app you create for Microsoft Teams bot. There’s no sign-in page: Everdeck asks Microsoft Teams bot for a token with them.

1. In the Azure portal, create an Azure Bot. Under Type of App choose "Single Tenant" and let it create a new Microsoft App ID.
2. In the bot's Configuration, copy the Microsoft App ID and the App Tenant ID. Open "Manage Password" and create a client secret; copy its Value.
3. Under Channels, add Microsoft Teams.
4. In Everdeck, add an OAuth app for Microsoft Teams bot with the App ID as the client ID and the secret's Value as the client secret, then connect with the App Tenant ID here.
5. On Chat approvals, set up the Teams front door with this connection and paste the Messaging endpoint it shows into the bot's Configuration.
6. Add the bot to Teams with an app package (Teams Developer Portal > Apps > New app > App features > Bot, choosing this bot and ticking Upload and download files so people can send it files), and install it for your organisation.

Field	What to enter
Directory (tenant) ID	Text. For example 00000000-0000-0000-0000-000000000000.

The scopes Everdeck asks for:

• https://api.botframework.com/.default

Disconnecting deletes the access token Everdeck saved for this connection. The OAuth app's client ID and secret stay saved under OAuth apps in Everdeck and keep working at Microsoft Teams bot until you delete the app or rotate its secret there.

What agents can do

An agent uses an action only when its charter grants it, on the agent’s Tools tab, where you choose whether each one runs by itself (Auto), asks first or never runs. Each action has a risk tier: tier 3 actions, which customers or the public see, ask first unless you choose otherwise, and tier 4 actions (money, deleting things, access) always need a person. How tools and tiers work.

Actions marked Reads outside content return things people outside your company may have written. Agents treat what they read as information, never as instructions, and their riskier actions later in the same session need approval.

• Send a message to a conversationTier 3 · Externalmicrosoft_teams_bot_send_message

  Post a plain-text message in a Teams conversation the bot is part of (a personal chat, a group chat or a channel thread). region is the part of the conversation's serviceUrl after smba.trafficmanager.net/, such as amer, emea or apac.

• Reply to a messageTier 3 · Externalmicrosoft_teams_bot_reply_to_message

  Reply to one message (activity) in a Teams conversation the bot is part of.

• Edit a message the bot sentTier 3 · Externalmicrosoft_teams_bot_update_message

  Replace the text of a message the bot sent earlier.

• Delete a message the bot sentTier 3 · ExternalReads outside contentmicrosoft_teams_bot_delete_message

  Delete a message the bot sent earlier.

• List conversation membersTier 0 · ReadReads outside contentmicrosoft_teams_bot_list_members

  List the people in a Teams conversation the bot is part of, with their names and Entra object ids.

Testing, problems and disconnecting

Everdeck checks the connection when you save it. On the connection’s page in Integrations, Test checks it again at any time.

If Microsoft Teams bot later refuses the connection, for example because a key was deleted or a sign-in expired, the connection shows Needs attention on the Integrations page and the people who manage connections are told. Agents can’t use it until a company admin fixes it with Edit.

To stop agents using Microsoft Teams bot, open the connection and select Disconnect. Agents stop using it at once and its saved credentials are deleted. What else happens depends on how it was connected: each way above says.