diff --git a/msteams-platform/TOC.yml b/msteams-platform/TOC.yml
index ea84d770c3d..57c09673cca 100644
--- a/msteams-platform/TOC.yml
+++ b/msteams-platform/TOC.yml
@@ -22,6 +22,9 @@
   - name: Extend agents to Microsoft 365 hubs
     href: /microsoft-365-copilot/extensibility/ecosystem?toc=/microsoftteams/platform/toc.json&bc=/microsoftteams/platform/breadcrumb/toc.json
     displayName: AI bot, Teams AI library, Teams SDK, custom agent
+  - name: Enable targeted messages for agents
+    href: agents-in-teams/targeted-messages.md
+    displayName: targeted messages, proactive messages, adaptive cards, message actions, message extension, notifications
 - name: Tools and SDKs
   items:
   - name: Overview
diff --git a/msteams-platform/agents-in-teams/targeted-messages.md b/msteams-platform/agents-in-teams/targeted-messages.md
new file mode 100644
index 00000000000..51deade93a1
--- /dev/null
+++ b/msteams-platform/agents-in-teams/targeted-messages.md
@@ -0,0 +1,151 @@
+---
+title: Targeted Messages
+description: Learn about enabling targeted messages for agents in Teams.
+ms.localizationpriority: high
+ms.date: 02/06/2025
+ms.topic: reference
+---
+
+# Enable targeted messages for agents
+
+Targeted messages are temporary, user-specific messages that appear in a group chat, meeting, or channel that're visible to only a single user. Agents can use them for sharing contextual, real-time support that includes reminders, welcome messages, or chat summary. It avoids adding permanent noise to the conversation that might be irrelevant to the other group members.
+
+Your agent can include most messages types like interactive Adaptive Cards with buttons, images, or file attachments. For example, a targeted message can deliver a sign‑in card or an error message with a help link to the user. Unlike standard messages, targeted messages are:
+
+- Triggered in response to user action.
+- Delivered to only one user in a group context.
+- Temporary and visible up to 24 hours only in the client.
+- Restricted for user actions such as reaction, replies, and forwarding.
+
+Even though targeted messages are contextually relevant, they're best suited for short-term, action-driven communication. Use them when you want the agent to respond in-the-moment as required by a specific user.
+
+## Targeted messages user experience
+
+A targeted message is an immediate, relevant, and private agent-to-user communication. From a single user's perspective, it appears as regular inline messages in a conversation. However, it's visible only to them and exist only for a short duration. Agents initiate targeted messages in response to a user action. Key aspects of the user experience include:
+
+- The messages appear in context where the triggering action occurred.
+- Only the intended user can see the message. Other group or channel members are unaware of the messages sent. The agent messages or responses appear to that user with the label **Only you can see this message** tagged on them.
+- The message disappears after 24 hours from the client UI.
+- The message doesn't impede the ongoing conversation and reduce spamming while still supporting the user effectively.
+
+## Why use targeted messages
+
+Targeted messages come with the following benefits for enhancing user experience:
+
+- **Reduce chat noise**: <br>
+    An agent can send a message in a group chat or channel that's visible only to a specific user. It prevents a single user's actions from cluttering the conversation. It allows other members to remain focused on the discussion, while the intended recipient of the targeted message still receives help from the agent.
+
+- **Maintain context**: <br>
+    The agent responds to the user request that's aligned with the chat context. The user can get chat summary and be updated about the discussion. It avoids the need to generalize or explain to the broader audience.
+
+- **Agent sensitivity and alertness**: <br>
+    In-the-moment responses from the agent to the user's requirement in the group setting enhances their experience. It reinforces that the agent is alert to user actions and it leads to instant and relevant response.
+
+- **Cleaner chat experience**: <br>
+    Agents can surface errors or feedback privately. It can help users engage more openly. The conversation remains reserved for meaningful, persistent communication. A clear message hierarchy that shows only the content that's meant for everyone is permanent in the chat.
+
+- **Human-in-the-loop scenarios**: <br>
+    It's useful for scenarios such as authentication prompts, approvals, or informational messages that should be visible to the intended user. It helps user's progress through a workflow without switching context or seeking assistance elsewhere.
+
+- **Ephemeral messages**: <br>
+    The targeted message isn't retained in the chat indefinitely. They're cleared after 24 hours to keep the conversation clean. However, your agent retains them in the backend storage for compliance as needed.
+
+[WIP: Placeholder image]
+
+:::image type="content" source="../assets/images/agents-in-teams/targeted-messages/targeted-messages.png" alt-text="Image shows user scenarios for targeted messages" border="false":::
+
+Some common use cases include:
+
+| Use case | Use for ... | To ... |
+| --- | --- | --- |
+| Authentication flows | Sending a sign-in card as a targeted message | Enable uninterrupted discussion by one user's log in workflow |
+| Help or error responses | Sharing tips, usage examples, or error details | Enable discreet support for the intended user |
+| Personal reminders or nudges | Privately sending reminders to a single user | Avoid public call-outs or irrelevant notifications for other group members |
+| Welcome and onboarding | Sending welcome messages or onboarding help to new members | Avoid unnecessary repetition of such information every time a new user joins |
+| AI or Copilot summary | Sharing discussion summary for long-running chats for a new participant | Avoid derailing ongoing discussion because of the summary |
+
+## Targeted message developer experience
+
+You can send a targeted message in an agent just as a normal message. The agent indicates that the message is intended for a specific user in the conversation, and the platform delivers it to that user. The agent doesn't initiate a separate conversation or create a new chat. The message lives in the same channel or thread ID, but with restricted visibility.
+
+Key steps for enabling targeted messages:
+
+1. **Detect the scenario to use a targeted message**:
+
+    The agent for  must determine to send a targeted message in response to one of the following triggers:
+
+    - When a user @mentions or selects a button that might require a response that isn't meant for other group members.
+    - The agent must send a proactive message to a specific user, for example, a reminder or welcome message in-context.
+    - The agent must send a recommendation to a user that isn't relevant to other group members.
+
+1. **Include the targeted designation**:
+
+    Ensure that you specify the following when the agent sends the message:
+
+    - The conversation (chat or channel) ID and targeted user’s ID (Principal ID or MRI). It identifies where the message goes and who should see it.
+    - A flag or API call that marks the message as targeted or ephemeral.
+
+        - **For REST APIs**: The exact URL varies by region. Use the service URL from the conversation. The `userId` is the user’s Teams ID (MRI) to target, and `conversationId` is the group chat or channel thread ID. The payload of the POST is the activity or message to send, just like a normal message activity.
+        - **For Teams SDK**: [WIP - details to be added]
+
+    The following code snippet is an example of a scenario where the agent uses targeted message to inform a group member when they submit their vote in a group poll:
+
+    ```rest
+    POST /v3/users/29:.../conversations/19:.../targetedactivities
+    {
+        "type": "message",
+        "text": "Thank you, your vote has been recorded.",
+        "replyToId": "<id of user's command>",
+        ... (recipient = user, etc.)
+    }
+    ```
+
+1. **Handle send results and fallbacks**:
+
+    After the agent calls the targeted `send` API, the API returns a success or error:
+
+    1. If successful, the targeted user gets the message sent by the agent.
+    1. If the `send` API fails, the agent chooses a fallback, such as sending a 1:1 chat message as a backup. However, the intended user must be a member of the chat or channel to receive a targeted message, else the message isn't delivered. Some scenarios where a send event might fail are if a user isn’t a group member or if the client doesn’t support targeted messages.
+
+    > [!NOTE]
+    > Backward compatibility logic is a service on Teams ensures older clients don't show targeted messages to all members, when not supported. It's helpful if your agent is notified when the client doesn't support targeted messages.
+
+1. **Agent edits and deletes the message**:
+
+    Your agent can update or delete the targeted message after sending it:
+
+    - **Edit**: If a user takes an action, for example submitting the log in card, the agent might want to update the original targeted message. The agent calls the update message API for that message using the message’s `activityId`). The edit updates the content only in the target user’s view.
+    - **Delete**: The agent can delete a targeted message using the delete message API. For example, if the user didn’t act on an ephemeral prompt for some time, the agent can delete it to avoid leaving stale content.
+
+1. **Use Graph API**:
+
+    Microsoft Graph exposes targeted messaging support. For instance, Graph API for Teams chat messages might include a property to send a message to specific users or a new endpoint for targeted messages. It allows workflows or external apps to create targeted messages.
+
+<!--
+| Targeted message in Teams client | End-user experience |
+| --- | --- |
+| **In Chat or Channel** | The targeted message appears in the chat or channel thread only for the target user. It shows up inline among other messages, with the label 'Only you can see this message' to indicate its privacy. The message can be at the root of the chat, channel, or inside a thread (if the bot message is a reply to a user's specific message in a channel). Bot developers can determine where to post the message, same as a normal bot message: <br> - If the bot replies in a channel thread (at level 2), it can target that reply to the specific user. Only that user sees the reply in the thread. Other users might temporarily see the thread as if it has no new replies (until there's a public reply). <br> - If the bot posts a top-level message (L1) in a chat or channel, it can mark it targeted to a user. The user sees the message in the main chat flow, but others don't see any message at that spot. |
+| **Threading behavior** | If a targeted message is sent as a new thread reply (level 2) in a channel: <br> - Teams creates a thread visible only to the targeted user. <br> - If later someone (or the bot) posts a public message in that thread, the thread becomes visible to everyone, but with some differences. Users who were previously unaware can see the thread starter and any public replies. However, the targeted reply remains invisible to them. <br> - Teams manages the thread count per user: The reply count and summary adapt per viewer so that the private reply is only counted for the person who received it. In short, thread reply counts and follow-status are personalized when targeted messages are involved. <br> - If the targeted user wasn’t already following the thread (or in a group chat context, if it’s a side conversation), the act of receiving a targeted message automatically makes them follow the thread (to ensure they get updates). The user can manually unfollow if they want. <br> - Other people can't reply to a targeted message. If another user replies to the same parent message (in a channel thread scenario), that reply starts a separate public thread (or be a separate reply). That user can’t see or join the private thread until a public message is posted in that thread. |
+| **Top-level targeted message in a chat or channel (level 1)** | - Other users simply don't see that message. It doesn't increment the chat “unread” for them. <br> - They might notice that the bot seemingly didn't respond to an earlier user’s command (if they saw the user’s message). This is the “dangling message” issue. |
+| **Ephemeral lifespan** | Targeted messages show in the clients for 24 hours only. They're retained in backend storage for compliance. |
+| **Notification** | Targeted messages aren't notified, however, the chat appears as bold when the user receives a new message in a group chat. |
+| **User actions** | The user actions are limited to any actions within the targeted message. The users can't react or reply to the message. |
+
+:::row:::
+    :::column:::
+        **Reduce chat noise**:
+    :::column-end:::
+    :::column span="2":::
+            An agent or bot can send a message in a group chat or channel that's visible only to a specific user. They prevent one user's actions from cluttering the conversation. It allows other members to remain focused on the main discussion, even if the intended recipient of the targeted message still receives help from the agent.
+    :::column-end:::
+:::row-end:::
+
+        - **For Bot Framework SDK**: In Bot Framework SDK, it's planned as a specialized method or property. For example, Teams is introducing a method like `SendTargetedActivityAsync` that you can call instead of the regular `SendActivityAsync`. It invokes a Teams-specific API endpoint to deliver a targeted message, where `isTargeted: true` indicates this message should be private to `targetUserId`.
+
+- **Authentication flows**: For an unauthenticated user who tries to access the group or channel, the agent can respond with a sign-in card as a targeted message. It ensures that other group members can continue their discussion without being interrupted by one user's log in workflow.
+- **Help or error responses**: For a user who requires help or who encounters an error in the group, the agent can share tips, usage examples, or error details through a targeted message. The user can receive the help they need discreetly.
+- **Personal reminders or nudges**: An agent can privately send reminders to a single user. It avoids public call-outs or irrelevant notifications to others.
+- **Welcome and onboarding**: An agent can send welcome messages or onboarding help to new members in the group or channel. It avoids unnecessary repetition of such information every time a new user joins.
+- **AI or Copilot summaries**: In long-running chats, an agent can share discussion summary for a new participant using a targeted message. The ongoing discussion isn't derailed because of the summary.
+
+-->
\ No newline at end of file
diff --git a/msteams-platform/assets/images/agents-in-teams/targeted-messages/targeted-messages.png b/msteams-platform/assets/images/agents-in-teams/targeted-messages/targeted-messages.png
new file mode 100644
index 00000000000..73c2032710f
Binary files /dev/null and b/msteams-platform/assets/images/agents-in-teams/targeted-messages/targeted-messages.png differ