diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md index ae2917a68a..95a7d4a31c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md @@ -13,7 +13,7 @@ title: Get-MailContact # Get-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 Get-MailContact cmdlet to view existing mail contacts. @@ -54,7 +54,7 @@ Get-MailContact [[-Identity] ] ## DESCRIPTION The Get-MailContact cmdlet retrieves all attributes of the specified contact. No parameters are required. If the cmdlet is run without a parameter, a complete list of contacts for the Exchange organization is returned. -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/Get-MailDetailATPReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md index 0cd35bc4ee..39cb412f8d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md @@ -65,7 +65,7 @@ For the reporting period you specify, the cmdlet returns the following informati This cmdlet is limited to 10,000 results. If you reach this limit, you can use the available parameters to filter 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 @@ -74,7 +74,9 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Get-MailDetailATPReport -StartDate 7/22/2018 -EndDate 7/31/2018 ``` -This example returns the actions for the last 10 days in July, 2018. (Note: Customers with Defender for Office 365 subscriptions will be able to get up to 30 days of data.) +This example returns the actions for the last 10 days in July, 2018. + +Customers with Defender for Office 365 subscriptions can get up to 30 days of data. ## PARAMETERS @@ -233,7 +235,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md index 2043cdee62..1318943b53 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md @@ -41,7 +41,7 @@ Get-MailDetailDlpPolicyReport [-Action ] ``` ## 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 @@ -185,7 +185,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md index 3f2175e653..986013442c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md @@ -54,7 +54,7 @@ If you append the command with ` | Format-List`, the following additional inform - Message Size - Subject -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 @@ -193,7 +193,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). You can specify multiple values separated by commas. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md index 7ca077624a..21c4bddb6f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md @@ -40,7 +40,7 @@ Get-MailDetailTransportRuleReport [-Action ] ``` ## 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 @@ -165,7 +165,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md index fca22fa5d4..3038284e6e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md @@ -31,7 +31,7 @@ Get-MailFilterListReport ``` ## 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/Get-MailFlowStatusReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailFlowStatusReport.md index c9ca311930..fc641edb9e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailFlowStatusReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailFlowStatusReport.md @@ -42,7 +42,7 @@ This cmdlet returns the following information: - Event Type - Count -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/Get-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md index 0ff82748fe..c9c71c1564 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md @@ -13,7 +13,7 @@ title: Get-MailPublicFolder # Get-MailPublicFolder ## 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 Get-MailPublicFolder cmdlet to retrieve mail-related information about mail-enabled public folders. If you want information about the basic (not mail-related) settings of mail-enabled public folders, use the Get-PublicFolder cmdlet instead. @@ -50,7 +50,7 @@ Get-MailPublicFolder [[-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/Get-MailTrafficATPReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md index 318fbbbe60..8c4dd7aca1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md @@ -53,7 +53,7 @@ For the reporting period you specify, the cmdlet returns the following informati - Verdict Source - Message Count -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/Get-MailTrafficEncryptionReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md index e864108d17..dc8465437c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md @@ -47,7 +47,7 @@ For the reporting period you specify, the cmdlet returns the following informati - Message Count - Recipient Count -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/Get-MailTrafficPolicyReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md index 78abc412a0..a85f525837 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md @@ -49,7 +49,7 @@ For the reporting period you specify, the cmdlet returns the following informati - Direction - Message Count -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/Get-MailTrafficSummaryReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md index 05ad814da1..652e149273 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md @@ -41,7 +41,7 @@ This cmdlet has C1, C2 and C3 as header names and the meaning of them depends on - TopSpamRecipient, TopMailSender, TopMailRecipient and TopMalwareRecipient: C1 is the recipient or sender and C2 the quantity of email messages. - TopMalware: C1 is the malware name and C2 the quantity of appearances. -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/Get-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md index 7e8cd7aefb..8198063763 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md @@ -13,7 +13,7 @@ title: Get-MailUser # Get-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 Get-MailUser cmdlet to view mail users and also guest users for Microsoft 365 Groups in cloud environments. @@ -79,7 +79,7 @@ Get-MailUser [-HVEAccount] ``` ## 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/Get-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md index 607711b6f8..1dd6099661 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md @@ -13,7 +13,7 @@ title: Get-MailboxSearch # Get-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 Get-MailboxSearch cmdlet to view mailbox searches that are in progress, complete or stopped. @@ -52,7 +52,7 @@ Get-MailboxSearch -InPlaceHoldIdentity ## DESCRIPTION In on-premises Exchange, a mailbox search is used to perform an In-Place eDiscovery or to place users on an In-Place Hold. Use the Get-MailboxSearch cmdlet to retrieve details of either type of mailbox search. -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/Get-MailboxSentItemsConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md index 847a41ef34..6ed02a5bdc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md @@ -30,7 +30,7 @@ Get-MailboxSentItemsConfiguration [-DomainController ] ## DESCRIPTION By default, when you use Send As or Send On Behalf Of to send a message from another mailbox, the message is saved in your Sent Items folder (not in the Sent Items folder of the source mailbox). In Microsoft Exchange Server 2010 Service Pack 3 (SP3), you can save copies messages in the Sent Items folder of the sender and the source mailbox. For example, consider a shared mailbox that receives customer feedback and is monitored by multiple users. When someone responds to a message in the shared mailbox, you can save the message in the Sent Items folder of the shared mailbox and the sender's mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md index 6be71ce89d..4c6925717f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md @@ -31,7 +31,7 @@ Get-MailboxServer [[-Identity] ] ## DESCRIPTION The ExchangeVersion attribute returned is the minimum version of Microsoft Exchange that you can use to manage the returned object. This attribute isn't the same as the version of Microsoft Exchange that's displayed in the Exchange admin center when you select Server Configuration. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md index d132b4950f..fc0ca8f8a2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md @@ -13,7 +13,7 @@ title: Get-MailboxSpellingConfiguration # Get-MailboxSpellingConfiguration ## 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 Get-MailboxSpellingConfiguration cmdlet to retrieve the Outlook on the web spelling checker settings of a specified user. For example, users can set their dictionary language and configure the spelling checker to ignore mixed digits and words in all uppercase. @@ -35,7 +35,7 @@ The Get-MailboxSpellingConfiguration cmdlet is primarily used to populate the sp - DictionaryLanguage: This setting specifies the dictionary language used when the spelling checker checks the spelling in messages. - IgnoreMixedDigits: This setting specifies whether the spelling checker ignores words that contain numbers. -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/Get-MailboxStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md index 53dfbc6753..fa20e834d4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md @@ -13,7 +13,7 @@ title: Get-MailboxStatistics # Get-MailboxStatistics ## 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 Get-MailboxStatistics cmdlet to return information about a mailbox, such as the size of the mailbox, the number of messages it contains, and the last time it was accessed. In addition, you can get the move history or a move report of a completed move request. @@ -75,7 +75,7 @@ You can only see move reports and move history for completed move requests. **Note**: We're deprecating the LastUserActionTime property in Exchange Online PowerShell. Don't use the value of that property as the last active time for a mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -135,7 +135,7 @@ $temp=Get-MailboxStatistics -Identity AylaKol -IncludeMoveHistory $temp.MoveHistory[0] ``` -This example returns the detailed move history for the completed move request for Ayla Kol's mailbox. This example uses a temporary variable to store the mailbox statistics object. If the mailbox has been moved multiple times, there are multiple move reports. The last move report is always MoveReport[0]. +This example returns the detailed move history for the completed move request for Ayla Kol's mailbox. This example uses a temporary variable to store the mailbox statistics object. If the mailbox is moved multiple times, there are multiple move reports. The last move report is always MoveReport[0]. ### Example 9 ```powershell diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md index 25cb4369a6..d93f8c7443 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md @@ -30,7 +30,7 @@ Get-MailboxTransportService [[-Identity] ] ## DESCRIPTION The Mailbox Transport service runs on all Mailbox servers and is responsible for delivering messages to and accepting messages from local mailbox databases using remote procedure calls (RPC). The Mailbox Transport service also uses SMTP to send messages to and from the Transport service that runs on all Mailbox servers for routing their ultimate destinations. -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/Get-MailboxUserConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md index 961975f2db..c5a73d9071 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md @@ -13,7 +13,7 @@ title: Get-MailboxUserConfiguration # Get-MailboxUserConfiguration ## 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 Get-MailboxUserConfiguration cmdlet to view user configuration items in mailboxes. @@ -30,7 +30,7 @@ Get-MailboxUserConfiguration [-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/Get-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md index 5d133ef2fb..70fc40e4e3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md @@ -13,7 +13,7 @@ title: Get-MalwareFilterPolicy # Get-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 Get-MalwareFilterPolicy cmdlet to view the malware filter policies in your organization. @@ -30,7 +30,7 @@ Get-MalwareFilterPolicy [[-Identity] ] ## DESCRIPTION Malware filter policies contain the malware settings and a list of domains to which those settings apply. A domain can't belong to more than one malware filter policy. -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/Get-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md index 9dece05188..851fe8bee1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md @@ -13,7 +13,7 @@ title: Get-MalwareFilterRule # Get-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 Enable-MalwareFilterRule cmdlet to view malware filter rules in your organization. @@ -29,7 +29,7 @@ Get-MalwareFilterRule [[-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/Get-MalwareFilteringServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md index 7cdc96ccc4..a5aa694930 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md @@ -28,7 +28,7 @@ Get-MalwareFilteringServer [[-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/Get-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md index 38de7eef3b..3363cb27c8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md @@ -40,7 +40,7 @@ The Get-ManagedContentSettings cmdlet retrieves from one to all of the managed c If only the Identity parameter is present, the folder content settings and all associated attributes are returned. If the Identity parameter isn't present, the command returns all content settings. If the FolderName parameter is present, the command returns all content settings contained in the specified managed folder and all the attributes of each setting. -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/Get-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md index a3984883b9..603b909fa6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md @@ -44,7 +44,7 @@ The Get-ManagedFolder cmdlet retrieves the specified managed folder attributes: The Get-ManagedFolder cmdlet accepts a ManagedFolder object or an identity string as pipelined input. -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/Get-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md index 012ba3077b..7c810e181a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md @@ -30,7 +30,7 @@ Get-ManagedFolderMailboxPolicy [[-Identity] ] ## DESCRIPTION A managed folder mailbox policy is a logical grouping of one or more managed folders. Policies are applied to mailboxes. The Get-ManagedFolderMailboxPolicy cmdlet lists one or more managed folder mailbox policies created in the Microsoft Exchange Server 2010 organization. All policies can be listed. -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/Get-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md index fc7a39e6d1..67b161bb48 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md @@ -13,7 +13,7 @@ title: Get-ManagementRole # Get-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 Get-ManagementRole cmdlet to view management roles that have been created in your organization. @@ -64,7 +64,7 @@ You can view management roles in several ways, from listing all the roles in you 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md index 31e8e41432..e3ee03a9c7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md @@ -13,7 +13,7 @@ title: Get-ManagementRoleAssignment # Get-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 Get-ManagementRoleAssignment cmdlet to retrieve management role assignments. @@ -76,7 +76,7 @@ You can retrieve role assignments in a variety of ways including by assignment t 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md index 7c88254dd8..6069d86005 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md @@ -13,7 +13,7 @@ title: Get-ManagementRoleEntry # Get-ManagementRoleEntry ## 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 Get-ManagementRoleEntry cmdlet to retrieve management role entries that have been configured on management roles. @@ -36,7 +36,7 @@ The Get-ManagementRoleEntry cmdlet retrieves role entries that have been configu For more information about management role entries, 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md index cc67cda634..e3d35c1cde 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md @@ -13,7 +13,7 @@ title: Get-ManagementScope # Get-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 Get-ManagementScope cmdlet to return a list of management scopes. @@ -34,7 +34,7 @@ You can retrieve one scope or many, retrieve only scopes that aren't associated 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/Get-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md index 72586d4075..8d63f79498 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md @@ -40,7 +40,7 @@ Get-MapiVirtualDirectory [[-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/Get-Message.md b/exchange/exchange-ps/ExchangePowerShell/Get-Message.md index f9c313b9b5..2aa1848340 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Message.md @@ -70,7 +70,7 @@ Get-Message [-Queue ] ## DESCRIPTION You can display messages by including the server name as part of the Identity parameter or the Queue parameter or by including the Server parameter with a filter query. The Identity parameter, Queue parameter, and Filter parameter settings are mutually exclusive. -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 @@ -195,7 +195,7 @@ Accept wildcard characters: False The IncludeComponentLatencyInfo switch specifies whether the information about component latency is included in the message properties. You don't need to specify a value with this switch. -If you include this switch, the message objects returned will include latency measurements for each Transport component that has contributed to the local server latency for each queued message. +If you include this switch, the message objects returned include latency measurements for each Transport component that has contributed to the local server latency for each queued message. ```yaml Type: SwitchParameter @@ -220,9 +220,9 @@ If you don't include the IncludeRecipientInfo switch, the Recipients field is bl Storing the results of a `Get-Message -IncludeRecipientInfo` command in a variable allows you to display additional properties for the message recipients. The following list describes the available recipient properties: - Address: The email address of the recipient. -- Type: The recipient type, which may be External, Mailbox or Distribution Group. Distribution Group is used when the destination is an expansion server. +- Type: The recipient type, which might be External, Mailbox or Distribution Group. Distribution Group is used when the destination is an expansion server. - FinalDestination: The distinguished name (DN) of the object used to route the message. -- Status: The recipient status may be Complete, Ready or Retry. +- Status: The recipient status might be Complete, Ready or Retry. - LastError: The SMTP response after the last delivery attempt or a localized error message if the message is placed in the unreachable queue. For example, to store the recipient information of a message in the contoso.com remote delivery queue that has the MessageIdentity value of 1234 to a variable named $x, use the following command: `$x=Get-Message -Identity "contoso.com\\1234" -IncludeRecipientInfo`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md index b459f539f4..3eaf7fb54c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md @@ -13,7 +13,7 @@ title: Get-MessageCategory # Get-MessageCategory ## 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 Get-MessageCategory cmdlet to retrieve a message category from the specified mailbox. @@ -31,7 +31,7 @@ Get-MessageCategory [[-Identity] ] ## DESCRIPTION The Get-MessageCategory cmdlet is used by the web management interface in Microsoft Exchange to populate fields that display message category information. -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/Get-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md index c2c3594d87..4dc5651fcc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md @@ -13,7 +13,7 @@ title: Get-MessageClassification # Get-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 Get-MessageClassification cmdlet to view existing message classifications in your organization. @@ -29,7 +29,7 @@ Get-MessageClassification [[-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/Get-MessageTrace.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md index a364e80569..a470a56e43 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md @@ -44,15 +44,15 @@ Get-MessageTrace ## DESCRIPTION You can use this cmdlet to search message data for the last 10 days. If you run this cmdlet without any parameters, only data from the last 48 hours is returned. -If you enter a start date that is older than 10 days, you will receive an error and the command will return no results. +If you enter a start date that is older than 10 days, you get an error and the command returns no results. To search for message data that is greater than 10 days old, use the Start-HistoricalSearch and Get-HistoricalSearch cmdlets. -By default, this cmdlet returns a maximum of 1000 results, and will timeout on very large queries. If your query returns too many results, consider splitting it up using smaller StartDate and EndDate intervals. +By default, this cmdlet returns a maximum of 1000 results, and times out on very large queries. If your query returns too many results, consider splitting it up using smaller StartDate and EndDate intervals. The time stamps on the output are in UTC time format. That might be different from the time format that you used for the -StartDate and the -EndDate parameters. -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 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md index 86ce5348b6..fd7c45e868 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md @@ -18,7 +18,7 @@ This cmdlet is available only in the cloud-based service. > [!NOTE] > This cmdlet is replaced by the [Get-MessageTraceDetailV2](https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagetracedetailv2) cmdlet and will eventually be deprecated. -Use the Get-MessageTraceDetail cmdlet to view the message trace event details for a specific message. Note that these detailed results are returned less quickly than the Get-MessageTrace results. +Use the Get-MessageTraceDetail cmdlet to view the message trace event details for a specific message. These detailed results are returned less quickly than the Get-MessageTrace results. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -39,11 +39,11 @@ Get-MessageTraceDetail -MessageTraceId -RecipientAddress ``` ## DESCRIPTION -You can use this cmdlet to search message data for the last 10 days. If you enter a time period that's older than 10 days, you will receive an error and the command will return no results. +You can use this cmdlet to search message data for the last 10 days. If you enter a time period that's older than 10 days, you get an error and the command returns no results. To search for message data that is greater than 10 days old, use the Start-HistoricalSearch and Get-HistoricalSearch cmdlets. -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 @@ The Event parameter filters the report by the message event. The following are e - DELIVER: The message was delivered to a mailbox. - EXPAND: The message was sent to a distribution group that was expanded. - TRANSFER: Recipients were moved to a bifurcated message because of content conversion, message recipient limits, or agents. -- DEFER: The message delivery was postponed and may be re-attempted later. +- DEFER: The message delivery was postponed and might be re-attempted later. You can specify multiple values separated by commas. @@ -181,7 +181,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md index 0c9ae55a19..2a3f46266f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md @@ -28,11 +28,11 @@ Get-MessageTraceDetailV2 [-MessageTraceId] [-RecipientAddress] ``` ## DESCRIPTION -You can use this cmdlet to search message data for the last 90 days. You can only query 10 days worth of data per query. If you enter a timeframe that's older than 90 days, you receive an error and the command will return no results. +You can use this cmdlet to search message data for the last 90 days. You can only query 10 days worth of data per query. If you enter a timeframe that's older than 90 days, you receive an error and the command returns no results. -Throttling limit: A maximum of 100 query requests will be accepted within 5 minutes running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the past 5 minutes +Throttling limit: A maximum of 100 query requests are accepted within a 5 minute running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the last 5 minutes -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 @@ The Event parameter filters the report by the message event. The following are e - DELIVER: The message was delivered to a mailbox. - EXPAND: The message was sent to a distribution group that was expanded. - TRANSFER: Recipients were moved to a bifurcated message because of content conversion, message recipient limits, or agents. -- DEFER: The message delivery was postponed and may be re-attempted later. +- DEFER: The message delivery was postponed and might be re-attempted later. You can specify multiple values separated by commas. @@ -162,7 +162,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md index 066f328ae0..0e274fc967 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md @@ -46,7 +46,7 @@ By default, this cmdlet returns up to 1000 results, with a maximum of 5000 resul The time stamps on the output are in UTC time format. That might be different from the time format that you used for the -StartDate and the -EndDate parameters. -Throttling limit: A maximum of 100 query requests will be accepted within 5 minutes running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the past 5 minutes +Throttling limit: A maximum of 100 query requests are accepted within a 5 minute running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the last 5 minutes Pagination isn't supported in this cmdlet. To query subsequent data, use the StartingRecipientAddress and EndDate parameters with the values from the **Recipient address** and **Received Time** properties respectively of the previous result in the next query. @@ -56,7 +56,7 @@ Best Practices: - Be as precise as possible. Narrow the gap between StartDate and EndDate and use additional parameters (for example, SenderAddress) where possible. - Use MessageTraceId where possible (required for messages sent to more than 1000 recipients). -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 @@ -111,7 +111,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md index b31a70814c..d2f4eae656 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md @@ -54,7 +54,7 @@ For more information about the message tracking log files, see [Message tracking You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding ` > ` to the command. For example: `Get-MessageTrackingLog -Start "03/13/2020 09:00:00" -End "03/13/2020 09:10:00" | ConvertTo-Html > "C:\My Documents\message track.html"`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -156,7 +156,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The MessageId parameter filters the message tracking log entries by the value of the MessageId field. The value of MessageId corresponds to the value of the Message-Id: header field in the message. If the Message-ID header field is blank or doesn't exist, an arbitrary value is assigned. Be sure to include the full MessageId string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the message tracking log entries by the value of the MessageId field. The value of MessageId corresponds to the value of the Message-Id: header field in the message. If the Message-ID header field is blank or doesn't exist, an arbitrary value is assigned. Be sure to include the full MessageId string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). ```yaml Type: String @@ -309,7 +309,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019 -The NetworkMessageId parameter filters the message tracking log entries by the value of the NetworkMessageId field. This field contains a unique message ID value that persists across copies of the message that may be created due to bifurcation or distribution group expansion. An example value is 1341ac7b13fb42ab4d4408cf7f55890f. +The NetworkMessageId parameter filters the message tracking log entries by the value of the NetworkMessageId field. This field contains a unique message ID value that persists across copies of the message that might be created due to bifurcation or distribution group expansion. An example value is 1341ac7b13fb42ab4d4408cf7f55890f. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md index 6ab8dab4b6..67532cc6d9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md @@ -41,7 +41,7 @@ Get-MessageTrackingReport [-Identity] ## DESCRIPTION This cmdlet requires the ID for the message tracking report that you want to view. Therefore, first you need to use the Search-MessageTrackingReport cmdlet to find the message tracking report ID for a specific message, and then pass the results to this cmdlet. For more information, see [Search-MessageTrackingReport](https://learn.microsoft.com/powershell/module/exchangepowershell/search-messagetrackingreport). -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/Get-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md index 0739a81f91..fb5ffbccec 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md @@ -13,7 +13,7 @@ title: Get-MigrationBatch # Get-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 Get-MigrationBatch cmdlet to retrieve status information about the current migration batch. @@ -78,9 +78,9 @@ The Get-MigrationBatch cmdlet displays status information about the current migr - Migration errors - Date and time when the migration was started and completed. -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**: In the cloud-based service, if you don't use the TimeZone parameter in the New-MigrationBatch command, the default time zone for the migration batch is UTC. The CompleteAfter and CompleteAfterUTC properties will contain the same value (as will the StartAfter and StartAfterUTC properties). When you create the migration batch in the Exchange admin center (EAC), the time zone that's used is based on your regional configuration. +**Note**: In the cloud-based service, if you don't use the TimeZone parameter in the New-MigrationBatch command, the default time zone for the migration batch is UTC. The CompleteAfter and CompleteAfterUTC properties contain the same value (and also the StartAfter and StartAfterUTC properties). When you create the migration batch in the Exchange admin center (EAC), the time zone that's used is based on your regional configuration. ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md index 6129685733..a256dc66ad 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md @@ -13,7 +13,7 @@ title: Get-MigrationConfig # Get-MigrationConfig ## 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 Get-MigrationConfig cmdlet to retrieve migration configuration settings on Exchange servers. @@ -42,7 +42,7 @@ Get-MigrationConfig [-AllPartitions] ``` ## 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/Get-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md index 44e621ed39..3ea33df985 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md @@ -13,7 +13,7 @@ title: Get-MigrationEndpoint # Get-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 Get-MigrationEndpoint cmdlet to retrieve migration endpoint settings for source or destination servers for cutover or staged Exchange migrations, IMAP migrations, and remote moves. @@ -67,7 +67,7 @@ For more information about the different move and migration scenarios, see: - [Mailbox moves in Exchange Server](https://learn.microsoft.com/Exchange/recipients/mailbox-moves) - [Manage on-premises mailbox moves in Exchange Server](https://learn.microsoft.com/Exchange/architecture/mailbox-servers/manage-mailbox-moves) -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/Get-MigrationStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md index a039591098..05587e4c0a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md @@ -13,7 +13,7 @@ title: Get-MigrationStatistics # Get-MigrationStatistics ## 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 Get-MigrationStatistics cmdlet to view detailed information about migration requests. @@ -31,7 +31,7 @@ Get-MigrationStatistics [-Diagnostic] ``` ## 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/Get-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md index 3539caf558..4f85b2de43 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md @@ -13,7 +13,7 @@ title: Get-MigrationUser # Get-MigrationUser ## 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 Get-MigrationUser cmdlet to view information about move and migration users. @@ -62,7 +62,7 @@ Get-MigrationUser -EmailAddress ``` ## 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/Get-MigrationUserStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md index 98b51272c1..cc7cf9ad2f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md @@ -13,7 +13,7 @@ title: Get-MigrationUserStatistics # Get-MigrationUserStatistics ## 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 Get-MigrationUserStatistics cmdlet to view detailed information about the migration requested for a specific user. @@ -37,7 +37,7 @@ Get-MigrationUserStatistics [-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/Get-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md index f0dcc63610..d54fc9963c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md @@ -13,7 +13,7 @@ title: Get-MobileDevice # Get-MobileDevice ## 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 Get-MobileDevice cmdlet to get the list of devices in your organization that have active partnerships. @@ -56,7 +56,7 @@ Get-MobileDevice [[-Identity] ] ## DESCRIPTION The Get-MobileDevice cmdlet returns identification, configuration, and status information for each mobile device. -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/Get-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md index 61bdb004a8..ce8b3ca55f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md @@ -13,7 +13,7 @@ title: Get-MobileDeviceMailboxPolicy # Get-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 Get-MobileDeviceMailboxPolicy cmdlet to retrieve the Mobile Device mailbox policy settings for a specific Mobile Device mailbox policy. @@ -30,7 +30,7 @@ Get-MobileDeviceMailboxPolicy [[-Identity] ] ## DESCRIPTION A Mobile Device mailbox policy is a group of settings that specifies how mobile devices connect Exchange. Exchange supports multiple mobile device mailbox policies. The Get-MobileDeviceMailboxPolicy cmdlet displays all the policy settings for the specified policy. These settings include password settings, file access settings and attachment 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md index 9e800bcd46..ae8aeb20f0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md @@ -13,7 +13,7 @@ title: Get-MobileDeviceStatistics # Get-MobileDeviceStatistics ## 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 Get-MobileDeviceStatistics cmdlet to retrieve the list of mobile devices configured to synchronize with a specified user's mailbox and return a list of statistics about the mobile devices. @@ -56,7 +56,7 @@ Get-MobileDeviceStatistics -Mailbox ## DESCRIPTION The Get-MobileDeviceStatistics cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes. -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/Get-MonitoringItemHelp.md b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md index d7d517597e..738fa466ce 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md @@ -27,7 +27,7 @@ Get-MonitoringItemHelp [-Identity] -Server ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md index ca5cfa71ed..3ac2e98fc2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md @@ -27,7 +27,7 @@ Get-MonitoringItemIdentity [-Identity] -Server ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md index b38430ed75..34a6e39394 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md @@ -13,7 +13,7 @@ title: Get-MoveRequest # Get-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 Get-MoveRequest cmdlet to view the detailed status of an ongoing asynchronous mailbox move that was initiated by using the New-MoveRequest cmdlet. @@ -61,7 +61,7 @@ Get-MoveRequest [-BatchName ] ## DESCRIPTION The search criteria for the Get-MoveRequest cmdlet is a Boolean And statement. If you use multiple parameters, it narrows your search and reduces your search results. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -196,7 +196,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The Flags parameter specifies the move type to retrieve information for. The following values may be used: +The Flags parameter specifies the move type to retrieve information for. Valid value are: - CrossOrg - HighPriority diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md index 68320eaf70..b3d60fea23 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md @@ -13,7 +13,7 @@ title: Get-MoveRequestStatistics # Get-MoveRequestStatistics ## 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 Get-MoveRequestStatistics cmdlet to view detailed information about move requests. @@ -67,7 +67,7 @@ Get-MoveRequestStatistics -MRSInstance ``` ## 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 @@ This example returns default statistics for all mailboxes whose move requests ar Get-MoveRequestStatistics -MRSInstance CAS01.contoso.com -MailboxGuid b6a6795c-a010-4f67-aaaa-da372d56fcb9 ``` -In Exchange Server 2010, this example returns default statistics for a mailbox that has been moved by the instance of the Microsoft Exchange Mailbox Replication service running on the server CAS01. +In Exchange Server 2010, this example returns default statistics for a mailbox that is moved by the instance of the Microsoft Exchange Mailbox Replication service running on the server CAS01. ### Example 6 ```powershell diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md index 381a4bd6ca..13fa49ad9d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md @@ -28,7 +28,7 @@ Get-MxRecordReport [-Domain ] ``` ## 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/Get-NetworkConnectionInfo.md b/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md index f7b4de2bb8..65e665e779 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md @@ -36,7 +36,7 @@ This cmdlet retrieves the following configuration information for each network a - AdapterGuid: This field displays the GUID assigned to the network adapter by Windows. - MacAddress: This field displays the media access control (MAC) address of the network adapter. -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/Get-Notification.md b/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md index 56c6a50bb9..88a4d4185b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md @@ -13,7 +13,7 @@ title: Get-Notification # Get-Notification ## 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. > [!NOTE] > This cmdlet will be deprecated in the cloud-based service. The classic Exchange admin center was deprecated in the cloud-based service in 2023. @@ -56,7 +56,7 @@ Get-Notification [-ProcessType ] ``` ## 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/Get-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md index a949238598..a7361a7e95 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md @@ -27,7 +27,7 @@ Get-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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md index 336fa65242..94749431a1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md @@ -27,9 +27,9 @@ Get-OMEMessageStatus -MessageId ``` ## DESCRIPTION -If encryption for the message was successfully revoked, the command will return the message: `The encrypted email with the subject "" and Message ID "" was successfully revoked`. +If encryption for the message was successfully revoked, the command returns the message: `The encrypted email with the subject "" and Message ID "" was successfully revoked`. -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 @@ -46,7 +46,7 @@ This example returns the encryption revocation status for the specified message. > Applicable: Exchange Online -The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). You can find the Message ID for a message in Message Trace or the Message Encryption Report in the Microsoft Purview compliance portal. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md index 7833b1e3f6..8cad368b7a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md @@ -40,7 +40,7 @@ Get-OabVirtualDirectory [[-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/Get-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md index ff9c978f2a..299ffe54d0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md @@ -13,7 +13,7 @@ title: Get-OfflineAddressBook # Get-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 Get-OfflineAddressBook cmdlet to view offline address books (OABs). @@ -38,7 +38,7 @@ Get-OfflineAddressBook [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md index 14db290342..bb8d46bbe8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md @@ -15,7 +15,7 @@ title: Get-OnPremisesOrganization ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Get-OnPremisesOrganization cmdlet to retrieve settings for the OnPremisesOrganization object that has been created for a hybrid deployment. +Use the Get-OnPremisesOrganization cmdlet to retrieve settings for the OnPremisesOrganization object that is created for a hybrid deployment. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -29,9 +29,9 @@ Get-OnPremisesOrganization [[-Identity] ] ## DESCRIPTION The OnPremisesOrganization object represents an on-premises 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. You can use the Get-OnPremisesOrganization cmdlet to view the properties of the OnPremisesOrganization object in the Microsoft 365 organization. -Manual modification of this object may result in hybrid deployment misconfiguration. We strongly recommend that you use the Hybrid Configuration wizard to modify this object in the Microsoft 365 organization. +Manual modification of this object might result in hybrid deployment misconfiguration. We strongly recommend that you use the Hybrid Configuration wizard to modify 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md index 7a988d46c5..402cc08950 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md @@ -35,7 +35,7 @@ Exchange Online maintains a per-user cache of Skype for Business Online meeting - LastSyncTime: The last time Exchange Online successfully synchronized meeting coordinates from Skype for Business Online. - LastSuccessfulSyncTime: The last time Exchange Online successfully cleaned the cached of used Skype for Business Online meeting coordinates. -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/Get-OrganizationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md index 002af611d2..d269f440c7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md @@ -13,7 +13,7 @@ title: Get-OrganizationConfig # Get-OrganizationConfig ## 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 Get-OrganizationConfig cmdlet to get configuration data for an Exchange organization. @@ -27,7 +27,7 @@ Get-OrganizationConfig [-DomainController ] ``` ## 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/Get-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md index 3207111a9e..7effe3c9ad 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md @@ -13,9 +13,9 @@ title: Get-OrganizationRelationship # Get-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 Get-OrganizationRelationship cmdlet to retrieve settings for an organization relationship that has been created for federated sharing with other federated Exchange organizations or for hybrid deployments with Exchange Online. +Use the Get-OrganizationRelationship cmdlet to retrieve settings for an organization relationship that is created for federated sharing with other federated Exchange organizations or for hybrid deployments with Exchange Online. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -28,7 +28,7 @@ Get-OrganizationRelationship [[-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/Get-OrganizationalUnit.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md index b624cd2c69..35252328c5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md @@ -13,7 +13,7 @@ title: Get-OrganizationalUnit # Get-OrganizationalUnit ## 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 Get-OrganizationalUnit cmdlet to view a list of organizational units (OUs) that exist in your organization. @@ -43,7 +43,7 @@ Get-OrganizationalUnit [-SearchText ] ## DESCRIPTION The Get-OrganizationalUnit cmdlet is used by the Exchange admin center to populate fields that display OU information. -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/Get-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md index 49cbedd76e..882495a3e6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md @@ -32,7 +32,7 @@ Get-OutboundConnector [[-Identity] ] ## 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 @@ -74,7 +74,7 @@ Accept wildcard characters: False The IncludeTestModeConnectors parameter filters the results by Outbound connectors that are in test mode. Valid values are: - $true: Only Outbound connectors that are in test mode are returned in the results. -- $false: All Outbound connectors that aren't in test mode are returned in the results. This is the default value. +- $false: All Outbound connectors that aren't in test mode are returned in the results. This value is the default. You configure an Outbound connector in test mode by using the TestMode parameter on the New-OutboundConnector or Set-OutboundConnector cmdlets. @@ -97,7 +97,7 @@ Accept wildcard characters: False The IsTransportRuleScoped parameter filters the results by Outbound connectors that are scoped to transport rules (also known as mail flow rules). Valid values are: - $true: Only Outbound connectors that are scoped to transport rules are returned in the results. -- $false: All Outbound connectors that aren't scoped to transport rules are returned in the results. This is the default value. +- $false: All Outbound connectors that aren't scoped to transport rules are returned in the results. This value is the default. You scope a transport rule to a specific Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md index 17040b63b4..7df51454de 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md @@ -28,7 +28,7 @@ Get-OutboundConnectorReport [-Domain ] ``` ## 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/Get-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md index 28d5d37d26..112de05d73 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md @@ -40,7 +40,7 @@ Get-OutlookAnywhere [[-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/Get-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md index 30ab2649a2..c6efe5855d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md @@ -15,7 +15,7 @@ title: Get-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 Get-OutlookProtectionRule cmdlet to retrieve Microsoft Outlook protection rules configured in an organization. @@ -32,7 +32,7 @@ Get-OutlookProtectionRule [[-Identity] ] ## DESCRIPTION Outlook protection rules are used to automatically Information Rights Management (IRM)-protect email messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To IRM-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-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/Get-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md index e73ad25a0a..d399eecb7f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md @@ -30,7 +30,7 @@ Get-OutlookProvider [[-Identity] ] ## DESCRIPTION The Get-OutlookProvider cmdlet gets the global settings from the AutoDiscoverConfig object in Active Directory and returns an OutlookProvider object to be managed in the Exchange admin center. -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/Get-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md index b282c856fa..6e68f829bf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md @@ -13,7 +13,7 @@ title: Get-OwaMailboxPolicy # Get-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 Get-OwaMailboxPolicy cmdlet to view Outlook on the web mailbox policies in the organization. @@ -28,7 +28,7 @@ Get-OwaMailboxPolicy [[-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/Get-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md index 255f7385df..e918994ed0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md @@ -44,7 +44,7 @@ The Get-OwaVirtualDirectory cmdlet can be run on a local server or run remotely The Get-OwaVirtualDirectory cmdlet can be run on any server that has the Exchange Server administration tools installed. -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/Get-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md index d445571b81..51e6a7a743 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md @@ -13,7 +13,7 @@ title: Get-PartnerApplication # Get-PartnerApplication ## 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 Get-PartnerApplication cmdlet to retrieve settings for a partner application. @@ -31,7 +31,7 @@ Get-PartnerApplication [[-Identity] ] ## DESCRIPTION You can configure partner applications such as Microsoft SharePoint to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://learn.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). -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/Get-PendingDelicenseUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md index dac9418166..ffc321eb50 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md @@ -34,7 +34,7 @@ Get-PendingDelicenseUser [-ResultSize ] [-ShowDueObjectsOnly] ``` ## 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/Get-PendingFederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md index 67b746dcbc..1b57b6d5c1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md @@ -26,7 +26,7 @@ Get-PendingFederatedDomain [] ``` ## 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/Get-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md index c782ae2639..d32e6822a1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md @@ -26,7 +26,7 @@ Get-PhishSimOverridePolicy [[-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/Get-Place.md b/exchange/exchange-ps/ExchangePowerShell/Get-Place.md index 0d99aef484..cd0df94272 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Place.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Place.md @@ -40,7 +40,7 @@ Get-Place [-Type ] ``` ## 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/Get-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md index 0f66e454dd..2ac670e3e4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md @@ -13,7 +13,7 @@ title: Get-PolicyTipConfig # Get-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 Get-PolicyTipConfig cmdlet to view the data loss prevention (DLP) Policy Tips in your organization. @@ -38,7 +38,7 @@ Get-PolicyTipConfig [[-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/Get-PopSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md index fdf0c23826..d140d3fa03 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md @@ -28,7 +28,7 @@ Get-PopSettings [-DomainController ] ``` ## 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/Get-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md index a5bc976d2e..4324161baf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md @@ -40,7 +40,7 @@ Get-PowerShellVirtualDirectory [[-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/Get-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md index 299fc5a598..aeeccce66a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md @@ -13,7 +13,7 @@ title: Get-PublicFolder # Get-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 Get-PublicFolder cmdlet to retrieve the attributes of a public folder or a set of public folders. @@ -70,7 +70,7 @@ Get-PublicFolder [[-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 @@ -273,7 +273,7 @@ Accept wildcard characters: False The ResidentFolders switch specifies whether to return public folders that reside in a specific content public folder mailbox. You don't need to specify a value with this switch. -If you don't use this switch, the command will return only public folders whose contents reside in the primary hierarchy public folder mailbox. +If you don't use this switch, the command returns only public folders whose contents reside in the primary hierarchy public folder mailbox. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md index 841f2e7c5e..b11d5b7b4e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md @@ -38,7 +38,7 @@ Get-PublicFolderAdministrativePermission [-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/Get-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md index e72bcbe253..2b1aef2051 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md @@ -13,7 +13,7 @@ title: Get-PublicFolderClientPermission # Get-PublicFolderClientPermission ## 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 Get-PublicFolderClientPermission cmdlet to retrieve the user permissions for a public folder. @@ -34,7 +34,7 @@ Get-PublicFolderClientPermission [-Identity] ## DESCRIPTION To view the permissions that are available on public folders, see [Public folder permissions for Exchange Server](https://learn.microsoft.com/exchange/troubleshoot/public-folders/public-folder-permissions-for-exchange-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/Get-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md index 9850b9ee99..4e6b5127ba 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md @@ -46,7 +46,7 @@ You can specify either the Server or Identity parameter, but not both. Only the When you run the Get-PublicFolderDatabase cmdlet with no parameters, it returns attributes of all of the public folder databases in the Exchange organization. To return specific database properties (including backup and mount status information) where the Get-PublicFolderDatabase cmdlet has to contact servers directly or perform a complex or slow calculation, make sure you use the Status 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md index 291f4e40cc..877ef36542 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md @@ -13,7 +13,7 @@ title: Get-PublicFolderItemStatistics # Get-PublicFolderItemStatistics ## 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 Get-PublicFolderItemStatistics cmdlet to view information about items within a specified public folder. Information returned includes subject, last modification time, creation time, attachments, message size, and the type of item. You can use this raw information to better understand the distribution of items and item characteristics across public folders. @@ -31,7 +31,7 @@ Get-PublicFolderItemStatistics [-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/Get-PublicFolderMailboxDiagnostics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md index 066a6a5076..3c19ede799 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md @@ -13,7 +13,7 @@ title: Get-PublicFolderMailboxDiagnostics # Get-PublicFolderMailboxDiagnostics ## 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 Get-PublicFolderMailboxDiagnostics cmdlet to view event-level information about a public folder mailbox. This information can be used to troubleshoot public folder issues. @@ -32,7 +32,7 @@ Get-PublicFolderMailboxDiagnostics [-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/Get-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md index ec4334625e..ab22880711 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md @@ -13,7 +13,7 @@ title: Get-PublicFolderMailboxMigrationRequest # Get-PublicFolderMailboxMigrationRequest ## 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 Get-PublicFolderMailboxMigrationRequest cmdlet to view the status of individual jobs in public folder migration batches that were created by using the New-MigrationBatch cmdlet. @@ -49,7 +49,7 @@ The Get-PublicFolderMailboxMigrationRequest cmdlet displays the following proper - TargetMailbox: The mailbox being migrated. - Status: The current status of the job. -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/Get-PublicFolderMailboxMigrationRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md index a29a4656ab..39bb0267b1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md @@ -13,7 +13,7 @@ title: Get-PublicFolderMailboxMigrationRequestStatistics # Get-PublicFolderMailboxMigrationRequestStatistics ## 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 Get-PublicFolderMailboxMigrationRequestStatistics cmdlet to view the detailed status of individual jobs in a public folder migration batch created using New-MigrationBatch cmdlet. @@ -62,7 +62,7 @@ The Get-PublicFolderMailboxMigrationRequestStatistics cmdlet displays the follow - TargetMailbox: The mailbox being migrated. - PercentComplete: The percentage of job completion. -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/Get-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md index 14a3d3411d..0bd6706de5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md @@ -46,7 +46,7 @@ Get-PublicFolderMigrationRequest [[-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/Get-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md index e1f09381b8..61e9261c2b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md @@ -13,7 +13,7 @@ title: Get-PublicFolderMoveRequest # Get-PublicFolderMoveRequest ## 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 Get-PublicFolderMoveRequest cmdlet to view the detailed status of an ongoing public folder move that was initiated using the New-PublicFolderMoveRequest cmdlet. @@ -44,7 +44,7 @@ Get-PublicFolderMoveRequest [-BatchName ] [-HighPriority ] [-Na ## DESCRIPTION Public folder move requests are used to move public folders between public folder mailboxes. After the move request is complete, you need to update the hierarchy using the Update-PublicFolderMailbox cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -178,7 +178,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The Name parameter specifies the name of the public folder move request. If you didn't specify a name when creating the move request, PublicFolderMove will be the default name assigned to the request. +The Name parameter specifies the name of the public folder move request. If you didn't specify a name when creating the move request, PublicFolderMove is the default name assigned to the request. You can't use this parameter with the Identity parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md index bce7688ee7..a2987dd3dc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md @@ -13,7 +13,7 @@ title: Get-PublicFolderMoveRequestStatistics # Get-PublicFolderMoveRequestStatistics ## 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 Get-PublicFolderMoveRequestStatistics cmdlet to view detailed information about public folder move requests. @@ -48,7 +48,7 @@ Get-PublicFolderMoveRequestStatistics -RequestQueue [-Requ ``` ## 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/Get-PublicFolderStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md index e7fb830203..51087f7a02 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md @@ -13,7 +13,7 @@ title: Get-PublicFolderStatistics # Get-PublicFolderStatistics ## 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 Get-PublicFolderStatistics cmdlet to retrieve statistical information about public folders, such as folder size and last logon time. @@ -31,7 +31,7 @@ Get-PublicFolderStatistics [[-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/Get-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md index 06e5a73791..d96f13ebbc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md @@ -61,7 +61,7 @@ Get-QuarantineMessage ``` ## 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 @@ -167,11 +167,11 @@ Accept wildcard characters: False > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection -The EndExpiresDate parameter specifies the latest messages that will automatically be deleted from the quarantine. Use this parameter with the StartExpiresDate parameter. +The EndExpiresDate parameter specifies the latest messages that are automatically deleted from the quarantine. Use this parameter with the StartExpiresDate 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". -For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you will only see messages that will expire from the quarantine in the next three days. +For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you only see messages that are set to expire from the quarantine in the next three days. ```yaml Type: System.DateTime @@ -250,7 +250,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, `""`). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, `""`). ```yaml Type: String @@ -512,11 +512,11 @@ Accept wildcard characters: False > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection -The StartExpiresDate parameter specifies the earliest messages that will automatically be deleted from the quarantine. Use this parameter with the EndExpiresDate parameter. +The StartExpiresDate parameter specifies the earliest messages that are automatically deleted from the quarantine. Use this parameter with the EndExpiresDate 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". -For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you will only see messages that will expire from the quarantine in the next three days. +For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you only see messages that are set to expire from the quarantine in the next three days. ```yaml Type: System.DateTime @@ -538,7 +538,7 @@ The StartReceivedDate parameter specifies the earliest messages to return in the 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". -By default, if you don't use the StartReceivedDate and EndReceivedDate parameters, the command will return data for the last 16 days. The maximum value for this parameter is 30 days. If you use a value that's older than 30 days, the value is ignored and only data for the last 30 days is returned. +By default, if you don't use the StartReceivedDate and EndReceivedDate parameters, the command returns data for the last 16 days. The maximum value for this parameter is 30 days. If you use a value that's older than 30 days, the value is ignored and only data for the last 30 days is returned. ```yaml Type: System.DateTime diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md index c7f2ec7c00..d3c413a69a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md @@ -15,7 +15,7 @@ title: Get-QuarantineMessageHeader ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Get-QuarantineMessageHeader cmdlet to view the message header of a quarantined message. The command will fail if the specified message is not in quarantine. +Use the Get-QuarantineMessageHeader cmdlet to view the message header of a quarantined message. The command fails if the specified message is not in quarantine. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -31,7 +31,7 @@ Get-QuarantineMessageHeader -Identity ## DESCRIPTION Standard SMTP message header syntax is described in RFC 5322. This cmdlet displays the message header exactly as it appears in the message. Individual header fields are not unfolded. -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