Merge branch 'main' into SIS-chrisda

chrisda · chrisda · commit 9ddbb56c5a12 · 2025-06-20T14:05:43.000-07:00
diff --git a/exchange/exchange-ps/exchange/Get-EXOMailbox.md b/exchange/exchange-ps/exchange/Get-EXOMailbox.md
@@ -447,7 +447,6 @@ The RecipientTypeDetails parameter filters the results by the specified mailbox
 
 - DiscoveryMailbox
 - EquipmentMailbox
-- GroupMailbox
 - LegacyMailbox
 - LinkedMailbox
 - LinkedRoomMailbox
diff --git a/exchange/exchange-ps/exchange/Get-FederationInformation.md b/exchange/exchange-ps/exchange/Get-FederationInformation.md
@@ -14,7 +14,10 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
 
-Use the Get-FederationInformation cmdlet to get federation information, including federated domain names and target URLs, from an external Exchange organization.
+Use the Get-FederationInformation cmdlet to get federation information from an external Exchange organization.
+
+> [!TIP]
+> For information about changes made to the Get-FederationInformation cmdlet to improve security and privacy, see [Important Update to the Get-FederationInformation Cmdlet in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/important-update-to-the-get-federationinformation-cmdlet-in-exchange-online/4410095).
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -29,9 +32,7 @@ Get-FederationInformation -DomainName <SmtpDomain>
 ```
 
 ## DESCRIPTION
-The Get-FederationInformation cmdlet retrieves federation information from the domain specified. Results from the cmdlet can be piped to the New-OrganizationRelationship cmdlet to establish an organization relationship with the Exchange organization being queried.
-
-The domain specified should have federation enabled.
+The Get-FederationInformation cmdlet retrieves federation information from the specified domain, which should have federation enabled.
 
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
diff --git a/exchange/exchange-ps/exchange/Get-MailDetailATPReport.md b/exchange/exchange-ps/exchange/Get-MailDetailATPReport.md
@@ -242,8 +242,8 @@ The MessageTraceId value is also available in the output of the following cmdlet
 - Get-MailDetailDlpPolicyReport
 - Get-MailDetailEncryptionReport
 - Get-MailDetailTransportRuleReport
-- Get-MessageTrace
-- Get-MessageTraceDetail
+- Get-MessageTraceV2
+- Get-MessageTraceDetailV2
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md b/exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md
@@ -194,8 +194,8 @@ The MessageTraceId value is also available in the output of the following cmdlet
 - Get-MailDetailATPReport
 - Get-MailDetailEncryptionReport
 - Get-MailDetailTransportRuleReport
-- Get-MessageTrace
-- Get-MessageTraceDetail
+- Get-MessageTraceV2
+- Get-MessageTraceDetailV2
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md b/exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md
@@ -204,8 +204,8 @@ The MessageTraceId value is also available in the output of the following cmdlet
 - Get-MailDetailATPReport
 - Get-MailDetailDlpPolicyReport
 - Get-MailDetailTransportRuleReport
-- Get-MessageTrace
-- Get-MessageTraceDetail
+- Get-MessageTraceV2
+- Get-MessageTraceDetailV2
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md b/exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md
@@ -176,8 +176,8 @@ The MessageTraceId value is also available in the output of the following cmdlet
 - Get-MailDetailATPReport
 - Get-MailDetailDlpPolicyReport
 - Get-MailDetailEncryptionReport
-- Get-MessageTrace
-- Get-MessageTraceDetail
+- Get-MessageTraceV2
+- Get-MessageTraceDetailV2
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/exchange/Get-MailUser.md b/exchange/exchange-ps/exchange/Get-MailUser.md
@@ -213,7 +213,7 @@ The HVEAccount switch specifies that this mail user account is specifically used
 
 ```yaml
 Type: SwitchParameter
-Parameter Sets: LOBAppAccount
+Parameter Sets: HVEAccount
 Aliases:
 Applicable: Exchange Online, Exchange Online Protection
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 ### -LOBAppAccount
 This parameter is available only in the cloud-based service.
 
-{{ Fill LOBAppAccount Description }}
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/exchange/Get-MessageTrace.md b/exchange/exchange-ps/exchange/Get-MessageTrace.md
@@ -14,6 +14,9 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
+> [!NOTE]
+> This cmdlet is replaced by the [Get-MessageTraceV2](https://learn.microsoft.com/powershell/module/exchange/get-messagetracev2) cmdlet and will eventually be deprecated.
+
 Use the Get-MessageTrace cmdlet to trace messages as they pass through the cloud-based organization.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
diff --git a/exchange/exchange-ps/exchange/Get-MessageTraceDetail.md b/exchange/exchange-ps/exchange/Get-MessageTraceDetail.md
@@ -14,6 +14,9 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
+> [!NOTE]
+> This cmdlet is replaced by the [Get-MessageTraceDetailV2](https://learn.microsoft.com/powershell/module/exchange/get-messagetracedetailv2) cmdlet and will eventually be deprecated.
+
 Use the Get-MessageTraceDetail cmdlet to view the message trace event details for a specific message. Note that these detailed results are returned less quickly than the Get-MessageTrace results.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
diff --git a/exchange/exchange-ps/exchange/Get-MessageTraceDetailV2.md b/exchange/exchange-ps/exchange/Get-MessageTraceDetailV2.md
@@ -47,7 +47,7 @@ This example retrieves detailed message trace information for messages with the
 Get-MessageTraceV2 -MessageTraceId 2bbad36aa4674c7ba82f4b307fff549f -SenderAddress john@contoso.com -StartDate 06/13/2025 -EndDate 06/15/2025 | Get-MessageTraceDetailV2
 ```
 
-This example uses the Get-MessageTrace cmdlet to retrieve message trace information for messages with the Exchange Network Message ID value 2bbad36aa4674c7ba82f4b307fff549f sent by `john@contoso.com` between June 13, 2025 and June 15, 2025, and pipelines the results to the Get-MessageTraceDetailV2 cmdlet.
+This example uses the Get-MessageTraceV2 cmdlet to retrieve message trace information for messages with the Exchange Network Message ID value 2bbad36aa4674c7ba82f4b307fff549f sent by `john@contoso.com` between June 13, 2025 and June 15, 2025, and pipelines the results to the Get-MessageTraceDetailV2 cmdlet.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/exchange/Get-MessageTrackingReport.md b/exchange/exchange-ps/exchange/Get-MessageTrackingReport.md
@@ -16,7 +16,7 @@ This cmdlet is functional only in on-premises Exchange.
 
 Use the Get-MessageTrackingReport cmdlet to return data for a specific message tracking report. This cmdlet is used by the delivery reports feature.
 
-In Exchange Online, delivery reports has been replaced by message trace (the Get-MessageTrace and Get-MessageTraceDetail cmdlets).
+In Exchange Online, delivery reports are replaced by message trace (the Get-MessageTraceV2 and Get-MessageTraceDetailV2 cmdlets).
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
diff --git a/exchange/exchange-ps/exchange/New-MailUser.md b/exchange/exchange-ps/exchange/New-MailUser.md
@@ -574,7 +574,7 @@ Accept wildcard characters: False
 ### -LOBAppAccount
 This parameter is available only in the cloud-based service.
 
-{{ Fill LOBAppAccount Description }}
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/exchange/New-OrganizationRelationship.md b/exchange/exchange-ps/exchange/New-OrganizationRelationship.md
@@ -65,7 +65,11 @@ Free/busy access is enabled.
 
 The requesting organization receives time, subject, and location information from the target organization.
 
-This example attempts to automatically discover configuration information from the external organization by using the domain names provided in the Get-FederationInformation command. If you use this method to create your organization relationship, you must first ensure that you've created an organization identifier by using the Set-FederationOrganizationIdentifier cmdlet.
+This example creates the organization relationship using only the domain name specified in the Get-FederationInformation command.
+
+Before you use this method to create an organization relationship, use the Get-FederatedOrganizationIdentifier cmdlet to verify you created an organization identifier using the Set-FederationOrganizationIdentifier cmdlet. Then you can add any additional domains used by the target organization.
+
+**Tip**: For information about changes made to the Get-FederationInformation cmdlet to improve security and privacy, see [Important Update to the Get-FederationInformation Cmdlet in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/important-update-to-the-get-federationinformation-cmdlet-in-exchange-online/4410095).
 
 ### Example 2
 ```powershell
diff --git a/exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md
@@ -446,7 +446,9 @@ Accept wildcard characters: False
 ```
 
 ### -PriorityCleanup
-The PriorityCleanup switch specifies whether to create a [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup) policy to expedite the deletion of sensitive content, overriding any existing retention settings or eDiscovery holds. You don't need to specify a value with this switch.
+The PriorityCleanup switch specifies whether to create a Priority cleanup policy. You don't need to specify a value with this switch.
+
+Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup).
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/exchange/New-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/New-RetentionComplianceRule.md
@@ -142,7 +142,9 @@ Accept wildcard characters: False
 ```
 
 ### -PriorityCleanup
-{{ Fill PriorityCleanup Description }}
+The PriorityCleanup switch specifies whether to create a rule associated with a Priority cleanup policy. You don't need to specify a value with this switch.
+
+Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup).
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md
@@ -99,7 +99,9 @@ Accept wildcard characters: False
 ```
 
 ### -PriorityCleanup
-{{ Fill PriorityCleanup Description }}
+The PriorityCleanup switch specifies whether to remove a Priority cleanup policy. You don't need to specify a value with this switch.
+
+Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup).
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md
@@ -101,7 +101,9 @@ Accept wildcard characters: False
 ```
 
 ### -PriorityCleanup
-{{ Fill PriorityCleanup Description }}
+The PriorityCleanup switch specifies whether to remove the rule associated with a Priority cleanup policy. You don't need to specify a value with this switch.
+
+Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup).
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/exchange/Search-MessageTrackingReport.md b/exchange/exchange-ps/exchange/Search-MessageTrackingReport.md
@@ -16,7 +16,7 @@ This cmdlet is functional only in on-premises Exchange.
 
 Use the Search-MessageTrackingReport cmdlet to find the unique message tracking report based on the search criteria provided. You can then pass this message tracking report ID to the Get-MessageTrackingReport cmdlet to get full message tracking information. For more information, see [Get-MessageTrackingReport](https://learn.microsoft.com/powershell/module/exchange/get-messagetrackingreport). The message tracking report cmdlets are used by the delivery reports feature.
 
-In Exchange Online, delivery reports has been replaced by message trace (the Get-MessageTrace and Get-MessageTraceDetail cmdlets).
+In Exchange Online, delivery reports are replaced by message trace (the Get-MessageTraceV2 and Get-MessageTraceDetailV2 cmdlets).
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
diff --git a/exchange/exchange-ps/exchange/Set-ComplianceTag.md b/exchange/exchange-ps/exchange/Set-ComplianceTag.md
@@ -300,7 +300,9 @@ Accept wildcard characters: False
 ```
 
 ### -PriorityCleanup
-{{ Fill PriorityCleanup Description }}
+The PriorityCleanup switch specifies whether to update the tag associated with a Priority cleanup policy. You don't need to specify a value with this switch.
+
+Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup).
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/exchange/Set-MailUser.md b/exchange/exchange-ps/exchange/Set-MailUser.md
@@ -1981,7 +1981,7 @@ Accept wildcard characters: False
 ### -LOBAppAccount
 This parameter is available only in the cloud-based service.
 
-{{ Fill LOBAppAccount Description }}
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md
@@ -790,7 +790,9 @@ Accept wildcard characters: False
 ```
 
 ### -PriorityCleanup
-{{ Fill PriorityCleanup Description }}
+The PriorityCleanup switch specifies whether to update a Priority cleanup policy. You don't need to specify a value with this switch.
+
+Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup).
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md
@@ -278,7 +278,9 @@ Accept wildcard characters: False
 ```
 
 ### -PriorityCleanup
-{{ Fill PriorityCleanup Description }}
+The PriorityCleanup switch specifies whether to update the rule associated with a Priority cleanup policy. You don't need to specify a value with this switch.
+
+Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup).
 
 ```yaml
 Type: SwitchParameter
diff --git a/teams/teams-ps/teams/Get-CsOnlineUser.md b/teams/teams-ps/teams/Get-CsOnlineUser.md
@@ -320,6 +320,17 @@ A recent fix has addressed an issue where some Guest users were being omitted fr
 - Conferencing_RequiresCommunicationCredits: Allows pay-per minute Audio Conferencing without monthly licenses.
 - CommunicationCredits: Enables users to pay Teams calling and conferencing through the credits.
 
+**Updates in Teams PowerShell Module verion 7.1.1 Preview and later**:
+
+- EffectivePolicyAssignments: The EffectivePolicyAssignments attribute has been added to the Get-CsOnlineUser cmdlet in commercial environments. This new attribute provides information about a user's effective policy assignments. Each assignment includes the following details:
+  - PolicyType - which specifies the type of policy assigned (for example, TeamsMeetingPolicy, TeamsCallingPolicy, and so on.)
+  - PolicyAssignment - which includes the display name of the assigned policy (displayName), the assignment type (assignmentType) indicating whether it is direct or group-based, the unique identifier of the policy (policyId), and the group identifier (groupId) if applicable.
+    **Note**: The policyId property isn't currently supported.
+  
+**Updates in Teams PowerShell Module**:
+
+- DialPlan: DialPlan attribute will be deprecated and no longer populated in the output of Get-CsOnlineUser in all clouds.
+  
 **Updates in Teams PowerShell Module version 7.0.0 and later**:
 
 - OptionFlags: OptionFlags attribute will no longer be populated with value in the output of Get-CsOnlineUser in all clouds. It's important to note that other details besides EnterpriseVoiceEnabled, previously found in OptionFlags, are no longer relevant for Teams. Administrators can still utilize the EnterpriseVoiceEnabled attribute in the output of the Get-CsOnlineUser cmdlet to get this information. This change will be rolled out to all Teams Powershell Module versions.
diff --git a/teams/teams-ps/teams/New-CsAutoAttendantCallFlow.md b/teams/teams-ps/teams/New-CsAutoAttendantCallFlow.md
@@ -15,6 +15,11 @@ ms.reviewer: williamlooney
 ## SYNOPSIS
 Use the New-CsAutoAttendantCallFlow cmdlet to create a new call flow.
 
+> [!CAUTION]
+> The following configuration parameters will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time.
+>
+> - -RingResourceAccountDelegates
+
 ## SYNTAX
 
 ```powershell
@@ -131,7 +136,31 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -RingResourceAccountDelegates
+
+If enabled for this call flow, Auto Attendant will first ring the delegates assigned to the resource account the call is on. If none of the delegates answer, the call is returned to the Auto Attendant for standard processing.
+
+If there are no delegates assigned to the resource account the call is on then the Auto Attendant will process the call normally.
+
+_Voice applications private preview customers only._
+
+_Saving an auto attendant configuration through Teams admin center will remove this setting._
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### CommonParameters
+
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS
diff --git a/teams/teams-ps/teams/New-CsTeamsMeetingPolicy.md b/teams/teams-ps/teams/New-CsTeamsMeetingPolicy.md
@@ -121,6 +121,7 @@ New-CsTeamsMeetingPolicy [-Identity] <XdsIdentity>
  [-WatermarkForScreenSharingPattern <String>]
  [-AllowedUsersForMeetingDetails <String>]
  [-RealTimeText <String>]
+ [-ParticipantSlideControl <string>]
  [-WhatIf]
  [-WhoCanRegister <Object>]
  [<CommonParameters>]
@@ -1912,6 +1913,31 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -ParticipantSlideControl
+>[!NOTE]
+>This feature has not been released yet and will have no changes if it is enabled or disabled.
+
+Determines whether participants can give control of presentation slides during meetings scheduled by this user. Set the type of users you want to be able to give control and be given control of presentation slides in meetings. Users excluded from the selected group will be prohibited from giving control, or being given control, in a meeting.
+
+Possible Values:
+- Everyone: Anyone in the meeting can give or take control
+- EveryoneInOrganization: Only internal AAD users and Multi-Tenant Organization (MTO) users can give or take control
+- EveryoneInOrganizationAndGuests: Only those who are Guests to the tenant, MTO users, and internal AAD users can give or take control
+- None: No one in the meeting can give or take control
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+Applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: Enabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -WhatIf
 Shows what would happen if the cmdlet runs.
 The cmdlet is not run.
diff --git a/teams/teams-ps/teams/Set-CsTeamsMeetingPolicy.md b/teams/teams-ps/teams/Set-CsTeamsMeetingPolicy.md
