diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md index 0779c91d83..a16c7bb305 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md @@ -28,7 +28,7 @@ Get-X400AuthoritativeDomain [[-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/Import-DlpPolicyCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md index 0785727433..52656dd2d1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md @@ -13,7 +13,7 @@ title: Import-DlpPolicyCollection # Import-DlpPolicyCollection ## SYNOPSIS -**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). +**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). This cmdlet is functional only in on-premises Exchange. @@ -37,7 +37,7 @@ The Import-DlpPolicyCollection cmdlet imports all the settings of the DLP polici Importing a DLP policy collection from an XML file removes or overwrites all pre-existing DLP policies that were defined in your organization. Make sure that you have a backup of your current DLP policy collection before you import and overwrite your current DLP policies. -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/Import-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md index 7cd67448e0..812c878550 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md @@ -29,7 +29,7 @@ Import-DlpPolicyTemplate [-FileData] ``` ## 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/Import-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md index 16a6171171..506ea14827 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md @@ -72,7 +72,7 @@ There are many factors to consider when you configure certificates for Transport Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration). -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 @@ -157,7 +157,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: String[] @@ -263,7 +263,7 @@ Accept wildcard characters: False The PrivateKeyExportable parameter specifies whether the certificate has an exportable private key and controls whether you can export the certificate from this server. Valid values are: - $true: The private key is exportable, so you can export the certificate from this server. -- $false: The private key isn't exportable, so you can't export the certificate from this server. This is the default value. +- $false: The private key isn't exportable, so you can't export the certificate from this server. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md index 20711926b1..66936d5797 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md @@ -36,7 +36,7 @@ Importing a journal rule collection from an XML file removes or overwrites all p For more information about how to export a journal rule collection to an XML file, see [Export-JournalRuleCollection](https://learn.microsoft.com/powershell/module/exchangepowershell/export-journalrulecollection). -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/Import-RecipientDataProperty.md b/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md index 4aa0575df7..772de76e50 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md @@ -42,7 +42,7 @@ Import-RecipientDataProperty [-Identity] -FileDa ``` ## 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/Import-TransportRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md index ac58f3c39e..cb5499437f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md @@ -37,7 +37,7 @@ Importing a transport rule collection from an XML file removes or overwrites all For information about how to export a transport rule collection to an XML file, see [Export-TransportRuleCollection](https://learn.microsoft.com/powershell/module/exchangepowershell/export-transportrulecollection). -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/Import-UMPrompt.md b/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md index 84ada54feb..69b9d8c936 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md @@ -62,7 +62,7 @@ The Import-UMPrompt cmdlet imports custom greeting audio files into UM dial plan After this task is completed, the custom audio file can be used by a UM dial plan or auto attendant. -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 @@ -131,7 +131,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -The PromptFileStream parameter specifies whether the audio file will be uploaded or imported as an audio stream and not a byte array. The default setting is for the audio file to imported as a byte array. +The PromptFileStream parameter specifies whether the audio file is uploaded or imported as an audio stream and not a byte array. The default setting is for the audio file to imported as a byte array. ```yaml Type: Stream diff --git a/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md index 92cf1ae653..b05098dde5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md @@ -31,9 +31,9 @@ Install-TransportAgent [-Name] -AssemblyPath -TransportAgentFa ``` ## DESCRIPTION -Transport agents have full access to all email messages that they encounter. Exchange puts no restrictions on a transport agent's behavior. Transport agents that are unstable or contain security flaws may affect the stability and security of Exchange. Therefore, you need to only install transport agents that you fully trust and that have been fully tested. +Transport agents have full access to all email messages that they encounter. Exchange puts no restrictions on a transport agent's behavior. Transport agents that are unstable or contain security flaws might affect the stability and security of Exchange. Therefore, you need to only install transport agents that you fully trust and that have been fully tested. -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/Invoke-ComplianceSearchActionStep.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md index 2faa34ef03..815fd65f2d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md +++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md @@ -13,7 +13,7 @@ title: Invoke-ComplianceSearchActionStep # Invoke-ComplianceSearchActionStep ## 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. This cmdlet is reserved for internal Microsoft use. diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md index 7292433a9c..62068c483c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md +++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md @@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange. Use the Invoke-MonitoringProbe cmdlet to run a Managed Availability probe on a selected server. -This cmdlet cannot be used to run every Managed Availability probe. Only some probes (mainly the deep test probes) can be run manually using this cmdlet. Probes that cannot be run with this cmdlet will generate an error message when Invoke-MonitoringProbe is used to run them. +This cmdlet can't be used to run every Managed Availability probe. Only some probes (mainly the deep test probes) can be run manually using this cmdlet. Probes that can't be run with this cmdlet return error messages when you use Invoke-MonitoringProbe to run them. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -38,7 +38,7 @@ Invoke-MonitoringProbe [-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 @@ -98,7 +98,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Account parameter specifies the identity of the mailbox or user account that will run the monitoring probe. +The Account parameter specifies the identity of the mailbox or user account that's used to run the monitoring probe. ```yaml Type: String @@ -134,7 +134,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The ItemTargetExtension parameter specifies cmdlet extension data that you can pass to the monitoring probe. The probe that runs on the server may require specific data for its execution. This data is presented to the probe on execution in an XML format. +The ItemTargetExtension parameter specifies cmdlet extension data that you can pass to the monitoring probe. The probe that runs on the server might require specific data for its execution. This data is presented to the probe on execution in an XML format. ```yaml Type: String @@ -152,7 +152,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Password parameter specifies the password of the mailbox or user account that will run the monitoring probe. +The Password parameter specifies the password of the mailbox or user account that's used to run the monitoring probe. ```yaml Type: String @@ -188,7 +188,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The SecondaryAccount parameter specifies the identity of the delegate mailbox or user account that will run the monitoring probe. +The SecondaryAccount parameter specifies the identity of the delegate mailbox or user account that's used to run the monitoring probe. ```yaml Type: String @@ -224,7 +224,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The SecondaryPassword parameter specifies the password of the delegate mailbox or user account that will run the monitoring probe. +The SecondaryPassword parameter specifies the password of the delegate mailbox or user account that's used to run the monitoring probe. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md index b9d8d46279..041d064d31 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md +++ b/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md @@ -33,7 +33,7 @@ Mount-Database [-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/Move-ActiveMailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md index 20923aba50..34ab7820b4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md @@ -100,7 +100,7 @@ Move-ActiveMailboxDatabase [-Identity] [-ActivateOnServer] ``` ## 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 @@ -130,7 +130,7 @@ This example performs a switchover of the database DB3 to the Mailbox server MBX Move-ActiveMailboxDatabase -Server MBX1 ``` -This example performs a server switchover for the Mailbox server MBX1. All active mailbox database copies on MBX1 will be activated on one or more other Mailbox servers with healthy copies of the active databases on MBX1. +This example performs a server switchover for the Mailbox server MBX1. All active mailbox database copies on MBX1 are activated on one or more other Mailbox servers with healthy copies of the active databases on MBX1. ## PARAMETERS @@ -291,13 +291,13 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The MountDialOverride parameter is used to override the auto database mount dial (AutoDatabaseMountDial) setting for the target server and specify an alternate setting. The following are possible values: +The MountDialOverride parameter is used to override the auto database mount dial (AutoDatabaseMountDial) setting for the target server and specify an alternate setting. Valid value are: -- None: When using this value, the currently configured auto database mount dial setting on the target server will be used. -- Lossless: This is the default value. When using this value, the database doesn't automatically mount until all log files that were generated on the original active copy have been copied to the passive copy. -- GoodAvailability: If you specify this value, the database automatically mounts immediately after a failover if the copy queue length is less than or equal to 6. If the copy queue length is greater than 6, the database doesn't automatically mount. When the copy queue length is less than or equal to 6, Microsoft Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database. -- BestEffort: If you specify this value, the database automatically mounts regardless of the size of the copy queue length. Because the database will mount with any amount of log loss, using this value could result in a large amount of data loss. -- BestAvailability: If you specify this value, the database automatically mounts immediately after a failover if the copy queue length is less than or equal to 12. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than 12, the database doesn't automatically mount. When the copy queue length is less than or equal to 12, Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database. +- None: The currently configured auto database mount dial setting on the target server is used. +- Lossless: This value is the default. The database doesn't automatically mount until all log files that were generated on the original active copy have been copied to the passive copy. +- GoodAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to 6. If the copy queue length is greater than 6, the database doesn't automatically mount. When the copy queue length is less than or equal to 6, Microsoft Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database. +- BestEffort: The database automatically mounts regardless of the size of the copy queue length. Because the database mounts with any amount of log loss, using this value could result in a large amount of data loss. +- BestAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to 12. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than 12, the database doesn't automatically mount. When the copy queue length is less than or equal to 12, Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database. ```yaml Type: DatabaseMountDialOverride @@ -373,7 +373,7 @@ Accept wildcard characters: False The SkipClientExperienceChecks switch specifies whether to skip the search catalog (content index) state check to see if the search catalog is healthy and up to date. You don't need to specify a value with this switch. -If the search catalog for the database copy you're activating is in an unhealthy or unusable state and you use this parameter to skip the search catalog health check and activate the database copy, you will need to either re-crawl or reseed the search catalog. +If the search catalog for the database copy you're activating is in an unhealthy or unusable state and you use this parameter to skip the search catalog health check and activate the database copy, you need to either re-crawl or reseed the search catalog. ```yaml Type: SwitchParameter @@ -449,7 +449,7 @@ Accept wildcard characters: False The SkipMaximumActiveDatabasesChecks switch specifies whether to skip checking the value of MaximumPreferredActiveDatabases during the best copy and server selection (BCSS) process. You don't need to specify a value with this switch. -Any configured value for MaximumActiveDatabases will still be honored during the BCSS process and by the Information Store. +Any configured value for MaximumActiveDatabases is honored during the BCSS process and by the Information Store. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md index 8a33bcacdd..fa8ea18b19 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md @@ -30,7 +30,7 @@ Move-AddressList [-Identity] -Target ``` ## 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/New-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md index 05e0967f85..1f49fba1f2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md @@ -41,7 +41,7 @@ For more information about preset security policies in PowerShell, see [Preset s > [!IMPORTANT] > Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). -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/New-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md index 5d3eb131cf..5ad446e0c5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md @@ -45,7 +45,7 @@ For more information about preset security policies in PowerShell, see [Preset s > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). -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 @@ -84,7 +84,7 @@ Accept wildcard characters: False The SafeAttachmentPolicy parameter specifies the existing Safe Attachments policy that's associated with the preset security policy. -If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy will be one of the following values: +If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy is one of the following values: - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650008019`. - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034872546`. @@ -109,7 +109,7 @@ Accept wildcard characters: False The SafeLinksPolicy parameter specifies the existing Safe Links policy that's associated with the preset security policy. -If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy will be one of the following values: +If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy is one of the following values: - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650008534`. - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034873192`. @@ -173,7 +173,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: -- $true: The rule is enabled. The State value of the rule is Enabled. This is the default value. +- $true: The rule is enabled. The State value of the rule is Enabled. This value is the default. - $false: The rule is disabled. The State value of the rule is Disabled. After you create the rule, you turn on or turn off the preset security policy using one of the following commands: diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md index 7b60a5bca3..bd520684c0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md @@ -31,7 +31,7 @@ New-AcceptedDomain [-Name] -DomainName ``` ## 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 @@ -68,7 +68,7 @@ Accept wildcard characters: False The DomainName parameter specifies the SMTP domain that you want to establish as an accepted domain. Valid input for the DomainName parameter is an SMTP domain. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: \*.contoso.com. -However, you can't embed a wildcard character, as shown in the following example: domain.\*.contoso.com. The domain name string may not contain more than 256 characters. +However, you can't embed a wildcard character, as shown in the following example: domain.\*.contoso.com. The domain name string might not contain more than 256 characters. ```yaml Type: SmtpDomainWithSubdomains diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md index 81e0237759..831cfa333c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md @@ -13,7 +13,7 @@ title: New-ActiveSyncDeviceAccessRule # New-ActiveSyncDeviceAccessRule ## 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 New-ActiveSyncDeviceAccessRule cmdlet to define the access levels for Exchange ActiveSync devices based on the identity of the device. @@ -32,7 +32,7 @@ New-ActiveSyncDeviceAccessRule -AccessLevel -Characteristic ## DESCRIPTION You can create multiple rules that define groups of devices: Allowed devices, blocked devices and quarantined devices. -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/New-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md index 9d14e34c18..2b7ff6ccd4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md @@ -13,7 +13,7 @@ title: New-ActiveSyncMailboxPolicy # New-ActiveSyncMailboxPolicy ## 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 New-ActiveSyncMailboxPolicy cmdlet to create a Microsoft Mobile Device mailbox policy object. @@ -89,7 +89,7 @@ The New-ActiveSyncMailboxPolicy cmdlet creates a Mobile Device mailbox policy fo Some Mobile Device mailbox policy settings require the mobile device to have certain built-in features that enforce these security and device management settings. If your organization allows all devices, you must set the AllowNonProvisionableDevices parameter to $true. This allows devices that can't enforce all policy settings to synchronize with your server. -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 @@ -112,7 +112,7 @@ This example creates the Mobile Device mailbox policy Management that has severa New-ActiveSyncMailboxPolicy -Name:"Contoso" -DevicePasswordEnabled:$true -AlphanumericDevicePasswordRequired:$true -PasswordRecoveryEnabled:$true -MinDevicePasswordComplexCharacters:3 -IsDefault:$true -DevicePasswordHistory:10 ``` -This example creates the Mobile Device mailbox policy Contoso that has several preconfigured values. This policy is configured to be the default policy for the organization. The default policy will be assigned to all new users. +This example creates the Mobile Device mailbox policy Contoso that has several preconfigured values. This policy is configured to be the default policy for the organization. The default policy is assigned to all new users. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md index 7580c9fdba..ff2968558b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md @@ -45,7 +45,7 @@ New-ActiveSyncVirtualDirectory [-ApplicationRoot ] ## DESCRIPTION The New-ActiveSyncVirtualDirectory cmdlet creates an Exchange ActiveSync virtual directory on the specified server under the specified website. The Exchange ActiveSync virtual directory created is named Microsoft-Server-ActiveSync. Only one Exchange ActiveSync virtual directory can exist in each Exchange ActiveSync website. -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 @@ -157,7 +157,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -177,7 +177,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -198,8 +198,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md index 0549ac3edd..36f586f9a4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md @@ -13,9 +13,9 @@ title: New-AddressBookPolicy # New-AddressBookPolicy ## 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 New-AddressBookPolicy cmdlet to create an address book policy. Address book policies define the global address list (GAL), offline address book (OAB), room list, and address lists that will be displayed to mailbox users who are assigned the policy. +Use the New-AddressBookPolicy cmdlet to create an address book policy. Address book policies define the global address list (GAL), offline address book (OAB), room list, and address lists shown to mailbox users who are assigned the policy. In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). @@ -32,7 +32,7 @@ New-AddressBookPolicy [-Name] -AddressLists ``` ## 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 @@ -73,7 +73,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The AddressLists parameter specifies the address lists that will be used by mailbox users who are assigned this address book policy. This parameter accepts multiple values, which should be separated by a comma. For example, "\\Mr. Munson's Class","Mrs. McKay's Class","Mrs. Count's Class". +The AddressLists parameter specifies the address lists for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the address list. For example: + +- Name +- Distinguished name (DN) +- GUID + +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"`. + +You can find the identify values of address lists by using the Get-AddressList cmdlet. ```yaml Type: AddressListIdParameter[] @@ -91,7 +99,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The GlobalAddressList parameter specifies the identity of the GAL that will be used by mailbox users who are assigned this address book policy. You can specify only one GAL for each address book policy. +The GlobalAddressList parameter specifies the GAL for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the GAL. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can find the identify values of GALs by using the Get-GlobalAddressList cmdlet. + +You can specify only one GAL for each address book policy. ```yaml Type: GlobalAddressListIdParameter @@ -109,7 +125,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The OfflineAddressBook parameter specifies the identity of the OAB that will be used by mailbox users who are assigned this address book policy. You can specify only one OAB for each address book policy. +The OfflineAddressBook parameter specifies the OAB for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the OAB. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can find the identify values of OABs by using the Get-OfflineAddressBook cmdlet. + +You can specify only one OAB for each address book policy. ```yaml Type: OfflineAddressBookIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md index b0e5d2457b..8c147fdbe2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md @@ -13,7 +13,7 @@ title: New-AddressList # New-AddressList ## 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 New-AddressList cmdlet to create address lists and apply them to recipients. @@ -74,7 +74,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter. -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/New-AdminAuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md index 6f6e1a5d91..18a80d3e96 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md @@ -16,7 +16,7 @@ title: New-AdminAuditLogSearch > [!NOTE] > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . -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 New-AdminAuditLogSearch cmdlet to search the contents of the administrator audit log and send the results to one or more mailboxes that you specify. @@ -41,7 +41,7 @@ New-AdminAuditLogSearch -EndDate -StartDate -StatusMai ## DESCRIPTION After the New-AdminAuditLogSearch cmdlet is run, the report is delivered to the mailboxes you specify within 15 minutes. The log is included as an XML attachment on the report email message. The maximum size of the log that can be generated is 10 megabytes (MB). -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/New-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md index 3275adc777..697abf3319 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md @@ -72,7 +72,7 @@ Phishing messages contain fraudulent links or spoofed domains in an effort to ge New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the AntiPhishPolicy parameter on the New-AntiPhishRule or Set-AntiPhishRule cmdlets to associate the policy with a rule. -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 @@ -135,7 +135,7 @@ This setting is part of spoof protection. The AuthenticationFailAction parameter specifies the action to take when the message fails composite authentication (a mixture of traditional SPF, DKIM, and DMARC email authentication checks and proprietary backend intelligence). Valid values are: -- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. - Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. ```yaml @@ -180,7 +180,7 @@ This setting is part of spoof protection. The DmarcQuarantineAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=quarantine`. Valid values are: - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. -- Quarantine: Deliver the message to quarantine. This is the default value. +- Quarantine: Deliver the message to quarantine. This value is the default. This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true. @@ -205,7 +205,7 @@ This setting is part of spoof protection. The DmarcRejectAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=reject`. Valid values are: - Quarantine: Deliver the message to quarantine. -- Reject: Reject the message. This is the default value. +- Reject: Reject the message. This value is the default. This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true. @@ -252,7 +252,7 @@ Accept wildcard characters: False The EnableFirstContactSafetyTips parameter specifies whether to enable or disable the safety tip that's shown when recipients first receive an email from a sender or do not often receive email from a sender. Valid values are: - $true: First contact safety tips are enabled. -- $false: First contact safety tips are disabled. This is the default value. +- $false: First contact safety tips are disabled. This value is the default. ```yaml Type: Boolean @@ -274,7 +274,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableMailboxIntelligence parameter specifies whether to enable or disable mailbox intelligence, which is artificial intelligence (AI) that determines user email patterns with their frequent contacts. Mailbox intelligence helps distinguish between messages from legitimate and impersonated senders based on a recipient's previous communication history. Valid values are: -- $true: Mailbox intelligence is enabled. This is the default value. +- $true: Mailbox intelligence is enabled. This value is the default. - $false: Mailbox intelligence is disabled. The values of the EnableMailboxIntelligenceProtection and MailboxIntelligenceProtectionAction parameters are ignored. ```yaml @@ -298,7 +298,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableMailboxIntelligenceProtection specifies whether to enable or disable taking action for impersonation detections from mailbox intelligence results. Valid values are: - $true: Take action for impersonation detections from mailbox intelligence results. Use the MailboxIntelligenceProtectionAction parameter to specify the action. -- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This is the default value. +- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This value is the default. This parameter is meaningful only if the EnableMailboxIntelligence parameter is set to the value $true. @@ -325,7 +325,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableOrganizationDomainsProtection parameter specifies whether to enable domain impersonation protection for all registered domains in the Microsoft 365 organization. Valid values are: - $true: Domain impersonation protection is enabled for all registered domains in the Microsoft 365 organization. -- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This is the default value. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters. +- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This value is the default. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters. ```yaml Type: Boolean @@ -348,7 +348,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for domain impersonation detections. Valid values are: - $true: Safety tips for similar domains are enabled. -- $false: Safety tips for similar domains are disabled. This is the default value. +- $false: Safety tips for similar domains are disabled. This value is the default. ```yaml Type: Boolean @@ -371,7 +371,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for user impersonation detections. Valid values are: - $true: Safety tips for similar users are enabled. -- $false: Safety tips for similar users are disabled. This is the default value. +- $false: Safety tips for similar users are disabled. This value is the default. ```yaml Type: Boolean @@ -417,7 +417,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableTargetedDomainsProtection parameter specifies whether to enable domain impersonation protection for a list of specified domains. Valid values are: - $true: Domain impersonation protection is enabled for the domains specified by the TargetedDomainsToProtect parameter. -- $false: The TargetedDomainsToProtect parameter isn't used. This is the default value. +- $false: The TargetedDomainsToProtect parameter isn't used. This value is the default. ```yaml Type: Boolean @@ -440,7 +440,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableTargetedUserProtection parameter specifies whether to enable user impersonation protection for a list of specified users. Valid values are: - $true: User impersonation protection is enabled for the users specified by the TargetedUsersToProtect parameter. -- $false: The TargetedUsersToProtect parameter isn't used. This is the default value. +- $false: The TargetedUsersToProtect parameter isn't used. This value is the default. ```yaml Type: Boolean @@ -462,7 +462,7 @@ This setting is part of spoof protection. The EnableUnauthenticatedSender parameter enables or disables unauthenticated sender identification in Outlook. Valid values are: -- $true: This is the default value. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication. +- $true: This value is the default. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication. - $false: A question mark is never applied to the sender's photo. To prevent these identifiers from being added to messages from specific senders, you have the following options: @@ -491,7 +491,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableUnusualCharactersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for unusual characters in domain and user impersonation detections. Valid values are: - $true: Safety tips for unusual characters are enabled. -- $false: Safety tips for unusual characters are disabled. This is the default value. +- $false: Safety tips for unusual characters are disabled. This value is the default. ```yaml Type: Boolean @@ -513,7 +513,7 @@ This setting is part of spoof protection. The EnableViaTag parameter enables or disables adding the via tag to the From address in Outlook (chris@contso.com via fabrikam.com). Valid values are: -- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This is the default value. +- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This value is the default. - $false: The via tag is not added to the From address. To prevent the via tag from being added to messages from specific senders, you have the following options: @@ -587,7 +587,7 @@ This setting is part of spoof protection. The HonorDmarcPolicy enables or disables using the sender's DMARC policy to determine what to do to messages that fail DMARC checks. Valid values are: -- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This is the default value. +- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This value is the default. - $false: If the message fails DMARC, ignore the action in the sender's DMARC policy. The AuthenticationFailAction parameter specifies the action to take on the message. ```yaml @@ -610,8 +610,8 @@ This setting is part of impersonation protection and is available only in Micros The ImpersonationProtectionState parameter specifies the configuration of impersonation protection. Valid values are: -- Automatic: This is the default value in the default policy named Office365 AntiPhish Policy. -- Manual: This is the default value in custom policies that you create. +- Automatic: This value is the default in the default policy named Office365 AntiPhish Policy. +- Manual: This value is the default in custom policies that you create. - Off ```yaml @@ -634,7 +634,7 @@ This setting is part of impersonation protection and is available only in Micros The MailboxIntelligenceProtectionAction parameter specifies what to do with messages that fail mailbox intelligence protection. Valid values are: -- NoAction: This is the default value. Note that this value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true. +- NoAction: This value is the default. This value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true. - BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. @@ -735,7 +735,7 @@ This setting is part of advanced settings and is available only in Microsoft Def The PhishThresholdLevel parameter specifies the tolerance level that's used by machine learning in the handling of phishing messages. Valid values are: -- 1: Standard: This is the default value. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied. +- 1: Standard: This value is the default. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied. - 2: Aggressive: Messages that are identified as phishing with a high degree of confidence are treated as if they were identified with a very high degree of confidence. - 3: More aggressive: Messages that are identified as phishing with a medium or high degree of confidence are treated as if they were identified with a very high degree of confidence. - 4: Most aggressive: Messages that are identified as phishing with a low, medium, or high degree of confidence are treated as if they were identified with a very high degree of confidence. @@ -864,7 +864,7 @@ This setting is part of impersonation protection and is available only in Micros The TargetedDomainProtectionAction parameter specifies the action to take on detected domain impersonation messages. You specify the protected domains in the TargetedDomainsToProtect parameter. Valid values are: -- NoAction: This is the default value. +- NoAction: This value is the default. - BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. @@ -965,7 +965,7 @@ This setting is part of impersonation protection and is available only in Micros The TargetedUserProtectionAction parameter specifies the action to take on detected user impersonation messages. You specify the protected users in the TargetedUsersToProtect parameter. Valid values are: -- NoAction: This is the default value. +- NoAction: This value is the default. - BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md index b779bdcd5c..c51ee1499b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md @@ -43,7 +43,7 @@ You need to add the antiphish rule to an existing policy by using the AntiPhishP > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Common policy settings](https://learn.microsoft.com/defender-office-365/anti-phishing-policies-about#common-policy-settings). -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 @@ -148,7 +148,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: -- $true: The rule is enabled. This is the default value. +- $true: The rule is enabled. This value is the default. - $false: The rule is disabled. In the properties of the rule, the value of this parameter is visible in the State property. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-App.md b/exchange/exchange-ps/ExchangePowerShell/New-App.md index 36786d92f6..89e31054bb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-App.md @@ -13,7 +13,7 @@ title: New-App # New-App ## 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 New-App cmdlet to install apps for Outlook. @@ -126,7 +126,7 @@ If the app is enabled for the entire organization, users can activate the new ap For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). -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 @@ -135,7 +135,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-App -FileData ([System.IO.File]::ReadAllBytes('C:\Apps\FinanceTestApp.xml')) ``` -This example installs the Finance Test app manifest file that has been copied to the local hard disk. +This example installs the Finance Test app manifest file that is copied to the local hard disk. ### Example 2 ```powershell @@ -272,7 +272,7 @@ Accept wildcard characters: False The DefaultStateForUser parameter specifies the default initial state of an organization app. Valid values are: - Enabled: The organization app is enabled by default. -- Disabled: The organization app is disabled by default. This is the default value. +- Disabled: The organization app is disabled by default. This value is the default. - AlwaysEnabled: The organization app is enabled and users can't disable it. You need to use the OrganizationApp switch when you use this parameter. @@ -335,7 +335,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the app is available to users in the organization. Valid values are: -- $true: The app is available to the specified users. This is the default value. +- $true: The app is available to the specified users. This value is the default. - $false: The app is hidden from all users in the organization. This setting overrides the ProvidedTo, UserList and DefaultStateForUser settings. This setting doesn't prevent users from installing their own instance of the app if they have install permissions. @@ -589,8 +589,8 @@ Accept wildcard characters: False The ProvidedTo parameter specifies the availability of the app in your organization. Valid values are: -- Everyone: This is the default value. This app is provided to every user in the organization. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions. -- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor will it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app. +- Everyone: This value is the default. This app is provided to every user in the organization. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions. +- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor does it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app. You use this parameter with the OrganizationApp switch. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md index 3e58c6fc38..ff23d6c486 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md @@ -197,7 +197,7 @@ Accept wildcard characters: False The Enabled parameter enables or disables the policy. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml @@ -379,9 +379,9 @@ Accept wildcard characters: False The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for the policy. Valid values are: - $true: Preservation Lock is enabled for the policy. No one -- including an administrator -- can turn off the policy or make it less restrictive. -- $false: Preservation Lock isn't enabled for the policy. This is the default value. +- $false: Preservation Lock isn't enabled for the policy. This value is the default. -After a policy has been locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. +After a policy is locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. Therefore, before you lock a policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md index 03b4a2058f..677746709d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md @@ -188,7 +188,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: +The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter doesn't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: - IPM.Note.Microsoft.Conversation - IPM.Note.Microsoft.Conversation.Voice @@ -199,7 +199,7 @@ The ExcludedItemClasses parameter specifies the types of messages to exclude fro - IPM.Note.Microsoft.Voicemail.UM - IPM.Note.Microsoft.Voicemail.UM.CA -Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. Note that the values you specify aren't validated, so the parameter accepts any text value. +Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. The values you specify aren't validated, so the parameter accepts any text value. You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`. @@ -307,7 +307,7 @@ The RetentionDurationDisplayHint parameter specifies the units that are used to - Months - Years -For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration. ```yaml Type: HoldDurationHint diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md index 7fb71820ea..0e3793c107 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md @@ -32,9 +32,9 @@ New-ApplicationAccessPolicy -AccessRight -AppId < ``` ## 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). -You can create a limited number of policies in your organization based on a fixed amount of space. If your organization runs out of space for these policies, you'll see the error: "The total size of App Access Policies exceeded the limit." To maximize the number of policies and reduce the amount of space that's consumed by the policies, set a one space character description for the policy. This method will allow approximately 300 policies (versus a previous limit of 100 policies). +You can create a limited number of policies in your organization based on a fixed amount of space. If your organization runs out of space for these policies, you get the error: "The total size of App Access Policies exceeded the limit." To maximize the number of policies and reduce the amount of space that's consumed by the policies, set a one space character description for the policy. This method allows approximately 300 policies (versus a previous limit of 100 policies). While scope-based resource access like Mail.Read or Calendar.Read is effective to ensure that the application can only read email or events within a mailbox and not do anything else, application access policies allow admins to enforce limits that are based on a list of mailboxes. For example, apps developed for one country/region shouldn't have access to data from other countries/regions. Or, or a CRM integration application should only access calendars in the Sales organization and no other departments. @@ -147,7 +147,7 @@ You can use any value that uniquely identifies the recipient. For example: To verify that a recipient is a security principal, run either of the following commands: `Get-Recipient -Identity | Select-Object IsValidSecurityPrincipal` or `Get-Recipient -ResultSize unlimited | Format-Table -Auto Name,RecipientType,RecipientTypeDetails,IsValidSecurityPrincipal`. -You can't use recipients that aren't security principals with this parameter. For example, the following types of recipients won't work: +You can specify only security principals with this parameter. For example, the following types of recipients don't work: - Discovery mailboxes (DiscoveryMailbox) - Dynamic distribution groups (DynamicDistributionGroup) diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md index ce878ff18c..4b5e2d74af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md @@ -32,7 +32,7 @@ New-AuthRedirect -AuthScheme -TargetUrl ## DESCRIPTION Exchange 2010 Client Access servers don't support OAuth authentication requests. Use this cmdlet to redirect OAuth authentication requests to Exchange servers that are running later versions of Exchange. This cmdlet is only useful if your organization has Exchange 2010 Client Access 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/New-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md index cbcdf925ab..7b361bd869 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md @@ -60,7 +60,7 @@ New-AuthServer [-Name] -Type ## DESCRIPTION Partner applications authorized by Exchange can access their resources after they're authenticated using server-to-server authentication. A partner application can authenticate by using self-issued tokens trusted by Exchange or by using an authorization server trusted by Exchange. -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 @@ -196,7 +196,11 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019 -{{ Fill DomainName Description }} +This parameter is available only in Exchange Server 2016 (CU18 or higher) and Exchange Server 2019 (CU7 or higher). + +The DomainName parameter links a cloud-based organization to the corresponding AuthServer object in the Multi-Tenant Exchange Hybrid. This parameter uses the syntax: "domain.onmicrosoft.com". + +For example, if the DomainName value is contoso.onmicrosoft.com, the AuthServer object is associated with the contoso cloud-based organization. ```yaml Type: MultiValuedProperty @@ -216,7 +220,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the authorization server is enabled. Valid values are: -- $true: Authorization tokens that are issued by the authorization server are accepted. This is the default value +- $true: Authorization tokens that are issued by the authorization server are accepted. This value is the default - $false: Authorization tokens that are issued by the authorization server are not accepted. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md index e623800578..a0774f7214 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md @@ -13,7 +13,7 @@ title: New-AuthenticationPolicy # New-AuthenticationPolicy ## 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 New-AuthenticationPolicy cmdlet to create authentication policies in your organization. @@ -57,7 +57,7 @@ New-AuthenticationPolicy [[-Name] ] ``` ## 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/New-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md index ed2a9f99e1..506ad13cb3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md @@ -67,7 +67,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned New-AutoSensitivityLabelPolicy -Name "GlobalPolicy" -Comment "Primary policy" -SharePointLocation "https://my.url","https://my.url2" -OneDriveLocation "https://my.url3","https://my.url4" -Mode TestWithoutNotifications -ApplySensitivityLabel "Test" ``` -This example creates an auto-labeling policy named GlobalPolicy for the specified SharePoint and OneDrive locations with the label "Test". The new policy has a descriptive comment and will be in simulation mode on creation. +This example creates an auto-labeling policy named GlobalPolicy for the specified SharePoint and OneDrive locations with the label "Test". The new policy has a descriptive comment and is created in simulation mode. ## PARAMETERS @@ -420,7 +420,7 @@ Accept wildcard characters: False The Mode parameter specifies the action and notification level of the auto-labeling policy. Valid values are: -- Enable: The policy is enabled for actions and notifications. This is the default value. +- Enable: The policy is enabled for actions and notifications. This value is the default. - Disable: The policy is disabled. - TestWithNotifications: No actions are taken, but notifications are sent. - TestWithoutNotifications: An audit mode where no actions are taken, and no notifications are sent. @@ -563,7 +563,7 @@ Accept wildcard characters: False The OverwriteLabel parameter specifies whether to overwrite a manual label. Valid values are: - $true: Overwrite the manual label. -- $false: Don't overwrite the manual label. This is the default value. +- $false: Don't overwrite the manual label. This value is the default. This parameter works only on Exchange locations. @@ -621,7 +621,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Priority parameter specifies the priority of the policy. The highest priority policy will take action over lower priority policies if two policies are applicable for a file. +The Priority parameter specifies the priority of the policy. The highest priority policy takes precedence over lower priority policies if two policies are applicable for a file. ```yaml Type: System.Int32 diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md index b329df41b6..e8a9aa3f46 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md @@ -335,7 +335,7 @@ Accept wildcard characters: False The Disabled parameter specifies whether the auto-labeling policy rule is enabled or disabled. Valid values are: - $true: The rule is disabled. -- $false: The rule is enabled. This is the default value. +- $false: The rule is enabled. This value is the default. ```yaml Type: Boolean @@ -447,7 +447,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this condition in auto-labeling policy rules that are scoped only to Exchange. @@ -690,7 +690,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this exception in auto-labeling policy rules that are scoped only to Exchange. @@ -1199,7 +1199,7 @@ Accept wildcard characters: False The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are: - None: You can't select this value if the rule has no actions configured. -- Low: This is the default value. +- Low: This value is the default. - Medium - High @@ -1224,7 +1224,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du - Ignore - RetryThenBlock -- Blank (the value $null): This is the default value. +- Blank (the value $null): This value is the default. ```yaml Type: PolicyRuleErrorAction diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md index 80f2a0f3bf..044ee90f33 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md @@ -49,7 +49,7 @@ If your organization has multiple email domains and each requires its own Autodi When you're creating an Autodiscover virtual directory, we recommend that you enable Secure Sockets Layer (SSL) for the Autodiscover service. -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 @@ -104,7 +104,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. ```yaml @@ -147,7 +147,7 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. -- $false: Digest authentication is disabled. This is the default value. +- $false: Digest authentication is disabled. This value is the default. ```yaml Type: Boolean @@ -189,7 +189,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -209,7 +209,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -230,8 +230,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -294,7 +294,7 @@ Accept wildcard characters: False The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are: -- $true: OAuth authentication is enabled. This is the default value. +- $true: OAuth authentication is enabled. This value is the default. - $false: OAuth authentication is disabled. ```yaml @@ -415,7 +415,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -- $true: Integrated Windows authentication is enabled. This is the default value. +- $true: Integrated Windows authentication is enabled. This value is the default. - $false: Integrated Windows authentication is disabled. ```yaml @@ -436,7 +436,7 @@ Accept wildcard characters: False The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are: -- $true: WS-Security authentication is enabled. This is the default value. +- $true: WS-Security authentication is enabled. This value is the default. - $false: WS-Security authentication is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md index 1617b9203b..d9d4f7cd86 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md @@ -31,7 +31,7 @@ New-AvailabilityConfig ``` ## 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/New-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md index f41f532d23..031e3b3e2f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md @@ -32,7 +32,7 @@ New-AvailabilityReportOutage [-SiteName] -Comment -DowntimeMin ``` ## 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/New-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md index a2a84309b5..c401cd7ed0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md @@ -18,7 +18,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the New-CaseHoldPolicy cmdlet to create new case hold policies in the Microsoft Purview compliance portal. > [!NOTE] -> After you use the New-CaseHoldPolicy cmdlet to create a case hold policy, you need to use the New-CaseHoldRule cmdlet to create a case hold rule and assign the rule to the policy. **If you don't create a rule for the policy, the hold won't be created, and content locations won't be placed on hold**. +> After you use the New-CaseHoldPolicy cmdlet to create a case hold policy, you need to use the New-CaseHoldRule cmdlet to create a case hold rule and assign the rule to the policy. **If you don't create a rule for the policy, the hold isn't created, and content locations aren't placed on hold**. > > Running this cmdlet causes a full synchronization across your organization, which is a significant operation. If you need to create multiple policies, wait until the policy distribution is successful before running the cmdlet again for the next policy. For information about the distribution status, see [Get-CaseHoldPolicy](https://learn.microsoft.com/powershell/module/exchangepowershell/get-caseholdpolicy). @@ -141,7 +141,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md index 917d74060d..40f1e04187 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md @@ -160,7 +160,7 @@ Accept wildcard characters: False The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are: - $true: The rule is disabled. -- $false: The rule is enabled. This is the default value. +- $false: The rule is enabled. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md index 9cfa7a8d54..3c89147d16 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md @@ -13,7 +13,7 @@ title: New-ClassificationRuleCollection # New-ClassificationRuleCollection ## 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 New-ClassificationRuleCollection cmdlet to import new classification rule collections into your organization. @@ -32,7 +32,7 @@ New-ClassificationRuleCollection [-FileData] ``` ## 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/New-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md index a81bd4b402..17f59324a8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md @@ -34,7 +34,7 @@ The New-ClientAccessArray cmdlet creates an object that represents a load balanc Client Access arrays allow Outlook clients in an Active Directory site to access the Client Access servers in the array by using RPC over TCP to a single, unified, fully qualified domain name (FQDN). The RpcClientAccessServer property of new mailbox databases is automatically populated with the FQDN of the Client Access array and this value is used during the creation of Outlook profiles for mailboxes in those databases. -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/New-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md index 38b6934b7f..ee0bc3376f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md @@ -16,7 +16,7 @@ title: New-ClientAccessRule > [!NOTE] > Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). -This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-ClientAccessRule cmdlet to create client access rules. Client access rules help you control access to your organization based on the properties of the connection. @@ -71,7 +71,7 @@ Protocols that don't support authentication type filters: - REST - UniversalOutlook -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 @@ -80,7 +80,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-ClientAccessRule -Name AllowRemotePS -Action Allow -AnyOfProtocols RemotePowerShell -Priority 1 ``` -This example creates a highest priority rule that allows access to remote PowerShell. This rule is an important safeguard to preserve access to your organization. Without this rule, if you create rules that block your access to remote PowerShell, or that block all protocols for everyone, you'll lose the ability to fix the rules yourself (you'll need to call Microsoft Customer Service and Support). +This example creates a highest priority rule that allows access to remote PowerShell. This rule is an important safeguard to preserve access to your organization. Without this rule, if you create rules that block your access to remote PowerShell, or that block all protocols for everyone, you lose the ability to fix the rules yourself (you need to call Microsoft Customer Service and Support). ### Example 2 ```powershell diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md index 28d59c54ab..a92b1a421c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md @@ -84,7 +84,7 @@ The CaseType parameter specifies the type of compliance case that you want to cr - ComplianceWorkspace: This value is reserved for internal Microsoft use. - DataInvestigation: Data investigation cases are used to investigate data spillage incidents. - DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations. -- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. This is the default value. +- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. This value is the default. - InsiderRisk: Insider risk cases are use to manage insider risk management cases. Typically, insider risk management cases are manually created in the Microsoft Purview compliance portal to further investigate activity based on a risk alert. - InternalInvestigation: This value is reserved for internal Microsoft use. - SupervisionPolicy: This type of case corresponds to communication compliance policy. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md index 175e4be26e..5c071cf02f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md @@ -196,7 +196,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The EventType parameter specifies the GUID value of the event that will start the retention period for labels that use this event type. Run the following command to see the available GUID values: `Get-ComplianceRetentionEventType | Format-Table Name,GUID`. +The EventType parameter specifies the GUID value of the event that starts the retention period for labels that use this event type. Run the following command to see the available GUID values: `Get-ComplianceRetentionEventType | Format-Table Name,GUID`. ```yaml Type: ComplianceRuleIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md index dde0f3b69a..d3311f357a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md @@ -13,7 +13,7 @@ title: New-ComplianceSearch # New-ComplianceSearch ## 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 New-ComplianceSearch cmdlet to create compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. You use this cmdlet to define the search criteria. @@ -50,7 +50,7 @@ A compliance search requires at least one location. For example, mailboxes using After you create a compliance search using the New-ComplianceSearch cmdlet, you run the search using the Start-ComplianceSearch 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). In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. @@ -108,7 +108,7 @@ Accept wildcard characters: False The AllowNotFoundExchangeLocationsEnabled parameter specifies whether to include mailboxes other than regular user mailboxes in the compliance search. Valid values are: - $true: The search doesn't try to validate the existence of the mailbox before proceeding. This value is required if you want to search mailboxes that don't resolve as regular mailboxes. -- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This is the default value. +- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This value is the default. The mailbox types that are affected by the value of this parameter include: @@ -287,9 +287,9 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The HoldNames parameter specifies that the content locations that have been placed on hold in the specified eDiscovery case will be searched. You use the value All for this parameter. You also need to specify the name of an eDiscovery case by using the Case parameter. +The HoldNames parameter specifies the content locations placed on hold in the specified eDiscovery case are searched. You use the value All for this parameter. You also need to specify the name of an eDiscovery case by using the Case parameter. -Also, if a content location was placed on a query-based case hold, only items that are on hold will be searched when you run this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search. +Also, if a content location was placed on a query-based case hold, only items that are on hold are searched when you run this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search. ```yaml Type: String[] @@ -329,8 +329,8 @@ This parameter is available only in the cloud-based service. The IncludeUserAppContent parameter specifies that you want to search the cloud-based storage location for users who don't have a regular Microsoft 365 user account in your organization. These types of users include users without an Exchange Online license who use Office applications, Microsoft 365 guest users, and on-premises users whose identity is synchronized with your Microsoft 365 organization. Valid values are: -- $true: The cloud-based storage location for the users specified in the ExchangeLocation parameter will be included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user will be included in the search. -- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter won't be included in the search. This is the default value. +- $true: The cloud-based storage location for the users specified in the ExchangeLocation parameter are included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user are included in the search. +- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter isn't included in the search. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md index 0ed529ffc5..bb12c6f155 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md @@ -13,7 +13,7 @@ title: New-ComplianceSearchAction # New-ComplianceSearchAction ## 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 New-ComplianceSearchAction cmdlet to create actions for content searches in Exchange Server and in the Microsoft Purview compliance portal. @@ -99,7 +99,7 @@ After you create a content search using the New-ComplianceSearch cmdlet and run In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. -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). In Microsoft 365, the account that you use to run this cmdlet must have a valid Microsoft 365 license assigned. @@ -128,7 +128,7 @@ This example creates an export search action for the content search named Projec New-ComplianceSearchAction -SearchName "Remove Phishing Message" -Purge -PurgeType SoftDelete ``` -This example deletes the search results returned by a content search named Remove Phishing Message. Note that unindexed items aren't deleted when you use the Purge parameter. +This example deletes the search results returned by a content search named Remove Phishing Message. Unindexed items aren't deleted when you use the Purge parameter. ### Example 4 ```powershell @@ -185,7 +185,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. To specify the format for Exchange search results, use the ExchangeArchiveFormat parameter. To specify the format for SharePoint and OneDrive search results, use the SharePointArchiveFormat parameter. @@ -259,7 +259,7 @@ The ExchangeArchiveFormat parameter specifies how to export Exchange search resu - PerUserPst: One PST file for each mailbox. - SinglePst: One PST file that contains all exported messages. - SingleFolderPst: One PST file with a single root folder for the entire export. -- IndividualMessage: Export each message as an .msg message file. This is the default value. +- IndividualMessage: Export each message as an .msg message file. This value is the default. - PerUserZip: One ZIP file for each mailbox. Each ZIP file contains the exported .msg message files from the mailbox. - SingleZip: One ZIP file for all mailboxes. The ZIP file contains all exported .msg message files from all mailboxes. This output setting is available only in PowerShell. @@ -396,7 +396,7 @@ This parameter is available only in the cloud-based service. The IncludeSharePointDocumentVersions parameter specifies whether to export previous versions of the document when you use the Export switch. Valid values are: - $true: Export all versions of the document. -- $false: Export only the current published version of the topic. This is the default value. +- $false: Export only the current published version of the topic. This value is the default. ```yaml Type: Boolean @@ -508,7 +508,7 @@ The Purge switch specifies the action for the content search is to remove items **Tip**: To purge more than 10 items, refer to [ediscoverySearch: purgeData](https://learn.microsoft.com/graph/api/security-ediscoverysearch-purgedata) in the Microsoft Graph API, which allows purging a maximum of 100 items per location. -- You can remove items from a maximum of 50,000 mailboxes using a single content search. To remove items from more than 50,000 mailboxes, you'll have to create separate content searches. For more information, see [Search for and delete email messages in your Microsoft 365 organization](https://learn.microsoft.com/purview/ediscovery-search-for-and-delete-email-messages). +- You can remove items from a maximum of 50,000 mailboxes using a single content search. To remove items from more than 50,000 mailboxes, you need to create separate content searches. For more information, see [Search for and delete email messages in your Microsoft 365 organization](https://learn.microsoft.com/purview/ediscovery-search-for-and-delete-email-messages). - Unindexed items aren't removed from mailboxes when you use this switch. - The value of the PurgeType parameter controls how the items are removed. @@ -533,7 +533,7 @@ Accept wildcard characters: False The PurgeType parameter specifies how to remove items when the action is Purge. Valid values are: - SoftDelete: Purged items are recoverable by users until the deleted item retention period expires. -- HardDelete (cloud only): Purged items are marked for permanent removal from the mailbox and will be permanently removed the next time the mailbox is processed by the Managed Folder Assistant. If single item recovery is enabled on the mailbox, purged items will be permanently removed after the deleted item retention period expires. +- HardDelete (cloud only): Purged items are marked for permanent removal from the mailbox and are permanently removed the next time the mailbox is processed by the Managed Folder Assistant. If single item recovery is enabled on the mailbox, purged items are permanently removed after the deleted item retention period expires. ```yaml Type: ComplianceDestroyType @@ -728,7 +728,7 @@ This parameter requires the Export role. By default, this role is assigned only The SharePointArchiveFormat parameter specifies how to export SharePoint and OneDrive search results. Valid values are: -- IndividualMessage: Export the files uncompressed. This is the default value. +- IndividualMessage: Export the files uncompressed. This value is the default. - PerUserZip: One ZIP file for each user. Each ZIP file contains the exported files for the user. - SingleZip: One ZIP file for all users. The ZIP file contains all exported files from all users. This output setting is available only in PowerShell. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md index e58199a8c7..a1340d5858 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md @@ -373,7 +373,7 @@ Accept wildcard characters: False The IsRecordLabel parameter specifies whether the label is a record label. Valid values are: - $true: The label is a record label. Once the label is applied to content, the label can't be removed. -- $false: The label isn't a record label. This is the default value. +- $false: The label isn't a record label. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md index ef07895c85..4fd215d87d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md @@ -15,7 +15,7 @@ title: New-DataClassification ## SYNOPSIS This cmdlet is functional only in on-premises Exchange. -In Exchange Online, this cmdlet has been replaced by the [New-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. +In Exchange Online, this cmdlet is replaced by the [New-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. Use the New-DataClassification cmdlet to create data classification rules that use document fingerprints. @@ -36,7 +36,7 @@ New-DataClassification [-Name] -Description -Fingerprints [-DatabaseAvailabilityGrou ``` ## 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/New-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md index 8727a41a18..3320d9ce11 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md @@ -39,7 +39,7 @@ New-DeliveryAgentConnector [-Name] -AddressSpaces ## DESCRIPTION Delivery agent connectors are used to route messages addressed to foreign systems that don't utilize the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in the Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-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/New-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md index c39103379a..e43f3ef571 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md @@ -117,7 +117,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md index 1b89079368..a2aff5f1c4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md @@ -152,7 +152,7 @@ Accept wildcard characters: False The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -173,7 +173,7 @@ Accept wildcard characters: False The AccountUserName parameter specifies the account user name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -195,7 +195,7 @@ The AllowAppStore parameter specifies whether to allow access to the app store o - $true: Access to the app store is allowed. - $false: Access to the app store isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -222,7 +222,7 @@ The AllowAssistantWhileLocked parameter specifies whether to allow the use of th - $true: The voice assistant can be used while devices are locked. - $false: The voice assistant can't be used while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -246,7 +246,7 @@ The AllowConvenienceLogon parameter specifies whether to allow convenience logon - $true: Convenience logons are allowed. - $false: Convenience logons aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -270,7 +270,7 @@ The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic su - $true: Diagnostic submissions are allowed. - $false: Diagnostic submissions aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -298,7 +298,7 @@ The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup f - $true: iCloud Backup is allowed. - $false: iCloud Backup isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -325,7 +325,7 @@ The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documen - $true: iCloud Documents & Data sync is allowed. - $false: iCloud Documents & Data sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -352,7 +352,7 @@ The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photo - $true: iCloud Photos sync is allowed. - $false: iCloud Photo sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -379,7 +379,7 @@ The AllowJailbroken parameter specifies whether to allow access to your organiza - $true: Jailbroken devices are allowed. - $false: Jailbroken devices aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -406,7 +406,7 @@ The AllowPassbookWhileLocked parameter specifies whether to allow the use of App - $true: Passbook is available while devices are locked. - $false: Passbook isn't available while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -430,7 +430,7 @@ The AllowScreenshot parameter specifies whether to allow screenshots on devices. - $true: Screenshots are allowed. - $false: Screenshots aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -457,7 +457,7 @@ The AllowSimplePassword parameter specifies whether to allow simple or non-compl - $true: Simple passwords are allowed. - $false: Simple passwords aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -485,7 +485,7 @@ The AllowVideoConferencing parameter specifies whether to allow video conferenci - $true: Video conferencing is allowed. - $false: Video conferencing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -509,7 +509,7 @@ The AllowVoiceAssistant parameter specifies whether to allow using the voice ass - $true: The voice assistant is allowed. - $false: The voice assistant isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -533,7 +533,7 @@ The AllowVoiceDialing parameter specifies whether to allow voice-activated telep - $true: Voice dialing is allowed. - $false: Voice dialing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -556,7 +556,7 @@ Accept wildcard characters: False The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -579,7 +579,7 @@ Accept wildcard characters: False The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -606,7 +606,7 @@ The AppsRating parameter species the maximum or most restrictive rating of apps - Rating9plus - Rating12plus - Rating17plus -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -633,7 +633,7 @@ The AutoUpdateStatus parameter specifies the update settings for devices. Valid - AutomaticUpdatesRequired - DeviceDefault - NeverCheckUpdates -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -657,7 +657,7 @@ The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth - $true: Bluetooth is enabled. - $false: Bluetooth is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -681,7 +681,7 @@ The CameraEnabled parameter specifies whether to enable or disable cameras on de - $true: Cameras are enabled. - $false: Cameras are disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -747,7 +747,7 @@ Accept wildcard characters: False The EmailAddress parameter specifies the email address. Valid values are: - An email address: For example, julia@contoso.com. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -769,7 +769,7 @@ The EnableRemovableStorage parameter specifies whether removable storage can be - $true: Removable storage can be used. - $false: Removable storage can't be used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -792,7 +792,7 @@ Accept wildcard characters: False The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -813,7 +813,7 @@ Accept wildcard characters: False The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are: - Required -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -837,7 +837,7 @@ The ForceAppStorePassword parameter specifies whether to require a password to u - $true: App store passwords are required. - $false: App store passwords aren't required. -- $null (blank): The feature isn't allowed or blocked by the rule. This is the default value. +- $null (blank): The feature isn't allowed or blocked by the rule. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -861,7 +861,7 @@ The ForceEncryptedBackup parameter specifies whether to force encrypted backups - $true: Encrypted backups are required. - $false: Encrypted backups aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -887,7 +887,7 @@ Accept wildcard characters: False The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -940,7 +940,7 @@ Valid values for the MoviesRating parameter are: - AllowAll: All movies are allowed, regardless of their rating. - DontAllow: No movies are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1039,7 +1039,7 @@ Accept wildcard characters: False The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int64 @@ -1060,7 +1060,7 @@ Accept wildcard characters: False The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1088,7 +1088,7 @@ Accept wildcard characters: False The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1116,7 +1116,7 @@ Accept wildcard characters: False The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int32 @@ -1137,7 +1137,7 @@ Accept wildcard characters: False The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1167,7 +1167,7 @@ The PasswordQuality parameter specifies the minimum password quality rating that Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Android 4+ devices. @@ -1191,7 +1191,7 @@ The PasswordRequired parameter specifies whether a password is required to acces - $true: Device passwords are required. - $false: Device passwords aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1246,7 +1246,7 @@ The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on de - $true: Memory is encrypted. - $false: Memory isn't encrypted. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1273,7 +1273,7 @@ The RegionRatings parameter specifies the rating system (country/region) to use Valid values for the RegionRating parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - au: Australia - ca: Canada - de: Germany @@ -1306,7 +1306,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required - $true: An email profile is required. This value is required for selective wipe on iOS devices. - $false: An email profile isn't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Boolean @@ -1328,7 +1328,7 @@ The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen - $true: SmartScreen is enabled. - $false: SmartScreen is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -1352,7 +1352,7 @@ The SystemSecurityTLS parameter specifies whether TLS encryption is used on devi - $true: TLS encryption is used. - $false: TLS encryption isn't used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -1378,7 +1378,7 @@ Valid values for the TVShowsRating parameter are: - AllowAll: All television shows are allowed, regardless of their rating. - DontAllow: No televisions shows are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1465,7 +1465,7 @@ Accept wildcard characters: False The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - AlwaysNotify - NeverNotify - NotifyAppChanges @@ -1511,7 +1511,7 @@ The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid valu - $true: Wi-Fi is enabled. - $false: Wi-Fi is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Microsoft Windows Phone 8.1 devices. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md index f3e3e885f1..09a319872c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md @@ -117,7 +117,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md index 47cb277d91..73b027f3ff 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md @@ -151,7 +151,7 @@ Accept wildcard characters: False The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -172,7 +172,7 @@ Accept wildcard characters: False The AccountUserName parameter specifies the account user name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -194,7 +194,7 @@ The AllowAppStore parameter specifies whether to allow access to the app store o - $true: Access to the app store is allowed. - $false: Access to the app store isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -221,7 +221,7 @@ The AllowAssistantWhileLocked parameter specifies whether to allow the use of th - $true: The voice assistant can be used while devices are locked. - $false: The voice assistant can't be used while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -245,7 +245,7 @@ The AllowConvenienceLogon parameter specifies whether to allow convenience logon - $true: Convenience logons are allowed. - $false: Convenience logons aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -269,7 +269,7 @@ The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic su - $true: Diagnostic submissions are allowed. - $false: Diagnostic submissions aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -297,7 +297,7 @@ The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup f - $true: iCloud Backup is allowed. - $false: iCloud Backup isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -324,7 +324,7 @@ The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documen - $true: iCloud Documents & Data sync is allowed. - $false: iCloud Documents & Data sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -351,7 +351,7 @@ The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photo - $true: iCloud Photos sync is allowed. - $false: iCloud Photo sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -378,7 +378,7 @@ The AllowPassbookWhileLocked parameter specifies whether to allow the use of App - $true: Passbook is available while devices are locked. - $false: Passbook isn't available while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -402,7 +402,7 @@ The AllowScreenshot parameter specifies whether to allow screenshots on devices. - $true: Screenshots are allowed. - $false: Screenshots aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -429,7 +429,7 @@ The AllowSimplePassword parameter specifies whether to allow simple or non-compl - $true: Simple passwords are allowed. - $false: Simple passwords aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -457,7 +457,7 @@ The AllowVideoConferencing parameter specifies whether to allow video conferenci - $true: Video conferencing is allowed. - $false: Video conferencing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -481,7 +481,7 @@ The AllowVoiceAssistant parameter specifies whether to allow using the voice ass - $true: The voice assistant is allowed. - $false: The voice assistant isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -505,7 +505,7 @@ The AllowVoiceDialing parameter specifies whether to allow voice-activated telep - $true: Voice dialing is allowed. - $false: Voice dialing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -528,7 +528,7 @@ Accept wildcard characters: False The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -551,7 +551,7 @@ Accept wildcard characters: False The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -578,7 +578,7 @@ The AppsRating parameter species the maximum or most restrictive rating of apps - Rating9plus - Rating12plus - Rating17plus -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -605,7 +605,7 @@ The AutoUpdateStatus parameter specifies the update settings for devices. Valid - AutomaticUpdatesRequired - DeviceDefault - NeverCheckUpdates -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -629,7 +629,7 @@ The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth - $true: Bluetooth is enabled. - $false: Bluetooth is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -653,7 +653,7 @@ The CameraEnabled parameter specifies whether to enable or disable cameras on de - $true: Cameras are enabled. - $false: Cameras are disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -719,7 +719,7 @@ Accept wildcard characters: False The EmailAddress parameter specifies the email address. Valid values are: - An email address: For example, julia@contoso.com. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -741,7 +741,7 @@ The EnableRemovableStorage parameter specifies whether removable storage can be - $true: Removable storage can be used. - $false: Removable storage can't be used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -764,7 +764,7 @@ Accept wildcard characters: False The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -785,7 +785,7 @@ Accept wildcard characters: False The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are: - Required -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -809,7 +809,7 @@ The ForceAppStorePassword parameter specifies whether to require a password to u - $true: App store passwords are required. - $false: App store passwords aren't required. -- $null (blank): The feature isn't allowed or blocked by the rule. This is the default value. +- $null (blank): The feature isn't allowed or blocked by the rule. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -833,7 +833,7 @@ The ForceEncryptedBackup parameter specifies whether to force encrypted backups - $true: Encrypted backups are required. - $false: Encrypted backups aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -859,7 +859,7 @@ Accept wildcard characters: False The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -912,7 +912,7 @@ Valid values for the MoviesRating parameter are: - AllowAll: All movies are allowed, regardless of their rating. - DontAllow: No movies are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1011,7 +1011,7 @@ Accept wildcard characters: False The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int64 @@ -1032,7 +1032,7 @@ Accept wildcard characters: False The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1060,7 +1060,7 @@ Accept wildcard characters: False The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1088,7 +1088,7 @@ Accept wildcard characters: False The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int32 @@ -1109,7 +1109,7 @@ Accept wildcard characters: False The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1139,7 +1139,7 @@ The PasswordQuality parameter specifies the minimum password quality rating that Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Android 4+ devices. @@ -1163,7 +1163,7 @@ The PasswordRequired parameter specifies whether a password is required to acces - $true: Device passwords are required. - $false: Device passwords aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1218,7 +1218,7 @@ The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on de - $true: Memory is encrypted. - $false: Memory isn't encrypted. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1245,7 +1245,7 @@ The RegionRatings parameter specifies the rating system (country/region) to use Valid values for the RegionRating parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - au: Australia - ca: Canada - de: Germany @@ -1278,7 +1278,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required - $true: An email profile is required. This value is required for selective wipe on iOS devices. - $false: An email profile isn't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Boolean @@ -1300,7 +1300,7 @@ The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen - $true: SmartScreen is enabled. - $false: SmartScreen is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -1324,7 +1324,7 @@ The SystemSecurityTLS parameter specifies whether TLS encryption is used on devi - $true: TLS encryption is used. - $false: TLS encryption isn't used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -1350,7 +1350,7 @@ Valid values for the TVShowsRating parameter are: - AllowAll: All television shows are allowed, regardless of their rating. - DontAllow: No televisions shows are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1437,7 +1437,7 @@ Accept wildcard characters: False The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - AlwaysNotify - NeverNotify - NotifyAppChanges @@ -1483,7 +1483,7 @@ The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid valu - $true: Wi-Fi is enabled. - $false: Wi-Fi is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Microsoft Windows Phone 8.1 devices. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md index dbfdd374b4..e41f6654c8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md @@ -98,7 +98,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md index ac577a237c..a8e5f0ae79 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md @@ -13,7 +13,7 @@ title: New-DistributionGroup # New-DistributionGroup ## 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 New-DistributionGroup cmdlet to create distribution groups and mail-enabled security groups. @@ -60,7 +60,7 @@ You can use the New-DistributionGroup cmdlet to create the following types of gr Distribution groups are used to consolidate groups of recipients into a single point of contact for email messages. Distribution groups aren't security principals, and therefore can't be assigned permissions. However, you can assign permissions to mail-enabled security groups. -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). In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. @@ -180,7 +180,7 @@ This parameter is available only in the cloud-based service. The BccBlocked parameter specifies whether members of the group don't receive messages if the group is used in the Bcc line. Valid values are: - $true: If the group is used in the Bcc line, members of the group don't receive the message, and the sender receives a non-delivery report (also known as an NDR or bounce message). Other recipients of the message aren't blocked. If an external sender uses the group in the Bcc line, members of the group aren't blocked. For nested groups, the message is blocked only for members of the top-level group. -- $false: There are no restrictions for using the group in the Bcc line of messages. This is the default value. +- $false: There are no restrictions for using the group in the Bcc line of messages. This value is the default. ```yaml Type: Boolean @@ -201,7 +201,7 @@ Accept wildcard characters: False The ByPassNestedModerationEnabled parameter specifies how to handle message approval when a moderated group contains other moderated groups as members. Valid values are: - $true: After a moderator approves a message sent to the group, the message is automatically approved for all other moderated groups that are members of the group. -- $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This is the default value. +- $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This value is the default. This parameter can be used only by top-level organization and tenant administrators. @@ -418,8 +418,8 @@ Accept wildcard characters: False The MemberDepartRestriction parameter specifies the restrictions that you put on requests to leave the group. Valid values are: -- Open: Members can leave the group without approval from one of the group owners. This is the default value for universal distribution groups. You can't use this value on universal security groups. -- Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This is the default value for universal security groups. +- Open: Members can leave the group without approval from one of the group owners. This value is the default for universal distribution groups. You can't use this value on universal security groups. +- Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This value is the default for universal security groups. ```yaml Type: MemberUpdateType @@ -440,7 +440,7 @@ Accept wildcard characters: False The MemberJoinRestriction parameter specifies the restrictions that you put on requests to join the group. Valid values are: - Open: Users can add themselves to the group without approval from a group owner. You can't use this value on universal security groups. -- Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This is the default value on universal security groups and universal distribution groups. +- Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This value is the default on universal security groups and universal distribution groups. - ApprovalRequired: Users can request to join the group. The user is added to the group after the request is approved by one of the group owners. Although you can use this value on universal security groups, user requests to join the group aren't sent to the group owners, so this setting is only effective on universal distribution groups. ```yaml @@ -472,7 +472,7 @@ You can enter multiple values separated by commas. If the values contain spaces After you create the group, you use the Get-DistributionGroupMember cmdlet to view the group members, and the Add-DistributionGroupMember, Remove-DistributionGroupMember, and Update-DistributionGroupMember cmdlets to manage group membership. -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. @@ -526,7 +526,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -652,7 +652,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). ```yaml Type: String @@ -672,7 +672,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -696,7 +696,7 @@ Accept wildcard characters: False The Type parameter specifies the type of group that you want to create. Valid values are: -- Distribution: A distribution group. These groups can't have permissions assigned. This is the default value. +- Distribution: A distribution group. These groups can't have permissions assigned. This value is the default. - Security: A mail-enabled security group. These groups can have permissions assigned. The group's scope is always Universal. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md index 0dfaee8eb1..66fa40daa5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md @@ -35,7 +35,7 @@ New-DkimSigningConfig [-DomainName] [-Enabled] Applicable: Security & Compliance -The Policy parameter specifies the existing DLP policy that will contain the new DLP rule. You can use any value that uniquely identifies the policy. For example: +The Policy parameter specifies the existing DLP policy that contains the new DLP rule. You can use any value that uniquely identifies the policy. For example: - Name - Distinguished name (DN) @@ -587,7 +587,7 @@ Accept wildcard characters: False The BlockAccess parameter specifies an action for the DLP rule that blocks access to the source item when the conditions of the rule are met. Valid values are: - $true: Blocks further access to the source item that matched the rule. The owner, author, and site owner can still access the item. -- $false: Allows access to the source item that matched the rule. This is the default value. +- $false: Allows access to the source item that matched the rule. This value is the default. ```yaml Type: Boolean @@ -815,7 +815,7 @@ Accept wildcard characters: False The Disabled parameter specifies whether the DLP rule is disabled. Valid values are: - $true: The rule is disabled. -- $false: The rule is enabled. This is the default value. +- $false: The rule is enabled. This value is the default. ```yaml Type: Boolean @@ -1013,7 +1013,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this condition in DLP policies that are scoped only to Exchange. @@ -1553,7 +1553,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this exception in DLP policies that are scoped only to Exchange. @@ -1759,7 +1759,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this exception in DLP policies that are scoped only to Exchange. @@ -2602,7 +2602,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this condition in DLP policies that are scoped only to Exchange. @@ -2961,7 +2961,7 @@ Accept wildcard characters: False The NotifyPolicyTipDialogOption parameter specifies a display option for the policy tip. Valid values are: -- Tip: Displays policy tip at the top of the mail. This is the default value. +- Tip: Displays policy tip at the top of the mail. This value is the default. - Dialog: Displays policy tip at the top of the mail and as a popup dialog. (exchange only) ```yaml @@ -3366,7 +3366,7 @@ Accept wildcard characters: False The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are: - None: You can't select this value if the rule has no actions configured. -- Low: This is the default value. +- Low: This value is the default. - Medium - High @@ -3426,7 +3426,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du - Ignore - RetryThenBlock -- Blank (the value $null): This is the default value. +- Blank (the value $null): This value is the default. ```yaml Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyRuleErrorAction @@ -3550,11 +3550,11 @@ Accept wildcard characters: False The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are: -- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This is the default value. +- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default. - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). - HeaderOrEnvelope: Examine senders in the message header and the message envelope. -Note that message envelope searching is available only for the following conditions and exceptions: +Message envelope searching is available only for the following conditions and exceptions: - From and ExceptIfFrom - FromAddressContainsWords and ExceptIfFromAddressContainsWords diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md index 143373bf26..b788cd9e15 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md @@ -33,7 +33,7 @@ New-DlpKeywordDictionary -Name ``` ## DESCRIPTION -After you create a custom sensitive information type that specifies the identity (GUID value) of the DLP keyword dictionary, the dictionary will appear in your list of sensitive information types, and you can use it in policies. +After you create a custom sensitive information type that specifies the identity (GUID value) of the DLP keyword dictionary, the dictionary appears in your list of sensitive information types, and you can use it in policies. To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md index 6f345ee2f5..e366f86920 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md @@ -13,7 +13,7 @@ title: New-DlpPolicy # New-DlpPolicy ## SYNOPSIS -**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the New-DlpCompliancePolicy and New-DlpComplianceRule cmdlets instead. +**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the New-DlpCompliancePolicy and New-DlpComplianceRule cmdlets instead. This cmdlet is functional only in on-premises Exchange. @@ -38,7 +38,7 @@ New-DlpPolicy [[-Name] ] ``` ## 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 @@ -157,7 +157,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The Parameters parameter specifies the parameter values that are required by the DLP policy template that you specify using the Template or TemplateData parameters. DLP policy templates may contain parameters that need to be populated with values from your organization. For example, a DLP policy template may include an exception group that defines users who are exempt from the DLP policy. +The Parameters parameter specifies the parameter values that are required by the DLP policy template that you specify using the Template or TemplateData parameters. DLP policy templates might contain parameters that need to be populated with values from your organization. For example, a DLP policy template might include an exception group that defines users who are exempt from the DLP policy. This parameter uses the syntax: `@{Parameter1="Value1";Parameter2="Value2"...}`. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md index fa1137e12b..97a2f8867f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md @@ -13,7 +13,7 @@ title: New-DynamicDistributionGroup # New-DynamicDistributionGroup ## 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 New-DynamicDistributionGroup cmdlet to create dynamic distribution groups. A dynamic distribution group queries mail-enabled objects and builds the group membership based on the results. The group membership is recalculated whenever an email message is sent to the group. @@ -86,7 +86,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPATH filter. -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 @@ -766,7 +766,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -844,7 +844,7 @@ The RecipientContainer parameter specifies a filter that's based on the recipien If you don't use this parameter, the default value is the OU where the object was created. -Note that the RecipientContainer property can't be blank. The group is always limited to looking for recipients in a specific location (the value you specify for this parameter, or the location where the group was created). +The RecipientContainer property can't be blank. The group is always limited to looking for recipients in a specific location (the value you specify for this parameter, or the location where the group was created). **Note**: Although this parameter is available in Exchange Online, there's only one usable OU in an Exchange Online organization, so using this parameter has no effect. @@ -866,7 +866,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md index 93ddfc0f15..02b42f2322 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md @@ -44,7 +44,7 @@ For more information about preset security policies in PowerShell, see [Preset s > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). -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 @@ -83,7 +83,7 @@ Accept wildcard characters: False The AntiPhishPolicy parameter specifies the existing anti-phishing policy that's associated with the preset security policy. -If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-phishing policy will be one of the following values: +If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-phishing policy is one of the following values: - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650005393`. - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034844713`. @@ -108,7 +108,7 @@ Accept wildcard characters: False The HostedContentFilterPolicy parameter specifies the existing anti-spam policy that's associated with the preset security policy. -If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-spam policy will be one of the following values: +If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-spam policy is one of the following values: - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650006407`. - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034847393`. @@ -133,7 +133,7 @@ Accept wildcard characters: False The HostedContentFilterPolicy parameter specifies the existing anti-malware policy that's associated with the preset security policy. -If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-malware policy will be one of the following values: +If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-malware policy is one of the following values: - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650007658`. - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034871908`. @@ -197,7 +197,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: -- $true: The rule is enabled. The State value of the rule is Enabled. This is the default value. +- $true: The rule is enabled. The State value of the rule is Enabled. This value is the default. - $false: The rule is disabled. The State value of the rule is Disabled. After you create the rule, you turn on or turn off the preset security policy using one of the following commands: diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md index 99729e8485..d7db96a683 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md @@ -41,7 +41,7 @@ New-EcpVirtualDirectory [-AppPoolId ] ``` ## 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 @@ -121,7 +121,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -141,7 +141,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -162,8 +162,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md index 9df879d76c..0f3c1a24b3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md @@ -36,9 +36,9 @@ New-EdgeSubscription [-AccountExpiryDuration ] ``` ## DESCRIPTION -The Edge Transport server doesn't have access to Active Directory. All configuration and recipient information is stored in the Active Directory Lightweight Directory Services (AD LDS) instance. The New-EdgeSubscription cmdlet creates the Edge Subscription file that will be imported on a Mailbox server in the Active Directory site to which you want to subscribe this Edge Transport server. +The Edge Transport server doesn't have access to Active Directory. All configuration and recipient information is stored in the Active Directory Lightweight Directory Services (AD LDS) instance. The New-EdgeSubscription cmdlet creates the Edge Subscription file to import on a Mailbox server in the Active Directory site where you want to subscribe this Edge Transport server. -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 @@ -73,7 +73,7 @@ This example also imports the Edge Subscription file generated in Example 1 to t > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The AccountExpiryDuration parameter specifies how soon the EdgeSync bootstrap replication account (ESBRA) created by this command will expire. +The AccountExpiryDuration parameter specifies how soon the EdgeSync bootstrap replication account (ESBRA) created by this command expires. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md index a8168f3519..c64ac8e72c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md @@ -43,7 +43,7 @@ New-EdgeSyncServiceConfig [-ConfigurationSyncInterval ] ``` ## 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 @@ -224,7 +224,7 @@ Accept wildcard characters: False The LogLevel parameter specifies the EdgeSync logging level. Valid values are: -- None (This is the default value) +- None (default value) - Low - Medium - High @@ -275,7 +275,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the LogMaxFileSize parameter must be less than or equal to the value of the LogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the EdgeSyncLLog directory. @@ -305,7 +305,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the LogMaxFileSize parameter must be less than or equal to the value of the LogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the EdgeSyncLog files. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md index 6b5b760e67..aaa242cc86 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md @@ -13,7 +13,7 @@ title: New-EmailAddressPolicy # New-EmailAddressPolicy ## 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 New-EmailAddressPolicy cmdlet to create email address policies. In Exchange Online, email address policies are available only for Microsoft 365 Groups. @@ -141,7 +141,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter. -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 @@ -793,7 +793,7 @@ The DisabledEmailAddressTemplates parameter specifies the proxy email addresses Valid syntax for this parameter is `Type:AddressFormat`: -- Type: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. Note that you can't use SMTP to specify a disabled primary SMTP email address. +- Type: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. You can't use SMTP to specify a disabled primary SMTP email address. - AddressFormat: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example: alias@contoso.com requires the value `%m@contoso.com`, and firstname.lastname@contoso.com requires the value `%g.%s@contoso.com`. You can specify multiple disabled email address templates separated by commas: `"[Type1:]EmailAddress1","[Type2:]EmailAddress2",..."[TypeN:]EmailAddressN"`. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md index 365938a134..9c2195d866 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md @@ -72,7 +72,7 @@ There are many factors to consider when you configure certificates for Transport Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). To find out why you should disable the SSL protocol and switch to TLS, check out [Protecting you against the SSL 3.0 vulnerability](https://azure.microsoft.com/blog/protecting-against-the-ssl-3-0-vulnerability/). -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 @@ -431,7 +431,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: X509Certificate2 @@ -452,7 +452,7 @@ Accept wildcard characters: False The KeySize parameter specifies the size (in bits) of the RSA public key that's associated with the new certificate request or self-signed certificate. Valid values are: - 1024 -- 2048 (This is the default value) +- 2048 (default value) - 4096 ```yaml @@ -474,7 +474,7 @@ Accept wildcard characters: False The PrivateKeyExportable parameter specifies whether the certificate has an exportable private key, and controls whether you can export the certificate from the server (and import the certificate on other servers). Valid values are: - $true: The private key is exportable, so you can export the certificate from the server. -- $false: The private key isn't exportable, so you can't export the certificate. This is the default value. +- $false: The private key isn't exportable, so you can't export the certificate. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md index a39cde59db..230a474641 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md @@ -31,7 +31,7 @@ New-ExchangeSettings [-Name] ``` ## 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/New-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md index 1c3e6a1a8f..89aac16ff6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md @@ -34,7 +34,7 @@ New-ExoPhishSimOverrideRule -Policy -SenderIpRanges ` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). +This example creates a new phishing simulation override rule with the specified settings. Regardless of the Name value specified, the rule name is `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). ## PARAMETERS @@ -182,7 +182,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The Name parameter specifies the name for the policy. Regardless of the value you specify, the name will be `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). +The Name parameter specifies the name for the policy. Regardless of the value you specify, the name is `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md index 919af1904f..675ba08cc7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md @@ -33,7 +33,7 @@ New-ExoSecOpsOverrideRule -Policy ``` ## 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 @@ -42,7 +42,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-ExoSecOpsOverrideRule -Name SecOpsOverrideRule -Policy SecOpsOverridePolicy ``` -This example creates the SecOps mailbox override rule with the specified settings. Regardless of the Name value specified, the rule name will be `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977efb). +This example creates the SecOps mailbox override rule with the specified settings. Regardless of the Name value specified, the rule name is `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977efb). ## PARAMETERS @@ -127,7 +127,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The Name parameter specifies the name for the policy. Regardless of the value you specify, the name will be `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977ef). +The Name parameter specifies the name for the policy. Regardless of the value you specify, the name is `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977ef). ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md index 1ef2e0094b..15c47b377e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md @@ -51,7 +51,7 @@ Federation trusts are trusts created between an Exchange organization and the Mi For more information, see [Federation](https://learn.microsoft.com/exchange/federation-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/New-Fingerprint.md b/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md index f72b4bc2e4..223d295bfa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md @@ -15,7 +15,7 @@ title: New-Fingerprint ## SYNOPSIS This cmdlet is functional only in on-premises Exchange. -**Note**: In Exchange Online, this cmdlet has been replaced by the [New-DlpFingerPrint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpfingerprint) cmdlet in Security & Compliance PowerShell. +**Note**: In Exchange Online, this cmdlet is replaced by the [New-DlpFingerPrint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpfingerprint) cmdlet in Security & Compliance PowerShell. Use the New-Fingerprint cmdlet to create document fingerprints that are used with data classification rules. Because the results of New-Fingerprint are not stored outside of the data classification rule, you always run New-Fingerprint and New-DataClassification or Set-DataClassification in the same PowerShell session. @@ -33,7 +33,7 @@ New-Fingerprint [[-FileData] ] -Description ## DESCRIPTION Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. -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/New-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md index 38a27b3040..4dc46016af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md @@ -34,7 +34,7 @@ New-ForeignConnector [-Name] -AddressSpaces ## DESCRIPTION A Foreign connector uses a Drop directory in the Transport service of a Mailbox server to send messages to a local messaging server that doesn't use SMTP as its primary transport mechanism. These messaging servers are known as foreign gateway servers. Non-Microsoft fax gateway servers are examples of foreign gateway servers. The address spaces assigned to a Foreign connector can be SMTP or non-SMTP. -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 @@ -77,7 +77,7 @@ Accept wildcard characters: False The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`. -- AddressSpaceType: The address space type may be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed. +- AddressSpaceType: The address space type might be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed. - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com isn't permitted. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of an address type, you can enter any text for the address space. - AddressSpaceCost: The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains the semicolon character (;), you must specify the address space cost. @@ -88,7 +88,7 @@ If you specify the address space type or the address space cost, you must enclos - "SMTP:contoso.com" - contoso.com -You may specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`. +You might specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`. ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md index a51e891a50..e642369e00 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md @@ -13,7 +13,7 @@ title: New-GlobalAddressList # New-GlobalAddressList ## 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 New-GlobalAddressList cmdlet to create a global address list (GAL). @@ -70,7 +70,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter. -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/New-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md index f791c26aab..38416ce39a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md @@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the New-HoldCompliancePolicy cmdlet to create new preservation policies in the Microsoft Purview compliance portal. -**Note**: The New-HoldCompliancePolicy cmdlet has been replaced by the New-RetentionCompliancePolicy cmdlet. If you have scripts that use New-HoldCompliancePolicy, update them to use New-RetentionCompliancePolicy. +**Note**: The New-HoldCompliancePolicy cmdlet is replaced by the New-RetentionCompliancePolicy cmdlet. If you have scripts that use New-HoldCompliancePolicy, update them to use New-RetentionCompliancePolicy. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -37,7 +37,7 @@ New-HoldCompliancePolicy [-Name] ``` ## DESCRIPTION -New policies are not valid and will not be applied until a preservation rule is added to the policy. +New policies are not valid and aren't applied until a preservation rule is added to the policy. To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). @@ -115,7 +115,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md index 59af4874f5..8dab017d8b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md @@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the New-HoldComplianceRule cmdlet to create new preservation rules in the Microsoft Purview compliance portal. -**Note**: The New-HoldComplianceRule cmdlet has been replaced by the New-RetentionComplianceRule cmdlet. If you have scripts that use New-HoldComplianceRule, update them to use New-RetentionComplianceRule. +**Note**: The New-HoldComplianceRule cmdlet is replaced by the New-RetentionComplianceRule cmdlet. If you have scripts that use New-HoldComplianceRule, update them to use New-RetentionComplianceRule. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -49,7 +49,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned New-HoldComplianceRule -Name SeptOneYear -Policy "Internal Company Policy" -ContentDateFrom "09/10/14 5:00 PM" -ContentDateTo "09/10/15 5:00 PM" -HoldContent Unlimited ``` -This example creates a new preservation rule named SeptOneYear and adds it to the existing preservation policy named "Internal Company Policy". Content created or updated between the specified dates will be held indefinitely. +This example creates a new preservation rule named SeptOneYear and adds it to the existing preservation policy named "Internal Company Policy". Content created or updated between the specified dates is held indefinitely. ## PARAMETERS @@ -237,7 +237,7 @@ The HoldDurationDisplayHint parameter specifies the units that are used to displ - Months - Years -For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. +For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration. ```yaml Type: HoldDurationHint diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md index 8bb8f78675..94dea10d3e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md @@ -84,7 +84,7 @@ New-HostedContentFilterPolicy [-Name] ``` ## 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). For more information about the limits for allowed and blocked senders, see [Exchange Online Protection Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-protection-service-description/exchange-online-protection-limits). @@ -139,7 +139,7 @@ For example, if you enter the value `X-This-is-my-custom-header`, the X-header t If you enter a value that contains spaces or colons (:), the value is ignored, and the default X-header is added to the message (`X-This-Is-Spam: This message appears to be spam.`). -Note that this setting is independent of the AddXHeader value of the TestModeAction parameter. +This setting is independent of the AddXHeader value of the TestModeAction parameter. ```yaml Type: String @@ -304,7 +304,7 @@ The BulkSpamAction parameter specifies the action to take on messages that are m - AddXHeader: Add the AddXHeaderValue parameter value to the message header and deliver the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). -- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). - NoAction - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. @@ -325,7 +325,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages will trigger the action that's specified by the BulkSpamAction parameter. +The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages trigger the action specified by the BulkSpamAction parameter. A higher BCL indicates the message is more likely to generate complaints (and is therefore more likely to be spam). For more information, see [Bulk complaint level (BCL) in EOP](https://learn.microsoft.com/defender-office-365/anti-spam-bulk-complaint-level-bcl-about). @@ -366,7 +366,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: Boolean @@ -384,7 +384,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: Boolean @@ -405,7 +405,7 @@ Accept wildcard characters: False The EnableLanguageBlockList parameter enables or disables marking messages that were written in specific languages as spam. Valid values are: - $true: Mark messages hat were written in the languages specified by the LanguageBlockList parameter as spam. -- $false: Don't mark messages as spam solely based on their languages. This is the default value. +- $false: Don't mark messages as spam solely based on their languages. This value is the default. ```yaml Type: Boolean @@ -426,7 +426,7 @@ Accept wildcard characters: False The EnableRegionBlockList parameter enables or disables marking messages that are sent from specific countries or regions as spam. Valid values are: - $true: Mark messages from senders in the RegionBlockList parameter as spam. -- $false: Don't mark messages as spam solely based on the source country or region. This is the default value. +- $false: Don't mark messages as spam solely based on the source country or region. This value is the default. ```yaml Type: Boolean @@ -444,7 +444,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: SmtpAddress @@ -462,7 +462,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: String @@ -480,7 +480,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: String @@ -498,7 +498,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: Int32 @@ -516,7 +516,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: EsnLanguage @@ -656,8 +656,8 @@ Accept wildcard characters: False The IncreaseScoreWithBizOrInfoUrls parameter increases the spam score of messages that contain links to .biz or .info domains. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. -- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting will be marked as spam. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. +- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting are marked as spam. - Test: The action specified by the TestModeAction parameter is taken on the message. ```yaml @@ -678,8 +678,8 @@ Accept wildcard characters: False The IncreaseScoreWithImageLinks parameter increases the spam score of messages that contain image links to remote websites. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. -- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting will be marked as spam. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. +- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting are marked as spam. - Test: The action specified by the TestModeAction parameter is taken on the message. ```yaml @@ -700,8 +700,8 @@ Accept wildcard characters: False The IncreaseScoreWithNumericIps parameter increases the spam score of messages that contain links to IP addresses. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. -- On: The setting is enabled. Messages that contain links to IP addresses are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. Note that not all messages which matches the setting will be marked as spam. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. +- On: The setting is enabled. Messages that contain links to IP addresses are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. Not all messages which matches the setting are marked as spam. - Test: The action specified by the TestModeAction parameter is taken on the message. ```yaml @@ -722,8 +722,8 @@ Accept wildcard characters: False The IncreaseScoreWithRedirectToOtherPort parameter increases the spam score of messages that contain links that redirect to TCP ports other than 80 (HTTP), 8080 (alternate HTTP), or 443 (HTTPS). Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. -- On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. Note that not all messages which matches the setting will be marked as spam. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. +- On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. Not all messages that match this setting are marked as spam. - Test: The action specified by the TestModeAction parameter is taken on the message. ```yaml @@ -744,7 +744,7 @@ Accept wildcard characters: False The InlineSafetyTipsEnabled parameter specifies whether to enable or disable safety tips that are shown to recipients in messages. Valid values are: -- $true: Safety tips are enabled. This is the default value. +- $true: Safety tips are enabled. This value is the default. - $false: Safety tips are disabled. ```yaml @@ -765,7 +765,7 @@ Accept wildcard characters: False The IntraOrgFilterState parameter specifies whether to enable anti-spam filtering for messages sent between internal users (users in the same organization). The action that's configured in the policy for the specified spam filter verdicts is taken on messages sent between internal users. Valid values are: -- Default: This is the default value. Currently, this value is the same as HighConfidencePhish. +- Default: This value is the default. Currently, this value is the same as HighConfidencePhish. - HighConfidencePhish - Phish: Includes phishing and high confidence phishing. - HighConfidenceSpam: Includes high confidence spam, phishing, and high confidence phishing. @@ -815,7 +815,7 @@ Accept wildcard characters: False The MarkAsSpamBulkMail parameter allows spam filtering to act on bulk email messages. Valid values are: - Off: The message is stamped with the BCL, but no action is taken for a bulk email filtering verdict. In effect, the values of the BulkThreshold and BulkSpamAction parameters are irrelevant. -- On: This is the default value. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message. +- On: This value is the default. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message. - Test: This value is available, but isn't used for this parameter. ```yaml @@ -836,7 +836,7 @@ Accept wildcard characters: False The MarkAsSpamEmbedTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Embed tag in html` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -858,7 +858,7 @@ Accept wildcard characters: False The MarkAsSpamEmptyMessages parameter marks a message as spam when the message contains no subject, no content in the message body, and no attachments. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Empty messages are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Empty Message` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -880,7 +880,7 @@ Accept wildcard characters: False The MarkAsSpamFormTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Form tag in html` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -902,7 +902,7 @@ Accept wildcard characters: False The MarkAsSpamFramesInHtml parameter marks a message as spam when the message contains HTML \ or \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ or \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: IFRAME or FRAME in HTML` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -924,7 +924,7 @@ Accept wildcard characters: False The MarkAsSpamFromAddressAuthFail parameter marks a message as spam when Sender ID filtering encounters a hard fail. This setting combines an Sender Policy Framework (SPF) check with a Sender ID check to help protect against message headers that contain forged senders. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages where Sender ID filtering encounters a hard fail are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF From Record Fail` is added to the message. ```yaml @@ -945,7 +945,7 @@ Accept wildcard characters: False The MarkAsSpamJavaScriptInHtml parameter marks a message as spam when the message contains JavaScript or VBScript. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain JavaScript or VBScript are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Javascript or VBscript tags in HTML` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -967,7 +967,7 @@ Accept wildcard characters: False The MarkAsSpamNdrBackscatter parameter marks a message as spam when the message is a non-delivery report (also known as an NDR or bounce messages) sent to a forged sender (known as *backscatter*). Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Backscatter is given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Backscatter NDR` is added to the message. ```yaml @@ -988,7 +988,7 @@ Accept wildcard characters: False The MarkAsSpamObjectTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Object tag in html` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -1010,7 +1010,7 @@ Accept wildcard characters: False The MarkAsSpamSensitiveWordList parameter marks a message as spam when the message contains words from the sensitive words list. Microsoft maintains a dynamic but non-editable list of words that are associated with potentially offensive messages. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain words from the sensitive word list in the subject or message body are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Sensitive word in subject/body` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -1032,7 +1032,7 @@ Accept wildcard characters: False The MarkAsSpamSpfRecordHardFail parameter marks a message as spam when SPF record checking encounters a hard fail. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages sent from an IP address that isn't specified in the SPF Sender Policy Framework (SPF) record in DNS are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF Record Fail` is added to the message. ```yaml @@ -1053,7 +1053,7 @@ Accept wildcard characters: False The MarkAsSpamWebBugsInHtml parameter marks a message as spam when the message contains web bugs (also known as web beacons). Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain web bugs are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Web bug` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -1132,7 +1132,7 @@ The PhishSpamAction parameter specifies the action to take on messages that are - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. -- Quarantine: Move the message to the quarantine. This is the default value. The quarantined message is available to the intended recipients (as of April, 2020) and admins. +- Quarantine: Move the message to the quarantine. This value is the default. The quarantined message is available to the intended recipients (as of April, 2020) and admins. - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as phishing are available to admins and (as of April 2020) the intended recipients. Or, you can use the PhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. @@ -1154,7 +1154,7 @@ Accept wildcard characters: False The PhishZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect phishing in already delivered messages in Exchange Online mailboxes. Valid values are: -- $true: ZAP for phishing messages is enabled. This is the default value. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. +- $true: ZAP for phishing messages is enabled. This value is the default. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. - $false: ZAP for phishing messages is disabled. You configure ZAP for spam with the SpamZapEnabled parameter. @@ -1279,7 +1279,7 @@ The SpamAction parameter specifies the action to take on messages that are marke - AddXHeader: Add the AddXHeaderValue parameter value to the message header, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). -- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. @@ -1329,7 +1329,7 @@ Accept wildcard characters: False The SpamZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect spam in already delivered messages in Exchange Online mailboxes. Valid values are: -- $true: ZAP for spam is enabled. This is the default value. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. +- $true: ZAP for spam is enabled. This value is the default. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. - $false: ZAP for spam is disabled. You configure ZAP for phishing messages with the PhishZapEnabled parameter. @@ -1352,7 +1352,7 @@ Accept wildcard characters: False The TestModeAction parameter specifies the additional action to take on messages when one or more IncreaseScoreWith\* or MarkAsSpam\* ASF parameters are set to the value Test. Valid values are: -- None: This is the default value, and we recommend that you don't change it. +- None: This value is the default, and we recommend that you don't change it. - AddXHeader: The X-header value `X-CustomSpam: This message was filtered by the custom spam filter option` is added to the message. - BccMessage: Redirect the message to the recipients specified by the TestModeBccToRecipients parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md index 7dc54be6f6..4560b98a1b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md @@ -41,7 +41,7 @@ New-HostedContentFilterRule [-Name] -HostedContentFilterPolicy [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Use the Microsoft Defender portal to create anti-spam policies](https://learn.microsoft.com/defender-office-365/anti-spam-policies-configure#use-the-microsoft-defender-portal-to-create-anti-spam-policies). -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/New-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md index d838d30f5b..944b15fa76 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md @@ -40,7 +40,7 @@ New-HostedOutboundSpamFilterPolicy [-Name] ## DESCRIPTION New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the HostedOutboundSpamFilterPolicy parameter on the New-HostedOutboundSpamFilterRule or Set-HostedOutboundSpamFilterRule cmdlets to associate the policy with a rule. -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 @@ -82,7 +82,7 @@ The ActionWhenThresholdReach parameter specifies the action to take when any of - Alert: No action, alert only. - BlockUser: Prevent the user from sending email messages. -- BlockUserForToday: Prevent the user from sending email messages until the following day. This is the default value. +- BlockUserForToday: Prevent the user from sending email messages until the following day. This value is the default. ```yaml Type: OutboundRecipientLimitsExceededAction @@ -121,7 +121,7 @@ Accept wildcard characters: False The AutoForwardingMode specifies how the policy controls automatic email forwarding to external recipients. Valid values are: -- Automatic: This is the default value. This value is now the same as Off. When this value was originally introduced, it was equivalent to On. Over time, thanks to the principles of [secure by default](https://learn.microsoft.com/defender-office-365/secure-by-default), the effect of this value was eventually changed to Off for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/all-you-need-to-know-about-automatic-email-forwarding-in/ba-p/2074888). +- Automatic: This value is the default. This value is now the same as Off. When this value was originally introduced, it was equivalent to On. Over time, thanks to the principles of [secure by default](https://learn.microsoft.com/defender-office-365/secure-by-default), the effect of this value was eventually changed to Off for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/all-you-need-to-know-about-automatic-email-forwarding-in/ba-p/2074888). - On: Automatic external email forwarding isn't disabled by the policy. - Off: Automatic external email forwarding is disabled by the policy and results in a non-delivery report (also known as an NDR or bounce message) to the sender. @@ -167,7 +167,7 @@ Accept wildcard characters: False The BccSuspiciousOutboundMail parameter specifies whether to add recipients to the Bcc field of outgoing spam messages. Valid values are: - $true: The recipients specified by the BccSuspiciousOutboundAdditionalRecipients parameter are added to outgoing spam messages. -- $false: No additional messages are added to outgoing spam messages. This is the default value. +- $false: No additional messages are added to outgoing spam messages. This value is the default. ```yaml Type: Boolean @@ -185,12 +185,12 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). +**Note**: This setting is replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). The NotifyOutboundSpam parameter specify whether to notify admins when outgoing spam is detected. Valid values are: - $true: Notify the admins specified by the NotifyOutboundSpamRecipients parameter. -- $false: Don't send notifications. This is the default value. +- $false: Don't send notifications. This value is the default. ```yaml Type: Boolean @@ -208,7 +208,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). +**Note**: This setting is replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). The NotifyOutboundSpamRecipients parameter specifies the email addresses of admins to notify when an outgoing spam is detected. You can specify multiple email addresses separated by commas. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md index 1afdd51735..423016b19a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md @@ -38,7 +38,7 @@ New-HostedOutboundSpamFilterRule [-Name] -HostedOutboundSpamFilterPolic ``` ## 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 @@ -142,7 +142,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: -- $true: The rule is enabled. This is the default value. +- $true: The rule is enabled. This value is the default. - $false: The rule is disabled. In the properties of the rule, the value of this parameter is visible in the State property. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md index eeb2dd5b03..8ba792670c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md @@ -51,7 +51,7 @@ The available settings in this cmdlet are configured when the Hybrid Configurati For more information, see [Exchange Server hybrid deployments](https://learn.microsoft.com/exchange/exchange-hybrid). -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/New-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md index bed3ce6485..8c1f5d800e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md @@ -53,7 +53,7 @@ New-InboundConnector [-Name] -SenderDomains ## DESCRIPTION Inbound connectors accept email messages from remote domains that require specific configuration options. -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 @@ -162,7 +162,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f Valid values are: -- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. +- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. ```yaml @@ -222,7 +222,7 @@ Accept wildcard characters: False The ConnectorSource parameter specifies how the connector is created. Valid input for this parameter includes the following values: -- Default: The connector is manually created. This is the default value. +- Default: The connector is manually created. This value is the default. - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. @@ -292,7 +292,7 @@ Accept wildcard characters: False The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connectors. Valid values are: - $true: Only the last message source is skipped. -- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This is the default value. +- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This value is the default. ```yaml Type: Boolean @@ -368,7 +368,7 @@ Accept wildcard characters: False The Enabled parameter enables or disables the connector. Valid values are: -- $true: The connector is enabled. This is the default value. +- $true: The connector is enabled. This value is the default. - $false: The connector is disabled. ```yaml @@ -389,7 +389,7 @@ Accept wildcard characters: False The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by a Partner type connector. Valid values are: -- $true: Reject messages if they aren't sent over TLS. This is the default value +- $true: Reject messages if they aren't sent over TLS. This value is the default - $false: Allow messages if they aren't sent over TLS. **Note**: This parameter applies only to Partner type connectors. @@ -413,7 +413,7 @@ Accept wildcard characters: False The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the Partner type connector. Valid values are: - $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value. -- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value. +- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This value is the default. **Note**: This parameter applies only to Partner type connectors. @@ -436,7 +436,7 @@ Accept wildcard characters: False The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses for Partner type connectors. Valid values are: - $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter. -- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value. +- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This value is the default. **Note**: This parameter applies only to Partner type connectors. @@ -522,7 +522,7 @@ Accept wildcard characters: False The TreatMessagesAsInternal parameter specifies an alternative method to identify messages sent from an on-premises organization as internal messages. You should only consider using this parameter when your on-premises organization doesn't use Exchange. Valid values are: - $true: Messages are considered internal if the sender's domain matches a domain that's configured in Microsoft 365. This setting allows internal mail flow between Microsoft 365 and on-premises organizations that don't have Exchange Server 2010 or later installed. However, this setting has potential security risks (for example, internal messages bypass antispam filtering), so use caution when configuring this setting. -- $false: Messages aren't considered internal. This is the default value. +- $false: Messages aren't considered internal. This value is the default. In hybrid environments, you don't need to use this parameter, because the Hybrid Configuration wizard automatically configures the required settings on the Inbound connector in Microsoft 365 and the Send connector in the on-premises Exchange organization (the CloudServicesMailEnabled parameter). diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md index c9db1ab9c4..7afb9dee03 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md @@ -13,7 +13,7 @@ title: New-InboxRule # New-InboxRule ## 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 New-InboxRule cmdlet to create Inbox rules in mailboxes. Inbox rules process messages in the Inbox based on conditions and take actions such as moving a message to a specified folder or deleting a message. @@ -117,7 +117,7 @@ When you create, modify, remove, enable, or disable an Inbox rule in Exchange Po Parameters that are used for conditions also have corresponding exception parameters. When conditions specified in an exception are matched, the rule isn't applied to the message. Exception parameters begin with ExceptIf. For example, the exception parameter for SubjectOrBodyContainsWords is ExceptIfSubjectOrBodyContainsWords. -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 @@ -179,7 +179,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The ValidateOnly switch tells the cmdlet to evaluate the conditions and requirements necessary to perform the operation and then reports whether the operation will succeed or fail. No changes are made when the ValidateOnly switch is used. +The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -944,7 +944,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the ExceptIfWithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of ExceptIfWithinSizeRangeMinimum. @@ -976,7 +976,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the ExceptIfWithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of ExceptIfWithinSizeRangeMaximum. @@ -1055,7 +1055,7 @@ Accept wildcard characters: False The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet. +A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet. ```yaml Type: SwitchParameter @@ -1823,7 +1823,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the WithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of WithinSizeRangeMinimum. @@ -1855,7 +1855,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the WithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of WithinSizeRangeMaximum. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md index 8b9e46152e..9937381641 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md @@ -269,7 +269,7 @@ Accept wildcard characters: False The State parameter specifies whether the information barrier policy is active or inactive. Valid values are: - Active -- Inactive (This is the default value.) +- Inactive (This value is the default.) ```yaml Type: EopInformationBarrierPolicyState diff --git a/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md index dd86a9f2b3..69e235ceee 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md @@ -13,7 +13,7 @@ title: New-IntraOrganizationConnector # New-IntraOrganizationConnector ## 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 New-IntraOrganizationConnector cmdlet to create an Intra-Organization connector between two on-premises Exchange forests in an organization, between an Exchange on-premises organization and an Exchange Online organization, or between two Exchange Online organizations. This connector enables feature availability and service connectivity across the organizations using a common connector and connection endpoints. @@ -36,7 +36,7 @@ The New-IntraOrganizationConnector cmdlet is used to create a connection for fea For hybrid deployments between on-premises Exchange and Exchange Online organizations, the New-IntraOrganizationConnector cmdlet is used by the Hybrid Configuration wizard. Typically, the Intra-Organization connector is configured when the hybrid deployment is initially created by the wizard. We strongly recommend that you use the Hybrid Configuration wizard to create the Intra-Organization connector when configuring a hybrid deployment with an Exchange Online organization. -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 @@ -89,7 +89,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The TargetAddressDomains parameter specifies the domain namespaces that will be used in the Intra-organization connector. These domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity. +The TargetAddressDomains parameter specifies the domain namespaces to use in the Intra-organization connector. These domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity. You specify multiple domain values separated by commas. @@ -172,7 +172,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services that will be used in the Intra-Organization connector. +The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services to use in the Intra-Organization connector. ```yaml Type: Uri diff --git a/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md index 0103a92195..97291cdb9b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md @@ -13,7 +13,7 @@ title: New-JournalRule # New-JournalRule ## 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 New-JournalRule cmdlet to create a journal rule in your organization. @@ -37,7 +37,7 @@ The New-JournalRule cmdlet creates a journal rule in your organization. By default, new journal rules are disabled unless the Enabled parameter is set to $true. For more information about how to enable a new journal rule that was created in a disabled state, see [Enable-JournalRule](https://learn.microsoft.com/powershell/module/exchangepowershell/enable-journalrule). -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/New-Label.md b/exchange/exchange-ps/ExchangePowerShell/New-Label.md index 6a8b3932a6..a7369fefac 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-Label.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-Label.md @@ -183,7 +183,7 @@ Some of the settings that you configure with this parameter are supported only b Supported settings for built-in labeling: -- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting impacts services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `New-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content). +- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting affects services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `New-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content). - **Color**: Specifies a label color as a hex triplet code for the red, green, and blue (RGB) components of the color. Example: `New-Label -DisplayName "General" -Name "General" -Tooltip "Business data that is not intended for public consumption." -AdvancedSettings @{color="#40e0d0"}`. For more information, see [Configuring custom colors by using PowerShell](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configuring-custom-colors-by-using-powershell). @@ -878,7 +878,7 @@ The feature for this parameter is currently in Public Preview, and is not availa The EncryptionDoubleKeyEncryptionUrl parameter specifies the Double Key Encryption endpoint URL. -You can't remove the URL after the label has been created; you can only modify it. +You can't remove the URL after the label is created; you can only modify it. This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md index ab078d7da6..c4edd6a938 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md @@ -130,7 +130,7 @@ Supported settings for built-in labeling: - **teamworkdefaultlabelid**: Outlook and Teams apps that support this setting apply a default label, or no label for meetings. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{teamworkdefaultlabelid="General"}`. For more information about labeling meetings, see [Use sensitivity labels to protect calendar items, Teams meetings, and chat](https://learn.microsoft.com/purview/sensitivity-labels-meetings). -- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) will be displayed. Users can't revert this setting in the app. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}` +- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) are displayed. Users can't revert this setting in the app. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}` Additionally, for Power BI: diff --git a/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md index ad9a4a3cdd..2554ec465a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md @@ -34,7 +34,7 @@ New-M365DataAtRestEncryptionPolicy [-Name] -AzureKeyIDs [-SupervisoryReviewPolicy] ``` ## 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). In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. @@ -802,7 +802,7 @@ Set-Mailbox -Identity Sales -GrantSendOnBehalfTo MarketingSG Add-MailboxPermission -Identity Sales -User MarketingSG -AccessRights FullAccess -InheritanceType All ``` -This example creates the shared mailbox "Sales Department" and grants Full Access and Send on Behalf permissions for the security group "MarketingSG". Users who are members of the security group will be granted the permissions to the mailbox. +This example creates the shared mailbox "Sales Department" and grants Full Access and Send on Behalf permissions for the security group "MarketingSG". Users who are members of the security group are granted the permissions to the mailbox. This example assumes that you've already created a mail-enabled security group named "MarketingSG" by using the New-DistributionGroup cmdlet. @@ -1584,7 +1584,7 @@ The HoldForMigration switch specifies whether to prevent any client or user, exc You need to use this parameter when you create the first public folder, which is called the hierarchy mailbox, in your organization. -Use this parameter only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you won't be able to create any public folders. +Use this parameter only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you can't create any public folders. ```yaml Type: SwitchParameter @@ -1640,7 +1640,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and won't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user will still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox. +The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and can't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user can still access the specified public folder mailbox, even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox. ```yaml Type: Boolean @@ -1828,7 +1828,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -1971,7 +1971,7 @@ Accept wildcard characters: False The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are: -- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value. +- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This value is the default. - $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC. Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server. @@ -1997,7 +1997,7 @@ Accept wildcard characters: False The ResetPasswordOnNextLogon parameter specifies whether the user is required to change their password the next time they log on to their mailbox. Valid values are: - $true: The user is required to change their password the next time they log on to their mailbox. -- $false: The user isn't required to change their password the next time they log on to their mailbox. This is the default value. +- $false: The user isn't required to change their password the next time they log on to their mailbox. This value is the default. ```yaml Type: Boolean @@ -2127,7 +2127,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -2147,7 +2147,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved.