Merge pull request #13080 from MicrosoftDocs/main

[AutoPublish] main to live - 08/28 10:31 PDT | 08/28 23:01 IST

Author: m365-skilling-repo-management[bot]

exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md

@@ -593,7 +593,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is deprecated from the cloud-based service. Admins must review the [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs) and any skipped items before the import completes.
+**Note**: This parameter has been deprecated in the cloud-based service. [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs) is used instead and tenant admins must review the DataConsistencyScore and any skipped items after the restore completes.
 
 ```yaml
 Type: Unlimited
@@ -910,7 +910,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is deprecated from the cloud-based service. Admins must review the [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs) and any skipped items before the restore completes.
+**Note**: This parameter has been deprecated in the cloud-based service. [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs) is used instead and tenant admins must review the DataConsistencyScore and any skipped items after the restore completes.
 
 ```yaml
 Type: Unlimited

teams/teams-ps/MicrosoftTeams/Set-CsTeamsMessagingConfiguration.md

@@ -65,10 +65,10 @@ Accept wildcard characters: False
 
 ### -ContentBasedPhishingCheck
 
->[!NOTE]
->This feature has not been released yet and will have no changes if it is enabled or disabled.
+> [!NOTE]
+> This feature has not been released.
 
-This setting determines if Content Based Phishing Check in teams messaging across the whole tenant
+This setting enables content-based phishing detection for Teams messages in the tenant.
 
 Possible Values:
 - Enabled
@@ -139,10 +139,10 @@ Accept wildcard characters: False
 
 ### -FileTypeCheck
 
->[!NOTE]
->This feature has not been released yet and will have no changes if it is enabled or disabled.
+> [!NOTE]
+> This parameter is in Private Preview.
 
-This setting determines if FileType check in teams messaging across the whole tenant
+This setting enables weaponizable file detection in Teams messages in the tenant.
 
 Possible Values:
 - Enabled
@@ -210,10 +210,10 @@ Accept wildcard characters: False
 
 ### -ReportIncorrectSecurityDetections
 
->[!NOTE]
->This feature has not been released yet and will have no changes if it is enabled or disabled.
+> [!NOTE]
+> This parameter is in Private Preview.
 
-This setting determines if Report Incorrect Security Detections is enabled in teams messaging across the whole tenant
+This setting enables the end users to Report incorrect security detections in Teams messages in the tenant.
 
 Possible Values:
 - Enabled
@@ -233,10 +233,10 @@ Accept wildcard characters: False
 
 ### -UrlReputationCheck
 
->[!NOTE]
->This feature has not been released yet and will have no changes if it is enabled or disabled.
+> [!NOTE]
+> This parameter is in Private Preview.
 
-This setting determines if UrlReputationCheck check in teams messaging across the whole tenant
+This setting enables malicious URL detection in Teams messages in the tenant.
 
 Possible Values:
 - Enabled