Move IsTargeted property from Activity to Account#477
Merged
heyitsaamir merged 1 commit intomicrosoft:mainfrom Mar 23, 2026
Merged
Conversation
Collaborator
@ShanmathiMayuramKrithivasan Can you include reasoning on why this was important? |
heyitsaamir
approved these changes
Mar 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moved IsTargeted from Activity to Account - making targeting a recipient‑level property, Recipient.IsTargeted provides a single, consistent model across both User to Bot and Bot to User flows in next phase of targeted messaging. This also enables the flag to be serialized for compat layers and keeps SDK behavior aligned with underlying service flows.
Updated routing logic to read from Recipient.IsTargeted instead of Activity.IsTargeted