From 41c8f8a854f478114139d6b0bf849340b9a60d40 Mon Sep 17 00:00:00 2001 From: wesmimsft <121474465+wesmimsft@users.noreply.github.com> Date: Tue, 12 Aug 2025 11:23:40 -0700 Subject: [PATCH 1/2] Update New-MoveRequest.md to clarify when to check status Fixing use of incorrect verb (restore vs move) and timing of checking DCS. --- exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md index 3f7a362caf..2bca08b794 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md @@ -559,7 +559,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 in the cloud-based service. [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs) is used instead. Admins must review the DataConsistencyScore and any skipped items after the restore completes. +**Note**: This parameter is deprecated in the cloud-based service. [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs) is used instead. Admins must review the DataConsistencyScore and any skipped items before the move completes. ```yaml Type: Unlimited @@ -840,7 +840,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 in the cloud-based service. [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs). Admins must review the DataConsistencyScore and any skipped items after the restore completes. +**Note**: This parameter is deprecated in the cloud-based service. [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs). Admins must review the DataConsistencyScore and any skipped items before the move completes. ```yaml Type: Unlimited From bc9ea492a715659544b9036b6fc34f2622ade8b2 Mon Sep 17 00:00:00 2001 From: Nicolas Riderelli Date: Mon, 29 Sep 2025 18:18:20 -0300 Subject: [PATCH 2/2] Fixing typo --- .../docs-conceptual/connect-exo-powershell-managed-identity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md b/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md index 8476642eae..794e562e3b 100644 --- a/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md +++ b/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md @@ -131,7 +131,7 @@ After you've successfully created the PowerShell runbook, do the following steps 3. On the **Runbooks** flyout that opens, select the runbook. 4. On the details page of the runbook, select **Start**. -### Connect to Exchange Online PowerShell using Azure VMs with system-assigned managed identities +### Connect to Exchange Online PowerShell using Azure VMs with user-assigned managed identities In a Windows PowerShell window in the Azure VM, use the command as described in the beginning of this section. For example: