diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md index 05d8755233..4144d034bc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md @@ -63,13 +63,13 @@ If the server hosting the test mailbox isn't available, the Test-OwaConnectivity If you run the Test-OwaConnectivity cmdlet on a Client Access server without using either the ClientAccessServer parameter or the URL parameter, the cmdlet tests the server on which you run the cmdlet. To test a specific Client Access server, use the ClientAccessServer parameter. -To test a single URL, run the Test-OwaConnectivity cmdlet with the URL parameter and credentials for an existing Exchange mailbox. If the URL is behind a load balancer, you can't predict which Client Access server the command will test. Because credentials are required as part of the parameters when you use the URL parameter, you can use any account to run the Test-OwaConnectivity cmdlet when you use the URL parameter. +To test a single URL, run the Test-OwaConnectivity cmdlet with the URL parameter and credentials for an existing Exchange mailbox. If the URL is behind a load balancer, you can't predict which Client Access server the command tests. Because credentials are required as part of the parameters when you use the URL parameter, you can use any account to run the Test-OwaConnectivity cmdlet when you use the URL parameter. If the command encounters a virtual directory that doesn't require Secure Sockets Layer (SSL), the command skips that directory unless the AllowUnsecureAccess parameter is used. If the AllowUnsecureAccess parameter is used, communications between servers are sent in clear text for purposes of the test. The Test-OwaConnectivity cmdlet can be run as a one-time interactive task or as a scheduled task under Microsoft System Center Operations Manager 2007 control. To run the Test-OwaConnectivity cmdlet as a System Center Operations Manager 2007 task, the Client Access test mailbox must be available on the Mailbox servers that the cmdlet tests against. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md index 76991b73a4..7e5870d3cf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md @@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange. Use the Test-PopConnectivity cmdlet to verify that the Microsoft Exchange POP3 service is working as expected. -**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -59,7 +59,7 @@ The test results are displayed on-screen. The cmdlet returns the following infor You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-PopConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\POP Test.html"`. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md index 3a86af6c76..45ec1f55f2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md @@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange. Use the Test-PowerShellConnectivity cmdlet to test client connectivity to Exchange remote PowerShell virtual directories. -**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -71,7 +71,7 @@ The test results are displayed on-screen. The cmdlet returns the following infor You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-PowerShellConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\PowerShell Test.html"`. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md index 16dd2f9e99..8e5467e89d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md @@ -37,7 +37,7 @@ Test-ReplicationHealth [[-Identity] ] ## DESCRIPTION The Test-ReplicationHealth cmdlet is designed for the proactive monitoring of continuous replication and the continuous replication pipeline, the availability of Active Manager and the health and status of the underlying cluster service, quorum and network components. The Test-ReplicationHealth cmdlet can be run locally or remotely against any Mailbox server in a DAG. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES @@ -163,7 +163,7 @@ Accept wildcard characters: False The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). -- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. +- $false: Monitoring events and performance counters aren't included in the command results. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md b/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md index 90f55ad910..d60fe06337 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md @@ -34,7 +34,7 @@ Test-SenderId -IPAddress -PurportedResponsibleDomain ## DESCRIPTION The Test-SenderId cmdlet provides the results of a Sender ID check for the IP address and the corresponding domain name that you specify. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md index 6ea5b4bb58..833a0a50b2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md @@ -32,9 +32,9 @@ Test-ServiceHealth [[-Server] ] ``` ## DESCRIPTION -This cmdlet isn't supported on Exchange 2013 Client Access servers (the cmdlet will return unexpected output). +This cmdlet isn't supported on Exchange 2013 Client Access servers (the cmdlet returns unexpected output). -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES @@ -138,7 +138,7 @@ Accept wildcard characters: False The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). -- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. +- $false: Monitoring events and performance counters aren't included in the command results. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md b/exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md index 957f3de564..b40a761d80 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md @@ -30,7 +30,7 @@ Test-ServicePrincipalAuthorization [-Identity] ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md index 2361c7f9ca..8620f8cc97 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md @@ -37,7 +37,7 @@ Test-SiteMailbox [[-Identity] ] ## DESCRIPTION If you don't specify the RequestorIdentity parameter, the command uses the identification of the user running this command. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md index 502a332306..5ad4bb647f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md @@ -42,7 +42,7 @@ When you run the Test-SmtpConnectivity cmdlet against a Mailbox server, the cmdl You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding ` > ` to the command. For example: `Test-SmtpConnectivity Mailbox01 | ConvertTo-Csv > "C:\My Documents\SMTP Test.csv"`. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES @@ -137,7 +137,7 @@ Accept wildcard characters: False The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). -- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. +- $false: Monitoring events and performance counters aren't included in the command results. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md index 5d3c22eb66..b12b185cce 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md @@ -48,7 +48,7 @@ Test-SystemHealth [-ADCredentials ] ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md b/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md index f703ca42a6..e22bd0b9d2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md @@ -13,7 +13,7 @@ title: Test-TextExtraction # Test-TextExtraction ## 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. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Test-TextExtraction cmdlet to return the text from unencrypted email message files. @@ -34,7 +34,7 @@ This cmdlet doesn't work on encrypted email message files. The Microsoft classification engine uses the results to classify content and determine the sensitive information types in the message file. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md index 5ca409cf40..d85acfead8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md @@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange. Use the Test-UMConnectivity cmdlet to test the operation of Unified Messaging (UM) servers. -**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -109,9 +109,9 @@ The Test-UMConnectivity cmdlet can be used to test the operation of a Mailbox se When you run this cmdlet in an on-premises Unified Messaging deployment, you need to create a UM IP gateway object for the computer or server that the cmdlet is testing. When you create the UM IP gateway object, you must configure it with a fully qualified domain name (FQDN) and that FQDN must match the name of the computer running this cmdlet. -After this task is complete, the cmdlet will have tested the operation of the Mailbox server and related telephony components. +After this task is complete, the cmdlet tested the operation of the Mailbox server and related telephony components. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES @@ -490,7 +490,7 @@ Accept wildcard characters: False The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). -- $false: Monitoring events and performance counters aren't included in the command results. This is the default value. +- $false: Monitoring events and performance counters aren't included in the command results. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md index db4d21c3d1..c156db20d0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md @@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange. Use the Test-WebServicesConnectivity cmdlet to test client connectivity to Exchange Web Services virtual directories. -**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. +**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -90,7 +90,7 @@ The test results are displayed on-screen. The cmdlet returns the following infor You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-WebServicesConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\EWS Test.html"`. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md index 9adf6497ad..e78381ee09 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md @@ -15,7 +15,7 @@ title: Undo-SoftDeletedMailbox ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that has been deleted. Mailboxes can be recovered within 30 days of being deleted. +Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that is deleted. Mailboxes can be recovered within 30 days of being deleted. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -45,11 +45,11 @@ Undo-SoftDeletedMailbox [-SoftDeletedObject] ``` ## DESCRIPTION -Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that has been deleted. When a mailbox is deleted with the Remove-Mailbox or Disable-Mailbox cmdlet, it's not actually deleted. It's hidden in Exchange and moved in Active Directory to the organizational unit (OU) Soft Deleted Objects. This enables administrators to recover deleted mailboxes for up to 30 days after deletion. +Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that is deleted. When a mailbox is deleted with the Remove-Mailbox or Disable-Mailbox cmdlet, it's not actually deleted. It's hidden in Exchange and moved in Active Directory to the organizational unit (OU) Soft Deleted Objects. This enables administrators to recover deleted mailboxes for up to 30 days after deletion. If the Microsoft account (formerly known as a Windows Live ID) wasn't deleted when the mailbox was deleted, you have to specify a new Microsoft account and password when you use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES @@ -65,7 +65,7 @@ This example recovers the deleted mailbox for the user Florence Flipo. When this Undo-SoftDeletedMailbox bjohnson@contoso.edu -WindowsLiveID brianj@contoso.edu -Password (Get-Credential).password ``` -This example recovers the deleted mailbox for the user Brian Johnson. When this mailbox was deleted, the associated Microsoft account wasn't deleted. Note that a new Microsoft account and password have to be created to recover this mailbox. In the scenario, the old Microsoft account is retained as a proxy address for the mailbox. +This example recovers the deleted mailbox for the user Brian Johnson. When this mailbox was deleted, the associated Microsoft account wasn't deleted. A new Microsoft account and password have to be created to recover this mailbox. In the scenario, the old Microsoft account is retained as a proxy address for the mailbox. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md index b9843c0afd..f8fa5fc6a6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md @@ -35,7 +35,7 @@ Soft-deleted Microsoft 365 Groups are groups that have been deleted, but can be To display all soft-deleted Microsoft 365 Groups in your organization, use the [Get-MgDirectoryDeletedItemAsGroup](https://learn.microsoft.com/powershell/module/microsoft.graph.identity.directorymanagement/get-mgdirectorydeleteditemasgroup) cmdlet in Microsoft Graph PowerShell. To permanently remove (purge) a soft-deleted Microsoft 365 Group, use the [Remove-MgDirectoryDeletedItem](https://learn.microsoft.com/powershell/module/microsoft.graph.identity.directorymanagement/remove-mgdirectorydeleteditem) cmdlet in Microsoft Graph PowerShell. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md index 016b827ab3..c4dbca1080 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md @@ -37,7 +37,7 @@ You can install and uninstall transport agents in the following locations: - The Front End Transport service on Mailbox servers. - Edge Transport servers. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md index f932437a97..b9d2e639b6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md @@ -30,7 +30,7 @@ Update-AddressList [-Identity] ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md index 57863d7f9f..95df48bd89 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md @@ -74,7 +74,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Members parameter specifies the users that will replace the current eDiscovery case members. You can use any value that uniquely identifies the user. For example: +The Members parameter specifies the users that replace the current eDiscovery case members. You can use any value that uniquely identifies the user. For example: - Name - Distinguished name (DN) diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md b/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md index a23646c719..28b74be06b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md @@ -15,7 +15,7 @@ title: Update-DatabaseSchema ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Update-DatabaseSchema cmdlet to upgrade the database schema for one or more databases after an Exchange software update that includes database schema updates has been installed on Mailbox servers in a database availability group (DAG). Some software updates for Exchange may include database schema updates. After such an update has been installed on all members of a DAG, the administrator must run the Update-DatabaseSchema cmdlet for each database in the DAG and dismount/mount or failover the database to trigger the database schema update. The in-place database schema upgrade engine ensures that no schema updates occur until all members of the DAG have compatible versions of the software. +Use the Update-DatabaseSchema cmdlet to upgrade the database schema for one or more databases after an Exchange software update that includes database schema updates is installed on Mailbox servers in a database availability group (DAG). Some software updates for Exchange might include database schema updates. After such an update is installed on all members of a DAG, the administrator must run the Update-DatabaseSchema cmdlet for each database in the DAG and dismount/mount or failover the database to trigger the database schema update. The in-place database schema upgrade engine ensures that no schema updates occur until all members of the DAG have compatible versions of the software. 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,7 +29,7 @@ Update-DatabaseSchema [-Identity] -MajorVersion - ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md index 797e2d1195..77501dbf64 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md @@ -13,7 +13,7 @@ title: Update-DistributionGroupMember # Update-DistributionGroupMember ## 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. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Update-DistributionGroupMember cmdlet to replace all members of distribution groups and mail-enabled security groups. To add or remove existing group members, use the Add-DistributionGroupMember and Remove-DistributionGroupMember cmdlets. @@ -32,7 +32,7 @@ Update-DistributionGroupMember [-Identity] ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES @@ -138,7 +138,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The Members parameter specifies the recipients (mail-enabled objects) that will replace the current group members. You can use any value that uniquely identifies the recipient. For example: +The Members parameter specifies the recipients (mail-enabled objects) that replace the current group members. You can use any value that uniquely identifies the recipient. For example: - Name - Alias @@ -149,7 +149,7 @@ The Members parameter specifies the recipients (mail-enabled objects) that will You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. -Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) won't have the permissions assigned. +Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) don't have the permissions assigned. The maximum number of entries for this parameter is 10000. diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md index 57d5e9ca5d..c93914c149 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md @@ -32,7 +32,7 @@ Update-EmailAddressPolicy [-Identity] ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md b/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md index 4d5145517d..9c99530bbe 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md @@ -31,7 +31,7 @@ The Update-ExchangeHelp cmdlet is available in Exchange Server 2013 or later. You need to run the Update-ExchangeHelp cmdlet on each Exchange server. By default, the cmdlet requires an Internet connection, but you can configure an offline mode. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES @@ -50,7 +50,7 @@ This example checks for the latest available version of Help for the Exchange Ma The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -By default, the Update-ExchangeHelp cmdlet has a throttling period of 24 hours. If you run this cmdlet within 24 hours of the last time you ran it, it won't check for updates. You can use this switch to force the cmdlet to check for updates more frequently and to display status or error messages. +By default, the Update-ExchangeHelp cmdlet has a throttling period of 24 hours. If you run this cmdlet within 24 hours of the last time you ran it, the cmdlet doesn't check for updates. You can use this switch to force the cmdlet to check for updates more frequently and to display status or error messages. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md b/exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md index 62bd156223..c7ef1e4eaf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md @@ -35,7 +35,7 @@ The Update-FileDistributionService cmdlet forces the Microsoft Exchange File Dis If you don't use the Type parameter when running this command, OAB, Unified Messaging, and Group Metrics data are reloaded. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md index 9122493067..4a98c2846a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md @@ -30,7 +30,7 @@ Update-GlobalAddressList [-Identity] ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md index 25c53663ef..32694c56bb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md @@ -13,7 +13,7 @@ title: Update-HybridConfiguration # Update-HybridConfiguration ## 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. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Update-HybridConfiguration cmdlet to define the credentials that are used to update the hybrid configuration object. @@ -32,7 +32,7 @@ Update-HybridConfiguration -OnPremisesCredentials -TenantCredenti ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md index 388cc0d20a..67ea153698 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md @@ -80,7 +80,7 @@ The Update-MailboxDatabaseCopy cmdlet can also be used to seed a content index c You must suspend a database copy before you can update it using the Update-MailboxDatabaseCopy cmdlet. For detailed steps about how to suspend a database copy, see [Suspend or resume a mailbox database copy](https://learn.microsoft.com/Exchange/high-availability/manage-ha/suspend-resume-db-copies). -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES @@ -352,7 +352,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Network parameter specifies which DAG network should be used for seeding. Note that content index catalog seeding always occurs over the MAPI network, even if you use this parameter to specify the DAG network. +The Network parameter specifies which DAG network should be used for seeding. Content index catalog seeding always occurs over the MAPI network, even if you use this parameter to specify the DAG network. ```yaml Type: DatabaseAvailabilityGroupNetworkIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md index 24c1ffe456..a3de0ee78b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md @@ -31,7 +31,7 @@ Update-OfflineAddressBook [-Identity] ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md index 7bf00fe065..3c4332d4c8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md @@ -30,7 +30,7 @@ Update-PublicFolder [-Identity] -Server ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md index 3980dd3f42..0b48213ae6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md @@ -13,7 +13,7 @@ title: Update-PublicFolderMailbox # Update-PublicFolderMailbox ## 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. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Update-PublicFolderMailbox cmdlet to update the hierarchy for public folders. @@ -48,7 +48,7 @@ Update-PublicFolderMailbox [-Identity] -FolderId Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The ReconcileFolders switch specifies whether to look closely for differences in the folder hierarchy between the primary public folder mailbox and the secondary public folder mailbox. Folders that exist in the primary public folder mailbox and not in the secondary will be recreated. You don't need to specify a value with this switch. +The ReconcileFolders switch specifies whether to look closely for differences in the folder hierarchy between the primary public folder mailbox and the secondary public folder mailbox. Folders that exist in the primary public folder mailbox and not in the secondary are recreated. You don't need to specify a value with this switch. -In on-premises Exchange, folders that exist in the secondary public folder mailbox and not in the primary will be deleted. +In on-premises Exchange, folders that exist in the secondary public folder mailbox and not in the primary are deleted. -In Exchange Online, folders that exist in the secondary public folder mailbox and not in the primary will be moved to \NON_IPM_SUBTREE\LOST_AND_FOUND. See [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/introducing-public-folder-8220-lost-and-found-8221-functionality/ba-p/604043) for more details about LOST_AND_FOUND functionality. +In Exchange Online, folders that exist in the secondary public folder mailbox and not in the primary are moved to \NON_IPM_SUBTREE\LOST_AND_FOUND. See [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/introducing-public-folder-8220-lost-and-found-8221-functionality/ba-p/604043) for more details about LOST_AND_FOUND functionality. In both the scenarios, public folders that were deleted or moved to LOST_AND_FOUND can be restored using Set-PublicFolder command. @@ -250,7 +250,7 @@ This example restores the public folder named "Documents" from LOST_AND_FOUND to `Set-PublicFolder -Identity \NON_IPM_SUBTREE\DUMPSTER_ROOT\DUMPSTER_EXTEND\RESERVED_1\RESERVED_1\9f32c468-4bc2-42aa-b979-16a057394b2f\Documents -Path \Engineering` -**Note**: You should use the ReconcileFolders switch only for repair or troubleshooting purposes to look for differences in the public folder hierarchy that aren't detected by a regular synchronization. These undetected differences may occur in database failover or disaster recovery scenarios. You must use this switch with the InvokeSynchronizer switch. +**Note**: You should use the ReconcileFolders switch only for repair or troubleshooting purposes to look for differences in the public folder hierarchy that aren't detected by a regular synchronization. These undetected differences might occur in database failover or disaster recovery scenarios. You must use this switch with the InvokeSynchronizer switch. ```yaml Type: SwitchParameter @@ -268,11 +268,11 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The SuppressStatus switch specifies that the output of this cmdlet is suppressed and that the command will run asynchronously in the background from the Exchange Management Shell. You don't need to specify a value with this switch. +The SuppressStatus switch specifies that the output of this cmdlet is suppressed and that the command runs asynchronously in the background from the Exchange Management Shell. You don't need to specify a value with this switch. You can only use this switch with the InvokeSynchronizer switch. -If you don't use this switch, the output will display status messages every 3 seconds for up to one minute. Until the minute passes, you can't use the PowerShell Window for other commands. +If you don't use this switch, the output displays status messages every 3 seconds for up to one minute. Until the minute passes, you can't use the PowerShell Window for other commands. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md b/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md index 3e39709f1d..df0c783950 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md @@ -13,7 +13,7 @@ title: Update-Recipient # Update-Recipient ## 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. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Update-Recipient cmdlet to add Exchange attributes to recipient objects. @@ -37,7 +37,7 @@ In on-premises Exchange, before you can run the Update-Recipient cmdlet to conve - mailNickname - msExchHomeServerName -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md index 8bb7860a0c..c9a3ecf00f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md @@ -13,7 +13,7 @@ title: Update-RoleGroupMember # Update-RoleGroupMember ## 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. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Update-RoleGroupMember cmdlet to modify the members of a management role group. @@ -36,13 +36,13 @@ The Update-RoleGroupMember cmdlet enables you to replace the entire membership l The Add-RoleGroupMember and Remove-RoleGroupMember cmdlets can be used to add or remove role group members. You can combine these cmdlets with other cmdlets, such as Get-Mailbox, to add or remove multiple members without overwriting the entire membership list at once. -If the ManagedBy property has been populated with role group managers, the user updating role group membership must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. +If the ManagedBy property is populated with role group managers, the user updating role group membership must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. If the role group is a linked role group, you can't use the Update-RoleGroupMember cmdlet to modify members on the role group. Instead, you need to modify members on the foreign universal security group (USG) that's linked to the linked role group. To find the foreign USG that's linked to a role group, use the Get-RoleGroup cmdlet. For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md b/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md index df0c3abf32..9317fb9dd9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md @@ -35,9 +35,9 @@ Update-SafeList [-Identity] ## DESCRIPTION The Update-SafeList cmdlet reads the safelist aggregation data stored on a Microsoft Outlook user mailbox and then hashes and writes the data to the corresponding user object in Active Directory. The command compares the binary attribute created to any value stored on the attribute. If the two values are identical, the command doesn't update the user attribute value with the safelist aggregation data. Safelist aggregation data contains the Outlook user's Safe Senders List and Safe Recipients List. -Be mindful of the network and replication traffic that may be generated when you run the Update-SafeList cmdlet. Running the command on multiple mailboxes where safelists are heavily used may generate a significant amount of traffic. We recommend that if you run the command on multiple mailboxes, you should run the command during off-peak, non-business hours. +Be mindful of the network and replication traffic that might be generated when you run the Update-SafeList cmdlet. Running the command on multiple mailboxes where safelists are heavily used might generate a significant amount of traffic. We recommend that if you run the command on multiple mailboxes, you should run the command during off-peak, non-business hours. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES @@ -155,7 +155,7 @@ The IncludeDomains switch specifies whether to include the sender domains specif By default, domains specified by the senders aren't included. -In most cases, we don't recommend that you include domains because users may include the domains of large Internet service providers (ISPs), which could unintentionally provide addresses that may be used or spoofed by spammers. +In most cases, we don't recommend that you include domains because users might include the domains of large Internet service providers (ISPs), which could unintentionally provide addresses that might be used or spoofed by spammers. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md index 8c732c49eb..36d54dd832 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md @@ -15,7 +15,7 @@ title: Update-SiteMailbox ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Update-SiteMailbox cmdlet to trigger a Microsoft SharePoint synchronization. This command synchronizes document content membership and permissions into Microsoft Exchange. You may need to perform this action when troubleshooting document or membership synchronization issues. +Use the Update-SiteMailbox cmdlet to trigger a Microsoft SharePoint synchronization. This command synchronizes document content membership and permissions into Microsoft Exchange. You might need to perform this action when troubleshooting document or membership synchronization issues. Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). @@ -38,7 +38,7 @@ Update-SiteMailbox [-Identity] ## DESCRIPTION If you are running this command against a site mailbox in which you aren't the owner, you need to use the BypassOwnerCheck parameter to run this cmdlet. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES @@ -128,7 +128,9 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The FullSync switch specifies full sync is expensive and will have a performance impact on the Exchange system. You don't need to specify a value with this switch. +The FullSync switch specifies a full synchronization. You don't need to specify a value with this switch. + +Full synchronizations are expensive and affect the performance of the Exchange system. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md b/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md index 4af3a76895..8c97f75874 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md @@ -29,9 +29,9 @@ Update-StoreMailboxState -Database -Identity Applicable: Security & Compliance -The Users parameter specifies the users that will replace the current eDiscovery Administrators. You can use any value that uniquely identifies the user. For example: +The Users parameter specifies the users that replaces the current eDiscovery Administrators. You can use any value that uniquely identifies the user. For example: - Name - Distinguished name (DN) diff --git a/exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md index 1545b8ffa2..3a013933e6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md @@ -32,7 +32,7 @@ Upgrade-DistributionGroup [-DlIdentities] ``` ## DESCRIPTION -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md index a68eaf0cde..1a4f895aa1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md @@ -36,7 +36,7 @@ The Validate-OutboundConnector cmdlet performs two tests on the specified connec - SMTP connectivity to each smart host that's defined on the connector. - Send test email messages to one or more recipients in the domain that's configured on the connector. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md index 71ab87ec02..c4eb0f5b84 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md @@ -13,7 +13,7 @@ title: Write-AdminAuditLog # Write-AdminAuditLog ## 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. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Write-AdminAuditLog cmdlet to write a comment to the administrator audit log. @@ -34,7 +34,7 @@ When the Write-AdminAuditLog cmdlet runs, the value provided in the Comment para For the Write-AdminAuditLog cmdlet to write to the audit log, it must be included in the list of cmdlets being logged by administrator audit logging. -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). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). ## EXAMPLES