diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md index 7c7abb37c4..38a1dafa95 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md @@ -13,7 +13,7 @@ title: New-MailContact # New-MailContact ## 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-MailContact cmdlet to create mail contacts. @@ -45,7 +45,7 @@ New-MailContact -Name -ExternalEmailAddress ``` ## 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 @@ -286,7 +286,7 @@ Accept wildcard characters: False The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: -- BinHex (This is the default value) +- BinHex (default value) - UuEncode - AppleSingle - AppleDouble @@ -316,7 +316,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -343,7 +343,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -398,7 +398,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. @@ -469,7 +469,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. @@ -494,7 +494,7 @@ Accept wildcard characters: False The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are: - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact. -- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. +- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md b/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md index 15dda9b258..a2f50ad71e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md @@ -13,7 +13,7 @@ title: New-MailMessage # New-MailMessage ## 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-MailMessage cmdlet to create an email message for the specified user mailbox and place the email message in the Drafts folder of the user's mailbox. @@ -35,7 +35,7 @@ New-MailMessage ## DESCRIPTION If the cmdlet is run without specifying the Subject or Body parameters, an empty email message is placed in the user's Drafts folder. -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-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md index b40c8f5a49..3aa57b37d4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md @@ -13,7 +13,7 @@ title: New-MailUser # New-MailUser ## 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-MailUser cmdlet to create mail users. Mail users (also known as mail-enabled users) have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. Email messages sent to mail users are delivered to the specified external email address. @@ -221,7 +221,7 @@ New-MailUser [-Name] -MicrosoftOnlineServicesID -Passwo ``` ## 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 @@ -604,7 +604,7 @@ Accept wildcard characters: False The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: -- BinHex (This is the default value) +- BinHex (default value) - UuEncode - AppleSingle - AppleDouble @@ -654,7 +654,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -680,7 +680,7 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text -- Mime (This is the default value) +- Mime (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -737,7 +737,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. @@ -808,7 +808,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. @@ -836,7 +836,7 @@ This parameter is available only in on-premises Exchange. The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are: - $true: The user is required to change their password the next time they log on. -- $false: The user isn't required to change their password the next time they log on. This is the default value. +- $false: The user isn't required to change their password the next time they log on. This value is the default. ```yaml Type: Boolean @@ -856,7 +856,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 @@ -876,7 +876,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. @@ -901,7 +901,7 @@ Accept wildcard characters: False The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are: - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact. -- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. +- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md index 668aa944b8..4aa8ca23e8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md @@ -16,7 +16,7 @@ title: New-MailboxAuditLogSearch > [!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-MailboxAuditLogSearch cmdlet to search mailbox audit logs and have search results sent via email to specified recipients. @@ -45,7 +45,7 @@ The New-MailboxAuditLogSearch cmdlet performs an asynchronous search of mailbox To search mailbox audit logs for a single mailbox and have the results displayed in the Exchange Management Shell window, use the Search-MailboxAuditLog cmdlet instead. To learn more about mailbox audit logging, see [Mailbox audit logging in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mailbox-audit-logging/mailbox-audit-logging). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -172,7 +172,7 @@ The ExternalAccess parameter specifies whether to return only audit log entries $true: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are returned. -$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This is the default value. +$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md index 6626bb96cf..13b7f9cdaf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md @@ -53,7 +53,7 @@ New-MailboxDatabase [[-Name] ] -Server ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md index 60444e5677..a4d5b91ef0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md @@ -120,14 +120,14 @@ New-MailboxExportRequest [-Mailbox] -ComplianceStor ## DESCRIPTION You can create more than one mailbox export request per mailbox, and each mailbox export request must have a unique name. Microsoft Exchange automatically generates up to 10 unique names for a mailbox export request. However, to create more than 10 export requests for a mailbox, you need to specify a unique name when creating the export request. You can remove existing export requests with the Remove-MailboxExportRequest cmdlet before starting a new request with the default request name `\MailboxExportX` (where X = 0-9). -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 need to grant the following permission to the group Exchange Trusted Subsystem to the network share where you want to export or import PST files: - To import PST files from the share: Read permission - To save exported PST files to the share: Read/Write permission. -If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. +If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share. ## EXAMPLES @@ -223,7 +223,7 @@ You need to grant the following permission to the group Exchange Trusted Subsyst - To import PST files from the share: Read permission - To save exported PST files to the share: Read/Write permission. -If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. +If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share. ```yaml Type: LongPath @@ -345,7 +345,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit is 30 days. +The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before it's automatically removed. The default value is 30 days. ```yaml Type: Unlimited @@ -389,7 +389,7 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl - ForceCopy - KeepAll - KeepLatestItem -- KeepSourceItem (This is the default value.) +- KeepSourceItem (This value is the default.) - KeepTargetItem - UpdateFromSource @@ -409,9 +409,9 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -**Important**: You can't use this parameter to export between two dates. If you try, you'll get system convert errors. You can export from a specific date, or export to a specific date, but not both. +**Important**: You can't use this parameter to export between two dates. You can export from a specific date, or export to a specific date, but not both. -The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter will be exported into the .pst file. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`. +The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter are exported into the .pst file. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`. - Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables. - Property is a filterable property. For filterable properties, see [Filterable properties for the ContentFilter parameter](https://learn.microsoft.com/exchange/filterable-properties-for-the-contentfilter-parameter). @@ -721,7 +721,7 @@ The Priority parameter specifies the order in which the request should be proces - Lower - Low -- Normal (This is the default value.) +- Normal (This value is the default.) - High - Higher - Highest @@ -824,7 +824,7 @@ Accept wildcard characters: False The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. -If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. +If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md index 01dfb10e92..d7e9d64fe5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md @@ -13,7 +13,7 @@ title: New-MailboxFolder # New-MailboxFolder ## 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-MailboxFolder cmdlet to create folders in your own mailbox. Administrators can't use this cmdlet to create folders in other mailboxes (the cmdlet is available only from the MyBaseOptions user role). @@ -32,7 +32,7 @@ New-MailboxFolder [-Name] -Parent ## DESCRIPTION If no parent folder is specified, the cmdlet creates a mail folder in the root folder hierarchy of the mailbox. If the mailbox isn't specified, the cmdlet creates the folder in the mailbox of the user currently running the task. When run, the cmdlet returns the new folder name and the folder path as the output. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). . +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). . ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md index 935c6d2a7b..3354f48df9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md @@ -13,7 +13,7 @@ title: New-MailboxImportRequest # New-MailboxImportRequest ## 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-MailboxImportRequest cmdlet to begin the process of importing a .pst file to a mailbox or archive. @@ -133,7 +133,7 @@ In on-premises Exchange, you need to grant the following permission to the group - To import PST files from the share: Read permission - To save exported PST files to the share: Read/Write permission. -If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. +If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share. ## EXAMPLES @@ -246,7 +246,7 @@ You need to grant the following permission to the group Exchange Trusted Subsyst - To import PST files from the share: Read permission - To save exported PST files to the share: Read/Write permission. -If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. +If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share. ```yaml Type: LongPath @@ -370,7 +370,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default value of the CompletedRequestAgeLimit parameter is 30 days. +The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before being automatically removed. The default value is 30 days. ```yaml Type: Unlimited @@ -414,7 +414,7 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl - ForceCopy (Exchange 2016 or later) - KeepAll - KeepLatestItem -- KeepSourceItem (This is the default value) +- KeepSourceItem (default value) - KeepTargetItem (Exchange 2016 or later) - UpdateFromSource (Exchange 2016 or later) @@ -894,7 +894,7 @@ Accept wildcard characters: False The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. -If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. +If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md index e79715622b..4342464833 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md @@ -51,7 +51,7 @@ After you begin a repair request, you can't stop it unless you dismount the data To avoid performance problems, only one request can be active on a server for a database-level repair, or up to 100 requests can be active on a server for a mailbox-level repair. -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-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md index b5a99217c4..4df394dfdc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md @@ -13,7 +13,7 @@ title: New-MailboxRestoreRequest # New-MailboxRestoreRequest ## 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-MailboxRestoreRequest cmdlet to restore a soft-deleted or disconnected mailbox. This cmdlet starts the process of moving content from the soft-deleted mailbox, disabled mailbox, or any mailbox in a recovery database into a connected primary or archive mailbox. @@ -220,15 +220,15 @@ To view soft-deleted mailboxes, run the Get-MailboxStatistics cmdlet against a d A mailbox is marked as Disabled a short time after the Disable-Mailbox or Remove-Mailbox command completes. -The mailbox won't be marked as Disabled until the Microsoft Exchange Information Store service determines that Active Directory has been updated with the disabled mailbox's information. You can expedite the process by running the Update-StoreMailboxState cmdlet against that database. +The mailbox isn't marked as Disabled until the Microsoft Exchange Information Store service determines that Active Directory is updated with the disabled mailbox's information. You can expedite the process by running the Update-StoreMailboxState cmdlet against that database. Exchange retains disabled mailboxes in the mailbox database based on the deleted mailbox retention settings configured for that mailbox database. After the specified period of time, the mailbox is permanently deleted. To view disabled mailboxes, run the Get-MailboxStatistics cmdlet against a database and look for results that have a DisconnectReason with a value of Disabled. For more information, see Examples 2 and 3 later in this topic. -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). -**Note**: To restore the contents of a primary mailbox to an archive mailbox, use the TargetRootFolder parameter to specify the archive mailbox folders to migrate the content to. This content will be visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users. +**Note**: To restore the contents of a primary mailbox to an archive mailbox, use the TargetRootFolder parameter to specify the archive mailbox folders to migrate the content to. This content is visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users. ## EXAMPLES @@ -563,7 +563,7 @@ The AssociatedMessagesCopyOption parameter specifies whether associated messages - DoNotCopy: The associated messages aren't copied. - MapByMessageClass: Find the associated message by looking up the MessageClass attribute of the source message. If there's an associated message of this class in both source and target folders, it overwrites the associated message in the target. If there isn't an associated message in the target, it creates a copy in the target. -- Copy: Copy associated messages from the source to the target. If the same message type exists both in the source and the target location, these associated messages are duplicated. This is the default value. +- Copy: Copy associated messages from the source to the target. If the same message type exists both in the source and the target location, these associated messages are duplicated. This value is the default. Content filtering doesn't apply to associated messages. @@ -589,7 +589,7 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -669,7 +669,7 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl - ForceCopy - KeepAll - KeepLatestItem -- KeepSourceItem (This is the default value.) +- KeepSourceItem (This value is the default.) - KeepTargetItem - UpdateFromSource @@ -691,7 +691,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter will be restored. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`. +The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter are restored. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`. - Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables. - Property is a filterable property. For filterable properties, see [Filterable properties for the ContentFilter parameter](https://learn.microsoft.com/exchange/filterable-properties-for-the-contentfilter-parameter). @@ -907,7 +907,7 @@ Valid input for this parameter is an integer or the value unlimited. The default If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -972,7 +972,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal (This is the default value.) +- Normal (This value is the default.) - High - Higher - Highest @@ -1086,7 +1086,7 @@ Accept wildcard characters: False The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. -If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. +If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet. ```yaml Type: SwitchParameter @@ -1142,7 +1142,7 @@ Accept wildcard characters: False The TargetRootFolder parameter specifies the top-level folder in which to restore data. If you don't specify this parameter, the command restores folders to the top of the folder structure in the target mailbox or archive. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure. -**Note**: To restore the contents of a primary mailbox to an archive mailbox, use this parameter to specify the archive mailbox folders to migrate the content to. This content will be visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users. +**Note**: To restore the contents of a primary mailbox to an archive mailbox, use this parameter to specify the archive mailbox folders to migrate the content to. This content is visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users. ```yaml Type: String @@ -1164,7 +1164,7 @@ The TargetType parameter specifies the type of mailbox that's the target for the - Archive - MailboxLocation -- Primary (This is the default value) +- Primary (default value) ```yaml Type: TargetTypeComponent diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md index 33a76bb56f..36cb459e8b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md @@ -13,7 +13,7 @@ title: New-MailboxSearch # New-MailboxSearch ## 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-MailboxSearch cmdlet to create a mailbox search and either get an estimate of search results, place search results on In-Place Hold or copy them to a Discovery mailbox. You can also place all contents in a mailbox on hold by not specifying a search query, which accomplishes similar results as Litigation Hold. @@ -62,7 +62,7 @@ By default, mailbox searches are performed across all Exchange 2013 or later Mai For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and [In-Place Hold and Litigation Hold in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/holds/holds). -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 @@ Accept wildcard characters: False The AllPublicFolderSources parameter specifies whether to include all public folders in the organization in the search. Valid values are: - $true: All public folders are included in the search. This value is required when the value of the AllSourceMailboxes parameter is $false and you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). -- $false: No public folders are included in the search. This is the default value. You can use this value when the value of the AllSourceMailboxes parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). +- $false: No public folders are included in the search. This value is the default. You can use this value when the value of the AllSourceMailboxes parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean @@ -151,7 +151,7 @@ Accept wildcard characters: False The AllSourceMailboxes parameter specifies whether to include all mailboxes in the search. Valid values are: - $true: All mailboxes are included in the search. This value is required when the value of the AllPublicFolderSources parameter is $false and you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). -- $false: All mailboxes aren't included in the search. This is the default value. You can use this value when the value of the AllPublicFolderSources parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). +- $false: All mailboxes aren't included in the search. This value is the default. You can use this value when the value of the AllPublicFolderSources parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean @@ -270,7 +270,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The EstimateOnly switch specifies that only an estimate of the number of items that will be returned is provided. You don't need to specify a value with this switch. +The EstimateOnly switch specifies that only an estimate of the number of items to be returned is provided. You don't need to specify a value with this switch. If you don't use this switch, messages are copied to the target mailbox. @@ -292,7 +292,7 @@ Accept wildcard characters: False The ExcludeDuplicateMessages parameter eliminates duplication of messages in search results. Valid values are: -- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This is the default value. +- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This value is the default. - $false: Copy all instances of a message if the same message exists in multiple folders or mailboxes. ```yaml @@ -372,11 +372,11 @@ Accept wildcard characters: False The InPlaceHoldEnabled parameter specifies whether to set an In-Place Hold on items in the search results. Valid values are: - $true: In-Place Hold is enabled on the search results. -- $false: In-Place Hold isn't enabled on the search results. This is the default value. +- $false: In-Place Hold isn't enabled on the search results. This value is the default. You can't set an In-Place Hold on the search results when the AllSourceMailboxes parameter is $true. -If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command may succeed but the mailboxes are not placed on In-Place Hold. +If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command might succeed but the mailboxes are not placed on In-Place Hold. ```yaml Type: Boolean @@ -415,7 +415,7 @@ Accept wildcard characters: False The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold onthe mailbox items (all mailbox items or the items that are returned in the search query results). The duration is calculated from the time the item is received or created in the mailbox. Valid values are: - An integer. -- The value unlimited. This is the default value. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false. +- The value unlimited. This value is the default. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false. ```yaml Type: Unlimited @@ -456,7 +456,7 @@ Accept wildcard characters: False The LogLevel parameter specifies the logging level for the search. Valid values are: - Suppress: No logs are kept. -- Basic: Basic information about the query and who ran it is kept. This is the default value. +- Basic: Basic information about the query and who ran it is kept. This value is the default. - Full: In addition to the information kept by the Basic log level, the Full log level adds a complete list of search results. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md index b137806a42..952710db59 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md @@ -13,7 +13,7 @@ title: New-MalwareFilterPolicy # New-MalwareFilterPolicy ## 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-MalwareFilterPolicy cmdlet to create malware filter policies in your organization. @@ -56,7 +56,7 @@ New-MalwareFilterPolicy [-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 MalwareFilterPolicy parameter on the New-MalwareFilterRule or Set-MalwareFilterRule 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 @@ -98,7 +98,7 @@ This parameter is available only in on-premises Exchange. The Action parameter specifies the action to take when malware is detected in a message. Valid values are: -- DeleteMessage: Handles the message without notifying the recipients. This is the default value. +- DeleteMessage: Handles the message without notifying the recipients. This value is the default. - DeleteAttachmentAndUseDefaultAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the default alert text. - DeleteAttachmentAndUseCustomAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the custom alert text specified by the CustomAlertText parameter. @@ -141,7 +141,7 @@ This parameter is available only in on-premises Exchange. The BypassInboundMessages parameter enables or disables malware filtering on incoming messages (messages entering the organization). Valid values are: - $true: Malware filtering is disabled on inbound messages. -- $false: Malware filtering is enabled on inbound messages. This is the default value. +- $false: Malware filtering is enabled on inbound messages. This value is the default. ```yaml Type: Boolean @@ -164,7 +164,7 @@ This parameter is available only in on-premises Exchange. The BypassOutboundMessages parameter enables or disables malware filtering on outgoing messages (messages leaving the organization). Valid values are: - $true: Malware filtering is disabled on outbound messages. -- $false: Malware filtering is enabled on outbound messages. This is the default value. +- $false: Malware filtering is enabled on outbound messages. This value is the default. ```yaml Type: Boolean @@ -418,7 +418,7 @@ Accept wildcard characters: False The EnableExternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from external senders, a notification messages is sent to the email address that's specified by the ExternalSenderAdminAddress parameter. -- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This is the default value. +- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This value is the default. **Note**: Admin notifications are sent only for _attachments_ that are classified as malware. @@ -443,7 +443,7 @@ This parameter is available only in on-premises Exchange. The EnableExternalSenderNotifications parameter enables or disables sending notification messages to external senders for malware detections in their messages. Valid values are: - $true: When malware is detected in a message from an external sender, send them a notification message. -- $false: Don't send malware detection notification messages to external message senders. This is the default value. +- $false: Don't send malware detection notification messages to external message senders. This value is the default. ```yaml Type: Boolean @@ -465,7 +465,7 @@ This parameter is available only in the cloud-based service. The EnableFileFilter parameter enables or disables the common attachments filter (also known as common attachment blocking). Valid values are: -- $true: The common attachments filter is enabled. This is the default value. +- $true: The common attachments filter is enabled. This value is the default. - $false: The common attachments filter is disabled. You specify the file types using the FileTypes parameter. A default list of values is automatically provided, but you can customize it. @@ -491,7 +491,7 @@ Accept wildcard characters: False The EnableInternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from internal senders, a notification messages is sent to the email address that's specified by the InternalSenderAdminAddress parameter. -- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This is the default value. +- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This value is the default. **Note**: Admin notifications are sent only for _attachments_ that are classified as malware. @@ -516,7 +516,7 @@ This parameter is available only in on-premises Exchange. The EnableInternalSenderNotifications parameter enables or disables sending notification messages to internal senders for malware detections in their messages. Valid values are: - $true: When malware is detected in a message from an internal sender, send them a notification message. -- $false: Don't send malware detection notification messages to internal message senders. This is the default value. +- $false: Don't send malware detection notification messages to internal message senders. This value is the default. ```yaml Type: Boolean @@ -559,7 +559,7 @@ This parameter is available only in the cloud-based service. The FileTypeAction parameter specifies what happens to messages that contain one or more attachments where the file extension is included in the FileTypes parameter (the common attachments filter). Valid values are: - Quarantine: Quarantine the message. Whether or not the recipient is notified depends on the quarantine notification settings in the quarantine policy that's selected for the malware filter policy by the QuarantineTag parameter. -- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This is the default value. +- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This value is the default. This parameter is meaningful only when the value of the EnableFileFilter parameter is $true. @@ -701,7 +701,7 @@ This parameter is available only in the cloud-based service. The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware in cloud mailboxes. ZAP detects malware in unread messages that have already been delivered to the user's Inbox. Valid values are: -- $true: ZAP for malware is enabled. Unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. This is the default value. +- $true: ZAP for malware is enabled. Unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. This value is the default. - $false: ZAP for malware is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md index 31f0a6a755..2b3a5a5742 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md @@ -13,7 +13,7 @@ title: New-MalwareFilterRule # New-MalwareFilterRule ## 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-MalwareFilterRule cmdlet to create malware filter rules in your organization. @@ -42,7 +42,7 @@ New-MalwareFilterRule [-Name] -MalwareFilterPolicy [!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 [Anti-malware policies](https://learn.microsoft.com/defender-office-365/anti-malware-protection-about#anti-malware-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-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md index 926d185d37..18d380d7d6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md @@ -46,7 +46,7 @@ Managed content settings are settings that you associate with managed folders to For more information about managed content settings, see [Messaging Records Management](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123507(v=exchg.141)). -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 @@ -55,7 +55,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-ManagedContentSettings -Name "CS-Exec-DeletedItems" -FolderName "Exec-DeletedItems" -MessageClass * -RetentionEnabled $true -RetentionAction DeleteAndAllowRecovery -AgeLimitForRetention 30.00:00:00 -TriggerForRetention WhenDelivered ``` -This example creates managed content settings for the managed default folder Exec-DeletedItems. When added to a managed folder mailbox policy and applied to a mailbox, items in the Deleted Items folder will be permanently deleted 30 days from the date of delivery. +This example creates managed content settings for the managed default folder Exec-DeletedItems. When added to a managed folder mailbox policy and applied to a mailbox, items in the Deleted Items folder are permanently deleted 30 days from the date of delivery. ### Example 2 ```powershell @@ -362,7 +362,7 @@ Valid values include: - WhenDelivered - WhenMoved -This value corresponds to the 0x4 bit of the msExchELCFlags attribute in Active Directory. The flag is set to $true if the item will expire based on the date it was moved and $false if the item will expire based on the delivery date. +This value corresponds to the 0x4 bit of the msExchELCFlags attribute in Active Directory. The flag is set to $true if the item expires based on the date it was moved and $false if the item expires based on the delivery date. If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md index 83bb4f8e24..826712ca3c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md @@ -62,7 +62,7 @@ The New-ManagedFolder cmdlet creates a new managed folder in Active Directory. A By default, managed custom folders are created with this cmdlet. However, you can also create additional copies of managed default folders using the DefaultFolderType parameter to specify which type of default folder to create (for example, an additional Inbox folder). When you create multiple copies of a managed default folder, you can assign different content settings to each one. For example, you could have two Inbox folders, one named InboxSixMonths and another named InboxOneYear. Then, you could assign a retention time of six months to the first folder and one year to the second folder with the New-ManagedContentSettings cmdlet (or using the New Managed Content Settings wizard in the Exchange Management Console). You must assign a unique name (using the Name parameter) to each of the managed default folders that you create. Users, however, always see the unaltered default folder name. In the example, whether users are assigned an InboxSixMonths folder or an InboxOneYear folder, the Inbox that they see in their mailbox is labeled Inbox. Although the folder names that users see in their mailboxes can be reassigned for managed custom folders (using the Set-ManagedFolder command FolderName parameter), the folder names seen by users for managed default folders can't be changed. -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 @@ -305,7 +305,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items may be added. Storage size limits can be specified in kilobytes (KB) or megabytes (MB), for example, 100 KB or 5 MB. +The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items might be added. Storage size limits can be specified in kilobytes (KB) or megabytes (MB), for example, 100 KB or 5 MB. ```yaml Type: Unlimited diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md index f969abf078..5a615b5bc8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md @@ -33,7 +33,7 @@ New-ManagedFolderMailboxPolicy [-Name] ## DESCRIPTION Managed folder mailbox policies are applied to user mailboxes to control message retention 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). Managed custom folders are a premium feature of messaging records management (MRM). Mailboxes with policies that include managed custom folders require an Exchange Server Enterprise client access license (CAL). diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md index 8a9bd82382..fa552a0a5e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md @@ -13,7 +13,7 @@ title: New-ManagementRole # New-ManagementRole ## 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-ManagementRole cmdlet to create a management role based on an existing role or create an unscoped management role. @@ -56,7 +56,7 @@ After you create a role, you can change the management role entries on the role For more information about management roles, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-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 @@ -81,7 +81,7 @@ For more information about pipelining and the Where cmdlet, see the following to New-ManagementRole -Name "In-house scripts" -UnScopedTopLevel ``` -In on-premises Exchange, this example creates the unscoped management role In-house scripts. Note that the UnScopedTopLevel switch requires the Unscoped Role Management role, which isn't assigned to any role group by default. +In on-premises Exchange, this example creates the unscoped management role In-house scripts. The UnScopedTopLevel switch requires the Unscoped Role Management role, which isn't assigned to any role group by default. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md index 49a991694b..1e4c1d0ef6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md @@ -13,7 +13,7 @@ title: New-ManagementRoleAssignment # New-ManagementRoleAssignment ## 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-ManagementRoleAssignment cmdlet to assign a management role to a management role group, management role assignment policy, user, or universal security group (USG). @@ -118,7 +118,7 @@ You can create custom management scopes using the New-ManagementScope cmdlet and For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-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 @@ -138,7 +138,7 @@ New-ManagementRoleAssignment -Role "MyVoiceMail" -Policy "Sales end-users" This example assigns the MyVoiceMail role to the "Sales end-users" role assignment policy. First, the IsEndUserRole property on the MyVoiceMail role is verified to be sure it's set to $true, indicating it's an end-user role. -After the role has been verified to be an end-user role, the role is assigned to the "Sales end-users" role assignment policy. +After the role is verified to be an end-user role, the role is assigned to the "Sales end-users" role assignment policy. ### Example 3 ```powershell @@ -181,7 +181,7 @@ This example assigns the Mail Recipients role to the Contoso Sub - Seattle role > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The Name parameter specifies a name for the new management role assignment. The maximum length of the name is 64 characters. If the management role assignment name contains spaces, enclose the name in quotation marks ("). If you don't specify a name, one will be created automatically. +The Name parameter specifies a name for the new management role assignment. The maximum length of the name is 64 characters. If the management role assignment name contains spaces, enclose the name in quotation marks ("). If you don't specify a name, a name is created automatically. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md index 61f701edc8..7689690822 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md @@ -13,7 +13,7 @@ title: New-ManagementScope # New-ManagementScope ## 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-ManagementScope cmdlet to create a regular or exclusive management scope. @@ -82,7 +82,7 @@ After you create a regular or exclusive scope, you need to associate the scope w For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-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-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md index 631e4cc9bc..2e66284d4f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md @@ -39,7 +39,7 @@ New-MapiVirtualDirectory ``` ## 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 @@ -104,7 +104,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 @@ -124,7 +124,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 @@ -145,8 +145,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-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md index 08169fc9b2..bf7fa10717 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md @@ -13,7 +13,7 @@ title: New-MessageClassification # New-MessageClassification ## 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-MessageClassification cmdlet to create a message classification instance in your organization. @@ -50,7 +50,7 @@ After you create a new message classification, you can specify the message class When you create a message classification, it has no locale. By default, the new message classification is used for all locales. After a default message classification is defined, you can add new locales of the classification by running the New-MessageClassification cmdlet and by specifying the default message classification identity that you want to localize. -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,19 +196,19 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that may be applied to a specified message. Valid values are: +The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that might be applied to a specified message. Valid values are: - Highest - Higher - High - MediumHigh -- Medium (This is the default value) +- Medium (default value) - MediumLow - Low - Lower - Lowest -Although Outlook only lets a user specify a single classification for a message, transport rules may apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter. +Although Outlook only lets a user specify a single classification for a message, transport rules might apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter. ```yaml Type: ClassificationDisplayPrecedenceLevel @@ -250,7 +250,7 @@ Accept wildcard characters: False The PermissionMenuVisible parameter specifies whether the values that you entered for the DisplayName and RecipientDescription parameters are displayed in Outlook as the user composes a message. Valid values are: -- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This is the default value. +- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This value is the default. - $false: Users can't assign the message classification to messages before they're sent, However, messages received with this message classification still display the classification information. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md index ef66847557..e928c46162 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md @@ -13,7 +13,7 @@ title: New-MigrationBatch # New-MigrationBatch ## 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-MigrationBatch cmdlet to submit a new migration request for a batch of users. @@ -454,12 +454,12 @@ Onboarding and offboarding in Exchange Online Both onboarding and offboarding remote move migrations are initiated from your Exchange Online organization. -- Cutover Exchange migration: This is another type of onboarding migration and is used to migrate all mailboxes in an on-premises Exchange organization to Exchange Online. You can migrate a maximum of 1,000 Exchange Server 2003, Exchange Server 2007, or Exchange Server 2010 mailboxes using a cutover migration. Mailboxes will be automatically provisioned in Exchange Online when you perform a cutover Exchange migration. For more information, see Example 5. +- Cutover Exchange migration: This is another type of onboarding migration and is used to migrate all mailboxes in an on-premises Exchange organization to Exchange Online. You can migrate a maximum of 1,000 Exchange Server 2003, Exchange Server 2007, or Exchange Server 2010 mailboxes using a cutover migration. Mailboxes are automatically provisioned in Exchange Online when you perform a cutover Exchange migration. For more information, see Example 5. - Staged Exchange migration: You can also migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online. This is another type of onboarding migration. Migrating mailboxes from Exchange 2010 or later versions of Exchange isn't supported using a staged migration. Prior to running a staged migration, you have to use directory synchronization or some other method to provision mail users in your Exchange Online organization. For more information, see Example 6. - IMAP migration: This onboarding migration type migrates mailbox data from an IMAP server (including Exchange) to Exchange Online. For an IMAP migration, you must first provision mailboxes in Exchange Online before you can migrate mailbox data. For more information, see Example 7. - Google Workspace (formerly G Suite) migration: This onboarding migration type migrates mailbox data from a Google Workspace organization to Exchange Online. For a Google Workspace migration, you must first provision mail users (or mailboxes) in Exchange Online before you can migrate mailbox data. For more information, see Example 10. -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 @@ -470,7 +470,7 @@ New-MigrationBatch -Local -Name LocalMove1 -CSVData ([System.IO.File]::ReadAllBy Start-MigrationBatch -Identity LocalMove1 ``` -This example creates a migration batch for a local move, where the mailboxes in the specified CSV file are moved to a different mailbox database. This CSV file contains a single column with the email address for the mailboxes that will be moved. The header for this column must be named EmailAddress. The migration batch in this example must be started manually by using the Start-MigrationBatch cmdlet or the Exchange admin center. Alternatively, you can use the AutoStart parameter to start the migration batch automatically. +This example creates a migration batch for a local move, where the mailboxes in the specified CSV file are moved to a different mailbox database. This CSV file contains a single column with the email address for the mailboxes to be moved. The header for this column must be named EmailAddress. The migration batch in this example must be started manually by using the Start-MigrationBatch cmdlet or the Exchange admin center. Alternatively, you can use the AutoStart parameter to start the migration batch automatically. ### Example 2 ```powershell @@ -483,7 +483,7 @@ $CrossForestBatch = New-MigrationBatch -Name CrossForestBatch1 -SourceEndpoint $ Start-MigrationBatch -Identity $CrossForestBatch.Identity ``` -This example creates a migration batch for a cross-forest enterprise move, where the mailboxes for the mail users specified in the CSV file are moved to a different forest. A new migration endpoint is created, which identifies the domain where the mailboxes are currently located. The endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. Note that cross-forest moves are initiated from the target forest, which is the forest that you want to move the mailboxes to. +This example creates a migration batch for a cross-forest enterprise move, where the mailboxes for the mail users specified in the CSV file are moved to a different forest. A new migration endpoint is created, which identifies the domain where the mailboxes are currently located. The endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. Cross-forest moves are initiated from the target forest, which is the forest that you want to move the mailboxes to. ### Example 3 ```powershell @@ -496,7 +496,7 @@ $OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $M Start-MigrationBatch -Identity $OnboardingBatch.Identity.Name ``` -This example creates a migration batch for an onboarding remote move migration from an on-premises Exchange organization to Exchange Online. The syntax is similar to that of a cross-forest move, but it's initiated from the Exchange Online organization. A new migration endpoint is created, which points to the on-premises organization as the source location of the mailboxes that will be migrated. This endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. +This example creates a migration batch for an onboarding remote move migration from an on-premises Exchange organization to Exchange Online. The syntax is similar to that of a cross-forest move, but it's initiated from the Exchange Online organization. A new migration endpoint is created, which points to the on-premises organization as the source location of the mailboxes to be migrated. This endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. ### Example 4 ```powershell @@ -555,7 +555,7 @@ $OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $M Start-MigrationBatch -Identity $OnboardingBatch.Identity ``` -This example is the same as Example 3, but the CompleteAfter parameter is also used. Data migration for the batch will start, but won't complete until 09/01/2018 7:00 PM (UTC). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Coordinated Universal Time. +This example is the same as Example 3, but the CompleteAfter parameter is also used. Data migration for the batch starts but doesn't complete until 09/01/2018 7:00 PM (UTC). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Coordinated Universal Time. ### Example 9 ```powershell @@ -568,7 +568,7 @@ $OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $M Start-MigrationBatch -Identity $OnboardingBatch.Identity ``` -This example is the same as Example 8, but the TimeZone parameter is also used. Data migration for the batch will start, but won't complete until 09/01/2018 7:00 PM (PST). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Pacific Standard Time. +This example is the same as Example 8, but the TimeZone parameter is also used. Data migration for the batch starts but doesn't complete until 09/01/2018 7:00 PM (PST). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Pacific Standard Time. ### Example 10 ```powershell @@ -699,7 +699,7 @@ The CSVData parameter specifies the CSV file that contains information about the A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). -**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes that are specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes. +**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes. ```yaml Type: Byte[] @@ -785,8 +785,8 @@ This parameter is available only in on-premises Exchange. The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are: -- $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. This is the default value. -- $false: Incremental synchronization is disabled. The migration batch will go into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization by using the Set-MigrationBatch cmdlet. +- $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. This value is the default. +- $false: Incremental synchronization is disabled. The migration batch goes into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization by using the Set-MigrationBatch cmdlet. ```yaml Type: Boolean @@ -807,7 +807,7 @@ Accept wildcard characters: False The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns in the CSV file that aren't used by migration. Valid values are: - $true: The migration ignores (silently skips) unknown columns in the CSV file (including optional columns with misspelled column headers). All unknown columns are treated like extra columns that aren't used by migration. -- $false: The migration fails if there are any unknown columns in the CSV file.This setting protects against spelling errors in column headers. This is the default value. +- $false: The migration fails if there are any unknown columns in the CSV file.This setting protects against spelling errors in column headers. This value is the default. ```yaml Type: Boolean @@ -973,7 +973,7 @@ The BadItemLimit parameter specifies the maximum number of bad items that are al Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if neither the BadItemLimit or LargeItemLimit parameters are specified, the migration will use Skipped Item approval semantics instead of BadItemLimit semantics. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if neither the BadItemLimit or LargeItemLimit parameters are specified, the migration uses Skipped Item approval semantics instead of BadItemLimit semantics. ```yaml Type: Unlimited @@ -993,14 +993,14 @@ Accept wildcard characters: False This parameter is functional only in the cloud-based service. -The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch will start, but completion won't start until the date/time you specify with this parameter. +The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch starts, but completion doesn't start until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. -- Specify the date/time value in your local time zone: For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. +- Specify the date/time value in your local time zone: For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter. ```yaml Type: DateTime @@ -1041,7 +1041,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service for IMAP migration and Google Workspace migration. -The ContentFilter parameter uses OPATH filter syntax to filter the messages by Received time. Only content that match the ContentFilter parameter will be moved to Exchange online. For example: +The ContentFilter parameter uses OPATH filter syntax to filter the messages by Received time. Only content that matches the ContentFilter parameter is moved to Exchange online. For example: - `"Received -gt '8/23/2020'"` - `"Received -le '2019/01/01'"` @@ -1350,7 +1350,7 @@ For more information about maximum message size values, see the following topics Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -1732,7 +1732,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been replaced by the MoveOptions parameter. +This parameter is replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -1814,7 +1814,7 @@ This parameter is available only in on-premises Exchange. The SkipSteps parameter specifies the steps in the staged Exchange migration that you want to skip. Valid values are: -- None (This is the default value) +- None (default value) - SettingTargetAddress: Don't set the target email address on the source mailbox. This setting prevents mail from being forwarded from the original mailbox to the new migrated mailbox. This parameter is only enforced for staged Exchange migrations. @@ -1878,14 +1878,14 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration will be prepared, but the actual data migration for the user won't start until the date/time you specify with this parameter. +The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration is prepared, but the actual data migration for the user doesn't start until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. -- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. +- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter. ```yaml Type: DateTime @@ -1903,7 +1903,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch will be migrated to. You can use any value that uniquely identifies the database. For example: +The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch are migrated to. You can use any value that uniquely identifies the database. For example: - Name - Distinguished name (DN) @@ -2052,7 +2052,7 @@ Accept wildcard characters: False The WorkflowControlFlags parameter specifies advanced controls for the steps that are performed in the migration. Valid values are: -- None (This is the default value) +- None (default value) - InjectAndForget - SkipSwitchover diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md index b70b95edb7..137f345d59 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md @@ -13,7 +13,7 @@ title: New-MigrationEndpoint # New-MigrationEndpoint ## 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-MigrationEndpoint cmdlet to configure the connection settings for cross-forests moves, remote move migrations, cutover or staged Exchange migrations, IMAP migrations, and Google Workspace (formerly G Suite) migrations. @@ -245,7 +245,7 @@ The New-MigrationEndpoint cmdlet configures the connection settings for differen Moving mailboxes between different servers or databases within a single on-premises Exchange forest (called a local move) doesn't require a migration endpoint. -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 @@ -270,23 +270,23 @@ $Credentials = Get-Credential New-MigrationEndpoint -ExchangeOutlookAnywhere -Name EXCH-AutoDiscover -Autodiscover -EmailAddress administrator@contoso.com -Credentials $Credentials ``` -This example creates an Outlook Anywhere migration endpoint by using the Autodiscover parameter to detect the connection settings to the on-premises organization. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The Get-Credential cmdlet is used to obtain the credentials for an on-premises account that has the necessary administrative privileges in the domain and that can access the mailboxes that will be migrated. When prompted for the user name, you can use either the email address or the domain\\username format for the administrator account. This account can be the same one that is specified by the EmailAddress parameter. +This example creates an Outlook Anywhere migration endpoint by using the Autodiscover parameter to detect the connection settings to the on-premises organization. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The Get-Credential cmdlet is used to obtain the credentials for an on-premises account that has the necessary administrative privileges in the domain and that can access the migrated mailboxes. When prompted for the user name, you can use either the email address or the domain\\username format for the administrator account. This account can be the same one that is specified by the EmailAddress parameter. ### Example 4 ```powershell New-MigrationEndpoint -ExchangeOutlookAnywhere -Name EXCH_Manual -ExchangeServer EXCH-01-MBX.contoso.com -RPCProxyServer EXCH-02-CAS.contoso.com -Credentials (Get-Credential administrator@contoso.com) -EmailAddress annb@contoso.com ``` -This example creates an Outlook Anywhere migration endpoint by specifying the connection settings manually. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The value for the ExchangeServer parameter specifies the on-premises Exchange server that hosts the mailboxes that will be migrated. The value for the RPCProxyServer parameter specifies the Exchange server in the on-premises organization that has the Client Access server role installed that directly accepts and proxies client connections. The EmailAddress parameter can specify any mailbox in the on-premises domain. +This example creates an Outlook Anywhere migration endpoint by specifying the connection settings manually. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The value for the ExchangeServer parameter specifies the on-premises Exchange server that hosts the migrated mailboxes. The value for the RPCProxyServer parameter specifies the Exchange server in the on-premises organization that has the Client Access server role installed that directly accepts and proxies client connections. The EmailAddress parameter can specify any mailbox in the on-premises domain. -It's recommended that you use a migration endpoint created with connection settings that are automatically discovered (see Example 3) because the Autodiscover service will be used to connect to each user mailbox in the migration batch. If you manually specify the connection settings for the endpoint and a user mailbox isn't located on the server specified by the ExchangeServer parameter, the migration for that user will fail. This is important if you have multiple on-premises Outlook Anywhere servers. Otherwise, you may need to create different migration endpoints that correspond to each on-premises server. +We recommend that you use a migration endpoint created with connection settings that are automatically discovered (see Example 3) because the Autodiscover service is used to connect to each user mailbox in the migration batch. If you manually specify the connection settings for the endpoint and a user mailbox isn't located on the server specified by the ExchangeServer parameter, the migration for that user will fail. This is important if you have multiple on-premises Outlook Anywhere servers. Otherwise, you might need to create different migration endpoints that correspond to each on-premises server. ### Example 5 ```powershell New-MigrationEndpoint -IMAP -Name IMAPEndpoint -RemoteServer imap.contoso.com -Port 993 -Security Ssl ``` -This example creates an IMAP migration endpoint. The value for the RemoteServer parameter specifies the FQDN of the IMAP server that hosts the mailboxes that will be migrated. The endpoint is configured to use port 993 for SSL encryption. +This example creates an IMAP migration endpoint. The value for the RemoteServer parameter specifies the FQDN of the IMAP server that hosts the migrated mailboxes. The endpoint is configured to use port 993 for SSL encryption. ### Example 6 ```powershell @@ -592,7 +592,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The RpcProxyServer parameter specifies the FQDN of the Exchange server in the on-premises Exchange organization that has the Client Access server role installed that directly accepts and proxies client connections. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. Typically, this FQDN will be the same as your Outlook on the web URL; for example, mail.contoso.com. This is also the URL for the proxy server that Outlook uses to connect to an Exchange server. +The RpcProxyServer parameter specifies the FQDN of the Exchange server in the on-premises Exchange organization that has the Client Access server role installed that directly accepts and proxies client connections. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. Typically, this FQDN wis the same as your Outlook on the web URL. For example, mail.contoso.com. This is also the URL for the proxy server that Outlook uses to connect to an Exchange server. This parameter is required only when you don't use the Autodiscover parameter. @@ -614,7 +614,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that has been granted access to your remote tenant is created. +The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that is granted access to your remote tenant is created. A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). @@ -777,7 +777,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The ExchangeServer parameter specifies the FQDN of the on-premises Exchange server that hosts the mailboxes that will be migrated. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. +The ExchangeServer parameter specifies the FQDN of the on-premises Exchange server that hosts the migrated mailboxes. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. This parameter is required only when you don't use the Autodiscover parameter. @@ -804,7 +804,7 @@ The MailboxPermission parameter specifies what permissions to use to access the The migration administrator account specified for the endpoint must have one of the following permissions: - Admin: The account is a domain administrator who can access any mailbox they want to migrate. -- FullAccess: The account is assigned either the Full Access permission to the mailboxes they want to migrate or the Receive As permission to the mailbox database that hosts the mailboxes that will be migrated. +- FullAccess: The account is assigned either the Full Access permission to the mailboxes they want to migrate or the Receive As permission to the mailbox database that hosts the migrated mailboxes. If this parameter isn't specified, the cmdlet tries to access source mailboxes using the domain administrator permission and if that fails, it then tries to access the source mailboxes using the Full Access or Receive As permissions. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md index 38821c4cb2..8d609417e7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md @@ -13,7 +13,7 @@ title: New-MobileDeviceMailboxPolicy # New-MobileDeviceMailboxPolicy ## 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-MobileDeviceMailboxPolicy cmdlet to create mobile device mailbox policies. @@ -90,7 +90,7 @@ Some mobile device mailbox policy settings require the mobile device to have cer Some settings in this cmdlet are supported by Outlook for iOS and Android. For more information, see [Leveraging Exchange Online mobile device policies](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/secure-outlook-for-ios-and-android#leveraging-exchange-online-mobile-device-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 @@ -900,7 +900,7 @@ Accept wildcard characters: False The MaxInactivityTimeLock parameter specifies the length of time that the mobile device can be inactive before the password is required to reactivate it. Valid values are: - A timespan: hh:mm:ss, where hh = hours, mm = minutes and ss= seconds. The valid input range is 00:01:00 to 01:00:00 (one minute to one hour). -- The value Unlimited. This is the default value. +- The value Unlimited. This value is the default. ```yaml Type: Unlimited @@ -1017,7 +1017,7 @@ Accept wildcard characters: False The PasswordExpiration parameter specifies how long a password can be used on a mobile device before the user is forced to change the password. Valid values are: - A timespan: ddd.hh:mm:ss, where ddd = days, hh = hours, mm = minutes and ss= seconds. The valid input range is 1.00:00:00 to 730.00:00:00 (one day to two years). -- The value Unlimited. This is the default value +- The value Unlimited. This value is the default ```yaml Type: Unlimited diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md index 315eb64fbe..f6067d134f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md @@ -13,7 +13,7 @@ title: New-MoveRequest # New-MoveRequest ## 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-MoveRequest cmdlet to begin the process of an asynchronous mailbox or personal archive move. You can also check mailbox readiness to be moved by using the WhatIf parameter. @@ -256,7 +256,7 @@ New-MoveRequest [-Identity] -TargetDeliveryDomain ``` ## 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 @@ -561,7 +561,7 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -624,7 +624,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. +The CompletedRequestAgeLimit parameter specifies how long the request are kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. ```yaml Type: Unlimited @@ -707,7 +707,7 @@ Accept wildcard characters: False The ForceOffline switch forces the mailbox move to be performed in offline mode. You don't need to specify a value with this switch. -Moving a mailbox in offline mode means the user will have no access to email during the mailbox move. +Moving a mailbox in offline mode means the user has no access to email during the mailbox move. ```yaml Type: SwitchParameter @@ -789,7 +789,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. This parameter is used together with the CompleteAfter parameter to create a move request that will do periodic incremental syncs after the initial sync is complete. +The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. Use this parameter with the CompleteAfter parameter to create a move request that does periodic incremental syncs after the initial sync is complete. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -842,7 +842,7 @@ Valid input for this parameter is an integer or the value unlimited. The default If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -949,7 +949,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest @@ -1105,7 +1105,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been replaced by the MoveOptions parameter. +This parameter is replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -1174,7 +1174,7 @@ Accept wildcard characters: False The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. -If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. +If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet. ```yaml Type: SwitchParameter @@ -1238,7 +1238,7 @@ The TargetDatabase parameter specifies the destination mailbox database for the - Distinguished name (DN) - GUID -If you don't use this parameter, the automatic distribution logic will select a random database in the Active Directory site where you are running the command. +If you don't use this parameter, the automatic distribution logic selects a random database in the Active Directory site where you are running the command. ```yaml Type: DatabaseIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md index 42c85225eb..1453b4cf91 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md @@ -40,7 +40,7 @@ New-OMEConfiguration [-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 @@ -79,7 +79,7 @@ The BackgroundColor parameter specifies the background color. Valid values are: - An available HTML hexadecimal (hex triplet) color code value (for example, `0x000000` is white). - An available text value (for example, `yellow` is 0x00FFFF00). -- $null (blank). This is the default value. +- $null (blank). This value is the default. For more information, see [Add your organization's brand to your encrypted messages](https://learn.microsoft.com/purview/add-your-organization-brand-to-encrypted-messages). @@ -155,7 +155,7 @@ Accept wildcard characters: False This parameter is available only with a Microsoft 365 Advanced Message Encryption subscription. -The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages will never expire. The default value is 0. +The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages never expire. The default value is 0. In the output of the Get-OMEConfiguration cmdlet, the value of this parameter is displayed in the ExternalMailExpiryInterval property. @@ -175,7 +175,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The Image parameter identifies and uploads an image that will be displayed in the email message and in the Microsoft 365 admin center. +The Image parameter identifies and uploads an image that's displayed in the email message and in the Microsoft 365 admin center. A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). @@ -219,7 +219,7 @@ Accept wildcard characters: False The OTPEnabled parameter specifies whether to allow recipients to use a one-time passcode to view encrypted messages. Valid values are: -- $true: Recipients can use a one-time passcode to view encrypted messages. This is the default value. +- $true: Recipients can use a one-time passcode to view encrypted messages. This value is the default. - $false: Recipients can't use a one-time passcode to view encrypted messages. The recipient is required to sign in using a Microsoft 365 work or school account. ```yaml @@ -294,7 +294,7 @@ Accept wildcard characters: False The SocialIdSignIn parameter specifies whether a user is allowed to view an encrypted message in the Microsoft 365 admin center using their own social network id (Google, Yahoo, etc). Valid values are: -- $true: Social network ID sign in is allowed. This is the default value. +- $true: Social network ID sign in is allowed. This value is the default. - $false: Social network ID sign in is not allowed. Whether the recipient can use a one-time passcode or their Microsoft 365 work or school account is controlled by the OTPEnabled parameter. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md index 6b565f5cfd..e521394787 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md @@ -45,7 +45,7 @@ The New-OABVirtualDirectory cmdlet configures a web distribution point for an OA You have to manually create the file system folder on the server that hosts the OAB files. -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 @@ -107,7 +107,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 @@ -127,7 +127,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 @@ -148,9 +148,9 @@ 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. -- 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. +- 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 fails. 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. @@ -262,7 +262,7 @@ Accept wildcard characters: False The RequireSSL parameter specifies whether the client connection to the virtual directory requires Secure Sockets Layer (SSL) encryption. Valid values are: -- $true: SSL encryption is required to connect to the virtual directory. This is the default value. +- $true: SSL encryption is required to connect to the virtual directory. This value is the default. - $false: SSL encryption isn't required to connect to the virtual directory. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md index d0e3db120c..02ba871661 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md @@ -13,7 +13,7 @@ title: New-OfflineAddressBook # New-OfflineAddressBook ## 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-OfflineAddressBook cmdlet to create offline address books (OABs). @@ -44,7 +44,7 @@ New-OfflineAddressBook [-Name] -AddressLists -HybridDomains ``` ## DESCRIPTION -The OnPremisesOrganization object represents an on-premises Microsoft Exchange organization configured for hybrid deployment with a Microsoft 365 organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. Manual modification of this object may result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization. +The OnPremisesOrganization object represents an on-premises Microsoft Exchange organization configured for hybrid deployment with a Microsoft 365 organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. Manual modification of this object might result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 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 @@ -69,7 +69,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains may be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com". +The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains might be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com". ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md index e18434a74d..976f4da310 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md @@ -13,7 +13,7 @@ title: New-OrganizationRelationship # New-OrganizationRelationship ## 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-OrganizationRelationship cmdlet to create organization relationships. Organization relationships define the settings that are used with external Exchange organizations to access calendar free/busy information or to move mailboxes between on-premises Exchange servers and Exchange Online as part of hybrid deployments. @@ -51,7 +51,7 @@ New-OrganizationRelationship [-Name] -DomainNames ## DESCRIPTION Before you can create an organization relationship, you must first create a federation trust. 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 @@ -131,10 +131,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The ArchiveAccessEnabled parameter specifies whether the organization relationship has been configured to provide remote archive access. Valid values are: +The ArchiveAccessEnabled parameter specifies whether the organization relationship is configured to provide remote archive access. Valid values are: - $true: The external organization provides remote access to mailbox archives. -- $false: The external organization doesn't provide remote access to mailbox archives. This is the default value. +- $false: The external organization doesn't provide remote access to mailbox archives. This value is the default. ```yaml Type: Boolean @@ -176,9 +176,9 @@ Accept wildcard characters: False The DeliveryReportEnabled parameter specifies whether Delivery Reports should be shared over the organization relationship. Valid values are: - $true: Delivery Reports should be shared over the organization relationship. This value means the organization has agreed to share all Delivery Reports with the external organization, and the organization relationship should be used to retrieve Delivery Report information from the external organization. -- $false: Delivery Reports shouldn't be shared over the organization relationship. This is the default value +- $false: Delivery Reports shouldn't be shared over the organization relationship. This value is the default -For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations won't work in either direction. +For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations doesn't work in either direction. ```yaml Type: Boolean @@ -218,7 +218,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable the organization relationship. Valid values are: -- $true: The organization relationship is enabled. This is the default value. +- $true: The organization relationship is enabled. This value is the default. - $false: The organization relationship is disabled. This value completely stops sharing for the organization relationship. ```yaml @@ -240,7 +240,7 @@ Accept wildcard characters: False The FreeBusyAccessEnabled parameter specifies whether the organization relationship should be used to retrieve free/busy information from the external organization. Valid values are: - $true: Free/busy information is retrieved from the external organization. -- $false: Free/busy information isn't retrieved from the external organization. This is the default value. +- $false: Free/busy information isn't retrieved from the external organization. This value is the default. You control the free/busy access level and scope by using the FreeBusyAccessLevel and FreeBusyAccessScope parameters. @@ -339,7 +339,7 @@ Accept wildcard characters: False The MailboxMoveEnabled parameter specifies whether the organization relationship enables moving mailboxes to or from the external organization. Valid values are: - $true: Mailbox moves to or from the external organization are allowed. -- $false: Mailbox moves to or from the external organization aren't allowed. This is the default value. +- $false: Mailbox moves to or from the external organization aren't allowed. This value is the default. ```yaml Type: Boolean @@ -389,7 +389,7 @@ Accept wildcard characters: False The MailTipsAccessEnabled parameter specifies whether MailTips for users in this organization are returned over this organization relationship. Valid values are: - $true: MailTips for users in this organization are returned over the organization relationship. -- $false: MailTips for users in this organization aren't returned over the organization relationship. This is the default value. +- $false: MailTips for users in this organization aren't returned over the organization relationship. This value is the default. You control the MailTips access level by using the MailTipsAccessLevel parameter. @@ -412,8 +412,8 @@ Accept wildcard characters: False The MailTipsAccessLevel parameter specifies the level of MailTips data that's externally shared over this organization relationship. This parameter can have the following values: - All: All MailTips are returned, but the recipients in the remote organization are considered external. For the Auto Reply MailTip, the external Auto Reply message is returned. -- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips won't be returned. -- None: No MailTips are returned to the remote organization. This is the default value. +- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips aren't returned. +- None: No MailTips are returned to the remote organization. This value is the default. This parameter is only meaningful when the MailTipsAccessEnabled parameter value is $true. @@ -509,7 +509,7 @@ Accept wildcard characters: False The PhotosEnabled parameter specifies whether photos for users in the internal organization are returned over the organization relationship. Valid values are: - $true: Photos for users in this organization are returned over the organization relationship. -- $false: Photos for users in this organization aren't returned over the organization relationship. This is the default value. +- $false: Photos for users in this organization aren't returned over the organization relationship. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md index 69dd558e8e..539c5c9b79 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md @@ -47,7 +47,7 @@ New-OutboundConnector [-Name] ## DESCRIPTION Outbound connectors send email messages to 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 @@ -88,7 +88,7 @@ Accept wildcard characters: False The AllAcceptedDomains parameter specifies whether the Outbound connector is used in hybrid organizations where message recipients are in accepted domains of the cloud-based organization. Valid values are: - $true: The Outbound connector is used in hybrid organizations when message recipients are in an accepted domain of the cloud-based organization. This setting requires OnPremises for the ConnectorType value. -- $false: The Outbound connector isn't used in hybrid organizations. This is the default value. +- $false: The Outbound connector isn't used in hybrid organizations. This value is the default. This parameter is effective only for OnPremises connectors. @@ -114,7 +114,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 @@ -174,7 +174,7 @@ Accept wildcard characters: False The ConnectorSource parameter specifies how the connector is created. Valid values are: -- Default: The connector is manually created. This is the default value when you use this cmdlet, and we recommend that you don't change this value. +- Default: The connector is manually created. This value is the default when you use this cmdlet, and we recommend that you don't change this value. - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. @@ -217,7 +217,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable or disable the Outbound 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 @@ -239,7 +239,7 @@ Accept wildcard characters: False The IsTransportRuleScoped parameter specifies whether the Outbound connector is associated with a transport rule (also known as a mail flow rule). Valid values are: - $true: The connector is associated with a transport rule. -- $false: The connector isn't associated with a transport rule. This is the default value. +- $false: The connector isn't associated with a transport rule. This value is the default. You scope a transport rule to an Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. Messages that match the conditions of the transport rule are routed to their destinations by using the specified Outbound connector. @@ -300,7 +300,7 @@ Accept wildcard characters: False The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises email system in hybrid organizations. Valid values are: - $true: Messages are routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. -- $false: Messages aren't routed through the on-premises email system. This is the default value. +- $false: Messages aren't routed through the on-premises email system. This value is the default. This parameter is effective only for OnPremises connectors. @@ -323,7 +323,7 @@ Accept wildcard characters: False The SenderRewritingEnabled parameter specifies that all messages that normally qualify for SRS rewriting are rewritten for routing through the on-premises email system. Valid values are: - $true: Messages are rewritten by SRS as needed before being routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. -- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This is the default value. +- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This value is the default. This parameter is effective only for OnPremises connectors. @@ -372,7 +372,7 @@ Accept wildcard characters: False The TestMode parameter specifies whether you want to enabled or disable test mode for the Outbound connector. Valid values are: - $true: Test mode is enabled. -- $false: Test mode is disabled. This is the default value. +- $false: Test mode is disabled. This value is the default. ```yaml Type: Boolean @@ -417,7 +417,7 @@ The TlsSettings parameter specifies the TLS authentication level that's used for - EncryptionOnly: TLS is used only to encrypt the communication channel. No certificate authentication is performed. - CertificateValidation: TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed. - DomainValidation: In addition to channel encryption and certificate validation, the Outbound connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter. -- $null (blank): This is the default value. +- $null (blank): This value is the default. ```yaml Type: TlsAuthLevel @@ -437,7 +437,7 @@ Accept wildcard characters: False The UseMXRecord parameter enables or disables DNS routing for the connector. Valid values are: -- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This is the default value. +- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This value is the default. - $false: The connector delivers email to one or more smart hosts. This setting requires one or more smart hosts for the SmartHosts value. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md index 264a04ed65..05485cdd9b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md @@ -15,7 +15,7 @@ title: New-OutlookProtectionRule ## SYNOPSIS **Note**: This cmdlet is no longer supported in the cloud-based service. -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-OutlookProtectionRule cmdlet to create a Microsoft Outlook protection rule. @@ -45,7 +45,7 @@ For more information, see [Outlook protection rules](https://learn.microsoft.com Outlook protection rules created without a condition apply to all 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-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md index af0e3feeb6..9e7a811556 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md @@ -32,7 +32,7 @@ New-OutlookProvider [-Name] ## DESCRIPTION The New-OutlookProvider cmdlet creates the AutoDiscoverConfig object under the Global Settings object in Active Directory and sets the attributes specified. -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-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md index 0ea3a13dbb..c0311a932d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md @@ -13,7 +13,7 @@ title: New-OwaMailboxPolicy # New-OwaMailboxPolicy ## 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-OwaMailboxPolicy cmdlet to create Outlook on the web mailbox policies. @@ -33,9 +33,9 @@ New-OwaMailboxPolicy [-Name] ## DESCRIPTION Use the Set-OwaMailboxPolicy cmdlet to configure the new policy. -Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). +Changes to Outlook on the web mailbox policies might take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). -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-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md index 291b08b57f..e051fb1584 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md @@ -45,7 +45,7 @@ New-OwaVirtualDirectory ## DESCRIPTION By default, when Exchange is installed, the Outlook on the web virtual directory owa is created in the default IIS website on the 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 @@ -163,7 +163,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 @@ -183,7 +183,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 @@ -204,8 +204,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 works, 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-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md index f78ea97f86..af5db2924b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md @@ -60,7 +60,7 @@ You can configure partner applications such as Microsoft SharePoint to access Ex We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications. -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 @@ -153,7 +153,7 @@ Accept wildcard characters: False The AccountType parameter specifies the type of Microsoft account that's required for the partner application. Valid values are: -- OrganizationalAccount (This is the default value) +- OrganizationalAccount (default value) - ConsumerAccount ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md index 3edf56b20a..fda8e38416 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md @@ -33,7 +33,7 @@ New-PhishSimOverridePolicy [-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 @@ -50,7 +50,7 @@ This example creates the phishing simulation override policy named PhishSimOverr > Applicable: Exchange Online -The Name parameter specifies the name for the phishing simulation override policy. Regardless of the value you specify, the name will be PhishSimOverridePolicy. +The Name parameter specifies the name for the phishing simulation override policy. Regardless of the value you specify, the name is PhishSimOverridePolicy. ```yaml Type: String @@ -127,7 +127,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-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md index bb9efbeb94..0eb6102ca0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md @@ -13,7 +13,7 @@ title: New-PolicyTipConfig # New-PolicyTipConfig ## 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 Set-PolicyTipConfig cmdlet to create custom Policy Tips in your organization. @@ -30,7 +30,7 @@ New-PolicyTipConfig [-Name] -Value ``` ## 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-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md index 6314ea56c9..b79b93eb6b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md @@ -42,7 +42,7 @@ New-PowerShellVirtualDirectory [-Name] ## DESCRIPTION Although it's possible to create a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. -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 @@ -59,7 +59,7 @@ This example creates a Windows PowerShell virtual directory and configures it to > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Name parameter specifies the name of the new PowerShell virtual directory. The name you provide will have the name of the website it's created under appended to it. If the name you provide contains spaces, enclose the name in quotation marks ("). +The Name parameter specifies the name of the new PowerShell virtual directory. The name you provide has the name of the website it's created under appended to it. If the name you provide contains spaces, enclose the name in quotation marks ("). ```yaml Type: String @@ -140,7 +140,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 @@ -160,7 +160,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 @@ -181,8 +181,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-ProtectionAlert.md b/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md index 1174020b1c..f52a7470fb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md @@ -174,8 +174,8 @@ Accept wildcard characters: False The AggregationType parameter specifies the how the alert policy triggers alerts for multiple occurrences of monitored activity. Valid values are: - None: Alerts are triggered for every occurrence of the activity. -- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This is the default value. -- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). Note that it can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. +- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This value is the default. +- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). It can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. ```yaml Type: AlertAggregationType @@ -332,7 +332,7 @@ Accept wildcard characters: False The Disabled parameter enables or disables the alert policy. Valid values are: - $true: The alert policy is disabled. -- $false: The alert policy is enabled. This is the default value. +- $false: The alert policy is enabled. This value is the default. ```yaml Type: Boolean @@ -479,7 +479,7 @@ Accept wildcard characters: False The NotifyUserOnFilterMatch parameter specifies whether to trigger an alert for a single event when the alert policy is configured for aggregated activity. Valid values are: - $true: Even though the alert is configured for aggregated activity, a notification is triggered during a match for the activity (basically, an early warning). -- $false: Alerts are triggered according to the specified aggregation type. This is the default value. +- $false: Alerts are triggered according to the specified aggregation type. This value is the default. You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). @@ -519,10 +519,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications has been reached in the time period, no more notifications are sent for the alert. Valid values are: +The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications is reached in the time period, no more notifications are sent for the alert. Valid values are: - An integer. -- The value $null. This is the default value (no maximum number of notifications for an alert). +- The value $null. This value is the default (no maximum number of notifications for an alert). ```yaml Type: Int32 @@ -543,7 +543,7 @@ Accept wildcard characters: False The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are: - An integer. -- The value $null. This is the default value (no interval for notification throttling). +- The value $null. This value is the default (no interval for notification throttling). ```yaml Type: Int32 @@ -639,7 +639,7 @@ Accept wildcard characters: False The Severity parameter specifies the severity of the detection. Valid values are: -- Low (This is the default value) +- Low (default value) - Medium - High diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md index 8f7f1f561f..77226a0eca 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md @@ -13,7 +13,7 @@ title: New-PublicFolder # New-PublicFolder ## 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-PublicFolder cmdlet to create a public folder with the specified name. @@ -34,7 +34,7 @@ New-PublicFolder [-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-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md index 4b6ccdc335..a22d12b805 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md @@ -34,7 +34,7 @@ New-PublicFolderDatabase [-Name] -Server ## DESCRIPTION The new database must be mounted after it's created. For more information about mounting databases, see [Mount a Database](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123587(v=exchg.141)). -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-PublicFolderDatabaseRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md index 231d0ed6c1..b7047a7953 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md @@ -35,7 +35,7 @@ Public folders on the public folder database can still be accessed while the req After you begin the repair request, it can't be stopped unless you dismount the database. For more information, see [Dismount a Database](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123903(v=exchg.141)). -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-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md index 6cc054734f..e096e2cdf4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md @@ -50,7 +50,7 @@ New-PublicFolderMigrationRequest [[-Name] ] -SourceDatabase -TargetMailbox ``` ## DESCRIPTION -The New-PublicFolderMoveRequest cmdlet moves public folders from a source public folder mailbox to a target public folder mailbox. While the move request is active, the target public folder mailbox will be locked. As a result, public folders already residing in the target public folder mailbox will be inaccessible until the move request is complete. Therefore, before you begin the move request, you should ensure that no users are accessing public folder data in that target public folder mailbox. +The New-PublicFolderMoveRequest cmdlet moves public folders from a source public folder mailbox to a target public folder mailbox. While the move request is active, the target public folder mailbox is locked. As a result, public folders already residing in the target public folder mailbox are inaccessible until the move request is complete. Therefore, before you begin the move request, you should ensure that no users are accessing public folder data in that target public folder mailbox. To move the public folder mailbox to another mailbox database, use the New-MoveRequest cmdlet. To ensure that this folder is already in the target public folder mailbox, run the Update-PublicFolderMailbox cmdlet against the target public folder mailbox. You can only perform one move request at a time. You can also move public folders by using the Move-PublicFolderBranch.ps1 script. -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 @@ This example moves all public folders from public folder mailbox Pub1 to public > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The Folders parameter specifies the public folders that you want to move. If the public folder has child public folders, these child public folders won't be moved unless you explicitly state them in the command. You can move multiple public folders by separating them with a comma, for example, \\Dev\\CustomerEngagements,\\Dev\\RequestsforChange,\\Dev\\Usability. +The Folders parameter specifies the public folders that you want to move. If the public folder has child public folders, these child public folders aren't moved unless you explicitly state them in the command. You can move multiple public folders by separating them with a comma, for example, \\Dev\\CustomerEngagements,\\Dev\\RequestsforChange,\\Dev\\Usability. ```yaml Type: PublicFolderIdParameter[] @@ -191,7 +191,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has been completed before being automatically removed. The default value for this parameter is 30 days. +The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before being automatically removed. The default value for this parameter is 30 days. ```yaml Type: Unlimited @@ -311,7 +311,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest @@ -360,7 +360,7 @@ Accept wildcard characters: False The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. -If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. +If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md index a5f3e8220a..07e69cfb7f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md @@ -39,7 +39,7 @@ New-QuarantinePermissions ## DESCRIPTION The default value for any parameters that you don't use is $false, so you only need to use parameters (permissions) that you want to set to $true. -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 @@ -79,7 +79,7 @@ In the same PowerShell session, you can use `$FullAccess` for the _EndUserQuaran The PermissionToAllowSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are: - $true: Allow sender is available for affected messages in quarantine. -- $false: Allow sender isn't available for affected messages in quarantine. This is the default value. +- $false: Allow sender isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -100,7 +100,7 @@ Accept wildcard characters: False The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are: - $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine. -- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This is the default value. +- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -121,7 +121,7 @@ Accept wildcard characters: False The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are: - $true: Delete messages and Delete from quarantine are available for affected messages in quarantine. -- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value. +- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -142,7 +142,7 @@ Accept wildcard characters: False The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are: - $true: The permission is enabled. -- $false: The permission is disabled. This is the default value. +- $false: The permission is disabled. This value is the default. Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. End-users can't download quarantined messages. @@ -165,7 +165,7 @@ Accept wildcard characters: False The PermissionToPreview parameter specifies whether users are allowed to preview quarantined messages. Valid values are: - $true: Preview message is available for affected messages in quarantine. -- $false: Preview message isn't available for affected messages in quarantine. This is the default value. +- $false: Preview message isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -232,7 +232,7 @@ Accept wildcard characters: False The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are: - $true: The permission is enabled. -- $false: The permission is disabled. This is the default value. +- $false: The permission is disabled. This value is the default. Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. View message header is always available for affected messages in quarantine. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md index 8a7e07202b..6cfaa0b09b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md @@ -51,7 +51,7 @@ New-QuarantinePolicy [-Name] ## DESCRIPTION Quarantine policies define what users are allowed to do to quarantined messages based on why the message was quarantined (for supported features) and quarantine notification settings. For more information, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-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 @@ -382,7 +382,7 @@ Accept wildcard characters: False The ESNEnabled parameter specifies whether to enable quarantine notifications (formerly known as end-user spam notifications) for the policy. Valid values are: - $true: Quarantine notifications are enabled. -- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This is the default value. +- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This value is the default. **Note**: If the value of this parameter is $true and the value of the EndUserQuarantinePermissionsValue parameter is 0 (No access where all permissions are turned off), users can see their messages in quarantine, but the only available action for the messages is **View message header**. @@ -405,7 +405,7 @@ Accept wildcard characters: False The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send quarantine notifications for quarantined messages from blocked sender addresses. Valid values are: - $true: Recipients get quarantine notifications for affected messages from blocked senders. -- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This is the default value. +- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md index 72b383e6a6..99f534f8f4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md @@ -384,7 +384,7 @@ On Mailbox servers, you can create Receive connectors in the Front End Transport For more information about Receive connector usage types, permission groups, and authentication methods, see [Receive connectors](https://learn.microsoft.com/Exchange/mail-flow/connectors/receive-connectors). -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 @@ -652,7 +652,7 @@ Accept wildcard characters: False The AdvertiseClientSettings parameter specifies whether the SMTP server name, port number, and authentication settings for the Receive connector are displayed to users in the options of Outlook on the web. Valid values are: - $true: The SMTP values are displayed in Outlook on the web. Typically, you would only use this setting for a Receive connector with the usage type Client (authenticated SMTP connections on TCP port 587 for POP3 and IMAP4 clients). -- $false: The SMTP values are displayed in Outlook on the web. This is the default value. +- $false: The SMTP values are displayed in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -704,7 +704,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019 -The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that may be abusing the connection. The default value is 5 seconds. +The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that might be abusing the connection. The default value is 5 seconds. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -752,7 +752,7 @@ Accept wildcard characters: False The BinaryMimeEnabled parameter specifies whether the BINARYMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This is the default value. +- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This value is the default. - $false: BINARYMIME is disabled and isn't advertised in the EHLO response. The binary MIME extension is defined in RFC 3030. @@ -775,7 +775,7 @@ Accept wildcard characters: False The ChunkingEnabled parameter specifies whether the CHUNKING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: CHUNKING is enabled and is advertised in the EHLO response. This is the default value. +- $true: CHUNKING is enabled and is advertised in the EHLO response. This value is the default. - $false: CHUNKING is disabled and isn't advertised in the EHLO response. Chunking is defined in RFC 3030. @@ -896,7 +896,7 @@ This usage type assigns the following default permission groups and authenticati When you use this switch, you also need to use the Bindings and RemoteIPRanges parameters. -If you don't also use the PermissionGroups parameter to assign at least one permission group, you'll need to use the PermissionGroups parameter on the Set-ReceiveConnector cmdlet after you create the Receive connector (otherwise, the Receive connector can't accept inbound SMTP connections). +If you don't also use the PermissionGroups parameter to assign at least one permission group, you need to use the PermissionGroups parameter on the Set-ReceiveConnector cmdlet after you create the Receive connector (otherwise, the Receive connector can't accept inbound SMTP connections). You can't use this switch with any other usage type parameters (Client, Internal, Internet, Partner, or Usage). @@ -946,7 +946,7 @@ Accept wildcard characters: False The DeliveryStatusNotificationEnabled parameter specifies whether the DSN (delivery status notification) Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: DSN is enabled and is advertised in the EHLO response. This is the default value. +- $true: DSN is enabled and is advertised in the EHLO response. This value is the default. - $false: DSN is disabled and isn't advertised in the EHLO response. Delivery status notifications are defined in RFC 3461. @@ -992,7 +992,7 @@ The DomainSecureEnabled parameter specifies whether to enable or disable mutual - $true: Mutual TLS authentication is enabled. - $false: Mutual TLS authentication is disabled. -Note that setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication: +Setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication: - The AuthMechanism parameter must contain the value Tls, and can't contain the value ExternalAuthoritative. - The domain that's used for mutual TLS authentication must be configured in the following locations: @@ -1018,7 +1018,7 @@ Accept wildcard characters: False The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: 8BITMIME is enabled and is advertised in the EHLO response. This is the default value. +- $true: 8BITMIME is enabled and is advertised in the EHLO response. This value is the default. - $false: 8BITMIME is disabled and isn't advertised in the EHLO response. 8-bit data transmission is defined in RFC 6152. @@ -1064,7 +1064,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable or disable the Receive connector. Valid values are: -- $true: The Receive connector is enabled. This is the default value. +- $true: The Receive connector is enabled. This value is the default. - $false: The Receive connector is disabled. ```yaml @@ -1085,7 +1085,7 @@ Accept wildcard characters: False The EnhancedStatusCodesEnabled parameter specifies whether the ENHANCEDSTATUSCODES Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This is the default value. +- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This value is the default. - $false: ENHANCEDSTATUSCODES is disabled and isn't advertised in the EHLO response. Enhanced status codes are defined in RFC 2034. @@ -1108,7 +1108,7 @@ Accept wildcard characters: False The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is implemented on the Receive connector. Valid values are: -- None: Extended Protection for Authentication isn't used. This is the default value. +- None: Extended Protection for Authentication isn't used. This value is the default. - Allow: Extended Protection for Authentication is used only if the connecting host supports it. Otherwise, connections are established without Extended Protection for Authentication. - Require: Extended Protection for Authentication is required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection is rejected. @@ -1158,7 +1158,7 @@ Accept wildcard characters: False The LongAddressesEnabled parameter specifies whether the Receive connector accepts long X.400 email addresses. The X.400 email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. Valid values are - $true: X.400 email addresses can be up to 1,860 characters long after IMCEA encapsulation. -- $false: The maximum length of a complete SMTP email address is 571 characters. This is the default value. +- $false: The maximum length of a complete SMTP email address is 571 characters. This value is the default. When you set this parameter to the value $true, the following changes are made to the Receive connector: @@ -1186,7 +1186,7 @@ Accept wildcard characters: False This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. -The MaxAcknowledgementDelay parameter specifies the maximum period the transport server delays acknowledgment until it verifies that the message has been successfully delivered to all recipients. When receiving messages from a host that doesn't support shadow redundancy, an Exchange Server 2010 transport server will delay issuing an acknowledgment until it verifies that the message has been successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server will time out and issue an acknowledgment anyway. +The MaxAcknowledgementDelay parameter specifies the maximum period the transport server delays acknowledgment until it verifies that the message is successfully delivered to all recipients. When receiving messages from a host that doesn't support shadow redundancy, an Exchange Server 2010 transport server delays issuing an acknowledgment until it verifies that the message is successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server times out and issue an acknowledgment anyway. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1217,7 +1217,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -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. A valid value is from 1 to 2147483647 bytes. @@ -1374,7 +1374,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -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. A valid value for this parameter is from 65536 to 2147483647 bytes. @@ -1488,7 +1488,7 @@ Accept wildcard characters: False The OrarEnabled parameter enables or disables Originator Requested Alternate Recipient (ORAR) on the Receive connector. Valid values are: - $true: ORAR is enabled and is advertised in the XORAR keyword in the EHLO response. The actual ORAR information is transmitted in the RCPT TO SMTP command. -- $false: ORAR is disabled and is isn't advertised in the EHLO response. This is the default value. +- $false: ORAR is disabled and is isn't advertised in the EHLO response. This value is the default. If the email address specified in the ORAR information is a long X.400 email address, you need to set the LongAddressesEnabled parameter to the value $true. @@ -1542,7 +1542,7 @@ Accept wildcard characters: False The PipeliningEnabled parameter specifies whether the PIPELINING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: PIPELINING is enabled and is advertised in the EHLO response. This is the default value. +- $true: PIPELINING is enabled and is advertised in the EHLO response. This value is the default. - $false: PIPELINING is disabled and isn't advertised in the EHLO response. Pipelining is defined in RFC 2920. @@ -1565,7 +1565,7 @@ Accept wildcard characters: False The ProtocolLoggingLevel parameter specifies whether to enable or disable protocol logging for the Receive connector. Valid values are: -- None: Protocol logging is disabled on the Receive connector. This is the default value. +- None: Protocol logging is disabled on the Receive connector. This value is the default. - Verbose: Protocol logging is enabled on the Receive connector. For more information about protocol logging, see [Protocol logging](https://learn.microsoft.com/Exchange/mail-flow/connectors/protocol-logging). @@ -1589,7 +1589,7 @@ Accept wildcard characters: False The RejectReservedSecondLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved second-level domains as specified in RFC 2606 (example.com, example.net, or example.org). Valid value are: - $true: RCPT TO commands that contain reserved second-level domains are rejected. -- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This is the default value. +- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1610,7 +1610,7 @@ Accept wildcard characters: False The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved top-level domains (TLDs) as specified in RFC 2606 (.test, .example, .invalid, or .localhost). Valid value are: - $true: RCPT TO commands that contain reserved TLDs are rejected. -- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This is the default value. +- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1631,7 +1631,7 @@ Accept wildcard characters: False The RejectSingleLabelRecipientDomains parameter specifies whether to reject connections that contain recipients in single-label domains (for example, chris@contoso instead of chris@contoso.com). Valid values are: - $true: RCPT TO commands that contain single-label domains are rejected. -- $false: RCPT TO commands that contain single-label domains aren't rejected. This is the default value. +- $false: RCPT TO commands that contain single-label domains aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1652,7 +1652,7 @@ Accept wildcard characters: False The RequireEHLODomain parameter specifies whether the client must provide a domain name in the EHLO handshake after the SMTP connection is established. Valid values are: - $true: The client must provide a domain name in the EHLO handshake. If it doesn't, the SMTP connection is closed. -- $false: The client isn't required to provide a domain name in the EHLO handshake. This is the default value. +- $false: The client isn't required to provide a domain name in the EHLO handshake. This value is the default. ```yaml Type: Boolean @@ -1673,7 +1673,7 @@ Accept wildcard characters: False The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are: - $true: Inbound messages on the Receive connector require TLS transmission. -- $false: Inbound messages on the Receive connector don't require TLS transmission. This is the default value. +- $false: Inbound messages on the Receive connector don't require TLS transmission. This value is the default. ```yaml Type: Boolean @@ -1736,7 +1736,7 @@ Accept wildcard characters: False The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are: -- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This is the default value. +- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This value is the default. - Disabled: SIZE is disabled and isn't advertised in the EHLO response. - EnabledwithoutValue: SIZE is enabled and is advertised in the EHLO response, but the value of the MaxMessageSize parameter isn't disclosed in the EHLO response. This setting allows messages to bypass message size checks for authenticated connections between Mailbox servers. @@ -1761,7 +1761,7 @@ Accept wildcard characters: False The SuppressXAnonymousTls parameter specifies whether the X-ANONYMOUSTLS Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: X-ANONYMOUSTLS is disabled and isn't advertised in the EHLO response. This setting also requires that you set the UseDownGradedExchangeServerAuth parameter to the value $true on the Set-TransportService cmdlet on the server. -- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This is the default value. +- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This value is the default. The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter contains the value ExchangeServer. @@ -1781,7 +1781,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The TarpitInterval parameter specifies the amount of time to delay an SMTP response to a remote server that may be abusing the connection. The default value is 00:00:05 (5 seconds.). +The TarpitInterval parameter specifies the amount of time to delay an SMTP response to a remote server that might be abusing the connection. The default value is 00:00:05 (5 seconds). 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-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md index 23e939498a..2b47aa2592 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md @@ -13,7 +13,7 @@ title: New-RemoteDomain # New-RemoteDomain ## 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-RemoteDomain cmdlet to create a managed connection for a remote domain. When you create a remote domain, you can control mail flow with more precision, apply message formatting and messaging policies and specify acceptable character sets for messages sent to and received from the remote domain. @@ -30,7 +30,7 @@ New-RemoteDomain [-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 diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md index f82e91d586..ad9e5e75d8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md @@ -158,7 +158,7 @@ Directory synchronization must be configured correctly for a mailbox to be creat The policies that you apply to recipients in the on-premises Exchange organization, such as Unified Messaging or compliance policies, aren't applied to mailboxes in the service. You must configure policies in the service if you want policies to be applied to recipients in the 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 @@ -169,7 +169,7 @@ $Credentials = Get-Credential New-RemoteMailbox -Name "Kim Akers" -Password $Credentials.Password -UserPrincipalName kim@corp.contoso.com ``` -This example creates an on-premises mail user and its associated mailbox in the service. The remote routing address doesn't need to be specified because mail flow between the on-premises organization and the service has been configured. Using this configuration, the New-RemoteMailbox cmdlet automatically calculates the SMTP address of the mailbox to be used with the RemoteRoutingAddress parameter. This example also assumes directory synchronization has been configured. +This example creates an on-premises mail user and its associated mailbox in the service. The remote routing address doesn't need to be specified because mail flow between the on-premises organization and the service is configured. Using this configuration, the New-RemoteMailbox cmdlet automatically calculates the SMTP address of the mailbox to be used with the RemoteRoutingAddress parameter. This example also assumes directory synchronization is configured. The first command stores the password to use with the new remote mailbox in a variable by using the Get-Credential cmdlet. The last command creates the mail user. @@ -577,7 +577,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. @@ -644,7 +644,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. @@ -690,7 +690,7 @@ Accept wildcard characters: False The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are: - $true: The user is required to change their password the next time they log on. -- $false: The user isn't required to change their password the next time they log on. This is the default value. +- $false: The user isn't required to change their password the next time they log on. This value is the default. ```yaml Type: Boolean @@ -708,7 +708,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -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 @@ -728,7 +728,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-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md index b692122c77..ed307ad3f4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md @@ -85,7 +85,7 @@ When you set the email address of the reporting mailbox in the Microsoft Defende - Microsoft integrated reporting using Microsoft reporting tools in Outlook: The ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhishAddresses parameters. - Microsoft integrated reporting using non-Microsoft tools in Outlook: The ThirdPartyReportAddresses parameter. -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 @@ -151,7 +151,7 @@ This example creates the report submission policy with the following values: rep The DisableQuarantineReportingOption parameter allows or prevents users from reporting messages in quarantine. Valid values are: - $true: Users can't report quarantined messages from quarantine. -- $false: Users can report quarantined messages from quarantine. This is the default value. +- $false: Users can report quarantined messages from quarantine. This value is the default. This parameter is meaningful only reporting in Outlook is enabled as described in the EnableReportToMicrosoft parameter. @@ -210,7 +210,7 @@ Accept wildcard characters: False The EnableCustomNotificationSender parameter specifies whether a custom sender email address is used for result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are: - $true: Use a custom Microsoft 365 sender email address. -- $false: Use the default sender email address. This is the default value. +- $false: Use the default sender email address. This value is the default. You specify the sender email address using the NotificationSenderAddress parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md index e15468aa90..277ab07e3d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md @@ -48,7 +48,7 @@ When you set the email address of the reporting mailbox in the Microsoft Defende When you use this cmdlet to set the email address of the reporting mailbox, the corresponding parameters in the *\-ReportSubmissionPolicy cmdlets are not updated. -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 or disabled. 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. After you create the rule, use the Enable-ReportSubmissionRule and Disable-ReportSubmissionRule cmdlets to enable or disable the rule. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md index b7d58bc239..bf34b33313 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md @@ -164,7 +164,7 @@ The Applications parameter specifies the target when Microsoft 365 Groups are in - `Group:Exchange` for the mailbox that's connected to the Microsoft 365 Group. - `Group:SharePoint` for the SharePoint site that's connected to the Microsoft 365 Group. - `"Group:Exchange,SharePoint"` for both the mailbox and the SharePoint site that are connected to the Microsoft 365 Group. -- blank (`$null`): This is the default value, and is functionally equivalent to the value `"Group:Exchange,SharePoint"`. +- blank (`$null`): This value is the default, and is functionally equivalent to the value `"Group:Exchange,SharePoint"`. ```yaml Type: MultiValuedProperty @@ -223,7 +223,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 @@ -523,9 +523,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 content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only ways that you can modify the retention policy are by adding content 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 content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only ways that you can modify the retention policy are by adding content 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 retention 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. @@ -550,7 +550,7 @@ Accept wildcard characters: False The RetainCloudAttachment parameter specifies that this is a cloud attachment policy. Valid values are: - $true: The policy is a cloud attachment policy. -- $false: The policy is not a cloud attachment policy. This is the default value. +- $false: The policy is not a cloud attachment policy. This value is the default. For the value $true, you can only use the following location parameters: diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md index 70672338c9..5744f9b2f0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md @@ -75,14 +75,14 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned New-RetentionComplianceRule -Name InternalCompanyRule -Policy "Internal Company Policy" -RetentionDuration Unlimited ``` -This example creates a new case hold rule named InternalCompanyRule and adds it to the existing case hold policy named "Internal Company Policy". Content will be held indefinitely. +This example creates a new case hold rule named InternalCompanyRule and adds it to the existing case hold policy named "Internal Company Policy". Content is held indefinitely. ### Example 2 ```powershell New-RetentionComplianceRule -Name SeptOneYear -Policy "Internal Company Policy" -RetentionDuration 365 -RetentionComplianceAction KeepAndDelete -ExpirationDateOption ModificationAgeInDays ``` -This example creates a new retention rule named SeptOneYear and adds it to the existing retention policy named "Internal Company Policy". Content will be held for one year from the day content was last modified before it is deleted. +This example creates a new retention rule named SeptOneYear and adds it to the existing retention policy named "Internal Company Policy". Content is held for one year from the day content was last modified before it is deleted. ## PARAMETERS @@ -285,7 +285,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 @@ -296,7 +296,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"`. @@ -428,7 +428,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. You can't use this parameter for Teams retention rules. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md index 68bc9f02ec..e52f0a2909 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md @@ -13,7 +13,7 @@ title: New-RetentionPolicy # New-RetentionPolicy ## 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-RetentionPolicy cmdlet to create a retention policy. @@ -36,7 +36,7 @@ New-RetentionPolicy [-Name] ## DESCRIPTION Retention policy tags are associated with a retention policy. When a retention policy is applied to a mailbox, tags associated with the policy are available to the mailbox user. -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 @@ -125,14 +125,14 @@ This parameter is available only in the cloud-based service. The IsDefault switch specifies that this retention policy is the default retention policy. You don't need to specify a value with this switch. -When you use this switch, you'll get a warning that this retention policy will replace the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy. +When you use this switch, you get a warning that this retention policy replaces the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy. **Note**: Changing which retention policy is the default might or might not affect new and existing mailboxes based on the value of the RetentionPolicy parameter on all mailbox plans: - $null (blank): Changes to which retention policy is the default are continually reflected in new and existing mailboxes. - A retention policy is specified: The value of the RetentionPolicy parameter for all mailbox plans should be $null (blank) or match the Exchange retention policy that's configured as default policy for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. For more information see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans). -If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value. +If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox is overwritten when changing licenses. You need to manually reset the RetentionPolicy to the original value. Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md index f38d4c2f54..cd0aad232e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md @@ -13,7 +13,7 @@ title: New-RetentionPolicyTag # New-RetentionPolicyTag ## 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-RetentionPolicyTag cmdlet to create a retention tag. @@ -72,7 +72,7 @@ Retention tags are used to apply message retention settings to folders and items Retention tags support a display of the tag name and an optional comment in localized languages. Language culture codes from the CultureInfo class are used for this purpose. -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 @@ -88,7 +88,7 @@ This example creates the retention policy tag Finance-DeletedItems for the Delet New-RetentionPolicyTag "Finance-Default" -Type All -RetentionEnabled $true -AgeLimitForRetention 365 -RetentionAction PermanentlyDelete ``` -This example creates the default policy tag Finance-Default. When applied to a mailbox as part of a retention policy, the tag permanently deletes all items without a retention tag within 365 days. Items of a particular message class such as Voicemail, for which a default tag (a retention tag of type All) exists, aren't impacted. +This example creates the default policy tag Finance-Default. When applied to a mailbox as part of a retention policy, the tag permanently deletes all items without a retention tag within 365 days. Items of a particular message class such as Voicemail, for which a default tag (a retention tag of type All) exists, aren't affected. ### Example 3 ```powershell @@ -421,7 +421,7 @@ The RetentionAction parameter specifies the action for the retention policy. Val - DeleteAndAllowRecovery: Deletes a message and allows recovery from the Recoverable Items folder. - MarkAsPastRetentionLimit: Messages are marked as past the retention limit. - MoveToArchive: Moves a message to the user's archive mailbox. You can use this action for retention tags of type All, Personal and RecoverableItems. -- PermanentlyDelete: Permanently deletes a message. A message that has been permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox. +- PermanentlyDelete: Permanently deletes a message. A message that is permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox. The MoveToDeletedItems and MoveToFolder actions are available, but don't work. These actions are available for upgrades from messaging records management (MRM) 1.0 (managed folders) to MRM 2.0 (retention policies). MRM 2.0 was introduced in Exchange 2010 Service Pack 1 (SP1). @@ -447,7 +447,7 @@ The RetentionEnabled parameter specifies whether the tag is enabled. When set to Messages with a disabled tag are still considered tagged, so any tags of the same type as the disabled tag in the user's retention policy aren't applied to such messages. -When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users may apply this tag to items they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later may result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it may be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_`. +When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users might apply this tag to items they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later might result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it might be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_`. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md index d3ed1851f8..fcd51b4f49 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md @@ -13,7 +13,7 @@ title: New-RoleAssignmentPolicy # New-RoleAssignmentPolicy ## 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-RoleAssignmentPolicy cmdlet to create management role assignment policies in your organization. @@ -35,11 +35,11 @@ New-RoleAssignmentPolicy [-Name] ## DESCRIPTION When you create an assignment policy, you can assign it to users using the New-Mailbox, Set-Mailbox, or Enable-Mailbox cmdlets. If you make the new assignment policy the default assignment policy, it's assigned to all new mailboxes that don't have an explicit assignment policy assigned to them. -You can add management roles to the new assignment policy when you create it, or you can create the assignment policy and add roles later. You must assign at least one management role to the new assignment policy for it to apply permissions to a mailbox. Without any roles assigned to the new assignment policy, users assigned to it won't be able to manage their mailbox configuration. To assign a management role after the assignment policy has been created, use the New-ManagementRoleAssignment cmdlet. For more information, see [Manage role assignment policies](https://learn.microsoft.com/Exchange/permissions/role-assignment-policies). +You can add management roles to the new assignment policy when you create it, or you can create the assignment policy and add roles later. You must assign at least one management role to the new assignment policy for it to apply permissions to a mailbox. Without any roles assigned to the new assignment policy, users assigned to it can't manage their mailbox configuration. To assign a management role after the assignment policy is created, use the New-ManagementRoleAssignment cmdlet. For more information, see [Manage role assignment policies](https://learn.microsoft.com/Exchange/permissions/role-assignment-policies). For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-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-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md index c73a9903bb..ac057d2934 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md @@ -13,7 +13,7 @@ title: New-RoleGroup # New-RoleGroup ## 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-RoleGroup cmdlet to create management role groups. @@ -69,7 +69,7 @@ When you create a role group, you can create the group and add members to it dir For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -462,7 +462,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 diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md index 353c3f4107..61483c3359 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md @@ -37,7 +37,7 @@ The New-RoutingGroupConnector cmdlet creates a new routing group connector betwe To create the routing group connector, you must specify the source servers from the originating routing group and the target servers in the destination routing group. The routing group connector is created in the routing group of which the source server is a member. By using the Bidirectional parameter, you can specify whether the connector is used for one-way or two-way mail flow. If you specify a two-way connector, a reciprocal connector is created in the target routing group. The source and target servers must be Exchange 2010 Hub Transport servers or Exchange 2003 bridgehead 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-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md index 0cfc7ea229..a64f68eb70 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md @@ -35,7 +35,7 @@ New-RpcClientAccess -Server ## DESCRIPTION After you run this command, you must start the Exchange RPC Client Access service on the Exchange Client Access server to enable RPC client access. -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-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md index 7830f1bf89..39965ff971 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md @@ -43,7 +43,7 @@ New safe attachment policies that you create using this cmdlet aren't applied to A safe attachment policy can be assigned to only one safe attachment 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 @@ -54,9 +54,9 @@ New-SafeAttachmentPolicy -Name "Marketing Block Attachments" -Enable $true -Redi This example creates a new safe attachment policy named Marketing Block Attachments with the following options: -- The action is Block. This is the default value of the Action parameter, so you don't need to specify it. -- The value $true for the Enable parameter is required so the policy will actually use the default Action parameter value of Block (or any other Action parameter value). -- Enable redirection for detected malware attachments and send the messages to admin@contoso.com. +- The action is Block. This value is the default of the Action parameter, so you don't need to specify it. +- The value $true for the Enable parameter is required so the policy actually uses the default Action parameter value of Block (or any other Action parameter value). +- Enable redirection for detected malware attachments and send the messages to `admin@contoso.com`. - If Safe Attachments scanning isn't available or encounters errors, don't deliver the message as normal. The default value of the ActionOnError parameter is $true, so you don't need to specify it. ## PARAMETERS @@ -86,7 +86,7 @@ Accept wildcard characters: False The Action parameter specifies the action for the safe attachment policy. Valid values are: - Allow: Deliver the message if malware is detected in the attachment and track scanning results. This value corresponds to **Monitor** for the **Safe Attachments unknown malware response** property of the policy in the Microsoft Defender portal. -- Block: Block the email message that contains the malware attachment. This is the default value. +- Block: Block the email message that contains the malware attachment. This value is the default. - DynamicDelivery: Deliver the email message with a placeholder for each email attachment. The placeholder remains until a copy of the attachment is scanned and determined to be safe. For more information, see [Dynamic Delivery in Safe Attachments policies](https://learn.microsoft.com/defender-office-365/safe-attachments-about#dynamic-delivery-in-safe-attachments-policies). The value of this parameter is meaningful only when the value of the Enable parameter is $true (the default value is $false). @@ -153,7 +153,7 @@ Accept wildcard characters: False The Enable parameter works with the Action parameter to specify the action for the safe attachment policy. Valid values are: - $true: The Action parameter specifies the action for the Safe Attachment policy. -- $false: This is the default value. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. This value corresponds to the **Off** selection for the **Safe Attachments unknown malware response** setting of the policy in the Microsoft Defender portal. +- $false: This value is the default. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. This value corresponds to the **Off** selection for the **Safe Attachments unknown malware response** setting of the policy in the Microsoft Defender portal. To enable or disable a complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell), use the Enable-SafeAttachmentRule or Disable-SafeAttachmentRule cmdlets. @@ -240,7 +240,7 @@ Accept wildcard characters: False The Redirect parameter specifies whether to deliver messages to an alternate email address if malware is detected in an attachment. Valid values are: - $true: Messages that contain malware attachments are delivered to the email address specified by the RedirectAddress parameter. This value is meaningful only when the value of the Action parameter is Allow. -- $false: Messages that contain malware attachments aren't delivered to another email address. This is the default value. +- $false: Messages that contain malware attachments aren't delivered to another email address. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md index 31aa541218..2edb57afa5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md @@ -47,7 +47,7 @@ Safe Attachments is a feature in Microsoft Defender for Office 365 that opens em > [!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 [Safe Attachments policy settings](https://learn.microsoft.com/defender-office-365/safe-attachments-about#safe-attachments-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 @@ -153,7 +153,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-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md index 0528b6b005..3ab8987a5c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md @@ -49,7 +49,7 @@ Safe Links is a feature in Microsoft Defender for Office 365 that checks links t 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 SafeLinksPolicy parameter on the New-SafeLinksRule or Set-SafeLinksRule 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 @@ -62,7 +62,7 @@ This example creates a new Safe Links policy named Marketing Block URL with the - The policy is enabled. - Users aren't allowed to click through to the original URL. -- User clicks on URLs are tracked. This is the default value of the TrackClicks parameter, so you don't need to specify it. +- User clicks on URLs are tracked. This value is the default of the TrackClicks parameter, so you don't need to specify it. ## PARAMETERS @@ -170,7 +170,7 @@ Accept wildcard characters: False The DeliverMessageAfterScan parameter specifies whether to deliver email messages only after Safe Links scanning is complete. Valid values are: -- $true: Wait until Safe Links scanning is complete before delivering the message. Messages that contain malicious links are not delivered. This is the default value. +- $true: Wait until Safe Links scanning is complete before delivering the message. Messages that contain malicious links are not delivered. This value is the default. - $false: If Safe Links scanning can't complete, deliver the message anyway. ```yaml @@ -192,7 +192,7 @@ Accept wildcard characters: False The DisableUrlRewrite parameter specifies whether to rewrite (wrap) URLs in email messages. Valid values are: - $true: URLs in messages are not rewritten, but messages are still scanned by Safe Links prior to delivery. Time of click checks on links are done using the Safe Links API in supported Outlook clients (currently, Outlook for Windows and Outlook for Mac). -- $false: URLs in messages are rewritten. API checks still occur on unwrapped URLs in supported clients if the user is in a valid Safe Links policy. This is the default value. +- $false: URLs in messages are rewritten. API checks still occur on unwrapped URLs in supported clients if the user is in a valid Safe Links policy. This value is the default. In PowerShell, the default value is $false. In new Safe Links policies created in the Microsoft Defender portal, the default value is $true. @@ -238,7 +238,7 @@ Accept wildcard characters: False The EnableForInternalSenders parameter specifies whether the Safe Links policy is applied to messages sent between internal senders and internal recipients within the same Exchange Online organization. Valid values are: -- $true: The policy is applied to internal and external senders. This is the default value. +- $true: The policy is applied to internal and external senders. This value is the default. - $false: The policy is applied only to external senders. ```yaml @@ -260,7 +260,7 @@ Accept wildcard characters: False The EnableOrganizationBranding parameter specifies whether your organization's logo is displayed on Safe Links warning and notification pages. Valid values are: - $true: Organization branding is displayed on Safe Links warning and notification pages. Before you configure this value, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your company logo. -- $false: Organization branding is not displayed on Safe Links warning and notification pages. This is the default value. +- $false: Organization branding is not displayed on Safe Links warning and notification pages. This value is the default. ```yaml Type: Boolean @@ -280,7 +280,7 @@ Accept wildcard characters: False The EnableSafeLinksForEmail parameter specifies whether to enable Safe Links protection for email messages. Valid values are: -- $true: Safe Links is enabled for email. This is the default value. When a user clicks a link in an email, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links is enabled for email. This value is the default. When a user clicks a link in an email, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for email. ```yaml @@ -301,10 +301,10 @@ Accept wildcard characters: False The EnableSafeLinksForOffice parameter specifies whether to enable Safe Links protection for supported Office desktop, mobile, or web apps. Valid values are: -- $true: Safe Links scanning is enabled in Office apps. This is the default value. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links scanning is enabled in Office apps. This value is the default. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for Office apps. -Note that this protection applies to links in Office documents, not links in email messages. +This protection applies to links in Office documents, not links in email messages. ```yaml Type: Boolean @@ -324,7 +324,7 @@ Accept wildcard characters: False The EnableSafeLinksForTeams parameter specifies whether Safe Links is enabled for Microsoft Teams. Valid values are: -- $true: Safe Links is enabled for Teams. This is the default value. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links is enabled for Teams. This value is the default. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for Teams. ```yaml @@ -381,7 +381,7 @@ Accept wildcard characters: False The ScanUrls parameter specifies whether to enable or disable real-time scanning of clicked links in email messages. Valid values are: -- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This is the default value. +- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This value is the default. - $false: Real-time scanning of clicked links, including links that point to files, is disabled. ```yaml @@ -402,7 +402,7 @@ Accept wildcard characters: False The TrackClicks parameter specifies whether to track user clicks related to Safe Links protection of links. Valid values are: -- $true: User clicks messages are tracked. This is the default value. +- $true: User clicks messages are tracked. This value is the default. - $false: User clicks messages aren't tracked. ```yaml @@ -424,7 +424,7 @@ Accept wildcard characters: False The UseTranslatedNotificationText specifies whether to use Microsoft Translator to automatically localize the custom notification text that you specified with the CustomNotificationText parameter. Valid values are: - $true: Translate custom notification text to the user's language. -- $false: Don't translate custom notification text to the user's language. This is the default value. +- $false: Don't translate custom notification text to the user's language. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md index f0bcda85ea..b097258420 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md @@ -45,7 +45,7 @@ Safe Links is a feature in Microsoft Defender for Office 365 that checks links i > [!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 [Recipient filters in Safe Links policies](https://learn.microsoft.com/defender-office-365/safe-links-about#recipient-filters-in-safe-links-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 @@ -176,7 +176,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-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md index bc6b60fcfa..4396c8006d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md @@ -31,9 +31,11 @@ New-SearchDocumentFormat [-Identity] -Extension -SentTo ``` ## 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 @@ -50,7 +50,7 @@ This example creates the SecOps mailbox override policy with the specified setti > Applicable: Exchange Online -The Name parameter specifies the name for the SecOps mailbox override policy. Regardless of the value you specify, the name will be SecOpsOverridePolicy. +The Name parameter specifies the name for the SecOps mailbox override policy. Regardless of the value you specify, the name is SecOpsOverridePolicy. ```yaml Type: String @@ -147,7 +147,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-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md index 25a2ec45c2..c200e2ff41 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md @@ -106,7 +106,7 @@ New-SendConnector [-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 @@ -161,7 +161,7 @@ Accept wildcard characters: False The AddressSpaces parameter specifies the domain names to which the Send connector routes mail. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`. -- AddressSpaceType: On an Edge server, the address space type must be SMTP. In the Transport service on a Mailbox server, the address space type may be SMTP, X400, or any other text string. If you omit the address space type, SMTP is assumed. +- AddressSpaceType: On an Edge server, the address space type must be SMTP. In the Transport service on a Mailbox server, the address space type might be SMTP, X400, or any other text string. If you omit the address space type, SMTP 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 is not. 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 address space 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. This parameter is optional. 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. @@ -172,7 +172,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, 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, enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3". If you specify a non-SMTP address space type on a Send connector configured in the Transport service on a Mailbox server, you must configure the following parameters: @@ -223,7 +223,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 @@ -305,7 +305,7 @@ Accept wildcard characters: False The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Microsoft 365. Valid values are: -- Default: The connector isn't used to send messages to Microsoft 365. This is the default value. +- Default: The connector isn't used to send messages to Microsoft 365. This value is the default. - XPremises: The connector is used to send messages to Microsoft 365. ```yaml @@ -698,7 +698,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. Values entered in bytes are rounded up to nearest kilobyte. The valid input range for this parameter is 0 to 2147483647 bytes. To remove the message size limit on a Send connector, enter a value of unlimited. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md index 57d018af70..6189996d80 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md @@ -36,7 +36,7 @@ Service principals exist in Microsoft Entra ID to define what apps can do, who c For more information, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals). -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-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md index 7ed4d11a9f..cbecf3513b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md @@ -38,7 +38,7 @@ New-SettingOverride [-Name] -Component -Parameters -Domains ``` ## 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 @@ -132,7 +132,7 @@ Accept wildcard characters: False The Default switch specifies that this sharing policy is the default sharing policy for all mailboxes. You don't need to specify a value with this switch. -If no sharing policy has been applied to a mailbox, the default policy is automatically applied. If you want to disable sharing across your organization, you can set the default policy as disabled. +If no sharing policy is applied to a mailbox, the default policy is automatically applied. If you want to disable sharing across your organization, you can set the default policy as disabled. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md index 6519e1a622..6d87b66bcf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md @@ -38,7 +38,7 @@ New-SiteMailbox [[-DisplayName] ] -SharePointUrl ``` ## 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-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md index 1c8207891f..78730144a7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md @@ -40,7 +40,7 @@ New-SiteMailboxProvisioningPolicy [-Name] ## DESCRIPTION Site mailboxes allow access to both Microsoft SharePoint documents and Exchange email using the same client interface. Site mailbox provisioning policies apply settings to new site mailboxes that you create. You can create multiple site mailbox provisioning policies, but only the default policy is followed when users create site mailboxes. The default site mailbox provisioning policy is named Default. -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 @@ -96,7 +96,7 @@ Accept wildcard characters: False The AliasPrefix parameter specifies the custom text prefix to add to the aliases of new site mailboxes. Valid values are: - A text string that's 8 characters or less. When you specify a text value, the value of the DefaultAliasPrefixEnabled parameter ignored and aliases get the text prefix you specified. -- The value $null. This is the default value. The results of this value depend on the DefaultAliasPrefixEnabled parameter value. When it's $true, aliases get the default prefix text. When it's $false, aliases don't get any prefix text. +- The value $null. This value is the default. The results of this value depend on the DefaultAliasPrefixEnabled parameter value. When it's $true, aliases get the default prefix text. When it's $false, aliases don't get any prefix text. ```yaml Type: String @@ -137,7 +137,7 @@ Accept wildcard characters: False The DefaultAliasPrefixEnabled parameter specifies whether new site mailboxes have the default prefix text added to the alias. Valid values are: -- $true: Aliases get the default prefix text. This is the default value. In Microsoft 365, the default prefix text is `SMO-` (for example, the alias value `BugBash_2016` becomes `SMO-BugBash_2016`). In on-premises Exchange, the default prefix text is `SM-` (for example, the alias value `BugBash_2016` becomes `SM-BugBash_2016`). +- $true: Aliases get the default prefix text. This value is the default. In Microsoft 365, the default prefix text is `SMO-` (for example, the alias value `BugBash_2016` becomes `SMO-BugBash_2016`). In on-premises Exchange, the default prefix text is `SM-` (for example, the alias value `BugBash_2016` becomes `SM-BugBash_2016`). - $false: Aliases don't get the default prefix text. The value of this parameter is related to the value of the AliasPrefix parameter. If you specify a text string for AliasPrefix, the DefaultAliasPrefixEnabled value is ignored. Specifying a text value for AliasPrefix automatically sets the value to $false, but even if you set it to $true, the default alias prefix text isn't used. @@ -206,7 +206,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - 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 IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. @@ -237,7 +237,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -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. A valid value is a number up to 1.999999 gigabytes (2147482624 bytes) or the value unlimited. The default value is 36 MB. @@ -267,7 +267,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - 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 must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md index 8b8cb8b880..a0e63f4d33 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md @@ -13,7 +13,7 @@ title: New-SweepRule # New-SweepRule ## 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-SweepRule cmdlet to create Sweep rules in mailboxes. Sweep rules run at regular intervals to help keep your Inbox clean. @@ -40,7 +40,7 @@ New-SweepRule [-Name] -Provider ``` ## 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 @@ -184,7 +184,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the Sweep rule is enabled or disabled. 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. After you create the rule, you can enable or disable it by using the Enable-SweepRule and Disable-SweepRule cmdlets. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md index 41a1745507..8c39847c58 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md @@ -13,7 +13,7 @@ title: New-SyncMailPublicFolder # New-SyncMailPublicFolder ## 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. The New-SyncMailPublicFolder cmdlet is used by the Import-MailPublicFoldersForMigration.ps1 and Sync-MailPublicFolders.ps1 scripts to create mail-enabled public folder recipient objects in Exchange Online (the scripts synchronize mail-enabled public folder objects from the source on-premises Exchange organization to Exchange Online). Don't use this cmdlet unless you are directed to do so by Microsoft Customer Service and Support or by specific documentation. @@ -63,7 +63,7 @@ New-SyncMailPublicFolder [-Name] [-Alias] -EntryId ## DESCRIPTION This cmdlet is only used by the Import-MailPublicFoldersForMigration.ps1 and Sync-MailPublicFolders.ps1 scripts. Don't run this cmdlet in the Exchange Management Shell or in Exchange Online PowerShell. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -510,7 +510,7 @@ Accept wildcard characters: False The DeliverToMailboxAndForward parameter specifies the message delivery behavior when a forwarding address is specified by the ForwardingAddress parameter. Valid values are: - $true: Messages are delivered to this mail-enabled public folder and forwarded to the specified recipient or email address. -- $false: If a forwarding recipient is configured, messages are delivered only to the specified recipient, and messages aren't delivered to this mail-enabled public folder. If no forwarding recipient is configured, messages are delivered only to this mailbox. This is the default value. +- $false: If a forwarding recipient is configured, messages are delivered only to the specified recipient, and messages aren't delivered to this mail-enabled public folder. If no forwarding recipient is configured, messages are delivered only to this mailbox. This value is the default. The default value is $false. This parameter is meaningful only if you configure a forwarding recipient by using the ForwardingAddress parameter. @@ -711,7 +711,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -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. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -742,7 +742,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -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. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md index 66b63211c0..5f57d4f5d4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md @@ -42,7 +42,7 @@ New-SystemMessage -Language -QuotaMessageType - ## DESCRIPTION NDRs are issued to the senders of email messages that haven't reached their intended recipients. Quota messages are issued to users whose mailboxes or public folders have reached the specific warning, prohibit send, or prohibit receive quotas. Custom NDRs and quota messages replace the default messages that are included with 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 @@ -205,7 +205,7 @@ The following HTML tags are available: - `` and `` (italic) - `
` (line break) - `

` and `

` (paragraph) -- `` and `` (hyperlink). **Note**: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you'll receive an error (because of the double quotation marks in the tag). +- `` and `` (hyperlink). **Note**: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you get an error (because of the double quotation marks in the tag). Use the following escape codes for these special characters: diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md index bfee67b53a..0968adb205 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md @@ -35,7 +35,7 @@ New-TeamsProtectionPolicy [-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 @@ -184,7 +184,7 @@ Accept wildcard characters: False The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware and high confidence phishing messages in Teams messages. Valid values are: -- $true: ZAP for malware and high confidence phishing messages in Teams is enabled. This is the default value. +- $true: ZAP for malware and high confidence phishing messages in Teams is enabled. This value is the default. - $false: ZAP for malware and high confidence phishing messages in Teams is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md index e9a52ab70d..dae92b700a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md @@ -45,7 +45,7 @@ You can use this cmdlet only if the following statements are true: > [!IMPORTANT] > Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Configure ZAP for Teams protection in Defender for Office 365 Plan 2](https://learn.microsoft.com/defender-office-365/mdo-support-teams-about#configure-zap-for-teams-protection-in-defender-for-office-365-plan-2). -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-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md index 0c72896810..f4de39cad9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md @@ -50,7 +50,7 @@ New-TenantAllowBlockListItems -Entries -ListType [-NoExpir ``` ## 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 @@ -254,7 +254,7 @@ Accept wildcard characters: False The ListSubType parameter specifies the subtype for this entry. Valid values are: - AdvancedDelivery: Use this value for phishing simulation URLs. For more information, see [Configure the advanced delivery policy for non-Microsoft phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). -- Tenant: This is the default value. +- Tenant: This value is the default. ```yaml Type: ListSubType diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md index dcb4b1d95f..049fb245fe 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md @@ -31,7 +31,7 @@ New-TenantAllowBlockListSpoofItems [-Identity] Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter isn't used and will be removed. +This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited @@ -880,7 +880,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search will run before it times out. +The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search runs before it times out. ```yaml Type: Unlimited @@ -1008,7 +1008,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships will remain active. By default, there is no limit to the number of days that a user's device partnerships will remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed. +The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships remain active. By default, there is no limit to the number of days that a user's device partnerships remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed. ```yaml Type: Unlimited @@ -2168,7 +2168,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter won't affect Exchange admin center operations or Exchange Web Services operations. +The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter doesn't affect Exchange admin center operations or Exchange Web Services operations. ```yaml Type: UInt32 @@ -2245,7 +2245,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets may help prevent accidental data loss. The following cmdlets are designated as destructive: +The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets might help prevent accidental data loss. The following cmdlets are designated as destructive: - Disable-Mailbox - Move-ActiveMailboxDatabase @@ -2293,7 +2293,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling may occur. The default setting is Unlimited. +The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling might occur. The default setting is Unlimited. ```yaml Type: Unlimited diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md index 930b4c4913..465d011257 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md @@ -13,7 +13,7 @@ title: New-TransportRule # New-TransportRule ## 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-TransportRule cmdlet to create transport rules (mail flow rules) in your organization. @@ -211,9 +211,9 @@ New-TransportRule [-Name] ## DESCRIPTION In on-premises Exchange organizations, rules created on Mailbox servers are stored in Active Directory. All Mailbox servers in the organization have access to the same set of rules. On Edge Transport servers, rules are saved in the local copy of Active Directory Lightweight Directory Services (AD LDS). Rules aren't shared or replicated between Edge Transport servers or between Mailbox servers and Edge Transport servers. Also, some conditions and actions are exclusive to each server role. -The search for words or text patterns in the subject or other header fields in the message occurs after the message has been decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You can't use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields in messages. +The search for words or text patterns in the subject or other header fields in the message occurs after the message is decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You can't use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields 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 @@ -226,7 +226,7 @@ This example creates a rule with the following settings: - Name: Ethical Wall - Sales and Brokerage Departments - Conditions: Messages that are sent between members of the groups named Sales Department and Brokerage Department. -- Actions: The message is rejected, and the custom rejection text is Messages sent between the Sales and Brokerage departments are strictly prohibited. Note that the default enhanced status code 5.7.1 is used, because we didn't use the RejectMessageEnhancedStatusCode parameter. +- Actions: The message is rejected, and the custom rejection text is Messages sent between the Sales and Brokerage departments are strictly prohibited. The default enhanced status code 5.7.1 is used, because we didn't use the RejectMessageEnhancedStatusCode parameter. - Exceptions: The Subject field contains the phrases Press Release or Corporate Communication or the message was sent by Tony Smith or Pilar Ackerman. ## PARAMETERS @@ -253,7 +253,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The ActivationDate parameter specifies when the rule starts processing messages. The rule won't take any action on messages until the specified date/time. +The ActivationDate parameter specifies when the rule starts processing messages. The rule doesn't take any action on messages until the specified date/time. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". @@ -333,7 +333,7 @@ In on-premises Exchange, this condition is available only on Mailbox servers. The ADComparisonOperator parameter specifies the comparison operator for the ADComparisonAttribute parameter. Valid values are: -- Equal (This is the default value) +- Equal (default value) - NotEqual ```yaml @@ -704,7 +704,7 @@ In on-premises Exchange, this action is available only on Mailbox servers. The ApplyHtmlDisclaimerFallbackAction parameter specifies what to do if the HTML disclaimer can't be applied to a message (for example, encrypted or signed messages where the contents can't be altered). Valid values are: -- Wrap: This is the default value. A new message is created and the original message is added to it as an attachment. The disclaimer text is added to the new message, which is delivered to the recipients. +- Wrap: This value is the default. A new message is created and the original message is added to it as an attachment. The disclaimer text is added to the new message, which is delivered to the recipients. If you want other rules to examine and act on the original message (which is now an attachment in the new message), make sure those rules are applied _before_ the disclaimer rule by using a lower priority for the disclaimer rule and higher priority for other rules. @@ -739,7 +739,7 @@ In on-premises Exchange, this action is available only on Mailbox servers. The ApplyHtmlDisclaimerLocation parameter specifies where to insert the HTML disclaimer text in the body of messages. Valid values are: -- Append: The disclaimer is added to the end of the message body. This is the default value. +- Append: The disclaimer is added to the end of the message body. This value is the default. - Prepend: The disclaimer is inserted at the beginning of the message body. If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the default value Append is used. @@ -1148,9 +1148,9 @@ 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 embedded images are treated as attachments (for example, messages with a picture in the signature); for this reason, we do not recommend using a very small value since unexpected messages will be blocked. +The embedded images are treated as attachments (for example, messages with a picture in the signature); for this reason, we do not recommend using a very small value since unexpected messages are blocked. ```yaml Type: ByteQuantifiedSize @@ -1449,7 +1449,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the new rule is created as enabled or disabled. Valid values are: -- $true: The new rule is enabled. This is the default value. +- $true: The new rule is enabled. This value is the default. - $false: The new rule is disabled. To enable or disable a rule after you create it, use the Enable-TransportRule and Disable-TransportRule cmdlets. @@ -1530,7 +1530,7 @@ In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfADComparisonOperator parameter specifies the comparison operator for the ExceptIfADComparisonAttribute parameter. Valid values are: -- Equal (This is the default value) +- Equal (default value) - NotEqual ```yaml @@ -2072,7 +2072,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. ```yaml Type: ByteQuantifiedSize @@ -2593,7 +2593,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. ```yaml Type: ByteQuantifiedSize @@ -2618,7 +2618,7 @@ In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfMessageTypeMatches parameter specifies an exception that looks for messages of the specified type. Valid values are: - OOF: Auto-reply messages configured by the user. -- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this exception **will not** match during mail flow rule evaluation. +- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message is forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this exception **does not** match during mail flow rule evaluation. - Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported. - Calendaring: Meeting requests and responses. - PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption). @@ -3300,7 +3300,7 @@ Accept wildcard characters: False This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. -The ExpiryDate parameter specifies when this rule will stop processing messages. The rule won't take any action on messages after the specified date/time. +The ExpiryDate parameter specifies when this rule stops processing messages. The rule doesn't take any action on messages after the specified date/time. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". @@ -3706,10 +3706,10 @@ In on-premises Exchange, this action is available only on Mailbox servers. The IncidentReportContent parameter specifies the message properties that are included in the incident report. Valid values are: - Sender: The sender of the message. -- Recipients: The recipients in the To field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. +- Recipients: The recipients in the To field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients are displayed. - Subject: The Subject field of the message. -- CC: The recipients in the Cc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. -- BCC: The recipients in the Bcc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. +- CC: The recipients in the Cc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients are displayed. +- BCC: The recipients in the Bcc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients are displayed. - Severity: The audit severity of the rule that was triggered. If the message was processed by more than one rule, the highest severity is displayed. - RuleDetections: The list of rules that the message triggered. - FalsePositive: The false positive if the sender marked the message as a false positive for a PolicyTip. @@ -3740,13 +3740,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2013. -This parameter has been deprecated and is no longer used. Use the IncidentReportContent parameter instead. The value AttachOriginalMail on the IncidentReportContent parameter is equivalent to setting this parameter to the value IncludeOriginalMail. +This parameter is deprecated and no longer used. Use the IncidentReportContent parameter instead. The value AttachOriginalMail on the IncidentReportContent parameter is equivalent to setting this parameter to the value IncludeOriginalMail. This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. -The IncidentReportOriginalMail parameter specifies whether to include the original message with the incident report. This parameter is used together with the GenerateIncidentReport parameter. Valid values are: +The IncidentReportOriginalMail parameter specifies whether to include the original message with the incident report. Use this parameter with the GenerateIncidentReport parameter. Valid values are: - IncludeOriginalMail - DoNotIncludeOriginalMail (this is the default value) @@ -3901,7 +3901,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. ```yaml Type: ByteQuantifiedSize @@ -3926,7 +3926,7 @@ In on-premises Exchange, this condition is available only on Mailbox servers. The MessageTypeMatches parameter specifies a condition that looks for messages of the specified type. Valid values are: - OOF: Auto-reply messages configured by the user. -- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this condition **will not** match during mail flow rule evaluation. +- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message is forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this condition **does not** match during mail flow rule evaluation. - Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported. - Calendaring: Meeting requests and responses. - PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption). @@ -3953,9 +3953,9 @@ Accept wildcard characters: False The Mode parameter specifies how the rule operates. Valid values are: -- Audit: The actions that the rule would have taken are written to the message tracking log, but no action that impacts message delivery is taken on the message. The GenerateIncidentReport action occurs. -- AuditAndNotify: The actions that the rule would have taken are written to the message tracking log, but no action that impacts message delivery is taken on the message. The GenerateIncidentReport and GenerateNotification actions occur. -- Enforce: All actions specified in the rule are taken. This is the default value. +- Audit: The actions that the rule would have taken are written to the message tracking log, but no action that affects message delivery is taken on the message. The GenerateIncidentReport action occurs. +- AuditAndNotify: The actions that the rule would have taken are written to the message tracking log, but no action that affects message delivery is taken on the message. The GenerateIncidentReport and GenerateNotification actions occur. +- Enforce: All actions specified in the rule are taken. This value is the default. ```yaml Type: RuleMode @@ -4051,7 +4051,7 @@ For all values except NotifyOnly, you can specify an enhanced status code and a If you use this parameter, you also need to specify a condition that looks for sensitive information types in messages by using the MessageContainsDataClassifications parameter. -This action is applicable to messages sent by internal users only. External senders will not receive notifications. +This action is applicable to messages sent by internal users only. External senders don't receive notifications. ```yaml Type: NotifySenderType @@ -4311,7 +4311,7 @@ This parameter is available only in the cloud-based service. The RecipientAddressType parameter specifies how conditions and exceptions check recipient email addresses. Valid values are: - Original: The rule checks the original address in the To field of the message. -- Resolved: The rule checks the recipient's primary SMTP email address without checking any proxy addresses. This is the default value. +- Resolved: The rule checks the recipient's primary SMTP email address without checking any proxy addresses. This value is the default. ```yaml Type: RecipientAddressType @@ -4616,7 +4616,7 @@ Accept wildcard characters: False The RuleErrorAction parameter specifies what to do if rule processing can't be completed on messages. Valid values are: -- Ignore: The message is sent anyway. This is the default value. +- Ignore: The message is sent anyway. This value is the default. - Defer: The message is deferred so the rules engine can attempt to process the message again. ```yaml @@ -4638,7 +4638,7 @@ Accept wildcard characters: False The RuleSubType parameter specifies the rule type. Valid values are: - Dlp: The rule is associated with a DLP policy. This value is meaningful only in on-premises Exchange. -- None: The rule is a regular transport rule. This is the default value. +- None: The rule is a regular transport rule. This value is the default. ```yaml Type: RuleSubType @@ -4799,7 +4799,7 @@ 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, in on-premises Exchange the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This is the default value, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1). +- Header: Only examine senders in the message headers. For example, in on-premises Exchange the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This value is the default, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1). - 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. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md index 1ce66f96fd..dbd81be6da 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md @@ -38,7 +38,7 @@ The New-UMAutoAttendant cmdlet creates one or more UM auto attendants. UM auto a After this task is completed, a UM auto attendant is created. -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 @@ -191,10 +191,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -The Status parameter specifies whether the UM auto attendant being created will be enabled. Valid values are: +The Status parameter specifies whether the UM auto attendant is enabled. Valid values are: - Enabled -- Disabled (This is the default value) +- Disabled (default value) ```yaml Type: StatusEnum diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md index b90838c318..4c24b04506 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md @@ -54,7 +54,7 @@ You can also specify the following actions: After this task is completed, the cmdlet sets the parameters and the values specified. -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 @@ -93,10 +93,10 @@ This example creates the call answering rule MyCallAnsweringRule in the mailbox - Sets the priority of the call answering rule to 2. - Creates key mappings for the call answering rule. -If the caller reaches the voice mail for the user and the status of the user is set to Busy, the caller can: +If the caller reaches the voice mail for the user and the status of the user is set to Busy, the caller can take the following actions: -- Press the 1 key and be transferred to a receptionist at extension 45678. -- Press the 2 key and the Find Me feature will be used for urgent issues and ring extension 23456 first, and then 45671. +- Press the 1 key to be transferred to a receptionist at extension 45678. +- Press the 2 key to use the Find Me feature for urgent issues and ring extension 23456 first, and then 45671. ### Example 5 ```powershell @@ -302,7 +302,9 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016 -The Priority parameter specifies the order that the call answering rule will be evaluated against other existing call answering rules. Call answering rules are processed in order of increasing priority values. The priority must be unique between all call answering rules in the UM-enabled mailbox. The priority on the call answering rule must be between 1 (highest) and 9 (lowest). The default is 9. +The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, and rules can't have the same priority value. + +A valid value is an integer from 1 (highest priority) to 9 (lowest priority). The default value is 9. ```yaml Type: Int32 diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md index ae5a236e98..ec35aabbf5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md @@ -42,7 +42,7 @@ After the new UM dial plan is created, a UM IP gateway and a Mailbox server must After this task is completed, a new UM dial plan is created. -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-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md index 01d67f8d5e..db2ed984de 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md @@ -35,7 +35,7 @@ The New-UMHuntGroup cmdlet creates a UM hunt group in Active Directory. Running After this task is completed, a new UM hunt group is created. -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-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md index 16e27a7fae..f9dca59459 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md @@ -36,7 +36,7 @@ A UM IP gateway has organization-wide scope and references a single physical IP This cmdlet is scheduled to be removed from Exchange Online on December 1, 2019. For more information, see this [blog post](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/New-date-for-discontinuation-of-support-for-Session-Border/ba-p/607853). -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 @@ -144,11 +144,11 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016 -The IPAddressFamily parameter specifies whether the UM IP gateway will use Internet Protocol version 4 (IPv4), IPv6, or both to communicate. Valid values are: +The IPAddressFamily parameter specifies the Internet Protocol (IP) version to use. Valid values are: -- IPv4Only: The UM IP gateway will only use IPv4 to communicate. This is the default value. -- IPv6Only: The UM IP gateway will only use IPv6. -- Any: IPv6 will be used first, and then if necessary, it will fall back to IPv4. +- IPv4Only: The UM IP gateway uses only IPv4 to communicate. This value is the default. +- IPv6Only: The UM IP gateway uses only IPv6. +- Any: IPv6 is used first. If IPv6 isn't available, IPV4 is used. ```yaml Type: IPAddressFamily diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md index 66e7527fc8..996149bc7e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md @@ -34,7 +34,7 @@ The New-UMMailboxPolicy cmdlet creates a UM mailbox policy that has organization After this task is completed, a new UM mailbox policy is created. -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-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md index cf6d755473..b0062846ba 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md @@ -81,7 +81,7 @@ The Priority parameter specifies a priority value for the policy that determines This parameter is required when you create an audit log retention policy, and you must use a unique priority value. -Any custom audit log retention policy that you create will take precedence over the default audit log retention policy. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies). +Any custom audit log retention policy that you create take precedence over the default audit log retention policy. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies). ```yaml Type: Int32 diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md index 644cb77055..840c3aec79 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md @@ -127,7 +127,7 @@ New-UnifiedGroup -DlIdentity ## DESCRIPTION Microsoft 365 Groups are group objects that are available across Microsoft 365 services. -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 @@ -197,7 +197,7 @@ Accept wildcard characters: False The AccessType parameter specifies the privacy type for the Microsoft 365 Group. Valid values are: -- Public: The group content and conversations are available to everyone, and anyone can join the group without approval from a group owner. This is the default value. +- Public: The group content and conversations are available to everyone, and anyone can join the group without approval from a group owner. This value is the default. - Private: The group content and conversations are available only to members of the group, and joining the group requires approval from a group owner. You can change the privacy type at any point in the lifecycle of the group. @@ -229,7 +229,7 @@ The Alias value can contain letters, numbers and the following characters: - Periods (.) must be surrounded by other valid characters (for example, `help.desk`). - Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a Microsoft 365 Group, the value of the DisplayName parameter is used for the Alias value. Spaces are removed, unsupported characters are converted to question marks (?), and numbers may be added to maintain the uniqueness of the Alias value. +If you don't use the Alias parameter when you create a Microsoft 365 Group, the value of the DisplayName parameter is used for the Alias value. Spaces are removed, unsupported characters are converted to question marks (?), and numbers might be added to maintain the uniqueness of the Alias value. When you create a Microsoft 365 Group without using the EmailAddresses parameter, the Alias value is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. @@ -253,8 +253,8 @@ Accept wildcard characters: False The AlwaysSubscribeMembersToCalendarEvents switch controls the default subscription settings of new members that are added to the Microsoft 365 Group. -- If you use this switch without a value, all future members that are added to the group will have their subscriptions set to ReplyAndEvents. -- If you use this exact syntax: `-AlwaysSubscribeMembersToCalendarEvents:$false`, all future members that are added to the group will have their subscriptions set to ReplyOnly. +- If you use this switch without a value, all future members that are added to the group have their subscriptions set to ReplyAndEvents. +- If you use this exact syntax: `-AlwaysSubscribeMembersToCalendarEvents:$false`, all future members that are added to the group have their subscriptions set to ReplyOnly. Group members can change their own subscription settings, which can override your intended use of this switch. @@ -339,7 +339,7 @@ The ConvertClosedDlToPrivateGroup switch specifies whether to migrate the closed By default, this switch is always applied when migrating closed distribution groups, and is no longer required. -If the distribution group has the value Closed for the MemberDepartRestriction or MemberJoinRestriction parameters, the distribution group will always be migrated to a private Microsoft 365 Group. For open distribution groups, the migrated Microsoft 365 Group is always public, not private. +If the distribution group has the value Closed for the MemberDepartRestriction or MemberJoinRestriction parameters, the distribution group is always migrated to a private Microsoft 365 Group. For open distribution groups, the migrated Microsoft 365 Group is always public, not private. You can only use this switch with the DlIdentity parameter. @@ -475,7 +475,7 @@ The HiddenGroupMembershipEnabled switch specifies whether to hide the members of You can use this setting to help comply with regulations that require you to hide group membership from outsiders (for example, a Microsoft 365 Group that represents students enrolled in a class). -**Note**: You can't change this setting after you create the group. If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group, or vice-versa. In addition, any Microsoft 365 Groups with this setting will not be supported in sensitivity labeling policies. +**Note**: You can't change this setting after you create the group. If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group, or vice-versa. Also, any Microsoft 365 Groups with hidden group membership aren't supported in sensitivity labeling policies. ```yaml Type: SwitchParameter @@ -594,7 +594,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. Previously, if you specified a value for this parameter, a random GUID value was added and used as the Name property value for the Microsoft 365 Group (`Name_`). Now, the value of the Name property is populated by the Alias parameter value and the ExternalDirectoryObjectId property value (`_`). @@ -736,7 +736,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md index 8cf2548106..a3d3fc0bc0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md @@ -53,7 +53,7 @@ New-WebServicesVirtualDirectory [-ApplicationRoot ] ``` ## 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 @@ -126,7 +126,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 @@ -169,7 +169,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 @@ -211,7 +211,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 @@ -231,7 +231,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 @@ -252,8 +252,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. @@ -317,7 +317,7 @@ Accept wildcard characters: False The GzipLevel parameter sets the Gzip configuration for the Exchange Web Services virtual directory. Valid values are: - Off: No compression. -- Low: Static compression only. This is the default value. This value has the same result as the Off value, because Exchange Web Services content is dynamic. +- Low: Static compression only. This value is the default. This value has the same result as the Off value, because Exchange Web Services content is dynamic. - High: Static and dynamic compression. Content from Exchange Web Services is compressed if clients indicate support for Gzip compression in their requests. - Error: Identifies errors in the Gzip compression configuration. @@ -397,7 +397,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010. -The MRSProxyMaxConnections parameter specifies the maximum number of simultaneous move sessions that an instance of MRSProxy will accept. This setting accepts values from 0 to unlimited. The default value is 100. For more information about MRSProxy, see [Understanding Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)). +The MRSProxyMaxConnections parameter specifies the maximum number of simultaneous move sessions that an instance of MRSProxy accepts. This setting accepts values from 0 to unlimited. The default value is 100. For more information about MRSProxy, see [Understanding Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)). ```yaml Type: Unlimited @@ -417,7 +417,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 @@ -538,7 +538,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 @@ -559,7 +559,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-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md index 75b1a7057a..af13148098 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md @@ -65,7 +65,7 @@ organizational unit name - Abbreviation: OU1 to OU4 - Maximum character length: 32 -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/Preview-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md index d4ecdb9cff..d111fb6995 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md @@ -29,7 +29,7 @@ Preview-QuarantineMessage -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/Redirect-Message.md b/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md index 7235d9cac0..4ff9812e91 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md @@ -33,9 +33,9 @@ When a message queue is drained, the active messages in the queues on the source - Only active messages are drained. Shadow queues aren't drained. - Messages in the poison message queue aren't drained. -- The source server won't accept new messages while the queues are drained. +- The source server doesn't accept new messages while the queues are drained. -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/Release-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md index 4e44347bf6..211696a797 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md @@ -78,7 +78,7 @@ Release-QuarantineMessage -Identity ## DESCRIPTION Consider the following scenario: john@gmail.com sends a message to faith@contoso.com and john@subsidiary.contoso.com. Gmail bifurcates this message into two copies that are both routed to quarantine as phishing in Microsoft. An admin releases both of these messages to admin@contoso.com. The first released message that reaches the admin mailbox is delivered. The second released message is identified as duplicate delivery and is skipped. Message are identified as duplicates if they have the same message ID and received time. -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 @@ -228,7 +228,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection -The AllowSender switch specifies that all future messages from the sender won't be quarantined. You don't need to specify a value with this switch. +The AllowSender switch specifies that all future messages from the sender isn't quarantined. You don't need to specify a value with this switch. If the message was quarantined because of a transport rule or blocked sender, messages from the sender can still be blocked in the future. diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md index 63652b6d44..4d52a5ac4c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md @@ -30,7 +30,7 @@ Remove-AcceptedDomain [-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/Remove-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md index 7e6cbd67b6..53d507564f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md @@ -13,7 +13,7 @@ title: Remove-ActiveSyncDevice # Remove-ActiveSyncDevice ## 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 Remove-ActiveSyncDevice cmdlet to remove mobile device partnerships that identify the devices that are configured to synchronize with user mailboxes. @@ -34,7 +34,7 @@ Remove-ActiveSyncDevice [-Identity] ## DESCRIPTION The Remove-ActiveSyncDevice cmdlet is useful for removing mobile devices that no longer synchronize successfully with the 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md index bbd927ed8e..252701126d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md @@ -13,7 +13,7 @@ title: Remove-ActiveSyncDeviceAccessRule # Remove-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 Remove-ActiveSyncDeviceAccessRule cmdlet to remove any existing device access rule. @@ -32,7 +32,7 @@ Remove-ActiveSyncDeviceAccessRule [-Identity]