Slack消息无法送达Azure：BotFramework与Slack通信故障排查请求

Hey Thomas, let’s walk through the most likely culprits here—since your first test bot worked perfectly, this is almost certainly a configuration misstep with your new bot, not code (which lines up with your hunch). Here’s where to start digging:

• Double-check Slack credentials in Azure Bot Service
  It’s super easy to mix up credentials between your test bot and new bot. Head to Azure Portal > Your New Bot > Channels > Slack > Configure, and cross-verify every field (Client ID, Client Secret, Verification Token, Bot User OAuth Token) against your new Slack app’s settings (Slack API > Your App > Basic Information for tokens, OAuth & Permissions for the bot token). Even one wrong character will silently block messages without triggering an error.

• Validate Slack App Event Subscriptions
  For your new Slack app, confirm:

  • Event Subscriptions are toggled On
  • The Request URL points exactly to your bot’s Azure endpoint: https://<your-bot-name>.azurewebsites.net/api/messages
  • You’ve subscribed to all required bot events (like message.channels, message.im) and saved the changes. Slack won’t send messages if events are missing or the URL isn’t properly validated—each app needs its own setup, even if your test bot worked.

• Recheck Azure Slack Channel Connection Status
  In Azure’s Channels page for your bot, make sure the Slack channel is marked Connected. Sometimes, credential entry looks correct but the connection fails silently due to a temporary glitch. Try disconnecting and re-connecting the channel to force a fresh validation.

• Dig into Azure App Service Logs
  Even if the Azure Portal shows no errors, hidden issues might pop up in the app service logs. Go to Azure Portal > Your Bot’s App Service > Log Stream, send a test message from Slack, and watch for 4xx/5xx errors, invalid token warnings, or route mismatches. The endpoint might return a 200 OK but fail to process messages if there’s a subtle route misconfiguration (unlikely if your code matches the test bot, but worth checking).

• Confirm Slack Bot Scope Permissions
  Ensure your new Slack app has all necessary bot scopes (like chat:write, channels:history, im:history). If you copied settings from your test app but forgot to re-add scopes when creating the new app, Slack will silently drop messages. Head to Slack API > Your App > OAuth & Permissions > Bot Token Scopes, verify the scopes, then reinstall the app to your workspace to apply changes.

• Verify Workspace Installation
  It sounds obvious, but double-check that you’ve installed the new Slack app to your workspace. If you created the app but skipped the installation flow, Slack won’t route messages to it. Check Slack API > Your App > Install App—if you see "Install to Workspace" instead of "Reinstall", run through that process.

Since neither platform is throwing errors, the issue is almost certainly a silent configuration block—start with credential and event subscription checks, those are the most common pitfalls when deploying a second bot.

内容的提问来源于stack exchange，提问作者Thomas