Merge pull request #16571 from MicrosoftDocs/main

Published main to live, Wednesday 10:30 AM PT, 02/19

Teams/messaging-policies-in-teams.md

@@ -21,19 +21,17 @@ ms.custom:
 - ms.teamsadmincenter.messagingpolicies.overview
 - seo-marvel-apr2020
 - chat-teams-channels-revamp
-description: "Learn about Messaging policies and how they can be used to control chat messaging in Teams."
+description: Learn about Messaging policies and how they can be used to control chat messaging in Teams.
 ---
 
 # Manage messaging policies in Teams
 
-<!--- Add zone marker here--->
-
 Messaging policies are used to control which chat and channel messaging features are available to [users (owners and members)](assign-roles-permissions.md) in Microsoft Teams. You can use the global (Org-wide default) policy that's created automatically or create and assign custom messaging policies.
 
 Users in your organization will automatically get the global policy, unless you create and assign a custom policy. Edit the settings in the global policy or create and assign one or more custom policies to turn on or turn off the features that you want.
 
 > [!NOTE]
-> To ensure syncing after a policy change, a reboot may be necessary for certain instances. 
+> To ensure syncing after a policy change, a reboot may be necessary for certain instances.
 
 ## Create a custom messaging policy
 
@@ -69,15 +67,13 @@ A user can only be assigned one messaging policy at a time.
 > [!NOTE]
 > You can't delete a policy if users are assigned to it. You must first assign a different policy to all affected users, and then you can delete the original policy.
 
-<!--- End zone marker here--->
-
 ## Messaging policy settings
 
 Here are the messaging policy settings that you can configure.
 
 - **Owners can delete sent messages** -   Enable this setting to allow owners to delete messages or posts sent by users, excluding their own. *To allow owners to delete their own sent messages, activate the **Delete Sent Messages** setting*.
 - **Delete sent messages** - Use this setting to let users delete individual messages that they sent in chat.
-- **Delete chat** - Use this setting to let users have the option to delete entire conversations from their chat list. This will only delete the chat content for the user taking the action; other users in the chat will still be able to see all of the messages. The user who deleted the chat will not see any existing messages in their activity feed or search results for the deleted chat; this user will also be removed from the deleted chat. Users will be prompted to confirm the decision to delete a chat. This setting is on by default. If this setting is turned off, users will no longer see the delete option for their chats.
+- **Delete chat** - Use this setting to let users have the option to delete entire conversations from their chat list. This will only delete the chat content for the user taking the action; other users in the chat will still be able to see all of the messages. The user who deleted the chat won't see any existing messages in their activity feed or search results for the deleted chat; this user will also be removed from the deleted chat. Users will be prompted to confirm the decision to delete a chat. This setting is on by default. If this setting is turned off, users will no longer see the delete option for their chats.
 - **Edit sent messages** - Use this setting to let users edit the messages that they sent in chat.
 - **Read receipts** - Read receipts allow the sender of a chat message to be notified when their message was read by the recipient in 1:1 and group chats 20 people or fewer. Message read receipts remove uncertainty about whether a message was read, and improve team communication. Read receipts aren't captured in eDiscovery reporting.  
   - **User controlled** - This means that users get to decide if they want read receipts ON or OFF. Default setting within the app is ON. Users can then turn it OFF.
@@ -107,14 +103,15 @@ Here are the messaging policy settings that you can configure.
   > Audio messages are not captured in eDiscovery reporting.
   - **Allowed in chats and channels** - This means that users can leave audio messages in both chats and channels.
   - **Allowed in chats only** - This means that users can leave audio messages in chats, but not in channels.
-  - **Not enabled** - This means that users cannot create audio messages in chats or channels.  
+  - **Not enabled** - This means that users can't create audio messages in chats or channels.  
 - **On mobile devices, display favorite channels above recent chats** - Enable this setting to move favorite channels to the top of the mobile device screen so that a user doesn't need to scroll to find them.
 - **Remove users from group chats** - Turn this setting ON to let a user remove other users from a group chat. This feature lets you continue a chat with a smaller group of people without losing the chat history.
 - **Text predictions** - Turn on this setting to let a user get text predictions for chat messages.
 - **Suggested replies** - Turn this setting on to enable suggested replies for chat messages.
 - **Chat permission role** - Use this setting to define the supervised chat role of the user. Learn more about [supervised chat](supervise-chats-edu.md).
 - **Users with full chat permissions can delete any message** - Use this setting to let users with full permissions delete any group or meeting chat message.
 - **Video messages** - Turn this setting on if you want users in your organization to be able to use the Teams app to send video messages to other people in chats and channels.
+- **Viva Engage experiences in Teams** - Turn this setting on if you want users in your organization to be able to integrate Viva Engage experiences, like Storyline, into their chats.
 
 > [!NOTE]
 > Some of these settings, such as using Giphys, can also be configured at the team level by team owners and at the private or shared channel level by channel owners.
@@ -126,33 +123,32 @@ Teams Chat supports closed captions for video messages. Users can disable captio
 > [!NOTE]
 > Captions are auto-generated and currently available only in English.
 
-As an administrator, you can hide or show captions for users by using the PowerShell cmdlet.
+As an administrator, you can hide or show captions for users by using PowerShell cmdlets.
+
+- Use the following command to enable captions:
 
--	Use the following command to enable captions:
-
     ```powershell
     Set-CsTeamsMessagingConfiguration -EnableVideoMessageCaptions $true
           
     ```
 
--	Use the following command to disable captions:
-    
+- Use the following command to disable captions:
+
     ```powershell
     Set-CsTeamsMessagingConfiguration -EnableVideoMessageCaptions $false
         
     ```
 
-- Use the following command to get the value for `TeamsMessagingConfiguration`:	
-    
+- Use the following command to get the value for `TeamsMessagingConfiguration`:
+
     ```powershell
     Get-CsTeamsMessagingConfiguration
         
     ```
 
 For more information about PowerShell, see [Microsoft Teams PowerShell Overview - Microsoft Teams | Microsoft Learn](teams-powershell-overview.md).
 
-
-### Related topics
+### Related articles
 
 - [Teams policies reference - Messaging policies](settings-policies-reference.md#messaging-policies)
 - [Assign policies to users and groups in Teams](assign-policies-users-and-groups.md)

Teams/teams-viva-experiences.md

@@ -0,0 +1,111 @@
+---
+title: Manage Viva Engage experiences in Microsoft Teams
+author: DaniEASmith
+ms.author: danismith
+manager: jtremper
+ms.reviewer: luises
+ms.topic: how-to
+ms.date: 02/13/2025
+ms.service: msteams
+audience: admin
+ms.collection: 
+- M365-collaboration
+ms.custom:
+- admindeeplinkTEAMS
+search.appverid: MET150
+f1.keywords:
+- NOCSH
+appliesto: 
+- Microsoft Teams
+ms.localizationpriority: medium
+description: Learn about how to manage Viva Engage experiences in Microsoft Teams.
+---
+
+# Manage Viva Engage experiences in Microsoft Teams
+
+> [!NOTE]
+> This feature is currently in public preview with Viva Engage storyline only.
+
+Viva Engage unites your organization, allowing people to connect with leaders, coworkers, and communities. With Viva Engage, your users can generate ideas, share their work and experience, and find connection at work.
+
+And, now Viva Engage can integrate into your users' Teams workflows.
+
+This article outlines the technical details of the integration of Viva Engage experiences in Teams and instructs IT admins on how they can manage this feature.
+
+## Technical details for Viva Engage experiences in Teams
+
+### Prerequisites for Viva Engage experiences
+
+Before rolling out Viva Engage experiences to Teams, ensure Viva Engage experiences are accessible by your users, including the following:
+
+- Your tenant isn't blocking [Viva Engage's IPs and URLs](/microsoft-365/enterprise/urls-and-ip-address-ranges).
+- Sign-ins for the Office 365 Viva Engage service are enabled in Microsoft Entra ID.
+  - Sign in to the [Microsoft Entra admin center](https://go.microsoft.com/fwlink/p/?linkid=2067268).
+  - Go to **Identity** > **Applications** > **Enterprise Applications** > **Viva Engage** > **Properties**.
+  - For the **Enabled for users to sign-in?** option, select **Yes**.
+
+### User requirements for Viva Engage experiences in Teams
+
+In order for users to access Viva Engage experiences in Teams, they must meet the following requirements:
+
+- Be assigned a Microsoft 365 license
+- Be assigned a Teams license
+- Have access to [Viva Engage either with or without Viva Engage license enforcement](/viva/engage/setup#set-up-licensing-for-viva-engage)
+
+### Current limitations of Viva Engage experiences in Teams
+
+In the following list, find the current limitations of Viva Engage experiences in Teams:
+
+- Assigning leaders in Viva Engage can only be done in the Viva Engage App or web experience.
+- Assigning and managing delegates can only be done in the Viva Engage App or web experience.
+- Campaigns and Topics pages can only be managed in the Viva Engage App or web experience.
+
+### Data handling of Viva Engage experiences in Teams
+
+Viva Engage content in Teams is handled by Viva Engage's security and compliance standards. To learn more about Viva Engage's data handling, see [Overview of security and compliance in Viva Engage](/viva/engage/manage-security-and-compliance/security-and-compliance).
+
+## How to turn off and on Viva Engage experiences in Teams
+
+The **Viva Engage experiences in Teams** messaging setting is turned **On** by default for your entire organization.
+
+To change this setting, complete the following steps:
+
+1. Sign in to the [Teams admin center](https://go.microsoft.com/fwlink/p/?linkid=2066851) with your admin credentials.
+1. In the left-rail menu, select **Settings & policies**.
+1. Select either **Global (Org-wide default) settings** or **Custom policies for users & groups**.
+1. Scroll to the **Messaging** section and select **Messaging**.
+1. On the **Messaging settings** page, find the **Viva Engage** section.
+1. Switch off or on the **Viva Engage experiences in Teams** toggle.
+1. Select the **Save** button.
+
+> [!NOTE]
+> If your organization has chosen to turn off Viva Engage or the storyline feature, storyline won't be available in Teams. Storyline in Teams won't grant storyline access or permissions to any user who doesn’t already have access to the features in Viva Engage.
+
+## User experience of Viva Engage in Teams chats
+
+The first Viva Engage experience to integrate with Teams chats is [storyline](/viva/engage/eac-storyline).
+
+Storyline content, whether originating from Teams or from Engage, is visible to all eligible users in both Teams and Viva Engage.
+
+Storyline pages can be accessed in Teams chats with the following capabilities:
+
+- Users can create new storyline posts directly from Teams.
+- Users can follow, view, and comment on others' storylines in Teams.
+- Users receive notifications in Teams for relevant activity in storyline.
+- Storyline conversations have a look and feel similar to other messaging experiences in Teams.
+
+If users have [Viva Engage Premium](/viva/engage/setup#set-up-licensing-for-viva-engage), they receive the following extra capabilities:
+
+- Assigned leaders can send storyline announcements.
+- Users can post a storyline or comment on storyline posts on behalf of others as a delegate.
+- Users can change the cover photo at the top of their storyline.
+- Users can view personal analytics about their storyline.
+
+## Related articles
+
+- [Manage messaging policies in Teams](messaging-policies-in-teams.md)
+- [Introducing Microsoft Viva Engage](/viva/engage/overview)
+- [Manage and set up storyline in Viva Engage](/viva/engage/eac-storyline)
+- [Data residency for Viva Engage](/viva/engage/manage-security-and-compliance/data-residency)
+- [Delegation in Viva Engage](https://support.microsoft.com/topic/delegation-in-viva-engage-2f0a64a3-c5c0-45cd-b3f1-e1e06732f89f)
+- [Identify leaders in Viva Engage](/viva/engage/leadership-identification)

Teams/toc.yml

@@ -652,6 +652,8 @@ items:
           href: presence-admins.md
         - name: User work location in Teams
           href: user-work-location-in-teams.md
+        - name: Viva Engage experiences in Teams
+          href: teams-viva-experiences.md
         - name: Custom emojis in Teams
           href: teams-custom-emojis.md
         - name: Supervised chat for non-educational tenants