Merge pull request MicrosoftDocs#11049 from MicrosoftDocs/Office-docs-powershell-Release-Branch

Yammer rebrand 7/12 publish

Author: chrisda

exchange/exchange-ps/exchange/Get-AppRetentionCompliancePolicy.md

@@ -29,7 +29,7 @@ Get-AppRetentionCompliancePolicy [[-Identity] <PolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Yammer chats, and Yammer community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you'll likely need to create one policy per workload.
+\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Viva Engage chats, and Viva Engage community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you'll likely need to create one policy per workload.
 
 To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/microsoft-365/compliance/microsoft-365-compliance-center-permissions).
 
@@ -44,10 +44,10 @@ This example returns a summary list of all app retention compliance policies.
 
 ### Example 1
 ```powershell
-Get-AppRetentionCompliancePolicy -Identity "Contoso Yammer"
+Get-AppRetentionCompliancePolicy -Identity "Contoso Viva Engage"
 ```
 
-This example returns detailed information for the app retention compliance policy named Contoso Yammer.
+This example returns detailed information for the app retention compliance policy named Contoso Viva Engage.
 
 ## PARAMETERS
 

exchange/exchange-ps/exchange/Get-AppRetentionComplianceRule.md

@@ -38,10 +38,10 @@ This example returns a summary list of all app retention compliance rules.
 
 ### Example 1
 ```powershell
-Get-AppRetentionComplianceRule -Identity "Contoso Yammer"
+Get-AppRetentionComplianceRule -Identity "Contoso Viva Engage"
 ```
 
-This example returns detailed information for the app retention compliance rule named Contoso Yammer.
+This example returns detailed information for the app retention compliance rule named Contoso Viva Engage.
 
 ## PARAMETERS
 

exchange/exchange-ps/exchange/Get-LicenseVsUsageSummaryReport.md

@@ -31,7 +31,7 @@ This cmdlet produces a report that is intended to enable clients to track and ma
 
 - Date: The period being measured.
 - TenantGuid: The unique identifier for the Exchange Online tenant.
-- Workload: The workload whose users are being counted. The current workloads include: Exchange Online, SharePoint Online, Skype for Business Online, and Microsoft Yammer.
+- Workload: The workload whose users are being counted. The current workloads include: Exchange Online, SharePoint Online, Skype for Business Online, and Microsoft Viva Engage.
 - NonTrialEntitlements: The number of entitled users for the workload.
 - TrialEntitlements: The number of provisionally entitled (trial) users for the workload.
 - ActiveUsers: The count of active users for the workload.

exchange/exchange-ps/exchange/New-AppRetentionCompliancePolicy.md

@@ -50,18 +50,18 @@ New-AppRetentionCompliancePolicy [-Name] <String> -Applications <String[]>
 ```
 
 ## DESCRIPTION
-\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Yammer chats, and Yammer community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you'll likely need to create one policy per workload.
+\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Viva Engage chats, and Viva Engage community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you'll likely need to create one policy per workload.
 
 To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/microsoft-365/compliance/microsoft-365-compliance-center-permissions).
 
 ## EXAMPLES
 
 ### Example 1
 ```powershell
-New-AppRetentionCompliancePolicy -Name "Regulation 567 Compliance" -Applications "User:MicrosoftTeams,Yammer","Group:MicrosoftTeams,Yammer" -ExchangeLocation "Jennifer Petersen","Kitty Nakamura"
+New-AppRetentionCompliancePolicy -Name "Regulation 567 Compliance" -Applications "User:MicrosoftTeams,VivaEngage","Group:MicrosoftTeams,VivaEngage" -ExchangeLocation "Jennifer Petersen","Kitty Nakamura"
 ```
 
-This example creates a static scope retention policy named Regulation 567 Compliance for the Yammer user messages of Jennifer Petersen and Kitty Nakamura.
+This example creates a static scope retention policy named Regulation 567 Compliance for the Viva Engage user messages of Jennifer Petersen and Kitty Nakamura.
 
 After you create the retention policy, use the New-AppRetentionComplianceRule cmdlet to create a retention rule and assign it the retention policy to it.
 
@@ -110,7 +110,7 @@ The Applications parameter specifies the applications to include in the policy a
 - ModernGroupLocation
 - AdaptiveScopeLocation
 
-This parameter uses the following syntax: `"LocationtType:App1,LocationType:App2,...LocationType:AppN` where LocationType is User or Group. For example, `"User:Exchange,User:OneDriveForBusiness,Group:Exchange,Group:SharePoint"` or `"User:MicrosoftTeams","User:Yammer"`.
+This parameter uses the following syntax: `"LocationtType:App1,LocationType:App2,...LocationType:AppN` where LocationType is User or Group. For example, `"User:Exchange,User:OneDriveForBusiness,Group:Exchange,Group:SharePoint"` or `"User:MicrosoftTeams","User:VivaEngage"`.
 
 ```yaml
 Type: String[]

exchange/exchange-ps/exchange/Remove-AppRetentionCompliancePolicy.md

@@ -35,10 +35,10 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 
 ### Example 1
 ```powershell
-Remove-AppRetentionCompliancePolicy -Identity "Contoso Yammer"
+Remove-AppRetentionCompliancePolicy -Identity "Contoso Viva Engage"
 ```
 
-This example removes the app retention compliance policy named Contoso Yammer.
+This example removes the app retention compliance policy named Contoso Viva Engage.
 
 ## PARAMETERS
 

exchange/exchange-ps/exchange/Remove-AppRetentionComplianceRule.md

@@ -35,10 +35,10 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 
 ### Example 1
 ```powershell
-Remove-AppRetentionComplianceRule -Identity "Contoso Yammer"
+Remove-AppRetentionComplianceRule -Identity "Contoso Viva Engage"
 ```
 
-This example removes the app retention compliance policy rule Contoso Yammer.
+This example removes the app retention compliance policy rule Contoso Viva Engage.
 
 ## PARAMETERS
 

exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md

@@ -108,7 +108,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 
 ### Example 1
 ```powershell
-Set-AppRetentionCompliancePolicy Identity "Regulation 563 Marketing" -Applications "User:MicrosoftTeams","Group:MicrosoftTeams,Yammer" -AddExchangeLocation "Scott Smith" -Comment "Added new counsel, 9/9/21"
+Set-AppRetentionCompliancePolicy Identity "Regulation 563 Marketing" -Applications "User:MicrosoftTeams","Group:MicrosoftTeams,VivaEngage" -AddExchangeLocation "Scott Smith" -Comment "Added new counsel, 9/9/21"
 ```
 
 This example adds a new user to the existing static scope retention policy named Regulation 563 Marketing that's set up for Teams private channels messages.
@@ -290,7 +290,7 @@ The Applications parameter specifies the applications to include and is relevant
 - ModernGroupLocation
 - AdaptiveScopeLocation
 
-This parameter uses the following syntax: `"LocationtType:App1,LocationType:App2,...LocationType:AppN` where LocationType is User or Group. For example, `"User:Exchange,User:OneDriveForBusiness,Group:Exchange,Group:SharePoint"` or `"User:MicrosoftTeams","User:Yammer"`.
+This parameter uses the following syntax: `"LocationtType:App1,LocationType:App2,...LocationType:AppN` where LocationType is User or Group. For example, `"User:Exchange,User:OneDriveForBusiness,Group:Exchange,Group:SharePoint"` or `"User:MicrosoftTeams","User:VivaEngage"`.
 
 ```yaml
 Type: String[]

exchange/exchange-ps/exchange/Set-Mailbox.md

@@ -4616,7 +4616,7 @@ Accept wildcard characters: False
 ### -RemoveDelayReleaseHoldApplied
 This parameter is available only in the cloud-based service.
 
-The RemoveDelayReleaseHoldApplied switch specifies whether to remove delay holds on cloud data generated by non-Exchange apps (such as Teams, Forms, and Yammer) from the mailbox. Data generated by a non-Exchange cloud-based app is typically stored in a hidden folder in the mailbox. You don't need to specify a value with this switch.
+The RemoveDelayReleaseHoldApplied switch specifies whether to remove delay holds on cloud data generated by non-Exchange apps (such as Teams, Forms, and Viva Engage) from the mailbox. Data generated by a non-Exchange cloud-based app is typically stored in a hidden folder in the mailbox. You don't need to specify a value with this switch.
 
 The removal of a hold from a mailbox is temporarily delayed to prevent the accidental purge of content that's no longer affected by the hold. This temporary delay in the removal of the hold is known as a delay hold. To see the hold history on a mailbox, replace `<MailboxIdentity>` with the name, email address, or alias of the mailbox, and run this command: `Export-MailboxDiagnosticLogs -Identity <MailboxIdentity> -ComponentName SubstrateHoldTracking`.
 

exchange/exchange-ps/exchange/Set-OrganizationConfig.md

@@ -1223,7 +1223,7 @@ The ConnectorsEnabled parameter specifies whether to enable or disable all conne
 - $true: Connectors are enabled. This is the default value.
 - $false: Connectors are disabled.
 
-The workloads that are affected by this parameter are Outlook, SharePoint, Teams, and Yammer.
+The workloads that are affected by this parameter are Outlook, SharePoint, Teams, and Viva Engage.
 
 ```yaml
 Type: Boolean
@@ -1308,7 +1308,7 @@ Accept wildcard characters: False
 ### -ConnectorsEnabledForYammer
 This parameter is available only in the cloud-based service.
 
-The ConnectorsEnabledForYammer parameter specifies whether to enable or disable connected apps on Yammer. Valid values are:
+The ConnectorsEnabledForYammer parameter specifies whether to enable or disable connected apps on Viva Engage. Valid values are:
 
 - $true: Connectors are enabled. This is the default value.
 - $false: Connectors are disabled.

exchange/exchange-ps/exchange/Set-UnifiedGroup.md

@@ -1212,7 +1212,7 @@ The UnifiedGroupWelcomeMessageEnabled switch specifies whether to enable or disa
 - To enable this setting, you don't need to specify a value with this switch.
 - To disable this setting, use this exact syntax: `-UnifiedGroupWelcomeMessageEnabled:$false`.
 
-This setting only controls email send by the Microsoft 365 Group. It doesn't control email sent by connected products (for example, Teams or Yammer).
+This setting only controls email send by the Microsoft 365 Group. It doesn't control email sent by connected products (for example, Teams or Viva Engage).
 
 This setting is enabled by default.