Teams Bots

Where

Dashboard sidebar → Settings → Connectors → Teams Bots.

What it does

A Teams bot is an Azure Bot of your own that represents one employee. Your team messages it in Teams, and the employee answers there.

One bot per employee. Add a second bot for a second employee. This is the longest connector to set up — it involves two Azure resources and an app installed in Teams — so plan a quiet half hour for the first one.

This is not Teams Impersonation. A bot speaks as itself; impersonation sends as a real connected Teams user.

The row shows how many bots are connected (0 connected until you add one).

What you will need

The product summarises it as a Quick Reference, and it is worth reading before you start:

The form fields are Bot Name, Tenant ID, Microsoft App ID and Microsoft App Password, all four required, then Add Bot.

You also need an Azure subscription — step 3 creates a resource, on the Free pricing tier — and, for step 9, a Teams administrator.

Create the bot, step by step

1. Create an Azure AD App Registration

1. Go to the Azure Portal → App Registrations.
2. Click New registration.
3. Enter a name, for example Brooke - Customer Support Bot.
4. Under Supported account types, select Accounts in this organizational directory only (Single tenant).
5. Leave the Redirect URI blank.
6. Click Register.
7. Copy the Application (client) ID and the Directory (tenant) ID.

2. Create a client secret

1. In the app registration, go to Certificates & secrets.
2. Click New client secret.
3. Add a description, for example Bot Secret.
4. Set the expiration to 24 months (recommended).
5. Click Add.

3. Create the Azure Bot resource

1. In the Azure Portal, choose Create Azure Bot.
2. Fill in the Bot handle, a unique identifier.
3. Select your Subscription and Resource group.
4. For Pricing tier, select Free.
5. Under Microsoft App ID, select Use existing app registration.
6. Enter the App ID from step 1.
7. Select Single Tenant as the app type.
8. Click Review + create, then Create.

4. Configure the messaging endpoint

1. In the new Bot resource, go to Settings → Configuration.
2. Set the Messaging endpoint to:

https://YOUR-INSTANCE/api/teams-bot-events

3. Click Apply.

5. Enable the Microsoft Teams channel

1. In your Azure Bot, go to Channels.
2. Click the Microsoft Teams icon.
3. Accept the Terms of Service.
4. Under Messaging, select the appropriate message types.
5. Click Apply.

6. Add API permissions (optional)

Only needed for proactive messaging, when the employee should be able to write first rather than only answer.

1. Back in Azure AD → App registrations, select your app.
2. Go to API permissions → Add a permission → Microsoft Graph.
3. Add these Application permissions:

User.Read.All
TeamsActivity.Send

4. Click Grant admin consent.

7. Add the bot in Geta.Team

1. In Settings → Connectors → Teams Bots, click + Add Bot.
2. Enter the Bot Name, usually the employee's name.
3. Paste the Tenant ID (Directory ID, step 1).
4. Paste the Microsoft App ID (Application ID, step 1).
5. Paste the Microsoft App Password (the client secret Value, step 2).
6. Click Add Bot.
7. Assign the bot to an employee.

8. Install the bot in Microsoft Teams

1. Click the download button next to your bot in the list — this gives you the manifest .zip.
2. In Teams, go to Apps → Manage your apps.
3. Click Upload an app → Upload a custom app.
4. Select the downloaded .zip.
5. Click Add.
6. Start a conversation with the bot: it is now handled by your AI employee.

9. Deploy to the whole organisation (admin only)

To make the bot available to everyone without each person installing it:

1. Go to the Teams Admin Center → Manage apps.
2. Click Upload new app and select the same .zip manifest.
3. Go to Teams apps → Setup policies.
4. Edit the Global (Org-wide default) policy.
5. Under Installed apps, click Add apps, find your bot, add it.
6. Click Save.

Policy changes may take up to 24 hours to reach all users.

Troubleshooting

"Invalid Microsoft App ID or App Password"

• Use the Directory (tenant) ID, not the Object ID.
• The client secret Value is not the Secret ID — use the Value.
• Check the secret has not expired.
• Confirm you selected Single tenant when creating the app registration.

"Upload custom app" is not available in Teams

Go to the Teams Admin Center → Teams apps → Permission policies and enable Upload custom apps for your organisation.

"manifestVersion property is missing"

Do not use the manifest from the Azure Portal, it is incomplete. Download the manifest with the button next to your bot in Geta.Team.

The bot does not respond to messages

• Check the messaging endpoint in Azure Bot → Settings → Configuration.
• Check the Microsoft Teams channel is enabled and healthy, green checkmark.
• Check an employee is actually assigned to the bot.

What breaks

The client secret has an expiry date, 24 months at most if you follow step 2. When it lapses the bot stops answering with no warning on the platform side. Write the date down the day you create it — this is what kills Teams bots long after a successful setup.