Bot configuration config/fetch returns same channel ID when switching channels within same team

Summary

When invoking a bot’s configuration flow (configuration.fetchTask) via an @mention-based settings entry point across different channels within the same Team, the request body consistently contains the same channelId, even after switching channels.

https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/bot-configuration-experience?tabs=teams-bot-sdk1%2Cteams-bot-sdk2%2Cteams-bot-sdk3

This makes it impossible to reliably determine which channel initiated the configuration.

Environment

• Microsoft Teams (desktop client)
• Bot installed at team scope
• Same Team, multiple channels
• Bot supports team scopes.
• Configuration enabled via manifest:
  

  "configuration": {

    "team": {

      "fetchTask": true

    }

  }

Steps to Reproduce

1. Install the bot into a Team with multiple channels
2. Navigate to Channel A
3. Invoke the bot configuration using an @Bot settings / configuration entry point
4. Observe the incoming config/fetch request payload
5. Note the channelId in the request body
6. Switch to Channel B (same Team)
7. Invoke the same configuration entry point again
8. Observe the incoming config/fetch request payload

Expected Behavior

The config/fetch request body should include a channel identifier corresponding to the channel where the configuration was initiated, e.g.:

• channelData.channel.id
• or another channel-scoped identifier that uniquely identifies the initiating channel

Actual Behavior

• The config/fetch request body always contains the same channel ID
• The channel ID does not change when switching channels
• The value appears to be:
  • either the Team’s General channel
  • or a cached / team-level channel context
• As a result, the bot cannot determine which channel the user intended to configure.

Impact

This behavior prevents implementing per-channel configuration using the bot configuration experience because:

• Configuration requests cannot be reliably scoped to the initiating channel
• All configuration actions appear to target the same channel
• Users configuring different channels in the same Team unintentionally overwrite the same settings

Additional Notes

• This occurs within the same Team
• Reproduced consistently across multiple channels
• Observed even when the configuration is invoked after explicitly switching channels
• Behavior suggests the configuration context may be team-scoped rather than channel-scoped, but this is not clearly documented