Skip to main content
Connect Microsoft Teams to let Duckie respond to messages in your Teams workspace.

Capabilities

Setup

Prerequisites

  • Microsoft 365 admin access or approval
  • Teams workspace with bot permissions enabled

Connect via OAuth

  1. Go to Settings → Connections in Duckie
  2. Find Microsoft Teams and click Connect
  3. Sign in with your Microsoft 365 account
  4. Grant the requested permissions
  5. You’ll be redirected back to Duckie
Your Microsoft 365 admin may need to approve the Duckie app before you can connect.

Using as a Deployment Trigger

Deploy an agent to Teams:
  1. Go to Deploy
  2. Click Create Deployment
  3. Select your agent
  4. Choose Microsoft Teams as the trigger
  5. Configure the trigger:

Trigger Options

Adding to Channels

After deployment, add Duckie to Teams channels:
  1. Go to the Teams channel
  2. Click + to add a tab or app
  3. Search for “Duckie” and add it
  4. Configure which messages trigger responses

Available Tools

Best Practices

Enterprise Approval Process

Work with your IT team to approve Duckie:
  1. Submit Duckie for admin approval
  2. IT reviews requested permissions
  3. Once approved, all users can add Duckie

Use Dedicated Channels

Create channels like “IT Support” or “HR Questions” specifically for Duckie interactions.

Integrate with Existing Workflows

Teams users often have established workflows — position Duckie as a helper in channels they already use.

Example Use Cases

IT Helpdesk

Deploy to an IT support channel to answer common questions about software, VPN, passwords, etc.

HR Questions

Let employees ask about PTO policies, benefits, and company procedures.

Sales Enablement

Help sales teams quickly find product information and competitive intel.

Troubleshooting

”App not approved”

  • Contact your Microsoft 365 admin
  • Request approval for the Duckie app
  • Admin can approve in the Teams Admin Center

”Bot not responding”

  • Verify Duckie is added to the channel
  • Check deployment mode (Live vs Testing)
  • Ensure trigger is configured correctly

”Permission denied”

  • Re-authenticate the connection
  • Verify your account has access to the channels