Bot Framework用户识别机制问询：如何获取正确状态数据及是否依赖IP？
Great question! Let me break down exactly how Bot Framework handles user identification and state persistence, including why it works seamlessly when a user switches devices on the same channel.
Core Identification: Channel-Assigned User IDs
First off, let's clear up a common misconception: Bot Framework does NOT rely on IP addresses for user identification. IPs are unreliable (users switch networks, multiple users can share the same IP) so they're never used for this purpose. Instead, the bot depends entirely on unique identifiers provided by the messaging channel itself (like Teams, Facebook Messenger, Slack, or WhatsApp):
- Every user on a channel has a persistent, unique ID tied directly to their account on that platform. When a user sends a message to your bot, the channel includes this ID in the message payload (usually in the
from.idfield). - Bot Framework extracts this ID and uses it as the primary key to link state data to the user. Since the ID is tied to the user's channel account—not their device or IP—switching devices (e.g., from a phone to a laptop) while logged into the same channel account will still send the same
from.idvalue. That's why the bot recognizes the user immediately, no matter what device they're on.
User vs. Conversation State: Keeping Context Straight
To avoid mixing up context between different interactions, Bot Framework uses two key state scopes, both anchored to channel identifiers:
- User State: Stored using a combination of
channelId+userId. This data persists across all conversations a user has with your bot on that channel. For example, if a user tells the bot their favorite pizza topping, that preference will be remembered even if they start a new chat session a week later. - Conversation State: Stored using
channelId+conversationId. This keeps data specific to a single chat thread—like the current step in a booking flow. If a user opens a new chat window with your bot, this state resets, but their user state (like preferences) stays intact.
How State Data is Stored and Retrieved
Bot Framework doesn't store state data locally by default (for production, you'll want a persistent storage solution). The storage layer uses the combined identifiers mentioned above to look up and save state:
- Popular production-ready options include Azure Cosmos DB, Azure Blob Storage, or custom storage providers you build yourself.
- When the bot receives a message, it fetches the corresponding user or conversation state from storage using the channel-provided IDs. This ensures it always pulls the right data for the user, no matter which device they're using.
Custom Channels: Your Role in User Identification
If you're building a custom channel integration (e.g., a chat widget on your website), you'll need to handle user identification yourself. The key rule here is to assign a unique, persistent ID to each user (tied to their account in your system) and include that ID in the message payload sent to Bot Framework. Without this, the bot won't be able to reliably track user state across devices or sessions.
内容的提问来源于stack exchange，提问作者Dmitriy Konyayev
