- An Agent created in Cassidy
- Access to the Teams Developer Portal
- The ability to create a Microsoft Teams bot
- Permission to submit custom apps for approval in Microsoft Teams, or a Teams admin who can upload the app package for you
- Your Microsoft 365 Tenant ID
- A Teams admin who can approve the app after you submit it
How Microsoft Teams deployment works
Cassidy generates the Microsoft Teams app package for you. You create the bot in the Teams Developer Portal, paste Cassidy’s callback URL into the bot, download the app package from Cassidy, import the package into Teams, and submit the app for approval. Publishing the app in the Teams Developer Portal submits the app to your organization. A Teams admin must approve the app in the Teams admin center, then install it for users or make it available for users to install.Deploy your Agent
Open the Microsoft Teams deployment
Enter app details
- Short name — The app name shown in Teams. Microsoft requires 30 characters or fewer.
- Long name — Optional. Use this if your full app name is longer than the short name.
- Short description — A brief description of the app.
- Long description — A fuller description for app review.
- App color icon and App outline icon — The icons shown in Teams.

Create the bot in Microsoft Teams


Create a client secret


Save the bot credentials in Cassidy
- Bot ID — On the Teams Developer Portal Bot management page, copy the value from the Bot Id column for the bot you created. You can also paste the full bot page URL and Cassidy will extract the Bot ID for you.
- Client secret — Paste the one-time secret value from the previous step.
- Tenant ID — Paste your Microsoft 365 Tenant ID.

Download the Teams app package
.zip file that contains the Teams app manifest and icons. The app package includes your bot ID, personal chat support, group chat support, channel support, and file support.The app package also requests permission to read messages in the group chats and channels the app is added to, and to read group chat names. The Agent uses these permissions to read earlier messages in the conversation before it answers. A team or chat owner approves them when they add the app.
Import the app package
.zip file you downloaded from Cassidy.Cassidy already generated the app package with your bot configuration, so you do not need to manually add the bot after importing.
Submit the app to your organization


Return to Cassidy
Let the Agent read files in group chats and channels
This step is optional. By default, Microsoft Teams only sends files to the bot directly in 1:1 chats. To let the Agent read files attached to messages in group chats and channel threads, a tenant admin must grant the bot’s app registration theFiles.Read.All Microsoft Graph application permission.
Files.Read.All lets the bot read files in your organization’s SharePoint and
OneDrive using its own identity. Microsoft Teams only sends files to the bot
directly in 1:1 chats, so in group chats and channels the Agent needs this
permission to read any attached file, including on the message that mentions
it. Without it, the Agent still reads messages and lists the names of files it
could not read.Find the bot's app registration

Add the Files.Read.All permission


Files.Read.All, then click Add permissions.
Grant admin consent

Admin approval and installation in Teams admin center
After the app is submitted to your organization, a Teams admin must approve and publish it in the Teams admin center. Publishing makes the app eligible for your organization, but the admin still needs to decide who gets it.Open Manage apps
Review the app details

Publish the app

Install or make the app available
- Everyone — Install or make the app available for all users in the organization.
- Specific users or groups — Install or make the app available only for selected people or groups.
- No one — Keep the app unavailable until the admin is ready.

Update your Teams app
You can change the name, description, icons, and other details for an existing Agent app in the same Teams Developer Portal you used during setup..png file:- Color icon — A full-color, 192 × 192 px image
- Outline icon — A transparent, 32 × 32 px image with a white outline
Open your app
Update the app details
- Open Basic information to change the app name, descriptions, or other app details.
- Open Branding to replace the Color icon or Outline icon.

Increase the app version
1.0.0 to 1.0.1. Click Save.
Publish the update


Add chat history permissions to an existing app
Apps created before Cassidy supported chat history can only see messages that mention the Agent. To let the Agent read earlier messages and respond without a mention, add the permissions to your app:Open your app

Set the Application (client) ID

Open Permissions
Add the team permission
ChannelMessage.Read.Group.
Add the chat permissions
ChatMessage.Read.Chat and ChatSettings.Read.Chat.
Save and publish the update

Choose when the Agent responds
In Cassidy, open the Microsoft Teams deployment and choose a Response Mode. The Agent always responds to direct messages.- Always respond — The Agent replies to every message in the group chats and channels it’s added to, including every new channel post.
- Respond when mentioned, then reply to all messages in that thread — After someone @mentions the Agent in a channel post, it replies to every message in that post’s thread. Group chats have no threads, so there the Agent only replies when mentioned. This is the default for new deployments.
- Only respond when mentioned — The Agent replies only when someone @mentions it. Deployments created before response modes were added use this mode.
Chat with your Agent in Teams
In a channel
To use the Agent in a Microsoft Teams channel, mention the app using @ followed by its short name. Start a new post and @mention the Agent — it will respond in that post’s thread. Before it answers, the Agent reads the earlier messages in that post’s thread, including messages that did not mention it.
In a group chat
Add the app to a group chat, then @mention the Agent. Before it answers, the Agent reads the messages sent since it last replied, so it can follow the conversation. The first time it’s mentioned, it reads the most recent messages in the chat.In a direct message
Start a new direct message to the Agent for a private, ongoing conversation. The Agent has access to the full chat history in DMs, giving it more context for follow-up questions.
- After adding or removing the Agent, the Teams app list may take a moment to update
- Bots in private channels are not supported
- Bots cannot see the subject line of messages
- The Agent reads at most the 50 most recent earlier messages in a chat or thread
- The Agent cannot read images pasted directly into earlier messages
- Type
/clearto start a new conversation. The Agent will not read messages sent before it
