diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md index b07f62ef9e..dde9b592f2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md @@ -81,8 +81,8 @@ In Exchange Online, this example sets up the sharing of free/busy information wi The AccessMethod parameter specifies how the free/busy data is accessed. Valid values are: - PerUserFB: Per-user free/busy information can be requested. The free/busy data is accessed in the defined per-user free/busy proxy account or group, or in the All Exchange Servers group. This value requires a trust between the two forests, and requires you to use either the UseServiceAccount parameter or Credentials parameter. -- OrgWideFB: Only default free/busy for each user can be requested. The free/busy data is accessed in the per-user free/busy proxy account or group in the target forest. This value requires you to use either the UseServiceAccount parameter or Credentials parameter. -- OrgWideFBBasic: Free/busy sharing between tenants that are all in Exchange Online. +- OrgWideFB: Only the default free/busy for each user can be requested. The free/busy data is accessed in the per-user free/busy proxy account or group in the target forest. This value requires you to use either the UseServiceAccount parameter or Credentials parameter. This value is deprecated for accessing target forests in Exchange Online. +- OrgWideFBToken: Used for free/busy sharing between two tenants in Exchange Online. Only the default free/busy for each user can be requested. This value also requires you to set both the TargetTenantId and TargetServiceEpr parameters. - InternalProxy: The request is proxied to an Exchange server in the site that's running a later version of Exchange. - PublicFolder: This value was used to access free/busy data on Exchange Server 2003 servers. @@ -229,6 +229,8 @@ The TargetServiceEpr parameter specifies the Exchange Online Calendar Service UR - Office 365 operated by 21Vianet: partner.outlook.cn - Microsoft 365 GCC High or DoD: outlook.office365.us +You use this parameter only when the AccessMethod parameter value is OrgWideFBToken. + ```yaml Type: String Parameter Sets: (All) @@ -249,6 +251,8 @@ This parameter is available only in the cloud-based service. The TargetTenantID parameter specifies the tenant ID of the external Microsoft 365 organization that you're trying to read free/busy information from. +You use this parameter only when the AccessMethod parameter value is OrgWideFBToken. + ```yaml Type: String Parameter Sets: (All) diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md index a1d0a13841..93b66367bd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md @@ -34,7 +34,7 @@ Data encryption policy cmdlets are the Exchange Online part of Customer Key. For You can assign a data encryption policy to a mailbox by using the DataEncryptionPolicy parameter on the Set-Mailbox cmdlet in Exchange Online PowerShell. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md index 158918e113..985c0a3e68 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md @@ -30,7 +30,7 @@ Get-DeliveryAgentConnector [[-Identity] ] ## DESCRIPTION Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DetailZapReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md index 259eb9844a..71c067b620 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md @@ -48,7 +48,7 @@ If you append the command with ` | Format-List`, the following additional inform - Delivery Status - Detection Technology -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md index ba5338a4a8..db826becce 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md @@ -32,7 +32,7 @@ Get-DetailsTemplate [[-Identity] ] ## DESCRIPTION The Get-DetailsTemplate cmdlet retrieves the attributes for one or more details templates. Wildcard characters can be used when specifying the type and language of the details templates. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md index 19775f1e8f..db98febfb6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md @@ -85,7 +85,7 @@ Get-DistributionGroup [-Credential ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md index 9bd3ff56a4..fced01ba5f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md @@ -35,7 +35,7 @@ Get-DistributionGroupMember [-Identity] ## DESCRIPTION If your organization has multiple Active Directory domains, you might need to run the Set-ADServerSettings cmdlet with the ViewEntireForest parameter set to $true before running the Get-DistributionGroupMember cmdlet to view the entire forest. For more information, see Example 2. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md index 89e4889084..edabbe60c2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md @@ -29,7 +29,7 @@ Get-DkimSigningConfig [[-Identity] ] ## DESCRIPTION DKIM in Microsoft 365 is an email authentication method that uses a public key infrastructure (PKI), message headers and CNAME records in DNS to authenticate the message sender, which is stamped in the DKIM-Signature header field. DKIM helps prevent forged sender email addresses (also known as spoofing) by verifying that the domain in the From address matches the domain in the DKIM-Signature header field. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DlpDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md index 1aad6efd02..e210567039 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md @@ -61,7 +61,7 @@ The Get-DlpDetailReport cmdlet returns detailed information about specific DLP r To see DLP detection data that's aggregated per day, use the [Get-DlpDetectionsReport](https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpdetectionsreport) cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DlpDetectionsReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md index 5d9632faf6..db6246c871 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md @@ -53,7 +53,7 @@ To see all of these columns (width issues), write the output to a file. For exam To see detailed information about each DLP rule match, use the Get-DlpDetailReport cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DlpIncidentDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md index 6b5f5fb3b1..e5e31d5ac0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md @@ -66,7 +66,7 @@ The output of the Get-DlpIncidentDetailReport cmdlet includes the following prop - SensitiveInformationCountList - SensitiveInformationConfidenceList -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md index 65c660582f..e211930a67 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md @@ -30,7 +30,7 @@ Get-DlpPolicy [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md index b3260543ef..7152f5927d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md @@ -30,7 +30,7 @@ Get-DlpPolicyTemplate [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DnssecStatusForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md index 282963d2eb..db6ed9f581 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md @@ -34,7 +34,7 @@ Get-DnssecStatusForVerifiedDomain [-DomainName] ## DESCRIPTION For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DomainController.md b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md index 5ef1c821e9..17becbdbe3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md @@ -40,7 +40,7 @@ Get-DomainController [-DomainName ] The Get-DomainController cmdlet is used by the Exchange admin center to populate fields that display domain controller information. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md index 85d20b7657..5b6aa5a8d5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md @@ -90,7 +90,7 @@ Get-DynamicDistributionGroup [-ManagedBy ] ## DESCRIPTION A dynamic distribution group queries mail-enabled objects and builds the group membership based on the results. The group membership is recalculated whenever an email message is sent to the group. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-DynamicDistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md index 73b6f4ac35..52dea07cde 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md @@ -32,7 +32,7 @@ Get-DynamicDistributionGroupMember [-Identity] ] ## DESCRIPTION For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md index a892d29bdf..f16142ba9d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md @@ -42,7 +42,7 @@ Get-EcpVirtualDirectory [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md index 0bcc05c3a9..848fef4f46 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md @@ -30,7 +30,7 @@ Get-EdgeSubscription [[-Identity] ] ## DESCRIPTION Run the Get-EdgeSubscription cmdlet on an Exchange server in your organization. This cmdlet retrieves the list of Edge Subscriptions. Each Edge Transport server that's subscribed to the Exchange organization has a separate Edge Subscription. You can use this cmdlet to view the Edge Subscription information for a specific Edge Transport server. You can also use this cmdlet to view the Edge Subscription information for all Edge Transport servers subscribed to Active Directory sites. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md index d10d31d535..cf67707480 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md @@ -29,7 +29,7 @@ Get-EdgeSyncServiceConfig [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-EligibleDistributionGroupForMigration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md index 85571cd4b0..18f1ca9705 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md @@ -38,7 +38,7 @@ Get-EligibleDistributionGroupForMigration [-ManagedBy ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-EmailTenantSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md index 48232a093d..f8e70e2a35 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md @@ -26,7 +26,7 @@ Get-EmailTenantSettings [[-Identity] ] [] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md index 0e6199f755..28431d01ac 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md @@ -36,7 +36,7 @@ Get-EventLogLevel [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-EventsFromEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md index 25832eb908..52e03a6dbd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md @@ -29,7 +29,7 @@ Get-EventsFromEmailConfiguration [-Identity] ## DESCRIPTION **Note**: The following output properties have been deprecated: EventReservationProcessingLevel, FoodEstablishmentReservationProcessingLevel, InvoiceProcessingLevel, and ServiceReservationProcessingLevel. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md index ab03c82edf..41ba1e52ca 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md @@ -28,7 +28,7 @@ Get-ExchangeAssistanceConfig [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md index 0931257c1a..1a7503a3a4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md @@ -92,7 +92,7 @@ If you append ` | Format-List *` to the command, the cmdlet returns these additi - SubjectName: Typically, this value is System.Security.Cryptography.X509Certificates.X500DistinguishedName. - Version: Typically, this value is 3. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExchangeDiagnosticInfo.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md index f0d225dc85..8bf3fbf192 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md @@ -31,7 +31,7 @@ Get-ExchangeDiagnosticInfo [-Argument ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md index 66aa3b8ac0..b9e03ef705 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md @@ -31,7 +31,7 @@ Get-ExchangeFeature [-Identity ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md index 0765cedd81..c98652453b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md @@ -42,7 +42,7 @@ Get-ExchangeServer [[-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 Exchange 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 article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExchangeServerAccessLicense.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md index 3bb1ee430a..f9685a6836 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md @@ -33,7 +33,7 @@ The Get-ExchangeServerAccessLicense cmdlet returns a collection of these license - Exchange Server Standard Edition - Exchange Server Enterprise Edition -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExchangeServerAccessLicenseUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md index eb7f39eb5d..983741a576 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md @@ -29,7 +29,7 @@ Get-ExchangeServerAccessLicenseUser -LicenseName ## DESCRIPTION The Get-ExchangeServerAccessLicenseUser cmdlet returns a collection of unique users for the specified license name. The list of unique users represents an estimate of your licenses when you run this cmdlet. Each object contains the FQDN or primary SMTP address of the mailbox and the license name to which it's associated. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md index d1d449f8f3..b3c862a120 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md @@ -40,7 +40,7 @@ Get-ExchangeSettings [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExoInformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md index c7bf951bbb..39d0c63f23 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md @@ -26,7 +26,7 @@ Get-ExoInformationBarrierPolicy [[-Identity] ] [-ShowF ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExoInformationBarrierRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md index 77602601cd..1adfb6db00 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md @@ -27,7 +27,7 @@ Get-ExoInformationBarrierRelationship -RecipientId1 -Reci ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExoInformationBarrierSegment.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md index b66215c355..4abb7a13a8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md @@ -26,7 +26,7 @@ Get-ExoInformationBarrierSegment [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md index 3d42a3cbcf..958273ae8c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md @@ -31,7 +31,7 @@ Get-ExoSecOpsOverrideRule [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ExternalInOutlook.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md index b33e844ca7..4a833e7025 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md @@ -31,7 +31,7 @@ The important properties that are returned in the output of this cmdlet are: - Enabled: True means the feature is enabled; False means the feature is disabled. - AllowList: The list of exceptions. Messages received from the specified senders or senders in the specified domains don't receive the External icon in the area of subject line. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-FailedContentIndexDocuments.md b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md index e86dea6e67..5bfda847f8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md @@ -71,7 +71,7 @@ After a new filter is installed, only new messages with attachments of the type The cmdlet output provides details about items in a mailbox that couldn't be indexed, including an error code and the reason for failure. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-FederatedDomainProof.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md index 4fe0da6daa..4885ae058c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md @@ -31,7 +31,7 @@ Get-FederatedDomainProof -DomainName ## DESCRIPTION The Get-FederatedDomainProof cmdlet generates a cryptographically secure string for the domain used for federated sharing. The resulting string is used to manually configure a text (TXT) record in the Domain Name System (DNS) zone for the domain used by the administrator when running the cmdlet. A TXT record needs to be added to DNS for all accepted domains used for federated sharing. If the thumbprint of a certificate isn't provided, the task generates strings for all the certificates currently configured for the federation trust. Upon initial configuration of federated sharing, the proof string generated for the current certificate needs to be put into the TXT record for the federated domain in DNS. We recommend you update the TXT records whenever a new certificate is configured for the federation trust. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md index 47e2fce1d9..aedaada0b0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md @@ -31,7 +31,7 @@ Get-FederatedOrganizationIdentifier [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-FederationInformation.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md index c270d36671..cbc458cea9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md @@ -35,7 +35,7 @@ Get-FederationInformation -DomainName ## DESCRIPTION The Get-FederationInformation cmdlet retrieves federation information from the specified domain, which should have federation enabled. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md index 56f0ba4831..a6583ce2f7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md @@ -28,7 +28,7 @@ Get-FederationTrust [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-FocusedInbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md index b1f7e2b8ea..bf5e31049a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md @@ -30,7 +30,7 @@ Get-FocusedInbox -Identity ## DESCRIPTION Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md index 6aa7779b61..e2055e5041 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md @@ -28,7 +28,7 @@ Get-ForeignConnector [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md index 0e1874937a..ff407fa6e7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md @@ -30,7 +30,7 @@ Get-FrontendTransportService [[-Identity] ] ## DESCRIPTION The Front End Transport service acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange organization. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md index 71b37b5867..9f93791074 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md @@ -40,7 +40,7 @@ Get-GlobalAddressList [[-Identity] ] ## DESCRIPTION The Get-GlobalAddressList cmdlet is mainly used to populate the GAL property pages in the Exchange admin center. This command doesn't provide a filtering capability. If filtering is required, you should use a WHERE clause with the command. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md index 5b523b365d..75a07338cb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md @@ -27,7 +27,7 @@ Get-GlobalMonitoringOverride [-DomainController ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-Group.md b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md index 7a8fd3d370..175c1c7ad4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md @@ -54,7 +54,7 @@ Get-Group [[-Identity] ] ## DESCRIPTION The Get-Group cmdlet returns no mail-related properties for distribution groups or mail-enabled security groups, and no role group-related properties for role groups. To view the object-specific properties for a group, you need to use the corresponding cmdlet based on the object type (for example, Get-DistributionGroup or Get-RoleGroup). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-HealthReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md index b729e36b53..8629351a23 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md @@ -41,7 +41,7 @@ The following list contains the health values that are returned: - Functional - Unavailable -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-HistoricalSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md index 97064d9895..3f1e3f33d2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md @@ -29,7 +29,7 @@ Get-HistoricalSearch [-JobId ] ## DESCRIPTION A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are less than 90 days old. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md index 9207a2a0e7..6a277a7fed 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md @@ -27,7 +27,7 @@ Get-HostedConnectionFilterPolicy [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md index 3259b337b8..c1b6455966 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md @@ -27,7 +27,7 @@ Get-HostedOutboundSpamFilterPolicy [-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md index f1c086874f..2d7cd5fc46 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md @@ -27,7 +27,7 @@ Get-HybridConfiguration [-DomainController ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-IPv6StatusForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md index 341dfde6a7..8315774650 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md @@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or 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] > diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md index 4e66c8198d..34e73d32b3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md @@ -29,7 +29,7 @@ Get-IRMConfiguration [-DomainController ] ## DESCRIPTION The Get-IRMConfiguration cmdlet provides details about the current IRM configuration, including whether individual IRM features are enabled or disabled and provides the URLs used for ServiceLocation, PublishingLocation and LicensingLocation. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ImapSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md index 3e3bc98b54..aa7c94f41a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md @@ -28,7 +28,7 @@ Get-ImapSettings [-DomainController ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md index 0dc6a2864e..cc7b89664c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md @@ -30,7 +30,7 @@ Get-InboundConnector [[-Identity] ] ## DESCRIPTION Inbound connectors accept email messages from remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md index 13da496b00..d534f407cd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md @@ -37,7 +37,7 @@ Get-InboxRule [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or 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**: This cmdlet doesn't work for members of View-Only Organization Management role group in Exchange Online or the Global Reader role in Microsoft Entra ID. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md index 3c8a1400ef..c604bab845 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md @@ -31,7 +31,7 @@ A hybrid Exchange deployment results in one logical organization made up of a nu Hybrid environments are enabled by Intra-Organization connectors. The connectors can be created and managed by cmdlets like New-IntraOrganizationConnector, but we strongly recommend that you use the Hybrid Configuration wizard when configuring a hybrid deployment with an Exchange Online organization. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md index f8c1970bfe..e1f54a76a5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md @@ -30,7 +30,7 @@ Get-IntraOrganizationConnector [[-Identity] ] ## DESCRIPTION The Get-JournalRule cmdlet displays journal rules configured in your organization. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-LinkedUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md index b75371ad04..cc39479866 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md @@ -42,7 +42,7 @@ Get-LinkedUser [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-LogonStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md index b688ec17cc..d64ba0f423 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md @@ -47,7 +47,7 @@ The Get-LogonStatistics cmdlet retrieves logon information about currently activ Users who log on to their mailboxes using Microsoft Office Outlook Web App aren't continually connected to the Mailbox server. An Outlook Web App client connects to the server, performs tasks, and then disconnects from the server. Therefore, you might see few or no logon statistics for Outlook Web App, even if users are logged on with this client. -You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you might not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Recipient Provisioning Permissions" section in the Mailbox Permissions topic. +You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you might not have access to some parameters if they aren't included in the permissions assigned to you. To see what permissions you need, see the "Recipient Provisioning Permissions" section in the Mailbox Permissions topic. ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md index 5fd747c8bd..1208f2a526 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md @@ -34,7 +34,7 @@ M365 data-at-rest encryption policy cmdlets are accessible to compliance adminis You can create and assign a Microsoft 365 data-at-rest encryption policy at the tenant level by using the appropriate M365DataAtRestEncryptionPolicy cmdlets in Exchange Online PowerShell. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md index a27e3b6d3f..a069af8112 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md @@ -28,7 +28,7 @@ Get-M365DataAtRestEncryptionPolicyAssignment [] ## DESCRIPTION This cmdlet lists the Microsoft 365 data-at-rest encryption policy that's currently assigned to the tenant. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-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-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md index 8025e351a4..b1f77201f7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md @@ -168,7 +168,7 @@ Get-Mailbox [-MailboxPlan ] ## DESCRIPTION When you use the Get-Mailbox cmdlet in on-premises Exchange environments to view the quota settings for a mailbox, you first need to check the value of the UseDatabaseQuotaDefaults property. The value True means per-mailbox quota settings are ignored, and you need to use the Get-MailboxDatabase cmdlet to see the actual values. If the UseDatabaseQuotaDefaults property is False, the per-mailbox quota settings are used, so what you see with the Get-Mailbox cmdlet are the actual quota values for the mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md index 6085bdb0ae..909b2e8062 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md @@ -13,7 +13,7 @@ title: Get-MailboxAuditBypassAssociation # Get-MailboxAuditBypassAssociation ## 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-MailboxAuditBypassAssociation cmdlet to retrieve information about the AuditBypassEnabled property value for user accounts (on-premises Exchange and the cloud) and computer accounts (on-premises Exchange only). You use the [Set-MailboxAuditBypassAssociation](https://learn.microsoft.com/powershell/module/exchangepowershell/set-mailboxauditbypassassociation) cmdlet to enable this property to bypass mailbox audit logging. @@ -31,7 +31,7 @@ Get-MailboxAuditBypassAssociation [[-Identity] ## DESCRIPTION The Get-MailboxCalendarFolder cmdlet retrieves information for the specified calendar folder. This information includes the calendar folder name, whether the folder is currently published or shared, the start and end range of calendar days published, the level of details published for the calendar, whether the published URL of the calendar can be searched on the web and the published URL for the calendar. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md index d0c9fca722..91f420193f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md @@ -55,7 +55,7 @@ The following list describes the properties that are returned in the results. - Recovery: Specifies whether the new database is designated as a recovery database. - ReplicationType: Replication type of the database. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-MailboxDatabaseCopyStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md index 90105c739e..e4b66a20fa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md @@ -47,7 +47,7 @@ Get-MailboxDatabaseCopyStatus [[-Identity] ] ## DESCRIPTION If a database is specified by using the Identity parameter with the command, the status of all copies of the database is returned. If a server is specified by using the Server parameter with the command, information about all database copies on the server is returned. If neither parameter is specified with the command, information about all database copies in the 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 @@ -132,7 +132,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md index 15d115b5e7..ea3af86b8e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md @@ -64,7 +64,7 @@ Get-MailboxExportRequest [-Mailbox ] ## DESCRIPTION The search criteria for the Get-MailboxExportRequest cmdlet is a Boolean And statement. If you use multiple parameters, you narrow your search and reduce 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 @@ -94,7 +94,7 @@ This example returns the status of export requests in the Attachment\_CompanyRep Get-MailboxExportRequest -Name "DB01toPST" -Suspend $true ``` -This example returns all export requests that have the name DB01toPST where the export has been suspended. +This example returns all export requests that have the name DB01toPST where the export is suspended. ## PARAMETERS @@ -308,7 +308,7 @@ The Status parameter filters the results based on status. You can use the follow You can't use this parameter with the Identity parameter. -CompletionInProgress and AutoSuspended don't apply to export requests and won't return any information. +CompletionInProgress and AutoSuspended don't apply to export requests and doesn't return any information. ```yaml Type: RequestStatus diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md index d5f0ed8fe8..5877037fe2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md @@ -58,7 +58,7 @@ Get-MailboxExportRequestStatistics -RequestQueue ## DESCRIPTION You can pipeline the Get-MailboxExportRequestStatistics cmdlet from the Get-MailboxExportRequest 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 @@ -88,14 +88,14 @@ This example returns additional information about the export request for Tony Sm Get-MailboxExportRequestStatistics -MRSInstance CAS01.contoso.com ``` -In Exchange Server 2010, this example returns default statistics for an export request being processed by the instance of MRS running on the server CAS01. This command only returns information for export requests that are currently being processed by an instance of MRS. If the request is already finished, it won't be returned. +In Exchange Server 2010, this example returns default statistics for an export request being processed by the instance of MRS running on the server CAS01. This command only returns information for export requests that are currently being processed by an instance of MRS. If the request is already finished, no information is returned. ### Example 5 ```powershell Get-MailboxExportRequestStatistics -RequestQueue MailboxDatabase01 ``` -This example returns default statistics for an export request being processed by the instance of MRS running on the server CAS01. This command only returns information for export requests currently being processed by an instance of MRS. If the request is already finished, it won't be returned. +This example returns default statistics for an export request being processed by the instance of MRS running on the server CAS01. This command only returns information for export requests currently being processed by an instance of MRS. If the request is already finished, no information is returned. ### Example 6 ```powershell diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md index 4f0450521d..681bdd6120 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md @@ -13,7 +13,7 @@ title: Get-MailboxFolder # Get-MailboxFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-MailboxFolder cmdlet to view folders in your own mailbox. Administrators can't use this cmdlet to view folders in other mailboxes (the cmdlet is available only from the MyBaseOptions user role). @@ -44,7 +44,7 @@ Get-MailboxFolder [[-Identity] ] ## DESCRIPTION This command checks that the mailbox specified in the Identity parameter is a valid Exchange mailbox before retrieving the requested folders. The cmdlet returns all folders if the MailFolderOnly switch isn't specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md index 45768bf0e7..198d611d27 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md @@ -13,7 +13,7 @@ title: Get-MailboxFolderPermission # Get-MailboxFolderPermission ## 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-MailboxFolderPermission cmdlet to view folder-level permissions in mailboxes. @@ -35,7 +35,7 @@ Get-MailboxFolderPermission [-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-MailboxFolderStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md index 51eb753990..7bd91cd3c4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md @@ -13,7 +13,7 @@ title: Get-MailboxFolderStatistics # Get-MailboxFolderStatistics ## 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-MailboxFolderStatistics cmdlet to retrieve information about the folders in a specified mailbox, including the number and size of items in the folder, the folder name and ID, and other information. @@ -68,7 +68,7 @@ Get-MailboxFolderStatistics -Database -StoreMailboxIdentit ``` ## 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). A mailbox can have hidden items that are never visible to the user and are only used by applications. The Get-MailboxFolderStatistics cmdlet can return hidden items for the following values: FolderSize, FolderAndSubfolderSize, ItemsInFolder and ItemsInFolderAndSubfolders. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md index 5988155a36..a20f74e575 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md @@ -33,7 +33,7 @@ Get-MailboxIRMAccess [[-Identity] ] > > Delegates with Full Access permission to the mailbox who don't appear in the results of this cmdlet have access to IRM-protected messages. Only Full Access delegates who are blocked from reading IRM-protected messages in the mailbox appear in the 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md index 26a0c1dd9f..0f27c0ce17 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md @@ -13,7 +13,7 @@ title: Get-MailboxImportRequest # Get-MailboxImportRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-MailboxImportRequest cmdlet to view the detailed status of an ongoing import request that was initiated using the New-MailboxImportRequest cmdlet. @@ -66,7 +66,7 @@ Get-MailboxImportRequest ## DESCRIPTION The search criteria for the Get-MailboxImportRequest cmdlet is a Boolean And statement. If you use multiple parameters, you narrow your search and reduce 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 @@ -96,7 +96,7 @@ This example returns the status of import requests in the ImportingDB1PSTs batch Get-MailboxImportRequest -Name "Recovered" -Suspend $true ``` -This example returns all import requests that have the name Recovered where the import has been suspended. +This example returns all import requests that have the name Recovered where the import is suspended. ## PARAMETERS @@ -314,7 +314,7 @@ The Status parameter filters the results based on status. You can use the follow You can't use this parameter with the Identity parameter. -CompletionInProgress and AutoSuspended don't apply to import requests and won't return any information. +CompletionInProgress and AutoSuspended don't apply to import requests and doesn't return any information. ```yaml Type: RequestStatus diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md index f2b4d0172b..9d553d04e1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md @@ -13,7 +13,7 @@ title: Get-MailboxImportRequestStatistics # Get-MailboxImportRequestStatistics ## 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-MailboxImportRequestStatistics cmdlet to view detailed information about import requests. @@ -67,7 +67,7 @@ Get-MailboxImportRequestStatistics -RequestQueue ## DESCRIPTION You can pipeline the Get-MailboxImportRequestStatistics cmdlet from the Get-MailboxImportRequest 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md index 2d93050ad9..4f7d3ec93d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md @@ -13,7 +13,7 @@ title: Get-MailboxJunkEmailConfiguration # Get-MailboxJunkEmailConfiguration ## 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-MailboxJunkEmailConfiguration cmdlet to view the junk email settings on mailboxes. @@ -43,7 +43,7 @@ The junk email settings on the mailbox are: Administrators can enable or disable the junk email rule, and configure the safelist collection on a mailbox by using the Set-MailboxJunkEmailConfiguration cmdlet. For more information, see [Configure Exchange antispam settings on mailboxes](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-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-MailboxLocation.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md index 49f45baaaf..13d0a15a7b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md @@ -13,7 +13,7 @@ title: Get-MailboxLocation # Get-MailboxLocation ## 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-MailboxLocation cmdlet to view mailbox location information in Exchange Online. @@ -53,7 +53,7 @@ Get-MailboxLocation -User ``` ## 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-MailboxMessageConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md index 973de8d9f7..c198362e18 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md @@ -13,7 +13,7 @@ title: Get-MailboxMessageConfiguration # Get-MailboxMessageConfiguration ## 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-MailboxMessageConfiguration cmdlet to view the Outlook on the web settings that are applied to specific mailboxes. @@ -38,7 +38,7 @@ The Get-MailboxMessageConfiguration cmdlet shows Outlook on the web settings for > [!NOTE] > The SignatureHtml and SignatureText parameters don't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Currently, the only way to make these parameters work again is to open a support ticket and ask to have Outlook roaming signatures disabled in your 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-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md index 46b2722ed2..6a41b26466 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md @@ -13,7 +13,7 @@ title: Get-MailboxPermission # Get-MailboxPermission ## 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-MailboxPermission cmdlet to retrieve permissions on a mailbox. @@ -64,13 +64,13 @@ By default, the following permissions are assigned to user mailboxes: - FullAccess and ReadPermission are directly assigned to NT AUTHORITY\\SELF. This entry gives a user permission to their own mailbox. - FullAccess is denied to Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permissions prevent these users and group members from opening other users' mailboxes. -- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. Note that these inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries. +- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries. - FullAccess is inherited by NT AUTHORITY\\SYSTEM and ReadPermission is inherited by NT AUTHORITY\\NETWORK. - FullAccess and ReadPermission are inherited by Exchange Servers, ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are inherited by Exchange Trusted Subsystem and ReadPermission is inherited by Managed Availability Servers. By default, other security groups and role groups inherit permissions to mailboxes based on their location (on-premises Exchange or Microsoft 365). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-MailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md index 76da58ae59..34dbb6428e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md @@ -35,7 +35,7 @@ Get-MailboxPlan [[-Identity] ] ## DESCRIPTION A mailbox plan is a template that automatically configures mailbox properties. Mailbox plans correspond to license types, and are applied when you license the user. The availability of a mailbox plan is determined by your selections when you enroll in the service and the age of your 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-MailboxRegionalConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md index a44a8b5da5..23813b7c6f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md @@ -13,7 +13,7 @@ title: Get-MailboxRegionalConfiguration # Get-MailboxRegionalConfiguration ## 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-MailboxRegionalConfiguration cmdlet to view the regional settings of a mailbox. You can view the date format, time format, time zone, and language of the mailbox. @@ -45,7 +45,7 @@ Get-MailboxRegionalConfiguration [-MailboxLocation ] ## DESCRIPTION To modify the regional settings of a mailbox, use the [Set-MailboxRegionalConfiguration](https://learn.microsoft.com/powershell/module/exchangepowershell/set-mailboxregionalconfiguration) 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md index d9224ee757..b7e31ea498 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md @@ -52,7 +52,7 @@ The Get-MailboxRepairRequest cmdlet displays information about mailbox repair re - The status of the repair request; values are Queued, Running, Succeeded and Failed. - The date and time when the mailbox repair request was created and when it finished. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md index 91a54258e6..9f68aae6cd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md @@ -13,7 +13,7 @@ title: Get-MailboxRestoreRequest # Get-MailboxRestoreRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-MailboxRestoreRequest cmdlet to view detailed status of an ongoing restore request that was initiated by using the New-MailboxRestoreRequest cmdlet. @@ -46,7 +46,7 @@ Get-MailboxRestoreRequest [-BatchName ] ``` ## 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 @@ -76,7 +76,7 @@ This example returns the status of in-progress and queued restore requests that Get-MailboxRestoreRequest -Name "RestoreToMBD01" -Suspend $true ``` -This example returns all restore requests that have the name RestoreToMBD01 where the restore request has been suspended. +This example returns all restore requests that have the name RestoreToMBD01 where the restore request is suspended. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md index cf05e6387b..9ef9b9e6e7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md @@ -13,7 +13,7 @@ title: Get-MailboxRestoreRequestStatistics # Get-MailboxRestoreRequestStatistics ## 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-MailboxRestoreRequestStatistics cmdlet to view detailed information about restore requests. @@ -63,7 +63,7 @@ Get-MailboxRestoreRequestStatistics -RequestQueue ``` ## 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md index b36d1fde0f..e4136578f7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md @@ -30,7 +30,7 @@ Get-QuarantinePolicy [[-Identity] ] ## DESCRIPTION Quarantine policies define what users are allowed to do to quarantined messages based on why the message was quarantined (for supported features) and quarantine notification settings. For more information, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -85,7 +85,7 @@ Accept wildcard characters: False The QuarantinePolicyType parameter filters the results by the specified quarantine policy type. Valid values are: -- QuarantinePolicy: This is the default value, and returns built-in and custom quarantine policies. +- QuarantinePolicy: This value is the default, and returns built-in and custom quarantine policies. - GlobalQuarantinePolicy: This value is required to return the global settings (quarantine notification settings) in the quarantine policy named DefaultGlobalTag. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md index a05d1686df..02f901b65b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md @@ -53,7 +53,7 @@ Get-Queue [-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-QueueDigest.md b/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md index c4277836aa..3e658ea466 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md @@ -68,7 +68,7 @@ Get-QueueDigest -Site ``` ## 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-RMSTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md index a4ee2746eb..dcd9a4ad30 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md @@ -13,7 +13,7 @@ title: Get-RMSTemplate # Get-RMSTemplate ## 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-RMSTemplate cmdlet to retrieve the current list of active rights policy templates from the Active Directory Rights Management Services (AD RMS) deployment for the organization. @@ -33,7 +33,7 @@ Get-RMSTemplate [[-Identity] ] ## DESCRIPTION The Get-RMSTemplate cmdlet doesn't return any active rights policy templates if internal licensing isn't enabled. Use the Get-IRMConfiguration cmdlet to check the InternalLicensingEnabled 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-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md index fe560729f4..1405cdb418 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md @@ -38,7 +38,7 @@ Get-ReceiveConnector [-Server ] ## DESCRIPTION You can view Receive connectors on Mailbox servers and Edge Transport servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md b/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md index 4497518c48..fb5e831977 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md @@ -13,7 +13,7 @@ title: Get-Recipient # Get-Recipient ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-Recipient cmdlet to view existing recipient objects in your organization. This cmdlet returns all mail-enabled objects (for example, mailboxes, mail users, mail contacts, and distribution groups). @@ -115,9 +115,9 @@ Get-Recipient [-RecipientPreviewFilter ] ``` ## DESCRIPTION -The Get-Recipient cmdlet may not return all object-specific properties for a recipient. To view the object-specific properties for a recipient, you need to use the corresponding cmdlet based on the object type (for example, Get-Mailbox, Get-MailUser, or Get-DistributionGroup). +The Get-Recipient cmdlet might not return all object-specific properties for a recipient. To view the object-specific properties for a recipient, you need to use the corresponding cmdlet based on the object type (for example, Get-Mailbox, Get-MailUser, or Get-DistributionGroup). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -599,7 +599,7 @@ The RecipientTypeDetails parameter filters the results by the specified recipien You can specify multiple values separated by commas. -The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You'll receive the error: None of the specified RecipientTypeDetails are included in any specified recipient type. +The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You get the error: None of the specified RecipientTypeDetails are included in any specified recipient type. ```yaml Type: RecipientTypeDetails[] diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md index 050feb8da1..bba82d81ec 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md @@ -28,7 +28,7 @@ Get-RecipientFilterConfig [[-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-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md index 65d31fe008..a5c68f73cf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md @@ -38,7 +38,7 @@ When a user is given SendAs permission to another user or group, the user can se > [!NOTE] > This cmdlet doesn't return expected results when the recipient specified by the Trustee parameter has multiple `SecurityPrincipalIdParameter` (Sid) values. When you use the Trustee parameter, the command compares the Sid of the specified Trustee with the recipient's access control list (ACL) record. If some of the recipient's Sid values have changed, there's a mismatch. The workaround is to not to use the user principal name (UPN) value, to use all Sids including the one for history. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-RecipientStatisticsReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md index e11d4e6142..aa8daee7d8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md @@ -28,7 +28,7 @@ Get-RecipientStatisticsReport [] ## DESCRIPTION The recipient statistics report provides information about the total number of mailboxes and the total number of active mailboxes in the 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-RecoverableItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md index 796b999fed..8d5b5d87bb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md @@ -12,7 +12,7 @@ title: Get-RecoverableItems # Get-RecoverableItems ## 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-RecoverableItems items cmdlet to view deleted items in mailboxes. After you find the deleted items, you use the Restore-RecoverableItems cmdlet to restore them. @@ -54,7 +54,7 @@ Get-RecoverableItems -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-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md index 8fa4cd2d7e..7244b020da 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md @@ -13,7 +13,7 @@ title: Get-RemoteDomain # Get-RemoteDomain ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-RemoteDomain cmdlet to view the configuration information for the remote domains configured in your organization. You can view the remote domain configuration from inside the Exchange organization or from an Edge Transport server in the perimeter network. @@ -29,7 +29,7 @@ Get-RemoteDomain [[-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-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md index 288f6d8327..b68d619e0f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md @@ -52,7 +52,7 @@ Get-RemoteMailbox [[-Identity] ] ## DESCRIPTION The Get-RemoteMailbox cmdlet retrieves the mail-related attributes of a mail user in the on-premises Active Directory. It doesn't retrieve the attributes of the associated cloud-based mailbox. Most of the mail-related attributes of the on-premises mail user and the associated cloud-based mailbox should be the same. However, the cloud-based mailbox has additional attributes that you can't view by using this cmdlet. To view the attributes of the cloud-based mailbox, you need to use the Exchange admin center in the cloud-based service, or connect to your cloud-based organization and run the Get-Mailbox 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md index 8c2a4481b7..ad948f54d5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md @@ -28,7 +28,7 @@ Get-ReportExecutionInstance [-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 @@ -70,7 +70,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The ScheduleId parameter filters the results by the specified ScheduleId property value, which is a GUID. Note that multiple report execution instances can have the same ScheduleId value. +The ScheduleId parameter filters the results by the specified ScheduleId property value, which is a GUID. Multiple report execution instances can have the same ScheduleId value. ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md index 5e6ea078a9..09a5ba4f86 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md @@ -30,7 +30,7 @@ The report submission policy controls most of the settings for user submissions The report submission rule (\*-ReportSubmissionRule cmdlets) controls the email address of the reporting mailbox where user reported messages are delivered. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md index 90b8ad8b50..9761c1326e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md @@ -26,7 +26,7 @@ Get-ReportSubmissionRule [[-Identity] ] [-State ] [< ``` ## 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-ResourceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md index fc626e15b6..077decbd72 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md @@ -13,7 +13,7 @@ title: Get-ResourceConfig # Get-ResourceConfig ## 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-ResourceConfig cmdlet to view custom room and equipment mailbox properties that you've configured by using the Set-ResourceConfig cmdlet. @@ -28,7 +28,7 @@ Get-ResourceConfig [[-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-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md index aa641f4105..a4f888b146 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md @@ -28,7 +28,7 @@ Get-ResubmitRequest [[-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-RetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md index 6f0edb31bd..1e0536d222 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md @@ -37,7 +37,7 @@ Get-RetentionCompliancePolicy [[-Identity] ] This list describes the properties that are displayed by default. - Name: The unique name of the policy. -- Workload: At the moment, it will show all workloads (Exchange, SharePoint, OneDriveForBusiness, Skype, ModernGroup) and it will not show the actual workload on which the policy is applied. +- Workload: Currently, it shows all workloads (Exchange, SharePoint, OneDriveForBusiness, Skype, ModernGroup). It doesn't show the actual workload on which the policy is applied. - Enabled: The value True means the policy is enabled. - Mode: The current operating mode of the policy. The possible values are Test (the content is tested, but no rules are enforced), AuditAndNotify (when content matches the conditions specified by the policy, the rule is not enforced, but notification emails are sent) or Enforce (all aspects of the policy are enabled and enforced). diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md index e8c112c3ed..d80526413b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md @@ -29,7 +29,7 @@ Get-RetentionEvent [[-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-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md index 4b13d321a9..877c8a1f16 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md @@ -13,7 +13,7 @@ title: Get-RetentionPolicy # Get-RetentionPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-RetentionPolicy cmdlet to retrieve the settings for retention policies. @@ -28,9 +28,9 @@ Get-RetentionPolicy [[-Identity] ] ``` ## DESCRIPTION -A retention policy is associated with a group of retention policy tags that specify retention settings for items in a mailbox. A policy may contain one default policy tag to move items to an archive mailbox, one default policy tag to delete all items, one default policy tag to delete voicemail items and multiple personal tags to move or delete items. A mailbox can have only one retention policy applied to it. The Get-RetentionPolicy cmdlet displays all policy settings associated with the specified policy. +A retention policy is associated with a group of retention policy tags that specify retention settings for items in a mailbox. A policy might contain one default policy tag to move items to an archive mailbox, one default policy tag to delete all items, one default policy tag to delete voicemail items and multiple personal tags to move or delete items. A mailbox can have only one retention policy applied to it. The Get-RetentionPolicy cmdlet displays all policy settings associated with the specified 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-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md index 97f1c0a293..a76704a0e9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md @@ -13,7 +13,7 @@ title: Get-RetentionPolicyTag # Get-RetentionPolicyTag ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-RetentionPolicyTag cmdlet to retrieve settings for a retention tag. @@ -49,7 +49,7 @@ Retention tags are used to apply message retention settings to messages or folde Retention policy tags are applied to default folders such as Inbox and Deleted Items. Personal tags are available to users to tag items and folders. The default policy tag is applied to all items that don't have a tag applied by the user or aren't inherited from the folder they're located in. The Get-RetentionPolicyTag cmdlet displays all the settings for the specified tag. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ReviewItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md index 63618d7061..24f56ac095 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md @@ -32,7 +32,7 @@ Get-ReviewItems -TargetLabelId ``` ## 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). The `Get-ReviewItems` cmdlet can be used to export a list of pending or disposed items from disposition review. To learn more about disposition review, see [Disposition of content](https://learn.microsoft.com/purview/disposition). @@ -111,7 +111,7 @@ Accept wildcard characters: False The Disposed parameter specifies whether to return disposed items instead of items pending disposition. Valid values are: - $true: Return disposed items. -- $false: Return items pending disposition. This is the default value. +- $false: Return items pending disposition. This value is the default. ```yaml Type: Boolean @@ -132,7 +132,7 @@ Accept wildcard characters: False The IncludeHeaders parameter specifies whether headers are returned as a property with the review items. Valid values are: - $true: Headers are returned as a property with the review items. This option is useful when converting the output to a PSObject in PowerShell or when exporting to CSV. -- $false: Headers are not returned as a property with the review items. This is the default value. +- $false: Headers are not returned as a property with the review items. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md index 0265d8527c..ba3b5931f4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md @@ -13,7 +13,7 @@ title: Get-RoleAssignmentPolicy # Get-RoleAssignmentPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-RoleAssignmentPolicy cmdlet to view existing management role assignment policies in your organization. @@ -30,7 +30,7 @@ Get-RoleAssignmentPolicy [[-Identity] ] ## DESCRIPTION For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md index 2a63f95861..b39c089258 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md @@ -13,7 +13,7 @@ title: Get-RoleGroup # Get-RoleGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-RoleGroup cmdlet to retrieve a list of management role groups. @@ -35,7 +35,7 @@ Get-RoleGroup [[-Identity] ] ## DESCRIPTION For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md index eb04094c83..0d162d0acd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md @@ -13,7 +13,7 @@ title: Get-RoleGroupMember # Get-RoleGroupMember ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-RoleGroupMember cmdlet to retrieve a list of members of a management role group. @@ -32,7 +32,7 @@ Get-RoleGroupMember [-Identity] ## DESCRIPTION For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md index 02c53261b2..7825224008 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md @@ -30,7 +30,7 @@ Get-RoutingGroupConnector [[-Identity] ] ## DESCRIPTION The Get-RoutingGroupConnector cmdlet displays the configuration details of routing group connectors that exist when an organization is running Exchange 2010 and Exchange Server 2003. A routing group connector is used to send and receive messages between Exchange 2010 Hub Transport servers and Exchange 2003 bridgehead servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md index 558b8e2687..75649aaa67 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md @@ -28,7 +28,7 @@ Get-RpcClientAccess [-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-SCInsights.md b/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md index 4ff893c003..7482a56503 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md @@ -35,7 +35,7 @@ This cmdlet returns the following output: - InsightSubType: The value All or Archive. - UsersCount: An integer count, or the size in megabytes for the InsightType value. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md index 126fcd4417..e6b721443e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md @@ -29,7 +29,7 @@ Get-SafeAttachmentPolicy [[-Identity] ] ## DESCRIPTION Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md index d5b539c3be..d2b729ab89 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md @@ -30,7 +30,7 @@ Get-SafeAttachmentRule [[-Identity] ] ## DESCRIPTION Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SafeLinksAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md index 921116fc89..a44c75426c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md @@ -32,7 +32,7 @@ Get-SafeLinksAggregateReport ``` ## DESCRIPTION -**Note**: If you run Get-SafeLinksAggregateReport without specifying a date range, the command will return an unspecified error. +**Note**: If you run Get-SafeLinksAggregateReport without specifying a date range, the command returns an unspecified error. Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. @@ -43,7 +43,7 @@ For the reporting period you specify, the cmdlet returns the following informati - MessageCount - RecipientCount -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SafeLinksDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md index 7d26d0b6c1..1bc37e0c2f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md @@ -35,7 +35,7 @@ Get-SafeLinksDetailReport ``` ## DESCRIPTION -**Note**: If you run Get-SafeLinksDetailReport without specifying a date range, the command will return an unspecified error. +**Note**: If you run Get-SafeLinksDetailReport without specifying a date range, the command returns an unspecified error. Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. @@ -56,7 +56,7 @@ This cmdlet returns the following information: - UrlType (currently empty) - Flags (0: Allowed 1: Blocked 2: ClickedEvenBlocked 3: ClickedDuringScan) -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md index a50d913ed8..57e426f923 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md @@ -29,7 +29,7 @@ Get-SafeLinksPolicy [[-Identity] ] ## DESCRIPTION Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md index 73b94df76c..bf94afdaa2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md @@ -30,7 +30,7 @@ Get-SafeLinksRule [[-Identity] ] ## DESCRIPTION Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md index ddcea38f6a..a9c7d69dd8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md @@ -13,7 +13,7 @@ title: Get-SearchDocumentFormat # Get-SearchDocumentFormat ## 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-SearchDocumentFormat cmdlet to retrieve details of file formats supported by Exchange Search. @@ -30,7 +30,7 @@ Get-SearchDocumentFormat [[-Identity] ] ## DESCRIPTION Exchange Search includes built-in support for indexing many file formats. Output from the Get-SearchDocumentFormat cmdlet includes details about each supported file format, including whether content indexing is enabled for the file format, the format handler and the file extension (such as .docx). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md index ecff279a3f..88e85ee0b6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md @@ -28,7 +28,7 @@ Get-SecOpsOverridePolicy [[-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-SecurityPrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md index 28d3b1a44d..e79ff3157f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md @@ -13,7 +13,7 @@ title: Get-SecurityPrincipal # Get-SecurityPrincipal ## 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-SecurityPrincipal cmdlet to return a list of security principals. Security principals are entities, such as users or security groups, which can be assigned permissions and user rights. @@ -36,7 +36,7 @@ Get-SecurityPrincipal [[-Identity] ] ## DESCRIPTION The Get-SecurityPrincipal cmdlet is used by the Exchange admin center to populate fields that display recipient 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-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md index 05f88698a8..b88096e120 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md @@ -28,7 +28,7 @@ Get-SendConnector [[-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-SenderFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md index 4cf064d7b1..3a2fac09b4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md @@ -28,7 +28,7 @@ Get-SenderFilterConfig [[-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-SenderIdConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md index ec6ce1c598..a48fe97c5b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md @@ -27,7 +27,7 @@ Get-SenderIdConfig [-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-SenderReputationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md index 871add3003..8bec50233b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md @@ -27,7 +27,7 @@ Get-SenderReputationConfig [-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-ServerComponentState.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md index 5a82a37409..357deadb5d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md @@ -29,7 +29,7 @@ Get-ServerComponentState [-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-ServerHealth.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md index 3dd602e8a9..19532a3368 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md @@ -29,11 +29,11 @@ Get-ServerHealth [-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). The cmdlet returns health values that you can use to determine the state of the server. See [Server health and performance in Exchange Server](https://learn.microsoft.com/Exchange/server-health/server-health) for related information. -The cmdlet also returns an alert value that provides the specific state of your server. The following values may be returned: +The cmdlet also returns an alert value that provides the specific state of your server. The following values might be returned: - Degraded - Unhealthy diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md index 641724b1b8..afcf7555af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md @@ -27,7 +27,7 @@ Get-ServerMonitoringOverride -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-ServiceDeliveryReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md index 8b0404f1c8..2b0bbce739 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md @@ -28,7 +28,7 @@ Get-ServiceDeliveryReport [-ProbeTag ] ``` ## 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-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md index 19cfbc1188..f8d118cd49 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md @@ -32,7 +32,7 @@ Service principals exist in Microsoft Entra ID to define what apps can do, who c For more information, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md index 2fb293f518..3a53168c56 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md @@ -32,7 +32,7 @@ Get-SettingOverride [[-Identity] ] ## DESCRIPTION Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and are lost when you install the next Exchange CU. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md index 928a905807..8f7acb12f7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md @@ -13,7 +13,7 @@ title: Get-SharingPolicy # Get-SharingPolicy ## 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-SharingPolicy cmdlet to view existing sharing policies that control how users inside your organization can share free/busy and contact information with users outside your organization. @@ -28,9 +28,9 @@ Get-SharingPolicy [[-Identity] ] ``` ## DESCRIPTION -Users can only share free/busy and contact information after federation has been configured between Exchange organizations. After that, users can send sharing invitations to the external recipients as long as those invitations comply with the sharing policy. A sharing policy needs to be assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the sharing settings for the mailbox. +Users can only share free/busy and contact information after federation is configured between Exchange organizations. After that, users can send sharing invitations to the external recipients as long as those invitations comply with the sharing policy. A sharing policy needs to be assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the sharing settings for the 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-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md index 1953f1a4b1..72d4c05408 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md @@ -15,7 +15,7 @@ title: Get-SiteMailbox ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Get-SiteMailbox cmdlet to view information about site mailboxes. This cmdlet is primarily used by Microsoft SharePoint and Exchange to display information to users in the user interface. However, you may find it helpful for discovering information such as the site mailbox's owners, members, and lifecycle status. +Use the Get-SiteMailbox cmdlet to view information about site mailboxes. This cmdlet is primarily used by Microsoft SharePoint and Exchange to display information to users in the user interface. However, you mightht find it helpful for discovering information such as the site mailbox's owners, members, and lifecycle status. Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028). @@ -37,7 +37,7 @@ Get-SiteMailbox [[-Identity] ] ## DESCRIPTION If you aren't a member or owner of the site mailbox that you want to view the diagnostics information for, you must use the BypassOwnerCheck parameter when running this cmdlet. If you aren't a member or owner of the site mailbox and you run this cmdlet without using the BypassOwnerCheck parameter, the command fails with an "object not found" error. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -139,7 +139,7 @@ Accept wildcard characters: False The DeletedSiteMailbox switch returns site mailboxes that have been marked for pending deletion. You don't need to specify a value with this switch. -When the lifecycle application in SharePoint closes a site mailbox, the site mailbox is retained for the period specified in the lifecycle policy in the closed state. The mailbox can then be reactivated by an end user or by a SharePoint administrator. After the retention period, the Exchange site mailbox that's housed in the mailbox database will have its name prepended with MDEL: to indicate that it has been marked for deletion. To free storage space and the alias, use the Remove-Mailbox cmdlet to manually remove these site mailboxes from the mailbox database. +When the lifecycle application in SharePoint closes a site mailbox, the site mailbox is retained for the period specified in the lifecycle policy in the closed state. The mailbox can then be reactivated by an end user or by a SharePoint administrator. After the retention period, the name of the Exchange site mailbox housed in the mailbox database is prepended with `MDEL:` to indicate it's marked for deletion. To free storage space and the alias, use the Remove-Mailbox cmdlet to manually remove these site mailboxes from the mailbox database. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md index e868fb6ee1..89878ddd9b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md @@ -35,7 +35,7 @@ Get-SiteMailboxDiagnostics [-Identity] ## DESCRIPTION If you aren't a member or owner of the site mailbox that you want to view the diagnostics information for, you must use the BypassOwnerCheck parameter when running this cmdlet. If you aren't a member or owner of the site mailbox and you run this cmdlet without using the BypassOwnerCheck parameter, the command fails with an "object not found" error. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md index 91b294c205..aa2e7109d2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md @@ -32,7 +32,7 @@ Get-SiteMailboxProvisioningPolicy [[-Identity] ] ## DESCRIPTION Site mailboxes allow access to both Microsoft SharePoint documents and Exchange email using the same client interface. Site mailbox provisioning policies apply settings to new site mailboxes that you create. You can create multiple site mailbox provisioning policies, but only the default policy is followed when users create site mailboxes. The default site mailbox provisioning policy is named Default. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md index cdd857bd7f..248d152e27 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md @@ -13,7 +13,7 @@ title: Get-SmimeConfig # Get-SmimeConfig ## 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-SmimeConfig cmdlet to view the S/MIME configuration for Outlook on the web (formerly known as Outlook Web App). @@ -27,7 +27,7 @@ Get-SmimeConfig [[-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-SmtpDaneInboundStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md index 7c93c5cd2b..68031aabf0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md @@ -28,7 +28,7 @@ Get-SmtpDaneInboundStatus [-DomainName] [] ## DESCRIPTION For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-SpoofIntelligenceInsight.md b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md index 351bcb4516..424b908c26 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md @@ -35,7 +35,7 @@ The Get-SpoofIntelligenceInsight cmdlet returns the following information: - SpoofType: Indicates whether the domain is internal to your organization or external. - Action: The two possible values are Allow (messages that contain any spoofed sender email addresses in your organization are allowed from the source email server), and Block (messages that contain any spoofed sender email addresses in your organization are not allowed from the source email 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-SpoofMailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md index 30898b8ba5..404128c301 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md @@ -41,7 +41,7 @@ The Get-SpoofMailReport cmdlet returns the following information: - Direction: This value is Inbound. - Domain: The sender domain. This corresponds to one of your organization's accepted domains. - Spoofed User: The sending email address if the domain is one of your organization's domains, or the sending domain if the domain is external. -- True Sender: The organizational domain of the PTR record, or pointer record, of the sending IP address, also known as the reverse DNS address. If the sending IP address does not have a PTR record, this field will be blank and the Sender IP column will be filled in. Both columns will not be filled in at the same time. +- True Sender: The organizational domain of the PTR record, or pointer record, of the sending IP address, also known as the reverse DNS address. If the sending IP address does not have a PTR record, this field is blank and the Sender IP column is filled in. Both columns aren't filled in at the same time. - Sending Infrastructure: The true sending domain that's found in the DNS record of the source email server. If no domain is found, the source email server's IP address is shown. - Count: The number of spoofed messages that were sent to your organization from the source messaging server during the specified time period. - Spoof Type: The relationship between the sender and recipient domain of the spoof mail. If both belong to same domain (including subdomains) or domain owned by the same organization, then Spoof Type is intra-org or Internal. If both belong to different domains, then Spoof Type is cross-org or External. @@ -52,7 +52,7 @@ The Get-SpoofMailReport cmdlet returns the following information: - DKIM - DMARC -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-StoreUsageStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md index ecf022b35a..df48bbb8a6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md @@ -51,7 +51,7 @@ Get-StoreUsageStatistics -Server ## DESCRIPTION The Microsoft Exchange Information Store collects per-user information on latency, input/output (I/O), page counts, processor usage, and TimeInServer. The TimeInServer metric represents the total time that synchronous and asynchronous requests spend in the Microsoft Exchange Information Store for a user's mailbox. You can retrieve this resource information in the Microsoft Exchange Information Store for the 25 highest usage accounts on a specified database. Usage of a mailbox is defined as the amount of server time spent in performing operations for that mailbox. The cmdlet reports the top 25 users for every one-minute period for the last 10 minutes (250 objects per ten-minute interval). The resource usage is an indicator of the load that different users are placing on the server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md index 71f674f883..a8f88c2678 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md @@ -15,7 +15,7 @@ title: Get-SupervisoryReviewActivity ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Get-SupervisoryReviewActivity cmdlet to view all activities performed by a reviewer for a specific supervision policy. This information may be useful if reviewer activities are required in regulatory compliance audits or in litigation. +Use the Get-SupervisoryReviewActivity cmdlet to view all activities performed by a reviewer for a specific supervision policy. This information might be useful if reviewer activities are required in regulatory compliance audits or in litigation. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -27,7 +27,7 @@ Get-SupervisoryReviewActivity -EndDate -PolicyId -StartDat ``` ## 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-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md index 4a56442e92..55817a5d14 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md @@ -13,7 +13,7 @@ title: Get-SweepRule # Get-SweepRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-SweepRule cmdlet to view Sweep rules in mailboxes. Sweep rules run at regular intervals to help keep your Inbox clean. @@ -32,7 +32,7 @@ Get-SweepRule [[-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-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md index 86e3e2f970..f04bf393c2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md @@ -38,7 +38,7 @@ Get-SystemMessage [-Original] ## DESCRIPTION NDRs are issued to the senders of email messages that haven't reached their intended recipients. Quota messages are issued to users whose mailboxes or public folders have reached the specific warning, prohibit send, or prohibit receive quotas. Custom NDRs and quota messages replace the default messages that are included with Exchange. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -70,7 +70,7 @@ Get-SystemMessage -Original | Select-Object -Property Identity,DsnCode,Language, This example outputs the list of all default system messages in all languages to an HTML file named C:\\My Documents\\Default System Messages.html. -You should output the list to a file, because the list is very long, and you'll receive errors if you don't have the required language packs installed. +You should output the list to a file, because the list is very long, and you get errors if you don't have the required language packs installed. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md index b7738fa384..eb40e3fa30 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md @@ -27,7 +27,7 @@ Get-TeamsProtectionPolicy [[-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-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md index ce99649cfb..25bfac1144 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md @@ -28,7 +28,7 @@ Get-TeamsProtectionPolicyRule [[-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-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md index 2281e8eb73..cf8b01b151 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md @@ -44,7 +44,7 @@ Get-TenantAllowBlockListItems -ListType [-NoExpiration] ``` ## 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 @@ -203,7 +203,7 @@ Accept wildcard characters: False The ListSubType parameter filters the results by subtype. Valid values are: - AdvancedDelivery -- Tenant: This is the default value. +- Tenant: This value is the default. ```yaml Type: ListSubType[] diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md index 4a6937ad9f..ce29b5cd5d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md @@ -31,13 +31,13 @@ Get-TenantAllowBlockListSpoofItems [[-Identity] ## DESCRIPTION When text messaging notifications are enabled on a mailbox, you can configure calendar notifications, voice mail notifications, and email notifications using an inbox rule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md index f3cb66dd00..43844b9234 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md @@ -35,7 +35,7 @@ The Get-ThrottlingPolicy cmdlet returns the client throttling settings for one o For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md index 77d4935205..8ba0ee4aea 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md @@ -44,7 +44,7 @@ Get-ThrottlingPolicyAssociation [[-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-TransportConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md index 02598b341e..ffef43d5a4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md @@ -13,7 +13,7 @@ title: Get-TransportConfig # Get-TransportConfig ## 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-TransportConfig cmdlet to view organization-wide transport configuration settings. @@ -30,7 +30,7 @@ Get-TransportConfig [[-Identity] ] ## DESCRIPTION The Get-TransportConfig cmdlet displays configuration information for global transport settings applied across the organization when the cmdlet is run on a Mailbox server. When this cmdlet is run on an Edge Transport server, only the transportation configuration settings for the local computer are shown. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-TransportPipeline.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md index f475a86fd2..31d4c51174 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md @@ -35,7 +35,7 @@ The Get-TransportPipeline cmdlet enables you to view all the transport agents th The associated transport service must be started and at least one email message must be sent through the server since the last service restart before the transport pipeline can be viewed. Only the transport events and agents that were involved in the processing of email messages since the associated service was last started are 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-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md index f0b41ab022..00a45e85c7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md @@ -13,7 +13,7 @@ title: Get-TransportRule # Get-TransportRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-TransportRule cmdlet to view transport rules (mail flow rules) in your organization. @@ -35,7 +35,7 @@ Get-TransportRule [[-Identity] ] ## DESCRIPTION On Mailbox servers, this cmdlet returns all rules in the Exchange organization that are stored in Active Directory. On an Edge Transport server, this cmdlet only returns rules that are configured on the local 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 @@ -169,7 +169,7 @@ This parameter is available only in the cloud-based service. The ExcludeConditionActionDetails parameter specifies whether to hide specific details from the results. Valid values are: - $true: The Description, Conditions, and Actions properties, as well as any configured condition, exception and action property values are blank. -- $false: No properties or property values are hidden. This is the default value. +- $false: No properties or property values are hidden. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md index 356cfd7f34..5d266e9ba2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md @@ -13,7 +13,7 @@ title: Get-TransportRuleAction # Get-TransportRuleAction ## 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-TransportRuleAction cmdlet to view the actions that are available for transport rules (mail flow rules). @@ -29,7 +29,7 @@ Get-TransportRuleAction [[-Name] ] ## DESCRIPTION In on-premises Exchange, the actions that are available on Mailboxes servers and Edge Transports server are different. Also, the names of some of the actions that are returned by this cmdlet are different than the corresponding parameter names in the New-TransportRule and Set-TransportRule 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md index 002d434fe7..0a039b0a93 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md @@ -13,7 +13,7 @@ title: Get-TransportRulePredicate # Get-TransportRulePredicate ## 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-TransportRulePredicate cmdlet to view the predicates (conditions and exceptions) that are available for transport rules (mal flow rules). @@ -31,7 +31,7 @@ Collectively, the conditions and exceptions in rules are known as predicates, be In on-premises Exchange, the predicates that are available on Mailboxes servers and Edge Transports server are different. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-TransportServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md index be4676662a..c4e3d2faa6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md @@ -30,7 +30,7 @@ Get-TransportServer [[-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-TransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md index a7da169a33..2f68807ab2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md @@ -28,7 +28,7 @@ Get-TransportService [[-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-Trust.md b/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md index 035a77f9d4..a188003b37 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md @@ -29,7 +29,7 @@ Get-Trust [-DomainName ] ## DESCRIPTION The Get-Trust cmdlet is used by the Exchange admin center in to populate fields that display recipient 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-UMActiveCalls.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md index 291c7a984f..3b5c18f829 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md @@ -56,7 +56,7 @@ When a Mailbox server is process cycling, the Get-UMActiveCalls cmdlet doesn't r After this task is completed, you can see the list of active calls being processed by a Mailbox 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-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md index f8dd5e3588..573e07b1cb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md @@ -33,7 +33,7 @@ The Get-UMAutoAttendant cmdlet retrieves the properties for a single UM auto att After this task is completed, if no parameter is supplied with the cmdlet, the cmdlet returns all UM auto attendants in the Active Directory forest. Or, if the UM dial plan ID is supplied but no name is supplied, the cmdlet returns all UM auto attendants linked to the UM dial plan. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md index 0c79f7fbfd..bc5e76e829 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md @@ -15,7 +15,7 @@ title: Get-UMCallAnsweringRule ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Get-UMCallAnsweringRule cmdlet to view the properties of a Unified Messaging (UM) call answering rule that has been created within a UM-enabled mailbox. +Use the Get-UMCallAnsweringRule cmdlet to view the properties of a Unified Messaging (UM) call answering rule that is created within a UM-enabled mailbox. 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,11 +29,11 @@ Get-UMCallAnsweringRule [[-Identity] ] ``` ## DESCRIPTION -The Get-UMCallAnsweringRule cmdlet enables you to view the properties of a call answering rule that has been created in a UM-enabled user's mailbox. It allows you to retrieve the properties for a single call answering rule or a list of call answering rules in a UM-enabled user's mailbox. +The Get-UMCallAnsweringRule cmdlet enables you to view the properties of a call answering rule that is created in a UM-enabled user's mailbox. It allows you to retrieve the properties for a single call answering rule or a list of call answering rules in a UM-enabled user's mailbox. After this task is completed, the cmdlet returns the parameters and the values specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md index ff1aaeaeeb..194e7797f1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md @@ -31,7 +31,7 @@ Get-UMCallDataRecord -Mailbox The Get-UMCallDataRecord cmdlet displays UM call data records for the last 90 days for a UM-enabled mailbox that you specify. Each UM call data record provides detailed information about all calls either placed to or received by the specified user. The following list details each of the properties that are returned: - Date: Date and time of the Mailbox server running the Microsoft Exchange Unified Messaging service that took the call in the Coordinated Universal Time (UTC) format. -- Duration: Total duration of this call. For Find Me calls, this will always be zero because the call is being transferred and won't be handled by Unified Messaging any longer. +- Duration: Total duration of this call. For Find Me calls, this value is always zero because the call is being transferred and is no longer handled by Unified Messaging. - AudioCodec: Audio codec used for the call including G.711 or Group System Mobile (GSM). - DialPlan: Name of the UM dial plan handling the call. - CallType: Type of the call (localized in the user's language): Call Answering Voice Message, Call Answering Missed Call, , Auto Attendant, Subscriber Access, Fax, PlayOnPhone, Find Me, None, UnauthenticatedPilotNumber, or PromptProvisioning. @@ -45,7 +45,7 @@ The Get-UMCallDataRecord cmdlet displays UM call data records for the last 90 da - RoundTripMilliseconds: Round trip time for Real Time Control Protocol (RTCP) statistics in milliseconds. - BurstLossDurationMilliseconds: Average duration of packet loss during bursts during the call. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-UMCallRouterSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md index 45deb8cca3..52e4f24797 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md @@ -30,7 +30,7 @@ Get-UMCallRouterSettings [[-Server] ] ## DESCRIPTION When the cmdlet is used for a single server, it returns the UM call router properties including MaxCalls, MaxFaxCalls and UMDialPlans. The properties and their values are stored in the Unified Messaging section of the Microsoft Exchange configuration object in Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-UMCallSummaryReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md index c37b790bbe..07ada2f752 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md @@ -52,7 +52,7 @@ The Get-UMCallSummaryReport cmdlet displays the aggregated statistics about all - Burst loss Duration: Average duration of packet loss during bursts of losses for the selected UM dial plan or UM IP gateway. - Number of samples: Number of calls sampled, when calculating the averages. A sample refers to any call data record that contains at least one of the audio quality metrics. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -148,7 +148,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -The UMIPGateway parameter specifies the UM IP gateway to show statistics for. If you don't specify a UM IP gateway, statistics are included for all UM IP gateways for a selected dial plan, or, if no dial plan is selected, results will be returned for all UM IP gateways in the organization. +The UMIPGateway parameter specifies the UM IP gateway to show statistics for. If you don't specify a UM IP gateway, statistics are included for all UM IP gateways for a selected dial plan, or, if no dial plan is selected, results are returned for all UM IP gateways in the organization. ```yaml Type: UMIPGatewayIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md index dbac8b385c..c81063f4c2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md @@ -32,7 +32,7 @@ The Get-UMDialPlan cmdlet displays all properties for a UM dial plan. After this task is completed, when you specify the Identity parameter, you can view the values set. When the Get-UMDialPlan cmdlet is run, if no parameter is supplied, the cmdlet returns all UM dial plans in the Active Directory forest. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md index 2c4eae3937..825cf9cf9b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md @@ -33,7 +33,7 @@ The Get-UMHuntGroup cmdlet retrieves the properties for a single UM hunt group o After this task is completed, if the Identity parameter is specified, the properties for the UM hunt group are returned. If neither the Identity nor the UMDialPlan parameter is specified, all UM hunt groups in the Active Directory forest are 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-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md index a34b158d04..5efbaf5ed9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md @@ -35,7 +35,7 @@ When you're using the Get-UMIPGateway cmdlet, you can't enter the IP address con After this task is completed, you can view the list of properties and values for a specific UM IP gateway. Or, if the Identity parameter isn't used, the cmdlet returns a list of all UM IP gateways in the forest. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md index b2de66ff19..67e9225252 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md @@ -50,7 +50,7 @@ Get-UMMailbox [[-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-UMMailboxPin.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md index 04ded39c11..ad7fbff753 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md @@ -33,11 +33,11 @@ Get-UMMailboxPin [[-Identity] ] ``` ## DESCRIPTION -The Get-UMMailboxPin cmdlet returns information calculated from the PIN data stored in encrypted form in the user's mailbox. This cmdlet also shows whether the mailbox or user access has been locked out. +The Get-UMMailboxPIN cmdlet returns information calculated from the PIN data encrypted and stored in the user's mailbox. This cmdlet also shows whether the mailbox or user access is locked out. After this task is completed, you can view information on a user'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-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md index 6bb94bc162..17e4fcbc3d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md @@ -33,7 +33,7 @@ The Get-UMMailboxPolicy cmdlet retrieves the configuration properties and values After this task is completed, if the Identity parameter is supplied, the properties and values for the specified UM mailbox policy object are returned. If no parameter is specified at the command prompt, all UM mailbox policies in the Active Directory forest are 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-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md index eeb14f3928..416a8f2674 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md @@ -34,7 +34,7 @@ The ExchangeVersion attribute that's returned is the minimum version of Microsof After this task is completed, you can view the parameters and values for a single Unified Messaging server or a list of all of the Unified Messaging servers in Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md index 1baf293205..9089d7734c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md @@ -32,7 +32,7 @@ When the cmdlet is used for a single Exchange server, it returns the Unified Mes The ExchangeVersion attribute that's returned is the minimum version of Exchange you can use to manage the returned object. This attribute isn't the same as the version of 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-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md index 0673369181..a6d99d02f5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md @@ -56,7 +56,7 @@ Get-UnifiedGroup [-Anr ] ## DESCRIPTION Microsoft 365 Groups are group objects that are available across Microsoft 365 services. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md index daf58d4d2b..889457c6de 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md @@ -30,7 +30,7 @@ Get-UnifiedGroupLinks [-Identity] -LinkType ## DESCRIPTION Microsoft 365 Groups are group objects that are available across Microsoft 365 services. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-User.md b/exchange/exchange-ps/ExchangePowerShell/Get-User.md index e2d12cf058..1c78f20404 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-User.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-User.md @@ -13,7 +13,7 @@ title: Get-User # Get-User ## 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-User cmdlet to view existing user objects in your organization. This cmdlet returns all objects that have user accounts (for example, user mailboxes, mail users, and user accounts). @@ -68,7 +68,7 @@ Get-User [[-Identity] ] ## DESCRIPTION The Get-User cmdlet returns no mail-related properties for mailboxes or mail users. To view the mail-related properties for a user, you need to use the corresponding cmdlet based on the object type (for example, Get-Mailbox or Get-MailUser). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-UserPhoto.md b/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md index 5112382af9..fe70eb0bcf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md @@ -60,7 +60,7 @@ Get-UserPhoto [[-Identity] ] ## DESCRIPTION The user photos feature allows users to associate a picture with their account. User photos are stored in the user's Active Directory account and in the root directory of the user's Exchange mailbox. The user photo feature must be set for a user before you can run the Get-UserPhoto cmdlet to view information about the user's photo. Otherwise, you get an error message saying the user photo doesn't exist for the specified users. Administrators use the Set-UserPhoto cmdlet or the Exchange admin center (EAC) to configure user photos. Users can upload, preview, and save a user photo to their account by using the Outlook on the web Options page. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-UserPrincipalNamesSuffix.md b/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md index 47c8e975ea..a33308cebd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md @@ -33,7 +33,7 @@ The default UPN is contained in the Canonical Name attribute on the Partitions c If you create user accounts by using Active Directory Users and Computers, every user must have a UPN. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md index bfc03e42ee..da0f74a7e0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md @@ -44,7 +44,7 @@ The Get-WebServicesVirtualDirectory cmdlet can be run on a local server or run r The Get-WebServicesVirtualDirectory cmdlet can be run on any server that has the Exchange 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-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md index 0779c91d83..a16c7bb305 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md @@ -28,7 +28,7 @@ Get-X400AuthoritativeDomain [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md index 0785727433..52656dd2d1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md @@ -13,7 +13,7 @@ title: Import-DlpPolicyCollection # Import-DlpPolicyCollection ## SYNOPSIS -**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). +**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). This cmdlet is functional only in on-premises Exchange. @@ -37,7 +37,7 @@ The Import-DlpPolicyCollection cmdlet imports all the settings of the DLP polici Importing a DLP policy collection from an XML file removes or overwrites all pre-existing DLP policies that were defined in your organization. Make sure that you have a backup of your current DLP policy collection before you import and overwrite your current DLP policies. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md index 7cd67448e0..812c878550 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md @@ -29,7 +29,7 @@ Import-DlpPolicyTemplate [-FileData] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md index 16a6171171..506ea14827 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md @@ -72,7 +72,7 @@ There are many factors to consider when you configure certificates for Transport Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -157,7 +157,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: String[] @@ -263,7 +263,7 @@ Accept wildcard characters: False The PrivateKeyExportable parameter specifies whether the certificate has an exportable private key and controls whether you can export the certificate from this server. Valid values are: - $true: The private key is exportable, so you can export the certificate from this server. -- $false: The private key isn't exportable, so you can't export the certificate from this server. This is the default value. +- $false: The private key isn't exportable, so you can't export the certificate from this server. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md index 20711926b1..66936d5797 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md @@ -36,7 +36,7 @@ Importing a journal rule collection from an XML file removes or overwrites all p For more information about how to export a journal rule collection to an XML file, see [Export-JournalRuleCollection](https://learn.microsoft.com/powershell/module/exchangepowershell/export-journalrulecollection). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md b/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md index 4aa0575df7..772de76e50 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md @@ -42,7 +42,7 @@ Import-RecipientDataProperty [-Identity] -FileDa ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md index ac58f3c39e..cb5499437f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md @@ -37,7 +37,7 @@ Importing a transport rule collection from an XML file removes or overwrites all For information about how to export a transport rule collection to an XML file, see [Export-TransportRuleCollection](https://learn.microsoft.com/powershell/module/exchangepowershell/export-transportrulecollection). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md b/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md index 84ada54feb..69b9d8c936 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md @@ -62,7 +62,7 @@ The Import-UMPrompt cmdlet imports custom greeting audio files into UM dial plan After this task is completed, the custom audio file can be used by a UM dial plan or auto attendant. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -131,7 +131,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -The PromptFileStream parameter specifies whether the audio file will be uploaded or imported as an audio stream and not a byte array. The default setting is for the audio file to imported as a byte array. +The PromptFileStream parameter specifies whether the audio file is uploaded or imported as an audio stream and not a byte array. The default setting is for the audio file to imported as a byte array. ```yaml Type: Stream diff --git a/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md index 92cf1ae653..b05098dde5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md @@ -31,9 +31,9 @@ Install-TransportAgent [-Name] -AssemblyPath -TransportAgentFa ``` ## DESCRIPTION -Transport agents have full access to all email messages that they encounter. Exchange puts no restrictions on a transport agent's behavior. Transport agents that are unstable or contain security flaws may affect the stability and security of Exchange. Therefore, you need to only install transport agents that you fully trust and that have been fully tested. +Transport agents have full access to all email messages that they encounter. Exchange puts no restrictions on a transport agent's behavior. Transport agents that are unstable or contain security flaws might affect the stability and security of Exchange. Therefore, you need to only install transport agents that you fully trust and that have been fully tested. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md index 2faa34ef03..815fd65f2d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md +++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md @@ -13,7 +13,7 @@ title: Invoke-ComplianceSearchActionStep # Invoke-ComplianceSearchActionStep ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. This cmdlet is reserved for internal Microsoft use. diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md index 7292433a9c..62068c483c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md +++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md @@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange. Use the Invoke-MonitoringProbe cmdlet to run a Managed Availability probe on a selected server. -This cmdlet cannot be used to run every Managed Availability probe. Only some probes (mainly the deep test probes) can be run manually using this cmdlet. Probes that cannot be run with this cmdlet will generate an error message when Invoke-MonitoringProbe is used to run them. +This cmdlet can't be used to run every Managed Availability probe. Only some probes (mainly the deep test probes) can be run manually using this cmdlet. Probes that can't be run with this cmdlet return error messages when you use Invoke-MonitoringProbe to run them. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -38,7 +38,7 @@ Invoke-MonitoringProbe [-Identity] -Server ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -98,7 +98,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Account parameter specifies the identity of the mailbox or user account that will run the monitoring probe. +The Account parameter specifies the identity of the mailbox or user account that's used to run the monitoring probe. ```yaml Type: String @@ -134,7 +134,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The ItemTargetExtension parameter specifies cmdlet extension data that you can pass to the monitoring probe. The probe that runs on the server may require specific data for its execution. This data is presented to the probe on execution in an XML format. +The ItemTargetExtension parameter specifies cmdlet extension data that you can pass to the monitoring probe. The probe that runs on the server might require specific data for its execution. This data is presented to the probe on execution in an XML format. ```yaml Type: String @@ -152,7 +152,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Password parameter specifies the password of the mailbox or user account that will run the monitoring probe. +The Password parameter specifies the password of the mailbox or user account that's used to run the monitoring probe. ```yaml Type: String @@ -188,7 +188,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The SecondaryAccount parameter specifies the identity of the delegate mailbox or user account that will run the monitoring probe. +The SecondaryAccount parameter specifies the identity of the delegate mailbox or user account that's used to run the monitoring probe. ```yaml Type: String @@ -224,7 +224,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The SecondaryPassword parameter specifies the password of the delegate mailbox or user account that will run the monitoring probe. +The SecondaryPassword parameter specifies the password of the delegate mailbox or user account that's used to run the monitoring probe. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md index b9d8d46279..041d064d31 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md +++ b/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md @@ -33,7 +33,7 @@ Mount-Database [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md index 20923aba50..34ab7820b4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md @@ -100,7 +100,7 @@ Move-ActiveMailboxDatabase [-Identity] [-ActivateOnServer] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -130,7 +130,7 @@ This example performs a switchover of the database DB3 to the Mailbox server MBX Move-ActiveMailboxDatabase -Server MBX1 ``` -This example performs a server switchover for the Mailbox server MBX1. All active mailbox database copies on MBX1 will be activated on one or more other Mailbox servers with healthy copies of the active databases on MBX1. +This example performs a server switchover for the Mailbox server MBX1. All active mailbox database copies on MBX1 are activated on one or more other Mailbox servers with healthy copies of the active databases on MBX1. ## PARAMETERS @@ -291,13 +291,13 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The MountDialOverride parameter is used to override the auto database mount dial (AutoDatabaseMountDial) setting for the target server and specify an alternate setting. The following are possible values: +The MountDialOverride parameter is used to override the auto database mount dial (AutoDatabaseMountDial) setting for the target server and specify an alternate setting. Valid value are: -- None: When using this value, the currently configured auto database mount dial setting on the target server will be used. -- Lossless: This is the default value. When using this value, the database doesn't automatically mount until all log files that were generated on the original active copy have been copied to the passive copy. -- GoodAvailability: If you specify this value, the database automatically mounts immediately after a failover if the copy queue length is less than or equal to 6. If the copy queue length is greater than 6, the database doesn't automatically mount. When the copy queue length is less than or equal to 6, Microsoft Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database. -- BestEffort: If you specify this value, the database automatically mounts regardless of the size of the copy queue length. Because the database will mount with any amount of log loss, using this value could result in a large amount of data loss. -- BestAvailability: If you specify this value, the database automatically mounts immediately after a failover if the copy queue length is less than or equal to 12. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than 12, the database doesn't automatically mount. When the copy queue length is less than or equal to 12, Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database. +- None: The currently configured auto database mount dial setting on the target server is used. +- Lossless: This value is the default. The database doesn't automatically mount until all log files that were generated on the original active copy have been copied to the passive copy. +- GoodAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to 6. If the copy queue length is greater than 6, the database doesn't automatically mount. When the copy queue length is less than or equal to 6, Microsoft Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database. +- BestEffort: The database automatically mounts regardless of the size of the copy queue length. Because the database mounts with any amount of log loss, using this value could result in a large amount of data loss. +- BestAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to 12. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than 12, the database doesn't automatically mount. When the copy queue length is less than or equal to 12, Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database. ```yaml Type: DatabaseMountDialOverride @@ -373,7 +373,7 @@ Accept wildcard characters: False The SkipClientExperienceChecks switch specifies whether to skip the search catalog (content index) state check to see if the search catalog is healthy and up to date. You don't need to specify a value with this switch. -If the search catalog for the database copy you're activating is in an unhealthy or unusable state and you use this parameter to skip the search catalog health check and activate the database copy, you will need to either re-crawl or reseed the search catalog. +If the search catalog for the database copy you're activating is in an unhealthy or unusable state and you use this parameter to skip the search catalog health check and activate the database copy, you need to either re-crawl or reseed the search catalog. ```yaml Type: SwitchParameter @@ -449,7 +449,7 @@ Accept wildcard characters: False The SkipMaximumActiveDatabasesChecks switch specifies whether to skip checking the value of MaximumPreferredActiveDatabases during the best copy and server selection (BCSS) process. You don't need to specify a value with this switch. -Any configured value for MaximumActiveDatabases will still be honored during the BCSS process and by the Information Store. +Any configured value for MaximumActiveDatabases is honored during the BCSS process and by the Information Store. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md index 8a33bcacdd..fa8ea18b19 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md @@ -30,7 +30,7 @@ Move-AddressList [-Identity] -Target ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md index 05e0967f85..1f49fba1f2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md @@ -41,7 +41,7 @@ For more information about preset security policies in PowerShell, see [Preset s > [!IMPORTANT] > Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md index 5d3eb131cf..5ad446e0c5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md @@ -45,7 +45,7 @@ For more information about preset security policies in PowerShell, see [Preset s > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -84,7 +84,7 @@ Accept wildcard characters: False The SafeAttachmentPolicy parameter specifies the existing Safe Attachments policy that's associated with the preset security policy. -If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy will be one of the following values: +If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy is one of the following values: - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650008019`. - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034872546`. @@ -109,7 +109,7 @@ Accept wildcard characters: False The SafeLinksPolicy parameter specifies the existing Safe Links policy that's associated with the preset security policy. -If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy will be one of the following values: +If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy is one of the following values: - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650008534`. - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034873192`. @@ -173,7 +173,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: -- $true: The rule is enabled. The State value of the rule is Enabled. This is the default value. +- $true: The rule is enabled. The State value of the rule is Enabled. This value is the default. - $false: The rule is disabled. The State value of the rule is Disabled. After you create the rule, you turn on or turn off the preset security policy using one of the following commands: diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md index 7b60a5bca3..bd520684c0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md @@ -31,7 +31,7 @@ New-AcceptedDomain [-Name] -DomainName ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -68,7 +68,7 @@ Accept wildcard characters: False The DomainName parameter specifies the SMTP domain that you want to establish as an accepted domain. Valid input for the DomainName parameter is an SMTP domain. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: \*.contoso.com. -However, you can't embed a wildcard character, as shown in the following example: domain.\*.contoso.com. The domain name string may not contain more than 256 characters. +However, you can't embed a wildcard character, as shown in the following example: domain.\*.contoso.com. The domain name string might not contain more than 256 characters. ```yaml Type: SmtpDomainWithSubdomains diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md index 81e0237759..831cfa333c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md @@ -13,7 +13,7 @@ title: New-ActiveSyncDeviceAccessRule # New-ActiveSyncDeviceAccessRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-ActiveSyncDeviceAccessRule cmdlet to define the access levels for Exchange ActiveSync devices based on the identity of the device. @@ -32,7 +32,7 @@ New-ActiveSyncDeviceAccessRule -AccessLevel -Characteristic ## DESCRIPTION You can create multiple rules that define groups of devices: Allowed devices, blocked devices and quarantined devices. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md index 9d14e34c18..2b7ff6ccd4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md @@ -13,7 +13,7 @@ title: New-ActiveSyncMailboxPolicy # New-ActiveSyncMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-ActiveSyncMailboxPolicy cmdlet to create a Microsoft Mobile Device mailbox policy object. @@ -89,7 +89,7 @@ The New-ActiveSyncMailboxPolicy cmdlet creates a Mobile Device mailbox policy fo Some Mobile Device mailbox policy settings require the mobile device to have certain built-in features that enforce these security and device management settings. If your organization allows all devices, you must set the AllowNonProvisionableDevices parameter to $true. This allows devices that can't enforce all policy settings to synchronize with your server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -112,7 +112,7 @@ This example creates the Mobile Device mailbox policy Management that has severa New-ActiveSyncMailboxPolicy -Name:"Contoso" -DevicePasswordEnabled:$true -AlphanumericDevicePasswordRequired:$true -PasswordRecoveryEnabled:$true -MinDevicePasswordComplexCharacters:3 -IsDefault:$true -DevicePasswordHistory:10 ``` -This example creates the Mobile Device mailbox policy Contoso that has several preconfigured values. This policy is configured to be the default policy for the organization. The default policy will be assigned to all new users. +This example creates the Mobile Device mailbox policy Contoso that has several preconfigured values. This policy is configured to be the default policy for the organization. The default policy is assigned to all new users. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md index 7580c9fdba..ff2968558b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md @@ -45,7 +45,7 @@ New-ActiveSyncVirtualDirectory [-ApplicationRoot ] ## DESCRIPTION The New-ActiveSyncVirtualDirectory cmdlet creates an Exchange ActiveSync virtual directory on the specified server under the specified website. The Exchange ActiveSync virtual directory created is named Microsoft-Server-ActiveSync. Only one Exchange ActiveSync virtual directory can exist in each Exchange ActiveSync website. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -157,7 +157,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -177,7 +177,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -198,8 +198,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md index 0549ac3edd..36f586f9a4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md @@ -13,9 +13,9 @@ title: New-AddressBookPolicy # New-AddressBookPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. -Use the New-AddressBookPolicy cmdlet to create an address book policy. Address book policies define the global address list (GAL), offline address book (OAB), room list, and address lists that will be displayed to mailbox users who are assigned the policy. +Use the New-AddressBookPolicy cmdlet to create an address book policy. Address book policies define the global address list (GAL), offline address book (OAB), room list, and address lists shown to mailbox users who are assigned the policy. In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). @@ -32,7 +32,7 @@ New-AddressBookPolicy [-Name] -AddressLists ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -73,7 +73,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The AddressLists parameter specifies the address lists that will be used by mailbox users who are assigned this address book policy. This parameter accepts multiple values, which should be separated by a comma. For example, "\\Mr. Munson's Class","Mrs. McKay's Class","Mrs. Count's Class". +The AddressLists parameter specifies the address lists for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the address list. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. + +You can find the identify values of address lists by using the Get-AddressList cmdlet. ```yaml Type: AddressListIdParameter[] @@ -91,7 +99,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The GlobalAddressList parameter specifies the identity of the GAL that will be used by mailbox users who are assigned this address book policy. You can specify only one GAL for each address book policy. +The GlobalAddressList parameter specifies the GAL for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the GAL. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can find the identify values of GALs by using the Get-GlobalAddressList cmdlet. + +You can specify only one GAL for each address book policy. ```yaml Type: GlobalAddressListIdParameter @@ -109,7 +125,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The OfflineAddressBook parameter specifies the identity of the OAB that will be used by mailbox users who are assigned this address book policy. You can specify only one OAB for each address book policy. +The OfflineAddressBook parameter specifies the OAB for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the OAB. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can find the identify values of OABs by using the Get-OfflineAddressBook cmdlet. + +You can specify only one OAB for each address book policy. ```yaml Type: OfflineAddressBookIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md index b0e5d2457b..8c147fdbe2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md @@ -13,7 +13,7 @@ title: New-AddressList # New-AddressList ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-AddressList cmdlet to create address lists and apply them to recipients. @@ -74,7 +74,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md index 6f6e1a5d91..18a80d3e96 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md @@ -16,7 +16,7 @@ title: New-AdminAuditLogSearch > [!NOTE] > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-AdminAuditLogSearch cmdlet to search the contents of the administrator audit log and send the results to one or more mailboxes that you specify. @@ -41,7 +41,7 @@ New-AdminAuditLogSearch -EndDate -StartDate -StatusMai ## DESCRIPTION After the New-AdminAuditLogSearch cmdlet is run, the report is delivered to the mailboxes you specify within 15 minutes. The log is included as an XML attachment on the report email message. The maximum size of the log that can be generated is 10 megabytes (MB). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md index 3275adc777..697abf3319 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md @@ -72,7 +72,7 @@ Phishing messages contain fraudulent links or spoofed domains in an effort to ge New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the AntiPhishPolicy parameter on the New-AntiPhishRule or Set-AntiPhishRule cmdlets to associate the policy with a rule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -135,7 +135,7 @@ This setting is part of spoof protection. The AuthenticationFailAction parameter specifies the action to take when the message fails composite authentication (a mixture of traditional SPF, DKIM, and DMARC email authentication checks and proprietary backend intelligence). Valid values are: -- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. - Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. ```yaml @@ -180,7 +180,7 @@ This setting is part of spoof protection. The DmarcQuarantineAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=quarantine`. Valid values are: - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. -- Quarantine: Deliver the message to quarantine. This is the default value. +- Quarantine: Deliver the message to quarantine. This value is the default. This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true. @@ -205,7 +205,7 @@ This setting is part of spoof protection. The DmarcRejectAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=reject`. Valid values are: - Quarantine: Deliver the message to quarantine. -- Reject: Reject the message. This is the default value. +- Reject: Reject the message. This value is the default. This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true. @@ -252,7 +252,7 @@ Accept wildcard characters: False The EnableFirstContactSafetyTips parameter specifies whether to enable or disable the safety tip that's shown when recipients first receive an email from a sender or do not often receive email from a sender. Valid values are: - $true: First contact safety tips are enabled. -- $false: First contact safety tips are disabled. This is the default value. +- $false: First contact safety tips are disabled. This value is the default. ```yaml Type: Boolean @@ -274,7 +274,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableMailboxIntelligence parameter specifies whether to enable or disable mailbox intelligence, which is artificial intelligence (AI) that determines user email patterns with their frequent contacts. Mailbox intelligence helps distinguish between messages from legitimate and impersonated senders based on a recipient's previous communication history. Valid values are: -- $true: Mailbox intelligence is enabled. This is the default value. +- $true: Mailbox intelligence is enabled. This value is the default. - $false: Mailbox intelligence is disabled. The values of the EnableMailboxIntelligenceProtection and MailboxIntelligenceProtectionAction parameters are ignored. ```yaml @@ -298,7 +298,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableMailboxIntelligenceProtection specifies whether to enable or disable taking action for impersonation detections from mailbox intelligence results. Valid values are: - $true: Take action for impersonation detections from mailbox intelligence results. Use the MailboxIntelligenceProtectionAction parameter to specify the action. -- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This is the default value. +- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This value is the default. This parameter is meaningful only if the EnableMailboxIntelligence parameter is set to the value $true. @@ -325,7 +325,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableOrganizationDomainsProtection parameter specifies whether to enable domain impersonation protection for all registered domains in the Microsoft 365 organization. Valid values are: - $true: Domain impersonation protection is enabled for all registered domains in the Microsoft 365 organization. -- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This is the default value. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters. +- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This value is the default. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters. ```yaml Type: Boolean @@ -348,7 +348,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for domain impersonation detections. Valid values are: - $true: Safety tips for similar domains are enabled. -- $false: Safety tips for similar domains are disabled. This is the default value. +- $false: Safety tips for similar domains are disabled. This value is the default. ```yaml Type: Boolean @@ -371,7 +371,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for user impersonation detections. Valid values are: - $true: Safety tips for similar users are enabled. -- $false: Safety tips for similar users are disabled. This is the default value. +- $false: Safety tips for similar users are disabled. This value is the default. ```yaml Type: Boolean @@ -417,7 +417,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableTargetedDomainsProtection parameter specifies whether to enable domain impersonation protection for a list of specified domains. Valid values are: - $true: Domain impersonation protection is enabled for the domains specified by the TargetedDomainsToProtect parameter. -- $false: The TargetedDomainsToProtect parameter isn't used. This is the default value. +- $false: The TargetedDomainsToProtect parameter isn't used. This value is the default. ```yaml Type: Boolean @@ -440,7 +440,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableTargetedUserProtection parameter specifies whether to enable user impersonation protection for a list of specified users. Valid values are: - $true: User impersonation protection is enabled for the users specified by the TargetedUsersToProtect parameter. -- $false: The TargetedUsersToProtect parameter isn't used. This is the default value. +- $false: The TargetedUsersToProtect parameter isn't used. This value is the default. ```yaml Type: Boolean @@ -462,7 +462,7 @@ This setting is part of spoof protection. The EnableUnauthenticatedSender parameter enables or disables unauthenticated sender identification in Outlook. Valid values are: -- $true: This is the default value. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication. +- $true: This value is the default. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication. - $false: A question mark is never applied to the sender's photo. To prevent these identifiers from being added to messages from specific senders, you have the following options: @@ -491,7 +491,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableUnusualCharactersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for unusual characters in domain and user impersonation detections. Valid values are: - $true: Safety tips for unusual characters are enabled. -- $false: Safety tips for unusual characters are disabled. This is the default value. +- $false: Safety tips for unusual characters are disabled. This value is the default. ```yaml Type: Boolean @@ -513,7 +513,7 @@ This setting is part of spoof protection. The EnableViaTag parameter enables or disables adding the via tag to the From address in Outlook (chris@contso.com via fabrikam.com). Valid values are: -- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This is the default value. +- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This value is the default. - $false: The via tag is not added to the From address. To prevent the via tag from being added to messages from specific senders, you have the following options: @@ -587,7 +587,7 @@ This setting is part of spoof protection. The HonorDmarcPolicy enables or disables using the sender's DMARC policy to determine what to do to messages that fail DMARC checks. Valid values are: -- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This is the default value. +- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This value is the default. - $false: If the message fails DMARC, ignore the action in the sender's DMARC policy. The AuthenticationFailAction parameter specifies the action to take on the message. ```yaml @@ -610,8 +610,8 @@ This setting is part of impersonation protection and is available only in Micros The ImpersonationProtectionState parameter specifies the configuration of impersonation protection. Valid values are: -- Automatic: This is the default value in the default policy named Office365 AntiPhish Policy. -- Manual: This is the default value in custom policies that you create. +- Automatic: This value is the default in the default policy named Office365 AntiPhish Policy. +- Manual: This value is the default in custom policies that you create. - Off ```yaml @@ -634,7 +634,7 @@ This setting is part of impersonation protection and is available only in Micros The MailboxIntelligenceProtectionAction parameter specifies what to do with messages that fail mailbox intelligence protection. Valid values are: -- NoAction: This is the default value. Note that this value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true. +- NoAction: This value is the default. This value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true. - BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. @@ -735,7 +735,7 @@ This setting is part of advanced settings and is available only in Microsoft Def The PhishThresholdLevel parameter specifies the tolerance level that's used by machine learning in the handling of phishing messages. Valid values are: -- 1: Standard: This is the default value. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied. +- 1: Standard: This value is the default. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied. - 2: Aggressive: Messages that are identified as phishing with a high degree of confidence are treated as if they were identified with a very high degree of confidence. - 3: More aggressive: Messages that are identified as phishing with a medium or high degree of confidence are treated as if they were identified with a very high degree of confidence. - 4: Most aggressive: Messages that are identified as phishing with a low, medium, or high degree of confidence are treated as if they were identified with a very high degree of confidence. @@ -864,7 +864,7 @@ This setting is part of impersonation protection and is available only in Micros The TargetedDomainProtectionAction parameter specifies the action to take on detected domain impersonation messages. You specify the protected domains in the TargetedDomainsToProtect parameter. Valid values are: -- NoAction: This is the default value. +- NoAction: This value is the default. - BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. @@ -965,7 +965,7 @@ This setting is part of impersonation protection and is available only in Micros The TargetedUserProtectionAction parameter specifies the action to take on detected user impersonation messages. You specify the protected users in the TargetedUsersToProtect parameter. Valid values are: -- NoAction: This is the default value. +- NoAction: This value is the default. - BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md index b779bdcd5c..c51ee1499b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md @@ -43,7 +43,7 @@ You need to add the antiphish rule to an existing policy by using the AntiPhishP > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Common policy settings](https://learn.microsoft.com/defender-office-365/anti-phishing-policies-about#common-policy-settings). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -148,7 +148,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: -- $true: The rule is enabled. This is the default value. +- $true: The rule is enabled. This value is the default. - $false: The rule is disabled. In the properties of the rule, the value of this parameter is visible in the State property. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-App.md b/exchange/exchange-ps/ExchangePowerShell/New-App.md index 36786d92f6..89e31054bb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-App.md @@ -13,7 +13,7 @@ title: New-App # New-App ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-App cmdlet to install apps for Outlook. @@ -126,7 +126,7 @@ If the app is enabled for the entire organization, users can activate the new ap For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -135,7 +135,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-App -FileData ([System.IO.File]::ReadAllBytes('C:\Apps\FinanceTestApp.xml')) ``` -This example installs the Finance Test app manifest file that has been copied to the local hard disk. +This example installs the Finance Test app manifest file that is copied to the local hard disk. ### Example 2 ```powershell @@ -272,7 +272,7 @@ Accept wildcard characters: False The DefaultStateForUser parameter specifies the default initial state of an organization app. Valid values are: - Enabled: The organization app is enabled by default. -- Disabled: The organization app is disabled by default. This is the default value. +- Disabled: The organization app is disabled by default. This value is the default. - AlwaysEnabled: The organization app is enabled and users can't disable it. You need to use the OrganizationApp switch when you use this parameter. @@ -335,7 +335,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the app is available to users in the organization. Valid values are: -- $true: The app is available to the specified users. This is the default value. +- $true: The app is available to the specified users. This value is the default. - $false: The app is hidden from all users in the organization. This setting overrides the ProvidedTo, UserList and DefaultStateForUser settings. This setting doesn't prevent users from installing their own instance of the app if they have install permissions. @@ -589,8 +589,8 @@ Accept wildcard characters: False The ProvidedTo parameter specifies the availability of the app in your organization. Valid values are: -- Everyone: This is the default value. This app is provided to every user in the organization. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions. -- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor will it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app. +- Everyone: This value is the default. This app is provided to every user in the organization. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions. +- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor does it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app. You use this parameter with the OrganizationApp switch. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md index 3e58c6fc38..ff23d6c486 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md @@ -197,7 +197,7 @@ Accept wildcard characters: False The Enabled parameter enables or disables the policy. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml @@ -379,9 +379,9 @@ Accept wildcard characters: False The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for the policy. Valid values are: - $true: Preservation Lock is enabled for the policy. No one -- including an administrator -- can turn off the policy or make it less restrictive. -- $false: Preservation Lock isn't enabled for the policy. This is the default value. +- $false: Preservation Lock isn't enabled for the policy. This value is the default. -After a policy has been locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. +After a policy is locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. Therefore, before you lock a policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md index 03b4a2058f..677746709d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md @@ -188,7 +188,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: +The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter doesn't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: - IPM.Note.Microsoft.Conversation - IPM.Note.Microsoft.Conversation.Voice @@ -199,7 +199,7 @@ The ExcludedItemClasses parameter specifies the types of messages to exclude fro - IPM.Note.Microsoft.Voicemail.UM - IPM.Note.Microsoft.Voicemail.UM.CA -Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. Note that the values you specify aren't validated, so the parameter accepts any text value. +Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. The values you specify aren't validated, so the parameter accepts any text value. You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`. @@ -307,7 +307,7 @@ The RetentionDurationDisplayHint parameter specifies the units that are used to - Months - Years -For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration. ```yaml Type: HoldDurationHint diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md index 7fb71820ea..0e3793c107 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md @@ -32,9 +32,9 @@ New-ApplicationAccessPolicy -AccessRight -AppId < ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). -You can create a limited number of policies in your organization based on a fixed amount of space. If your organization runs out of space for these policies, you'll see the error: "The total size of App Access Policies exceeded the limit." To maximize the number of policies and reduce the amount of space that's consumed by the policies, set a one space character description for the policy. This method will allow approximately 300 policies (versus a previous limit of 100 policies). +You can create a limited number of policies in your organization based on a fixed amount of space. If your organization runs out of space for these policies, you get the error: "The total size of App Access Policies exceeded the limit." To maximize the number of policies and reduce the amount of space that's consumed by the policies, set a one space character description for the policy. This method allows approximately 300 policies (versus a previous limit of 100 policies). While scope-based resource access like Mail.Read or Calendar.Read is effective to ensure that the application can only read email or events within a mailbox and not do anything else, application access policies allow admins to enforce limits that are based on a list of mailboxes. For example, apps developed for one country/region shouldn't have access to data from other countries/regions. Or, or a CRM integration application should only access calendars in the Sales organization and no other departments. @@ -147,7 +147,7 @@ You can use any value that uniquely identifies the recipient. For example: To verify that a recipient is a security principal, run either of the following commands: `Get-Recipient -Identity | Select-Object IsValidSecurityPrincipal` or `Get-Recipient -ResultSize unlimited | Format-Table -Auto Name,RecipientType,RecipientTypeDetails,IsValidSecurityPrincipal`. -You can't use recipients that aren't security principals with this parameter. For example, the following types of recipients won't work: +You can specify only security principals with this parameter. For example, the following types of recipients don't work: - Discovery mailboxes (DiscoveryMailbox) - Dynamic distribution groups (DynamicDistributionGroup) diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md index ce878ff18c..4b5e2d74af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md @@ -32,7 +32,7 @@ New-AuthRedirect -AuthScheme -TargetUrl ## DESCRIPTION Exchange 2010 Client Access servers don't support OAuth authentication requests. Use this cmdlet to redirect OAuth authentication requests to Exchange servers that are running later versions of Exchange. This cmdlet is only useful if your organization has Exchange 2010 Client Access servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md index cbcdf925ab..7b361bd869 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md @@ -60,7 +60,7 @@ New-AuthServer [-Name] -Type ## DESCRIPTION Partner applications authorized by Exchange can access their resources after they're authenticated using server-to-server authentication. A partner application can authenticate by using self-issued tokens trusted by Exchange or by using an authorization server trusted by Exchange. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -196,7 +196,11 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019 -{{ Fill DomainName Description }} +This parameter is available only in Exchange Server 2016 (CU18 or higher) and Exchange Server 2019 (CU7 or higher). + +The DomainName parameter links a cloud-based organization to the corresponding AuthServer object in the Multi-Tenant Exchange Hybrid. This parameter uses the syntax: "domain.onmicrosoft.com". + +For example, if the DomainName value is contoso.onmicrosoft.com, the AuthServer object is associated with the contoso cloud-based organization. ```yaml Type: MultiValuedProperty @@ -216,7 +220,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the authorization server is enabled. Valid values are: -- $true: Authorization tokens that are issued by the authorization server are accepted. This is the default value +- $true: Authorization tokens that are issued by the authorization server are accepted. This value is the default - $false: Authorization tokens that are issued by the authorization server are not accepted. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md index e623800578..a0774f7214 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md @@ -13,7 +13,7 @@ title: New-AuthenticationPolicy # New-AuthenticationPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-AuthenticationPolicy cmdlet to create authentication policies in your organization. @@ -57,7 +57,7 @@ New-AuthenticationPolicy [[-Name] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md index ed2a9f99e1..506ad13cb3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md @@ -67,7 +67,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned New-AutoSensitivityLabelPolicy -Name "GlobalPolicy" -Comment "Primary policy" -SharePointLocation "https://my.url","https://my.url2" -OneDriveLocation "https://my.url3","https://my.url4" -Mode TestWithoutNotifications -ApplySensitivityLabel "Test" ``` -This example creates an auto-labeling policy named GlobalPolicy for the specified SharePoint and OneDrive locations with the label "Test". The new policy has a descriptive comment and will be in simulation mode on creation. +This example creates an auto-labeling policy named GlobalPolicy for the specified SharePoint and OneDrive locations with the label "Test". The new policy has a descriptive comment and is created in simulation mode. ## PARAMETERS @@ -420,7 +420,7 @@ Accept wildcard characters: False The Mode parameter specifies the action and notification level of the auto-labeling policy. Valid values are: -- Enable: The policy is enabled for actions and notifications. This is the default value. +- Enable: The policy is enabled for actions and notifications. This value is the default. - Disable: The policy is disabled. - TestWithNotifications: No actions are taken, but notifications are sent. - TestWithoutNotifications: An audit mode where no actions are taken, and no notifications are sent. @@ -563,7 +563,7 @@ Accept wildcard characters: False The OverwriteLabel parameter specifies whether to overwrite a manual label. Valid values are: - $true: Overwrite the manual label. -- $false: Don't overwrite the manual label. This is the default value. +- $false: Don't overwrite the manual label. This value is the default. This parameter works only on Exchange locations. @@ -621,7 +621,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Priority parameter specifies the priority of the policy. The highest priority policy will take action over lower priority policies if two policies are applicable for a file. +The Priority parameter specifies the priority of the policy. The highest priority policy takes precedence over lower priority policies if two policies are applicable for a file. ```yaml Type: System.Int32 diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md index b329df41b6..e8a9aa3f46 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md @@ -335,7 +335,7 @@ Accept wildcard characters: False The Disabled parameter specifies whether the auto-labeling policy rule is enabled or disabled. Valid values are: - $true: The rule is disabled. -- $false: The rule is enabled. This is the default value. +- $false: The rule is enabled. This value is the default. ```yaml Type: Boolean @@ -447,7 +447,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this condition in auto-labeling policy rules that are scoped only to Exchange. @@ -690,7 +690,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this exception in auto-labeling policy rules that are scoped only to Exchange. @@ -1199,7 +1199,7 @@ Accept wildcard characters: False The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are: - None: You can't select this value if the rule has no actions configured. -- Low: This is the default value. +- Low: This value is the default. - Medium - High @@ -1224,7 +1224,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du - Ignore - RetryThenBlock -- Blank (the value $null): This is the default value. +- Blank (the value $null): This value is the default. ```yaml Type: PolicyRuleErrorAction diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md index 80f2a0f3bf..044ee90f33 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md @@ -49,7 +49,7 @@ If your organization has multiple email domains and each requires its own Autodi When you're creating an Autodiscover virtual directory, we recommend that you enable Secure Sockets Layer (SSL) for the Autodiscover service. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -104,7 +104,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. ```yaml @@ -147,7 +147,7 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. -- $false: Digest authentication is disabled. This is the default value. +- $false: Digest authentication is disabled. This value is the default. ```yaml Type: Boolean @@ -189,7 +189,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -209,7 +209,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -230,8 +230,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -294,7 +294,7 @@ Accept wildcard characters: False The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are: -- $true: OAuth authentication is enabled. This is the default value. +- $true: OAuth authentication is enabled. This value is the default. - $false: OAuth authentication is disabled. ```yaml @@ -415,7 +415,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -- $true: Integrated Windows authentication is enabled. This is the default value. +- $true: Integrated Windows authentication is enabled. This value is the default. - $false: Integrated Windows authentication is disabled. ```yaml @@ -436,7 +436,7 @@ Accept wildcard characters: False The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are: -- $true: WS-Security authentication is enabled. This is the default value. +- $true: WS-Security authentication is enabled. This value is the default. - $false: WS-Security authentication is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md index 1617b9203b..d9d4f7cd86 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md @@ -31,7 +31,7 @@ New-AvailabilityConfig ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md index f41f532d23..031e3b3e2f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md @@ -32,7 +32,7 @@ New-AvailabilityReportOutage [-SiteName] -Comment -DowntimeMin ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md index a2a84309b5..c401cd7ed0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md @@ -18,7 +18,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the New-CaseHoldPolicy cmdlet to create new case hold policies in the Microsoft Purview compliance portal. > [!NOTE] -> After you use the New-CaseHoldPolicy cmdlet to create a case hold policy, you need to use the New-CaseHoldRule cmdlet to create a case hold rule and assign the rule to the policy. **If you don't create a rule for the policy, the hold won't be created, and content locations won't be placed on hold**. +> After you use the New-CaseHoldPolicy cmdlet to create a case hold policy, you need to use the New-CaseHoldRule cmdlet to create a case hold rule and assign the rule to the policy. **If you don't create a rule for the policy, the hold isn't created, and content locations aren't placed on hold**. > > Running this cmdlet causes a full synchronization across your organization, which is a significant operation. If you need to create multiple policies, wait until the policy distribution is successful before running the cmdlet again for the next policy. For information about the distribution status, see [Get-CaseHoldPolicy](https://learn.microsoft.com/powershell/module/exchangepowershell/get-caseholdpolicy). @@ -141,7 +141,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md index 917d74060d..40f1e04187 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md @@ -160,7 +160,7 @@ Accept wildcard characters: False The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are: - $true: The rule is disabled. -- $false: The rule is enabled. This is the default value. +- $false: The rule is enabled. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md index 9cfa7a8d54..3c89147d16 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md @@ -13,7 +13,7 @@ title: New-ClassificationRuleCollection # New-ClassificationRuleCollection ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-ClassificationRuleCollection cmdlet to import new classification rule collections into your organization. @@ -32,7 +32,7 @@ New-ClassificationRuleCollection [-FileData] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md index a81bd4b402..17f59324a8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md @@ -34,7 +34,7 @@ The New-ClientAccessArray cmdlet creates an object that represents a load balanc Client Access arrays allow Outlook clients in an Active Directory site to access the Client Access servers in the array by using RPC over TCP to a single, unified, fully qualified domain name (FQDN). The RpcClientAccessServer property of new mailbox databases is automatically populated with the FQDN of the Client Access array and this value is used during the creation of Outlook profiles for mailboxes in those databases. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md index 38b6934b7f..ee0bc3376f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md @@ -16,7 +16,7 @@ title: New-ClientAccessRule > [!NOTE] > Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). -This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-ClientAccessRule cmdlet to create client access rules. Client access rules help you control access to your organization based on the properties of the connection. @@ -71,7 +71,7 @@ Protocols that don't support authentication type filters: - REST - UniversalOutlook -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -80,7 +80,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-ClientAccessRule -Name AllowRemotePS -Action Allow -AnyOfProtocols RemotePowerShell -Priority 1 ``` -This example creates a highest priority rule that allows access to remote PowerShell. This rule is an important safeguard to preserve access to your organization. Without this rule, if you create rules that block your access to remote PowerShell, or that block all protocols for everyone, you'll lose the ability to fix the rules yourself (you'll need to call Microsoft Customer Service and Support). +This example creates a highest priority rule that allows access to remote PowerShell. This rule is an important safeguard to preserve access to your organization. Without this rule, if you create rules that block your access to remote PowerShell, or that block all protocols for everyone, you lose the ability to fix the rules yourself (you need to call Microsoft Customer Service and Support). ### Example 2 ```powershell diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md index 28d59c54ab..a92b1a421c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md @@ -84,7 +84,7 @@ The CaseType parameter specifies the type of compliance case that you want to cr - ComplianceWorkspace: This value is reserved for internal Microsoft use. - DataInvestigation: Data investigation cases are used to investigate data spillage incidents. - DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations. -- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. This is the default value. +- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. This value is the default. - InsiderRisk: Insider risk cases are use to manage insider risk management cases. Typically, insider risk management cases are manually created in the Microsoft Purview compliance portal to further investigate activity based on a risk alert. - InternalInvestigation: This value is reserved for internal Microsoft use. - SupervisionPolicy: This type of case corresponds to communication compliance policy. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md index 175e4be26e..5c071cf02f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md @@ -196,7 +196,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The EventType parameter specifies the GUID value of the event that will start the retention period for labels that use this event type. Run the following command to see the available GUID values: `Get-ComplianceRetentionEventType | Format-Table Name,GUID`. +The EventType parameter specifies the GUID value of the event that starts the retention period for labels that use this event type. Run the following command to see the available GUID values: `Get-ComplianceRetentionEventType | Format-Table Name,GUID`. ```yaml Type: ComplianceRuleIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md index dde0f3b69a..d3311f357a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md @@ -13,7 +13,7 @@ title: New-ComplianceSearch # New-ComplianceSearch ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-ComplianceSearch cmdlet to create compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. You use this cmdlet to define the search criteria. @@ -50,7 +50,7 @@ A compliance search requires at least one location. For example, mailboxes using After you create a compliance search using the New-ComplianceSearch cmdlet, you run the search using the Start-ComplianceSearch cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. @@ -108,7 +108,7 @@ Accept wildcard characters: False The AllowNotFoundExchangeLocationsEnabled parameter specifies whether to include mailboxes other than regular user mailboxes in the compliance search. Valid values are: - $true: The search doesn't try to validate the existence of the mailbox before proceeding. This value is required if you want to search mailboxes that don't resolve as regular mailboxes. -- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This is the default value. +- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This value is the default. The mailbox types that are affected by the value of this parameter include: @@ -287,9 +287,9 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The HoldNames parameter specifies that the content locations that have been placed on hold in the specified eDiscovery case will be searched. You use the value All for this parameter. You also need to specify the name of an eDiscovery case by using the Case parameter. +The HoldNames parameter specifies the content locations placed on hold in the specified eDiscovery case are searched. You use the value All for this parameter. You also need to specify the name of an eDiscovery case by using the Case parameter. -Also, if a content location was placed on a query-based case hold, only items that are on hold will be searched when you run this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search. +Also, if a content location was placed on a query-based case hold, only items that are on hold are searched when you run this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search. ```yaml Type: String[] @@ -329,8 +329,8 @@ This parameter is available only in the cloud-based service. The IncludeUserAppContent parameter specifies that you want to search the cloud-based storage location for users who don't have a regular Microsoft 365 user account in your organization. These types of users include users without an Exchange Online license who use Office applications, Microsoft 365 guest users, and on-premises users whose identity is synchronized with your Microsoft 365 organization. Valid values are: -- $true: The cloud-based storage location for the users specified in the ExchangeLocation parameter will be included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user will be included in the search. -- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter won't be included in the search. This is the default value. +- $true: The cloud-based storage location for the users specified in the ExchangeLocation parameter are included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user are included in the search. +- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter isn't included in the search. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md index 0ed529ffc5..bb12c6f155 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md @@ -13,7 +13,7 @@ title: New-ComplianceSearchAction # New-ComplianceSearchAction ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-ComplianceSearchAction cmdlet to create actions for content searches in Exchange Server and in the Microsoft Purview compliance portal. @@ -99,7 +99,7 @@ After you create a content search using the New-ComplianceSearch cmdlet and run In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). In Microsoft 365, the account that you use to run this cmdlet must have a valid Microsoft 365 license assigned. @@ -128,7 +128,7 @@ This example creates an export search action for the content search named Projec New-ComplianceSearchAction -SearchName "Remove Phishing Message" -Purge -PurgeType SoftDelete ``` -This example deletes the search results returned by a content search named Remove Phishing Message. Note that unindexed items aren't deleted when you use the Purge parameter. +This example deletes the search results returned by a content search named Remove Phishing Message. Unindexed items aren't deleted when you use the Purge parameter. ### Example 4 ```powershell @@ -185,7 +185,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. To specify the format for Exchange search results, use the ExchangeArchiveFormat parameter. To specify the format for SharePoint and OneDrive search results, use the SharePointArchiveFormat parameter. @@ -259,7 +259,7 @@ The ExchangeArchiveFormat parameter specifies how to export Exchange search resu - PerUserPst: One PST file for each mailbox. - SinglePst: One PST file that contains all exported messages. - SingleFolderPst: One PST file with a single root folder for the entire export. -- IndividualMessage: Export each message as an .msg message file. This is the default value. +- IndividualMessage: Export each message as an .msg message file. This value is the default. - PerUserZip: One ZIP file for each mailbox. Each ZIP file contains the exported .msg message files from the mailbox. - SingleZip: One ZIP file for all mailboxes. The ZIP file contains all exported .msg message files from all mailboxes. This output setting is available only in PowerShell. @@ -396,7 +396,7 @@ This parameter is available only in the cloud-based service. The IncludeSharePointDocumentVersions parameter specifies whether to export previous versions of the document when you use the Export switch. Valid values are: - $true: Export all versions of the document. -- $false: Export only the current published version of the topic. This is the default value. +- $false: Export only the current published version of the topic. This value is the default. ```yaml Type: Boolean @@ -508,7 +508,7 @@ The Purge switch specifies the action for the content search is to remove items **Tip**: To purge more than 10 items, refer to [ediscoverySearch: purgeData](https://learn.microsoft.com/graph/api/security-ediscoverysearch-purgedata) in the Microsoft Graph API, which allows purging a maximum of 100 items per location. -- You can remove items from a maximum of 50,000 mailboxes using a single content search. To remove items from more than 50,000 mailboxes, you'll have to create separate content searches. For more information, see [Search for and delete email messages in your Microsoft 365 organization](https://learn.microsoft.com/purview/ediscovery-search-for-and-delete-email-messages). +- You can remove items from a maximum of 50,000 mailboxes using a single content search. To remove items from more than 50,000 mailboxes, you need to create separate content searches. For more information, see [Search for and delete email messages in your Microsoft 365 organization](https://learn.microsoft.com/purview/ediscovery-search-for-and-delete-email-messages). - Unindexed items aren't removed from mailboxes when you use this switch. - The value of the PurgeType parameter controls how the items are removed. @@ -533,7 +533,7 @@ Accept wildcard characters: False The PurgeType parameter specifies how to remove items when the action is Purge. Valid values are: - SoftDelete: Purged items are recoverable by users until the deleted item retention period expires. -- HardDelete (cloud only): Purged items are marked for permanent removal from the mailbox and will be permanently removed the next time the mailbox is processed by the Managed Folder Assistant. If single item recovery is enabled on the mailbox, purged items will be permanently removed after the deleted item retention period expires. +- HardDelete (cloud only): Purged items are marked for permanent removal from the mailbox and are permanently removed the next time the mailbox is processed by the Managed Folder Assistant. If single item recovery is enabled on the mailbox, purged items are permanently removed after the deleted item retention period expires. ```yaml Type: ComplianceDestroyType @@ -728,7 +728,7 @@ This parameter requires the Export role. By default, this role is assigned only The SharePointArchiveFormat parameter specifies how to export SharePoint and OneDrive search results. Valid values are: -- IndividualMessage: Export the files uncompressed. This is the default value. +- IndividualMessage: Export the files uncompressed. This value is the default. - PerUserZip: One ZIP file for each user. Each ZIP file contains the exported files for the user. - SingleZip: One ZIP file for all users. The ZIP file contains all exported files from all users. This output setting is available only in PowerShell. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md index e58199a8c7..a1340d5858 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md @@ -373,7 +373,7 @@ Accept wildcard characters: False The IsRecordLabel parameter specifies whether the label is a record label. Valid values are: - $true: The label is a record label. Once the label is applied to content, the label can't be removed. -- $false: The label isn't a record label. This is the default value. +- $false: The label isn't a record label. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md index ef07895c85..4fd215d87d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md @@ -15,7 +15,7 @@ title: New-DataClassification ## SYNOPSIS This cmdlet is functional only in on-premises Exchange. -In Exchange Online, this cmdlet has been replaced by the [New-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. +In Exchange Online, this cmdlet is replaced by the [New-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. Use the New-DataClassification cmdlet to create data classification rules that use document fingerprints. @@ -36,7 +36,7 @@ New-DataClassification [-Name] -Description -Fingerprints [-DatabaseAvailabilityGrou ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md index 8727a41a18..3320d9ce11 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md @@ -39,7 +39,7 @@ New-DeliveryAgentConnector [-Name] -AddressSpaces ## DESCRIPTION Delivery agent connectors are used to route messages addressed to foreign systems that don't utilize the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in the Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md index c39103379a..e43f3ef571 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md @@ -117,7 +117,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md index 1b89079368..a2aff5f1c4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md @@ -152,7 +152,7 @@ Accept wildcard characters: False The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -173,7 +173,7 @@ Accept wildcard characters: False The AccountUserName parameter specifies the account user name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -195,7 +195,7 @@ The AllowAppStore parameter specifies whether to allow access to the app store o - $true: Access to the app store is allowed. - $false: Access to the app store isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -222,7 +222,7 @@ The AllowAssistantWhileLocked parameter specifies whether to allow the use of th - $true: The voice assistant can be used while devices are locked. - $false: The voice assistant can't be used while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -246,7 +246,7 @@ The AllowConvenienceLogon parameter specifies whether to allow convenience logon - $true: Convenience logons are allowed. - $false: Convenience logons aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -270,7 +270,7 @@ The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic su - $true: Diagnostic submissions are allowed. - $false: Diagnostic submissions aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -298,7 +298,7 @@ The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup f - $true: iCloud Backup is allowed. - $false: iCloud Backup isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -325,7 +325,7 @@ The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documen - $true: iCloud Documents & Data sync is allowed. - $false: iCloud Documents & Data sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -352,7 +352,7 @@ The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photo - $true: iCloud Photos sync is allowed. - $false: iCloud Photo sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -379,7 +379,7 @@ The AllowJailbroken parameter specifies whether to allow access to your organiza - $true: Jailbroken devices are allowed. - $false: Jailbroken devices aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -406,7 +406,7 @@ The AllowPassbookWhileLocked parameter specifies whether to allow the use of App - $true: Passbook is available while devices are locked. - $false: Passbook isn't available while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -430,7 +430,7 @@ The AllowScreenshot parameter specifies whether to allow screenshots on devices. - $true: Screenshots are allowed. - $false: Screenshots aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -457,7 +457,7 @@ The AllowSimplePassword parameter specifies whether to allow simple or non-compl - $true: Simple passwords are allowed. - $false: Simple passwords aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -485,7 +485,7 @@ The AllowVideoConferencing parameter specifies whether to allow video conferenci - $true: Video conferencing is allowed. - $false: Video conferencing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -509,7 +509,7 @@ The AllowVoiceAssistant parameter specifies whether to allow using the voice ass - $true: The voice assistant is allowed. - $false: The voice assistant isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -533,7 +533,7 @@ The AllowVoiceDialing parameter specifies whether to allow voice-activated telep - $true: Voice dialing is allowed. - $false: Voice dialing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -556,7 +556,7 @@ Accept wildcard characters: False The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -579,7 +579,7 @@ Accept wildcard characters: False The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -606,7 +606,7 @@ The AppsRating parameter species the maximum or most restrictive rating of apps - Rating9plus - Rating12plus - Rating17plus -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -633,7 +633,7 @@ The AutoUpdateStatus parameter specifies the update settings for devices. Valid - AutomaticUpdatesRequired - DeviceDefault - NeverCheckUpdates -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -657,7 +657,7 @@ The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth - $true: Bluetooth is enabled. - $false: Bluetooth is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -681,7 +681,7 @@ The CameraEnabled parameter specifies whether to enable or disable cameras on de - $true: Cameras are enabled. - $false: Cameras are disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -747,7 +747,7 @@ Accept wildcard characters: False The EmailAddress parameter specifies the email address. Valid values are: - An email address: For example, julia@contoso.com. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -769,7 +769,7 @@ The EnableRemovableStorage parameter specifies whether removable storage can be - $true: Removable storage can be used. - $false: Removable storage can't be used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -792,7 +792,7 @@ Accept wildcard characters: False The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -813,7 +813,7 @@ Accept wildcard characters: False The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are: - Required -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -837,7 +837,7 @@ The ForceAppStorePassword parameter specifies whether to require a password to u - $true: App store passwords are required. - $false: App store passwords aren't required. -- $null (blank): The feature isn't allowed or blocked by the rule. This is the default value. +- $null (blank): The feature isn't allowed or blocked by the rule. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -861,7 +861,7 @@ The ForceEncryptedBackup parameter specifies whether to force encrypted backups - $true: Encrypted backups are required. - $false: Encrypted backups aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -887,7 +887,7 @@ Accept wildcard characters: False The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -940,7 +940,7 @@ Valid values for the MoviesRating parameter are: - AllowAll: All movies are allowed, regardless of their rating. - DontAllow: No movies are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1039,7 +1039,7 @@ Accept wildcard characters: False The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int64 @@ -1060,7 +1060,7 @@ Accept wildcard characters: False The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1088,7 +1088,7 @@ Accept wildcard characters: False The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1116,7 +1116,7 @@ Accept wildcard characters: False The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int32 @@ -1137,7 +1137,7 @@ Accept wildcard characters: False The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1167,7 +1167,7 @@ The PasswordQuality parameter specifies the minimum password quality rating that Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Android 4+ devices. @@ -1191,7 +1191,7 @@ The PasswordRequired parameter specifies whether a password is required to acces - $true: Device passwords are required. - $false: Device passwords aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1246,7 +1246,7 @@ The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on de - $true: Memory is encrypted. - $false: Memory isn't encrypted. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1273,7 +1273,7 @@ The RegionRatings parameter specifies the rating system (country/region) to use Valid values for the RegionRating parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - au: Australia - ca: Canada - de: Germany @@ -1306,7 +1306,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required - $true: An email profile is required. This value is required for selective wipe on iOS devices. - $false: An email profile isn't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Boolean @@ -1328,7 +1328,7 @@ The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen - $true: SmartScreen is enabled. - $false: SmartScreen is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -1352,7 +1352,7 @@ The SystemSecurityTLS parameter specifies whether TLS encryption is used on devi - $true: TLS encryption is used. - $false: TLS encryption isn't used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -1378,7 +1378,7 @@ Valid values for the TVShowsRating parameter are: - AllowAll: All television shows are allowed, regardless of their rating. - DontAllow: No televisions shows are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1465,7 +1465,7 @@ Accept wildcard characters: False The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - AlwaysNotify - NeverNotify - NotifyAppChanges @@ -1511,7 +1511,7 @@ The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid valu - $true: Wi-Fi is enabled. - $false: Wi-Fi is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Microsoft Windows Phone 8.1 devices. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md index f3e3e885f1..09a319872c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md @@ -117,7 +117,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md index 47cb277d91..73b027f3ff 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md @@ -151,7 +151,7 @@ Accept wildcard characters: False The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -172,7 +172,7 @@ Accept wildcard characters: False The AccountUserName parameter specifies the account user name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -194,7 +194,7 @@ The AllowAppStore parameter specifies whether to allow access to the app store o - $true: Access to the app store is allowed. - $false: Access to the app store isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -221,7 +221,7 @@ The AllowAssistantWhileLocked parameter specifies whether to allow the use of th - $true: The voice assistant can be used while devices are locked. - $false: The voice assistant can't be used while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -245,7 +245,7 @@ The AllowConvenienceLogon parameter specifies whether to allow convenience logon - $true: Convenience logons are allowed. - $false: Convenience logons aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -269,7 +269,7 @@ The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic su - $true: Diagnostic submissions are allowed. - $false: Diagnostic submissions aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -297,7 +297,7 @@ The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup f - $true: iCloud Backup is allowed. - $false: iCloud Backup isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -324,7 +324,7 @@ The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documen - $true: iCloud Documents & Data sync is allowed. - $false: iCloud Documents & Data sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -351,7 +351,7 @@ The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photo - $true: iCloud Photos sync is allowed. - $false: iCloud Photo sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -378,7 +378,7 @@ The AllowPassbookWhileLocked parameter specifies whether to allow the use of App - $true: Passbook is available while devices are locked. - $false: Passbook isn't available while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -402,7 +402,7 @@ The AllowScreenshot parameter specifies whether to allow screenshots on devices. - $true: Screenshots are allowed. - $false: Screenshots aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -429,7 +429,7 @@ The AllowSimplePassword parameter specifies whether to allow simple or non-compl - $true: Simple passwords are allowed. - $false: Simple passwords aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -457,7 +457,7 @@ The AllowVideoConferencing parameter specifies whether to allow video conferenci - $true: Video conferencing is allowed. - $false: Video conferencing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -481,7 +481,7 @@ The AllowVoiceAssistant parameter specifies whether to allow using the voice ass - $true: The voice assistant is allowed. - $false: The voice assistant isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -505,7 +505,7 @@ The AllowVoiceDialing parameter specifies whether to allow voice-activated telep - $true: Voice dialing is allowed. - $false: Voice dialing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -528,7 +528,7 @@ Accept wildcard characters: False The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -551,7 +551,7 @@ Accept wildcard characters: False The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -578,7 +578,7 @@ The AppsRating parameter species the maximum or most restrictive rating of apps - Rating9plus - Rating12plus - Rating17plus -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -605,7 +605,7 @@ The AutoUpdateStatus parameter specifies the update settings for devices. Valid - AutomaticUpdatesRequired - DeviceDefault - NeverCheckUpdates -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -629,7 +629,7 @@ The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth - $true: Bluetooth is enabled. - $false: Bluetooth is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -653,7 +653,7 @@ The CameraEnabled parameter specifies whether to enable or disable cameras on de - $true: Cameras are enabled. - $false: Cameras are disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -719,7 +719,7 @@ Accept wildcard characters: False The EmailAddress parameter specifies the email address. Valid values are: - An email address: For example, julia@contoso.com. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -741,7 +741,7 @@ The EnableRemovableStorage parameter specifies whether removable storage can be - $true: Removable storage can be used. - $false: Removable storage can't be used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -764,7 +764,7 @@ Accept wildcard characters: False The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -785,7 +785,7 @@ Accept wildcard characters: False The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are: - Required -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -809,7 +809,7 @@ The ForceAppStorePassword parameter specifies whether to require a password to u - $true: App store passwords are required. - $false: App store passwords aren't required. -- $null (blank): The feature isn't allowed or blocked by the rule. This is the default value. +- $null (blank): The feature isn't allowed or blocked by the rule. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -833,7 +833,7 @@ The ForceEncryptedBackup parameter specifies whether to force encrypted backups - $true: Encrypted backups are required. - $false: Encrypted backups aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -859,7 +859,7 @@ Accept wildcard characters: False The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -912,7 +912,7 @@ Valid values for the MoviesRating parameter are: - AllowAll: All movies are allowed, regardless of their rating. - DontAllow: No movies are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1011,7 +1011,7 @@ Accept wildcard characters: False The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int64 @@ -1032,7 +1032,7 @@ Accept wildcard characters: False The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1060,7 +1060,7 @@ Accept wildcard characters: False The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1088,7 +1088,7 @@ Accept wildcard characters: False The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int32 @@ -1109,7 +1109,7 @@ Accept wildcard characters: False The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1139,7 +1139,7 @@ The PasswordQuality parameter specifies the minimum password quality rating that Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Android 4+ devices. @@ -1163,7 +1163,7 @@ The PasswordRequired parameter specifies whether a password is required to acces - $true: Device passwords are required. - $false: Device passwords aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1218,7 +1218,7 @@ The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on de - $true: Memory is encrypted. - $false: Memory isn't encrypted. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1245,7 +1245,7 @@ The RegionRatings parameter specifies the rating system (country/region) to use Valid values for the RegionRating parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - au: Australia - ca: Canada - de: Germany @@ -1278,7 +1278,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required - $true: An email profile is required. This value is required for selective wipe on iOS devices. - $false: An email profile isn't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Boolean @@ -1300,7 +1300,7 @@ The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen - $true: SmartScreen is enabled. - $false: SmartScreen is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -1324,7 +1324,7 @@ The SystemSecurityTLS parameter specifies whether TLS encryption is used on devi - $true: TLS encryption is used. - $false: TLS encryption isn't used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -1350,7 +1350,7 @@ Valid values for the TVShowsRating parameter are: - AllowAll: All television shows are allowed, regardless of their rating. - DontAllow: No televisions shows are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1437,7 +1437,7 @@ Accept wildcard characters: False The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - AlwaysNotify - NeverNotify - NotifyAppChanges @@ -1483,7 +1483,7 @@ The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid valu - $true: Wi-Fi is enabled. - $false: Wi-Fi is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Microsoft Windows Phone 8.1 devices. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md index dbfdd374b4..e41f6654c8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md @@ -98,7 +98,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md index ac577a237c..a8e5f0ae79 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md @@ -13,7 +13,7 @@ title: New-DistributionGroup # New-DistributionGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-DistributionGroup cmdlet to create distribution groups and mail-enabled security groups. @@ -60,7 +60,7 @@ You can use the New-DistributionGroup cmdlet to create the following types of gr Distribution groups are used to consolidate groups of recipients into a single point of contact for email messages. Distribution groups aren't security principals, and therefore can't be assigned permissions. However, you can assign permissions to mail-enabled security groups. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. @@ -180,7 +180,7 @@ This parameter is available only in the cloud-based service. The BccBlocked parameter specifies whether members of the group don't receive messages if the group is used in the Bcc line. Valid values are: - $true: If the group is used in the Bcc line, members of the group don't receive the message, and the sender receives a non-delivery report (also known as an NDR or bounce message). Other recipients of the message aren't blocked. If an external sender uses the group in the Bcc line, members of the group aren't blocked. For nested groups, the message is blocked only for members of the top-level group. -- $false: There are no restrictions for using the group in the Bcc line of messages. This is the default value. +- $false: There are no restrictions for using the group in the Bcc line of messages. This value is the default. ```yaml Type: Boolean @@ -201,7 +201,7 @@ Accept wildcard characters: False The ByPassNestedModerationEnabled parameter specifies how to handle message approval when a moderated group contains other moderated groups as members. Valid values are: - $true: After a moderator approves a message sent to the group, the message is automatically approved for all other moderated groups that are members of the group. -- $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This is the default value. +- $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This value is the default. This parameter can be used only by top-level organization and tenant administrators. @@ -418,8 +418,8 @@ Accept wildcard characters: False The MemberDepartRestriction parameter specifies the restrictions that you put on requests to leave the group. Valid values are: -- Open: Members can leave the group without approval from one of the group owners. This is the default value for universal distribution groups. You can't use this value on universal security groups. -- Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This is the default value for universal security groups. +- Open: Members can leave the group without approval from one of the group owners. This value is the default for universal distribution groups. You can't use this value on universal security groups. +- Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This value is the default for universal security groups. ```yaml Type: MemberUpdateType @@ -440,7 +440,7 @@ Accept wildcard characters: False The MemberJoinRestriction parameter specifies the restrictions that you put on requests to join the group. Valid values are: - Open: Users can add themselves to the group without approval from a group owner. You can't use this value on universal security groups. -- Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This is the default value on universal security groups and universal distribution groups. +- Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This value is the default on universal security groups and universal distribution groups. - ApprovalRequired: Users can request to join the group. The user is added to the group after the request is approved by one of the group owners. Although you can use this value on universal security groups, user requests to join the group aren't sent to the group owners, so this setting is only effective on universal distribution groups. ```yaml @@ -472,7 +472,7 @@ You can enter multiple values separated by commas. If the values contain spaces After you create the group, you use the Get-DistributionGroupMember cmdlet to view the group members, and the Add-DistributionGroupMember, Remove-DistributionGroupMember, and Update-DistributionGroupMember cmdlets to manage group membership. -Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) won't have the permissions assigned. +Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) don't have the permissions assigned. The maximum number of entries for this parameter is 10000. @@ -526,7 +526,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -652,7 +652,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). ```yaml Type: String @@ -672,7 +672,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -696,7 +696,7 @@ Accept wildcard characters: False The Type parameter specifies the type of group that you want to create. Valid values are: -- Distribution: A distribution group. These groups can't have permissions assigned. This is the default value. +- Distribution: A distribution group. These groups can't have permissions assigned. This value is the default. - Security: A mail-enabled security group. These groups can have permissions assigned. The group's scope is always Universal. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md index 0dfaee8eb1..66fa40daa5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md @@ -35,7 +35,7 @@ New-DkimSigningConfig [-DomainName] [-Enabled] Applicable: Security & Compliance -The Policy parameter specifies the existing DLP policy that will contain the new DLP rule. You can use any value that uniquely identifies the policy. For example: +The Policy parameter specifies the existing DLP policy that contains the new DLP rule. You can use any value that uniquely identifies the policy. For example: - Name - Distinguished name (DN) @@ -587,7 +587,7 @@ Accept wildcard characters: False The BlockAccess parameter specifies an action for the DLP rule that blocks access to the source item when the conditions of the rule are met. Valid values are: - $true: Blocks further access to the source item that matched the rule. The owner, author, and site owner can still access the item. -- $false: Allows access to the source item that matched the rule. This is the default value. +- $false: Allows access to the source item that matched the rule. This value is the default. ```yaml Type: Boolean @@ -815,7 +815,7 @@ Accept wildcard characters: False The Disabled parameter specifies whether the DLP rule is disabled. Valid values are: - $true: The rule is disabled. -- $false: The rule is enabled. This is the default value. +- $false: The rule is enabled. This value is the default. ```yaml Type: Boolean @@ -1013,7 +1013,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this condition in DLP policies that are scoped only to Exchange. @@ -1553,7 +1553,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this exception in DLP policies that are scoped only to Exchange. @@ -1759,7 +1759,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this exception in DLP policies that are scoped only to Exchange. @@ -2602,7 +2602,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this condition in DLP policies that are scoped only to Exchange. @@ -2961,7 +2961,7 @@ Accept wildcard characters: False The NotifyPolicyTipDialogOption parameter specifies a display option for the policy tip. Valid values are: -- Tip: Displays policy tip at the top of the mail. This is the default value. +- Tip: Displays policy tip at the top of the mail. This value is the default. - Dialog: Displays policy tip at the top of the mail and as a popup dialog. (exchange only) ```yaml @@ -3366,7 +3366,7 @@ Accept wildcard characters: False The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are: - None: You can't select this value if the rule has no actions configured. -- Low: This is the default value. +- Low: This value is the default. - Medium - High @@ -3426,7 +3426,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du - Ignore - RetryThenBlock -- Blank (the value $null): This is the default value. +- Blank (the value $null): This value is the default. ```yaml Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyRuleErrorAction @@ -3550,11 +3550,11 @@ Accept wildcard characters: False The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are: -- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This is the default value. +- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default. - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). - HeaderOrEnvelope: Examine senders in the message header and the message envelope. -Note that message envelope searching is available only for the following conditions and exceptions: +Message envelope searching is available only for the following conditions and exceptions: - From and ExceptIfFrom - FromAddressContainsWords and ExceptIfFromAddressContainsWords diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md index 143373bf26..b788cd9e15 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md @@ -33,7 +33,7 @@ New-DlpKeywordDictionary -Name ``` ## DESCRIPTION -After you create a custom sensitive information type that specifies the identity (GUID value) of the DLP keyword dictionary, the dictionary will appear in your list of sensitive information types, and you can use it in policies. +After you create a custom sensitive information type that specifies the identity (GUID value) of the DLP keyword dictionary, the dictionary appears in your list of sensitive information types, and you can use it in policies. To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md index 6f345ee2f5..e366f86920 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md @@ -13,7 +13,7 @@ title: New-DlpPolicy # New-DlpPolicy ## SYNOPSIS -**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the New-DlpCompliancePolicy and New-DlpComplianceRule cmdlets instead. +**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the New-DlpCompliancePolicy and New-DlpComplianceRule cmdlets instead. This cmdlet is functional only in on-premises Exchange. @@ -38,7 +38,7 @@ New-DlpPolicy [[-Name] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -157,7 +157,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The Parameters parameter specifies the parameter values that are required by the DLP policy template that you specify using the Template or TemplateData parameters. DLP policy templates may contain parameters that need to be populated with values from your organization. For example, a DLP policy template may include an exception group that defines users who are exempt from the DLP policy. +The Parameters parameter specifies the parameter values that are required by the DLP policy template that you specify using the Template or TemplateData parameters. DLP policy templates might contain parameters that need to be populated with values from your organization. For example, a DLP policy template might include an exception group that defines users who are exempt from the DLP policy. This parameter uses the syntax: `@{Parameter1="Value1";Parameter2="Value2"...}`. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md index fa1137e12b..97a2f8867f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md @@ -13,7 +13,7 @@ title: New-DynamicDistributionGroup # New-DynamicDistributionGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-DynamicDistributionGroup cmdlet to create dynamic distribution groups. A dynamic distribution group queries mail-enabled objects and builds the group membership based on the results. The group membership is recalculated whenever an email message is sent to the group. @@ -86,7 +86,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPATH filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -766,7 +766,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -844,7 +844,7 @@ The RecipientContainer parameter specifies a filter that's based on the recipien If you don't use this parameter, the default value is the OU where the object was created. -Note that the RecipientContainer property can't be blank. The group is always limited to looking for recipients in a specific location (the value you specify for this parameter, or the location where the group was created). +The RecipientContainer property can't be blank. The group is always limited to looking for recipients in a specific location (the value you specify for this parameter, or the location where the group was created). **Note**: Although this parameter is available in Exchange Online, there's only one usable OU in an Exchange Online organization, so using this parameter has no effect. @@ -866,7 +866,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md index 93ddfc0f15..02b42f2322 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md @@ -44,7 +44,7 @@ For more information about preset security policies in PowerShell, see [Preset s > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -83,7 +83,7 @@ Accept wildcard characters: False The AntiPhishPolicy parameter specifies the existing anti-phishing policy that's associated with the preset security policy. -If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-phishing policy will be one of the following values: +If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-phishing policy is one of the following values: - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650005393`. - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034844713`. @@ -108,7 +108,7 @@ Accept wildcard characters: False The HostedContentFilterPolicy parameter specifies the existing anti-spam policy that's associated with the preset security policy. -If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-spam policy will be one of the following values: +If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-spam policy is one of the following values: - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650006407`. - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034847393`. @@ -133,7 +133,7 @@ Accept wildcard characters: False The HostedContentFilterPolicy parameter specifies the existing anti-malware policy that's associated with the preset security policy. -If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-malware policy will be one of the following values: +If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-malware policy is one of the following values: - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650007658`. - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034871908`. @@ -197,7 +197,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: -- $true: The rule is enabled. The State value of the rule is Enabled. This is the default value. +- $true: The rule is enabled. The State value of the rule is Enabled. This value is the default. - $false: The rule is disabled. The State value of the rule is Disabled. After you create the rule, you turn on or turn off the preset security policy using one of the following commands: diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md index 99729e8485..d7db96a683 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md @@ -41,7 +41,7 @@ New-EcpVirtualDirectory [-AppPoolId ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -121,7 +121,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -141,7 +141,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -162,8 +162,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md index 9df879d76c..0f3c1a24b3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md @@ -36,9 +36,9 @@ New-EdgeSubscription [-AccountExpiryDuration ] ``` ## DESCRIPTION -The Edge Transport server doesn't have access to Active Directory. All configuration and recipient information is stored in the Active Directory Lightweight Directory Services (AD LDS) instance. The New-EdgeSubscription cmdlet creates the Edge Subscription file that will be imported on a Mailbox server in the Active Directory site to which you want to subscribe this Edge Transport server. +The Edge Transport server doesn't have access to Active Directory. All configuration and recipient information is stored in the Active Directory Lightweight Directory Services (AD LDS) instance. The New-EdgeSubscription cmdlet creates the Edge Subscription file to import on a Mailbox server in the Active Directory site where you want to subscribe this Edge Transport server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -73,7 +73,7 @@ This example also imports the Edge Subscription file generated in Example 1 to t > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The AccountExpiryDuration parameter specifies how soon the EdgeSync bootstrap replication account (ESBRA) created by this command will expire. +The AccountExpiryDuration parameter specifies how soon the EdgeSync bootstrap replication account (ESBRA) created by this command expires. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md index a8168f3519..c64ac8e72c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md @@ -43,7 +43,7 @@ New-EdgeSyncServiceConfig [-ConfigurationSyncInterval ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -224,7 +224,7 @@ Accept wildcard characters: False The LogLevel parameter specifies the EdgeSync logging level. Valid values are: -- None (This is the default value) +- None (default value) - Low - Medium - High @@ -275,7 +275,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the LogMaxFileSize parameter must be less than or equal to the value of the LogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the EdgeSyncLLog directory. @@ -305,7 +305,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the LogMaxFileSize parameter must be less than or equal to the value of the LogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the EdgeSyncLog files. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md index 6b5b760e67..aaa242cc86 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md @@ -13,7 +13,7 @@ title: New-EmailAddressPolicy # New-EmailAddressPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-EmailAddressPolicy cmdlet to create email address policies. In Exchange Online, email address policies are available only for Microsoft 365 Groups. @@ -141,7 +141,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -793,7 +793,7 @@ The DisabledEmailAddressTemplates parameter specifies the proxy email addresses Valid syntax for this parameter is `Type:AddressFormat`: -- Type: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. Note that you can't use SMTP to specify a disabled primary SMTP email address. +- Type: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. You can't use SMTP to specify a disabled primary SMTP email address. - AddressFormat: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example: alias@contoso.com requires the value `%m@contoso.com`, and firstname.lastname@contoso.com requires the value `%g.%s@contoso.com`. You can specify multiple disabled email address templates separated by commas: `"[Type1:]EmailAddress1","[Type2:]EmailAddress2",..."[TypeN:]EmailAddressN"`. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md index 365938a134..9c2195d866 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md @@ -72,7 +72,7 @@ There are many factors to consider when you configure certificates for Transport Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). To find out why you should disable the SSL protocol and switch to TLS, check out [Protecting you against the SSL 3.0 vulnerability](https://azure.microsoft.com/blog/protecting-against-the-ssl-3-0-vulnerability/). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -431,7 +431,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: X509Certificate2 @@ -452,7 +452,7 @@ Accept wildcard characters: False The KeySize parameter specifies the size (in bits) of the RSA public key that's associated with the new certificate request or self-signed certificate. Valid values are: - 1024 -- 2048 (This is the default value) +- 2048 (default value) - 4096 ```yaml @@ -474,7 +474,7 @@ Accept wildcard characters: False The PrivateKeyExportable parameter specifies whether the certificate has an exportable private key, and controls whether you can export the certificate from the server (and import the certificate on other servers). Valid values are: - $true: The private key is exportable, so you can export the certificate from the server. -- $false: The private key isn't exportable, so you can't export the certificate. This is the default value. +- $false: The private key isn't exportable, so you can't export the certificate. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md index a39cde59db..230a474641 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md @@ -31,7 +31,7 @@ New-ExchangeSettings [-Name] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md index 1c3e6a1a8f..89aac16ff6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md @@ -34,7 +34,7 @@ New-ExoPhishSimOverrideRule -Policy -SenderIpRanges ` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). +This example creates a new phishing simulation override rule with the specified settings. Regardless of the Name value specified, the rule name is `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). ## PARAMETERS @@ -182,7 +182,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The Name parameter specifies the name for the policy. Regardless of the value you specify, the name will be `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). +The Name parameter specifies the name for the policy. Regardless of the value you specify, the name is `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329). ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md index 919af1904f..675ba08cc7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md @@ -33,7 +33,7 @@ New-ExoSecOpsOverrideRule -Policy ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -42,7 +42,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-ExoSecOpsOverrideRule -Name SecOpsOverrideRule -Policy SecOpsOverridePolicy ``` -This example creates the SecOps mailbox override rule with the specified settings. Regardless of the Name value specified, the rule name will be `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977efb). +This example creates the SecOps mailbox override rule with the specified settings. Regardless of the Name value specified, the rule name is `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977efb). ## PARAMETERS @@ -127,7 +127,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The Name parameter specifies the name for the policy. Regardless of the value you specify, the name will be `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977ef). +The Name parameter specifies the name for the policy. Regardless of the value you specify, the name is `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977ef). ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md index 1ef2e0094b..15c47b377e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md @@ -51,7 +51,7 @@ Federation trusts are trusts created between an Exchange organization and the Mi For more information, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md b/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md index f72b4bc2e4..223d295bfa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md @@ -15,7 +15,7 @@ title: New-Fingerprint ## SYNOPSIS This cmdlet is functional only in on-premises Exchange. -**Note**: In Exchange Online, this cmdlet has been replaced by the [New-DlpFingerPrint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpfingerprint) cmdlet in Security & Compliance PowerShell. +**Note**: In Exchange Online, this cmdlet is replaced by the [New-DlpFingerPrint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpfingerprint) cmdlet in Security & Compliance PowerShell. Use the New-Fingerprint cmdlet to create document fingerprints that are used with data classification rules. Because the results of New-Fingerprint are not stored outside of the data classification rule, you always run New-Fingerprint and New-DataClassification or Set-DataClassification in the same PowerShell session. @@ -33,7 +33,7 @@ New-Fingerprint [[-FileData] ] -Description ## DESCRIPTION Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md index 38a27b3040..4dc46016af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md @@ -34,7 +34,7 @@ New-ForeignConnector [-Name] -AddressSpaces ## DESCRIPTION A Foreign connector uses a Drop directory in the Transport service of a Mailbox server to send messages to a local messaging server that doesn't use SMTP as its primary transport mechanism. These messaging servers are known as foreign gateway servers. Non-Microsoft fax gateway servers are examples of foreign gateway servers. The address spaces assigned to a Foreign connector can be SMTP or non-SMTP. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -77,7 +77,7 @@ Accept wildcard characters: False The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`. -- AddressSpaceType: The address space type may be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed. +- AddressSpaceType: The address space type might be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed. - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com isn't permitted. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of an address type, you can enter any text for the address space. - AddressSpaceCost: The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains the semicolon character (;), you must specify the address space cost. @@ -88,7 +88,7 @@ If you specify the address space type or the address space cost, you must enclos - "SMTP:contoso.com" - contoso.com -You may specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`. +You might specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`. ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md index a51e891a50..e642369e00 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md @@ -13,7 +13,7 @@ title: New-GlobalAddressList # New-GlobalAddressList ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-GlobalAddressList cmdlet to create a global address list (GAL). @@ -70,7 +70,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md index f791c26aab..38416ce39a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md @@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the New-HoldCompliancePolicy cmdlet to create new preservation policies in the Microsoft Purview compliance portal. -**Note**: The New-HoldCompliancePolicy cmdlet has been replaced by the New-RetentionCompliancePolicy cmdlet. If you have scripts that use New-HoldCompliancePolicy, update them to use New-RetentionCompliancePolicy. +**Note**: The New-HoldCompliancePolicy cmdlet is replaced by the New-RetentionCompliancePolicy cmdlet. If you have scripts that use New-HoldCompliancePolicy, update them to use New-RetentionCompliancePolicy. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -37,7 +37,7 @@ New-HoldCompliancePolicy [-Name] ``` ## DESCRIPTION -New policies are not valid and will not be applied until a preservation rule is added to the policy. +New policies are not valid and aren't applied until a preservation rule is added to the policy. To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). @@ -115,7 +115,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md index 59af4874f5..8dab017d8b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md @@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the New-HoldComplianceRule cmdlet to create new preservation rules in the Microsoft Purview compliance portal. -**Note**: The New-HoldComplianceRule cmdlet has been replaced by the New-RetentionComplianceRule cmdlet. If you have scripts that use New-HoldComplianceRule, update them to use New-RetentionComplianceRule. +**Note**: The New-HoldComplianceRule cmdlet is replaced by the New-RetentionComplianceRule cmdlet. If you have scripts that use New-HoldComplianceRule, update them to use New-RetentionComplianceRule. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -49,7 +49,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned New-HoldComplianceRule -Name SeptOneYear -Policy "Internal Company Policy" -ContentDateFrom "09/10/14 5:00 PM" -ContentDateTo "09/10/15 5:00 PM" -HoldContent Unlimited ``` -This example creates a new preservation rule named SeptOneYear and adds it to the existing preservation policy named "Internal Company Policy". Content created or updated between the specified dates will be held indefinitely. +This example creates a new preservation rule named SeptOneYear and adds it to the existing preservation policy named "Internal Company Policy". Content created or updated between the specified dates is held indefinitely. ## PARAMETERS @@ -237,7 +237,7 @@ The HoldDurationDisplayHint parameter specifies the units that are used to displ - Months - Years -For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. +For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration. ```yaml Type: HoldDurationHint diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md index 8bb8f78675..94dea10d3e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md @@ -84,7 +84,7 @@ New-HostedContentFilterPolicy [-Name] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). For more information about the limits for allowed and blocked senders, see [Exchange Online Protection Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-protection-service-description/exchange-online-protection-limits). @@ -139,7 +139,7 @@ For example, if you enter the value `X-This-is-my-custom-header`, the X-header t If you enter a value that contains spaces or colons (:), the value is ignored, and the default X-header is added to the message (`X-This-Is-Spam: This message appears to be spam.`). -Note that this setting is independent of the AddXHeader value of the TestModeAction parameter. +This setting is independent of the AddXHeader value of the TestModeAction parameter. ```yaml Type: String @@ -304,7 +304,7 @@ The BulkSpamAction parameter specifies the action to take on messages that are m - AddXHeader: Add the AddXHeaderValue parameter value to the message header and deliver the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). -- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). - NoAction - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. @@ -325,7 +325,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages will trigger the action that's specified by the BulkSpamAction parameter. +The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages trigger the action specified by the BulkSpamAction parameter. A higher BCL indicates the message is more likely to generate complaints (and is therefore more likely to be spam). For more information, see [Bulk complaint level (BCL) in EOP](https://learn.microsoft.com/defender-office-365/anti-spam-bulk-complaint-level-bcl-about). @@ -366,7 +366,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: Boolean @@ -384,7 +384,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: Boolean @@ -405,7 +405,7 @@ Accept wildcard characters: False The EnableLanguageBlockList parameter enables or disables marking messages that were written in specific languages as spam. Valid values are: - $true: Mark messages hat were written in the languages specified by the LanguageBlockList parameter as spam. -- $false: Don't mark messages as spam solely based on their languages. This is the default value. +- $false: Don't mark messages as spam solely based on their languages. This value is the default. ```yaml Type: Boolean @@ -426,7 +426,7 @@ Accept wildcard characters: False The EnableRegionBlockList parameter enables or disables marking messages that are sent from specific countries or regions as spam. Valid values are: - $true: Mark messages from senders in the RegionBlockList parameter as spam. -- $false: Don't mark messages as spam solely based on the source country or region. This is the default value. +- $false: Don't mark messages as spam solely based on the source country or region. This value is the default. ```yaml Type: Boolean @@ -444,7 +444,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: SmtpAddress @@ -462,7 +462,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: String @@ -480,7 +480,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: String @@ -498,7 +498,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: Int32 @@ -516,7 +516,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: EsnLanguage @@ -656,8 +656,8 @@ Accept wildcard characters: False The IncreaseScoreWithBizOrInfoUrls parameter increases the spam score of messages that contain links to .biz or .info domains. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. -- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting will be marked as spam. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. +- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting are marked as spam. - Test: The action specified by the TestModeAction parameter is taken on the message. ```yaml @@ -678,8 +678,8 @@ Accept wildcard characters: False The IncreaseScoreWithImageLinks parameter increases the spam score of messages that contain image links to remote websites. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. -- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting will be marked as spam. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. +- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting are marked as spam. - Test: The action specified by the TestModeAction parameter is taken on the message. ```yaml @@ -700,8 +700,8 @@ Accept wildcard characters: False The IncreaseScoreWithNumericIps parameter increases the spam score of messages that contain links to IP addresses. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. -- On: The setting is enabled. Messages that contain links to IP addresses are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. Note that not all messages which matches the setting will be marked as spam. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. +- On: The setting is enabled. Messages that contain links to IP addresses are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. Not all messages which matches the setting are marked as spam. - Test: The action specified by the TestModeAction parameter is taken on the message. ```yaml @@ -722,8 +722,8 @@ Accept wildcard characters: False The IncreaseScoreWithRedirectToOtherPort parameter increases the spam score of messages that contain links that redirect to TCP ports other than 80 (HTTP), 8080 (alternate HTTP), or 443 (HTTPS). Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. -- On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. Note that not all messages which matches the setting will be marked as spam. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. +- On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. Not all messages that match this setting are marked as spam. - Test: The action specified by the TestModeAction parameter is taken on the message. ```yaml @@ -744,7 +744,7 @@ Accept wildcard characters: False The InlineSafetyTipsEnabled parameter specifies whether to enable or disable safety tips that are shown to recipients in messages. Valid values are: -- $true: Safety tips are enabled. This is the default value. +- $true: Safety tips are enabled. This value is the default. - $false: Safety tips are disabled. ```yaml @@ -765,7 +765,7 @@ Accept wildcard characters: False The IntraOrgFilterState parameter specifies whether to enable anti-spam filtering for messages sent between internal users (users in the same organization). The action that's configured in the policy for the specified spam filter verdicts is taken on messages sent between internal users. Valid values are: -- Default: This is the default value. Currently, this value is the same as HighConfidencePhish. +- Default: This value is the default. Currently, this value is the same as HighConfidencePhish. - HighConfidencePhish - Phish: Includes phishing and high confidence phishing. - HighConfidenceSpam: Includes high confidence spam, phishing, and high confidence phishing. @@ -815,7 +815,7 @@ Accept wildcard characters: False The MarkAsSpamBulkMail parameter allows spam filtering to act on bulk email messages. Valid values are: - Off: The message is stamped with the BCL, but no action is taken for a bulk email filtering verdict. In effect, the values of the BulkThreshold and BulkSpamAction parameters are irrelevant. -- On: This is the default value. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message. +- On: This value is the default. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message. - Test: This value is available, but isn't used for this parameter. ```yaml @@ -836,7 +836,7 @@ Accept wildcard characters: False The MarkAsSpamEmbedTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Embed tag in html` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -858,7 +858,7 @@ Accept wildcard characters: False The MarkAsSpamEmptyMessages parameter marks a message as spam when the message contains no subject, no content in the message body, and no attachments. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Empty messages are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Empty Message` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -880,7 +880,7 @@ Accept wildcard characters: False The MarkAsSpamFormTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Form tag in html` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -902,7 +902,7 @@ Accept wildcard characters: False The MarkAsSpamFramesInHtml parameter marks a message as spam when the message contains HTML \ or \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ or \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: IFRAME or FRAME in HTML` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -924,7 +924,7 @@ Accept wildcard characters: False The MarkAsSpamFromAddressAuthFail parameter marks a message as spam when Sender ID filtering encounters a hard fail. This setting combines an Sender Policy Framework (SPF) check with a Sender ID check to help protect against message headers that contain forged senders. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages where Sender ID filtering encounters a hard fail are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF From Record Fail` is added to the message. ```yaml @@ -945,7 +945,7 @@ Accept wildcard characters: False The MarkAsSpamJavaScriptInHtml parameter marks a message as spam when the message contains JavaScript or VBScript. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain JavaScript or VBScript are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Javascript or VBscript tags in HTML` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -967,7 +967,7 @@ Accept wildcard characters: False The MarkAsSpamNdrBackscatter parameter marks a message as spam when the message is a non-delivery report (also known as an NDR or bounce messages) sent to a forged sender (known as *backscatter*). Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Backscatter is given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Backscatter NDR` is added to the message. ```yaml @@ -988,7 +988,7 @@ Accept wildcard characters: False The MarkAsSpamObjectTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Object tag in html` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -1010,7 +1010,7 @@ Accept wildcard characters: False The MarkAsSpamSensitiveWordList parameter marks a message as spam when the message contains words from the sensitive words list. Microsoft maintains a dynamic but non-editable list of words that are associated with potentially offensive messages. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain words from the sensitive word list in the subject or message body are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Sensitive word in subject/body` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -1032,7 +1032,7 @@ Accept wildcard characters: False The MarkAsSpamSpfRecordHardFail parameter marks a message as spam when SPF record checking encounters a hard fail. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages sent from an IP address that isn't specified in the SPF Sender Policy Framework (SPF) record in DNS are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF Record Fail` is added to the message. ```yaml @@ -1053,7 +1053,7 @@ Accept wildcard characters: False The MarkAsSpamWebBugsInHtml parameter marks a message as spam when the message contains web bugs (also known as web beacons). Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain web bugs are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Web bug` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -1132,7 +1132,7 @@ The PhishSpamAction parameter specifies the action to take on messages that are - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. -- Quarantine: Move the message to the quarantine. This is the default value. The quarantined message is available to the intended recipients (as of April, 2020) and admins. +- Quarantine: Move the message to the quarantine. This value is the default. The quarantined message is available to the intended recipients (as of April, 2020) and admins. - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as phishing are available to admins and (as of April 2020) the intended recipients. Or, you can use the PhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. @@ -1154,7 +1154,7 @@ Accept wildcard characters: False The PhishZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect phishing in already delivered messages in Exchange Online mailboxes. Valid values are: -- $true: ZAP for phishing messages is enabled. This is the default value. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. +- $true: ZAP for phishing messages is enabled. This value is the default. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. - $false: ZAP for phishing messages is disabled. You configure ZAP for spam with the SpamZapEnabled parameter. @@ -1279,7 +1279,7 @@ The SpamAction parameter specifies the action to take on messages that are marke - AddXHeader: Add the AddXHeaderValue parameter value to the message header, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). -- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. @@ -1329,7 +1329,7 @@ Accept wildcard characters: False The SpamZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect spam in already delivered messages in Exchange Online mailboxes. Valid values are: -- $true: ZAP for spam is enabled. This is the default value. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. +- $true: ZAP for spam is enabled. This value is the default. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. - $false: ZAP for spam is disabled. You configure ZAP for phishing messages with the PhishZapEnabled parameter. @@ -1352,7 +1352,7 @@ Accept wildcard characters: False The TestModeAction parameter specifies the additional action to take on messages when one or more IncreaseScoreWith\* or MarkAsSpam\* ASF parameters are set to the value Test. Valid values are: -- None: This is the default value, and we recommend that you don't change it. +- None: This value is the default, and we recommend that you don't change it. - AddXHeader: The X-header value `X-CustomSpam: This message was filtered by the custom spam filter option` is added to the message. - BccMessage: Redirect the message to the recipients specified by the TestModeBccToRecipients parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md index 7dc54be6f6..4560b98a1b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md @@ -41,7 +41,7 @@ New-HostedContentFilterRule [-Name] -HostedContentFilterPolicy [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Use the Microsoft Defender portal to create anti-spam policies](https://learn.microsoft.com/defender-office-365/anti-spam-policies-configure#use-the-microsoft-defender-portal-to-create-anti-spam-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md index d838d30f5b..944b15fa76 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md @@ -40,7 +40,7 @@ New-HostedOutboundSpamFilterPolicy [-Name] ## DESCRIPTION New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the HostedOutboundSpamFilterPolicy parameter on the New-HostedOutboundSpamFilterRule or Set-HostedOutboundSpamFilterRule cmdlets to associate the policy with a rule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -82,7 +82,7 @@ The ActionWhenThresholdReach parameter specifies the action to take when any of - Alert: No action, alert only. - BlockUser: Prevent the user from sending email messages. -- BlockUserForToday: Prevent the user from sending email messages until the following day. This is the default value. +- BlockUserForToday: Prevent the user from sending email messages until the following day. This value is the default. ```yaml Type: OutboundRecipientLimitsExceededAction @@ -121,7 +121,7 @@ Accept wildcard characters: False The AutoForwardingMode specifies how the policy controls automatic email forwarding to external recipients. Valid values are: -- Automatic: This is the default value. This value is now the same as Off. When this value was originally introduced, it was equivalent to On. Over time, thanks to the principles of [secure by default](https://learn.microsoft.com/defender-office-365/secure-by-default), the effect of this value was eventually changed to Off for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/all-you-need-to-know-about-automatic-email-forwarding-in/ba-p/2074888). +- Automatic: This value is the default. This value is now the same as Off. When this value was originally introduced, it was equivalent to On. Over time, thanks to the principles of [secure by default](https://learn.microsoft.com/defender-office-365/secure-by-default), the effect of this value was eventually changed to Off for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/all-you-need-to-know-about-automatic-email-forwarding-in/ba-p/2074888). - On: Automatic external email forwarding isn't disabled by the policy. - Off: Automatic external email forwarding is disabled by the policy and results in a non-delivery report (also known as an NDR or bounce message) to the sender. @@ -167,7 +167,7 @@ Accept wildcard characters: False The BccSuspiciousOutboundMail parameter specifies whether to add recipients to the Bcc field of outgoing spam messages. Valid values are: - $true: The recipients specified by the BccSuspiciousOutboundAdditionalRecipients parameter are added to outgoing spam messages. -- $false: No additional messages are added to outgoing spam messages. This is the default value. +- $false: No additional messages are added to outgoing spam messages. This value is the default. ```yaml Type: Boolean @@ -185,12 +185,12 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). +**Note**: This setting is replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). The NotifyOutboundSpam parameter specify whether to notify admins when outgoing spam is detected. Valid values are: - $true: Notify the admins specified by the NotifyOutboundSpamRecipients parameter. -- $false: Don't send notifications. This is the default value. +- $false: Don't send notifications. This value is the default. ```yaml Type: Boolean @@ -208,7 +208,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). +**Note**: This setting is replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). The NotifyOutboundSpamRecipients parameter specifies the email addresses of admins to notify when an outgoing spam is detected. You can specify multiple email addresses separated by commas. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md index 1afdd51735..423016b19a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md @@ -38,7 +38,7 @@ New-HostedOutboundSpamFilterRule [-Name] -HostedOutboundSpamFilterPolic ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -142,7 +142,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: -- $true: The rule is enabled. This is the default value. +- $true: The rule is enabled. This value is the default. - $false: The rule is disabled. In the properties of the rule, the value of this parameter is visible in the State property. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md index eeb2dd5b03..8ba792670c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md @@ -51,7 +51,7 @@ The available settings in this cmdlet are configured when the Hybrid Configurati For more information, see [Exchange Server hybrid deployments](https://learn.microsoft.com/exchange/exchange-hybrid). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md index bed3ce6485..8c1f5d800e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md @@ -53,7 +53,7 @@ New-InboundConnector [-Name] -SenderDomains ## DESCRIPTION Inbound connectors accept email messages from remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -162,7 +162,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f Valid values are: -- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. +- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. ```yaml @@ -222,7 +222,7 @@ Accept wildcard characters: False The ConnectorSource parameter specifies how the connector is created. Valid input for this parameter includes the following values: -- Default: The connector is manually created. This is the default value. +- Default: The connector is manually created. This value is the default. - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. @@ -292,7 +292,7 @@ Accept wildcard characters: False The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connectors. Valid values are: - $true: Only the last message source is skipped. -- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This is the default value. +- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This value is the default. ```yaml Type: Boolean @@ -368,7 +368,7 @@ Accept wildcard characters: False The Enabled parameter enables or disables the connector. Valid values are: -- $true: The connector is enabled. This is the default value. +- $true: The connector is enabled. This value is the default. - $false: The connector is disabled. ```yaml @@ -389,7 +389,7 @@ Accept wildcard characters: False The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by a Partner type connector. Valid values are: -- $true: Reject messages if they aren't sent over TLS. This is the default value +- $true: Reject messages if they aren't sent over TLS. This value is the default - $false: Allow messages if they aren't sent over TLS. **Note**: This parameter applies only to Partner type connectors. @@ -413,7 +413,7 @@ Accept wildcard characters: False The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the Partner type connector. Valid values are: - $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value. -- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value. +- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This value is the default. **Note**: This parameter applies only to Partner type connectors. @@ -436,7 +436,7 @@ Accept wildcard characters: False The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses for Partner type connectors. Valid values are: - $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter. -- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value. +- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This value is the default. **Note**: This parameter applies only to Partner type connectors. @@ -522,7 +522,7 @@ Accept wildcard characters: False The TreatMessagesAsInternal parameter specifies an alternative method to identify messages sent from an on-premises organization as internal messages. You should only consider using this parameter when your on-premises organization doesn't use Exchange. Valid values are: - $true: Messages are considered internal if the sender's domain matches a domain that's configured in Microsoft 365. This setting allows internal mail flow between Microsoft 365 and on-premises organizations that don't have Exchange Server 2010 or later installed. However, this setting has potential security risks (for example, internal messages bypass antispam filtering), so use caution when configuring this setting. -- $false: Messages aren't considered internal. This is the default value. +- $false: Messages aren't considered internal. This value is the default. In hybrid environments, you don't need to use this parameter, because the Hybrid Configuration wizard automatically configures the required settings on the Inbound connector in Microsoft 365 and the Send connector in the on-premises Exchange organization (the CloudServicesMailEnabled parameter). diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md index c9db1ab9c4..7afb9dee03 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md @@ -13,7 +13,7 @@ title: New-InboxRule # New-InboxRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-InboxRule cmdlet to create Inbox rules in mailboxes. Inbox rules process messages in the Inbox based on conditions and take actions such as moving a message to a specified folder or deleting a message. @@ -117,7 +117,7 @@ When you create, modify, remove, enable, or disable an Inbox rule in Exchange Po Parameters that are used for conditions also have corresponding exception parameters. When conditions specified in an exception are matched, the rule isn't applied to the message. Exception parameters begin with ExceptIf. For example, the exception parameter for SubjectOrBodyContainsWords is ExceptIfSubjectOrBodyContainsWords. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -179,7 +179,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The ValidateOnly switch tells the cmdlet to evaluate the conditions and requirements necessary to perform the operation and then reports whether the operation will succeed or fail. No changes are made when the ValidateOnly switch is used. +The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -944,7 +944,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the ExceptIfWithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of ExceptIfWithinSizeRangeMinimum. @@ -976,7 +976,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the ExceptIfWithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of ExceptIfWithinSizeRangeMaximum. @@ -1055,7 +1055,7 @@ Accept wildcard characters: False The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet. +A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet. ```yaml Type: SwitchParameter @@ -1823,7 +1823,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the WithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of WithinSizeRangeMinimum. @@ -1855,7 +1855,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the WithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of WithinSizeRangeMaximum. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md index 8b9e46152e..9937381641 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md @@ -269,7 +269,7 @@ Accept wildcard characters: False The State parameter specifies whether the information barrier policy is active or inactive. Valid values are: - Active -- Inactive (This is the default value.) +- Inactive (This value is the default.) ```yaml Type: EopInformationBarrierPolicyState diff --git a/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md index dd86a9f2b3..69e235ceee 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md @@ -13,7 +13,7 @@ title: New-IntraOrganizationConnector # New-IntraOrganizationConnector ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-IntraOrganizationConnector cmdlet to create an Intra-Organization connector between two on-premises Exchange forests in an organization, between an Exchange on-premises organization and an Exchange Online organization, or between two Exchange Online organizations. This connector enables feature availability and service connectivity across the organizations using a common connector and connection endpoints. @@ -36,7 +36,7 @@ The New-IntraOrganizationConnector cmdlet is used to create a connection for fea For hybrid deployments between on-premises Exchange and Exchange Online organizations, the New-IntraOrganizationConnector cmdlet is used by the Hybrid Configuration wizard. Typically, the Intra-Organization connector is configured when the hybrid deployment is initially created by the wizard. We strongly recommend that you use the Hybrid Configuration wizard to create the Intra-Organization connector when configuring a hybrid deployment with an Exchange Online organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -89,7 +89,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The TargetAddressDomains parameter specifies the domain namespaces that will be used in the Intra-organization connector. These domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity. +The TargetAddressDomains parameter specifies the domain namespaces to use in the Intra-organization connector. These domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity. You specify multiple domain values separated by commas. @@ -172,7 +172,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services that will be used in the Intra-Organization connector. +The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services to use in the Intra-Organization connector. ```yaml Type: Uri diff --git a/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md index 0103a92195..97291cdb9b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md @@ -13,7 +13,7 @@ title: New-JournalRule # New-JournalRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-JournalRule cmdlet to create a journal rule in your organization. @@ -37,7 +37,7 @@ The New-JournalRule cmdlet creates a journal rule in your organization. By default, new journal rules are disabled unless the Enabled parameter is set to $true. For more information about how to enable a new journal rule that was created in a disabled state, see [Enable-JournalRule](https://learn.microsoft.com/powershell/module/exchangepowershell/enable-journalrule). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-Label.md b/exchange/exchange-ps/ExchangePowerShell/New-Label.md index 6a8b3932a6..a7369fefac 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-Label.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-Label.md @@ -183,7 +183,7 @@ Some of the settings that you configure with this parameter are supported only b Supported settings for built-in labeling: -- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting impacts services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `New-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content). +- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting affects services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `New-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content). - **Color**: Specifies a label color as a hex triplet code for the red, green, and blue (RGB) components of the color. Example: `New-Label -DisplayName "General" -Name "General" -Tooltip "Business data that is not intended for public consumption." -AdvancedSettings @{color="#40e0d0"}`. For more information, see [Configuring custom colors by using PowerShell](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configuring-custom-colors-by-using-powershell). @@ -878,7 +878,7 @@ The feature for this parameter is currently in Public Preview, and is not availa The EncryptionDoubleKeyEncryptionUrl parameter specifies the Double Key Encryption endpoint URL. -You can't remove the URL after the label has been created; you can only modify it. +You can't remove the URL after the label is created; you can only modify it. This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md index ab078d7da6..c4edd6a938 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md @@ -130,7 +130,7 @@ Supported settings for built-in labeling: - **teamworkdefaultlabelid**: Outlook and Teams apps that support this setting apply a default label, or no label for meetings. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{teamworkdefaultlabelid="General"}`. For more information about labeling meetings, see [Use sensitivity labels to protect calendar items, Teams meetings, and chat](https://learn.microsoft.com/purview/sensitivity-labels-meetings). -- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) will be displayed. Users can't revert this setting in the app. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}` +- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) are displayed. Users can't revert this setting in the app. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}` Additionally, for Power BI: diff --git a/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md index ad9a4a3cdd..2554ec465a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md @@ -34,7 +34,7 @@ New-M365DataAtRestEncryptionPolicy [-Name] -AzureKeyIDs -ExternalEmailAddress ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -286,7 +286,7 @@ Accept wildcard characters: False The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: -- BinHex (This is the default value) +- BinHex (default value) - UuEncode - AppleSingle - AppleDouble @@ -316,7 +316,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -343,7 +343,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -398,7 +398,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -469,7 +469,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -494,7 +494,7 @@ Accept wildcard characters: False The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are: - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact. -- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. +- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md b/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md index 15dda9b258..a2f50ad71e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md @@ -13,7 +13,7 @@ title: New-MailMessage # New-MailMessage ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MailMessage cmdlet to create an email message for the specified user mailbox and place the email message in the Drafts folder of the user's mailbox. @@ -35,7 +35,7 @@ New-MailMessage ## DESCRIPTION If the cmdlet is run without specifying the Subject or Body parameters, an empty email message is placed in the user's Drafts folder. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md index b40c8f5a49..3aa57b37d4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md @@ -13,7 +13,7 @@ title: New-MailUser # New-MailUser ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MailUser cmdlet to create mail users. Mail users (also known as mail-enabled users) have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. Email messages sent to mail users are delivered to the specified external email address. @@ -221,7 +221,7 @@ New-MailUser [-Name] -MicrosoftOnlineServicesID -Passwo ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -604,7 +604,7 @@ Accept wildcard characters: False The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: -- BinHex (This is the default value) +- BinHex (default value) - UuEncode - AppleSingle - AppleDouble @@ -654,7 +654,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -680,7 +680,7 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text -- Mime (This is the default value) +- Mime (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -737,7 +737,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -808,7 +808,7 @@ Accept wildcard characters: False The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are: -- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value. +- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This value is the default. - $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC. Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server. @@ -836,7 +836,7 @@ This parameter is available only in on-premises Exchange. The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are: - $true: The user is required to change their password the next time they log on. -- $false: The user isn't required to change their password the next time they log on. This is the default value. +- $false: The user isn't required to change their password the next time they log on. This value is the default. ```yaml Type: Boolean @@ -856,7 +856,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -876,7 +876,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -901,7 +901,7 @@ Accept wildcard characters: False The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are: - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact. -- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. +- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md index 6e85684156..28c5437879 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md @@ -13,7 +13,7 @@ title: New-Mailbox # New-Mailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-Mailbox cmdlet to create mailboxes and user accounts at the same time. @@ -764,7 +764,7 @@ New-Mailbox [-Name] [-SupervisoryReviewPolicy] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. @@ -802,7 +802,7 @@ Set-Mailbox -Identity Sales -GrantSendOnBehalfTo MarketingSG Add-MailboxPermission -Identity Sales -User MarketingSG -AccessRights FullAccess -InheritanceType All ``` -This example creates the shared mailbox "Sales Department" and grants Full Access and Send on Behalf permissions for the security group "MarketingSG". Users who are members of the security group will be granted the permissions to the mailbox. +This example creates the shared mailbox "Sales Department" and grants Full Access and Send on Behalf permissions for the security group "MarketingSG". Users who are members of the security group are granted the permissions to the mailbox. This example assumes that you've already created a mail-enabled security group named "MarketingSG" by using the New-DistributionGroup cmdlet. @@ -1584,7 +1584,7 @@ The HoldForMigration switch specifies whether to prevent any client or user, exc You need to use this parameter when you create the first public folder, which is called the hierarchy mailbox, in your organization. -Use this parameter only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you won't be able to create any public folders. +Use this parameter only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you can't create any public folders. ```yaml Type: SwitchParameter @@ -1640,7 +1640,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and won't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user will still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox. +The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and can't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user can still access the specified public folder mailbox, even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox. ```yaml Type: Boolean @@ -1828,7 +1828,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -1971,7 +1971,7 @@ Accept wildcard characters: False The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are: -- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value. +- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This value is the default. - $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC. Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server. @@ -1997,7 +1997,7 @@ Accept wildcard characters: False The ResetPasswordOnNextLogon parameter specifies whether the user is required to change their password the next time they log on to their mailbox. Valid values are: - $true: The user is required to change their password the next time they log on to their mailbox. -- $false: The user isn't required to change their password the next time they log on to their mailbox. This is the default value. +- $false: The user isn't required to change their password the next time they log on to their mailbox. This value is the default. ```yaml Type: Boolean @@ -2127,7 +2127,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -2147,7 +2147,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md index 668aa944b8..4aa8ca23e8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md @@ -16,7 +16,7 @@ title: New-MailboxAuditLogSearch > [!NOTE] > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MailboxAuditLogSearch cmdlet to search mailbox audit logs and have search results sent via email to specified recipients. @@ -45,7 +45,7 @@ The New-MailboxAuditLogSearch cmdlet performs an asynchronous search of mailbox To search mailbox audit logs for a single mailbox and have the results displayed in the Exchange Management Shell window, use the Search-MailboxAuditLog cmdlet instead. To learn more about mailbox audit logging, see [Mailbox audit logging in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mailbox-audit-logging/mailbox-audit-logging). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -172,7 +172,7 @@ The ExternalAccess parameter specifies whether to return only audit log entries $true: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are returned. -$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This is the default value. +$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md index 6626bb96cf..13b7f9cdaf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md @@ -53,7 +53,7 @@ New-MailboxDatabase [[-Name] ] -Server ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md index 60444e5677..a4d5b91ef0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md @@ -120,14 +120,14 @@ New-MailboxExportRequest [-Mailbox] -ComplianceStor ## DESCRIPTION You can create more than one mailbox export request per mailbox, and each mailbox export request must have a unique name. Microsoft Exchange automatically generates up to 10 unique names for a mailbox export request. However, to create more than 10 export requests for a mailbox, you need to specify a unique name when creating the export request. You can remove existing export requests with the Remove-MailboxExportRequest cmdlet before starting a new request with the default request name `\MailboxExportX` (where X = 0-9). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). You need to grant the following permission to the group Exchange Trusted Subsystem to the network share where you want to export or import PST files: - To import PST files from the share: Read permission - To save exported PST files to the share: Read/Write permission. -If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. +If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share. ## EXAMPLES @@ -223,7 +223,7 @@ You need to grant the following permission to the group Exchange Trusted Subsyst - To import PST files from the share: Read permission - To save exported PST files to the share: Read/Write permission. -If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. +If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share. ```yaml Type: LongPath @@ -345,7 +345,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit is 30 days. +The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before it's automatically removed. The default value is 30 days. ```yaml Type: Unlimited @@ -389,7 +389,7 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl - ForceCopy - KeepAll - KeepLatestItem -- KeepSourceItem (This is the default value.) +- KeepSourceItem (This value is the default.) - KeepTargetItem - UpdateFromSource @@ -409,9 +409,9 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -**Important**: You can't use this parameter to export between two dates. If you try, you'll get system convert errors. You can export from a specific date, or export to a specific date, but not both. +**Important**: You can't use this parameter to export between two dates. You can export from a specific date, or export to a specific date, but not both. -The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter will be exported into the .pst file. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`. +The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter are exported into the .pst file. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`. - Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables. - Property is a filterable property. For filterable properties, see [Filterable properties for the ContentFilter parameter](https://learn.microsoft.com/exchange/filterable-properties-for-the-contentfilter-parameter). @@ -721,7 +721,7 @@ The Priority parameter specifies the order in which the request should be proces - Lower - Low -- Normal (This is the default value.) +- Normal (This value is the default.) - High - Higher - Highest @@ -824,7 +824,7 @@ Accept wildcard characters: False The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. -If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. +If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md index 01dfb10e92..d7e9d64fe5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md @@ -13,7 +13,7 @@ title: New-MailboxFolder # New-MailboxFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MailboxFolder cmdlet to create folders in your own mailbox. Administrators can't use this cmdlet to create folders in other mailboxes (the cmdlet is available only from the MyBaseOptions user role). @@ -32,7 +32,7 @@ New-MailboxFolder [-Name] -Parent ## DESCRIPTION If no parent folder is specified, the cmdlet creates a mail folder in the root folder hierarchy of the mailbox. If the mailbox isn't specified, the cmdlet creates the folder in the mailbox of the user currently running the task. When run, the cmdlet returns the new folder name and the folder path as the output. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). . +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). . ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md index 935c6d2a7b..3354f48df9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md @@ -13,7 +13,7 @@ title: New-MailboxImportRequest # New-MailboxImportRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MailboxImportRequest cmdlet to begin the process of importing a .pst file to a mailbox or archive. @@ -133,7 +133,7 @@ In on-premises Exchange, you need to grant the following permission to the group - To import PST files from the share: Read permission - To save exported PST files to the share: Read/Write permission. -If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. +If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share. ## EXAMPLES @@ -246,7 +246,7 @@ You need to grant the following permission to the group Exchange Trusted Subsyst - To import PST files from the share: Read permission - To save exported PST files to the share: Read/Write permission. -If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share. +If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share. ```yaml Type: LongPath @@ -370,7 +370,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default value of the CompletedRequestAgeLimit parameter is 30 days. +The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before being automatically removed. The default value is 30 days. ```yaml Type: Unlimited @@ -414,7 +414,7 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl - ForceCopy (Exchange 2016 or later) - KeepAll - KeepLatestItem -- KeepSourceItem (This is the default value) +- KeepSourceItem (default value) - KeepTargetItem (Exchange 2016 or later) - UpdateFromSource (Exchange 2016 or later) @@ -894,7 +894,7 @@ Accept wildcard characters: False The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. -If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. +If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md index e79715622b..4342464833 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md @@ -51,7 +51,7 @@ After you begin a repair request, you can't stop it unless you dismount the data To avoid performance problems, only one request can be active on a server for a database-level repair, or up to 100 requests can be active on a server for a mailbox-level repair. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md index b5a99217c4..4df394dfdc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md @@ -13,7 +13,7 @@ title: New-MailboxRestoreRequest # New-MailboxRestoreRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MailboxRestoreRequest cmdlet to restore a soft-deleted or disconnected mailbox. This cmdlet starts the process of moving content from the soft-deleted mailbox, disabled mailbox, or any mailbox in a recovery database into a connected primary or archive mailbox. @@ -220,15 +220,15 @@ To view soft-deleted mailboxes, run the Get-MailboxStatistics cmdlet against a d A mailbox is marked as Disabled a short time after the Disable-Mailbox or Remove-Mailbox command completes. -The mailbox won't be marked as Disabled until the Microsoft Exchange Information Store service determines that Active Directory has been updated with the disabled mailbox's information. You can expedite the process by running the Update-StoreMailboxState cmdlet against that database. +The mailbox isn't marked as Disabled until the Microsoft Exchange Information Store service determines that Active Directory is updated with the disabled mailbox's information. You can expedite the process by running the Update-StoreMailboxState cmdlet against that database. Exchange retains disabled mailboxes in the mailbox database based on the deleted mailbox retention settings configured for that mailbox database. After the specified period of time, the mailbox is permanently deleted. To view disabled mailboxes, run the Get-MailboxStatistics cmdlet against a database and look for results that have a DisconnectReason with a value of Disabled. For more information, see Examples 2 and 3 later in this topic. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). -**Note**: To restore the contents of a primary mailbox to an archive mailbox, use the TargetRootFolder parameter to specify the archive mailbox folders to migrate the content to. This content will be visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users. +**Note**: To restore the contents of a primary mailbox to an archive mailbox, use the TargetRootFolder parameter to specify the archive mailbox folders to migrate the content to. This content is visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users. ## EXAMPLES @@ -563,7 +563,7 @@ The AssociatedMessagesCopyOption parameter specifies whether associated messages - DoNotCopy: The associated messages aren't copied. - MapByMessageClass: Find the associated message by looking up the MessageClass attribute of the source message. If there's an associated message of this class in both source and target folders, it overwrites the associated message in the target. If there isn't an associated message in the target, it creates a copy in the target. -- Copy: Copy associated messages from the source to the target. If the same message type exists both in the source and the target location, these associated messages are duplicated. This is the default value. +- Copy: Copy associated messages from the source to the target. If the same message type exists both in the source and the target location, these associated messages are duplicated. This value is the default. Content filtering doesn't apply to associated messages. @@ -589,7 +589,7 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -669,7 +669,7 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl - ForceCopy - KeepAll - KeepLatestItem -- KeepSourceItem (This is the default value.) +- KeepSourceItem (This value is the default.) - KeepTargetItem - UpdateFromSource @@ -691,7 +691,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter will be restored. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`. +The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter are restored. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`. - Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables. - Property is a filterable property. For filterable properties, see [Filterable properties for the ContentFilter parameter](https://learn.microsoft.com/exchange/filterable-properties-for-the-contentfilter-parameter). @@ -907,7 +907,7 @@ Valid input for this parameter is an integer or the value unlimited. The default If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -972,7 +972,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal (This is the default value.) +- Normal (This value is the default.) - High - Higher - Highest @@ -1086,7 +1086,7 @@ Accept wildcard characters: False The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. -If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. +If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet. ```yaml Type: SwitchParameter @@ -1142,7 +1142,7 @@ Accept wildcard characters: False The TargetRootFolder parameter specifies the top-level folder in which to restore data. If you don't specify this parameter, the command restores folders to the top of the folder structure in the target mailbox or archive. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure. -**Note**: To restore the contents of a primary mailbox to an archive mailbox, use this parameter to specify the archive mailbox folders to migrate the content to. This content will be visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users. +**Note**: To restore the contents of a primary mailbox to an archive mailbox, use this parameter to specify the archive mailbox folders to migrate the content to. This content is visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users. ```yaml Type: String @@ -1164,7 +1164,7 @@ The TargetType parameter specifies the type of mailbox that's the target for the - Archive - MailboxLocation -- Primary (This is the default value) +- Primary (default value) ```yaml Type: TargetTypeComponent diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md index 33a76bb56f..36cb459e8b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md @@ -13,7 +13,7 @@ title: New-MailboxSearch # New-MailboxSearch ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MailboxSearch cmdlet to create a mailbox search and either get an estimate of search results, place search results on In-Place Hold or copy them to a Discovery mailbox. You can also place all contents in a mailbox on hold by not specifying a search query, which accomplishes similar results as Litigation Hold. @@ -62,7 +62,7 @@ By default, mailbox searches are performed across all Exchange 2013 or later Mai For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and [In-Place Hold and Litigation Hold in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/holds/holds). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -130,7 +130,7 @@ Accept wildcard characters: False The AllPublicFolderSources parameter specifies whether to include all public folders in the organization in the search. Valid values are: - $true: All public folders are included in the search. This value is required when the value of the AllSourceMailboxes parameter is $false and you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). -- $false: No public folders are included in the search. This is the default value. You can use this value when the value of the AllSourceMailboxes parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). +- $false: No public folders are included in the search. This value is the default. You can use this value when the value of the AllSourceMailboxes parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean @@ -151,7 +151,7 @@ Accept wildcard characters: False The AllSourceMailboxes parameter specifies whether to include all mailboxes in the search. Valid values are: - $true: All mailboxes are included in the search. This value is required when the value of the AllPublicFolderSources parameter is $false and you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). -- $false: All mailboxes aren't included in the search. This is the default value. You can use this value when the value of the AllPublicFolderSources parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). +- $false: All mailboxes aren't included in the search. This value is the default. You can use this value when the value of the AllPublicFolderSources parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean @@ -270,7 +270,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The EstimateOnly switch specifies that only an estimate of the number of items that will be returned is provided. You don't need to specify a value with this switch. +The EstimateOnly switch specifies that only an estimate of the number of items to be returned is provided. You don't need to specify a value with this switch. If you don't use this switch, messages are copied to the target mailbox. @@ -292,7 +292,7 @@ Accept wildcard characters: False The ExcludeDuplicateMessages parameter eliminates duplication of messages in search results. Valid values are: -- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This is the default value. +- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This value is the default. - $false: Copy all instances of a message if the same message exists in multiple folders or mailboxes. ```yaml @@ -372,11 +372,11 @@ Accept wildcard characters: False The InPlaceHoldEnabled parameter specifies whether to set an In-Place Hold on items in the search results. Valid values are: - $true: In-Place Hold is enabled on the search results. -- $false: In-Place Hold isn't enabled on the search results. This is the default value. +- $false: In-Place Hold isn't enabled on the search results. This value is the default. You can't set an In-Place Hold on the search results when the AllSourceMailboxes parameter is $true. -If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command may succeed but the mailboxes are not placed on In-Place Hold. +If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command might succeed but the mailboxes are not placed on In-Place Hold. ```yaml Type: Boolean @@ -415,7 +415,7 @@ Accept wildcard characters: False The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold onthe mailbox items (all mailbox items or the items that are returned in the search query results). The duration is calculated from the time the item is received or created in the mailbox. Valid values are: - An integer. -- The value unlimited. This is the default value. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false. +- The value unlimited. This value is the default. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false. ```yaml Type: Unlimited @@ -456,7 +456,7 @@ Accept wildcard characters: False The LogLevel parameter specifies the logging level for the search. Valid values are: - Suppress: No logs are kept. -- Basic: Basic information about the query and who ran it is kept. This is the default value. +- Basic: Basic information about the query and who ran it is kept. This value is the default. - Full: In addition to the information kept by the Basic log level, the Full log level adds a complete list of search results. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md index b137806a42..952710db59 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md @@ -13,7 +13,7 @@ title: New-MalwareFilterPolicy # New-MalwareFilterPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MalwareFilterPolicy cmdlet to create malware filter policies in your organization. @@ -56,7 +56,7 @@ New-MalwareFilterPolicy [-Name] ## DESCRIPTION New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the MalwareFilterPolicy parameter on the New-MalwareFilterRule or Set-MalwareFilterRule cmdlets to associate the policy with a rule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -98,7 +98,7 @@ This parameter is available only in on-premises Exchange. The Action parameter specifies the action to take when malware is detected in a message. Valid values are: -- DeleteMessage: Handles the message without notifying the recipients. This is the default value. +- DeleteMessage: Handles the message without notifying the recipients. This value is the default. - DeleteAttachmentAndUseDefaultAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the default alert text. - DeleteAttachmentAndUseCustomAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the custom alert text specified by the CustomAlertText parameter. @@ -141,7 +141,7 @@ This parameter is available only in on-premises Exchange. The BypassInboundMessages parameter enables or disables malware filtering on incoming messages (messages entering the organization). Valid values are: - $true: Malware filtering is disabled on inbound messages. -- $false: Malware filtering is enabled on inbound messages. This is the default value. +- $false: Malware filtering is enabled on inbound messages. This value is the default. ```yaml Type: Boolean @@ -164,7 +164,7 @@ This parameter is available only in on-premises Exchange. The BypassOutboundMessages parameter enables or disables malware filtering on outgoing messages (messages leaving the organization). Valid values are: - $true: Malware filtering is disabled on outbound messages. -- $false: Malware filtering is enabled on outbound messages. This is the default value. +- $false: Malware filtering is enabled on outbound messages. This value is the default. ```yaml Type: Boolean @@ -418,7 +418,7 @@ Accept wildcard characters: False The EnableExternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from external senders, a notification messages is sent to the email address that's specified by the ExternalSenderAdminAddress parameter. -- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This is the default value. +- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This value is the default. **Note**: Admin notifications are sent only for _attachments_ that are classified as malware. @@ -443,7 +443,7 @@ This parameter is available only in on-premises Exchange. The EnableExternalSenderNotifications parameter enables or disables sending notification messages to external senders for malware detections in their messages. Valid values are: - $true: When malware is detected in a message from an external sender, send them a notification message. -- $false: Don't send malware detection notification messages to external message senders. This is the default value. +- $false: Don't send malware detection notification messages to external message senders. This value is the default. ```yaml Type: Boolean @@ -465,7 +465,7 @@ This parameter is available only in the cloud-based service. The EnableFileFilter parameter enables or disables the common attachments filter (also known as common attachment blocking). Valid values are: -- $true: The common attachments filter is enabled. This is the default value. +- $true: The common attachments filter is enabled. This value is the default. - $false: The common attachments filter is disabled. You specify the file types using the FileTypes parameter. A default list of values is automatically provided, but you can customize it. @@ -491,7 +491,7 @@ Accept wildcard characters: False The EnableInternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from internal senders, a notification messages is sent to the email address that's specified by the InternalSenderAdminAddress parameter. -- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This is the default value. +- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This value is the default. **Note**: Admin notifications are sent only for _attachments_ that are classified as malware. @@ -516,7 +516,7 @@ This parameter is available only in on-premises Exchange. The EnableInternalSenderNotifications parameter enables or disables sending notification messages to internal senders for malware detections in their messages. Valid values are: - $true: When malware is detected in a message from an internal sender, send them a notification message. -- $false: Don't send malware detection notification messages to internal message senders. This is the default value. +- $false: Don't send malware detection notification messages to internal message senders. This value is the default. ```yaml Type: Boolean @@ -559,7 +559,7 @@ This parameter is available only in the cloud-based service. The FileTypeAction parameter specifies what happens to messages that contain one or more attachments where the file extension is included in the FileTypes parameter (the common attachments filter). Valid values are: - Quarantine: Quarantine the message. Whether or not the recipient is notified depends on the quarantine notification settings in the quarantine policy that's selected for the malware filter policy by the QuarantineTag parameter. -- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This is the default value. +- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This value is the default. This parameter is meaningful only when the value of the EnableFileFilter parameter is $true. @@ -701,7 +701,7 @@ This parameter is available only in the cloud-based service. The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware in cloud mailboxes. ZAP detects malware in unread messages that have already been delivered to the user's Inbox. Valid values are: -- $true: ZAP for malware is enabled. Unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. This is the default value. +- $true: ZAP for malware is enabled. Unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. This value is the default. - $false: ZAP for malware is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md index 31f0a6a755..2b3a5a5742 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md @@ -13,7 +13,7 @@ title: New-MalwareFilterRule # New-MalwareFilterRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MalwareFilterRule cmdlet to create malware filter rules in your organization. @@ -42,7 +42,7 @@ New-MalwareFilterRule [-Name] -MalwareFilterPolicy [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Anti-malware policies](https://learn.microsoft.com/defender-office-365/anti-malware-protection-about#anti-malware-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md index 926d185d37..18d380d7d6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md @@ -46,7 +46,7 @@ Managed content settings are settings that you associate with managed folders to For more information about managed content settings, see [Messaging Records Management](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123507(v=exchg.141)). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -55,7 +55,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi New-ManagedContentSettings -Name "CS-Exec-DeletedItems" -FolderName "Exec-DeletedItems" -MessageClass * -RetentionEnabled $true -RetentionAction DeleteAndAllowRecovery -AgeLimitForRetention 30.00:00:00 -TriggerForRetention WhenDelivered ``` -This example creates managed content settings for the managed default folder Exec-DeletedItems. When added to a managed folder mailbox policy and applied to a mailbox, items in the Deleted Items folder will be permanently deleted 30 days from the date of delivery. +This example creates managed content settings for the managed default folder Exec-DeletedItems. When added to a managed folder mailbox policy and applied to a mailbox, items in the Deleted Items folder are permanently deleted 30 days from the date of delivery. ### Example 2 ```powershell @@ -362,7 +362,7 @@ Valid values include: - WhenDelivered - WhenMoved -This value corresponds to the 0x4 bit of the msExchELCFlags attribute in Active Directory. The flag is set to $true if the item will expire based on the date it was moved and $false if the item will expire based on the delivery date. +This value corresponds to the 0x4 bit of the msExchELCFlags attribute in Active Directory. The flag is set to $true if the item expires based on the date it was moved and $false if the item expires based on the delivery date. If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md index 83bb4f8e24..826712ca3c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md @@ -62,7 +62,7 @@ The New-ManagedFolder cmdlet creates a new managed folder in Active Directory. A By default, managed custom folders are created with this cmdlet. However, you can also create additional copies of managed default folders using the DefaultFolderType parameter to specify which type of default folder to create (for example, an additional Inbox folder). When you create multiple copies of a managed default folder, you can assign different content settings to each one. For example, you could have two Inbox folders, one named InboxSixMonths and another named InboxOneYear. Then, you could assign a retention time of six months to the first folder and one year to the second folder with the New-ManagedContentSettings cmdlet (or using the New Managed Content Settings wizard in the Exchange Management Console). You must assign a unique name (using the Name parameter) to each of the managed default folders that you create. Users, however, always see the unaltered default folder name. In the example, whether users are assigned an InboxSixMonths folder or an InboxOneYear folder, the Inbox that they see in their mailbox is labeled Inbox. Although the folder names that users see in their mailboxes can be reassigned for managed custom folders (using the Set-ManagedFolder command FolderName parameter), the folder names seen by users for managed default folders can't be changed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -305,7 +305,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items may be added. Storage size limits can be specified in kilobytes (KB) or megabytes (MB), for example, 100 KB or 5 MB. +The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items might be added. Storage size limits can be specified in kilobytes (KB) or megabytes (MB), for example, 100 KB or 5 MB. ```yaml Type: Unlimited diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md index f969abf078..5a615b5bc8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md @@ -33,7 +33,7 @@ New-ManagedFolderMailboxPolicy [-Name] ## DESCRIPTION Managed folder mailbox policies are applied to user mailboxes to control message retention settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). Managed custom folders are a premium feature of messaging records management (MRM). Mailboxes with policies that include managed custom folders require an Exchange Server Enterprise client access license (CAL). diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md index 8a9bd82382..fa552a0a5e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md @@ -13,7 +13,7 @@ title: New-ManagementRole # New-ManagementRole ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-ManagementRole cmdlet to create a management role based on an existing role or create an unscoped management role. @@ -56,7 +56,7 @@ After you create a role, you can change the management role entries on the role For more information about management roles, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -81,7 +81,7 @@ For more information about pipelining and the Where cmdlet, see the following to New-ManagementRole -Name "In-house scripts" -UnScopedTopLevel ``` -In on-premises Exchange, this example creates the unscoped management role In-house scripts. Note that the UnScopedTopLevel switch requires the Unscoped Role Management role, which isn't assigned to any role group by default. +In on-premises Exchange, this example creates the unscoped management role In-house scripts. The UnScopedTopLevel switch requires the Unscoped Role Management role, which isn't assigned to any role group by default. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md index 49a991694b..1e4c1d0ef6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md @@ -13,7 +13,7 @@ title: New-ManagementRoleAssignment # New-ManagementRoleAssignment ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-ManagementRoleAssignment cmdlet to assign a management role to a management role group, management role assignment policy, user, or universal security group (USG). @@ -118,7 +118,7 @@ You can create custom management scopes using the New-ManagementScope cmdlet and For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -138,7 +138,7 @@ New-ManagementRoleAssignment -Role "MyVoiceMail" -Policy "Sales end-users" This example assigns the MyVoiceMail role to the "Sales end-users" role assignment policy. First, the IsEndUserRole property on the MyVoiceMail role is verified to be sure it's set to $true, indicating it's an end-user role. -After the role has been verified to be an end-user role, the role is assigned to the "Sales end-users" role assignment policy. +After the role is verified to be an end-user role, the role is assigned to the "Sales end-users" role assignment policy. ### Example 3 ```powershell @@ -181,7 +181,7 @@ This example assigns the Mail Recipients role to the Contoso Sub - Seattle role > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The Name parameter specifies a name for the new management role assignment. The maximum length of the name is 64 characters. If the management role assignment name contains spaces, enclose the name in quotation marks ("). If you don't specify a name, one will be created automatically. +The Name parameter specifies a name for the new management role assignment. The maximum length of the name is 64 characters. If the management role assignment name contains spaces, enclose the name in quotation marks ("). If you don't specify a name, a name is created automatically. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md index 61f701edc8..7689690822 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md @@ -13,7 +13,7 @@ title: New-ManagementScope # New-ManagementScope ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-ManagementScope cmdlet to create a regular or exclusive management scope. @@ -82,7 +82,7 @@ After you create a regular or exclusive scope, you need to associate the scope w For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md index 631e4cc9bc..2e66284d4f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md @@ -39,7 +39,7 @@ New-MapiVirtualDirectory ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -104,7 +104,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -124,7 +124,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -145,8 +145,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md index 08169fc9b2..bf7fa10717 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md @@ -13,7 +13,7 @@ title: New-MessageClassification # New-MessageClassification ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MessageClassification cmdlet to create a message classification instance in your organization. @@ -50,7 +50,7 @@ After you create a new message classification, you can specify the message class When you create a message classification, it has no locale. By default, the new message classification is used for all locales. After a default message classification is defined, you can add new locales of the classification by running the New-MessageClassification cmdlet and by specifying the default message classification identity that you want to localize. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -196,19 +196,19 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that may be applied to a specified message. Valid values are: +The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that might be applied to a specified message. Valid values are: - Highest - Higher - High - MediumHigh -- Medium (This is the default value) +- Medium (default value) - MediumLow - Low - Lower - Lowest -Although Outlook only lets a user specify a single classification for a message, transport rules may apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter. +Although Outlook only lets a user specify a single classification for a message, transport rules might apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter. ```yaml Type: ClassificationDisplayPrecedenceLevel @@ -250,7 +250,7 @@ Accept wildcard characters: False The PermissionMenuVisible parameter specifies whether the values that you entered for the DisplayName and RecipientDescription parameters are displayed in Outlook as the user composes a message. Valid values are: -- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This is the default value. +- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This value is the default. - $false: Users can't assign the message classification to messages before they're sent, However, messages received with this message classification still display the classification information. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md index ef66847557..e928c46162 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md @@ -13,7 +13,7 @@ title: New-MigrationBatch # New-MigrationBatch ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MigrationBatch cmdlet to submit a new migration request for a batch of users. @@ -454,12 +454,12 @@ Onboarding and offboarding in Exchange Online Both onboarding and offboarding remote move migrations are initiated from your Exchange Online organization. -- Cutover Exchange migration: This is another type of onboarding migration and is used to migrate all mailboxes in an on-premises Exchange organization to Exchange Online. You can migrate a maximum of 1,000 Exchange Server 2003, Exchange Server 2007, or Exchange Server 2010 mailboxes using a cutover migration. Mailboxes will be automatically provisioned in Exchange Online when you perform a cutover Exchange migration. For more information, see Example 5. +- Cutover Exchange migration: This is another type of onboarding migration and is used to migrate all mailboxes in an on-premises Exchange organization to Exchange Online. You can migrate a maximum of 1,000 Exchange Server 2003, Exchange Server 2007, or Exchange Server 2010 mailboxes using a cutover migration. Mailboxes are automatically provisioned in Exchange Online when you perform a cutover Exchange migration. For more information, see Example 5. - Staged Exchange migration: You can also migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online. This is another type of onboarding migration. Migrating mailboxes from Exchange 2010 or later versions of Exchange isn't supported using a staged migration. Prior to running a staged migration, you have to use directory synchronization or some other method to provision mail users in your Exchange Online organization. For more information, see Example 6. - IMAP migration: This onboarding migration type migrates mailbox data from an IMAP server (including Exchange) to Exchange Online. For an IMAP migration, you must first provision mailboxes in Exchange Online before you can migrate mailbox data. For more information, see Example 7. - Google Workspace (formerly G Suite) migration: This onboarding migration type migrates mailbox data from a Google Workspace organization to Exchange Online. For a Google Workspace migration, you must first provision mail users (or mailboxes) in Exchange Online before you can migrate mailbox data. For more information, see Example 10. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -470,7 +470,7 @@ New-MigrationBatch -Local -Name LocalMove1 -CSVData ([System.IO.File]::ReadAllBy Start-MigrationBatch -Identity LocalMove1 ``` -This example creates a migration batch for a local move, where the mailboxes in the specified CSV file are moved to a different mailbox database. This CSV file contains a single column with the email address for the mailboxes that will be moved. The header for this column must be named EmailAddress. The migration batch in this example must be started manually by using the Start-MigrationBatch cmdlet or the Exchange admin center. Alternatively, you can use the AutoStart parameter to start the migration batch automatically. +This example creates a migration batch for a local move, where the mailboxes in the specified CSV file are moved to a different mailbox database. This CSV file contains a single column with the email address for the mailboxes to be moved. The header for this column must be named EmailAddress. The migration batch in this example must be started manually by using the Start-MigrationBatch cmdlet or the Exchange admin center. Alternatively, you can use the AutoStart parameter to start the migration batch automatically. ### Example 2 ```powershell @@ -483,7 +483,7 @@ $CrossForestBatch = New-MigrationBatch -Name CrossForestBatch1 -SourceEndpoint $ Start-MigrationBatch -Identity $CrossForestBatch.Identity ``` -This example creates a migration batch for a cross-forest enterprise move, where the mailboxes for the mail users specified in the CSV file are moved to a different forest. A new migration endpoint is created, which identifies the domain where the mailboxes are currently located. The endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. Note that cross-forest moves are initiated from the target forest, which is the forest that you want to move the mailboxes to. +This example creates a migration batch for a cross-forest enterprise move, where the mailboxes for the mail users specified in the CSV file are moved to a different forest. A new migration endpoint is created, which identifies the domain where the mailboxes are currently located. The endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. Cross-forest moves are initiated from the target forest, which is the forest that you want to move the mailboxes to. ### Example 3 ```powershell @@ -496,7 +496,7 @@ $OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $M Start-MigrationBatch -Identity $OnboardingBatch.Identity.Name ``` -This example creates a migration batch for an onboarding remote move migration from an on-premises Exchange organization to Exchange Online. The syntax is similar to that of a cross-forest move, but it's initiated from the Exchange Online organization. A new migration endpoint is created, which points to the on-premises organization as the source location of the mailboxes that will be migrated. This endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. +This example creates a migration batch for an onboarding remote move migration from an on-premises Exchange organization to Exchange Online. The syntax is similar to that of a cross-forest move, but it's initiated from the Exchange Online organization. A new migration endpoint is created, which points to the on-premises organization as the source location of the mailboxes to be migrated. This endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. ### Example 4 ```powershell @@ -555,7 +555,7 @@ $OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $M Start-MigrationBatch -Identity $OnboardingBatch.Identity ``` -This example is the same as Example 3, but the CompleteAfter parameter is also used. Data migration for the batch will start, but won't complete until 09/01/2018 7:00 PM (UTC). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Coordinated Universal Time. +This example is the same as Example 3, but the CompleteAfter parameter is also used. Data migration for the batch starts but doesn't complete until 09/01/2018 7:00 PM (UTC). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Coordinated Universal Time. ### Example 9 ```powershell @@ -568,7 +568,7 @@ $OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $M Start-MigrationBatch -Identity $OnboardingBatch.Identity ``` -This example is the same as Example 8, but the TimeZone parameter is also used. Data migration for the batch will start, but won't complete until 09/01/2018 7:00 PM (PST). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Pacific Standard Time. +This example is the same as Example 8, but the TimeZone parameter is also used. Data migration for the batch starts but doesn't complete until 09/01/2018 7:00 PM (PST). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Pacific Standard Time. ### Example 10 ```powershell @@ -699,7 +699,7 @@ The CSVData parameter specifies the CSV file that contains information about the A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). -**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes that are specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes. +**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes. ```yaml Type: Byte[] @@ -785,8 +785,8 @@ This parameter is available only in on-premises Exchange. The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are: -- $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. This is the default value. -- $false: Incremental synchronization is disabled. The migration batch will go into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization by using the Set-MigrationBatch cmdlet. +- $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. This value is the default. +- $false: Incremental synchronization is disabled. The migration batch goes into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization by using the Set-MigrationBatch cmdlet. ```yaml Type: Boolean @@ -807,7 +807,7 @@ Accept wildcard characters: False The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns in the CSV file that aren't used by migration. Valid values are: - $true: The migration ignores (silently skips) unknown columns in the CSV file (including optional columns with misspelled column headers). All unknown columns are treated like extra columns that aren't used by migration. -- $false: The migration fails if there are any unknown columns in the CSV file.This setting protects against spelling errors in column headers. This is the default value. +- $false: The migration fails if there are any unknown columns in the CSV file.This setting protects against spelling errors in column headers. This value is the default. ```yaml Type: Boolean @@ -973,7 +973,7 @@ The BadItemLimit parameter specifies the maximum number of bad items that are al Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if neither the BadItemLimit or LargeItemLimit parameters are specified, the migration will use Skipped Item approval semantics instead of BadItemLimit semantics. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if neither the BadItemLimit or LargeItemLimit parameters are specified, the migration uses Skipped Item approval semantics instead of BadItemLimit semantics. ```yaml Type: Unlimited @@ -993,14 +993,14 @@ Accept wildcard characters: False This parameter is functional only in the cloud-based service. -The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch will start, but completion won't start until the date/time you specify with this parameter. +The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch starts, but completion doesn't start until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. -- Specify the date/time value in your local time zone: For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. +- Specify the date/time value in your local time zone: For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter. ```yaml Type: DateTime @@ -1041,7 +1041,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service for IMAP migration and Google Workspace migration. -The ContentFilter parameter uses OPATH filter syntax to filter the messages by Received time. Only content that match the ContentFilter parameter will be moved to Exchange online. For example: +The ContentFilter parameter uses OPATH filter syntax to filter the messages by Received time. Only content that matches the ContentFilter parameter is moved to Exchange online. For example: - `"Received -gt '8/23/2020'"` - `"Received -le '2019/01/01'"` @@ -1350,7 +1350,7 @@ For more information about maximum message size values, see the following topics Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -1732,7 +1732,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been replaced by the MoveOptions parameter. +This parameter is replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -1814,7 +1814,7 @@ This parameter is available only in on-premises Exchange. The SkipSteps parameter specifies the steps in the staged Exchange migration that you want to skip. Valid values are: -- None (This is the default value) +- None (default value) - SettingTargetAddress: Don't set the target email address on the source mailbox. This setting prevents mail from being forwarded from the original mailbox to the new migrated mailbox. This parameter is only enforced for staged Exchange migrations. @@ -1878,14 +1878,14 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration will be prepared, but the actual data migration for the user won't start until the date/time you specify with this parameter. +The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration is prepared, but the actual data migration for the user doesn't start until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. -- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. +- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter. ```yaml Type: DateTime @@ -1903,7 +1903,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch will be migrated to. You can use any value that uniquely identifies the database. For example: +The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch are migrated to. You can use any value that uniquely identifies the database. For example: - Name - Distinguished name (DN) @@ -2052,7 +2052,7 @@ Accept wildcard characters: False The WorkflowControlFlags parameter specifies advanced controls for the steps that are performed in the migration. Valid values are: -- None (This is the default value) +- None (default value) - InjectAndForget - SkipSwitchover diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md index b70b95edb7..137f345d59 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md @@ -13,7 +13,7 @@ title: New-MigrationEndpoint # New-MigrationEndpoint ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MigrationEndpoint cmdlet to configure the connection settings for cross-forests moves, remote move migrations, cutover or staged Exchange migrations, IMAP migrations, and Google Workspace (formerly G Suite) migrations. @@ -245,7 +245,7 @@ The New-MigrationEndpoint cmdlet configures the connection settings for differen Moving mailboxes between different servers or databases within a single on-premises Exchange forest (called a local move) doesn't require a migration endpoint. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -270,23 +270,23 @@ $Credentials = Get-Credential New-MigrationEndpoint -ExchangeOutlookAnywhere -Name EXCH-AutoDiscover -Autodiscover -EmailAddress administrator@contoso.com -Credentials $Credentials ``` -This example creates an Outlook Anywhere migration endpoint by using the Autodiscover parameter to detect the connection settings to the on-premises organization. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The Get-Credential cmdlet is used to obtain the credentials for an on-premises account that has the necessary administrative privileges in the domain and that can access the mailboxes that will be migrated. When prompted for the user name, you can use either the email address or the domain\\username format for the administrator account. This account can be the same one that is specified by the EmailAddress parameter. +This example creates an Outlook Anywhere migration endpoint by using the Autodiscover parameter to detect the connection settings to the on-premises organization. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The Get-Credential cmdlet is used to obtain the credentials for an on-premises account that has the necessary administrative privileges in the domain and that can access the migrated mailboxes. When prompted for the user name, you can use either the email address or the domain\\username format for the administrator account. This account can be the same one that is specified by the EmailAddress parameter. ### Example 4 ```powershell New-MigrationEndpoint -ExchangeOutlookAnywhere -Name EXCH_Manual -ExchangeServer EXCH-01-MBX.contoso.com -RPCProxyServer EXCH-02-CAS.contoso.com -Credentials (Get-Credential administrator@contoso.com) -EmailAddress annb@contoso.com ``` -This example creates an Outlook Anywhere migration endpoint by specifying the connection settings manually. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The value for the ExchangeServer parameter specifies the on-premises Exchange server that hosts the mailboxes that will be migrated. The value for the RPCProxyServer parameter specifies the Exchange server in the on-premises organization that has the Client Access server role installed that directly accepts and proxies client connections. The EmailAddress parameter can specify any mailbox in the on-premises domain. +This example creates an Outlook Anywhere migration endpoint by specifying the connection settings manually. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The value for the ExchangeServer parameter specifies the on-premises Exchange server that hosts the migrated mailboxes. The value for the RPCProxyServer parameter specifies the Exchange server in the on-premises organization that has the Client Access server role installed that directly accepts and proxies client connections. The EmailAddress parameter can specify any mailbox in the on-premises domain. -It's recommended that you use a migration endpoint created with connection settings that are automatically discovered (see Example 3) because the Autodiscover service will be used to connect to each user mailbox in the migration batch. If you manually specify the connection settings for the endpoint and a user mailbox isn't located on the server specified by the ExchangeServer parameter, the migration for that user will fail. This is important if you have multiple on-premises Outlook Anywhere servers. Otherwise, you may need to create different migration endpoints that correspond to each on-premises server. +We recommend that you use a migration endpoint created with connection settings that are automatically discovered (see Example 3) because the Autodiscover service is used to connect to each user mailbox in the migration batch. If you manually specify the connection settings for the endpoint and a user mailbox isn't located on the server specified by the ExchangeServer parameter, the migration for that user will fail. This is important if you have multiple on-premises Outlook Anywhere servers. Otherwise, you might need to create different migration endpoints that correspond to each on-premises server. ### Example 5 ```powershell New-MigrationEndpoint -IMAP -Name IMAPEndpoint -RemoteServer imap.contoso.com -Port 993 -Security Ssl ``` -This example creates an IMAP migration endpoint. The value for the RemoteServer parameter specifies the FQDN of the IMAP server that hosts the mailboxes that will be migrated. The endpoint is configured to use port 993 for SSL encryption. +This example creates an IMAP migration endpoint. The value for the RemoteServer parameter specifies the FQDN of the IMAP server that hosts the migrated mailboxes. The endpoint is configured to use port 993 for SSL encryption. ### Example 6 ```powershell @@ -592,7 +592,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The RpcProxyServer parameter specifies the FQDN of the Exchange server in the on-premises Exchange organization that has the Client Access server role installed that directly accepts and proxies client connections. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. Typically, this FQDN will be the same as your Outlook on the web URL; for example, mail.contoso.com. This is also the URL for the proxy server that Outlook uses to connect to an Exchange server. +The RpcProxyServer parameter specifies the FQDN of the Exchange server in the on-premises Exchange organization that has the Client Access server role installed that directly accepts and proxies client connections. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. Typically, this FQDN wis the same as your Outlook on the web URL. For example, mail.contoso.com. This is also the URL for the proxy server that Outlook uses to connect to an Exchange server. This parameter is required only when you don't use the Autodiscover parameter. @@ -614,7 +614,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that has been granted access to your remote tenant is created. +The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that is granted access to your remote tenant is created. A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). @@ -777,7 +777,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The ExchangeServer parameter specifies the FQDN of the on-premises Exchange server that hosts the mailboxes that will be migrated. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. +The ExchangeServer parameter specifies the FQDN of the on-premises Exchange server that hosts the migrated mailboxes. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. This parameter is required only when you don't use the Autodiscover parameter. @@ -804,7 +804,7 @@ The MailboxPermission parameter specifies what permissions to use to access the The migration administrator account specified for the endpoint must have one of the following permissions: - Admin: The account is a domain administrator who can access any mailbox they want to migrate. -- FullAccess: The account is assigned either the Full Access permission to the mailboxes they want to migrate or the Receive As permission to the mailbox database that hosts the mailboxes that will be migrated. +- FullAccess: The account is assigned either the Full Access permission to the mailboxes they want to migrate or the Receive As permission to the mailbox database that hosts the migrated mailboxes. If this parameter isn't specified, the cmdlet tries to access source mailboxes using the domain administrator permission and if that fails, it then tries to access the source mailboxes using the Full Access or Receive As permissions. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md index 38821c4cb2..8d609417e7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md @@ -13,7 +13,7 @@ title: New-MobileDeviceMailboxPolicy # New-MobileDeviceMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MobileDeviceMailboxPolicy cmdlet to create mobile device mailbox policies. @@ -90,7 +90,7 @@ Some mobile device mailbox policy settings require the mobile device to have cer Some settings in this cmdlet are supported by Outlook for iOS and Android. For more information, see [Leveraging Exchange Online mobile device policies](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/secure-outlook-for-ios-and-android#leveraging-exchange-online-mobile-device-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -900,7 +900,7 @@ Accept wildcard characters: False The MaxInactivityTimeLock parameter specifies the length of time that the mobile device can be inactive before the password is required to reactivate it. Valid values are: - A timespan: hh:mm:ss, where hh = hours, mm = minutes and ss= seconds. The valid input range is 00:01:00 to 01:00:00 (one minute to one hour). -- The value Unlimited. This is the default value. +- The value Unlimited. This value is the default. ```yaml Type: Unlimited @@ -1017,7 +1017,7 @@ Accept wildcard characters: False The PasswordExpiration parameter specifies how long a password can be used on a mobile device before the user is forced to change the password. Valid values are: - A timespan: ddd.hh:mm:ss, where ddd = days, hh = hours, mm = minutes and ss= seconds. The valid input range is 1.00:00:00 to 730.00:00:00 (one day to two years). -- The value Unlimited. This is the default value +- The value Unlimited. This value is the default ```yaml Type: Unlimited diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md index 315eb64fbe..f6067d134f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md @@ -13,7 +13,7 @@ title: New-MoveRequest # New-MoveRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-MoveRequest cmdlet to begin the process of an asynchronous mailbox or personal archive move. You can also check mailbox readiness to be moved by using the WhatIf parameter. @@ -256,7 +256,7 @@ New-MoveRequest [-Identity] -TargetDeliveryDomain ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -561,7 +561,7 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -624,7 +624,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. +The CompletedRequestAgeLimit parameter specifies how long the request are kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. ```yaml Type: Unlimited @@ -707,7 +707,7 @@ Accept wildcard characters: False The ForceOffline switch forces the mailbox move to be performed in offline mode. You don't need to specify a value with this switch. -Moving a mailbox in offline mode means the user will have no access to email during the mailbox move. +Moving a mailbox in offline mode means the user has no access to email during the mailbox move. ```yaml Type: SwitchParameter @@ -789,7 +789,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. This parameter is used together with the CompleteAfter parameter to create a move request that will do periodic incremental syncs after the initial sync is complete. +The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. Use this parameter with the CompleteAfter parameter to create a move request that does periodic incremental syncs after the initial sync is complete. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -842,7 +842,7 @@ Valid input for this parameter is an integer or the value unlimited. The default If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -949,7 +949,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest @@ -1105,7 +1105,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been replaced by the MoveOptions parameter. +This parameter is replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -1174,7 +1174,7 @@ Accept wildcard characters: False The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. -If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. +If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet. ```yaml Type: SwitchParameter @@ -1238,7 +1238,7 @@ The TargetDatabase parameter specifies the destination mailbox database for the - Distinguished name (DN) - GUID -If you don't use this parameter, the automatic distribution logic will select a random database in the Active Directory site where you are running the command. +If you don't use this parameter, the automatic distribution logic selects a random database in the Active Directory site where you are running the command. ```yaml Type: DatabaseIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md index 42c85225eb..1453b4cf91 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md @@ -40,7 +40,7 @@ New-OMEConfiguration [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,7 +79,7 @@ The BackgroundColor parameter specifies the background color. Valid values are: - An available HTML hexadecimal (hex triplet) color code value (for example, `0x000000` is white). - An available text value (for example, `yellow` is 0x00FFFF00). -- $null (blank). This is the default value. +- $null (blank). This value is the default. For more information, see [Add your organization's brand to your encrypted messages](https://learn.microsoft.com/purview/add-your-organization-brand-to-encrypted-messages). @@ -155,7 +155,7 @@ Accept wildcard characters: False This parameter is available only with a Microsoft 365 Advanced Message Encryption subscription. -The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages will never expire. The default value is 0. +The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages never expire. The default value is 0. In the output of the Get-OMEConfiguration cmdlet, the value of this parameter is displayed in the ExternalMailExpiryInterval property. @@ -175,7 +175,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The Image parameter identifies and uploads an image that will be displayed in the email message and in the Microsoft 365 admin center. +The Image parameter identifies and uploads an image that's displayed in the email message and in the Microsoft 365 admin center. A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). @@ -219,7 +219,7 @@ Accept wildcard characters: False The OTPEnabled parameter specifies whether to allow recipients to use a one-time passcode to view encrypted messages. Valid values are: -- $true: Recipients can use a one-time passcode to view encrypted messages. This is the default value. +- $true: Recipients can use a one-time passcode to view encrypted messages. This value is the default. - $false: Recipients can't use a one-time passcode to view encrypted messages. The recipient is required to sign in using a Microsoft 365 work or school account. ```yaml @@ -294,7 +294,7 @@ Accept wildcard characters: False The SocialIdSignIn parameter specifies whether a user is allowed to view an encrypted message in the Microsoft 365 admin center using their own social network id (Google, Yahoo, etc). Valid values are: -- $true: Social network ID sign in is allowed. This is the default value. +- $true: Social network ID sign in is allowed. This value is the default. - $false: Social network ID sign in is not allowed. Whether the recipient can use a one-time passcode or their Microsoft 365 work or school account is controlled by the OTPEnabled parameter. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md index 6b565f5cfd..e521394787 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md @@ -45,7 +45,7 @@ The New-OABVirtualDirectory cmdlet configures a web distribution point for an OA You have to manually create the file system folder on the server that hosts the OAB files. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -107,7 +107,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -127,7 +127,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -148,9 +148,9 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. -- Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. +- Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection fails. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -262,7 +262,7 @@ Accept wildcard characters: False The RequireSSL parameter specifies whether the client connection to the virtual directory requires Secure Sockets Layer (SSL) encryption. Valid values are: -- $true: SSL encryption is required to connect to the virtual directory. This is the default value. +- $true: SSL encryption is required to connect to the virtual directory. This value is the default. - $false: SSL encryption isn't required to connect to the virtual directory. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md index d0e3db120c..02ba871661 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md @@ -13,7 +13,7 @@ title: New-OfflineAddressBook # New-OfflineAddressBook ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-OfflineAddressBook cmdlet to create offline address books (OABs). @@ -44,7 +44,7 @@ New-OfflineAddressBook [-Name] -AddressLists -HybridDomains ``` ## DESCRIPTION -The OnPremisesOrganization object represents an on-premises Microsoft Exchange organization configured for hybrid deployment with a Microsoft 365 organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. Manual modification of this object may result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization. +The OnPremisesOrganization object represents an on-premises Microsoft Exchange organization configured for hybrid deployment with a Microsoft 365 organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. Manual modification of this object might result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,7 +69,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains may be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com". +The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains might be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com". ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md index 770257916d..976f4da310 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md @@ -13,7 +13,7 @@ title: New-OrganizationRelationship # New-OrganizationRelationship ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-OrganizationRelationship cmdlet to create organization relationships. Organization relationships define the settings that are used with external Exchange organizations to access calendar free/busy information or to move mailboxes between on-premises Exchange servers and Exchange Online as part of hybrid deployments. @@ -51,7 +51,7 @@ New-OrganizationRelationship [-Name] -DomainNames ## DESCRIPTION Before you can create an organization relationship, you must first create a federation trust. For more information, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -131,10 +131,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The ArchiveAccessEnabled parameter specifies whether the organization relationship has been configured to provide remote archive access. Valid values are: +The ArchiveAccessEnabled parameter specifies whether the organization relationship is configured to provide remote archive access. Valid values are: - $true: The external organization provides remote access to mailbox archives. -- $false: The external organization doesn't provide remote access to mailbox archives. This is the default value. +- $false: The external organization doesn't provide remote access to mailbox archives. This value is the default. ```yaml Type: Boolean @@ -176,9 +176,9 @@ Accept wildcard characters: False The DeliveryReportEnabled parameter specifies whether Delivery Reports should be shared over the organization relationship. Valid values are: - $true: Delivery Reports should be shared over the organization relationship. This value means the organization has agreed to share all Delivery Reports with the external organization, and the organization relationship should be used to retrieve Delivery Report information from the external organization. -- $false: Delivery Reports shouldn't be shared over the organization relationship. This is the default value +- $false: Delivery Reports shouldn't be shared over the organization relationship. This value is the default -For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations won't work in either direction. +For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations doesn't work in either direction. ```yaml Type: Boolean @@ -218,7 +218,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable the organization relationship. Valid values are: -- $true: The organization relationship is enabled. This is the default value. +- $true: The organization relationship is enabled. This value is the default. - $false: The organization relationship is disabled. This value completely stops sharing for the organization relationship. ```yaml @@ -240,7 +240,7 @@ Accept wildcard characters: False The FreeBusyAccessEnabled parameter specifies whether the organization relationship should be used to retrieve free/busy information from the external organization. Valid values are: - $true: Free/busy information is retrieved from the external organization. -- $false: Free/busy information isn't retrieved from the external organization. This is the default value. +- $false: Free/busy information isn't retrieved from the external organization. This value is the default. You control the free/busy access level and scope by using the FreeBusyAccessLevel and FreeBusyAccessScope parameters. @@ -284,7 +284,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The FreeBusyAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. You can use any value that uniquely identifies the group. For example: +The FreeBusyAccessScope parameter specifies an internal mail-enabled security group where member free/busy information is accessible by the external organization. For best performance, the group should have less than 10,000 members. You can use any value that uniquely identifies the group. For example: - Name - Distinguished name (DN) @@ -339,7 +339,7 @@ Accept wildcard characters: False The MailboxMoveEnabled parameter specifies whether the organization relationship enables moving mailboxes to or from the external organization. Valid values are: - $true: Mailbox moves to or from the external organization are allowed. -- $false: Mailbox moves to or from the external organization aren't allowed. This is the default value. +- $false: Mailbox moves to or from the external organization aren't allowed. This value is the default. ```yaml Type: Boolean @@ -389,7 +389,7 @@ Accept wildcard characters: False The MailTipsAccessEnabled parameter specifies whether MailTips for users in this organization are returned over this organization relationship. Valid values are: - $true: MailTips for users in this organization are returned over the organization relationship. -- $false: MailTips for users in this organization aren't returned over the organization relationship. This is the default value. +- $false: MailTips for users in this organization aren't returned over the organization relationship. This value is the default. You control the MailTips access level by using the MailTipsAccessLevel parameter. @@ -412,8 +412,8 @@ Accept wildcard characters: False The MailTipsAccessLevel parameter specifies the level of MailTips data that's externally shared over this organization relationship. This parameter can have the following values: - All: All MailTips are returned, but the recipients in the remote organization are considered external. For the Auto Reply MailTip, the external Auto Reply message is returned. -- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips won't be returned. -- None: No MailTips are returned to the remote organization. This is the default value. +- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips aren't returned. +- None: No MailTips are returned to the remote organization. This value is the default. This parameter is only meaningful when the MailTipsAccessEnabled parameter value is $true. @@ -509,7 +509,7 @@ Accept wildcard characters: False The PhotosEnabled parameter specifies whether photos for users in the internal organization are returned over the organization relationship. Valid values are: - $true: Photos for users in this organization are returned over the organization relationship. -- $false: Photos for users in this organization aren't returned over the organization relationship. This is the default value. +- $false: Photos for users in this organization aren't returned over the organization relationship. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md index 69dd558e8e..539c5c9b79 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md @@ -47,7 +47,7 @@ New-OutboundConnector [-Name] ## DESCRIPTION Outbound connectors send email messages to remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -88,7 +88,7 @@ Accept wildcard characters: False The AllAcceptedDomains parameter specifies whether the Outbound connector is used in hybrid organizations where message recipients are in accepted domains of the cloud-based organization. Valid values are: - $true: The Outbound connector is used in hybrid organizations when message recipients are in an accepted domain of the cloud-based organization. This setting requires OnPremises for the ConnectorType value. -- $false: The Outbound connector isn't used in hybrid organizations. This is the default value. +- $false: The Outbound connector isn't used in hybrid organizations. This value is the default. This parameter is effective only for OnPremises connectors. @@ -114,7 +114,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f Valid values are: -- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. +- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. ```yaml @@ -174,7 +174,7 @@ Accept wildcard characters: False The ConnectorSource parameter specifies how the connector is created. Valid values are: -- Default: The connector is manually created. This is the default value when you use this cmdlet, and we recommend that you don't change this value. +- Default: The connector is manually created. This value is the default when you use this cmdlet, and we recommend that you don't change this value. - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. @@ -217,7 +217,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable or disable the Outbound connector. Valid values are: -- $true: The connector is enabled. This is the default value. +- $true: The connector is enabled. This value is the default. - $false: The connector is disabled. ```yaml @@ -239,7 +239,7 @@ Accept wildcard characters: False The IsTransportRuleScoped parameter specifies whether the Outbound connector is associated with a transport rule (also known as a mail flow rule). Valid values are: - $true: The connector is associated with a transport rule. -- $false: The connector isn't associated with a transport rule. This is the default value. +- $false: The connector isn't associated with a transport rule. This value is the default. You scope a transport rule to an Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. Messages that match the conditions of the transport rule are routed to their destinations by using the specified Outbound connector. @@ -300,7 +300,7 @@ Accept wildcard characters: False The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises email system in hybrid organizations. Valid values are: - $true: Messages are routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. -- $false: Messages aren't routed through the on-premises email system. This is the default value. +- $false: Messages aren't routed through the on-premises email system. This value is the default. This parameter is effective only for OnPremises connectors. @@ -323,7 +323,7 @@ Accept wildcard characters: False The SenderRewritingEnabled parameter specifies that all messages that normally qualify for SRS rewriting are rewritten for routing through the on-premises email system. Valid values are: - $true: Messages are rewritten by SRS as needed before being routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. -- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This is the default value. +- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This value is the default. This parameter is effective only for OnPremises connectors. @@ -372,7 +372,7 @@ Accept wildcard characters: False The TestMode parameter specifies whether you want to enabled or disable test mode for the Outbound connector. Valid values are: - $true: Test mode is enabled. -- $false: Test mode is disabled. This is the default value. +- $false: Test mode is disabled. This value is the default. ```yaml Type: Boolean @@ -417,7 +417,7 @@ The TlsSettings parameter specifies the TLS authentication level that's used for - EncryptionOnly: TLS is used only to encrypt the communication channel. No certificate authentication is performed. - CertificateValidation: TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed. - DomainValidation: In addition to channel encryption and certificate validation, the Outbound connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter. -- $null (blank): This is the default value. +- $null (blank): This value is the default. ```yaml Type: TlsAuthLevel @@ -437,7 +437,7 @@ Accept wildcard characters: False The UseMXRecord parameter enables or disables DNS routing for the connector. Valid values are: -- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This is the default value. +- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This value is the default. - $false: The connector delivers email to one or more smart hosts. This setting requires one or more smart hosts for the SmartHosts value. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md index 264a04ed65..05485cdd9b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md @@ -15,7 +15,7 @@ title: New-OutlookProtectionRule ## SYNOPSIS **Note**: This cmdlet is no longer supported in the cloud-based service. -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-OutlookProtectionRule cmdlet to create a Microsoft Outlook protection rule. @@ -45,7 +45,7 @@ For more information, see [Outlook protection rules](https://learn.microsoft.com Outlook protection rules created without a condition apply to all messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md index af0e3feeb6..9e7a811556 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md @@ -32,7 +32,7 @@ New-OutlookProvider [-Name] ## DESCRIPTION The New-OutlookProvider cmdlet creates the AutoDiscoverConfig object under the Global Settings object in Active Directory and sets the attributes specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md index 0ea3a13dbb..c0311a932d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md @@ -13,7 +13,7 @@ title: New-OwaMailboxPolicy # New-OwaMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-OwaMailboxPolicy cmdlet to create Outlook on the web mailbox policies. @@ -33,9 +33,9 @@ New-OwaMailboxPolicy [-Name] ## DESCRIPTION Use the Set-OwaMailboxPolicy cmdlet to configure the new policy. -Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). +Changes to Outlook on the web mailbox policies might take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md index 291b08b57f..e051fb1584 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md @@ -45,7 +45,7 @@ New-OwaVirtualDirectory ## DESCRIPTION By default, when Exchange is installed, the Outlook on the web virtual directory owa is created in the default IIS website on the server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -163,7 +163,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -183,7 +183,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -204,8 +204,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication works, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md index f78ea97f86..af5db2924b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md @@ -60,7 +60,7 @@ You can configure partner applications such as Microsoft SharePoint to access Ex We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -153,7 +153,7 @@ Accept wildcard characters: False The AccountType parameter specifies the type of Microsoft account that's required for the partner application. Valid values are: -- OrganizationalAccount (This is the default value) +- OrganizationalAccount (default value) - ConsumerAccount ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md index 3edf56b20a..fda8e38416 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md @@ -33,7 +33,7 @@ New-PhishSimOverridePolicy [-Name] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,7 +50,7 @@ This example creates the phishing simulation override policy named PhishSimOverr > Applicable: Exchange Online -The Name parameter specifies the name for the phishing simulation override policy. Regardless of the value you specify, the name will be PhishSimOverridePolicy. +The Name parameter specifies the name for the phishing simulation override policy. Regardless of the value you specify, the name is PhishSimOverridePolicy. ```yaml Type: String @@ -127,7 +127,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md index bb9efbeb94..0eb6102ca0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md @@ -13,7 +13,7 @@ title: New-PolicyTipConfig # New-PolicyTipConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-PolicyTipConfig cmdlet to create custom Policy Tips in your organization. @@ -30,7 +30,7 @@ New-PolicyTipConfig [-Name] -Value ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md index 6314ea56c9..b79b93eb6b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md @@ -42,7 +42,7 @@ New-PowerShellVirtualDirectory [-Name] ## DESCRIPTION Although it's possible to create a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -59,7 +59,7 @@ This example creates a Windows PowerShell virtual directory and configures it to > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Name parameter specifies the name of the new PowerShell virtual directory. The name you provide will have the name of the website it's created under appended to it. If the name you provide contains spaces, enclose the name in quotation marks ("). +The Name parameter specifies the name of the new PowerShell virtual directory. The name you provide has the name of the website it's created under appended to it. If the name you provide contains spaces, enclose the name in quotation marks ("). ```yaml Type: String @@ -140,7 +140,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -160,7 +160,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -181,8 +181,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md b/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md index 1174020b1c..f52a7470fb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md @@ -174,8 +174,8 @@ Accept wildcard characters: False The AggregationType parameter specifies the how the alert policy triggers alerts for multiple occurrences of monitored activity. Valid values are: - None: Alerts are triggered for every occurrence of the activity. -- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This is the default value. -- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). Note that it can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. +- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This value is the default. +- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). It can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. ```yaml Type: AlertAggregationType @@ -332,7 +332,7 @@ Accept wildcard characters: False The Disabled parameter enables or disables the alert policy. Valid values are: - $true: The alert policy is disabled. -- $false: The alert policy is enabled. This is the default value. +- $false: The alert policy is enabled. This value is the default. ```yaml Type: Boolean @@ -479,7 +479,7 @@ Accept wildcard characters: False The NotifyUserOnFilterMatch parameter specifies whether to trigger an alert for a single event when the alert policy is configured for aggregated activity. Valid values are: - $true: Even though the alert is configured for aggregated activity, a notification is triggered during a match for the activity (basically, an early warning). -- $false: Alerts are triggered according to the specified aggregation type. This is the default value. +- $false: Alerts are triggered according to the specified aggregation type. This value is the default. You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). @@ -519,10 +519,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications has been reached in the time period, no more notifications are sent for the alert. Valid values are: +The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications is reached in the time period, no more notifications are sent for the alert. Valid values are: - An integer. -- The value $null. This is the default value (no maximum number of notifications for an alert). +- The value $null. This value is the default (no maximum number of notifications for an alert). ```yaml Type: Int32 @@ -543,7 +543,7 @@ Accept wildcard characters: False The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are: - An integer. -- The value $null. This is the default value (no interval for notification throttling). +- The value $null. This value is the default (no interval for notification throttling). ```yaml Type: Int32 @@ -639,7 +639,7 @@ Accept wildcard characters: False The Severity parameter specifies the severity of the detection. Valid values are: -- Low (This is the default value) +- Low (default value) - Medium - High diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md index 8f7f1f561f..77226a0eca 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md @@ -13,7 +13,7 @@ title: New-PublicFolder # New-PublicFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-PublicFolder cmdlet to create a public folder with the specified name. @@ -34,7 +34,7 @@ New-PublicFolder [-Name] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md index 4b6ccdc335..a22d12b805 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md @@ -34,7 +34,7 @@ New-PublicFolderDatabase [-Name] -Server ## DESCRIPTION The new database must be mounted after it's created. For more information about mounting databases, see [Mount a Database](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123587(v=exchg.141)). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md index 231d0ed6c1..b7047a7953 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md @@ -35,7 +35,7 @@ Public folders on the public folder database can still be accessed while the req After you begin the repair request, it can't be stopped unless you dismount the database. For more information, see [Dismount a Database](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123903(v=exchg.141)). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md index 6cc054734f..e096e2cdf4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md @@ -50,7 +50,7 @@ New-PublicFolderMigrationRequest [[-Name] ] -SourceDatabase -TargetMailbox ``` ## DESCRIPTION -The New-PublicFolderMoveRequest cmdlet moves public folders from a source public folder mailbox to a target public folder mailbox. While the move request is active, the target public folder mailbox will be locked. As a result, public folders already residing in the target public folder mailbox will be inaccessible until the move request is complete. Therefore, before you begin the move request, you should ensure that no users are accessing public folder data in that target public folder mailbox. +The New-PublicFolderMoveRequest cmdlet moves public folders from a source public folder mailbox to a target public folder mailbox. While the move request is active, the target public folder mailbox is locked. As a result, public folders already residing in the target public folder mailbox are inaccessible until the move request is complete. Therefore, before you begin the move request, you should ensure that no users are accessing public folder data in that target public folder mailbox. To move the public folder mailbox to another mailbox database, use the New-MoveRequest cmdlet. To ensure that this folder is already in the target public folder mailbox, run the Update-PublicFolderMailbox cmdlet against the target public folder mailbox. You can only perform one move request at a time. You can also move public folders by using the Move-PublicFolderBranch.ps1 script. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -84,7 +84,7 @@ This example moves all public folders from public folder mailbox Pub1 to public > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The Folders parameter specifies the public folders that you want to move. If the public folder has child public folders, these child public folders won't be moved unless you explicitly state them in the command. You can move multiple public folders by separating them with a comma, for example, \\Dev\\CustomerEngagements,\\Dev\\RequestsforChange,\\Dev\\Usability. +The Folders parameter specifies the public folders that you want to move. If the public folder has child public folders, these child public folders aren't moved unless you explicitly state them in the command. You can move multiple public folders by separating them with a comma, for example, \\Dev\\CustomerEngagements,\\Dev\\RequestsforChange,\\Dev\\Usability. ```yaml Type: PublicFolderIdParameter[] @@ -191,7 +191,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has been completed before being automatically removed. The default value for this parameter is 30 days. +The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before being automatically removed. The default value for this parameter is 30 days. ```yaml Type: Unlimited @@ -311,7 +311,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest @@ -360,7 +360,7 @@ Accept wildcard characters: False The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. -If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. +If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md index a5f3e8220a..07e69cfb7f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md @@ -39,7 +39,7 @@ New-QuarantinePermissions ## DESCRIPTION The default value for any parameters that you don't use is $false, so you only need to use parameters (permissions) that you want to set to $true. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,7 +79,7 @@ In the same PowerShell session, you can use `$FullAccess` for the _EndUserQuaran The PermissionToAllowSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are: - $true: Allow sender is available for affected messages in quarantine. -- $false: Allow sender isn't available for affected messages in quarantine. This is the default value. +- $false: Allow sender isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -100,7 +100,7 @@ Accept wildcard characters: False The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are: - $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine. -- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This is the default value. +- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -121,7 +121,7 @@ Accept wildcard characters: False The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are: - $true: Delete messages and Delete from quarantine are available for affected messages in quarantine. -- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value. +- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -142,7 +142,7 @@ Accept wildcard characters: False The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are: - $true: The permission is enabled. -- $false: The permission is disabled. This is the default value. +- $false: The permission is disabled. This value is the default. Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. End-users can't download quarantined messages. @@ -165,7 +165,7 @@ Accept wildcard characters: False The PermissionToPreview parameter specifies whether users are allowed to preview quarantined messages. Valid values are: - $true: Preview message is available for affected messages in quarantine. -- $false: Preview message isn't available for affected messages in quarantine. This is the default value. +- $false: Preview message isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -232,7 +232,7 @@ Accept wildcard characters: False The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are: - $true: The permission is enabled. -- $false: The permission is disabled. This is the default value. +- $false: The permission is disabled. This value is the default. Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. View message header is always available for affected messages in quarantine. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md index 8a7e07202b..6cfaa0b09b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md @@ -51,7 +51,7 @@ New-QuarantinePolicy [-Name] ## DESCRIPTION Quarantine policies define what users are allowed to do to quarantined messages based on why the message was quarantined (for supported features) and quarantine notification settings. For more information, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -382,7 +382,7 @@ Accept wildcard characters: False The ESNEnabled parameter specifies whether to enable quarantine notifications (formerly known as end-user spam notifications) for the policy. Valid values are: - $true: Quarantine notifications are enabled. -- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This is the default value. +- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This value is the default. **Note**: If the value of this parameter is $true and the value of the EndUserQuarantinePermissionsValue parameter is 0 (No access where all permissions are turned off), users can see their messages in quarantine, but the only available action for the messages is **View message header**. @@ -405,7 +405,7 @@ Accept wildcard characters: False The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send quarantine notifications for quarantined messages from blocked sender addresses. Valid values are: - $true: Recipients get quarantine notifications for affected messages from blocked senders. -- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This is the default value. +- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md index 72b383e6a6..99f534f8f4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md @@ -384,7 +384,7 @@ On Mailbox servers, you can create Receive connectors in the Front End Transport For more information about Receive connector usage types, permission groups, and authentication methods, see [Receive connectors](https://learn.microsoft.com/Exchange/mail-flow/connectors/receive-connectors). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -652,7 +652,7 @@ Accept wildcard characters: False The AdvertiseClientSettings parameter specifies whether the SMTP server name, port number, and authentication settings for the Receive connector are displayed to users in the options of Outlook on the web. Valid values are: - $true: The SMTP values are displayed in Outlook on the web. Typically, you would only use this setting for a Receive connector with the usage type Client (authenticated SMTP connections on TCP port 587 for POP3 and IMAP4 clients). -- $false: The SMTP values are displayed in Outlook on the web. This is the default value. +- $false: The SMTP values are displayed in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -704,7 +704,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019 -The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that may be abusing the connection. The default value is 5 seconds. +The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that might be abusing the connection. The default value is 5 seconds. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -752,7 +752,7 @@ Accept wildcard characters: False The BinaryMimeEnabled parameter specifies whether the BINARYMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This is the default value. +- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This value is the default. - $false: BINARYMIME is disabled and isn't advertised in the EHLO response. The binary MIME extension is defined in RFC 3030. @@ -775,7 +775,7 @@ Accept wildcard characters: False The ChunkingEnabled parameter specifies whether the CHUNKING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: CHUNKING is enabled and is advertised in the EHLO response. This is the default value. +- $true: CHUNKING is enabled and is advertised in the EHLO response. This value is the default. - $false: CHUNKING is disabled and isn't advertised in the EHLO response. Chunking is defined in RFC 3030. @@ -896,7 +896,7 @@ This usage type assigns the following default permission groups and authenticati When you use this switch, you also need to use the Bindings and RemoteIPRanges parameters. -If you don't also use the PermissionGroups parameter to assign at least one permission group, you'll need to use the PermissionGroups parameter on the Set-ReceiveConnector cmdlet after you create the Receive connector (otherwise, the Receive connector can't accept inbound SMTP connections). +If you don't also use the PermissionGroups parameter to assign at least one permission group, you need to use the PermissionGroups parameter on the Set-ReceiveConnector cmdlet after you create the Receive connector (otherwise, the Receive connector can't accept inbound SMTP connections). You can't use this switch with any other usage type parameters (Client, Internal, Internet, Partner, or Usage). @@ -946,7 +946,7 @@ Accept wildcard characters: False The DeliveryStatusNotificationEnabled parameter specifies whether the DSN (delivery status notification) Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: DSN is enabled and is advertised in the EHLO response. This is the default value. +- $true: DSN is enabled and is advertised in the EHLO response. This value is the default. - $false: DSN is disabled and isn't advertised in the EHLO response. Delivery status notifications are defined in RFC 3461. @@ -992,7 +992,7 @@ The DomainSecureEnabled parameter specifies whether to enable or disable mutual - $true: Mutual TLS authentication is enabled. - $false: Mutual TLS authentication is disabled. -Note that setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication: +Setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication: - The AuthMechanism parameter must contain the value Tls, and can't contain the value ExternalAuthoritative. - The domain that's used for mutual TLS authentication must be configured in the following locations: @@ -1018,7 +1018,7 @@ Accept wildcard characters: False The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: 8BITMIME is enabled and is advertised in the EHLO response. This is the default value. +- $true: 8BITMIME is enabled and is advertised in the EHLO response. This value is the default. - $false: 8BITMIME is disabled and isn't advertised in the EHLO response. 8-bit data transmission is defined in RFC 6152. @@ -1064,7 +1064,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable or disable the Receive connector. Valid values are: -- $true: The Receive connector is enabled. This is the default value. +- $true: The Receive connector is enabled. This value is the default. - $false: The Receive connector is disabled. ```yaml @@ -1085,7 +1085,7 @@ Accept wildcard characters: False The EnhancedStatusCodesEnabled parameter specifies whether the ENHANCEDSTATUSCODES Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This is the default value. +- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This value is the default. - $false: ENHANCEDSTATUSCODES is disabled and isn't advertised in the EHLO response. Enhanced status codes are defined in RFC 2034. @@ -1108,7 +1108,7 @@ Accept wildcard characters: False The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is implemented on the Receive connector. Valid values are: -- None: Extended Protection for Authentication isn't used. This is the default value. +- None: Extended Protection for Authentication isn't used. This value is the default. - Allow: Extended Protection for Authentication is used only if the connecting host supports it. Otherwise, connections are established without Extended Protection for Authentication. - Require: Extended Protection for Authentication is required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection is rejected. @@ -1158,7 +1158,7 @@ Accept wildcard characters: False The LongAddressesEnabled parameter specifies whether the Receive connector accepts long X.400 email addresses. The X.400 email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. Valid values are - $true: X.400 email addresses can be up to 1,860 characters long after IMCEA encapsulation. -- $false: The maximum length of a complete SMTP email address is 571 characters. This is the default value. +- $false: The maximum length of a complete SMTP email address is 571 characters. This value is the default. When you set this parameter to the value $true, the following changes are made to the Receive connector: @@ -1186,7 +1186,7 @@ Accept wildcard characters: False This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. -The MaxAcknowledgementDelay parameter specifies the maximum period the transport server delays acknowledgment until it verifies that the message has been successfully delivered to all recipients. When receiving messages from a host that doesn't support shadow redundancy, an Exchange Server 2010 transport server will delay issuing an acknowledgment until it verifies that the message has been successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server will time out and issue an acknowledgment anyway. +The MaxAcknowledgementDelay parameter specifies the maximum period the transport server delays acknowledgment until it verifies that the message is successfully delivered to all recipients. When receiving messages from a host that doesn't support shadow redundancy, an Exchange Server 2010 transport server delays issuing an acknowledgment until it verifies that the message is successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server times out and issue an acknowledgment anyway. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1217,7 +1217,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is from 1 to 2147483647 bytes. @@ -1374,7 +1374,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value for this parameter is from 65536 to 2147483647 bytes. @@ -1488,7 +1488,7 @@ Accept wildcard characters: False The OrarEnabled parameter enables or disables Originator Requested Alternate Recipient (ORAR) on the Receive connector. Valid values are: - $true: ORAR is enabled and is advertised in the XORAR keyword in the EHLO response. The actual ORAR information is transmitted in the RCPT TO SMTP command. -- $false: ORAR is disabled and is isn't advertised in the EHLO response. This is the default value. +- $false: ORAR is disabled and is isn't advertised in the EHLO response. This value is the default. If the email address specified in the ORAR information is a long X.400 email address, you need to set the LongAddressesEnabled parameter to the value $true. @@ -1542,7 +1542,7 @@ Accept wildcard characters: False The PipeliningEnabled parameter specifies whether the PIPELINING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: PIPELINING is enabled and is advertised in the EHLO response. This is the default value. +- $true: PIPELINING is enabled and is advertised in the EHLO response. This value is the default. - $false: PIPELINING is disabled and isn't advertised in the EHLO response. Pipelining is defined in RFC 2920. @@ -1565,7 +1565,7 @@ Accept wildcard characters: False The ProtocolLoggingLevel parameter specifies whether to enable or disable protocol logging for the Receive connector. Valid values are: -- None: Protocol logging is disabled on the Receive connector. This is the default value. +- None: Protocol logging is disabled on the Receive connector. This value is the default. - Verbose: Protocol logging is enabled on the Receive connector. For more information about protocol logging, see [Protocol logging](https://learn.microsoft.com/Exchange/mail-flow/connectors/protocol-logging). @@ -1589,7 +1589,7 @@ Accept wildcard characters: False The RejectReservedSecondLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved second-level domains as specified in RFC 2606 (example.com, example.net, or example.org). Valid value are: - $true: RCPT TO commands that contain reserved second-level domains are rejected. -- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This is the default value. +- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1610,7 +1610,7 @@ Accept wildcard characters: False The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved top-level domains (TLDs) as specified in RFC 2606 (.test, .example, .invalid, or .localhost). Valid value are: - $true: RCPT TO commands that contain reserved TLDs are rejected. -- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This is the default value. +- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1631,7 +1631,7 @@ Accept wildcard characters: False The RejectSingleLabelRecipientDomains parameter specifies whether to reject connections that contain recipients in single-label domains (for example, chris@contoso instead of chris@contoso.com). Valid values are: - $true: RCPT TO commands that contain single-label domains are rejected. -- $false: RCPT TO commands that contain single-label domains aren't rejected. This is the default value. +- $false: RCPT TO commands that contain single-label domains aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1652,7 +1652,7 @@ Accept wildcard characters: False The RequireEHLODomain parameter specifies whether the client must provide a domain name in the EHLO handshake after the SMTP connection is established. Valid values are: - $true: The client must provide a domain name in the EHLO handshake. If it doesn't, the SMTP connection is closed. -- $false: The client isn't required to provide a domain name in the EHLO handshake. This is the default value. +- $false: The client isn't required to provide a domain name in the EHLO handshake. This value is the default. ```yaml Type: Boolean @@ -1673,7 +1673,7 @@ Accept wildcard characters: False The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are: - $true: Inbound messages on the Receive connector require TLS transmission. -- $false: Inbound messages on the Receive connector don't require TLS transmission. This is the default value. +- $false: Inbound messages on the Receive connector don't require TLS transmission. This value is the default. ```yaml Type: Boolean @@ -1736,7 +1736,7 @@ Accept wildcard characters: False The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are: -- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This is the default value. +- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This value is the default. - Disabled: SIZE is disabled and isn't advertised in the EHLO response. - EnabledwithoutValue: SIZE is enabled and is advertised in the EHLO response, but the value of the MaxMessageSize parameter isn't disclosed in the EHLO response. This setting allows messages to bypass message size checks for authenticated connections between Mailbox servers. @@ -1761,7 +1761,7 @@ Accept wildcard characters: False The SuppressXAnonymousTls parameter specifies whether the X-ANONYMOUSTLS Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: X-ANONYMOUSTLS is disabled and isn't advertised in the EHLO response. This setting also requires that you set the UseDownGradedExchangeServerAuth parameter to the value $true on the Set-TransportService cmdlet on the server. -- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This is the default value. +- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This value is the default. The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter contains the value ExchangeServer. @@ -1781,7 +1781,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The TarpitInterval parameter specifies the amount of time to delay an SMTP response to a remote server that may be abusing the connection. The default value is 00:00:05 (5 seconds.). +The TarpitInterval parameter specifies the amount of time to delay an SMTP response to a remote server that might be abusing the connection. The default value is 00:00:05 (5 seconds). To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md index 23e939498a..2b47aa2592 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md @@ -13,7 +13,7 @@ title: New-RemoteDomain # New-RemoteDomain ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-RemoteDomain cmdlet to create a managed connection for a remote domain. When you create a remote domain, you can control mail flow with more precision, apply message formatting and messaging policies and specify acceptable character sets for messages sent to and received from the remote domain. @@ -30,7 +30,7 @@ New-RemoteDomain [-Name] -DomainName ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md index f82e91d586..ad9e5e75d8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md @@ -158,7 +158,7 @@ Directory synchronization must be configured correctly for a mailbox to be creat The policies that you apply to recipients in the on-premises Exchange organization, such as Unified Messaging or compliance policies, aren't applied to mailboxes in the service. You must configure policies in the service if you want policies to be applied to recipients in the service. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -169,7 +169,7 @@ $Credentials = Get-Credential New-RemoteMailbox -Name "Kim Akers" -Password $Credentials.Password -UserPrincipalName kim@corp.contoso.com ``` -This example creates an on-premises mail user and its associated mailbox in the service. The remote routing address doesn't need to be specified because mail flow between the on-premises organization and the service has been configured. Using this configuration, the New-RemoteMailbox cmdlet automatically calculates the SMTP address of the mailbox to be used with the RemoteRoutingAddress parameter. This example also assumes directory synchronization has been configured. +This example creates an on-premises mail user and its associated mailbox in the service. The remote routing address doesn't need to be specified because mail flow between the on-premises organization and the service is configured. Using this configuration, the New-RemoteMailbox cmdlet automatically calculates the SMTP address of the mailbox to be used with the RemoteRoutingAddress parameter. This example also assumes directory synchronization is configured. The first command stores the password to use with the new remote mailbox in a variable by using the Get-Credential cmdlet. The last command creates the mail user. @@ -577,7 +577,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -644,7 +644,7 @@ Accept wildcard characters: False The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are: -- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value. +- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This value is the default. - $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC. Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server. @@ -690,7 +690,7 @@ Accept wildcard characters: False The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are: - $true: The user is required to change their password the next time they log on. -- $false: The user isn't required to change their password the next time they log on. This is the default value. +- $false: The user isn't required to change their password the next time they log on. This value is the default. ```yaml Type: Boolean @@ -708,7 +708,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -728,7 +728,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md index b692122c77..ed307ad3f4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md @@ -85,7 +85,7 @@ When you set the email address of the reporting mailbox in the Microsoft Defende - Microsoft integrated reporting using Microsoft reporting tools in Outlook: The ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhishAddresses parameters. - Microsoft integrated reporting using non-Microsoft tools in Outlook: The ThirdPartyReportAddresses parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -151,7 +151,7 @@ This example creates the report submission policy with the following values: rep The DisableQuarantineReportingOption parameter allows or prevents users from reporting messages in quarantine. Valid values are: - $true: Users can't report quarantined messages from quarantine. -- $false: Users can report quarantined messages from quarantine. This is the default value. +- $false: Users can report quarantined messages from quarantine. This value is the default. This parameter is meaningful only reporting in Outlook is enabled as described in the EnableReportToMicrosoft parameter. @@ -210,7 +210,7 @@ Accept wildcard characters: False The EnableCustomNotificationSender parameter specifies whether a custom sender email address is used for result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are: - $true: Use a custom Microsoft 365 sender email address. -- $false: Use the default sender email address. This is the default value. +- $false: Use the default sender email address. This value is the default. You specify the sender email address using the NotificationSenderAddress parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md index e15468aa90..277ab07e3d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md @@ -48,7 +48,7 @@ When you set the email address of the reporting mailbox in the Microsoft Defende When you use this cmdlet to set the email address of the reporting mailbox, the corresponding parameters in the *\-ReportSubmissionPolicy cmdlets are not updated. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -142,7 +142,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled or disabled. Valid values are: -- $true: The rule is enabled. This is the default value. +- $true: The rule is enabled. This value is the default. - $false: The rule is disabled. After you create the rule, use the Enable-ReportSubmissionRule and Disable-ReportSubmissionRule cmdlets to enable or disable the rule. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md index b7d58bc239..bf34b33313 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md @@ -164,7 +164,7 @@ The Applications parameter specifies the target when Microsoft 365 Groups are in - `Group:Exchange` for the mailbox that's connected to the Microsoft 365 Group. - `Group:SharePoint` for the SharePoint site that's connected to the Microsoft 365 Group. - `"Group:Exchange,SharePoint"` for both the mailbox and the SharePoint site that are connected to the Microsoft 365 Group. -- blank (`$null`): This is the default value, and is functionally equivalent to the value `"Group:Exchange,SharePoint"`. +- blank (`$null`): This value is the default, and is functionally equivalent to the value `"Group:Exchange,SharePoint"`. ```yaml Type: MultiValuedProperty @@ -223,7 +223,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml @@ -523,9 +523,9 @@ Accept wildcard characters: False The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for the policy. Valid values are: - $true: Preservation Lock is enabled for the policy. No one -- including an administrator -- can turn off the policy or make it less restrictive. -- $false: Preservation Lock isn't enabled for the policy. This is the default value. +- $false: Preservation Lock isn't enabled for the policy. This value is the default. -After a policy has been locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only ways that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. +After a policy is locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only ways that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. Therefore, before you lock a retention policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need. @@ -550,7 +550,7 @@ Accept wildcard characters: False The RetainCloudAttachment parameter specifies that this is a cloud attachment policy. Valid values are: - $true: The policy is a cloud attachment policy. -- $false: The policy is not a cloud attachment policy. This is the default value. +- $false: The policy is not a cloud attachment policy. This value is the default. For the value $true, you can only use the following location parameters: diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md index 70672338c9..5744f9b2f0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md @@ -75,14 +75,14 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned New-RetentionComplianceRule -Name InternalCompanyRule -Policy "Internal Company Policy" -RetentionDuration Unlimited ``` -This example creates a new case hold rule named InternalCompanyRule and adds it to the existing case hold policy named "Internal Company Policy". Content will be held indefinitely. +This example creates a new case hold rule named InternalCompanyRule and adds it to the existing case hold policy named "Internal Company Policy". Content is held indefinitely. ### Example 2 ```powershell New-RetentionComplianceRule -Name SeptOneYear -Policy "Internal Company Policy" -RetentionDuration 365 -RetentionComplianceAction KeepAndDelete -ExpirationDateOption ModificationAgeInDays ``` -This example creates a new retention rule named SeptOneYear and adds it to the existing retention policy named "Internal Company Policy". Content will be held for one year from the day content was last modified before it is deleted. +This example creates a new retention rule named SeptOneYear and adds it to the existing retention policy named "Internal Company Policy". Content is held for one year from the day content was last modified before it is deleted. ## PARAMETERS @@ -285,7 +285,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: +The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter doesn't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: - IPM.Note.Microsoft.Conversation - IPM.Note.Microsoft.Conversation.Voice @@ -296,7 +296,7 @@ The ExcludedItemClasses parameter specifies the types of messages to exclude fro - IPM.Note.Microsoft.Voicemail.UM - IPM.Note.Microsoft.Voicemail.UM.CA -Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. Note that the values you specify aren't validated, so the parameter accepts any text value. +Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. The values you specify aren't validated, so the parameter accepts any text value. You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`. @@ -428,7 +428,7 @@ The RetentionDurationDisplayHint parameter specifies the units that are used to - Months - Years -For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration. You can't use this parameter for Teams retention rules. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md index 68bc9f02ec..e52f0a2909 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md @@ -13,7 +13,7 @@ title: New-RetentionPolicy # New-RetentionPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-RetentionPolicy cmdlet to create a retention policy. @@ -36,7 +36,7 @@ New-RetentionPolicy [-Name] ## DESCRIPTION Retention policy tags are associated with a retention policy. When a retention policy is applied to a mailbox, tags associated with the policy are available to the mailbox user. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -125,14 +125,14 @@ This parameter is available only in the cloud-based service. The IsDefault switch specifies that this retention policy is the default retention policy. You don't need to specify a value with this switch. -When you use this switch, you'll get a warning that this retention policy will replace the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy. +When you use this switch, you get a warning that this retention policy replaces the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy. **Note**: Changing which retention policy is the default might or might not affect new and existing mailboxes based on the value of the RetentionPolicy parameter on all mailbox plans: - $null (blank): Changes to which retention policy is the default are continually reflected in new and existing mailboxes. - A retention policy is specified: The value of the RetentionPolicy parameter for all mailbox plans should be $null (blank) or match the Exchange retention policy that's configured as default policy for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. For more information see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans). -If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value. +If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox is overwritten when changing licenses. You need to manually reset the RetentionPolicy to the original value. Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md index f38d4c2f54..cd0aad232e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md @@ -13,7 +13,7 @@ title: New-RetentionPolicyTag # New-RetentionPolicyTag ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-RetentionPolicyTag cmdlet to create a retention tag. @@ -72,7 +72,7 @@ Retention tags are used to apply message retention settings to folders and items Retention tags support a display of the tag name and an optional comment in localized languages. Language culture codes from the CultureInfo class are used for this purpose. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -88,7 +88,7 @@ This example creates the retention policy tag Finance-DeletedItems for the Delet New-RetentionPolicyTag "Finance-Default" -Type All -RetentionEnabled $true -AgeLimitForRetention 365 -RetentionAction PermanentlyDelete ``` -This example creates the default policy tag Finance-Default. When applied to a mailbox as part of a retention policy, the tag permanently deletes all items without a retention tag within 365 days. Items of a particular message class such as Voicemail, for which a default tag (a retention tag of type All) exists, aren't impacted. +This example creates the default policy tag Finance-Default. When applied to a mailbox as part of a retention policy, the tag permanently deletes all items without a retention tag within 365 days. Items of a particular message class such as Voicemail, for which a default tag (a retention tag of type All) exists, aren't affected. ### Example 3 ```powershell @@ -421,7 +421,7 @@ The RetentionAction parameter specifies the action for the retention policy. Val - DeleteAndAllowRecovery: Deletes a message and allows recovery from the Recoverable Items folder. - MarkAsPastRetentionLimit: Messages are marked as past the retention limit. - MoveToArchive: Moves a message to the user's archive mailbox. You can use this action for retention tags of type All, Personal and RecoverableItems. -- PermanentlyDelete: Permanently deletes a message. A message that has been permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox. +- PermanentlyDelete: Permanently deletes a message. A message that is permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox. The MoveToDeletedItems and MoveToFolder actions are available, but don't work. These actions are available for upgrades from messaging records management (MRM) 1.0 (managed folders) to MRM 2.0 (retention policies). MRM 2.0 was introduced in Exchange 2010 Service Pack 1 (SP1). @@ -447,7 +447,7 @@ The RetentionEnabled parameter specifies whether the tag is enabled. When set to Messages with a disabled tag are still considered tagged, so any tags of the same type as the disabled tag in the user's retention policy aren't applied to such messages. -When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users may apply this tag to items they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later may result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it may be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_`. +When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users might apply this tag to items they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later might result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it might be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_`. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md index d3ed1851f8..fcd51b4f49 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md @@ -13,7 +13,7 @@ title: New-RoleAssignmentPolicy # New-RoleAssignmentPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-RoleAssignmentPolicy cmdlet to create management role assignment policies in your organization. @@ -35,11 +35,11 @@ New-RoleAssignmentPolicy [-Name] ## DESCRIPTION When you create an assignment policy, you can assign it to users using the New-Mailbox, Set-Mailbox, or Enable-Mailbox cmdlets. If you make the new assignment policy the default assignment policy, it's assigned to all new mailboxes that don't have an explicit assignment policy assigned to them. -You can add management roles to the new assignment policy when you create it, or you can create the assignment policy and add roles later. You must assign at least one management role to the new assignment policy for it to apply permissions to a mailbox. Without any roles assigned to the new assignment policy, users assigned to it won't be able to manage their mailbox configuration. To assign a management role after the assignment policy has been created, use the New-ManagementRoleAssignment cmdlet. For more information, see [Manage role assignment policies](https://learn.microsoft.com/Exchange/permissions/role-assignment-policies). +You can add management roles to the new assignment policy when you create it, or you can create the assignment policy and add roles later. You must assign at least one management role to the new assignment policy for it to apply permissions to a mailbox. Without any roles assigned to the new assignment policy, users assigned to it can't manage their mailbox configuration. To assign a management role after the assignment policy is created, use the New-ManagementRoleAssignment cmdlet. For more information, see [Manage role assignment policies](https://learn.microsoft.com/Exchange/permissions/role-assignment-policies). For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md index c73a9903bb..ac057d2934 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md @@ -13,7 +13,7 @@ title: New-RoleGroup # New-RoleGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-RoleGroup cmdlet to create management role groups. @@ -69,7 +69,7 @@ When you create a role group, you can create the group and add members to it dir For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -462,7 +462,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md index 353c3f4107..61483c3359 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md @@ -37,7 +37,7 @@ The New-RoutingGroupConnector cmdlet creates a new routing group connector betwe To create the routing group connector, you must specify the source servers from the originating routing group and the target servers in the destination routing group. The routing group connector is created in the routing group of which the source server is a member. By using the Bidirectional parameter, you can specify whether the connector is used for one-way or two-way mail flow. If you specify a two-way connector, a reciprocal connector is created in the target routing group. The source and target servers must be Exchange 2010 Hub Transport servers or Exchange 2003 bridgehead servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md index 0cfc7ea229..a64f68eb70 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md @@ -35,7 +35,7 @@ New-RpcClientAccess -Server ## DESCRIPTION After you run this command, you must start the Exchange RPC Client Access service on the Exchange Client Access server to enable RPC client access. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md index 7830f1bf89..39965ff971 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md @@ -43,7 +43,7 @@ New safe attachment policies that you create using this cmdlet aren't applied to A safe attachment policy can be assigned to only one safe attachment rule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,9 +54,9 @@ New-SafeAttachmentPolicy -Name "Marketing Block Attachments" -Enable $true -Redi This example creates a new safe attachment policy named Marketing Block Attachments with the following options: -- The action is Block. This is the default value of the Action parameter, so you don't need to specify it. -- The value $true for the Enable parameter is required so the policy will actually use the default Action parameter value of Block (or any other Action parameter value). -- Enable redirection for detected malware attachments and send the messages to admin@contoso.com. +- The action is Block. This value is the default of the Action parameter, so you don't need to specify it. +- The value $true for the Enable parameter is required so the policy actually uses the default Action parameter value of Block (or any other Action parameter value). +- Enable redirection for detected malware attachments and send the messages to `admin@contoso.com`. - If Safe Attachments scanning isn't available or encounters errors, don't deliver the message as normal. The default value of the ActionOnError parameter is $true, so you don't need to specify it. ## PARAMETERS @@ -86,7 +86,7 @@ Accept wildcard characters: False The Action parameter specifies the action for the safe attachment policy. Valid values are: - Allow: Deliver the message if malware is detected in the attachment and track scanning results. This value corresponds to **Monitor** for the **Safe Attachments unknown malware response** property of the policy in the Microsoft Defender portal. -- Block: Block the email message that contains the malware attachment. This is the default value. +- Block: Block the email message that contains the malware attachment. This value is the default. - DynamicDelivery: Deliver the email message with a placeholder for each email attachment. The placeholder remains until a copy of the attachment is scanned and determined to be safe. For more information, see [Dynamic Delivery in Safe Attachments policies](https://learn.microsoft.com/defender-office-365/safe-attachments-about#dynamic-delivery-in-safe-attachments-policies). The value of this parameter is meaningful only when the value of the Enable parameter is $true (the default value is $false). @@ -153,7 +153,7 @@ Accept wildcard characters: False The Enable parameter works with the Action parameter to specify the action for the safe attachment policy. Valid values are: - $true: The Action parameter specifies the action for the Safe Attachment policy. -- $false: This is the default value. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. This value corresponds to the **Off** selection for the **Safe Attachments unknown malware response** setting of the policy in the Microsoft Defender portal. +- $false: This value is the default. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. This value corresponds to the **Off** selection for the **Safe Attachments unknown malware response** setting of the policy in the Microsoft Defender portal. To enable or disable a complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell), use the Enable-SafeAttachmentRule or Disable-SafeAttachmentRule cmdlets. @@ -240,7 +240,7 @@ Accept wildcard characters: False The Redirect parameter specifies whether to deliver messages to an alternate email address if malware is detected in an attachment. Valid values are: - $true: Messages that contain malware attachments are delivered to the email address specified by the RedirectAddress parameter. This value is meaningful only when the value of the Action parameter is Allow. -- $false: Messages that contain malware attachments aren't delivered to another email address. This is the default value. +- $false: Messages that contain malware attachments aren't delivered to another email address. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md index 31aa541218..2edb57afa5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md @@ -47,7 +47,7 @@ Safe Attachments is a feature in Microsoft Defender for Office 365 that opens em > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Safe Attachments policy settings](https://learn.microsoft.com/defender-office-365/safe-attachments-about#safe-attachments-policy-settings). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -153,7 +153,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: -- $true: The rule is enabled. This is the default value. +- $true: The rule is enabled. This value is the default. - $false: The rule is disabled. In the properties of the rule, the value of this parameter is visible in the State property. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md index 0528b6b005..3ab8987a5c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md @@ -49,7 +49,7 @@ Safe Links is a feature in Microsoft Defender for Office 365 that checks links t New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the SafeLinksPolicy parameter on the New-SafeLinksRule or Set-SafeLinksRule cmdlets to associate the policy with a rule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,7 +62,7 @@ This example creates a new Safe Links policy named Marketing Block URL with the - The policy is enabled. - Users aren't allowed to click through to the original URL. -- User clicks on URLs are tracked. This is the default value of the TrackClicks parameter, so you don't need to specify it. +- User clicks on URLs are tracked. This value is the default of the TrackClicks parameter, so you don't need to specify it. ## PARAMETERS @@ -170,7 +170,7 @@ Accept wildcard characters: False The DeliverMessageAfterScan parameter specifies whether to deliver email messages only after Safe Links scanning is complete. Valid values are: -- $true: Wait until Safe Links scanning is complete before delivering the message. Messages that contain malicious links are not delivered. This is the default value. +- $true: Wait until Safe Links scanning is complete before delivering the message. Messages that contain malicious links are not delivered. This value is the default. - $false: If Safe Links scanning can't complete, deliver the message anyway. ```yaml @@ -192,7 +192,7 @@ Accept wildcard characters: False The DisableUrlRewrite parameter specifies whether to rewrite (wrap) URLs in email messages. Valid values are: - $true: URLs in messages are not rewritten, but messages are still scanned by Safe Links prior to delivery. Time of click checks on links are done using the Safe Links API in supported Outlook clients (currently, Outlook for Windows and Outlook for Mac). -- $false: URLs in messages are rewritten. API checks still occur on unwrapped URLs in supported clients if the user is in a valid Safe Links policy. This is the default value. +- $false: URLs in messages are rewritten. API checks still occur on unwrapped URLs in supported clients if the user is in a valid Safe Links policy. This value is the default. In PowerShell, the default value is $false. In new Safe Links policies created in the Microsoft Defender portal, the default value is $true. @@ -238,7 +238,7 @@ Accept wildcard characters: False The EnableForInternalSenders parameter specifies whether the Safe Links policy is applied to messages sent between internal senders and internal recipients within the same Exchange Online organization. Valid values are: -- $true: The policy is applied to internal and external senders. This is the default value. +- $true: The policy is applied to internal and external senders. This value is the default. - $false: The policy is applied only to external senders. ```yaml @@ -260,7 +260,7 @@ Accept wildcard characters: False The EnableOrganizationBranding parameter specifies whether your organization's logo is displayed on Safe Links warning and notification pages. Valid values are: - $true: Organization branding is displayed on Safe Links warning and notification pages. Before you configure this value, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your company logo. -- $false: Organization branding is not displayed on Safe Links warning and notification pages. This is the default value. +- $false: Organization branding is not displayed on Safe Links warning and notification pages. This value is the default. ```yaml Type: Boolean @@ -280,7 +280,7 @@ Accept wildcard characters: False The EnableSafeLinksForEmail parameter specifies whether to enable Safe Links protection for email messages. Valid values are: -- $true: Safe Links is enabled for email. This is the default value. When a user clicks a link in an email, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links is enabled for email. This value is the default. When a user clicks a link in an email, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for email. ```yaml @@ -301,10 +301,10 @@ Accept wildcard characters: False The EnableSafeLinksForOffice parameter specifies whether to enable Safe Links protection for supported Office desktop, mobile, or web apps. Valid values are: -- $true: Safe Links scanning is enabled in Office apps. This is the default value. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links scanning is enabled in Office apps. This value is the default. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for Office apps. -Note that this protection applies to links in Office documents, not links in email messages. +This protection applies to links in Office documents, not links in email messages. ```yaml Type: Boolean @@ -324,7 +324,7 @@ Accept wildcard characters: False The EnableSafeLinksForTeams parameter specifies whether Safe Links is enabled for Microsoft Teams. Valid values are: -- $true: Safe Links is enabled for Teams. This is the default value. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links is enabled for Teams. This value is the default. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for Teams. ```yaml @@ -381,7 +381,7 @@ Accept wildcard characters: False The ScanUrls parameter specifies whether to enable or disable real-time scanning of clicked links in email messages. Valid values are: -- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This is the default value. +- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This value is the default. - $false: Real-time scanning of clicked links, including links that point to files, is disabled. ```yaml @@ -402,7 +402,7 @@ Accept wildcard characters: False The TrackClicks parameter specifies whether to track user clicks related to Safe Links protection of links. Valid values are: -- $true: User clicks messages are tracked. This is the default value. +- $true: User clicks messages are tracked. This value is the default. - $false: User clicks messages aren't tracked. ```yaml @@ -424,7 +424,7 @@ Accept wildcard characters: False The UseTranslatedNotificationText specifies whether to use Microsoft Translator to automatically localize the custom notification text that you specified with the CustomNotificationText parameter. Valid values are: - $true: Translate custom notification text to the user's language. -- $false: Don't translate custom notification text to the user's language. This is the default value. +- $false: Don't translate custom notification text to the user's language. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md index f0bcda85ea..b097258420 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md @@ -45,7 +45,7 @@ Safe Links is a feature in Microsoft Defender for Office 365 that checks links i > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Recipient filters in Safe Links policies](https://learn.microsoft.com/defender-office-365/safe-links-about#recipient-filters-in-safe-links-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -176,7 +176,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the rule is enabled. Valid values are: -- $true: The rule is enabled. This is the default value. +- $true: The rule is enabled. This value is the default. - $false: The rule is disabled. In the properties of the rule, the value of this parameter is visible in the State property. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md index bc6b60fcfa..4396c8006d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md @@ -31,9 +31,11 @@ New-SearchDocumentFormat [-Identity] -Extension -SentTo ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -50,7 +50,7 @@ This example creates the SecOps mailbox override policy with the specified setti > Applicable: Exchange Online -The Name parameter specifies the name for the SecOps mailbox override policy. Regardless of the value you specify, the name will be SecOpsOverridePolicy. +The Name parameter specifies the name for the SecOps mailbox override policy. Regardless of the value you specify, the name is SecOpsOverridePolicy. ```yaml Type: String @@ -147,7 +147,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md index 25a2ec45c2..c200e2ff41 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md @@ -106,7 +106,7 @@ New-SendConnector [-Name] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -161,7 +161,7 @@ Accept wildcard characters: False The AddressSpaces parameter specifies the domain names to which the Send connector routes mail. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`. -- AddressSpaceType: On an Edge server, the address space type must be SMTP. In the Transport service on a Mailbox server, the address space type may be SMTP, X400, or any other text string. If you omit the address space type, SMTP is assumed. +- AddressSpaceType: On an Edge server, the address space type must be SMTP. In the Transport service on a Mailbox server, the address space type might be SMTP, X400, or any other text string. If you omit the address space type, SMTP is assumed. - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com is not. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address space type, you can enter any text for the address space. - AddressSpaceCost: The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. This parameter is optional. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains the semicolon character (;), you must specify the address space cost. @@ -172,7 +172,7 @@ If you specify the address space type or the address space cost, you must enclos - "SMTP:contoso.com" - contoso.com -You may specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3". +You might specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3". If you specify a non-SMTP address space type on a Send connector configured in the Transport service on a Mailbox server, you must configure the following parameters: @@ -223,7 +223,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f Valid values are: -- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. +- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. ```yaml @@ -305,7 +305,7 @@ Accept wildcard characters: False The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Microsoft 365. Valid values are: -- Default: The connector isn't used to send messages to Microsoft 365. This is the default value. +- Default: The connector isn't used to send messages to Microsoft 365. This value is the default. - XPremises: The connector is used to send messages to Microsoft 365. ```yaml @@ -698,7 +698,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. Values entered in bytes are rounded up to nearest kilobyte. The valid input range for this parameter is 0 to 2147483647 bytes. To remove the message size limit on a Send connector, enter a value of unlimited. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md index 57d018af70..6189996d80 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md @@ -36,7 +36,7 @@ Service principals exist in Microsoft Entra ID to define what apps can do, who c For more information, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md index 7ed4d11a9f..cbecf3513b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md @@ -38,7 +38,7 @@ New-SettingOverride [-Name] -Component -Parameters -Domains ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -132,7 +132,7 @@ Accept wildcard characters: False The Default switch specifies that this sharing policy is the default sharing policy for all mailboxes. You don't need to specify a value with this switch. -If no sharing policy has been applied to a mailbox, the default policy is automatically applied. If you want to disable sharing across your organization, you can set the default policy as disabled. +If no sharing policy is applied to a mailbox, the default policy is automatically applied. If you want to disable sharing across your organization, you can set the default policy as disabled. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md index 6519e1a622..6d87b66bcf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md @@ -38,7 +38,7 @@ New-SiteMailbox [[-DisplayName] ] -SharePointUrl ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md index 1c8207891f..78730144a7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md @@ -40,7 +40,7 @@ New-SiteMailboxProvisioningPolicy [-Name] ## DESCRIPTION Site mailboxes allow access to both Microsoft SharePoint documents and Exchange email using the same client interface. Site mailbox provisioning policies apply settings to new site mailboxes that you create. You can create multiple site mailbox provisioning policies, but only the default policy is followed when users create site mailboxes. The default site mailbox provisioning policy is named Default. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -96,7 +96,7 @@ Accept wildcard characters: False The AliasPrefix parameter specifies the custom text prefix to add to the aliases of new site mailboxes. Valid values are: - A text string that's 8 characters or less. When you specify a text value, the value of the DefaultAliasPrefixEnabled parameter ignored and aliases get the text prefix you specified. -- The value $null. This is the default value. The results of this value depend on the DefaultAliasPrefixEnabled parameter value. When it's $true, aliases get the default prefix text. When it's $false, aliases don't get any prefix text. +- The value $null. This value is the default. The results of this value depend on the DefaultAliasPrefixEnabled parameter value. When it's $true, aliases get the default prefix text. When it's $false, aliases don't get any prefix text. ```yaml Type: String @@ -137,7 +137,7 @@ Accept wildcard characters: False The DefaultAliasPrefixEnabled parameter specifies whether new site mailboxes have the default prefix text added to the alias. Valid values are: -- $true: Aliases get the default prefix text. This is the default value. In Microsoft 365, the default prefix text is `SMO-` (for example, the alias value `BugBash_2016` becomes `SMO-BugBash_2016`). In on-premises Exchange, the default prefix text is `SM-` (for example, the alias value `BugBash_2016` becomes `SM-BugBash_2016`). +- $true: Aliases get the default prefix text. This value is the default. In Microsoft 365, the default prefix text is `SMO-` (for example, the alias value `BugBash_2016` becomes `SMO-BugBash_2016`). In on-premises Exchange, the default prefix text is `SM-` (for example, the alias value `BugBash_2016` becomes `SM-BugBash_2016`). - $false: Aliases don't get the default prefix text. The value of this parameter is related to the value of the AliasPrefix parameter. If you specify a text string for AliasPrefix, the DefaultAliasPrefixEnabled value is ignored. Specifying a text value for AliasPrefix automatically sets the value to $false, but even if you set it to $true, the default alias prefix text isn't used. @@ -206,7 +206,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. @@ -237,7 +237,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147482624 bytes) or the value unlimited. The default value is 36 MB. @@ -267,7 +267,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md index 8b8cb8b880..a0e63f4d33 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md @@ -13,7 +13,7 @@ title: New-SweepRule # New-SweepRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-SweepRule cmdlet to create Sweep rules in mailboxes. Sweep rules run at regular intervals to help keep your Inbox clean. @@ -40,7 +40,7 @@ New-SweepRule [-Name] -Provider ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -184,7 +184,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the Sweep rule is enabled or disabled. Valid values are: -- $true: The rule is enabled. This is the default value. +- $true: The rule is enabled. This value is the default. - $false: The rule is disabled. After you create the rule, you can enable or disable it by using the Enable-SweepRule and Disable-SweepRule cmdlets. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md index 41a1745507..8c39847c58 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md @@ -13,7 +13,7 @@ title: New-SyncMailPublicFolder # New-SyncMailPublicFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. The New-SyncMailPublicFolder cmdlet is used by the Import-MailPublicFoldersForMigration.ps1 and Sync-MailPublicFolders.ps1 scripts to create mail-enabled public folder recipient objects in Exchange Online (the scripts synchronize mail-enabled public folder objects from the source on-premises Exchange organization to Exchange Online). Don't use this cmdlet unless you are directed to do so by Microsoft Customer Service and Support or by specific documentation. @@ -63,7 +63,7 @@ New-SyncMailPublicFolder [-Name] [-Alias] -EntryId ## DESCRIPTION This cmdlet is only used by the Import-MailPublicFoldersForMigration.ps1 and Sync-MailPublicFolders.ps1 scripts. Don't run this cmdlet in the Exchange Management Shell or in Exchange Online PowerShell. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -510,7 +510,7 @@ Accept wildcard characters: False The DeliverToMailboxAndForward parameter specifies the message delivery behavior when a forwarding address is specified by the ForwardingAddress parameter. Valid values are: - $true: Messages are delivered to this mail-enabled public folder and forwarded to the specified recipient or email address. -- $false: If a forwarding recipient is configured, messages are delivered only to the specified recipient, and messages aren't delivered to this mail-enabled public folder. If no forwarding recipient is configured, messages are delivered only to this mailbox. This is the default value. +- $false: If a forwarding recipient is configured, messages are delivered only to the specified recipient, and messages aren't delivered to this mail-enabled public folder. If no forwarding recipient is configured, messages are delivered only to this mailbox. This value is the default. The default value is $false. This parameter is meaningful only if you configure a forwarding recipient by using the ForwardingAddress parameter. @@ -711,7 +711,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -742,7 +742,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md index 66b63211c0..5f57d4f5d4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md @@ -42,7 +42,7 @@ New-SystemMessage -Language -QuotaMessageType - ## DESCRIPTION NDRs are issued to the senders of email messages that haven't reached their intended recipients. Quota messages are issued to users whose mailboxes or public folders have reached the specific warning, prohibit send, or prohibit receive quotas. Custom NDRs and quota messages replace the default messages that are included with Exchange. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -205,7 +205,7 @@ The following HTML tags are available: - `` and `` (italic) - `
` (line break) - `

` and `

` (paragraph) -- `` and `` (hyperlink). **Note**: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you'll receive an error (because of the double quotation marks in the tag). +- `` and `` (hyperlink). **Note**: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you get an error (because of the double quotation marks in the tag). Use the following escape codes for these special characters: diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md index bfee67b53a..0968adb205 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md @@ -35,7 +35,7 @@ New-TeamsProtectionPolicy [-Name] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -184,7 +184,7 @@ Accept wildcard characters: False The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware and high confidence phishing messages in Teams messages. Valid values are: -- $true: ZAP for malware and high confidence phishing messages in Teams is enabled. This is the default value. +- $true: ZAP for malware and high confidence phishing messages in Teams is enabled. This value is the default. - $false: ZAP for malware and high confidence phishing messages in Teams is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md index e9a52ab70d..dae92b700a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md @@ -45,7 +45,7 @@ You can use this cmdlet only if the following statements are true: > [!IMPORTANT] > Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Configure ZAP for Teams protection in Defender for Office 365 Plan 2](https://learn.microsoft.com/defender-office-365/mdo-support-teams-about#configure-zap-for-teams-protection-in-defender-for-office-365-plan-2). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md index 0c72896810..f4de39cad9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md @@ -50,7 +50,7 @@ New-TenantAllowBlockListItems -Entries -ListType [-NoExpir ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -254,7 +254,7 @@ Accept wildcard characters: False The ListSubType parameter specifies the subtype for this entry. Valid values are: - AdvancedDelivery: Use this value for phishing simulation URLs. For more information, see [Configure the advanced delivery policy for non-Microsoft phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). -- Tenant: This is the default value. +- Tenant: This value is the default. ```yaml Type: ListSubType diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md index dcb4b1d95f..049fb245fe 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md @@ -31,7 +31,7 @@ New-TenantAllowBlockListSpoofItems [-Identity] Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter isn't used and will be removed. +This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited @@ -880,7 +880,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search will run before it times out. +The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search runs before it times out. ```yaml Type: Unlimited @@ -1008,7 +1008,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships will remain active. By default, there is no limit to the number of days that a user's device partnerships will remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed. +The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships remain active. By default, there is no limit to the number of days that a user's device partnerships remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed. ```yaml Type: Unlimited @@ -2168,7 +2168,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter won't affect Exchange admin center operations or Exchange Web Services operations. +The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter doesn't affect Exchange admin center operations or Exchange Web Services operations. ```yaml Type: UInt32 @@ -2245,7 +2245,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets may help prevent accidental data loss. The following cmdlets are designated as destructive: +The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets might help prevent accidental data loss. The following cmdlets are designated as destructive: - Disable-Mailbox - Move-ActiveMailboxDatabase @@ -2293,7 +2293,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling may occur. The default setting is Unlimited. +The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling might occur. The default setting is Unlimited. ```yaml Type: Unlimited diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md index 930b4c4913..465d011257 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md @@ -13,7 +13,7 @@ title: New-TransportRule # New-TransportRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the New-TransportRule cmdlet to create transport rules (mail flow rules) in your organization. @@ -211,9 +211,9 @@ New-TransportRule [-Name] ## DESCRIPTION In on-premises Exchange organizations, rules created on Mailbox servers are stored in Active Directory. All Mailbox servers in the organization have access to the same set of rules. On Edge Transport servers, rules are saved in the local copy of Active Directory Lightweight Directory Services (AD LDS). Rules aren't shared or replicated between Edge Transport servers or between Mailbox servers and Edge Transport servers. Also, some conditions and actions are exclusive to each server role. -The search for words or text patterns in the subject or other header fields in the message occurs after the message has been decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You can't use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields in messages. +The search for words or text patterns in the subject or other header fields in the message occurs after the message is decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You can't use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -226,7 +226,7 @@ This example creates a rule with the following settings: - Name: Ethical Wall - Sales and Brokerage Departments - Conditions: Messages that are sent between members of the groups named Sales Department and Brokerage Department. -- Actions: The message is rejected, and the custom rejection text is Messages sent between the Sales and Brokerage departments are strictly prohibited. Note that the default enhanced status code 5.7.1 is used, because we didn't use the RejectMessageEnhancedStatusCode parameter. +- Actions: The message is rejected, and the custom rejection text is Messages sent between the Sales and Brokerage departments are strictly prohibited. The default enhanced status code 5.7.1 is used, because we didn't use the RejectMessageEnhancedStatusCode parameter. - Exceptions: The Subject field contains the phrases Press Release or Corporate Communication or the message was sent by Tony Smith or Pilar Ackerman. ## PARAMETERS @@ -253,7 +253,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The ActivationDate parameter specifies when the rule starts processing messages. The rule won't take any action on messages until the specified date/time. +The ActivationDate parameter specifies when the rule starts processing messages. The rule doesn't take any action on messages until the specified date/time. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". @@ -333,7 +333,7 @@ In on-premises Exchange, this condition is available only on Mailbox servers. The ADComparisonOperator parameter specifies the comparison operator for the ADComparisonAttribute parameter. Valid values are: -- Equal (This is the default value) +- Equal (default value) - NotEqual ```yaml @@ -704,7 +704,7 @@ In on-premises Exchange, this action is available only on Mailbox servers. The ApplyHtmlDisclaimerFallbackAction parameter specifies what to do if the HTML disclaimer can't be applied to a message (for example, encrypted or signed messages where the contents can't be altered). Valid values are: -- Wrap: This is the default value. A new message is created and the original message is added to it as an attachment. The disclaimer text is added to the new message, which is delivered to the recipients. +- Wrap: This value is the default. A new message is created and the original message is added to it as an attachment. The disclaimer text is added to the new message, which is delivered to the recipients. If you want other rules to examine and act on the original message (which is now an attachment in the new message), make sure those rules are applied _before_ the disclaimer rule by using a lower priority for the disclaimer rule and higher priority for other rules. @@ -739,7 +739,7 @@ In on-premises Exchange, this action is available only on Mailbox servers. The ApplyHtmlDisclaimerLocation parameter specifies where to insert the HTML disclaimer text in the body of messages. Valid values are: -- Append: The disclaimer is added to the end of the message body. This is the default value. +- Append: The disclaimer is added to the end of the message body. This value is the default. - Prepend: The disclaimer is inserted at the beginning of the message body. If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the default value Append is used. @@ -1148,9 +1148,9 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. -The embedded images are treated as attachments (for example, messages with a picture in the signature); for this reason, we do not recommend using a very small value since unexpected messages will be blocked. +The embedded images are treated as attachments (for example, messages with a picture in the signature); for this reason, we do not recommend using a very small value since unexpected messages are blocked. ```yaml Type: ByteQuantifiedSize @@ -1449,7 +1449,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the new rule is created as enabled or disabled. Valid values are: -- $true: The new rule is enabled. This is the default value. +- $true: The new rule is enabled. This value is the default. - $false: The new rule is disabled. To enable or disable a rule after you create it, use the Enable-TransportRule and Disable-TransportRule cmdlets. @@ -1530,7 +1530,7 @@ In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfADComparisonOperator parameter specifies the comparison operator for the ExceptIfADComparisonAttribute parameter. Valid values are: -- Equal (This is the default value) +- Equal (default value) - NotEqual ```yaml @@ -2072,7 +2072,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. ```yaml Type: ByteQuantifiedSize @@ -2593,7 +2593,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. ```yaml Type: ByteQuantifiedSize @@ -2618,7 +2618,7 @@ In on-premises Exchange, this exception is available only on Mailbox servers. The ExceptIfMessageTypeMatches parameter specifies an exception that looks for messages of the specified type. Valid values are: - OOF: Auto-reply messages configured by the user. -- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this exception **will not** match during mail flow rule evaluation. +- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message is forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this exception **does not** match during mail flow rule evaluation. - Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported. - Calendaring: Meeting requests and responses. - PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption). @@ -3300,7 +3300,7 @@ Accept wildcard characters: False This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. -The ExpiryDate parameter specifies when this rule will stop processing messages. The rule won't take any action on messages after the specified date/time. +The ExpiryDate parameter specifies when this rule stops processing messages. The rule doesn't take any action on messages after the specified date/time. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". @@ -3706,10 +3706,10 @@ In on-premises Exchange, this action is available only on Mailbox servers. The IncidentReportContent parameter specifies the message properties that are included in the incident report. Valid values are: - Sender: The sender of the message. -- Recipients: The recipients in the To field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. +- Recipients: The recipients in the To field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients are displayed. - Subject: The Subject field of the message. -- CC: The recipients in the Cc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. -- BCC: The recipients in the Bcc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed. +- CC: The recipients in the Cc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients are displayed. +- BCC: The recipients in the Bcc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients are displayed. - Severity: The audit severity of the rule that was triggered. If the message was processed by more than one rule, the highest severity is displayed. - RuleDetections: The list of rules that the message triggered. - FalsePositive: The false positive if the sender marked the message as a false positive for a PolicyTip. @@ -3740,13 +3740,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2013. -This parameter has been deprecated and is no longer used. Use the IncidentReportContent parameter instead. The value AttachOriginalMail on the IncidentReportContent parameter is equivalent to setting this parameter to the value IncludeOriginalMail. +This parameter is deprecated and no longer used. Use the IncidentReportContent parameter instead. The value AttachOriginalMail on the IncidentReportContent parameter is equivalent to setting this parameter to the value IncludeOriginalMail. This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. -The IncidentReportOriginalMail parameter specifies whether to include the original message with the incident report. This parameter is used together with the GenerateIncidentReport parameter. Valid values are: +The IncidentReportOriginalMail parameter specifies whether to include the original message with the incident report. Use this parameter with the GenerateIncidentReport parameter. Valid values are: - IncludeOriginalMail - DoNotIncludeOriginalMail (this is the default value) @@ -3901,7 +3901,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. ```yaml Type: ByteQuantifiedSize @@ -3926,7 +3926,7 @@ In on-premises Exchange, this condition is available only on Mailbox servers. The MessageTypeMatches parameter specifies a condition that looks for messages of the specified type. Valid values are: - OOF: Auto-reply messages configured by the user. -- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this condition **will not** match during mail flow rule evaluation. +- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message is forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this condition **does not** match during mail flow rule evaluation. - Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported. - Calendaring: Meeting requests and responses. - PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption). @@ -3953,9 +3953,9 @@ Accept wildcard characters: False The Mode parameter specifies how the rule operates. Valid values are: -- Audit: The actions that the rule would have taken are written to the message tracking log, but no action that impacts message delivery is taken on the message. The GenerateIncidentReport action occurs. -- AuditAndNotify: The actions that the rule would have taken are written to the message tracking log, but no action that impacts message delivery is taken on the message. The GenerateIncidentReport and GenerateNotification actions occur. -- Enforce: All actions specified in the rule are taken. This is the default value. +- Audit: The actions that the rule would have taken are written to the message tracking log, but no action that affects message delivery is taken on the message. The GenerateIncidentReport action occurs. +- AuditAndNotify: The actions that the rule would have taken are written to the message tracking log, but no action that affects message delivery is taken on the message. The GenerateIncidentReport and GenerateNotification actions occur. +- Enforce: All actions specified in the rule are taken. This value is the default. ```yaml Type: RuleMode @@ -4051,7 +4051,7 @@ For all values except NotifyOnly, you can specify an enhanced status code and a If you use this parameter, you also need to specify a condition that looks for sensitive information types in messages by using the MessageContainsDataClassifications parameter. -This action is applicable to messages sent by internal users only. External senders will not receive notifications. +This action is applicable to messages sent by internal users only. External senders don't receive notifications. ```yaml Type: NotifySenderType @@ -4311,7 +4311,7 @@ This parameter is available only in the cloud-based service. The RecipientAddressType parameter specifies how conditions and exceptions check recipient email addresses. Valid values are: - Original: The rule checks the original address in the To field of the message. -- Resolved: The rule checks the recipient's primary SMTP email address without checking any proxy addresses. This is the default value. +- Resolved: The rule checks the recipient's primary SMTP email address without checking any proxy addresses. This value is the default. ```yaml Type: RecipientAddressType @@ -4616,7 +4616,7 @@ Accept wildcard characters: False The RuleErrorAction parameter specifies what to do if rule processing can't be completed on messages. Valid values are: -- Ignore: The message is sent anyway. This is the default value. +- Ignore: The message is sent anyway. This value is the default. - Defer: The message is deferred so the rules engine can attempt to process the message again. ```yaml @@ -4638,7 +4638,7 @@ Accept wildcard characters: False The RuleSubType parameter specifies the rule type. Valid values are: - Dlp: The rule is associated with a DLP policy. This value is meaningful only in on-premises Exchange. -- None: The rule is a regular transport rule. This is the default value. +- None: The rule is a regular transport rule. This value is the default. ```yaml Type: RuleSubType @@ -4799,7 +4799,7 @@ Accept wildcard characters: False The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are: -- Header: Only examine senders in the message headers. For example, in on-premises Exchange the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This is the default value, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1). +- Header: Only examine senders in the message headers. For example, in on-premises Exchange the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This value is the default, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1). - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). - HeaderOrEnvelope: Examine senders in the message header and the message envelope. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md index 1ce66f96fd..dbd81be6da 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md @@ -38,7 +38,7 @@ The New-UMAutoAttendant cmdlet creates one or more UM auto attendants. UM auto a After this task is completed, a UM auto attendant is created. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -191,10 +191,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -The Status parameter specifies whether the UM auto attendant being created will be enabled. Valid values are: +The Status parameter specifies whether the UM auto attendant is enabled. Valid values are: - Enabled -- Disabled (This is the default value) +- Disabled (default value) ```yaml Type: StatusEnum diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md index b90838c318..4c24b04506 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md @@ -54,7 +54,7 @@ You can also specify the following actions: After this task is completed, the cmdlet sets the parameters and the values specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -93,10 +93,10 @@ This example creates the call answering rule MyCallAnsweringRule in the mailbox - Sets the priority of the call answering rule to 2. - Creates key mappings for the call answering rule. -If the caller reaches the voice mail for the user and the status of the user is set to Busy, the caller can: +If the caller reaches the voice mail for the user and the status of the user is set to Busy, the caller can take the following actions: -- Press the 1 key and be transferred to a receptionist at extension 45678. -- Press the 2 key and the Find Me feature will be used for urgent issues and ring extension 23456 first, and then 45671. +- Press the 1 key to be transferred to a receptionist at extension 45678. +- Press the 2 key to use the Find Me feature for urgent issues and ring extension 23456 first, and then 45671. ### Example 5 ```powershell @@ -302,7 +302,9 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016 -The Priority parameter specifies the order that the call answering rule will be evaluated against other existing call answering rules. Call answering rules are processed in order of increasing priority values. The priority must be unique between all call answering rules in the UM-enabled mailbox. The priority on the call answering rule must be between 1 (highest) and 9 (lowest). The default is 9. +The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, and rules can't have the same priority value. + +A valid value is an integer from 1 (highest priority) to 9 (lowest priority). The default value is 9. ```yaml Type: Int32 diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md index ae5a236e98..ec35aabbf5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md @@ -42,7 +42,7 @@ After the new UM dial plan is created, a UM IP gateway and a Mailbox server must After this task is completed, a new UM dial plan is created. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md index 01d67f8d5e..db2ed984de 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md @@ -35,7 +35,7 @@ The New-UMHuntGroup cmdlet creates a UM hunt group in Active Directory. Running After this task is completed, a new UM hunt group is created. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md index 16e27a7fae..f9dca59459 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md @@ -36,7 +36,7 @@ A UM IP gateway has organization-wide scope and references a single physical IP This cmdlet is scheduled to be removed from Exchange Online on December 1, 2019. For more information, see this [blog post](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/New-date-for-discontinuation-of-support-for-Session-Border/ba-p/607853). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -144,11 +144,11 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016 -The IPAddressFamily parameter specifies whether the UM IP gateway will use Internet Protocol version 4 (IPv4), IPv6, or both to communicate. Valid values are: +The IPAddressFamily parameter specifies the Internet Protocol (IP) version to use. Valid values are: -- IPv4Only: The UM IP gateway will only use IPv4 to communicate. This is the default value. -- IPv6Only: The UM IP gateway will only use IPv6. -- Any: IPv6 will be used first, and then if necessary, it will fall back to IPv4. +- IPv4Only: The UM IP gateway uses only IPv4 to communicate. This value is the default. +- IPv6Only: The UM IP gateway uses only IPv6. +- Any: IPv6 is used first. If IPv6 isn't available, IPV4 is used. ```yaml Type: IPAddressFamily diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md index 66e7527fc8..996149bc7e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md @@ -34,7 +34,7 @@ The New-UMMailboxPolicy cmdlet creates a UM mailbox policy that has organization After this task is completed, a new UM mailbox policy is created. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md index cf6d755473..b0062846ba 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md @@ -81,7 +81,7 @@ The Priority parameter specifies a priority value for the policy that determines This parameter is required when you create an audit log retention policy, and you must use a unique priority value. -Any custom audit log retention policy that you create will take precedence over the default audit log retention policy. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies). +Any custom audit log retention policy that you create take precedence over the default audit log retention policy. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies). ```yaml Type: Int32 diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md index 644cb77055..840c3aec79 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md @@ -127,7 +127,7 @@ New-UnifiedGroup -DlIdentity ## DESCRIPTION Microsoft 365 Groups are group objects that are available across Microsoft 365 services. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -197,7 +197,7 @@ Accept wildcard characters: False The AccessType parameter specifies the privacy type for the Microsoft 365 Group. Valid values are: -- Public: The group content and conversations are available to everyone, and anyone can join the group without approval from a group owner. This is the default value. +- Public: The group content and conversations are available to everyone, and anyone can join the group without approval from a group owner. This value is the default. - Private: The group content and conversations are available only to members of the group, and joining the group requires approval from a group owner. You can change the privacy type at any point in the lifecycle of the group. @@ -229,7 +229,7 @@ The Alias value can contain letters, numbers and the following characters: - Periods (.) must be surrounded by other valid characters (for example, `help.desk`). - Unicode characters U+00A1 to U+00FF. -If you don't use the Alias parameter when you create a Microsoft 365 Group, the value of the DisplayName parameter is used for the Alias value. Spaces are removed, unsupported characters are converted to question marks (?), and numbers may be added to maintain the uniqueness of the Alias value. +If you don't use the Alias parameter when you create a Microsoft 365 Group, the value of the DisplayName parameter is used for the Alias value. Spaces are removed, unsupported characters are converted to question marks (?), and numbers might be added to maintain the uniqueness of the Alias value. When you create a Microsoft 365 Group without using the EmailAddresses parameter, the Alias value is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address. @@ -253,8 +253,8 @@ Accept wildcard characters: False The AlwaysSubscribeMembersToCalendarEvents switch controls the default subscription settings of new members that are added to the Microsoft 365 Group. -- If you use this switch without a value, all future members that are added to the group will have their subscriptions set to ReplyAndEvents. -- If you use this exact syntax: `-AlwaysSubscribeMembersToCalendarEvents:$false`, all future members that are added to the group will have their subscriptions set to ReplyOnly. +- If you use this switch without a value, all future members that are added to the group have their subscriptions set to ReplyAndEvents. +- If you use this exact syntax: `-AlwaysSubscribeMembersToCalendarEvents:$false`, all future members that are added to the group have their subscriptions set to ReplyOnly. Group members can change their own subscription settings, which can override your intended use of this switch. @@ -339,7 +339,7 @@ The ConvertClosedDlToPrivateGroup switch specifies whether to migrate the closed By default, this switch is always applied when migrating closed distribution groups, and is no longer required. -If the distribution group has the value Closed for the MemberDepartRestriction or MemberJoinRestriction parameters, the distribution group will always be migrated to a private Microsoft 365 Group. For open distribution groups, the migrated Microsoft 365 Group is always public, not private. +If the distribution group has the value Closed for the MemberDepartRestriction or MemberJoinRestriction parameters, the distribution group is always migrated to a private Microsoft 365 Group. For open distribution groups, the migrated Microsoft 365 Group is always public, not private. You can only use this switch with the DlIdentity parameter. @@ -475,7 +475,7 @@ The HiddenGroupMembershipEnabled switch specifies whether to hide the members of You can use this setting to help comply with regulations that require you to hide group membership from outsiders (for example, a Microsoft 365 Group that represents students enrolled in a class). -**Note**: You can't change this setting after you create the group. If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group, or vice-versa. In addition, any Microsoft 365 Groups with this setting will not be supported in sensitivity labeling policies. +**Note**: You can't change this setting after you create the group. If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group, or vice-versa. Also, any Microsoft 365 Groups with hidden group membership aren't supported in sensitivity labeling policies. ```yaml Type: SwitchParameter @@ -594,7 +594,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. Previously, if you specified a value for this parameter, a random GUID value was added and used as the Name property value for the Microsoft 365 Group (`Name_`). Now, the value of the Name property is populated by the Alias parameter value and the ExternalDirectoryObjectId property value (`_`). @@ -736,7 +736,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md index 8cf2548106..a3d3fc0bc0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md @@ -53,7 +53,7 @@ New-WebServicesVirtualDirectory [-ApplicationRoot ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -126,7 +126,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. ```yaml @@ -169,7 +169,7 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. -- $false: Digest authentication is disabled. This is the default value. +- $false: Digest authentication is disabled. This value is the default. ```yaml Type: Boolean @@ -211,7 +211,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -231,7 +231,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -252,8 +252,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -317,7 +317,7 @@ Accept wildcard characters: False The GzipLevel parameter sets the Gzip configuration for the Exchange Web Services virtual directory. Valid values are: - Off: No compression. -- Low: Static compression only. This is the default value. This value has the same result as the Off value, because Exchange Web Services content is dynamic. +- Low: Static compression only. This value is the default. This value has the same result as the Off value, because Exchange Web Services content is dynamic. - High: Static and dynamic compression. Content from Exchange Web Services is compressed if clients indicate support for Gzip compression in their requests. - Error: Identifies errors in the Gzip compression configuration. @@ -397,7 +397,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010. -The MRSProxyMaxConnections parameter specifies the maximum number of simultaneous move sessions that an instance of MRSProxy will accept. This setting accepts values from 0 to unlimited. The default value is 100. For more information about MRSProxy, see [Understanding Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)). +The MRSProxyMaxConnections parameter specifies the maximum number of simultaneous move sessions that an instance of MRSProxy accepts. This setting accepts values from 0 to unlimited. The default value is 100. For more information about MRSProxy, see [Understanding Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)). ```yaml Type: Unlimited @@ -417,7 +417,7 @@ Accept wildcard characters: False The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are: -- $true: OAuth authentication is enabled. This is the default value. +- $true: OAuth authentication is enabled. This value is the default. - $false: OAuth authentication is disabled. ```yaml @@ -538,7 +538,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -- $true: Integrated Windows authentication is enabled. This is the default value. +- $true: Integrated Windows authentication is enabled. This value is the default. - $false: Integrated Windows authentication is disabled. ```yaml @@ -559,7 +559,7 @@ Accept wildcard characters: False The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are: -- $true: WS-Security authentication is enabled. This is the default value. +- $true: WS-Security authentication is enabled. This value is the default. - $false: WS-Security authentication is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md index 75b1a7057a..af13148098 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md @@ -65,7 +65,7 @@ organizational unit name - Abbreviation: OU1 to OU4 - Maximum character length: 32 -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md index d4ecdb9cff..d111fb6995 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md @@ -29,7 +29,7 @@ Preview-QuarantineMessage -Identity ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md b/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md index 7235d9cac0..4ff9812e91 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md @@ -33,9 +33,9 @@ When a message queue is drained, the active messages in the queues on the source - Only active messages are drained. Shadow queues aren't drained. - Messages in the poison message queue aren't drained. -- The source server won't accept new messages while the queues are drained. +- The source server doesn't accept new messages while the queues are drained. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md index 4e44347bf6..211696a797 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md @@ -78,7 +78,7 @@ Release-QuarantineMessage -Identity ## DESCRIPTION Consider the following scenario: john@gmail.com sends a message to faith@contoso.com and john@subsidiary.contoso.com. Gmail bifurcates this message into two copies that are both routed to quarantine as phishing in Microsoft. An admin releases both of these messages to admin@contoso.com. The first released message that reaches the admin mailbox is delivered. The second released message is identified as duplicate delivery and is skipped. Message are identified as duplicates if they have the same message ID and received time. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -228,7 +228,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection -The AllowSender switch specifies that all future messages from the sender won't be quarantined. You don't need to specify a value with this switch. +The AllowSender switch specifies that all future messages from the sender isn't quarantined. You don't need to specify a value with this switch. If the message was quarantined because of a transport rule or blocked sender, messages from the sender can still be blocked in the future. diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md index ca71f92469..590b14b804 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md @@ -64,9 +64,9 @@ Remove-ADPermission [[-Identity] ] -Instance ## DESCRIPTION For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md index 63652b6d44..4d52a5ac4c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md @@ -30,7 +30,7 @@ Remove-AcceptedDomain [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md index 7e6cbd67b6..53d507564f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md @@ -13,7 +13,7 @@ title: Remove-ActiveSyncDevice # Remove-ActiveSyncDevice ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-ActiveSyncDevice cmdlet to remove mobile device partnerships that identify the devices that are configured to synchronize with user mailboxes. @@ -34,7 +34,7 @@ Remove-ActiveSyncDevice [-Identity] ## DESCRIPTION The Remove-ActiveSyncDevice cmdlet is useful for removing mobile devices that no longer synchronize successfully with the server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md index bbd927ed8e..252701126d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md @@ -13,7 +13,7 @@ title: Remove-ActiveSyncDeviceAccessRule # Remove-ActiveSyncDeviceAccessRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-ActiveSyncDeviceAccessRule cmdlet to remove any existing device access rule. @@ -32,7 +32,7 @@ Remove-ActiveSyncDeviceAccessRule [-Identity] ## DESCRIPTION The Remove-ActiveSyncDeviceClass cmdlet cleans up the list of devices that are associated with your organization. Mobile phones and devices that are inactive or have been remote wiped are removed from the list and the Microsoft Exchange ActiveSync process regenerates the list with the current mobile phones and devices. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md index 2841e91d45..529397252e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md @@ -13,7 +13,7 @@ title: Remove-ActiveSyncMailboxPolicy # Remove-ActiveSyncMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-ActiveSyncMailboxPolicy cmdlet to remove mobile device mailbox policies. @@ -35,7 +35,7 @@ Remove-ActiveSyncMailboxPolicy [-Identity] ## DESCRIPTION A mobile device mailbox policy is a group of settings that specifies how mobile phones connect to Exchange. Exchange supports multiple mobile device mailbox policies. If any users are assigned to the policy when you attempt to remove it, the command fails. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md index 5a164c4717..781217db58 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md @@ -32,7 +32,7 @@ Remove-ActiveSyncVirtualDirectory [-Identity] ## DESCRIPTION When the Exchange ActiveSync virtual directory is removed from a specified server and website, the virtual directory is also removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md index d68f6ae1c5..e878164f2d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md @@ -13,7 +13,7 @@ title: Remove-AddressBookPolicy # Remove-AddressBookPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-AddressBookPolicy cmdlet to delete an address book policy. You can't remove the address book policy if it's still assigned to a user's mailbox. @@ -36,7 +36,7 @@ You can't delete an address book policy if it's assigned to a user. To determine `Get-Mailbox -ResultSize unlimited -Filter "AddressBookPolicy -eq '$((Get-AddressBookPolicy "Murchison's Class").DistinguishedName)'"` -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md index c74e1d44d6..02ce9abe28 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md @@ -13,7 +13,7 @@ title: Remove-AddressList # Remove-AddressList ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-AddressList cmdlet to remove existing address lists. @@ -38,7 +38,7 @@ You can use the Remove-AddressList cmdlet with the Get-AddressList cmdlet in the - Use the Get-AddressList cmdlet to get address list information, and then pipe the output to the Format-List cmdlet to get the GUID, distinguished name (DN), or path and name of an existing address list. - Use the Get-AddressList cmdlet to get a specific existing address list, and then pipe the output directly to the Remove-AddressList 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md index 62b3f8de89..4c0519e57b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md @@ -30,7 +30,7 @@ Remove-AntiPhishPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md index 2f16d1e2f0..6977beb97b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md @@ -29,7 +29,7 @@ Remove-AntiPhishRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-App.md b/exchange/exchange-ps/ExchangePowerShell/Remove-App.md index 87256dfcde..1c77501a84 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-App.md @@ -13,7 +13,7 @@ title: Remove-App # Remove-App ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-App cmdlet to uninstall an app. @@ -34,9 +34,9 @@ Remove-App [-Identity] ``` ## DESCRIPTION -The Remove-App cmdlet requires that the specified app has already been installed (for example, that the app has been installed with the New-App cmdlet. Apps installed by default can't be uninstalled, but they can be disabled. +The Remove-App cmdlet requires that the specified app has already been installed (for example, that the app is installed with the New-App cmdlet. Apps installed by default can't be uninstalled, but they can be disabled. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md index 9434a09c97..484f3eeee3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md @@ -15,7 +15,7 @@ title: Remove-ApplicationAccessPolicy ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Remove-ApplicationAccessPolicy cmdlet to remove application access policies. These changes may take up to 30 minutes to go live. +Use the Remove-ApplicationAccessPolicy cmdlet to remove application access policies. These changes might take up to 30 minutes to go live. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -29,7 +29,7 @@ Remove-ApplicationAccessPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md index 04c48fbf3e..42edc677b5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md @@ -30,7 +30,7 @@ Remove-AuthRedirect [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md index 95ab8e8b0d..a611561cbd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md @@ -30,7 +30,7 @@ Remove-AuthServer [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md index 1d83ba7551..2a4e144071 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md @@ -13,7 +13,7 @@ title: Remove-AuthenticationPolicy # Remove-AuthenticationPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-AuthenticationPolicy cmdlet to remove authentication policies from your organization. @@ -31,7 +31,7 @@ Remove-AuthenticationPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md index f87faad103..32c9ff50f0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md @@ -30,7 +30,7 @@ Remove-AutodiscoverVirtualDirectory [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md index 5f3792e4d4..3f035835bd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md @@ -13,7 +13,7 @@ title: Remove-AvailabilityAddressSpace # Remove-AvailabilityAddressSpace ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-AvailabilityAddressSpace cmdlet to remove existing availability address space objects and the associated credentials that were used to share free/busy data across Exchange organizations. @@ -32,7 +32,7 @@ Remove-AvailabilityAddressSpace [-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md index 66bd5aaed6..24ba21761f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md @@ -32,7 +32,7 @@ Remove-AvailabilityReportOutage [-SiteName] -ReportDate ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md index 35eb04fb6e..b89de490a5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md @@ -26,7 +26,7 @@ Remove-BlockedConnector -ConnectorId [-Reason ] [ ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md b/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md index 23dd9a41c8..37af6e5b5e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md @@ -13,7 +13,7 @@ title: Remove-CalendarEvents # Remove-CalendarEvents ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-CalendarEvents cmdlet to cancel future meetings in user or resource mailboxes. Cancelling future meetings removes them from attendee and resource calendars (for example, you're going to remove the mailbox, or the user is going on a leave of absence). @@ -35,7 +35,7 @@ Remove-CalendarEvents [-Identity] -QueryWindowInDays ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md index 780d8f60b7..81d804fa9c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md @@ -16,7 +16,7 @@ title: Remove-ClientAccessRule > [!NOTE] > Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). -This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-ClientAccessRule cmdlet to remove client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection. @@ -35,7 +35,7 @@ Remove-ClientAccessRule [-Identity] ## DESCRIPTION Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md index 3a13bfbf98..22edb5ed6a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md @@ -30,7 +30,7 @@ Remove-ComplianceRetentionEventType -Identity ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md index 882cb412ba..523371b286 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md @@ -13,7 +13,7 @@ title: Remove-ComplianceSearch # Remove-ComplianceSearch ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-ComplianceSearch cmdlet to remove compliance searches from Exchange Server 2016 and from the Microsoft Purview compliance portal. The searches must be stopped or completed. @@ -29,7 +29,7 @@ Remove-ComplianceSearch [-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). In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md index 3ae844829d..8598c8c44c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md @@ -40,7 +40,7 @@ Remove-ContentFilterPhrase [-Phrase ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md index 80df1068f7..11847d2a17 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md @@ -15,7 +15,7 @@ title: Remove-DataClassification ## SYNOPSIS This cmdlet is functional only in on-premises Exchange. -In Exchange Online, this cmdlet has been replaced by the [Remove-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/remove-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. +In Exchange Online, this cmdlet is replaced by the [Remove-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/remove-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. Use the Remove-DataClassification cmdlet to remove data classification rules that use document fingerprints. You can't use this cmdlet to remove built-in data classification rules. @@ -34,7 +34,7 @@ Remove-DataClassification [-Identity] ## DESCRIPTION Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md index eee46900a9..d80ad23b93 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md @@ -30,7 +30,7 @@ Remove-DatabaseAvailabilityGroup [-Identity] ## DESCRIPTION Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md index fe40250ea6..cf0c056d74 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md @@ -13,7 +13,7 @@ title: Remove-DistributionGroup # Remove-DistributionGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-DistributionGroup cmdlet to remove distribution groups and mail-enabled security groups. @@ -32,7 +32,7 @@ Remove-DistributionGroup [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md index 9d8ad97a3d..4e4bc7777a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md @@ -13,7 +13,7 @@ title: Remove-DistributionGroupMember # Remove-DistributionGroupMember ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-DistributionGroupMember cmdlet to remove a single member from distribution groups or mail-enabled security groups. To replace all members, use the Update-DistributionGroupMember cmdlet. @@ -34,7 +34,7 @@ Remove-DistributionGroupMember [-Identity] ## DESCRIPTION You can't use the Remove-DistributionGroupMember cmdlet to remove the member of a dynamic distribution group. A dynamic distribution group's membership is calculated from query 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md index 316c9cd1a2..7f63c45109 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md @@ -13,7 +13,7 @@ title: Remove-DlpPolicy # Remove-DlpPolicy ## SYNOPSIS -**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Remove-DlpCompliancePolicy and Remove-DlpComplianceRule cmdlets instead. +**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Remove-DlpCompliancePolicy and Remove-DlpComplianceRule cmdlets instead. This cmdlet is functional only in on-premises Exchange. @@ -32,7 +32,7 @@ Remove-DlpPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md index 1a5970540d..bce7076d60 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md @@ -30,7 +30,7 @@ Remove-DlpPolicyTemplate [[-Identity] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md index 34d08a77f7..2070951572 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md @@ -13,7 +13,7 @@ title: Remove-DynamicDistributionGroup # Remove-DynamicDistributionGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-DynamicDistributionGroup cmdlet to delete dynamic distribution groups. @@ -31,7 +31,7 @@ Remove-DynamicDistributionGroup [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md index 3581bd35c2..5c64c8e9df 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md @@ -33,7 +33,7 @@ Remove-EOPProtectionPolicyRule [-Identity] ## DESCRIPTION For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md index 5cecafe529..f38307da67 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md @@ -32,7 +32,7 @@ Remove-EcpVirtualDirectory [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md index b5b4a410da..ab2e694756 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md @@ -38,7 +38,7 @@ When you remove an Edge Subscription, the following changes are made: - The Edge Transport server is removed from the list of source servers for any Send connector. - If the Edge Transport server is the only source server for any Send connector, the Send connector is removed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -116,7 +116,7 @@ Accept wildcard characters: False The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -If you don't use this switch, the command will inform you that the removal of the replicated recipient data from AD LDS can take a long time and will give you the option to cancel the operation. +If you don't use this switch, the command informs you that the removal of the replicated recipient data from AD LDS can take a long time and gives you the option to cancel the operation. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md index c69eced8d4..659c486619 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md @@ -13,7 +13,7 @@ title: Remove-EmailAddressPolicy # Remove-EmailAddressPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-EmailAddressPolicy cmdlet to remove existing email address policies and update the affected recipients. In Exchange Online, email address policies are available only for Microsoft 365 Groups. @@ -30,7 +30,7 @@ Remove-EmailAddressPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md index 2d4b35d81b..759c87b53a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md @@ -47,7 +47,7 @@ There are many factors to consider when you configure certificates for Transport Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md index d8fa30e9df..cca2ee0b20 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md @@ -30,7 +30,7 @@ Remove-ExoPhishSimOverrideRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md index 38d2d1fda7..78b46cde3f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md @@ -30,7 +30,7 @@ Remove-ExoSecOpsOverrideRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md index 0269e862b1..a902c0d79e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md @@ -37,7 +37,7 @@ Remove-FederatedDomain [[-Identity] ] -DomainName ## DESCRIPTION Federation trusts are set up with Microsoft Federation Gateway to enable calendar sharing and free/busy sharing with external Exchange organizations or individuals. The Remove-FederationTrust cmdlet removes a federation trust. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md index cca67c8bde..ec31d4ab73 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md @@ -32,9 +32,9 @@ Remove-ForeignConnector [-Identity] ## DESCRIPTION The Remove-ForeignConnector cmdlet deletes the object and the configuration information for a Foreign connector. -Although a Foreign connector is configured on a local Mailbox server, if you delete a Foreign connector, you may affect mail flow throughout the organization. +Although a Foreign connector is configured on a local Mailbox server, if you delete a Foreign connector, you might affect mail flow throughout the 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/Remove-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md index 24d6c5a6f3..aa81c3aac7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md @@ -13,7 +13,7 @@ title: Remove-GlobalAddressList # Remove-GlobalAddressList ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-GlobalAddressList cmdlet to remove an existing global address list (GAL). @@ -32,7 +32,7 @@ Remove-GlobalAddressList [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md index c8e627d480..a2657bb1a4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md @@ -15,7 +15,7 @@ title: Remove-GlobalMonitoringOverride ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Remove-GlobalMonitoringOverride cmdlet to remove a managed availability global override that has been configured for a probe, monitor or responder. +Use the Remove-GlobalMonitoringOverride cmdlet to remove a managed availability global override that is configured for a probe, monitor or responder. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -32,7 +32,7 @@ Remove-GlobalMonitoringOverride [-Identity] -ItemType ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md index ccbdb0fe1d..0d328a1aaa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md @@ -30,7 +30,7 @@ Remove-HostedOutboundSpamFilterPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md index 678ece27dd..612fd6ffd0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md @@ -13,7 +13,7 @@ title: Remove-HybridConfiguration # Remove-HybridConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-HybridConfiguration cmdlet to delete the HybridConfigurationActive Directory object for your on-premises Exchange organization. @@ -29,9 +29,9 @@ Remove-HybridConfiguration [-Confirm] ``` ## DESCRIPTION -Removing a HybridConfiguration object should typically only be performed in circumstances where the hybrid deployment state is corrupt and under the direction of Microsoft Customer Service and Support. After removing the HybridConfiguration object, your existing hybrid deployment configuration settings aren't disabled or removed. However, when the Hybrid Configuration wizard is run again after removing the HybridConfiguration object, the wizard won't have a hybrid configuration reference point for your existing feature settings. As a result, it will automatically create a HybridConfiguration object and record the new hybrid deployment configuration feature values defined in the wizard. The feature settings associated with the hybrid deployment, such as organization relationship or Send and Receive connector parameters, which were configured with the HybridConfiguration object that's removed, aren't removed or modified until the Hybrid Configuration wizard is run again. +Removing a HybridConfiguration object should typically only be performed in circumstances where the hybrid deployment state is corrupt and under the direction of Microsoft Customer Service and Support. After removing the HybridConfiguration object, your existing hybrid deployment configuration settings aren't disabled or removed. However, when the Hybrid Configuration wizard is run again after removing the HybridConfiguration object, the wizard don't have a hybrid configuration reference point for your existing feature settings. As a result, it automatically creates a HybridConfiguration object and record the new hybrid deployment configuration feature values defined in the wizard. The feature settings associated with the hybrid deployment, such as organization relationship or Send and Receive connector parameters, which were configured with the HybridConfiguration object that's removed, aren't removed or modified until the Hybrid Configuration wizard is run again. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md index ab3d6ef257..b75c6d0852 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md @@ -31,7 +31,7 @@ Remove-InboundConnector [-Identity] ## DESCRIPTION Inbound connectors accept email messages from remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md index 7fa5cb1815..c4f3397c11 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md @@ -13,7 +13,7 @@ title: Remove-InboxRule # Remove-InboxRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-InboxRule cmdlet to remove an Inbox rule. @@ -35,7 +35,7 @@ Remove-InboxRule [-Identity] ## DESCRIPTION When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -143,7 +143,7 @@ Accept wildcard characters: False The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet. +A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md index 63bd0b6700..426008cadc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md @@ -13,7 +13,7 @@ title: Remove-IntraOrganizationConnector # Remove-IntraOrganizationConnector ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-IntraOrganizationConnector cmdlet to remove existing Intra-Organization connectors. @@ -34,7 +34,7 @@ Intra-Organizational connectors enable features and services between divisions i The Remove-IntraOrganizationConnector cmdlet removes the connector objects. To stop feature or service connectivity without removing the connector object, run the command: `Set-IntraOrganizationConnector -Enabled $false`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md index 751b3b50ad..58e379d9f0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md @@ -13,7 +13,7 @@ title: Remove-JournalRule # Remove-JournalRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-JournalRule cmdlet to remove an existing journal rule. @@ -32,7 +32,7 @@ Remove-JournalRule [-Identity] ## DESCRIPTION The Remove-JournalRule cmdlet removes the specified journal rule from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md index a45da6931e..41677f24f9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md @@ -13,7 +13,7 @@ title: Remove-MailContact # Remove-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 Remove-MailContact cmdlet to delete existing mail contacts. @@ -31,7 +31,7 @@ Remove-MailContact [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md index 65fa8bfa18..550a45c9ff 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md @@ -13,7 +13,7 @@ title: Remove-MailUser # Remove-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 Remove-MailUser cmdlet to remove existing mail users. @@ -33,7 +33,7 @@ Remove-MailUser [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md index 3aeeb163aa..0765f501d9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md @@ -13,7 +13,7 @@ title: Remove-Mailbox # Remove-Mailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-Mailbox cmdlet to delete mailboxes and the associated user accounts. @@ -81,7 +81,7 @@ Use the Identity and Permanent parameters to disconnect the mailbox from the use Use the Disable-Mailbox cmdlet to disconnect the mailbox from the user account, but keep the user account. The mailbox is retained until the deleted mailbox retention period for the database or the mailbox expires, and then the mailbox is permanently deleted (purged). Or, you can immediately purge the disconnected mailbox by using the Database and StoreMailboxIdentity parameters on the Remove-Mailbox 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 @@ -106,7 +106,7 @@ $Temp = Get-Mailbox | Where {$_.DisplayName -eq 'John Rodman'} Remove-Mailbox -Database Server01\Database01 -StoreMailboxIdentity $Temp.MailboxGuid ``` -In on-premises Exchange, this example removes John Rodman's mailbox from the mailbox database after the mailbox has been disconnected from the user account. The example uses the Get-Mailbox cmdlet to retrieve the mailbox GUID value of the disconnected mailbox, which is required by the StoreMailboxIdentity parameter. +In on-premises Exchange, this example removes John Rodman's mailbox from the mailbox database after the mailbox is disconnected from the user account. The example uses the Get-Mailbox cmdlet to retrieve the mailbox GUID value of the disconnected mailbox, which is required by the StoreMailboxIdentity parameter. ### Example 4 ```powershell @@ -409,7 +409,7 @@ This parameter is available only in on-premises Exchange. The Permanent parameter specifies whether to permanently delete the mailbox from the mailbox database. Valid values are: - $true: The mailbox is immediately and permanently deleted (purged). You can't reconnect or restore the mailbox. -- $false: The mailbox disabled and retained until the deleted mailbox retention period expires. You can reconnect or restore the mailbox until the deleted mailbox retention period expires. This is the default value. +- $false: The mailbox disabled and retained until the deleted mailbox retention period expires. You can reconnect or restore the mailbox until the deleted mailbox retention period expires. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md index 943286d523..25db72c47c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md @@ -34,7 +34,7 @@ If the mailbox database has a database copy, the Remove-MailboxDatabase cmdlet a The Remove-MailboxDatabase cmdlet removes only the database object from Active Directory. It doesn't remove the physical database files. You must remove the database files manually after you run the Remove-MailboxDatabase 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md index e6b2cbbd4e..04f4669b42 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md @@ -33,11 +33,11 @@ Remove-MailboxDatabaseCopy [-Identity] To use the Remove-MailboxDatabaseCopy cmdlet to remove a mailbox database copy, the following criteria must be met: - The database availability group (DAG) hosting the mailbox database must have quorum and all cluster and network functions must be healthy. -- If you're removing the last passive copy of the database, continuous replication circular logging (CRCL) must not be enabled for the specified mailbox database. If CRCL is enabled, you must first disable it. After the mailbox database copy has been removed, circular logging can be enabled. After enabling circular logging for a non-replicated mailbox database, JET circular logging is used instead of CRCL. If you aren't removing the last passive copy of a database, CRCL can remain enabled. +- If you're removing the last passive copy of the database, continuous replication circular logging (CRCL) must not be enabled for the specified mailbox database. If CRCL is enabled, you must first disable it. After the mailbox database copy is removed, circular logging can be enabled. After enabling circular logging for a non-replicated mailbox database, JET circular logging is used instead of CRCL. If you aren't removing the last passive copy of a database, CRCL can remain enabled. You can't use this cmdlet to remove the active copy of a mailbox database. To remove the active copy of a mailbox database, you must first remove all passive copies of the database and then use the Remove-MailboxDatabase cmdlet to remove the active copy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). Running this cmdlet removes the mailbox database copy configuration, but doesn't delete the database copy's files. If necessary, you can manually delete those files. diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md index 9e5d6dcdcb..f4371e2ec3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md @@ -49,7 +49,7 @@ The parameter set that requires the Identity parameter allows you to remove a fu The parameter set that requires the RequestGuid and RequestQueue parameters is used for Microsoft Exchange Mailbox Replication service (MRS) debugging purposes only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md index ba7741eb85..fd615eb7b3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md @@ -13,7 +13,7 @@ title: Remove-MailboxFolderPermission # Remove-MailboxFolderPermission ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-MailboxFolderPermission cmdlet to remove folder-level permissions for users in mailboxes. @@ -53,7 +53,7 @@ Remove-MailboxFolderPermission [-Identity] [-ResetDel ## DESCRIPTION You can't use this cmdlet to selectively remove permissions from a user on a mailbox folder. The cmdlet removes all permissions that are assigned to the user on the specified folder. To modify the permissions that are assigned to the user on a mailbox folder, use the Set-MailboxFolderPermission 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 @@ -69,7 +69,7 @@ This example removes John's permissions to the Training folder in Kim's mailbox. Remove-MailboxFolderPermission -Identity kim@contoso.com:\Calendar -ResetDelegateUserCollection ``` -This example will clear any corrupted delegate information from Kim's mailbox. +This example clears any corrupted delegate information from Kim's mailbox. ## PARAMETERS @@ -205,7 +205,7 @@ Accept wildcard characters: False The ResetDelegateUserCollection switch forces the removal of the LocalFreeBusy or the PR_FREEBUSY_ENTRYIDs files in case of corruption. You don't need to specify a value with this switch. -Use this switch if you encounter problems trying add, change, or remove delegate permissions. Using this switch deletes those files and downgrades any existing delegates to Editor permissions. You'll need to grant delegate permissions again using `-SharingPermissionFlag Delegate`. +Use this switch if you encounter problems trying add, change, or remove delegate permissions. Using this switch deletes those files and downgrades any existing delegates to Editor permissions. You need to grant delegate permissions again using `-SharingPermissionFlag Delegate`. When you use this switch, the value of Identity should be the user's primary calendar folder (for example, `kim@contoso.com:\Calendar`). @@ -230,7 +230,7 @@ This parameter is available only in the cloud-based service. The SendNotificationToUser parameter specifies whether to send a notification to the user when you remove their calendar permissions. Valid values are: - $true: A notification is sent. -- $false: No notification is sent. This is the default value. +- $false: No notification is sent. This value is the default. This parameter only applies to calendar folders. diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md index 1c949e5443..ff233167dc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md @@ -30,7 +30,7 @@ Remove-MailboxIRMAccess [-Identity] -User [!NOTE] > This cmdlet works only for delegates who already have Full Access permission to the mailbox. For more information, see [Manage permissions for recipients in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-permissions-for-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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md index 88ffe57767..4b0ccfcb1b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md @@ -13,7 +13,7 @@ title: Remove-MailboxImportRequest # Remove-MailboxImportRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-MailboxImportRequest cmdlet to remove fully or partially completed import requests. Completed import requests aren't automatically cleared. Requests need to be removed by using the Remove-MailboxImportRequest cmdlet. Multiple import requests can exist against the same mailbox if you provide a distinct import request name. @@ -21,7 +21,7 @@ NOTE: This cmdlet is no longer supported in Exchange Online. To import a .pst fi This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). -Removing a partially completed import request removes the request from the Microsoft Exchange Mailbox Replication service (MRS) job queue. Any import progress that was made until the removal won't be reverted. +Removing a partially completed import request removes the request from the Microsoft Exchange Mailbox Replication service (MRS) job queue. Any import progress made before the removal isn't reverted. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -51,7 +51,7 @@ The parameter set that requires the Identity parameter allows you to remove a fu The parameter set that requires the RequestGuid and RequestQueue parameters is used for MRS debugging purposes only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md index 64516015a0..49d7dc1c4e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md @@ -13,7 +13,7 @@ title: Remove-MailboxPermission # Remove-MailboxPermission ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-MailboxPermission cmdlet to remove permissions from a user's mailbox or from an Exchange Server 2016, Exchange Server 2019 or Exchange Online mail user. @@ -87,7 +87,7 @@ Remove-MailboxPermission [-Identity] [-ResetDefault] ## DESCRIPTION The Remove-MailboxPermission cmdlet allows you to remove permissions from a user's mailbox, for example, removing full access to another user'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/Remove-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md index 714bff2d94..0f77f23c1c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md @@ -30,9 +30,9 @@ Remove-MailboxRepairRequest [-Identity] ``` ## DESCRIPTION -You can run the Remove-MailboxRepairRequest cmdlet to remove all mailbox repair requests for a specific database, for a group of related mailbox repair requests, or for a specific mailbox repair request. Mailbox repair requests are identified by a complex GUID with the following format: `DatabaseGuid\RequestGuid\JobGuid`. The DatabaseGuid identifies the mailbox database where the mailbox being repaired is located. The RequestGuid identifies related requests that may contain more than one job if the request runs more than one task or targets more than one mailbox. The JobGuid identifies a unique job. See the examples to remove all requests on a mailbox database, remove a group of related requests that share the same RequestGuid, or remove a specific request by specifying the complete `DatabaseGuid\RequestGuid\JobGuid` value. +You can run the Remove-MailboxRepairRequest cmdlet to remove all mailbox repair requests for a specific database, for a group of related mailbox repair requests, or for a specific mailbox repair request. Mailbox repair requests are identified by a complex GUID with the following format: `DatabaseGuid\RequestGuid\JobGuid`. The DatabaseGuid identifies the mailbox database where the mailbox being repaired is located. The RequestGuid identifies related requests that might contain more than one job if the request runs more than one task or targets more than one mailbox. The JobGuid identifies a unique job. See the examples to remove all requests on a mailbox database, remove a group of related requests that share the same RequestGuid, or remove a specific request by specifying the complete `DatabaseGuid\RequestGuid\JobGuid` value. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md index 9a86971144..3b1bd245ff 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md @@ -13,7 +13,7 @@ title: Remove-MailboxRestoreRequest # Remove-MailboxRestoreRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-MailboxRestoreRequest cmdlet to remove fully or partially completed restore requests. @@ -45,7 +45,7 @@ The parameter set that requires the Identity parameter allows you to remove a fu The parameter set that requires the RequestGuid and RequestQueue parameters is used for Microsoft Exchange Mailbox Replication service (MRS) debugging purposes only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md index 0c67e70f83..90b6f263d9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md @@ -13,7 +13,7 @@ title: Remove-MailboxSearch # Remove-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 Remove-MailboxSearch cmdlet to remove a mailbox search. @@ -34,7 +34,7 @@ Remove-MailboxSearch [-Identity] ## DESCRIPTION In on-premises Exchange, mailbox searches are used for In-Place eDiscovery and In-Place Hold. You can't remove an In-Place Hold without first disabling the hold. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md index c8bd7e9dd0..df48043dd3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md @@ -13,7 +13,7 @@ title: Remove-MailboxUserConfiguration # Remove-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 Remove-MailboxUserConfiguration cmdlet to remove user configuration items from mailboxes. Typically, after you delete a user configuration item, it's automatically recreated the next time the user uses that feature in their mailbox. @@ -30,7 +30,7 @@ Remove-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/Remove-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md index 9ef8eb5d88..eea5a20e1b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md @@ -13,7 +13,7 @@ title: Remove-MalwareFilterRule # Remove-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 Remove-MalwareFilterRule cmdlet to remove malware filter rules from your organization. @@ -30,7 +30,7 @@ Remove-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/Remove-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedContentSettings.md index 15b27f5dc3..ece20ad599 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedContentSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedContentSettings.md @@ -32,7 +32,7 @@ Remove-ManagedContentSettings [-Identity] ## DESCRIPTION When managed content settings are removed from a managed folder, the folder effectively ceases to be a managed folder, and folder contents are no longer under messaging records management (MRM). Removing managed content settings disables any retention and journaling policies for the folder. It doesn't affect whether you can move, delete, or rename the folder, or whether the folder has a quota or policy statement that's displayed in Microsoft Outlook or Microsoft Office Outlook Web App. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md index 47dd5e5805..3c1c9a65e9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md @@ -32,7 +32,7 @@ Remove-ManagedFolder [-Identity] ## DESCRIPTION The Remove-ManagedFolder cmdlet accepts a managed folder object or a mailbox identity 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/Remove-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolderMailboxPolicy.md index 4a3882a8e3..67fa7e4aa1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolderMailboxPolicy.md @@ -31,9 +31,9 @@ Remove-ManagedFolderMailboxPolicy [-Identity] ``` ## DESCRIPTION -If you remove a managed folder mailbox policy that's applied to users' mailboxes, the affected mailboxes may no longer have retention settings. Therefore, before using this cmdlet to remove a policy, you should determine if the managed folder mailbox policy is applied to any users, and apply another policy to those users. +If you remove a managed folder mailbox policy that's applied to users' mailboxes, the affected mailboxes might no longer have retention settings. Therefore, before using this cmdlet to remove a policy, you should determine if the managed folder mailbox policy is applied to any users, and apply another policy to those users. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md index c55c9255c5..39277631d6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md @@ -13,7 +13,7 @@ title: Remove-ManagementRole # Remove-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 Remove-ManagementRole cmdlet to remove custom management roles that you don't need anymore. @@ -35,7 +35,7 @@ Remove-ManagementRole [-Identity] ## DESCRIPTION You need to remove all the management role assignments from a role before you delete it. If the role is the parent of child roles, the child roles must be removed before you remove the parent role, or you must use the Recurse parameter when you remove the parent role. You can only remove custom roles. Built-in roles, such as the Mail Recipients role, can't be removed. For more information about how to remove a custom role, see [Remove a role](https://learn.microsoft.com/exchange/remove-a-role-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 @@ -67,7 +67,7 @@ This example uses the Get-ManagementRole cmdlet to get a list of roles that cont Remove-ManagementRole "In-house scripts" -UnScopedTopLevel ``` -In on-premises Exchange, this example removes the In-house scripts unscoped top-level management role. Because this is an unscoped top-level role, the UnScopedTopLevel switch must be used. Note that the UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default. +In on-premises Exchange, this example removes the In-house scripts unscoped top-level management role. Because this is an unscoped top-level role, the UnScopedTopLevel switch must be used. The UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default. For more information about unscoped top-level management roles, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md index 41c64180c4..4a4e87c6c9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md @@ -13,7 +13,7 @@ title: Remove-ManagementRoleAssignment # Remove-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 Remove-ManagementRoleAssignment cmdlet to remove management role assignments. @@ -33,7 +33,7 @@ Remove-ManagementRoleAssignment [-Identity] ## DESCRIPTION When you remove a role assignment, the management role group, management role assignment, user, or universal security group (USG) that was assigned the associated role can no longer access the cmdlets or parameters made available by the role. 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/Remove-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md index fa22bd85fe..def11dc9d1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md @@ -13,7 +13,7 @@ title: Remove-ManagementRoleEntry # Remove-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 Remove-ManagementRoleEntry cmdlet to remove existing management role entries. @@ -35,7 +35,7 @@ The Remove-ManagementRoleEntry cmdlet removes existing role entries. However, yo 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/Remove-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md index da3e698805..d21c285668 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md @@ -13,7 +13,7 @@ title: Remove-ManagementScope # Remove-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 Remove-ManagementScope cmdlet to remove an existing management scope. @@ -33,7 +33,7 @@ Remove-ManagementScope [-Identity] ## DESCRIPTION You can't remove a management scope if it's associated with a management role assignment. Use the Get-ManagementScope cmdlet to retrieve a list of orphaned scopes. 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/Remove-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md index 743e25116c..b5634346e1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md @@ -30,7 +30,7 @@ Remove-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/Remove-Message.md b/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md index f61b55fd1a..462f8cf196 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md @@ -42,7 +42,7 @@ Remove-Message [-Identity] ## DESCRIPTION A message being transmitted to multiple recipients might be located in multiple queues. If you specify an Identity parameter, the message is removed from a single queue if that identity matches only a single message. If the identity matches more than one message, you receive an error. To remove a message from more than one queue in a single operation, you must use the Filter parameter. If you try to remove a message currently being delivered, the message status changes to PendingDelete. Message delivery isn't interrupted, but if the delivery fails and causes the message to re-enter the queue, it's then removed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md index 488a7efb2d..3ad8456773 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md @@ -13,7 +13,7 @@ title: Remove-MessageClassification # Remove-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 Remove-MessageClassification cmdlet to delete an existing message classification instance from your organization. @@ -30,7 +30,7 @@ Remove-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/Remove-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md index 1c7dc32bba..621ad34cae 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md @@ -13,9 +13,9 @@ title: Remove-MigrationBatch # Remove-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 Remove-MigrationBatch cmdlet to delete a migration batch that either isn't running or has been completed. If necessary, you can run the Get-MigrationBatch cmdlet to determine the status of a migration batch before you remove it. +Use the Remove-MigrationBatch cmdlet to delete a migration batch that either isn't running or is completed. If necessary, you can run the Get-MigrationBatch cmdlet to determine the status of a migration batch before you remove it. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -36,7 +36,7 @@ The Remove-MigrationBatch cmdlet removes a migration batch. All subscriptions ar If you use the Force switch with this cmdlet, the individual user requests and subscriptions that were part of the removed migration batch aren't removed. You need to remove the individual migration user requests with the command: `Remove-MigrationUser -Force`. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md index a5d4823b42..b550b89413 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md @@ -13,7 +13,7 @@ title: Remove-MigrationEndpoint # Remove-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 Remove-MigrationEndpoint cmdlet to remove existing migration endpoints for source or destination servers for cutover or staged Exchange migrations, IMAP migrations and remote moves. @@ -35,7 +35,7 @@ Use the Remove-MigrationEndpoint cmdlet to remove an existing migration endpoint For more information about migration endpoints, see [Set-MigrationEndpoint](https://learn.microsoft.com/powershell/module/exchangepowershell/set-migrationendpoint) and [New-MigrationEndpoint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-migrationendpoint). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md index 6b633b250b..21265c4d48 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md @@ -13,7 +13,7 @@ title: Remove-MigrationUser # Remove-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 Remove-MigrationUser cmdlet to remove a migration user from a batch. @@ -32,7 +32,7 @@ Remove-MigrationUser [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md index a77fdb44ad..d47d20a69c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md @@ -13,7 +13,7 @@ title: Remove-MobileDevice # Remove-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 Remove-MobileDevice cmdlet to remove mobile device partnerships that identify the devices that are configured to synchronize with user mailboxes. @@ -32,7 +32,7 @@ Remove-MobileDevice [-Identity] ## DESCRIPTION The Remove-MobileDevice cmdlet is useful for removing mobile devices that no longer synchronize successfully with the server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md index ca89c8284e..978c5c882f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md @@ -13,7 +13,7 @@ title: Remove-MobileDeviceMailboxPolicy # Remove-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 Remove-MobileDeviceMailboxPolicy cmdlet to remove mobile device mailbox policies from Exchange servers. @@ -33,7 +33,7 @@ Remove-MobileDeviceMailboxPolicy [-Identity] ## DESCRIPTION A Mobile Device mailbox policy is a group of settings that specifies how mobile phones connect to Exchange. Exchange supports multiple mobile device mailbox policies. The Remove-MobileDeviceMailboxPolicy cmdlet removes a specific mobile device mailbox policy. If any users are assigned to the policy when you remove it, the Remove-MobileDeviceMailboxPolicy cmdlet fails. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md index ba85c16ce2..3c1e58353f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md @@ -13,7 +13,7 @@ title: Remove-MoveRequest # Remove-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 Remove-MoveRequest cmdlet to cancel a mailbox move initiated using the New-MoveRequest cmdlet. @@ -49,7 +49,7 @@ In Exchange 2010, you need to use the Remove-MoveRequest cmdlet on completed mov The MoveRequestQueue and MailboxGuid parameters are for debugging purposes only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md index b883db3f6a..11da253b2d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md @@ -29,7 +29,7 @@ Remove-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/Remove-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md index 9fbb317d05..ce326f3292 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md @@ -33,7 +33,7 @@ Remove-OabVirtualDirectory [-Identity] ## DESCRIPTION Some situations require the removal of an OAB virtual directory. For example, to uninstall an Exchange server that contains an OAB distribution points list, you need to remove the OAB virtual directory and then re-create it on another server. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md index ae2cf79c53..7d7ab5b347 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md @@ -13,7 +13,7 @@ title: Remove-OfflineAddressBook # Remove-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 Remove-OfflineAddressBook cmdlet to remove (delete) offline address books (OABs). @@ -35,7 +35,7 @@ Remove-OfflineAddressBook [-Identity] ## DESCRIPTION If you remove the default OAB, you need to configure another OAB as the default by using the IsDefault parameter on the New-OfflineAddressBook or Set-OfflineAddressBook 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md index 02de5ee8ee..1c96267990 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md @@ -29,9 +29,9 @@ Remove-OnPremisesOrganization [-Identity] ``` ## DESCRIPTION -Removing an OnPremisesOrganization object should only be used in circumstances where the hybrid deployment state is corrupt and under the direction and supervision of Microsoft Customer Service and Support. After removing the OnPremisesOrganization object, any related hybrid deployment configured with this object won't be functional and will need to be re-created and reconfigured. +Removing an OnPremisesOrganization object should only be used in circumstances where the hybrid deployment state is corrupt and under the direction and supervision of Microsoft Customer Service and Support. After removing the OnPremisesOrganization object, any related hybrid deployment configured with this object aren't functional and need to be re-created and reconfigured. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md index 006af945f7..e1a750ebb3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md @@ -13,7 +13,7 @@ title: Remove-OrganizationRelationship # Remove-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 Remove-OrganizationRelationship cmdlet to remove the organization relationship with an external Exchange organization. @@ -32,7 +32,7 @@ Remove-OrganizationRelationship [-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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md index dcfd7ccd4c..9c740ebb31 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md @@ -15,7 +15,7 @@ title: Remove-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 Remove-OutlookProtectionRule cmdlet to remove Outlook protection rules. @@ -34,7 +34,7 @@ Remove-OutlookProtectionRule [-Identity] ## DESCRIPTION Outlook protection rules use an Active Directory Rights Management Services (AD RMS) rights template to automatically apply Information Rights Management (IRM) protection to messages before they're sent. 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/Remove-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md index ca4e1e331e..963f8c71d9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md @@ -32,7 +32,7 @@ Remove-OutlookProvider [-Identity] ## DESCRIPTION The Remove-OutlookProvider cmdlet deletes the AutoDiscoverConfig object under the Global Settings object in Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md index 0bd84f979a..5b620c8bb2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md @@ -13,7 +13,7 @@ title: Remove-OwaMailboxPolicy # Remove-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 Remove-OwaMailboxPolicy cmdlet to remove Outlook on the web mailbox policies from the organization. @@ -31,9 +31,9 @@ Remove-OwaMailboxPolicy [-Identity] ``` ## DESCRIPTION -Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). +Changes to Outlook on the web mailbox policies might take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md index 8eb57c6379..a124400754 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md @@ -37,7 +37,7 @@ You might be required to use the Remove-OwaVirtualDirectory cmdlet in the follow Remove-OwaVirtualDirectory permanently removes an Outlook on the web virtual directory or directories. When you use this cmdlet, make sure that you don't accidentally delete the default Outlook on the web virtual directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md index 1badd61959..936b9caaf0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md @@ -13,7 +13,7 @@ title: Remove-PartnerApplication # Remove-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 Remove-PartnerApplication cmdlet to remove a partner application configuration. @@ -34,7 +34,7 @@ You can configure partner applications such as Microsoft SharePoint to access Ex We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md index eef6fba7a1..3943fd117f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md @@ -31,7 +31,7 @@ Remove-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/Remove-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md index e2011f2ab5..d20d920506 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md @@ -13,7 +13,7 @@ title: Remove-PolicyTipConfig # Remove-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 Remove-PolicyTipConfig cmdlet to remove custom data loss prevention (DLP) Policy Tips from your organization. You can't remove built-in Policy Tips. @@ -30,7 +30,7 @@ Remove-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/Remove-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md index 2174fd682c..72abe8d4c1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md @@ -32,7 +32,7 @@ Remove-PowerShellVirtualDirectory [-Identity] ## DESCRIPTION Although it's possible to remove a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,7 +43,7 @@ Remove-PowerShellVirtualDirectory "Internal (Default Web Site)" -Confirm:$False This example removes a Windows PowerShell virtual directory without confirmation. -Be careful when using the Remove-PowerShellVirtualDirectory cmdlet without confirmation. You won't be prompted before the virtual directory is deleted. +Be careful when using the Remove-PowerShellVirtualDirectory cmdlet without confirmation. You aren't prompted before the virtual directory is deleted. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md index c1eeb1b2cd..d3d0cdf444 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md @@ -13,7 +13,7 @@ title: Remove-PublicFolder # Remove-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 Remove-PublicFolder cmdlet to remove an existing public folder. @@ -35,7 +35,7 @@ Remove-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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md index 23f93a12d8..8a8bf774bd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md @@ -48,7 +48,7 @@ Remove-PublicFolderAdministrativePermission [[-Identity] -Acces ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md index bdd0ea1ad5..8f6803762a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md @@ -31,7 +31,7 @@ Remove-PublicFolderDatabase [-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). Removing a public folder database can have a broad range of serious consequences. (This is particularly true when removing the last public folder database in the organization.) For more information, see [Remove Public Folder Databases](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd876883(v=exchg.141)). diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md index 72b59a29e3..0667881178 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md @@ -13,7 +13,7 @@ title: Remove-PublicFolderMailboxMigrationRequest # Remove-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 Remove-PublicFolderMailboxMigrationRequest cmdlet to remove individual jobs from public folder migration batches that were created by using the New-MigrationBatch cmdlet. @@ -41,7 +41,7 @@ Remove-PublicFolderMailboxMigrationRequest -RequestGuid -RequestQueue -RequestQueue -RequestQueue ## DESCRIPTION You can't remove the built-in quarantine policies named AdminOnlyAccessPolicy or DefaultFullAccessPolicy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md index 1bacd5e932..f8720a5197 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md @@ -32,7 +32,7 @@ Remove-ReceiveConnector [-Identity] ## DESCRIPTION Removing a Receive connector from the server might affect mail flow throughout the 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/Remove-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md index 5532764950..ac050e0a57 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md @@ -36,7 +36,7 @@ Remove-RecipientPermission [-Identity] -AccessRights ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md index 8b72bc15ab..fd6ab9e40a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md @@ -36,7 +36,7 @@ With the Remove-RemoteMailbox cmdlet, you can remove an on-premises mail-enabled Directory synchronization must be configured correctly for a mailbox to be removed from the service. Removal of the mailbox from the service isn't immediate and depends on the directory synchronization schedule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,7 +45,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Remove-RemoteMailbox "Kim Akers" ``` -This example removes the on-premises mail-enabled user Kim Akers and the associated mailbox from the service. This example assumes directory synchronization has been configured. +This example removes the on-premises mail-enabled user Kim Akers and the associated mailbox from the service. This example assumes directory synchronization is configured. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md index 68777847fb..37601a5812 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md @@ -28,7 +28,7 @@ Remove-ReportSubmissionPolicy [-Identity] [< ## DESCRIPTION There's only one report submission policy in an organization, and it's named DefaultReportSubmissionPolicy. You can remove the policy and then use the New-ReportSubmissionPolicy cmdlet to recreate it with the default 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/Remove-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md index fabd608925..40faf43a7b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md @@ -31,7 +31,7 @@ Remove-ReportSubmissionRule [-Identity] ## DESCRIPTION To disable the report submission rule without deleting it, use the Disable-ReportSubmissionRule 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md index 73733485fe..c85c142160 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md @@ -30,7 +30,7 @@ Remove-ResubmitRequest [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md index c8d5021c8d..0475a58a8f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md @@ -13,7 +13,7 @@ title: Remove-RetentionPolicy # Remove-RetentionPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-RetentionPolicy cmdlet to remove a retention policy. @@ -33,9 +33,9 @@ Remove-RetentionPolicy [-Identity] ## DESCRIPTION Retention policies are used to apply message retention settings to folders and items in a mailbox. The Remove-RetentionPolicy cmdlet removes an existing retention policy. -If you remove a retention policy that's assigned to users and they don't have another retention policy assigned, messages in those mailboxes may never expire. This may be a violation of the organization's messaging retention policies. When you attempt to remove a policy that's assigned to users, Microsoft Exchange displays a confirmation message indicating that the policy is assigned to users. Note that this message is in addition to the confirmation prompt displayed when removing a retention policy. +If you remove a retention policy that's assigned to users and they don't have another retention policy assigned, messages in those mailboxes might never expire. This might be a violation of the organization's messaging retention policies. When you attempt to remove a policy that's assigned to users, Microsoft Exchange displays a confirmation message indicating that the policy is assigned to users. This message is in addition to the confirmation prompt displayed when removing a retention 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/Remove-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md index 782489d23e..d8d0bfdde8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md @@ -13,7 +13,7 @@ title: Remove-RetentionPolicyTag # Remove-RetentionPolicyTag ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-RetentionPolicyTag cmdlet to remove a retention tag. @@ -32,11 +32,11 @@ Remove-RetentionPolicyTag [-Identity] ## DESCRIPTION Retention tags are added to a retention policy, which is applied to a mailbox. -When you use the Remove-RetentionPolicyTag cmdlet to remove a retention tag, it removes the tag definition stored in Active Directory. The next time the Managed Folder Assistant runs, it processes all items that have the removed tag applied and restamps them. Depending on the number of mailboxes and messages, this process may result in significant resource consumption on all Mailbox servers that contain mailboxes with a retention policy that includes the removed tag. +When you use the Remove-RetentionPolicyTag cmdlet to remove a retention tag, it removes the tag definition stored in Active Directory. The next time the Managed Folder Assistant runs, it processes all items that have the removed tag applied and restamps them. Depending on the number of mailboxes and messages, this process might result in significant resource consumption on all Mailbox servers that contain mailboxes with a retention policy that includes the removed tag. For more information about retention tags, see [Retention tags and retention policies in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mrm/retention-tags-and-retention-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md index 20586d4cb2..5b564b0d0d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md @@ -13,7 +13,7 @@ title: Remove-RoleAssignmentPolicy # Remove-RoleAssignmentPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-RoleAssignmentPolicy cmdlet to remove existing management role assignment policies from your organization. @@ -38,7 +38,7 @@ The assignment policy you want to remove can't be assigned to any mailboxes or m For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md index f23147c627..8823aa5d8b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md @@ -13,7 +13,7 @@ title: Remove-RoleGroup # Remove-RoleGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-RoleGroup cmdlet to remove a management role group. @@ -36,11 +36,11 @@ When you remove a role group, all the management role assignments assigned manag You can't remove built-in role groups. -If the ManagedBy property has been populated with role group managers, the user removing the role group must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. +If the ManagedBy property is populated with role group managers, the user removing the role group must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md index 7abb07e98f..a7c39c03c7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md @@ -13,7 +13,7 @@ title: Remove-RoleGroupMember # Remove-RoleGroupMember ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-RoleGroupMember cmdlet to remove a member of a management role group. @@ -33,13 +33,13 @@ Remove-RoleGroupMember [-Identity] -Member ``` ## DESCRIPTION -Disabling RPC client access on a server blocks all RPC access through the specified Client Access server. Therefore, RPC clients (for example, clients running Microsoft Office Outlook 2007) with mailboxes on any mailbox databases configured to use the specified Client Access server won't be able to connect. +Disabling RPC client access on a server blocks all RPC access through the specified Client Access server. Therefore, RPC clients (for example, clients running Microsoft Office Outlook 2007) with mailboxes on any mailbox databases configured to use the specified Client Access server can't connect. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md index d79cf3b777..97148431b9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md @@ -32,7 +32,7 @@ Remove-SafeAttachmentPolicy [-Identity] ## DESCRIPTION Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md index 74fae37eb9..28b2b0c067 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md @@ -31,7 +31,7 @@ Remove-SafeAttachmentRule [-Identity] ## DESCRIPTION Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md index e4fcd71186..40c1b76e66 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md @@ -34,7 +34,7 @@ You can't remove the default Safe Links policy (the policy where the IsDefault p Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md index a8c412145f..3fd4cb00d9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md @@ -31,7 +31,7 @@ Remove-SafeLinksRule [-Identity] ## DESCRIPTION Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md index fd539a83c6..f0db065269 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md @@ -30,9 +30,11 @@ Remove-SearchDocumentFormat [-Identity] ``` ## DESCRIPTION -After running the Remove-SearchDocumentFormat cmdlet, your must run the following cmdlet to restart the search service. There will be a brief search outage. +After running the Remove-SearchDocumentFormat cmdlet, you must run the following cmdlet to restart the search service. There will be a brief search outage. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +`Restart-Service HostControllerService` + +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md index 878683aaa8..a8094fee23 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md @@ -31,7 +31,7 @@ Remove-SecOpsOverridePolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md index ef7ec0522d..731a453bec 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md @@ -32,9 +32,9 @@ Remove-SendConnector [-Identity] ## DESCRIPTION The Remove-SendConnector cmdlet deletes the object and the configuration settings for the Send connector. -Although a Send connector is configured locally in the Transport service on a Mailbox server or on an Edge server, deleting a Send connector may affect mail flow throughout the organization. +Although a Send connector is configured locally in the Transport service on a Mailbox server or on an Edge server, deleting a Send connector might affect mail flow throughout the 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/Remove-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md index 8797d26742..d4d2e18a65 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md @@ -15,7 +15,7 @@ title: Remove-ServerMonitoringOverride ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Remove-ServerMonitoringOverride cmdlet to remove a managed availability local server override that has been configured for a probe, monitor or responder. +Use the Remove-ServerMonitoringOverride cmdlet to remove a managed availability local server override that is configured for a probe, monitor or responder. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -29,7 +29,7 @@ Remove-ServerMonitoringOverride [-Identity] -ItemType ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md index f1f2727920..be10212190 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md @@ -34,7 +34,7 @@ Remove-SettingOverride [-Identity] ## DESCRIPTION Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and they're lost when you install the next Exchange CU. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md index 2422bc4285..719d9621a8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md @@ -13,7 +13,7 @@ title: Remove-SharingPolicy # Remove-SharingPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-SharingPolicy cmdlet to remove a sharing policy. Before you can remove a sharing policy, you must ensure that no mailbox users are provisioned to use that policy. @@ -30,7 +30,7 @@ Remove-SharingPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md index f896036b30..78406d422b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md @@ -34,7 +34,7 @@ Remove-SiteMailboxProvisioningPolicy [-Identity] ## DESCRIPTION You can't delete the default site mailbox provisioning policy. You need to create a new default policy by using the New-SiteMailboxProvisioningPolicy cmdlet or designate an existing policy as the default policy by using the Set-SiteMailboxProvisioningPolicy 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md index eced30b9b1..7f22253212 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md @@ -37,7 +37,7 @@ A mailbox is marked as Disabled immediately after the Disable-Mailbox or Remove- To view disabled mailboxes, run the Get-MailboxStatistics cmdlet against a database using the property DisconnectReason with a value of Disabled. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md index 35879232b1..3815b75020 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md @@ -13,7 +13,7 @@ title: Remove-SweepRule # Remove-SweepRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-SweepRule cmdlet to remove Sweep rules from mailboxes. @@ -31,7 +31,7 @@ Remove-SweepRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md index 76b893ba88..5b7c3b265b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md @@ -13,7 +13,7 @@ title: Remove-SyncMailPublicFolder # Remove-SyncMailPublicFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. The Remove-SyncMailPublicFolder cmdlet is used by the Sync-MailPublicFolders.ps1 script to remove mail-enabled public folder recipient objects from Exchange Online (the script synchronizes mail-enabled public folder objects from the source on-premises Exchange organization to Exchange Online). Don't use this cmdlet unless you are directed to do so by Microsoft Customer Service and Support or by specific documentation. @@ -32,7 +32,7 @@ Remove-SyncMailPublicFolder [-Identity] ## DESCRIPTION This cmdlet is only used by the Sync-MailPublicFolders.ps1 script. Don't run this cmdlet in the Exchange Management Shell or in Exchange Online PowerShell. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md index 0ee365aefb..159bf7e9fa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md @@ -32,7 +32,7 @@ Remove-SystemMessage [-Identity] ## DESCRIPTION You can't remove a default system message that's included with Exchange. When you remove a custom system message, the message text reverts to the text in the corresponding system message (if any) that's included with Exchange. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md index 7bf6419833..98cf2e12da 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md @@ -38,7 +38,7 @@ Remove-TenantAllowBlockListItems -Ids -ListType ``` ## 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 @@ -139,7 +139,7 @@ Accept wildcard characters: False The ListSubType specifies further specifies the type of entry that you want to remove. Valid values are: - AdvancedDelivery: Use this value for phishing simulation URLs. -- Tenant: This is the default value. +- Tenant: This value is the default. ```yaml Type: ListSubType diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md index be8e893e78..8e2392eaba 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md @@ -31,7 +31,7 @@ Remove-TenantAllowBlockListSpoofItems [-Identity] ``` ## DESCRIPTION -The Remove-UMCallAnsweringRule cmdlet removes an existing UM call answering rule that has been created and stored in a UM-enabled user's mailbox. When you remove an existing call answering rule, all of the remaining call answering rules are still processed in order of their priority. +The Remove-UMCallAnsweringRule cmdlet removes an existing UM call answering rule that is created and stored in a UM-enabled user's mailbox. When you remove an existing call answering rule, all of the remaining call answering rules are still processed in order of their priority. After this task is completed, the cmdlet sets the parameters and the values specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md index 9891da4d6d..8f422da9ef 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md @@ -34,7 +34,7 @@ The Remove-UMDialPlan cmdlet deletes an existing UM dial plan from Active Direct After this task is completed, the UM dial plan is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md index 5a6e163d62..6966e94209 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md @@ -34,7 +34,7 @@ The Remove-UMHuntGroup cmdlet deletes an existing UM hunt group from Active Dire After this task is completed, the UM hunt group is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md index f0bb270293..2eb54404fe 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md @@ -36,7 +36,7 @@ The Remove-UMIPGateway cmdlet should be run only by an administrator who fully u After this task is completed, the UM IP gateway is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md index 6e1dbd4616..47622239c9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md @@ -34,7 +34,7 @@ The Remove-UMMailboxPolicy cmdlet deletes or removes a UM mailbox policy. If the After this task is completed, the UM mailbox policy is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md index cbccda7b2c..28b72dc892 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md @@ -34,7 +34,7 @@ Remove-UnifiedGroup [-Identity] ## DESCRIPTION Microsoft 365 Groups are group objects that are available across Microsoft 365 services. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md index afdf8598ab..494ea656fd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md @@ -34,7 +34,7 @@ Remove-UnifiedGroupLinks [-Identity] -Links Use the Remove-UserPhoto cmdlet to delete the user photo currently associated with a user's account. This cmdlet removes the photo from user's Exchange mailbox root. In on-premises Exchange, it also removes the user's photo from their Active Directory account. Administrators can also use the Exchange admin center (EAC) to delete user photos by accessing the Options page in the user's mailbox in Outlook on the web. -**Notes**: Changes to the user photo won't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image. +**Notes**: Changes to the user photo don't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md index fd0cb8ce9c..fe576b5f2d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md @@ -15,7 +15,7 @@ title: Remove-VivaModuleFeaturePolicy ## SYNOPSIS This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). -Use the Remove-VivaModuleFeaturePolicy cmdlet to delete an access policy for a feature in a Viva module in Viva. Once you delete a policy, the policy is permanently deleted. You cannot undo the deletion. +Use the Remove-VivaModuleFeaturePolicy cmdlet to delete an access policy for a feature in a Viva module in Viva. Once you delete a policy, the policy is permanently deleted. You can't undo the deletion. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md index 4a2b358ce1..146c97aa5f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md @@ -33,7 +33,7 @@ Remove-WebServicesVirtualDirectory [-Identity] ## DESCRIPTION You can remove the default Exchange Web Services virtual directory or another Exchange Web Services virtual directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md index 4e966c4f48..d15a9671e2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md @@ -30,7 +30,7 @@ Remove-X400AuthoritativeDomain [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md index 6eda0f1f75..304b16a5f9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md +++ b/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md @@ -47,7 +47,7 @@ The Reset-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely The Reset-ProvisioningCache cmdlet clears the Windows PowerShell provisioning cache of frequently used Active Directory objects. To reduce Active Directory requests, a provisioning cache is initialized in each Windows PowerShell runspace and is used to cache common objects that are frequently used by cmdlets and provisioning handlers. During Exchange cmdlet execution, the provisioning cache loads configuration objects from Active Directory to help run a cmdlet. For example, when you create a mailbox, the New-Mailbox cmdlet obtains properties from Active Directory. When running cmdlets, configuration objects such as database containers, administrative role groups, and LegacyDNs are retrieved from Active Directory. Because these types of objects are stable and don't change for months or years after they're created, they're stored in the provisioning cache used by Windows PowerShell. This increases provisioning efficiency and significantly improves cmdlet performance. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -191,7 +191,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Organizations parameter specifies the organizations that the provisioning cache will be reset. This parameter is used in multi-tenant deployments. +The Organizations parameter specifies the organizations where the provisioning cache is reset. Use this parameter in multi-tenant deployments. ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md index ae01926758..d57df551a4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md @@ -45,7 +45,7 @@ The Restore-DatabaseAvailabilityGroup cmdlet performs several operations that af - Forcibly evicts the servers listed on the StoppedMailboxServers list from the DAG's cluster, thereby reestablishing quorum for the cluster enabling the surviving DAG members to start and provide service. - Configures the DAG to use the alternate witness server if there is an even number of surviving DAG members, or a single surviving DAG member. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Restore-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md index bfb2fae14f..c535b125f8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md @@ -32,7 +32,7 @@ Restore-DetailsTemplate [-Identity] ## DESCRIPTION Details templates can't be created or deleted, but this task restores the specified template to its default state. All user changes are lost. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Restore-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md index acdecb4511..88fdd90071 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md @@ -49,7 +49,7 @@ Restore-Mailbox [-Identity] -RecoveryDatabase Applicable: Exchange Server 2010 -The EndDate parameter specifies the end date for filtering content that will be exported from the source mailbox. Only items in the mailbox whose date is prior to the end date are exported. When you enter a specific date, use the short date format defined in the Regional Options settings configured on the local computer. For example, if your computer is configured to use the short date format MM/dd/yyyy, enter 03/01/2010 to specify March 1, 2010. +The EndDate parameter specifies the end date for filtering content to be exported from the source mailbox. Only items in the mailbox whose date is prior to the end date are exported. When you enter a specific date, use the short date format defined in the Regional Options settings configured on the local computer. For example, if your computer is configured to use the short date format MM/dd/yyyy, enter 03/01/2010 to specify March 1, 2010. ```yaml Type: DateTime @@ -475,9 +475,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The ValidateOnly switch tells the command to evaluate the conditions and requirements necessary to perform the operation, and then report whether the operation will succeed or fail. You don't need to specify a value with this switch. - -No changes are made when you use this switch. +The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md b/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md index cd4e7247c4..7dfbf5787e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md @@ -13,7 +13,7 @@ title: Restore-RecoverableItems # Restore-RecoverableItems ## 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 Restore-RecoverableItems items cmdlet to restore deleted items in mailboxes. You use the Get-RecoverableItems cmdlet to find the deleted items to recover. @@ -58,7 +58,7 @@ Restore-RecoverableItems -Identity ## DESCRIPTION Items are restored to the original folder location if the information is available for the item. If the information can't be found, the item is restored to the default folder for the item type (Inbox for messages, Calendar for meetings and appointments, etc.). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -322,7 +322,7 @@ This parameter is available only in the cloud-based service. The RestoreTargetFolder parameter specifies the top-level folder in which to restore data. If you don't specify this parameter, the command restores folders to the top of the folder structure in the target mailbox or archive. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure. -This parameter is available only on primary mailboxes and is ignored on archive mailboxes. A destination folder will be created if it does not exist. Valid paths are: +This parameter is available only on primary mailboxes and is ignored on archive mailboxes. A destination folder is created if it does not exist. Valid paths are: - `/` - `/folder1` @@ -330,7 +330,7 @@ This parameter is available only on primary mailboxes and is ignored on archive - `folder1` - `folder1/folder2` -The preceding or trailing `/` will be ignored. Then, it will be treated as the relative path of the IPM sub-tree: `/Top Of Information Store`. +The preceding or trailing `/` are ignored. Then, it's treated as the relative path of the IPM sub-tree: `/Top Of Information Store`. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md index 1403d54b10..645c002cfe 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md @@ -45,7 +45,7 @@ Resume-MailboxDatabaseCopy [-Identity] ## DESCRIPTION The Resume-MailboxDatabaseCopy cmdlet resumes replication and replay from a suspended state. If a database copy was suspended without administrator intervention, it's because the database copy is in a bad state. You can use the Get-MailboxDatabaseCopyStatus cmdlet to see if there are any messages indicating a failure. If the copy of the database is in a bad state, resuming the copy causes replication to fail and the mailbox database copy to return to a suspended state. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Resume-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md index e8b277aa9d..9dd5908f7a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md @@ -34,7 +34,7 @@ Resume-MailboxExportRequest [-Identity] ## DESCRIPTION The Resume-MailboxExportRequest cmdlet can be pipelined with the Get-MailboxExportRequest 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md index 298495c2a6..785786b9af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md @@ -13,7 +13,7 @@ title: Resume-MailboxImportRequest # Resume-MailboxImportRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Resume-MailboxImportRequest cmdlet to resume an import request that was suspended or failed. @@ -36,7 +36,7 @@ Resume-MailboxImportRequest [-Identity] ## DESCRIPTION This cmdlet can be pipelined with the Get-MailboxImportRequest 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md index 83322f5be6..fad77ae856 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md @@ -13,7 +13,7 @@ title: Resume-MailboxRestoreRequest # Resume-MailboxRestoreRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Resume-MailboxRestoreRequest cmdlet to resume a restore request that was suspended or failed. @@ -30,7 +30,7 @@ Resume-MailboxRestoreRequest [-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/Resume-Message.md b/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md index 2f95ea5a15..0e3a1e81b7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md @@ -41,7 +41,7 @@ Resume-Message [-Identity] ## DESCRIPTION A message being sent to multiple recipients might be located in multiple queues. If you specify an Identity parameter, the message is resumed in a single queue if that identity matches only a single message. If the identity matches more than one message, you receive an error. To resume a message in more than one queue in a single operation, you must use the Filter 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 @@ -54,7 +54,7 @@ This example resumes delivery of all messages in a suspended state and for which - The messages were sent by the sender kweku@contoso.com. - The messages are queued on the server Server1. -- The messages will expire before 15:00 on January 5, 2018. +- The messages expire before 15:00 on January 5, 2018. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md index f03468c869..b1659f57e9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md @@ -13,9 +13,9 @@ title: Resume-MoveRequest # Resume-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 Resume-MoveRequest cmdlet to resume a move request that has been suspended or has failed. +Use the Resume-MoveRequest cmdlet to resume a move request that is suspended or has failed. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -32,7 +32,7 @@ Resume-MoveRequest [-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/Resume-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md index 0ed306d912..bd11ab1149 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md @@ -32,7 +32,7 @@ Resume-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/Resume-PublicFolderReplication.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md index fdedc6a3ae..a5ee4bc606 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md @@ -29,7 +29,7 @@ Resume-PublicFolderReplication [-Confirm] ``` ## 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/Resume-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md index 7d18b6c74d..fcd4ceaf1c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md @@ -41,7 +41,7 @@ Resume-Queue [-Identity] ## DESCRIPTION If you use the Identity parameter, the queue is resumed only if that identity matches a single queue. If the identity matches more than one queue, you receive an error. To resume more than one queue in a single operation, you must use the Filter 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/Retry-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md index 42164baa7f..20b8cbb918 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md +++ b/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md @@ -43,7 +43,7 @@ Retry-Queue [-Identity] ## DESCRIPTION The Retry-Queue cmdlet forces a connection attempt for a queue that has a status of Retry. The cmdlet establishes a connection to the next hop if possible. If a connection isn't established, a new retry time is set. To use this command to retry delivery of messages in the Unreachable queue, you must include the Resubmit 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/Rotate-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md index 894b736a5b..14fd8444d3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md @@ -30,7 +30,7 @@ Rotate-DkimSigningConfig [-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/Search-AdminAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md index ead5224ff7..a1fe3fddee 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md @@ -16,7 +16,7 @@ title: Search-AdminAuditLog > [!NOTE] > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Search-AdminAuditLog cmdlet to search the contents of the administrator audit log. Administrator audit logging records when a user or administrator makes a change in your organization (in the Exchange admin center or by using cmdlets). @@ -45,11 +45,11 @@ If you run the Search-AdminAuditLog cmdlet without any parameters, up to 1,000 l In Exchange Online PowerShell, if you don't use the StartDate or EndDate parameters, only results from the last 14 days are returned. -In Exchange Online PowerShell, data is available for the last 90 days. You can enter dates older than 90 days, but only data from the last 90 days will be returned. +In Exchange Online PowerShell, data is available for the last 90 days. You can enter dates older than 90 days, but only data from the last 90 days are returned. For more information about the structure and properties of the audit log, see [Administrator audit log structure](https://learn.microsoft.com/Exchange/policy-and-compliance/admin-audit-logging/log-structure). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -215,7 +215,7 @@ The ObjectIds parameter filters the results by the object that was modified (the - Canonical distinguished name (for example, contoso.com/Users/Akia Al-Zuhairi) - Public folder identity (for example, \\Engineering\\Customer Discussion) -You'll likely need to use other filtering parameters on this cmdlet to narrow down the results and identify the types of objects that you're interested in. In the results of this cmdlet, this property is named **ObjectModified**. +You likely need to use other filtering parameters on this cmdlet to narrow down the results and identify the types of objects that you're interested in. In the results of this cmdlet, this property is named **ObjectModified**. You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md index c2be455ddb..31efc27c8a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md @@ -348,7 +348,7 @@ The LogLevel parameter specifies the logging level for the search. It can have o The default log level is Basic. -When you included this parameter, an email message is created and sent to the mailbox specified by the TargetMailbox parameter. The log file (which is a CSV-formatted file named Search Results.csv) is attached to this email message, and will be located in the folder specified by the TargetFolder parameter. The log file contains a row for each message that's included in the search results when you run the Search-Mailbox cmdlet. +When you included this parameter, an email message is created and sent to the mailbox specified by the TargetMailbox parameter. The log file (which is a CSV-formatted file named Search Results.csv) is attached to this email message, and is located in the folder specified by the TargetFolder parameter. The log file contains a row for each message that's included in the search results when you run the Search-Mailbox cmdlet. ```yaml Type: LoggingLevel diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md index ec79d9383b..8a20ce8c36 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md @@ -16,7 +16,7 @@ title: Search-MailboxAuditLog > [!NOTE] > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Search-MailboxAuditLog cmdlet to search mailbox audit log entries matching the specified search terms. @@ -62,7 +62,7 @@ The Search-MailboxAuditLog cmdlet performs a synchronous search of mailbox audit In multi-geo environments, when you run this cmdlet in a different region from the mailbox that you're trying to search, you might receive the error, "An error occurred while trying to access the audit log." In this scenario, you need to anchor the PowerShell session to a user in the same region as the mailbox as described in [Connect directly to a geo location using Exchange Online PowerShell](https://learn.microsoft.com/microsoft-365/enterprise/administering-exchange-online-multi-geo#connect-directly-to-a-geo-location-using-exchange-online-powershell). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -166,7 +166,7 @@ The ExternalAccess parameter specifies whether to return only audit log entries $true: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are returned. -$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This is the default value. +$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md b/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md index d1f91cda9d..87a469ee90 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md @@ -57,7 +57,7 @@ Search-MessageTrackingReport [-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 @@ -235,7 +235,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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/Search-UnifiedAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md index c468fec3d7..6c403ffeeb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md @@ -48,13 +48,13 @@ The Search-UnifiedAuditLog cmdlet is available in Exchange Online PowerShell. Yo If you want to programmatically download data from the Microsoft 365 audit log, we recommend that you use the Microsoft 365 Management Activity API instead of using the Search-UnifiedAuditLog cmdlet in a PowerShell script. The Microsoft 365 Management Activity API is a REST web service that you can use to develop operations, security, and compliance monitoring solutions for your organization. For more information, see [Management Activity API reference](https://learn.microsoft.com/office/office-365-management-api/office-365-management-activity-api-reference). -This cmdlet is available in Office 365 operated by 21Vianet, but it won't return any results. +This cmdlet is available in Office 365 operated by 21Vianet, but it doesn't return any results. The OutVariable parameter accepts objects of type ArrayList. Here's an example of how to use it: `$start = (Get-Date).AddDays(-1); $end = (Get-Date).AddDays(-0.5); $auditData = New-Object System.Collections.ArrayList; Search-UnifiedAuditLog -StartDate $start -EndDate $end -OutVariable +auditData | Out-Null` -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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 @@ Search-UnifiedAuditLog -StartDate "6/1/2023 8:00 AM" -EndDate "6/1/2023 6:00 PM" This example searches the unified audit log for all Exchange admin events from 8:00 AM to 6:00 PM on June 1, 2023. -**Note** If you use the same date for the StartDate and EndDate parameters, you need to include a timestamp; otherwise, no results will be returned because the date and time for the start and end dates will be the same. +**Note** If you use the same date for the StartDate and EndDate parameters, you need to include a timestamp; otherwise, no results are returned because the date and time for the start and end dates are the same. ### Example 3 ```powershell @@ -335,7 +335,7 @@ Accept wildcard characters: False The SessionCommand parameter specifies how much information is returned and how it's organized. This parameter is required if you want to retrieve more than the default limit of 100 results. Valid values are: -- ReturnLargeSet: This value causes the cmdlet to return unsorted data. By using paging, you can access a maximum of 50,000 results. This is the recommended value if an ordered result is not required and has been optimized for search latency. +- ReturnLargeSet: This value causes the cmdlet to return unsorted data. By using paging, you can access a maximum of 50,000 results. This is the recommended value if an ordered result is not required and is optimized for search latency. - ReturnNextPreviewPage: This value causes the cmdlet to return data sorted on date. The maximum number of records returned through use of either paging or the ResultSize parameter is 5,000 records. **Note**: Always use the same SessionCommand value for a given SessionId value. Don't switch between ReturnLargeSet and ReturnNextPreviewPage for the same session ID. Otherwise, the output is limited to 10,000 results. @@ -356,9 +356,9 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The SessionId parameter specifies an ID you provide in the form of a string to identify a command (the cmdlet and its parameters) that will be run multiple times to return paged data. The SessionId can be any string value you choose. +The SessionId parameter specifies an ID string to identify a command (the cmdlet and its parameters) that's run multiple times to return paged data. The SessionId can be any string value you choose. -When the cmdlet is run sequentially with the same session ID, the cmdlet will return the data in sequential blocks of the size specified by ResultSize. +When the cmdlet is run sequentially with the same session ID, the cmdlet returns the data in sequential blocks of the size specified by ResultSize. For a given session ID, if you use the SessionCommand value ReturnLargeSet, and then you use the SessionCommand value ReturnNextPreviewPage, the results are limited to 10,000 records. To have all 50,000 records available, always use the ReturnLargeSet value each time your run the cmdlet for the same session ID. diff --git a/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md index b1af8ec2d7..af84b61d3e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md +++ b/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md @@ -13,7 +13,7 @@ title: Send-TextMessagingVerificationCode # Send-TextMessagingVerificationCode ## 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 Send-TextMessagingVerificationCode cmdlet to send a text messaging verification as part of configuring text message notifications on the mailbox. @@ -32,7 +32,7 @@ Send-TextMessagingVerificationCode [[-Identity] ] ## DESCRIPTION The Send-TextMessagingVerificationCode cmdlet generates a verification code and sends it to a user's mobile phone. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). This cmdlet returns an error if the user requests a verification code more than three times within a 24-hour period. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md index 080dc688ce..537e6dd15f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md @@ -52,7 +52,7 @@ Set-ADServerSettings [[-PreferredServer] ] ``` ## 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/Set-ADSite.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md index d3e770f585..03b5ba59ce 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md @@ -33,7 +33,7 @@ Set-ADSite [-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 @@ -125,9 +125,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The InboundMailEnabled parameter enables or disables receiving incoming messages for all the Exchange located in the Active Directory site. Typically, this parameter is used after Active Directory site failover or maintenance. +The InboundMailEnabled parameter enables or disables receiving incoming messages for all Exchange servers located in the Active Directory site. Typically, you use this parameter after Active Directory site failover or maintenance. Valid values are: -Valid input for this parameter is $true or $false. The default value is $true. If you set the value to $false, none of the Exchange servers in the Active Directory site will be able to receive incoming messages. +- $true: All Exchange servers in the Active Directory site can receive incoming email messages. This value is the default. +- $false: No Exchange servers in the Active Directory site can receive incoming email messages. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md index 01d0e16fc3..f47a8b17c3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md @@ -35,7 +35,7 @@ Set-ADSiteLink [-Identity] ## DESCRIPTION By default, Microsoft Exchange determines the least cost routing path by using the cost assigned to the Active Directory IP site link. You can use the Set-ADSiteLink cmdlet to assign an Exchange-specific cost to the Active Directory IP site link. The Exchange-specific cost is a separate attribute used instead of the Active Directory-assigned cost to determine the least cost routing path. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -139,7 +139,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 64 KB through Int64. To remove the message size limit on an Active Directory IP site link, enter a value of unlimited. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md index 8a156797ad..d5c9dd43e2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md @@ -38,7 +38,7 @@ For more information about preset security policies in PowerShell, see [Preset s > [!IMPORTANT] > Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md index ea44a4a727..b623a6b8de 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md @@ -43,7 +43,7 @@ For more information about preset security policies in PowerShell, see [Preset s > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md index d4947a9cab..6c681e1ca8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md @@ -13,7 +13,7 @@ title: Set-AcceptedDomain # Set-AcceptedDomain ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-AcceptedDomain cmdlet to modify existing accepted domains in your organization. An accepted domain is any SMTP namespace for which an Exchange organization sends and receives email. @@ -42,7 +42,7 @@ Set-AcceptedDomain [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -166,7 +166,7 @@ Accept wildcard characters: False The DomainType parameter specifies the accepted domain type. Valid values are: -- Authoritative: This is the default value. Your organization is completely responsible for delivering email to recipients in the domain, and for generating non-delivery reports (also known as an NDRs, delivery system notifications, DSNs, or bounce messages) for unresolved recipients. +- Authoritative: This value is the default. Your organization is completely responsible for delivering email to recipients in the domain, and for generating non-delivery reports (also known as an NDRs, delivery system notifications, DSNs, or bounce messages) for unresolved recipients. - InternalRelay: This is a type of non-authoritative domain. Your organization receives email that's sent to recipients in the domain, but the messages are relayed to an external email system that's under your control. The external email system is responsible for generating NDRs for unresolved recipients. Use this value to treat messages that are sent to the domain as internal messages. - ExternalRelay: This is a type of non-authoritative domain that's available only in on-premises Exchange organizations. Your organization receives email that's sent to recipients in the domain, but the messages are relayed to an external email system that's completely outside of your control. The external email system is responsible for generating NDRs for unresolved recipients. @@ -212,7 +212,7 @@ This parameter is available only in on-premises Exchange. The MakeDefault parameter specifies whether the accepted domain is the default domain. Valid values are: $true or $false. -- $true: The accepted domain is the default domain. This is the default value for first accepted domain that's created in the organization. +- $true: The accepted domain is the default domain. This value is the default for first accepted domain that's created in the organization. - $false: The accepted domain isn't the default domain. This the default value for subsequent accepted domains. The default accepted domain is used in sender email addresses when the senders have only non-SMTP email addresses (for example, X.400 addresses). Non-SMTP email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. IMCEA encapsulation uses the default domain value in the SMTP email address. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md index 0f0c11f6da..aaedd38eb6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md @@ -31,7 +31,7 @@ Set-AccessToCustomerDataRequest -ApprovalDecision Your device has been blocked. "] +Set-ActiveSyncDeviceAutoblockThreshold -Identity "UserAgentChanges" BehaviorTypeIncidenceLimit 2 -BehaviorTypeIncidenceDuration 1440 -DeviceBlockDuration 1440 -AdminEmailInsert "Your device is blocked. "] ``` This example sets the autoblock threshold rule UserAgentChanges with several settings. It limits the number of accepted UserAgent changes to 2, specifies that the incidence duration is 1440 minutes and blocks the mobile device for 1440 minutes. Lastly, it inserts a message into the administrative email message sent to the user. ### Example 2 ```powershell -Set-ActiveSyncDeviceAutoblockThreshold -Identity "RecentCommands" BehaviorTypeIncidenceLimit 5 -BehaviorTypeIncidenceDuration 720 -DeviceBlockDuration 720 -AdminEmailInsert "Your device has been blocked. "] +Set-ActiveSyncDeviceAutoblockThreshold -Identity "RecentCommands" BehaviorTypeIncidenceLimit 5 -BehaviorTypeIncidenceDuration 720 -DeviceBlockDuration 720 -AdminEmailInsert "Your device is blocked. "] ``` This example sets the autoblock threshold rule RecentCommands with several settings. It limits the number of accepted RecentCommands changes to 5, specifies that the incidence duration is 720 minutes and blocks the mobile device for 720 minutes. Lastly, it inserts a message into the administrative email message sent to the user. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md index c315385640..d5222a900b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md @@ -13,7 +13,7 @@ title: Set-ActiveSyncMailboxPolicy # Set-ActiveSyncMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ActiveSyncMailboxPolicy cmdlet to apply a variety of Mobile Device mailbox policy settings to a server. You can set any of the parameters by using one command. @@ -90,7 +90,7 @@ With the Set-ActiveSyncMailboxPolicy cmdlet, you can set each parameter in a mai Some Microsoft Mobile Device mailbox policy settings require the mobile device to have specific built-in features that enforce these security and device management settings. If your organization allows all devices, you must set the AllowNonProvisionableDevices parameter to $true. This applies to devices that can't enforce all policy settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md index 3e8b02bfe3..c1e59f6d4b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md @@ -13,7 +13,7 @@ title: Set-ActiveSyncOrganizationSettings # Set-ActiveSyncOrganizationSettings ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ActiveSyncOrganizationSettings cmdlet to set the Exchange ActiveSync settings for the organization. @@ -38,7 +38,7 @@ Set-ActiveSyncOrganizationSettings [[-Identity] ## DESCRIPTION The Set-ActiveSyncVirtualDirectory cmdlet configures a variety of settings on the virtual directory used for Exchange ActiveSync including security, authentication, and internal and external URL settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -148,7 +148,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. ```yaml @@ -248,7 +248,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -268,7 +268,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -289,8 +289,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md index ad5d4f2c0d..3ca49ee585 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md @@ -13,7 +13,7 @@ title: Set-AddressBookPolicy # Set-AddressBookPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-AddressBookPolicy cmdlet to change the settings of an address book policy. @@ -37,7 +37,7 @@ Set-AddressBookPolicy [-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 @@ -72,7 +72,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The AddressLists parameter specifies the address lists that will be used by mailbox users who are assigned this address book policy. This parameter accepts multiple values, which should be separated by a comma. +The AddressLists parameter specifies the address lists for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the address list. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. + +You can find the identify values of address lists by using the Get-AddressList cmdlet. ```yaml Type: AddressListIdParameter[] @@ -131,7 +139,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The GlobalAddressList parameter specifies the identity of the global address list (GAL) that will be used by mailbox users who are assigned this address book policy. You can specify only one GAL for each address book policy. +The GlobalAddressList parameter specifies the GAL for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the GAL. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can find the identify values of GALs by using the Get-GlobalAddressList cmdlet. + +You can specify only one GAL for each address book policy. ```yaml Type: GlobalAddressListIdParameter @@ -167,7 +183,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The OfflineAddressBook parameter specifies the identity of the offline address book (OAB) that will be used by mailbox users who are assigned this address book policy. You can specify only one OAB for each address book policy. +The OfflineAddressBook parameter specifies the OAB for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the OAB. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can find the identify values of OABs by using the Get-OfflineAddressBook cmdlet. + +You can specify only one OAB for each address book policy. ```yaml Type: OfflineAddressBookIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md index bee9b693b5..72c8d4e3e6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md @@ -13,7 +13,7 @@ title: Set-AddressList # Set-AddressList ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-AddressList cmdlet to modify existing address lists. @@ -68,7 +68,7 @@ To create flexible filters that use any available recipient property and that ar You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md index 2039a6a6de..42c5b5bdfa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md @@ -13,7 +13,7 @@ title: Set-AdminAuditLogConfig # Set-AdminAuditLogConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-AdminAuditLogConfig cmdlet to configure the administrator audit logging configuration settings. @@ -44,11 +44,11 @@ When audit logging is enabled, a log entry is created for each cmdlet run, exclu The Set-AdminAuditLogConfig, Enable-CmdletExtensionAgent, and Disable-CmdletExtensionAgent cmdlets are logged when they're run regardless of whether administrator audit logging is enabled or disabled. -Administrator audit logging relies on Active Directory replication to replicate the configuration settings you specify to the domain controllers in your organization. Depending on your replication settings, the changes you make may not be immediately applied to all Exchange servers in your organization. +Administrator audit logging relies on Active Directory replication to replicate the configuration settings you specify to the domain controllers in your organization. Depending on your replication settings, the changes you make might not be immediately applied to all Exchange servers in your organization. -Changes to the audit log configuration may take up to 60 minutes to be applied on computers that have the Exchange Management Shell open at the time a configuration change is made. If you want to apply the changes immediately, close and reopen the Exchange Management Shell on each computer. +Changes to the audit log configuration might take up to 60 minutes to be applied on computers that have the Exchange Management Shell open at the time a configuration change is made. If you want to apply the changes immediately, close and reopen the Exchange Management Shell on each computer. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -151,7 +151,7 @@ This parameter is available only in on-premises Exchange. The AdminAuditLogEnabled parameter specifies whether administrator audit logging is enabled. Valid values are: -- $true: Administrator audit logging is enabled. This is the default value. +- $true: Administrator audit logging is enabled. This value is the default. - $false: Administrator audit logging is disabled. You must specify an administrator audit log mailbox before you enable logging. @@ -281,7 +281,7 @@ This parameter is available only in on-premises Exchange. The LogLevel parameter specifies whether additional properties should be included in the log entries. Valid values are: -- None: The CmdletName, ObjectName, Parameters (values), and the Caller, Succeeded and RunDate properties are included in log entries. This is the default value. +- None: The CmdletName, ObjectName, Parameters (values), and the Caller, Succeeded and RunDate properties are included in log entries. This value is the default. - Verbose: The ModifiedProperties (old and new) and ModifiedObjectResolvedName properties are also included in log entries. ```yaml @@ -327,7 +327,7 @@ This parameter is available only in on-premises Exchange. The TestCmdletLoggingEnabled parameter specifies whether test cmdlets (cmdlet names that begin with the verb Test) results are included in admin audit logging. Valid values are: - $true: Test cmdlets are included in admin audit logging. -- $false: Test cmdlets aren't included in admin audit logging. This is the default value. +- $false: Test cmdlets aren't included in admin audit logging. This value is the default. Test cmdlets can produce a large amount of information. As such, you should only enable logging of test cmdlets for a short period of time. @@ -351,7 +351,7 @@ This parameter is functional only in the cloud-based service. The UnifiedAuditLogIngestionEnabled parameter specifies whether to enable or disable the recording of user and admin activities in the Microsoft 365 audit log. Valid values are: -- $true: User and admin activities are recorded in the Microsoft 365 audit log, and admins can search the Microsoft 365 audit log. This is the default value. +- $true: User and admin activities are recorded in the Microsoft 365 audit log, and admins can search the Microsoft 365 audit log. This value is the default. - $false: User and admin activities aren't recorded in the Microsoft 365 audit log, and admins can't search the Microsoft 365 audit log. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md index f4a26fbb29..4cfb21fc4b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md @@ -65,7 +65,7 @@ Set-AntiPhishPolicy -Identity ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -138,7 +138,7 @@ This setting is part of spoof protection. The AuthenticationFailAction parameter specifies the action to take when the message fails composite authentication (a mixture of traditional SPF, DKIM, and DMARC email authentication checks and proprietary backend intelligence). Valid values are: -- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. - Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients. ```yaml @@ -183,7 +183,7 @@ This setting is part of spoof protection. The DmarcQuarantineAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=quarantine`. Valid values are: - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. -- Quarantine: Deliver the message to quarantine. This is the default value. +- Quarantine: Deliver the message to quarantine. This value is the default. ```yaml Type: SpoofDmarcQuarantineAction @@ -206,7 +206,7 @@ This setting is part of spoof protection. The DmarcRejectAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=reject`. Valid values are: - Quarantine: Deliver the message to quarantine. -- Reject: Reject the message. This is the default value. +- Reject: Reject the message. This value is the default. This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true. @@ -253,7 +253,7 @@ Accept wildcard characters: False The EnableFirstContactSafetyTips parameter specifies whether to enable or disable the safety tip that's shown when recipients first receive an email from a sender or do not often receive email from a sender. Valid values are: - $true: First contact safety tips are enabled. -- $false: First contact safety tips are disabled. This is the default value. +- $false: First contact safety tips are disabled. This value is the default. ```yaml Type: Boolean @@ -275,7 +275,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableMailboxIntelligence parameter specifies whether to enable or disable mailbox intelligence, which is artificial intelligence (AI) that determines user email patterns with their frequent contacts. Mailbox intelligence helps distinguish between messages from legitimate and impersonated senders based on a recipient's previous communication history. Valid values are: -- $true: Mailbox intelligence is enabled. This is the default value. +- $true: Mailbox intelligence is enabled. This value is the default. - $false: Mailbox intelligence is disabled. The values of the EnableMailboxIntelligenceProtection and MailboxIntelligenceProtectionAction parameters are ignored. ```yaml @@ -299,7 +299,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableMailboxIntelligenceProtection specifies whether to enable or disable taking action for impersonation detections from mailbox intelligence results. Valid values are: - $true: Take action for impersonation detections from mailbox intelligence results. Use the MailboxIntelligenceProtectionAction parameter to specify the action. -- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This is the default value. +- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This value is the default. This parameter is meaningful only if the EnableMailboxIntelligence parameter is set to the value $true. @@ -326,7 +326,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableOrganizationDomainsProtection parameter specifies whether to enable domain impersonation protection for all registered domains in the Microsoft 365 organization. Valid values are: - $true: Domain impersonation protection is enabled for all registered domains in the Microsoft 365 organization. -- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This is the default value. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters. +- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This value is the default. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters. ```yaml Type: Boolean @@ -349,7 +349,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for domain impersonation detections. Valid values are: - $true: Safety tips for similar domains are enabled. -- $false: Safety tips for similar domains are disabled. This is the default value. +- $false: Safety tips for similar domains are disabled. This value is the default. ```yaml Type: Boolean @@ -372,7 +372,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for user impersonation detections. Valid values are: - $true: Safety tips for similar users are enabled. -- $false: Safety tips for similar users are disabled. This is the default value. +- $false: Safety tips for similar users are disabled. This value is the default. ```yaml Type: Boolean @@ -418,7 +418,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableTargetedDomainsProtection parameter specifies whether to enable domain impersonation protection for a list of specified domains. Valid values are: - $true: Domain impersonation protection is enabled for the domains specified by the TargetedDomainsToProtect parameter. -- $false: The TargetedDomainsToProtect parameter isn't used. This is the default value. +- $false: The TargetedDomainsToProtect parameter isn't used. This value is the default. ```yaml Type: Boolean @@ -441,7 +441,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableTargetedUserProtection parameter specifies whether to enable user impersonation protection for a list of specified users. Valid values are: - $true: User impersonation protection is enabled for the users specified by the TargetedUsersToProtect parameter. -- $false: The TargetedUsersToProtect parameter isn't used. This is the default value. +- $false: The TargetedUsersToProtect parameter isn't used. This value is the default. ```yaml Type: Boolean @@ -463,7 +463,7 @@ This setting is part of spoof protection. The EnableUnauthenticatedSender parameter enables or disables unauthenticated sender identification in Outlook. Valid values are: -- $true: This is the default value. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication. +- $true: This value is the default. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication. - $false: A question mark is never applied to the sender's photo. To prevent these identifiers from being added to messages from specific senders, you have the following options: @@ -492,7 +492,7 @@ This setting is part of impersonation protection and is available only in Micros The EnableUnusualCharactersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for unusual characters in domain and user impersonation detections. Valid values are: - $true: Safety tips for unusual characters are enabled. -- $false: Safety tips for unusual characters are disabled. This is the default value. +- $false: Safety tips for unusual characters are disabled. This value is the default. ```yaml Type: Boolean @@ -514,7 +514,7 @@ This setting is part of spoof protection. The EnableViaTag parameter enables or disables adding the via tag to the From address in Outlook (chris@contso.com via fabrikam.com). Valid values are: -- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This is the default value. +- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This value is the default. - $false: The via tag is not added to the From address. To prevent the via tag from being added to messages from specific senders, you have the following options: @@ -588,7 +588,7 @@ This setting is part of spoof protection. The HonorDmarcPolicy enables or disables using the sender's DMARC policy to determine what to do to messages that fail DMARC checks. Valid values are: -- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This is the default value. +- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This value is the default. - $false: If the message fails DMARC, ignore the action in the sender's DMARC policy. The AuthenticationFailAction parameter specifies the action to take on the message. ```yaml @@ -611,8 +611,8 @@ This setting is part of impersonation protection and is available only in Micros The ImpersonationProtectionState parameter specifies the configuration of impersonation protection. Valid values are: -- Automatic: This is the default value in the default policy named Office365 AntiPhish Policy. -- Manual: This is the default value in custom policies that you create. +- Automatic: This value is the default in the default policy named Office365 AntiPhish Policy. +- Manual: This value is the default in custom policies that you create. - Off ```yaml @@ -635,7 +635,7 @@ This setting is part of impersonation protection and is available only in Micros The MailboxIntelligenceProtectionAction parameter specifies what to do with messages that fail mailbox intelligence protection. Valid values are: -- NoAction: This is the default value. Note that this value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true. +- NoAction: This value is the default. This value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true. - BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. @@ -736,7 +736,7 @@ This setting is part of advanced settings and is available only in Microsoft Def The PhishThresholdLevel parameter specifies the tolerance level that's used by machine learning in the handling of phishing messages. Valid values are: -- 1: Standard: This is the default value. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied. +- 1: Standard: This value is the default. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied. - 2: Aggressive: Messages that are identified as phishing with a high degree of confidence are treated as if they were identified with a very high degree of confidence. - 3: More aggressive: Messages that are identified as phishing with a medium or high degree of confidence are treated as if they were identified with a very high degree of confidence. - 4: Most aggressive: Messages that are identified as phishing with a low, medium, or high degree of confidence are treated as if they were identified with a very high degree of confidence. @@ -829,7 +829,7 @@ This setting is part of impersonation protection and is available only in Micros The TargetedDomainProtectionAction parameter specifies the action to take on detected domain impersonation messages. You specify the protected domains in the TargetedDomainsToProtect parameter. Valid values are: -- NoAction: This is the default value. +- NoAction: This value is the default. - BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message, and deliver the message to the Junk Email folder of all (original + BCC-ed) recipients' mailboxes. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. @@ -930,7 +930,7 @@ This setting is part of impersonation protection and is available only in Micros The TargetedUserProtectionAction parameter specifies the action to take on detected user impersonation messages. You specify the protected users in the TargetedUsersToProtect parameter. Valid values are: -- NoAction: This is the default value. +- NoAction: This value is the default. - BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md index d3b9cfe74d..e84298092e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md @@ -42,7 +42,7 @@ Set-AntiPhishRule [-Identity] > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Common policy settings](https://learn.microsoft.com/defender-office-365/anti-phishing-policies-about#common-policy-settings). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-App.md b/exchange/exchange-ps/ExchangePowerShell/Set-App.md index 5c05af8d3d..4fe9357f89 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-App.md @@ -13,7 +13,7 @@ title: Set-App # Set-App ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-App cmdlet to modify the availability of organization apps. @@ -36,13 +36,13 @@ Set-App [-Identity] ``` ## DESCRIPTION -The Set-App cmdlet can only be used when configuring the availability of an organization app. This task requires that the specified app has already been installed (for example, that the app has been installed with the New-App cmdlet, or that it's a default app for Outlook). +The Set-App cmdlet can only be used when configuring the availability of an organization app. This task requires that the specified app has already been installed (for example, that the app is installed with the New-App cmdlet, or that it's a default app for Outlook). Default apps in Outlook on the web and apps that you've installed for use by users in your organization are known as organization apps. Organization apps can't be removed by end users, but can be enabled or disabled. If an app is an organization app (scope default or organization), the delete control on the toolbar is disabled for end users. Administrators are able to remove organization apps. Administrators can't remove default apps, but they can disable them for the entire organization. For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -110,7 +110,7 @@ Accept wildcard characters: False The DefaultStateForUser parameter specifies the default initial state of the organization app for the specified users. Valid values are: - Enabled: The organization app is enabled. -- Disabled: The organization app is disabled. This is the default value. +- Disabled: The organization app is disabled. This value is the default. - AlwaysEnabled: The organization app is enabled, and users can't disable it. You use this parameter with the OrganizationApp switch. @@ -153,7 +153,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the app is available to users in the organization. Valid values are: -- $true: The app is enabled for the specified users. This is the default value. +- $true: The app is enabled for the specified users. This value is the default. - $false: The app isn't enabled for any users in the organization. This hides the app from user view for all users. This setting overrides the ProvidedTo, UserList, and DefaultStateForUser settings. This setting doesn't prevent users from installing their own instance of the app if they have install permissions. @@ -212,8 +212,8 @@ Accept wildcard characters: False The ProvidedTo parameter specifies the availability of the app in your organization. Valid value are: -- Everyone: The app is provided to every user in the organization. This is the default value. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions. -- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor will it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app. +- Everyone: The app is provided to every user in the organization. This value is the default. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions. +- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor does it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app. You use this parameter with the OrganizationApp switch. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md index 4830d65dc5..8d42672ef9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md @@ -431,7 +431,7 @@ A valid value is a JSON string. Refer to the Examples section for syntax and usa For information about the inactive mailbox scenario, see [Learn about inactive mailboxes](https://learn.microsoft.com/purview/inactive-mailboxes-in-office-365). -**CAUTION**: This parameter uses the SMTP address of the deleted mailbox or mail user, which might also be specified for other mailboxes or mail users. If you use this parameter without first taking additional steps, other mailboxes and mail users with the same SMTP address in the retention policy will also be excluded. To check for additional mailboxes or mail users with the same SMTP address, use the following command and replace `user@contoso.com` with the SMTP address to check: `Get-Recipient -IncludeSoftDeletedRecipients user@contoso.com | Select-Object DisplayName, EmailAddresses, Description, Alias, RecipientTypeDetails, WhenSoftDeleted` +**CAUTION**: This parameter uses the SMTP address of the deleted mailbox or mail user, which might also be specified for other mailboxes or mail users. If you use this parameter without first taking additional steps, other mailboxes and mail users with the same SMTP address in the retention policy are also excluded. To check for additional mailboxes or mail users with the same SMTP address, use the following command and replace `user@contoso.com` with the SMTP address to check: `Get-Recipient -IncludeSoftDeletedRecipients user@contoso.com | Select-Object DisplayName, EmailAddresses, Description, Alias, RecipientTypeDetails, WhenSoftDeleted` To prevent active mailboxes or mail users with the same SMTP address from being excluded, put the mailbox on [Litigation Hold](https://learn.microsoft.com/purview/ediscovery-create-a-litigation-hold) before you run the command with the DeletedResources parameter. @@ -453,7 +453,7 @@ Accept wildcard characters: False The Enabled parameter enables or disables the policy. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml @@ -655,9 +655,9 @@ Accept wildcard characters: False The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for the policy. Valid values are: - $true: Preservation Lock is enabled for the policy. No one -- including an administrator -- can turn off the policy or make it less restrictive. -- $false: Preservation Lock isn't enabled for the policy. This is the default value. +- $false: Preservation Lock isn't enabled for the policy. This value is the default. -After a policy has been locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. +After a policy is locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off. Therefore, before you lock a policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md index 94ac093cd4..1e3923865e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md @@ -195,7 +195,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: +The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter doesn't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: - IPM.Note.Microsoft.Conversation - IPM.Note.Microsoft.Conversation.Voice @@ -206,7 +206,7 @@ The ExcludedItemClasses parameter specifies the types of messages to exclude fro - IPM.Note.Microsoft.Voicemail.UM - IPM.Note.Microsoft.Voicemail.UM.CA -Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. Note that the values you specify aren't validated, so the parameter accepts any text value. +Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. The values you specify aren't validated, so the parameter accepts any text value. You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`. @@ -296,7 +296,7 @@ The RetentionDurationDisplayHint parameter specifies the units that are used to - Months - Years -For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration. ```yaml Type: HoldDurationHint diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md index eef7ce2879..b2e7429a58 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md @@ -32,7 +32,7 @@ Set-ApplicationAccessPolicy [-Identity] ## DESCRIPTION This feature applies only to apps connecting to the Microsoft Graph API for Outlook resources. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Set-ArcConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md index 8b419a49ce..9bbb3811d5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md @@ -31,7 +31,7 @@ Set-ArcConfig [-Identity] -ArcTrustedS ## DESCRIPTION Services that modify message content in transit before delivery can invalidate DKIM email signatures and affect the authentication of the message. These services can use ARC to provide details of the original authentication before the modifications occurred. Your organization can then trust these details to help authenticate the message. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Set-AtpPolicyForO365.md b/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md index 5f93a93d5c..4b4654ecbd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md @@ -42,7 +42,7 @@ Safe Documents scans documents and files that are opened in Protected View. For Safe Attachments for SharePoint, OneDrive, and Microsoft Teams prevents users from opening and downloading files that are identified as malicious. For more information, see [Safe Attachments for SharePoint, OneDrive, and Microsoft Teams](https://learn.microsoft.com/defender-office-365/safe-attachments-for-spo-odfb-teams-about). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,7 +79,7 @@ Accept wildcard characters: False The AllowSafeDocsOpen parameter specifies whether users can click through and bypass the Protected View container even when Safe Documents identifies a file as malicious. Valid values are: -- $true: Users are allowed to exit the Protected View container even if the document has been identified as malicious. +- $true: Users are allowed to exit the Protected View container even if the document is identified as malicious. - $false: Users aren't allowed to exit Protected View in case of a malicious detection. This parameter is meaningful only when the EnableSafeDocs parameter value is $true. @@ -124,7 +124,7 @@ Accept wildcard characters: False The EnableATPForSPOTeamsODB parameter enables or disables Safe Attachments for SharePoint, OneDrive, and Microsoft Teams. Valid values are: - $true: Safe Attachments for SharePoint, OneDrive, and Microsoft Teams is enabled. SharePoint admins can use the DisallowInfectedFileDownload parameter on the [Set-SPOTenant](https://learn.microsoft.com/powershell/module/sharepoint-online/Set-SPOTenant) cmdlet to control whether users are allowed to download files that are found to be malicious. -- $false: Safe Attachments for SharePoint, OneDrive, and Microsoft Teams is disabled. This is the default value. +- $false: Safe Attachments for SharePoint, OneDrive, and Microsoft Teams is disabled. This value is the default. ```yaml Type: Boolean @@ -144,8 +144,8 @@ Accept wildcard characters: False The EnableSafeDocs parameter enables or disables Safe Documents in organizations with Microsoft 365 A5 or Microsoft 365 E5 Security licenses. Valid values are: -- $true: Safe Documents is enabled and will upload user files to Microsoft Defender for Endpoint for scanning and verification. -- $false: Safe Documents is disabled. This is the default value. +- $true: Safe Documents is enabled and uploads user files to Microsoft Defender for Endpoint for scanning and verification. +- $false: Safe Documents is disabled. This value is the default. For more information about Safe Documents, see [Safe Documents in Microsoft 365 A5 or E5 Security](https://learn.microsoft.com/defender-office-365/safe-documents-in-e5-plus-security-about) diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md index 1c317461b0..40c8190235 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md @@ -55,7 +55,7 @@ This example modifies the action that the Attachment Filtering agent takes on an The Action parameter specifies how the Attachment Filtering agent handles an attachment that matches an entry on the attachment filter list. Valid values are: -- Reject: This value prevents both the email message and attachment from being delivered to the recipient and issues a non-delivery report (NDR) to the sender. This is the default value. +- Reject: This value prevents both the email message and attachment from being delivered to the recipient and issues a non-delivery report (NDR) to the sender. This value is the default. - Strip: This value removes the offending attachment from the email message and allows the message and other attachments that don't match an entry on the attachment filter list through. A notification that the attachment was removed is added to the email message. - SilentDelete: This value prevents both the email message and the attachment from being delivered to the recipient. No notification that the email message and attachment were blocked is sent to the sender. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md index ab3ba426ba..8bdf7d268b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md @@ -70,7 +70,7 @@ Set-AuthConfig [-Realm ] ## DESCRIPTION The Set-AuthConfig parameter defines Microsoft Exchange as a partner application for server-to-server authentication with other partner applications such as Microsoft SharePoint 2013 and Microsoft Lync 2013 or Skype for Business Server 2015, including the certificate used for signing tokens. It's generally not required for this configuration to be modified except in some cases where you must use a different certificate instead of the self-signed certificate created by Exchange Setup or to use a new certificate after the old one has expired. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,7 +79,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Set-AuthConfig -NewCertificateThumbprint DB821B4FCA2A5DA9593B9DE00C86BC5EA35D0FC0 -NewCertificateEffectiveDate 4/17/2014 ``` -This example specifies a new certificate and a date when the certificate will become effective. +This example specifies a new certificate and a date when the certificate is effective. ### Example 2 ```powershell diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md index 8facbc23d1..f23fcfa6f2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md @@ -31,7 +31,7 @@ Set-AuthRedirect [-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 @@ -112,7 +112,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The TargetUrl parameter specifies the FQDN of the Exchange 2013 Client Access server that will process the Oauth request. +The TargetUrl parameter specifies the FQDN of the Exchange 2013 Client Access server that processes the Oauth request. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md index 9086e663d8..5419f5f7de 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md @@ -81,7 +81,7 @@ Partner applications authorized by Exchange can access their resources after the Use the Set-AuthServer cmdlet to enable or disable the authorization server, change the AuthMetadataUrl parameter or refresh authorization metadata. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -199,9 +199,9 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2016 (CU18 or higher) and Exchange Server 2019 (CU7 or higher). -The DomainName parameter specifies the tenant domain that's linked with the AuthServer object. This parameter uses the syntax: "tenantname.onmicrosoft.com". +The DomainName parameter links a cloud-based organization to the corresponding AuthServer object in the Multi-Tenant Exchange Hybrid. This parameter uses the syntax: "domain.onmicrosoft.com". -This parameter is used to link Tenant to the corresponding authserver object in the Multi-Tenant Exchange Hybrid. For example, if DomainName is contoso.onmicrosoft.com, then the AuthServer object will be associated with the contoso tenant. +For example, if the DomainName value is contoso.onmicrosoft.com, the AuthServer object is associated with the contoso cloud-based organization. ```yaml Type: MultiValuedProperty @@ -223,7 +223,7 @@ The Enabled parameter specifies whether the authorization server is enabled. Onl The Enabled parameter specifies whether the authorization server is enabled. Valid values are: -- $true: Authorization tokens that are issued by the authorization server are accepted. This is the default value +- $true: Authorization tokens that are issued by the authorization server are accepted. This value is the default - $false: The authorization server does not issue or accept authorization tokens. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md index 480c57c088..cf7790c298 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md @@ -13,7 +13,7 @@ title: Set-AuthenticationPolicy # Set-AuthenticationPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-AuthenticationPolicy cmdlet to modify authentication policies in your organization. @@ -60,7 +60,7 @@ Set-AuthenticationPolicy [-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 @@ -616,7 +616,7 @@ The switch applies to the entire organization. The Identity parameter is require - Legacy Exchange Online tokens will be turned off for all organizations from August 2025 through September 2025. Once turned off, you can't use the _AllowLegacyExchangeTokens_ switch on the **Set-AuthenticationPolicy** cmdlet to turn on these tokens. You get the warning "Legacy Exchange Online tokens are disabled" when you run the command `Get-AuthenticationPolicy -AllowLegacyExchangeTokens`. You can [contact Microsoft Support to request an exception](https://aka.ms/LegacyTokensByOctober). For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). - Apart from the Identity parameter, this switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. - It might take up to 24 hours for the change to take effect across your entire organization. -- Legacy Exchange tokens issued to Outlook add-ins before token blocking was implemented in your organization will remain valid until they expire. +- Legacy Exchange tokens issued to Outlook add-ins before token blocking was implemented in your organization remain valid until they expire. - Blocking legacy Exchange tokens might cause some Microsoft add-ins to stop working. These add-ins are being updated to no longer use legacy tokens. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md index 7c95423e8b..e8c95a366c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md @@ -129,7 +129,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The AddExchangeLocation parameter adds email messages to the policy if they're not already included. The valid value for this parameter is All. +The AddExchangeLocation parameter adds email messages to the policy if they aren't already included. The valid value for this parameter is All. If the policy doesn't already include email messages (in the output of the Get-AutoSensitivityLabelPolicy cmdlet, the ExchangeLocation property value is blank), you can use this parameter in the following procedures: @@ -243,7 +243,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The ApplySensitivityLabel parameter selects which label to be used for the policy. This will override the previous label on the policy. +The ApplySensitivityLabel parameter selects the label to use for the policy. This value overrides the previous label on the policy. ```yaml Type: String @@ -326,7 +326,7 @@ Accept wildcard characters: False The Enabled parameter enables or disables the policy. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml @@ -706,7 +706,7 @@ Accept wildcard characters: False The OverwriteLabel parameter specifies whether to overwrite a manual label. Valid values are: - $true: Overwrite the manual label. -- $false: Don't overwrite the manual label. This is the default value. +- $false: Don't overwrite the manual label. This value is the default. This parameter works only on Exchange locations. @@ -974,7 +974,7 @@ Accept wildcard characters: False Use the StartSimulation parameter to restart the simulation for updated results. Valid values are: - $true: Restart the simulation for updated results. **Any edits to an auto-labeling policy require restarting the simulation by using this value.** -- $false: This is the default value +- $false: This value is the default ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md index a41e2735f2..ee05901854 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md @@ -335,7 +335,7 @@ Accept wildcard characters: False The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are: - $true: The rule is disabled. -- $false: The rule is enabled. This is the default value. +- $false: The rule is enabled. This value is the default. ```yaml Type: Boolean @@ -446,7 +446,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this condition in auto-labeling policy rules that are scoped only to Exchange. @@ -689,7 +689,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this exception in auto-labeling policy rules that are scoped only to Exchange. @@ -1158,7 +1158,7 @@ Accept wildcard characters: False The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are: - None: You can't select this value if the rule has no actions configured. -- Low: This is the default value. +- Low: This value is the default. - Medium - High @@ -1183,7 +1183,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du - Ignore - RetryThenBlock -- Blank (the value $null): This is the default value. +- Blank (the value $null): This value is the default. ```yaml Type: PolicyRuleErrorAction diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md index d079983959..ca01c30e74 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md @@ -40,7 +40,7 @@ Set-AutodiscoverVirtualDirectory [-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 @@ -97,7 +97,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. ```yaml @@ -140,7 +140,7 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. -- $false: Digest authentication is disabled. This is the default value. +- $false: Digest authentication is disabled. This value is the default. ```yaml Type: Boolean @@ -182,7 +182,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -202,7 +202,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -223,8 +223,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -287,7 +287,7 @@ Accept wildcard characters: False The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are: -- $true: OAuth authentication is enabled. This is the default value. +- $true: OAuth authentication is enabled. This value is the default. - $false: OAuth authentication is disabled. ```yaml @@ -326,7 +326,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -- $true: Integrated Windows authentication is enabled. This is the default value. +- $true: Integrated Windows authentication is enabled. This value is the default. - $false: Integrated Windows authentication is disabled. ```yaml @@ -347,7 +347,7 @@ Accept wildcard characters: False The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are: -- $true: WS-Security authentication is enabled. This is the default value. +- $true: WS-Security authentication is enabled. This value is the default. - $false: WS-Security authentication is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md index 2364adde75..1eb3727049 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md @@ -13,7 +13,7 @@ title: Set-AvailabilityConfig # Set-AvailabilityConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-AvailabilityConfig cmdlet to set the access level for free/busy information. @@ -39,7 +39,7 @@ For cross-forest availability services to retrieve free/busy information in the In Exchange Online, this cmdlet lets you update the set of tenant ids that free/busy information sharing is allowed with. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Set-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md index 7ff6054fec..6920c4e782 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md @@ -46,7 +46,7 @@ Set-AvailabilityReportOutage [-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/Set-CASMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md index 9a16d536b4..e4545c1e31 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md @@ -13,7 +13,7 @@ title: Set-CASMailbox # Set-CASMailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-CASMailbox cmdlet to configure client access settings on a mailbox. For example, you can configure settings for Exchange ActiveSync, Outlook, Outlook on the web, POP3, and IMAP4. @@ -81,7 +81,7 @@ Set-CASMailbox [-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 @@ -192,7 +192,7 @@ Accept wildcard characters: False The ActiveSyncDebugLogging parameter enables or disables Exchange ActiveSync debug logging for the mailbox. Valid values are: - $true: ActiveSync debug logging is enabled for 48 hours in Exchange Online, and 72 hours in Exchange Server. After the time period expires, the value reverts to $false. -- $false: ActiveSync debug logging is disabled. This is the default value +- $false: ActiveSync debug logging is disabled. This value is the default ```yaml Type: Boolean @@ -212,7 +212,7 @@ Accept wildcard characters: False The ActiveSyncEnabled parameter enables or disables access to the mailbox using Exchange ActiveSync. Valid values are: -- $true: Access to the mailbox using ActiveSync is enabled. This is the default value. +- $true: Access to the mailbox using ActiveSync is enabled. This value is the default. - $false. Access to the mailbox using ActiveSync is disabled. Other ActiveSync settings in this cmdlet are ignored. For more information, see [Enable or disable Exchange ActiveSync for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-exchange-activesync), or [Enable or disable Exchange ActiveSync access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/exchange-activesync/activesync-mailbox-access). @@ -260,7 +260,7 @@ Accept wildcard characters: False The ActiveSyncSuppressReadReceipt parameter controls the behavior of read receipts for Exchange ActiveSync clients that access the mailbox. Valid values are: - $true: Read receipts are not automatically returned when the user opens a message sent with a read receipt request. -- $false: A read receipt is automatically returned when the user opens a message sent with a read receipt request. This is the default value. +- $false: A read receipt is automatically returned when the user opens a message sent with a read receipt request. This value is the default. ```yaml Type: Boolean @@ -343,7 +343,7 @@ This parameter is available only in on-premises Exchange. The ECPEnabled parameter enables or disables access the Exchange admin center (EAC) or the Exchange Control Panel (ECP) for the specified user. Valid values are: -- $true: Access to the EAC or ECP is enabled. This is the default value. +- $true: Access to the EAC or ECP is enabled. This value is the default. - $false: Access to the EAC or ECP is disabled. ```yaml @@ -403,7 +403,7 @@ Accept wildcard characters: False The EwsAllowEntourage parameter enables or disables access to the mailbox by Microsoft Entourage clients that use Exchange Web Services (for example, Entourage 2008 for Mac, Web Services Edition). -- $true: Access to the mailbox using Microsoft Entourage is enabled. This is the default value. +- $true: Access to the mailbox using Microsoft Entourage is enabled. This value is the default. - $false: Access to the mailbox using Microsoft Entourage is disabled. ```yaml @@ -448,7 +448,7 @@ Accept wildcard characters: False The EwsAllowMacOutlook parameter enables or disables access to the mailbox by Outlook for Mac clients that use Exchange Web Services (for example, Outlook for Mac 2011 or later). Valid values are: -- $true: Outlook for Mac clients that use EWS are allowed to access the mailbox. This is the default value. +- $true: Outlook for Mac clients that use EWS are allowed to access the mailbox. This value is the default. - $false: Outlook for Mac clients that use EWS are not allowed to access the mailbox. In the cloud-based service, access for Outlook for Mac clients that use Microsoft Sync technology is controlled by the MacOutlookEnabled parameter. @@ -541,7 +541,7 @@ Accept wildcard characters: False The EwsEnabled parameter enables or disables access to the mailbox using Exchange Web Services clients. Valid values are: -- $true: Access to the mailbox using EWS is enabled. This is the default value. +- $true: Access to the mailbox using EWS is enabled. This value is the default. - $false: Access to the mailbox using EWS is disabled. Other Exchange Web Services settings in this cmdlet are ignored. The value of this parameter is meaningful only if the EwsEnabled parameter on the Set-OrganizationConfig parameter isn't set to the value $false. @@ -612,7 +612,7 @@ Accept wildcard characters: False The ImapEnabled parameter enables or disables access to the mailbox using IMAP4 clients. Valid values are: -- $true: Access to the mailbox using IMAP4 is enabled. This is the default value. +- $true: Access to the mailbox using IMAP4 is enabled. This value is the default. - $fale: Access to the mailbox using IMAP4 is disabled. The other IMAP4 settings in this cmdlet are ignored. For more information, see [Enable or Disable POP3 or IMAP4 access for a user in Exchange Online](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/pop3-and-imap4/enable-or-disable-pop3-or-imap4-access), or [Enable or disable POP3 or IMAP4 access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/pop3-and-imap4/configure-mailbox-access). @@ -638,7 +638,7 @@ This parameter is available only in on-premises Exchange. The ImapEnableExactRFC822Size parameter specifies how message sizes are presented to IMAP4 clients that access the mailbox. Valid values are: - $true: Calculate the exact message size. -- $false: Use an estimated message size. This is the default value. +- $false: Use an estimated message size. This value is the default. We don't recommend changing this value unless you determine that the default setting causes problems for IMAP4 clients. To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $false. @@ -661,7 +661,7 @@ Accept wildcard characters: False The ImapForceICalForCalendarRetrievalOption parameter specifies how meeting requests are presented to IMAP4 clients that access the mailbox. Valid values are: - $true: All meeting requests are in the iCal format. -- $false: All meeting requests appear as Outlook on the web links. This is the default value. +- $false: All meeting requests appear as Outlook on the web links. This value is the default. To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $false. @@ -712,7 +712,7 @@ Accept wildcard characters: False The ImapSuppressReadReceipt parameter controls the behavior of read receipts for IMAP4 clients that access the mailbox. Valid values are: - $true: The user receives a read receipt when the recipient opens the message. -- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. This is the default value. +- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. This value is the default. To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $false. @@ -734,7 +734,7 @@ Accept wildcard characters: False The ImapUseProtocolDefaults parameter specifies whether to use the IMAP4 protocol defaults for the mailbox. Valid values are: -- $true: Use the protocol defaults for IMAP4 access to the mailbox. This is the default value. +- $true: Use the protocol defaults for IMAP4 access to the mailbox. This value is the default. - $false: Use custom protocol settings for IMAP4 access to the mailbox. You need to set this parameter to $false when you use any of the following IMAP4 parameters: @@ -787,7 +787,7 @@ This parameter is available only in the cloud-based service. The MacOutlookEnabled parameter enables or disables access to the mailbox using Outlook for Mac clients that use Microsoft Sync technology. Valid values are: -- $true: Access to the mailbox using Outlook for Mac clients is enabled. This is the default value. +- $true: Access to the mailbox using Outlook for Mac clients is enabled. This value is the default. - $false: Access to the mailbox using Outlook for Mac clients is disabled. Access for older Outlook for Mac clients that use Exchange Web Services is controlled by the EwsAllowMacOutlook parameter. @@ -813,7 +813,7 @@ This parameter is available only in on-premises Exchange. The MAPIBlockOutlookNonCachedMode parameter controls access to the mailbox using Outlook in online or offline mode. Valid values are: - $true: Only Outlook clients that are configured to use Cached Exchange Mode (offline mode) are allowed to access the mailbox. -- $false: The state of the Cached Exchange Mode setting isn't checked before Outlook clients are allowed to access the mailbox (online mode and offline mode are allowed). This is the default value. +- $false: The state of the Cached Exchange Mode setting isn't checked before Outlook clients are allowed to access the mailbox (online mode and offline mode are allowed). This value is the default. ```yaml Type: Boolean @@ -838,7 +838,7 @@ The MAPIBlockOutlookExternalConnectivity parameter enables or disables external - $true: External Outlook clients can't use Outlook Anywhere, MAPI over HTTP, or EWS to access the mailbox. - $false: External Outlook clients can use Outlook Anywhere, MAPI over HTTP, or EWS to access the mailbox. -**Note**: If your organization uses the same Autodiscover URL values for internal and external clients, setting this parameter to $true won't block access for external clients. +**Note**: If your organization uses the same Autodiscover URL values for internal and external clients, setting this parameter to $true doesn't block access for external clients. ```yaml Type: Boolean @@ -861,7 +861,7 @@ This parameter is available only in on-premises Exchange. The MAPIBlockOutlookRpcHttp parameter enables or disables access to the mailbox in Outlook using Outlook Anywhere. Valid values are: - $true: Access to the mailbox using Outlook Anywhere is disabled. -- $false: Access to the mailbox using Outlook Anywhere is enabled. This is the default value. +- $false: Access to the mailbox using Outlook Anywhere is enabled. This value is the default. ```yaml Type: Boolean @@ -905,7 +905,7 @@ Accept wildcard characters: False The MAPIEnabled parameter enables or disables access to the mailbox using MAPI clients (for example, Outlook). Valid values are: -- $true: Access to the mailbox using MAPI clients is enabled. This is the default value. +- $true: Access to the mailbox using MAPI clients is enabled. This value is the default. - $false: Access to the mailbox using MAPI clients is disabled. The other MAPI settings in this cmdlet are ignored. For more information, see[Enable or disable MAPI for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-mapi), or [Enable or disable MAPI access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/mapi-mailbox-access). @@ -932,7 +932,7 @@ The MapiHttpEnabled parameter enables or disables access to the mailbox in Outlo - $true: Access to the mailbox using MAPI over HTTP is enabled. - $false: Access to the mailbox using MAPI over HTTP is disabled. -- $null (blank): The setting isn't configured. The mailbox uses the organization setting for MAPI over HTTP (the MapiHttpEnabled parameter on the Set-OrganizationConfig cmdlet). This is the default value. +- $null (blank): The setting isn't configured. The mailbox uses the organization setting for MAPI over HTTP (the MapiHttpEnabled parameter on the Set-OrganizationConfig cmdlet). This value is the default. ```yaml Type: Boolean @@ -975,7 +975,7 @@ This parameter is available only in the cloud-based service. The OneWinNativeOutlookEnabled parameter enables or disables access to the mailbox using the new Outlook for Windows. Valid values are: -- $true: Access to the mailbox using the new Outlook for Windows is enabled. This is the default value. +- $true: Access to the mailbox using the new Outlook for Windows is enabled. This value is the default. - $false: Access to the mailbox using the new Outlook for Windows is disabled. ```yaml @@ -998,7 +998,7 @@ This parameter is available only in the cloud-based service. The OutlookMobileEnabled parameter enables or disables access to the mailbox using Outlook for iOS and Android. Valid values are: -- $true: Access to the mailbox using Outlook for iOS and Android is enabled. This is the default value. +- $true: Access to the mailbox using Outlook for iOS and Android is enabled. This value is the default. - $false: Access to the mailbox using Outlook for iOS and Android is disabled. ```yaml @@ -1019,7 +1019,7 @@ Accept wildcard characters: False The OWAEnabled parameter enables or disables access to the mailbox using Outlook on the web (formerly known as Outlook Web App or OWA) and the new Outlook for Windows. Valid values are: -- $true: Access to the mailbox using Outlook on the web is enabled. This is the default value. +- $true: Access to the mailbox using Outlook on the web is enabled. This value is the default. - $false: Access to the mailbox using Outlook on the web and the new Outlook for Windows is disabled. The other Outlook on the web settings in this cmdlet are ignored. For more information, see [Enable or disable Outlook on the web for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-outlook-web-app), or [Enable or disable Outlook on the web access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/outlook-on-the-web/mailbox-access). @@ -1042,7 +1042,7 @@ Accept wildcard characters: False The OWAforDevicesEnabled parameter enables or disables access to the mailbox using the older Outlook Web App (OWA) app on iOS and Android devices. Valid values are: -- $true: Access to the mailbox using OWA for Devices is enabled. This is the default value. +- $true: Access to the mailbox using OWA for Devices is enabled. This value is the default. - $false: Access to the mailbox using OWA for Devices is disabled. ```yaml @@ -1087,7 +1087,7 @@ Accept wildcard characters: False The PopEnabled parameter enables or disables access to the mailbox using POP3 clients. Valid values are: -- $true: Access to the mailbox using POP3 clients is enabled. This is the default value. +- $true: Access to the mailbox using POP3 clients is enabled. This value is the default. - $false: Access to the mailbox using POP3 clients is disabled. The other POP3 settings in this cmdlet are ignored. For more information, see [Enable or Disable POP3 or IMAP4 access for a user in Exchange Online](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/pop3-and-imap4/enable-or-disable-pop3-or-imap4-access), or [Enable or disable POP3 or IMAP4 access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/pop3-and-imap4/configure-mailbox-access). @@ -1113,7 +1113,7 @@ This parameter is available only in on-premises Exchange. The PopEnableExactRFC822Size parameter specifies how message sizes are presented to POP3 clients that access the mailbox. Valid values are: - $true: Calculate the exact message size. -- $false: Use an estimated message size. This is the default value +- $false: Use an estimated message size. This value is the default We don't recommend changing this value unless you determine that the default setting causes problems for POP3 clients. To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $false. @@ -1136,7 +1136,7 @@ Accept wildcard characters: False The PopForceICalForCalendarRetrievalOption parameter specifies how meeting requests are presented to POP3 clients that access the mailbox. Valid values are: - $true: All meeting requests are in the iCal format. -- $false: All meeting requests appear as Outlook on the web links. This is the default value. +- $false: All meeting requests appear as Outlook on the web links. This value is the default. To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $false. @@ -1187,7 +1187,7 @@ Accept wildcard characters: False The PopSuppressReadReceipt parameter controls the behavior of read receipts for POP3 clients that access the mailbox. Valid values are: - $true: The user receives a read receipt when the recipient opens the message. -- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. This is the default value. +- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. This value is the default. To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $false. @@ -1209,7 +1209,7 @@ Accept wildcard characters: False The PopUseProtocolDefaults parameter specifies whether to use the POP3 protocol defaults for the mailbox. Valid values are: -- $true: Use the protocol defaults for POP3 access to the mailbox. This is the default value. +- $true: Use the protocol defaults for POP3 access to the mailbox. This value is the default. - $false: Use custom protocol settings for POP3 access to the mailbox. You need to set this parameter to $false when you use any of following parameters: @@ -1258,7 +1258,7 @@ Accept wildcard characters: False The PublicFolderClientAccess parameter enables or disables access to public folders in Microsoft Outlook. Valid values are: - $true: The user can access public folders in Outlook if the value of the PublicFolderShowClientControl parameter on the Set-OrganizationConfig cmdlet is $true (the default value is $false). -- $false: The user can't access public folders in Outlook if the value of the PublicFolderShowClientControl parameter on the Set-OrganizationConfig cmdlet is $true. This is the default value. +- $false: The user can't access public folders in Outlook if the value of the PublicFolderShowClientControl parameter on the Set-OrganizationConfig cmdlet is $true. This value is the default. ```yaml Type: Boolean @@ -1298,7 +1298,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -1318,7 +1318,7 @@ Accept wildcard characters: False The ShowGalAsDefaultView parameter specifies whether the global address list (GAL) is the default recipient picker for messages. Valid values are: -- $true: Use the GAL as the primary address picker. This is the default value. +- $true: Use the GAL as the primary address picker. This value is the default. - $false: Don't use the GAL as the primary address picker. ```yaml @@ -1350,7 +1350,7 @@ Valid values for this parameter are: - $true: Authenticated SMTP is disabled for the mailbox. - $false: Authenticated SMTP is enabled for the mailbox. -- blank ($null): This is the default value. The authenticated SMTP setting for the mailbox is controlled by the corresponding SmtpClientAuthenticationDisabled parameter on the Set-TransportConfig cmdlet for the whole organization. +- blank ($null): This value is the default. The authenticated SMTP setting for the mailbox is controlled by the corresponding SmtpClientAuthenticationDisabled parameter on the Set-TransportConfig cmdlet for the whole organization. To selectively enable authenticated SMTP for specific mailboxes only: disable authenticated SMTP at the organizational level ($true), enable it for the specific mailboxes ($false), and leave the rest of the mailboxes with their default value ($null). @@ -1374,7 +1374,7 @@ This parameter is available only in the cloud-based service. The UniversalOutlookEnabled parameter enables or disables access to the mailbox using Windows 10 Mail and Calendar. Valid values are: -- $true: Access to the mailbox using Windows 10 Mail and Calendar is enabled. This is the default value. +- $true: Access to the mailbox using Windows 10 Mail and Calendar is enabled. This value is the default. - $false: Access to the mailbox using Windows 10 Mail and Calendar is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md index d755e6ec94..d7570a544d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md @@ -39,7 +39,7 @@ Set-CASMailboxPlan [-Identity] ## DESCRIPTION A CAS mailbox plan is tied to the corresponding mailbox plan that has the same name (and display name). Like mailbox plans, CAS mailbox plans correspond to license types, and are applied to a mailbox when you license the user. The availability of a CAS mailbox plan is determined by your selections when you enroll in the service and the age of your 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 @@ -82,7 +82,7 @@ Accept wildcard characters: False The ActiveSyncEnabled parameter enables or disables access to the mailbox by using Exchange Active Sync (EAS). Valid values are: -- $true: ActiveSync access to the mailbox is enabled. This is the default value. +- $true: ActiveSync access to the mailbox is enabled. This value is the default. - $false: ActiveSync access to the mailbox is disabled. ```yaml @@ -243,7 +243,7 @@ Accept wildcard characters: False The PopEnabled parameter enables or disables access to the mailbox by using POP3 clients. Valid values are: -- $true: POP3 access to the mailbox is enabled. This is the default value. +- $true: POP3 access to the mailbox is enabled. This value is the default. - $false: POP3 access to the mailbox is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md index 21a621c826..c20aafc1af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md @@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange. The Set-CalendarNotification cmdlet allows users to set text message notification options for calendar events in their own calendar. By default, the MyTextMessaging end-user role gives access to this cmdlet, so admins can't configure text messaging notification for calendar events in user calendars. -**Note**: This cmdlet has been deprecated in Exchange Online PowerShell. The text message notification service has been discontinued in Microsoft 365. +**Note**: This cmdlet is deprecated in Exchange Online PowerShell. The text message notification service is discontinued in Microsoft 365. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -42,7 +42,7 @@ Set-CalendarNotification [-Identity] ## DESCRIPTION Users can receive text message notifications of changes to calendar events and daily agendas. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -95,7 +95,7 @@ Accept wildcard characters: False The CalendarUpdateNotification parameter specifies whether calendar update text message notifications are sent to the user's mobile device. Valid values are: - $true: Calendar update text message notifications are enabled. -- $false: Calendar update text message notifications aren't enabled. This is the default value. +- $false: Calendar update text message notifications aren't enabled. This value is the default. ```yaml Type: Boolean @@ -116,7 +116,7 @@ Accept wildcard characters: False The CalendarUpdateSendDuringWorkHour parameter specifies whether calendar update text notifications are sent to the user's mobile device during working hours only. Valid values are: - $true: Calendar update text message notifications are sent during working hours only. -- $false: Calendar update text message notifications are sent anytime. This is the default value. +- $false: Calendar update text message notifications are sent anytime. This value is the default. ```yaml Type: Boolean @@ -158,7 +158,7 @@ Accept wildcard characters: False The DailyAgendaNotification parameter specifies whether daily agenda text message notifications are sent to the user's mobile device. Valid values are: - $true: Daily agenda text message notifications are sent. -- $false: Daily agenda text message notifications aren't sent. This is the default value. +- $false: Daily agenda text message notifications aren't sent. This value is the default. ```yaml Type: Boolean @@ -237,7 +237,7 @@ Accept wildcard characters: False The MeetingReminderNotification parameter specifies whether meeting reminder text message notifications are sent to the user's mobile device. Valid values are: - $true: Meeting reminder text message notifications are sent. -- $false: Meeting reminder text message notifications aren't sent. This is the default value. +- $false: Meeting reminder text message notifications aren't sent. This value is the default. ```yaml Type: Boolean @@ -258,7 +258,7 @@ Accept wildcard characters: False The MeetingReminderSendDuringWorkHour parameter specifies whether meeting reminder text message notifications are sent to the user's mobile device during working hours only. Valid values are: - $true: Meeting update notifications are sent during working hours only. -- $false: Meeting update notifications are sent anytime. This is the default value. +- $false: Meeting update notifications are sent anytime. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md index 6897e1410a..da0a5b0cfd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md @@ -13,9 +13,9 @@ title: Set-CalendarProcessing # Set-CalendarProcessing ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. -Use the Set-CalendarProcessing cmdlet to modify calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant, and calendar configuration. Note that this cmdlet is effective only on resource mailboxes. +Use the Set-CalendarProcessing cmdlet to modify calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant, and calendar configuration. This cmdlet is effective only on resource mailboxes. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -69,7 +69,7 @@ Set-CalendarProcessing [-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 @@ -192,7 +192,7 @@ Accept wildcard characters: False The AddAdditionalResponse parameter specifies whether additional information (the value of the AdditionalResponse parameter) is added to meeting request responses. Valid values are: - $true: Text from the AdditionalResponse parameter is added to meeting request responses. -- $false: No additional text is added to meeting request responses (any text in the AddAdditionalResponse parameter isn't used). This is the default value. +- $false: No additional text is added to meeting request responses (any text in the AddAdditionalResponse parameter isn't used). This value is the default. This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept. @@ -232,7 +232,7 @@ Accept wildcard characters: False The AddNewRequestsTentatively parameter specifies whether new meeting requests are added to the calendar as tentative. Valid values are: -- $true: New calendar items are added to the calendar as tentative. This is the default value. +- $true: New calendar items are added to the calendar as tentative. This value is the default. - $false: Only existing calendar items are updated by the Calendar Attendant. ```yaml @@ -253,7 +253,7 @@ Accept wildcard characters: False The AddOrganizerToSubject parameter specifies whether the meeting organizer's name is used as the subject of the meeting request. Valid values are: -- $true: The meeting organizer's name replaces any existing Subject value for the meeting request. This is the default value. +- $true: The meeting organizer's name replaces any existing Subject value for the meeting request. This value is the default. - $false: The original Subject value is preserved. This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept. @@ -278,7 +278,7 @@ Accept wildcard characters: False The AllBookInPolicy parameter specifies whether to automatically approve in-policy requests from all users to the resource mailbox. Valid values are: -- $true: In-policy requests from all users are automatically approved. This is the default value. +- $true: In-policy requests from all users are automatically approved. This value is the default. - $false: In-policy requests from all users aren't automatically approved (approval by a delegate is required). ```yaml @@ -300,11 +300,11 @@ Accept wildcard characters: False The AllowConflicts parameter specifies whether to allow conflicting meeting requests. Valid values are: - $true: Conflicts are allowed. A recurring meeting series is accepted regardless of whether any occurrences conflict with existing bookings. The values of the ConflictPercentageAllowed or MaximumConflictInstances parameters are ignored. -- $false: Conflicts aren't allowed. This is the default value. Whether an entire series is declined depends on the amount of conflicts in the series: +- $false: Conflicts aren't allowed. This value is the default. Whether an entire series is declined depends on the amount of conflicts in the series: • The series is declined if the number or percentage of conflicts is higher than the ConflictPercentageAllowed or MaximumConflictInstances parameter values. - • The series is accepted, but conflicting occurrences are declined if the number or percentage of conflicts is lower than the ConflictPercentageAllowed or MaximumConflictInstances parameter values. If the EnableResponseDetails parameter value is $true, the organizer will receive a notification email for each declined occurrence. + • The series is accepted, but conflicting occurrences are declined if the number or percentage of conflicts is lower than the ConflictPercentageAllowed or MaximumConflictInstances parameter values. If the EnableResponseDetails parameter value is $true, the organizer receives a notification email for each declined occurrence. ```yaml Type: Boolean @@ -324,7 +324,7 @@ Accept wildcard characters: False The AllowRecurringMeetings parameter specifies whether to allow recurring meetings in meeting requests. Valid values are: -- $true: Recurring meetings are allowed. This is the default value. +- $true: Recurring meetings are allowed. This value is the default. - $false: Recurring meetings aren't allowed. ```yaml @@ -346,7 +346,7 @@ Accept wildcard characters: False The AllRequestInPolicy parameter specifies whether to allow all users to submit in-policy requests to the resource mailbox. Valid values are: - $true: All users are allowed to submit in-policy requests to the resource mailbox. These requests require approval by a resource mailbox delegate if the AllBookInPolicy parameter is set to $false (the default value of AllBookInPolicy is $true). -- $false: All users can't submit in-policy requests to the resource mailbox. This is the default value. +- $false: All users can't submit in-policy requests to the resource mailbox. This value is the default. ```yaml Type: Boolean @@ -367,7 +367,7 @@ Accept wildcard characters: False The AllRequestOutOfPolicy parameter specifies whether to allow all users to submit out-of-policy requests to the resource mailbox. Valid values are: - $true: All users are allowed to submit out-of-policy requests to the resource mailbox. Out-of-policy requests require approval by a resource mailbox delegate. -- $false: All users can't submit out-of-policy requests to the resource mailbox. This is the default value. +- $false: All users can't submit out-of-policy requests to the resource mailbox. This value is the default. ```yaml Type: Boolean @@ -417,7 +417,7 @@ This parameter is available only in the cloud-based service. The BookingType parameter specifies how reservations work on the resource mailbox. Valid values are: -- Standard: The resource can be reserved based on the other settings in this cmdlet. This is the default value +- Standard: The resource can be reserved based on the other settings in this cmdlet. This value is the default - Reserved: The resource can't be reserved. ```yaml @@ -530,7 +530,7 @@ Accept wildcard characters: False The DeleteAttachments parameter specifies whether to remove attachments from all incoming messages. Valid values are: -- $true: Remove any attachments in incoming messages. This is the default value. +- $true: Remove any attachments in incoming messages. This value is the default. - $false: Preserve any attachments in incoming messages. This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept. @@ -553,7 +553,7 @@ Accept wildcard characters: False The DeleteComments parameter specifies whether to remove or keep any text in the message body of incoming meeting requests. Valid values are: -- $true: Remove any text in the message body of incoming meeting requests. This is the default value. +- $true: Remove any text in the message body of incoming meeting requests. This value is the default. - $false: Preserve any text in the message body of incoming meeting requests. This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept. @@ -576,7 +576,7 @@ Accept wildcard characters: False The DeleteNonCalendarItems parameter specifies whether to remove or keep all non-calendar-related messages that are received by the resource mailbox. Valid values are: -- $true: Non-calendar messages are deleted. This is the default value. +- $true: Non-calendar messages are deleted. This value is the default. - $false: Non-calendar messages are preserved. ```yaml @@ -597,7 +597,7 @@ Accept wildcard characters: False The DeleteSubject parameter specifies whether to remove or keep the subject of incoming meeting requests. Valid values are: -- $true: Remove the Subject value of incoming meeting requests. This is the default value. +- $true: Remove the Subject value of incoming meeting requests. This value is the default. - $false: Preserve The Subject value of incoming meeting requests. This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept. @@ -660,7 +660,7 @@ Accept wildcard characters: False The EnableResponseDetails parameter specifies whether to include the reasons for accepting or declining a meeting in the response email message. Valid values are: -- $true: The reasons for accepting or declining a meeting are included in the response message. This is the default value. +- $true: The reasons for accepting or declining a meeting are included in the response message. This value is the default. - $false: The reasons for accepting or declining a meeting aren't included in the response message. ```yaml @@ -684,7 +684,7 @@ This parameter is available only in the cloud-based service. The EnforceCapacity parameter specifies whether to restrict the number of attendees to the capacity of the workspace. For example, if capacity is set to 10, then only 10 people can book the workspace. Valid values are: - $true: Capacity is enforced. -- $false: Capacity is not enforced. This is the default value. +- $false: Capacity is not enforced. This value is the default. ```yaml Type: Boolean @@ -704,8 +704,8 @@ Accept wildcard characters: False The EnforceSchedulingHorizon parameter controls the behavior of recurring meetings that extend beyond the date specified by the BookingWindowInDays parameter. Valid values are: -- $true: A recurring meeting request is automatically declined if the meetings start on or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date. This is the default value. -- $false: A recurring meeting request is automatically accepted if the meetings start on or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date. However, the number of meetings is automatically reduced so meetings won't occur after the specified date. +- $true: A recurring meeting request is automatically declined if the meetings start on or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date. This value is the default. +- $false: A recurring meeting request is automatically accepted if the meetings start on or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date. However, the number of meetings is automatically reduced so meetings don't occur after the specified date. ```yaml Type: Boolean @@ -725,7 +725,7 @@ Accept wildcard characters: False The ForwardRequestsToDelegates parameter specifies whether to forward incoming meeting requests to the delegates that are configured for the resource mailbox. Valid values are: -- $true: Forward incoming meeting requests to the delegates. This is the default value. +- $true: Forward incoming meeting requests to the delegates. This value is the default. - $false: Don't forward incoming meeting requests to the delegates. ```yaml @@ -833,7 +833,7 @@ Accept wildcard characters: False The OrganizerInfo parameter specifies whether the resource mailbox sends organizer information when a meeting request is declined because of conflicts. Valid values are: -- $true: Organizer information is sent when a meeting request is declined because of conflicts. This is the default value. +- $true: Organizer information is sent when a meeting request is declined because of conflicts. This value is the default. - $false: Organizer information isn't sent when a meeting request is declined because of conflicts. ```yaml @@ -875,7 +875,7 @@ Accept wildcard characters: False The ProcessExternalMeetingMessages parameter specifies whether to process meeting requests that originate outside the Exchange organization. Valid values are: - $true: Meeting requests from external senders are processed. -- $false: Meeting requests from external senders are rejected. This is the default value. +- $false: Meeting requests from external senders are rejected. This value is the default. ```yaml Type: Boolean @@ -898,7 +898,7 @@ This parameter is available only in the cloud-based service. The RemoveCanceledMeetings parameter specifies whether to automatically delete meetings that were cancelled by the organizer from the resource mailbox's calendar. Valid values are: - $true: Canceled meetings are deleted. -- $false: Canceled meetings aren't deleted. This is the default value. +- $false: Canceled meetings aren't deleted. This value is the default. ```yaml Type: Boolean @@ -919,7 +919,7 @@ Accept wildcard characters: False The RemoveForwardedMeetingNotifications parameter specifies whether forwarded meeting notifications are moved to the Deleted Items folder after they're processed by the Calendar Attendant. Valid values are: - $true: Processed forwarded meeting notifications are deleted (moved to the Deleted Items folder). -- $false: Processed forwarded meeting notifications aren't deleted. This is the default value. +- $false: Processed forwarded meeting notifications aren't deleted. This value is the default. ```yaml Type: Boolean @@ -939,7 +939,7 @@ Accept wildcard characters: False The RemoveOldMeetingMessages parameter specifies whether the Calendar Attendant removes old and redundant updates and responses. Valid values are: -- $true: Outdated and redundant meeting messages are deleted. This is the default value. +- $true: Outdated and redundant meeting messages are deleted. This value is the default. - $false: Outdated and redundant meeting messages aren't deleted. ```yaml @@ -960,7 +960,7 @@ Accept wildcard characters: False The RemovePrivateProperty parameter specifies whether to clear the private flag for incoming meetings that were sent by the organizer in the original requests. Valid values are: -- $true: The private flag for incoming meeting requests is cleared (the meeting is no longer private). This is the default value. +- $true: The private flag for incoming meeting requests is cleared (the meeting is no longer private). This value is the default. - $false: The private flag for incoming meeting requests is preserved (private meetings stay private). ```yaml @@ -1063,7 +1063,7 @@ Accept wildcard characters: False The ScheduleOnlyDuringWorkHours parameter specifies whether to allow meetings to be scheduled outside of the working hours that are defined for the resource mailbox. Valid values are: - $true: Meeting requests that are outside of working hours are automatically rejected. -- $false: Meeting requests that are outside of working hours aren't automatically rejected. This is the default value. +- $false: Meeting requests that are outside of working hours aren't automatically rejected. This value is the default. You configure the working hours of the resource mailbox by using the WorkDays, WorkingHoursStartTime, WorkingHoursEndTime and WorkingHoursTimeZone parameters on the Set-MailboxCalendarConfiguration cmdlet. @@ -1085,7 +1085,7 @@ Accept wildcard characters: False The TentativePendingApproval parameter specifies whether to mark pending requests as tentative on the calendar. Valid values are: -- $true: Meeting requests that are awaiting approval from a delegate appear in the calendar as tentative. This is the default value. +- $true: Meeting requests that are awaiting approval from a delegate appear in the calendar as tentative. This value is the default. - $false: Meeting requests that are awaiting approval appear in the calendar as free. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md index 68741273ad..d6849d6df6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md @@ -228,7 +228,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md index c34bc26621..b608519c55 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md @@ -133,7 +133,7 @@ Accept wildcard characters: False The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are: - $true: The rule is disabled. -- $false: The rule is enabled. This is the default value. +- $false: The rule is enabled. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md index 2502056704..53a24290a9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md @@ -13,7 +13,7 @@ title: Set-ClassificationRuleCollection # Set-ClassificationRuleCollection ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ClassificationRuleCollection cmdlet to update existing classification rule collections in your organization. @@ -32,7 +32,7 @@ Set-ClassificationRuleCollection [-FileData] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md index 00eda61ee3..527bdc1924 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md @@ -33,7 +33,7 @@ Set-ClientAccessArray [-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/Set-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md index 19c664d7a8..c608194cb5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md @@ -16,7 +16,7 @@ title: Set-ClientAccessRule > [!NOTE] > Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). -This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ClientAccessRule cmdlet to modify existing client access rules. Client access rules help you control access to your organization based on the properties of the connection. @@ -73,7 +73,7 @@ Protocols that don't support authentication type filters: - REST - UniversalOutlook -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md index 485c03031d..c508f745f4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md @@ -60,7 +60,7 @@ Set-ClientAccessServer [-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 @@ -293,7 +293,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. ```yaml Type: Unlimited @@ -324,7 +324,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the ReceiveProtocolLogMaxDirectorySize parameter. @@ -348,6 +348,8 @@ This parameter is available only in Exchange Server 2010. The IrmLogPath parameter specifies the location of the IRM log files. The default location is %ExchangeInstallPath%Logging\\IRMLogs. +If you set the value of this parameter to $null, you effectively disable IRM logging. However, if the value of the IrmLogEnabled parameter is $true, Exchange adds errors to the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false. + ```yaml Type: LocalLongFullPath Parameter Sets: (All) diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md index 513a753cb2..054020ca76 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md @@ -46,7 +46,7 @@ Set-ClientAccessService [-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/Set-Clutter.md b/exchange/exchange-ps/ExchangePowerShell/Set-Clutter.md index 0744a0ad2e..69a1410858 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Clutter.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Clutter.md @@ -29,7 +29,7 @@ Set-Clutter -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 @@ -77,7 +77,7 @@ Accept wildcard characters: False The Enable parameter specifies whether to enable or disable Clutter for the mailbox. Valid values are: -- $true: Clutter is enabled for the mailbox. This is the default value. +- $true: Clutter is enabled for the mailbox. This value is the default. - $false: Clutter is disabled for the mailbox. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md index 681865354f..1076192f9a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md @@ -36,7 +36,7 @@ Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and The changes that you make by using the Set-CmdletExtensionAgent cmdlet are applied to every Exchange server in the 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/Set-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md index a8987cc8b3..336c84486c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md @@ -30,7 +30,7 @@ Set-ComplianceRetentionEventType -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/Set-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md index 3919717169..77914d94f0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md @@ -13,7 +13,7 @@ title: Set-ComplianceSearch # Set-ComplianceSearch ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ComplianceSearch cmdlet to modify non-running compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. @@ -53,7 +53,7 @@ Set-ComplianceSearch [-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). In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. @@ -208,7 +208,7 @@ Accept wildcard characters: False The AllowNotFoundExchangeLocationsEnabled parameter specifies whether to include mailboxes other than regular user mailboxes in the compliance search. Valid values are: - $true: The search doesn't try to validate the existence of the mailbox before proceeding. This value is required if you want to search mailboxes that don't resolve as regular mailboxes. -- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This is the default value. +- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This value is the default. The mailbox types that are affected by the value of this parameter include: @@ -365,11 +365,11 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The HoldNames parameter specifies that the content locations that have been placed on hold in the eDiscovery case will be searched. You use the value All for this parameter. You can use this parameter only for compliance searches that are associated with an eDiscovery case. +The HoldNames parameter specifies the content locations placed on hold in the specified eDiscovery case are searched. You use the value All for this parameter. You can use this parameter only for compliance searches that are associated with an eDiscovery case. If the content locations in the compliance search include mailboxes, you also need to use the ExchangeLocation parameter with the value $null. Similarly, if the compliance search includes SharePoint sites, you also need to use the SharePointLocation parameter with the value $null. -Also, if a content location was placed on a query-based case hold, only items that are on hold will be searched when you restart this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search. +Also, if a content location was placed on a query-based case hold, only items that are on hold are searched when you restart this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search. ```yaml Type: String[] @@ -409,8 +409,8 @@ This parameter is available only in the cloud-based service. The IncludeUserAppContent parameter specifies that you want to search the cloud-based storage location for users who don't have a regular Microsoft 365 user account in your organization. These types of users include users without an Exchange Online license who use Office applications, Microsoft 365 guest users, and on-premises users whose identity is synchronized with your Microsoft 365 organization. Valid values are: -- $true: The cloud-based storage location for the users specified in any of the Exchange location parameters will be included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user will be included in the search. -- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter won't be included in the search. This is the default value. +- $true: The cloud-based storage location for the users specified in any of the Exchange location parameters are included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user are included in the search. +- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter isn't included in the search. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md index a70ca0736f..7b3b7caae8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md @@ -34,7 +34,7 @@ Set-ComplianceSearchAction [-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). This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md index 1717b76660..40742de678 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md @@ -210,7 +210,7 @@ The Users parameter specifies the user who gets this filter applied to their sea You can't specify distribution groups with this parameter. -The values you specify will overwrite any existing entries. See the Examples section to add or remove users without affecting other existing entries. +The values you specify overwrite any existing entries. See the Examples section to add or remove users without affecting other existing entries. ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md b/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md index 29b5f373c7..cfd2ce2f56 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md @@ -13,7 +13,7 @@ title: Set-Contact # Set-Contact ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-Contact cmdlet to modify contact object settings. If the contact is a mail contact, you can use the Set-MailContact cmdlet to modify other Microsoft Exchange settings that aren't available by using the Set-Contact cmdlet. @@ -68,7 +68,7 @@ Set-Contact [-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 @@ -233,7 +233,7 @@ This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: -- $true: A DTMF map is created for the recipient. This is the default value. +- $true: A DTMF map is created for the recipient. This value is the default. - $false: A DTMF map isn't created for the recipient. ```yaml @@ -682,7 +682,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The SeniorityIndex parameter specifies the order in which this contact will display in a hierarchical address book. A contact with a value of 2 will display higher in an address book than a contact with a value of 1. +The SeniorityIndex parameter specifies the order in which this contact displays in a hierarchical address book. A contact with a value of 2 displays higher in an address book than a contact with a value of 1. ```yaml Type: Int32 @@ -800,7 +800,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The UMCallingLineIds parameter specifies telephone numbers or extensions that can be mapped to a Unified Messaging (UM)-enabled user. You can specify more than one telephone number for each user, separated by a comma. Values for this parameter must be less than 128 characters in length and may include an optional plus sign (+) that precedes the numbers. Each UM-enabled user must have a unique UMCallingLineIds parameter value. +The UMCallingLineIds parameter specifies telephone numbers or extensions that can be mapped to a Unified Messaging (UM)-enabled user. You can specify more than one telephone number for each user, separated by a comma. Values for this parameter must be less than 128 characters in length and might include an optional plus sign (+) that precedes the numbers. Each UM-enabled user must have a unique UMCallingLineIds parameter value. ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md index 43970e90cf..e16cf78246 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md @@ -44,7 +44,7 @@ Set-ContentFilterConfig [-BypassedRecipients ] ``` ## 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 @@ -66,7 +66,7 @@ It enables and configures the SCL threshold functionalities that quarantine, rej It specifies `SpamQuarantineMailbox@contoso.com` as the spam quarantine mailbox. -It defines two users for whom the Content Filter won't process messages. +It defines two users for whom the Content Filter doesn't process messages. ## PARAMETERS @@ -177,7 +177,7 @@ Accept wildcard characters: False The Enabled parameter enables or disables the Content Filter agent on the computer on which you're running the command. Valid values are: -- $true: The Content Filter agent is enabled. This is the default value. +- $true: The Content Filter agent is enabled. This value is the default. - $false: The Content Filter agent is disabled. ```yaml @@ -198,7 +198,7 @@ Accept wildcard characters: False The ExternalMailEnabled parameter specifies whether all messages from unauthenticated connections from sources external to your Exchange organization are processed by the Content Filter agent. Valid values are: -- $true: Messages from unauthenticated connections are processed by the Content Filter agent. This is the default value. +- $true: Messages from unauthenticated connections are processed by the Content Filter agent. This value is the default. - $false: Messages from unauthenticated connections aren't processed by the Content Filter agent. ```yaml @@ -220,7 +220,7 @@ Accept wildcard characters: False The InternalMailEnabled parameter specifies whether all messages from authenticated connections and from authoritative domains in your enterprise are processed by the Content Filter agent. Valid values are: - $true: Messages from authenticated connections are processed by the Content Filter agent. -- $false: Messages from authenticated connections aren't processed by the Content Filter agent. This is the default value. +- $false: Messages from authenticated connections aren't processed by the Content Filter agent. This value is the default. ```yaml Type: Boolean @@ -246,7 +246,7 @@ The OutlookEmailPostmarkValidationEnabled parameter specifies whether Outlook Em Valid values are: - $true: Outlook Email Postmark validation is enabled. -- $false: Outlook Email Postmark validation is disabled. This is the default value. +- $false: Outlook Email Postmark validation is disabled. This value is the default. ```yaml Type: Boolean @@ -303,7 +303,7 @@ Accept wildcard characters: False The SCLDeleteEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLDeleteThreshold parameter are deleted. Valid values are: - $true: Messages that meet or exceed the value set in the SCLDeleteThreshold parameter are deleted. -- $false: Messages aren't deleted. This is the default value. +- $false: Messages aren't deleted. This value is the default. ```yaml Type: Boolean @@ -342,7 +342,7 @@ Accept wildcard characters: False The SCLQuarantineEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLQuarantineThreshold parameter are sent to the spam quarantine mailbox specified in the QuarantineMailbox parameter. Valid values are: - $true: Messages that meet or exceed the value set in the SCLQuarantineThreshold parameter are sent to the spam quarantine mailbox specified in the QuarantineMailbox parameter. -- $false: Messages aren't quarantined. This is the default value. +- $false: Messages aren't quarantined. This value is the default. ```yaml Type: Boolean @@ -381,7 +381,7 @@ Accept wildcard characters: False The SCLRejectEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLRejectThreshold parameter are rejected in an NDR to the sender. Valid values are: - $true: Messages that meet or exceed the value set in the SCLRejectThreshold parameter are rejected in an NDR is to the sender. -- $false: Messages aren't rejected. This is the default value. +- $false: Messages aren't rejected. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md index adc832cfbe..96da55616a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md @@ -15,7 +15,7 @@ title: Set-DataClassification ## SYNOPSIS This cmdlet is functional only in on-premises Exchange. -In Exchange Online, this cmdlet has been replaced by the [Set-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/set-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. +In Exchange Online, this cmdlet is replaced by the [Set-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/set-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. Use the Set-DataClassification cmdlet to modify data classification rules that use document fingerprints. @@ -39,7 +39,7 @@ Set-DataClassification [-Identity] ## DESCRIPTION Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md index 12b4c81f90..737d608e85 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md @@ -62,7 +62,7 @@ Set-DataEncryptionPolicy [-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 @@ -78,7 +78,7 @@ This example disabled the data encryption policy named US Mailboxes. Set-DataEncryptionPolicy -Identity "Europe Mailboxes" -Refresh ``` -This example updates the data encryption policy named Europe Mailboxes after one of the associated keys has been rotated in the Azure Key Vault. +This example updates the data encryption policy named Europe Mailboxes after one of the associated keys is rotated in the Azure Key Vault. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md index 9d95637c81..050d159a8c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md @@ -69,7 +69,7 @@ DAG property values are stored in both Active Directory and the cluster database - NetworkEncryption - DiscoverNetworks -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -353,7 +353,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The AutoDagDiskReclaimerEnabled is used to enable or disable the volume formatting functions used by Autoreseed. The default value is $true (enabled). If you set this to $false, you will need to manually format the volume before the database(s) can be reseeded. +The AutoDagDiskReclaimerEnabled is used to enable or disable the volume formatting functions used by Autoreseed. The default value is $true (enabled). If you set this to $false, you need to manually format the volume before the database(s) can be reseeded. ```yaml Type: Boolean @@ -650,7 +650,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h The default value is 01:00:00 (1 hour). To disable this feature, specify the value `([System.Threading.Timeout]::InfiniteTimeSpan)`. -**Important**: Don't specify a value larger than 49.7 days. A larger value will crash MSExchangeRepl.exe with an ArgumentOutOfRangeException error on all DAG members. +**Important**: Don't specify a value larger than 49.7 days. A larger value crashes MSExchangeRepl.exe with an ArgumentOutOfRangeException error on all DAG members. ```yaml Type: TimeSpan @@ -758,7 +758,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The WitnessServer parameter specifies the name of a server that will act as a witness for the DAG. The server specified can't be a member of the DAG. +The WitnessServer parameter specifies the name of a server that acts as a witness for the DAG. The server specified can't be a member of the DAG. ```yaml Type: FileShareWitnessServerName diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md index 12e8a3b755..26432fbd03 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md @@ -37,7 +37,7 @@ Set-DatabaseAvailabilityGroupNetwork [-Identity] ## DESCRIPTION Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md index 248527df63..95bb18e238 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md @@ -31,7 +31,7 @@ Set-DetailsTemplate [-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/Set-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md index 5e4ae5fe94..807af383b6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md @@ -149,7 +149,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md index 2bf094221a..4f2b1cd162 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md @@ -145,7 +145,7 @@ Accept wildcard characters: False The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -166,7 +166,7 @@ Accept wildcard characters: False The AccountUserName parameter specifies the account user name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -188,7 +188,7 @@ The AllowAppStore parameter specifies whether to allow access to the app store o - $true: Access to the app store is allowed. - $false: Access to the app store isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -215,7 +215,7 @@ The AllowAssistantWhileLocked parameter specifies whether to allow the use of th - $true: The voice assistant can be used while devices are locked. - $false: The voice assistant can't be used while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -239,7 +239,7 @@ The AllowConvenienceLogon parameter specifies whether to allow convenience logon - $true: Convenience logons are allowed. - $false: Convenience logons aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -263,7 +263,7 @@ The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic su - $true: Diagnostic submissions are allowed. - $false: Diagnostic submissions aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -291,7 +291,7 @@ The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup f - $true: iCloud Backup is allowed. - $false: iCloud Backup isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -318,7 +318,7 @@ The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documen - $true: iCloud Documents & Data sync is allowed. - $false: iCloud Documents & Data sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -345,7 +345,7 @@ The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photo - $true: iCloud Photos sync is allowed. - $false: iCloud Photo sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -372,7 +372,7 @@ The AllowJailbroken parameter specifies whether to allow access to your organiza - $true: Jailbroken devices are allowed. - $false: Jailbroken devices aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -399,7 +399,7 @@ The AllowPassbookWhileLocked parameter specifies whether to allow the use of App - $true: Passbook is available while devices are locked. - $false: Passbook isn't available while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -423,7 +423,7 @@ The AllowScreenshot parameter specifies whether to allow screenshots on devices. - $true: Screenshots are allowed. - $false: Screenshots aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -450,7 +450,7 @@ The AllowSimplePassword parameter specifies whether to allow simple or non-compl - $true: Simple passwords are allowed. - $false: Simple passwords aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -478,7 +478,7 @@ The AllowVideoConferencing parameter specifies whether to allow video conferenci - $true: Video conferencing is allowed. - $false: Video conferencing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -502,7 +502,7 @@ The AllowVoiceAssistant parameter specifies whether to allow using the voice ass - $true: The voice assistant is allowed. - $false: The voice assistant isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -526,7 +526,7 @@ The AllowVoiceDialing parameter specifies whether to allow voice-activated telep - $true: Voice dialing is allowed. - $false: Voice dialing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -549,7 +549,7 @@ Accept wildcard characters: False The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -572,7 +572,7 @@ Accept wildcard characters: False The AntiVirusStatus parameter specifies antivirus status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -599,7 +599,7 @@ The AppsRating parameter species the maximum or most restrictive rating of apps - Rating9plus - Rating12plus - Rating17plus -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -626,7 +626,7 @@ The AutoUpdateStatus parameter specifies the update settings for devices. Valid - AutomaticUpdatesRequired - DeviceDefault - NeverCheckUpdates -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -650,7 +650,7 @@ The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth - $true: Bluetooth is enabled. - $false: Bluetooth is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -674,7 +674,7 @@ The CameraEnabled parameter specifies whether to enable or disable cameras on de - $true: Cameras are enabled. - $false: Cameras are disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -740,7 +740,7 @@ Accept wildcard characters: False The EmailAddress parameter specifies the email address. Valid values are: - An email address: For example, julia@contoso.com. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -762,7 +762,7 @@ The EnableRemovableStorage parameter specifies whether removable storage can be - $true: Removable storage can be used. - $false: Removable storage can't be used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -785,7 +785,7 @@ Accept wildcard characters: False The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -806,7 +806,7 @@ Accept wildcard characters: False The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are: - Required -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -830,7 +830,7 @@ The ForceAppStorePassword parameter specifies whether to require a password to u - $true: App store passwords are required. - $false: App store passwords aren't required. -- $null (blank): The feature isn't allowed or blocked by the rule. This is the default value. +- $null (blank): The feature isn't allowed or blocked by the rule. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -854,7 +854,7 @@ The ForceEncryptedBackup parameter specifies whether to force encrypted backups - $true: Encrypted backups are required. - $false: Encrypted backups aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -880,7 +880,7 @@ Accept wildcard characters: False The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -933,7 +933,7 @@ Valid values for the MoviesRating parameter are: - AllowAll: All movies are allowed, regardless of their rating. - DontAllow: No movies are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1032,7 +1032,7 @@ Accept wildcard characters: False The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int64 @@ -1053,7 +1053,7 @@ Accept wildcard characters: False The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1081,7 +1081,7 @@ Accept wildcard characters: False The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1109,7 +1109,7 @@ Accept wildcard characters: False The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int32 @@ -1130,7 +1130,7 @@ Accept wildcard characters: False The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1160,7 +1160,7 @@ The PasswordQuality parameter specifies the minimum password quality rating that Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Android 4+ devices. @@ -1184,7 +1184,7 @@ The PasswordRequired parameter specifies whether a password is required to acces - $true: Device passwords are required. - $false: Device passwords aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1239,7 +1239,7 @@ The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on de - $true: Memory is encrypted. - $false: Memory isn't encrypted. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1266,7 +1266,7 @@ The RegionRatings parameter specifies the rating system (country/region) to use Valid values for the RegionRating parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - au: Australia - ca: Canada - de: Germany @@ -1299,7 +1299,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required - $true: An email profile is required. This value is required for selective wipe on iOS devices. - $false: An email profile isn't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Boolean @@ -1321,7 +1321,7 @@ The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen - $true: SmartScreen is enabled. - $false: SmartScreen is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -1345,7 +1345,7 @@ The SystemSecurityTLS parameter specifies whether TLS encryption is used on devi - $true: TLS encryption is used. - $false: TLS encryption isn't used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -1371,7 +1371,7 @@ Valid values for the TVShowsRating parameter are: - AllowAll: All television shows are allowed, regardless of their rating. - DontAllow: No televisions shows are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1458,7 +1458,7 @@ Accept wildcard characters: False The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - AlwaysNotify - NeverNotify - NotifyAppChanges @@ -1504,7 +1504,7 @@ The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid valu - $true: Wi-Fi is enabled. - $false: Wi-Fi is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Microsoft Windows Phone 8.1 devices. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md index 4f8b285283..68bf9001ec 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md @@ -149,7 +149,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md index 5495fd17ec..ca87acb7a7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md @@ -144,7 +144,7 @@ Accept wildcard characters: False The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -165,7 +165,7 @@ Accept wildcard characters: False The AccountUserName parameter specifies the account user name. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -187,7 +187,7 @@ The AllowAppStore parameter specifies whether to allow access to the app store o - $true: Access to the app store is allowed. - $false: Access to the app store isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -214,7 +214,7 @@ The AllowAssistantWhileLocked parameter specifies whether to allow the use of th - $true: The voice assistant can be used while devices are locked. - $false: The voice assistant can't be used while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -238,7 +238,7 @@ The AllowConvenienceLogon parameter specifies whether to allow convenience logon - $true: Convenience logons are allowed. - $false: Convenience logons aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -262,7 +262,7 @@ The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic su - $true: Diagnostic submissions are allowed. - $false: Diagnostic submissions aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -290,7 +290,7 @@ The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup f - $true: iCloud Backup is allowed. - $false: iCloud Backup isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -317,7 +317,7 @@ The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documen - $true: iCloud Documents & Data sync is allowed. - $false: iCloud Documents & Data sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -344,7 +344,7 @@ The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photo - $true: iCloud Photos sync is allowed. - $false: iCloud Photo sync isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -371,7 +371,7 @@ The AllowPassbookWhileLocked parameter specifies whether to allow the use of App - $true: Passbook is available while devices are locked. - $false: Passbook isn't available while devices are locked. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -395,7 +395,7 @@ The AllowScreenshot parameter specifies whether to allow screenshots on devices. - $true: Screenshots are allowed. - $false: Screenshots aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -422,7 +422,7 @@ The AllowSimplePassword parameter specifies whether to allow simple or non-compl - $true: Simple passwords are allowed. - $false: Simple passwords aren't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -450,7 +450,7 @@ The AllowVideoConferencing parameter specifies whether to allow video conferenci - $true: Video conferencing is allowed. - $false: Video conferencing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -474,7 +474,7 @@ The AllowVoiceAssistant parameter specifies whether to allow using the voice ass - $true: The voice assistant is allowed. - $false: The voice assistant isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -498,7 +498,7 @@ The AllowVoiceDialing parameter specifies whether to allow voice-activated telep - $true: Voice dialing is allowed. - $false: Voice dialing isn't allowed. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -521,7 +521,7 @@ Accept wildcard characters: False The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -544,7 +544,7 @@ Accept wildcard characters: False The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -571,7 +571,7 @@ The AppsRating parameter species the maximum or most restrictive rating of apps - Rating9plus - Rating12plus - Rating17plus -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -598,7 +598,7 @@ The AutoUpdateStatus parameter specifies the update settings for devices. Valid - AutomaticUpdatesRequired - DeviceDefault - NeverCheckUpdates -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -622,7 +622,7 @@ The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth - $true: Bluetooth is enabled. - $false: Bluetooth is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -646,7 +646,7 @@ The CameraEnabled parameter specifies whether to enable or disable cameras on de - $true: Cameras are enabled. - $false: Cameras are disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -712,7 +712,7 @@ Accept wildcard characters: False The EmailAddress parameter specifies the email address. Valid values are: - An email address: For example, julia@contoso.com. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -734,7 +734,7 @@ The EnableRemovableStorage parameter specifies whether removable storage can be - $true: Removable storage can be used. - $false: Removable storage can't be used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows Phone 8.1 devices. @@ -757,7 +757,7 @@ Accept wildcard characters: False The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are: - A text value. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: String @@ -778,7 +778,7 @@ Accept wildcard characters: False The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are: - Required -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -802,7 +802,7 @@ The ForceAppStorePassword parameter specifies whether to require a password to u - $true: App store passwords are required. - $false: App store passwords aren't required. -- $null (blank): The feature isn't allowed or blocked by the rule. This is the default value. +- $null (blank): The feature isn't allowed or blocked by the rule. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -826,7 +826,7 @@ The ForceEncryptedBackup parameter specifies whether to force encrypted backups - $true: Encrypted backups are required. - $false: Encrypted backups aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -852,7 +852,7 @@ Accept wildcard characters: False The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -905,7 +905,7 @@ Valid values for the MoviesRating parameter are: - AllowAll: All movies are allowed, regardless of their rating. - DontAllow: No movies are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1004,7 +1004,7 @@ Accept wildcard characters: False The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int64 @@ -1025,7 +1025,7 @@ Accept wildcard characters: False The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1053,7 +1053,7 @@ Accept wildcard characters: False The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1081,7 +1081,7 @@ Accept wildcard characters: False The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Int32 @@ -1102,7 +1102,7 @@ Accept wildcard characters: False The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1132,7 +1132,7 @@ The PasswordQuality parameter specifies the minimum password quality rating that Valid values for this parameter are: - An integer. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Android 4+ devices. @@ -1156,7 +1156,7 @@ The PasswordRequired parameter specifies whether a password is required to acces - $true: Device passwords are required. - $false: Device passwords aren't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1211,7 +1211,7 @@ The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on de - $true: Memory is encrypted. - $false: Memory isn't encrypted. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available on the following types of devices: @@ -1238,7 +1238,7 @@ The RegionRatings parameter specifies the rating system (country/region) to use Valid values for the RegionRating parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - au: Australia - ca: Canada - de: Germany @@ -1271,7 +1271,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required - $true: An email profile is required. This value is required for selective wipe on iOS devices. - $false: An email profile isn't required. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. ```yaml Type: Boolean @@ -1293,7 +1293,7 @@ The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen - $true: SmartScreen is enabled. - $false: SmartScreen is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Windows 8.1 RT devices. @@ -1317,7 +1317,7 @@ The SystemSecurityTLS parameter specifies whether TLS encryption is used on devi - $true: TLS encryption is used. - $false: TLS encryption isn't used. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Apple iOS 6+ devices. @@ -1343,7 +1343,7 @@ Valid values for the TVShowsRating parameter are: - AllowAll: All television shows are allowed, regardless of their rating. - DontAllow: No televisions shows are allowed, regardless of their rating. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. Australia @@ -1430,7 +1430,7 @@ Accept wildcard characters: False The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are: -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. - AlwaysNotify - NeverNotify - NotifyAppChanges @@ -1476,7 +1476,7 @@ The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid valu - $true: Wi-Fi is enabled. - $false: Wi-Fi is disabled. -- $null (blank): The setting isn't configured. This is the default value. +- $null (blank): The setting isn't configured. This value is the default. This setting is available only on Microsoft Windows Phone 8.1 devices. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md index c5e82785ad..7882d265a4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md @@ -127,7 +127,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md index 0eafe6e2d8..01e017c678 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md @@ -13,7 +13,7 @@ title: Set-DistributionGroup # Set-DistributionGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-DistributionGroup cmdlet to modify the settings of existing distribution groups or mail-enabled security groups. To add or remove group members, use the Add-DistributionGroupMember, Remove-DistributionGroupMember or Update-DistributionGroupMember cmdlets. @@ -99,7 +99,7 @@ Set-DistributionGroup [-Identity] ## DESCRIPTION Distribution groups are used to consolidate groups of recipients into a single point of contact for email messages. Distribution groups aren't security principals, and therefore can't be assigned permissions. However, you can assign permissions to mail-enabled security groups. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -334,7 +334,7 @@ This parameter is available only in the cloud-based service. The BccBlocked parameter specifies whether members of the group don't receive messages if the group is used in the Bcc line. Valid values are: - $true: If the group is used in the Bcc line, members of the group don't receive the message, and the sender receives a non-delivery report (also known as an NDR or bounce message). Other recipients of the message aren't blocked. If an external sender uses the group in the Bcc line, members of the group aren't blocked. For nested groups, the message is blocked only for members of the top-level group. -- $false: There are no restrictions for using the group in the Bcc line of messages. This is the default value. +- $false: There are no restrictions for using the group in the Bcc line of messages. This value is the default. ```yaml Type: Boolean @@ -388,7 +388,7 @@ Accept wildcard characters: False The ByPassNestedModerationEnabled parameter specifies how to handle message approval when a moderated group contains other moderated groups as members. Valid values are: - $true: After a moderator approves a message sent to the group, the message is automatically approved for all other moderated groups that are members of the group. -- $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This is the default value. +- $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This value is the default. ```yaml Type: Boolean @@ -454,7 +454,7 @@ This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: -- $true: A DTMF map is created for the recipient. This is the default value. +- $true: A DTMF map is created for the recipient. This value is the default. - $false: A DTMF map isn't created for the recipient. ```yaml @@ -846,7 +846,7 @@ This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -898,7 +898,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -922,7 +922,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -946,7 +946,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -970,7 +970,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -994,7 +994,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1070,7 +1070,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -1267,7 +1267,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -1300,7 +1300,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -1324,8 +1324,8 @@ Accept wildcard characters: False The MemberDepartRestriction parameter specifies the restrictions that you put on requests to leave the group. Valid values are: -- Open: Members can leave the group without approval from one of the group owners. This is the default value for universal distribution groups. You can't use this value on universal security groups. -- Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This is the default value for universal security groups. +- Open: Members can leave the group without approval from one of the group owners. This value is the default for universal distribution groups. You can't use this value on universal security groups. +- Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This value is the default for universal security groups. ```yaml Type: MemberUpdateType @@ -1346,7 +1346,7 @@ Accept wildcard characters: False The MemberJoinRestriction parameter specifies the restrictions that you put on requests to join the group. Valid values are: - Open: Users can add themselves to the group without approval from a group owner. You can't use this value on universal security groups. -- Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This is the default value on universal security groups and universal distribution groups. +- Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This value is the default on universal security groups and universal distribution groups. - ApprovalRequired: Users can request to join the group. The user is added to the group after the request is approved by one of the group owners. Although you can use this value on universal security groups, user requests to join the group aren't sent to the group owners, so this setting is only effective on universal distribution groups. ```yaml @@ -1401,7 +1401,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -1571,7 +1571,7 @@ Accept wildcard characters: False The ReportToManagerEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the owner (first one listed if more than one) of the group (defined by the ManagedBy property). Valid values are: - $true: Delivery status notifications are sent to the owner (first one listed if more than one) of the group. -- $false: Delivery status notifications aren't sent to the owner (first one listed if more than one) of the group. This is the default value. +- $false: Delivery status notifications aren't sent to the owner (first one listed if more than one) of the group. This value is the default. The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true. @@ -1593,7 +1593,7 @@ Accept wildcard characters: False The ReportToOriginatorEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to senders who send messages to this group. Valid values are: -- $true: Delivery status notifications are sent to the message senders. This is the default value. +- $true: Delivery status notifications are sent to the message senders. This value is the default. - $false: Delivery status notifications aren't sent to the message senders. The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true. @@ -1677,7 +1677,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). ```yaml Type: String @@ -1697,7 +1697,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -1722,7 +1722,7 @@ Accept wildcard characters: False The SendOofMessageToOriginatorEnabled parameter specifies how to handle out of office (OOF) messages for members of the group. Valid values are: - $true: When messages are sent to the group, OOF messages for any of the group members are sent to the message sender. -- $false: When messages are sent to the group, OOF messages for any of the group members aren't sent to the message sender. This is the default value. +- $false: When messages are sent to the group, OOF messages for any of the group members aren't sent to the message sender. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md index e05a1d19ae..91d0b4e1e1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md @@ -34,7 +34,7 @@ Set-DkimSigningConfig [-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 @@ -93,7 +93,7 @@ Accept wildcard characters: False The BodyCanonicalization parameter specifies the canonicalization algorithm that's used to create and verify the message body part of the DKIM signature. This value effectively controls the sensitivity of DKIM to changes to the message body in transit. Valid values are: -- Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This is the default value. +- Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This value is the default. - Simple: Only changes in empty lines at the end of the message body are tolerated. ```yaml @@ -135,7 +135,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml @@ -156,7 +156,7 @@ Accept wildcard characters: False The HeaderCanonicalization parameter specifies the canonicalization algorithm that's used to create and verify the message header part of the DKIM signature. This value effectively controls the sensitivity of DKIM to changes to the message headers in transit. Valid values are: -- Relaxed: Common modifications to the message header are tolerated (for example, header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields). This is the default value. +- Relaxed: Common modifications to the message header are tolerated (for example, header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields). This value is the default. - Simple: No changes to the header fields are tolerated. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md index 1970809d33..4abc2dd131 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md @@ -221,7 +221,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The AddExchangeLocation parameter adds email messages to the DLP policy if they're not already included. The valid value for this parameter is All. +The AddExchangeLocation parameter adds email messages to the DLP policy if they aren't already included. The valid value for this parameter is All. If the policy doesn't already include email messages (in the output of the Get-DlpCompliancePolicy cmdlet, the ExchangeLocation property value is blank), you can use this parameter in the following procedures: @@ -247,7 +247,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The AddOneDriveLocation parameter adds OneDrive sites to the DLP policy if they're not already included. The valid value for this parameter is All. +The AddOneDriveLocation parameter adds OneDrive sites to the DLP policy if they aren't already included. The valid value for this parameter is All. If the policy doesn't already include OneDrive sites (in the output of the Get-DlpCompliancePolicy cmdlet, the OneDriveLocation property value is blank), you can use this parameter in the following procedures: @@ -874,7 +874,7 @@ Accept wildcard characters: False The Mode parameter specifies the action and notification level of the DLP policy. Valid values are: -- Enable: The policy is enabled for actions and notifications. This is the default value. +- Enable: The policy is enabled for actions and notifications. This value is the default. - Disable: The policy is disabled. - TestWithNotifications: Simulation mode where no actions are taken, but notifications **are** sent. - TestWithoutNotifications: Simulation mode where no actions are taken, and no notifications are sent. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md index 1843b0a257..31fbb3026c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md @@ -502,7 +502,7 @@ Accept wildcard characters: False The BlockAccess parameter specifies an action for the DLP rule that blocks access to the source item when the conditions of the rule are met. Valid values are: - $true: Blocks further access to the source item that matched the rule. The owner, author, and site owner can still access the item. -- $false: Allows access to the source item that matched the rule. This is the default value. +- $false: Allows access to the source item that matched the rule. This value is the default. ```yaml Type: Boolean @@ -720,7 +720,7 @@ Accept wildcard characters: False The Disabled parameter specifies whether the DLP rule is disabled. Valid values are: - $true: The rule is disabled. -- $false: The rule is enabled. This is the default value. +- $false: The rule is enabled. This value is the default. ```yaml Type: Boolean @@ -914,7 +914,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this condition in DLP policies that are scoped only to Exchange. @@ -1446,7 +1446,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this exception in DLP policies that are scoped only to Exchange. @@ -1652,7 +1652,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, although small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, although small values might be rounded up to the nearest kilobyte. You can use this exception in DLP policies that are scoped only to Exchange. @@ -2476,7 +2476,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You can use this condition in DLP policies that are scoped only to Exchange. @@ -2835,7 +2835,7 @@ Accept wildcard characters: False The NotifyPolicyTipDialogOption parameter specifies a display option for the policy tip. Valid values are: -- Tip: Displays policy tip at the top of the mail. This is the default value. +- Tip: Displays policy tip at the top of the mail. This value is the default. - Dialog: Displays policy tip at the top of the mail and as a popup dialog. (exchange only) ```yaml @@ -3239,7 +3239,7 @@ Accept wildcard characters: False The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are: - None: You can't select this value if the rule has no actions configured. -- Low: This is the default value. +- Low: This value is the default. - Medium - High @@ -3299,7 +3299,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du - Ignore: Ignore the failure of the rule and thereby any actions in that rule and move to the next rule. - RetryThenBlock: Do a maximum of 5 retries of the rule with an increasing time gap of 10 min (i.e, 1st retry happens after 10 min, 2nd retry after 20 min, etc.). After the failure of the fifth retry, the message is dropped and we send a non-delivery report (also known as an NDR or bounce messages). -- Blank (the value $null): Defer the delivery of the message and keep retrying the rule. This is the default value. +- Blank (the value $null): Defer the delivery of the message and keep retrying the rule. This value is the default. ```yaml Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyRuleErrorAction @@ -3423,11 +3423,11 @@ Accept wildcard characters: False The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are: -- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This is the default value. +- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default. - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). - HeaderOrEnvelope: Examine senders in the message header and the message envelope. -Note that message envelope searching is available only for the following conditions and exceptions: +Message envelope searching is available only for the following conditions and exceptions: - From and ExceptIfFrom - FromAddressContainsWords and ExceptIfFromAddressContainsWords diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md index 5a996fc620..5229b5b8b3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md @@ -13,7 +13,7 @@ title: Set-DlpPolicy # Set-DlpPolicy ## SYNOPSIS -**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Set-DlpCompliancePolicy and Set-DlpComplianceRule cmdlets instead. +**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Set-DlpCompliancePolicy and Set-DlpComplianceRule cmdlets instead. This cmdlet is functional only in on-premises Exchange. @@ -36,7 +36,7 @@ Set-DlpPolicy [-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/Set-DlpSensitiveInformationType.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md index 73e210f497..7b6975cbdd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md @@ -13,7 +13,7 @@ title: Set-DlpSensitiveInformationType # Set-DlpSensitiveInformationType ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-DlpSensitiveInformationType cmdlet to modify sensitive information type rules that use document fingerprints. @@ -39,7 +39,7 @@ Set-DlpSensitiveInformationType [-Identity] [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md index 5626991ff1..dfc2e8dfb3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md @@ -47,7 +47,7 @@ Set-EcpVirtualDirectory [-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 @@ -137,7 +137,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. This parameter can be used with the FormsAuthentication parameter or with the DigestAuthentication and WindowsAuthentication parameters. @@ -182,7 +182,7 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. -- $false: Digest authentication is disabled. This is the default value. +- $false: Digest authentication is disabled. This value is the default. ```yaml Type: Boolean @@ -224,7 +224,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -244,7 +244,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -265,8 +265,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -402,7 +402,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The OwaOptionsEnabled parameter specifies that Outlook on the web Options is enabled for end users. If this parameter is set to $false, users aren't able to access Outlook on the web Options. You may want to disable access if your organization uses non-Microsoft provider tools. This parameter accepts $true or $false. +The OwaOptionsEnabled parameter specifies that Outlook on the web Options is enabled for end users. If this parameter is set to $false, users aren't able to access Outlook on the web Options. You might want to disable access if your organization uses non-Microsoft provider tools. This parameter accepts $true or $false. ```yaml Type: Boolean @@ -440,7 +440,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -- $true: Integrated Windows authentication is enabled. This is the default value. +- $true: Integrated Windows authentication is enabled. This value is the default. - $false: Integrated Windows authentication is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md index 3ee57372e0..46b76be6cb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md @@ -44,7 +44,7 @@ Set-EdgeSyncServiceConfig [-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 @@ -246,7 +246,7 @@ Accept wildcard characters: False The LogLevel parameter specifies the EdgeSync logging level. Valid values are: -- None (This is the default value) +- None (default value) - Low - Medium - High @@ -297,7 +297,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the LogMaxFileSize parameter must be less than or equal to the value of the LogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the EdgeSyncLog directory. @@ -327,7 +327,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the LogMaxFileSize parameter must be less than or equal to the value of the LogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the EdgeSyncLog files. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md index 1124b51735..1c7aeb2dd0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md @@ -13,7 +13,7 @@ title: Set-EmailAddressPolicy # Set-EmailAddressPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-EmailAddressPolicy cmdlet to modify email address policies. In Exchange Online, email address policies are available only for Microsoft 365 Groups. @@ -69,7 +69,7 @@ To create flexible filters that use any available recipient property and that ar You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -617,7 +617,7 @@ The DisabledEmailAddressTemplates parameter specifies the proxy email addresses Valid syntax for this parameter is `Type:AddressFormat`: -- Type: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. Note that you can't use SMTP to specify a disabled primary SMTP email address. +- Type: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. You can't use SMTP to specify a disabled primary SMTP email address. - AddressFormat: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example: alias@contoso.com requires the value `%m@contoso.com`, and firstname.lastname@contoso.com requires the value `%g.%s@contoso.com`. You can specify multiple disabled email address templates separated by commas: `"[Type1:]EmailAddress1","[Type2:]EmailAddress2",..."[TypeN:]EmailAddressN"`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md index bffda0e62d..efcc915182 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md @@ -32,7 +32,7 @@ Set-EmailTenantSettings [[-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/Set-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md index 9c20bb18f4..79703e4588 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md @@ -29,7 +29,7 @@ Set-EventLogLevel [-Identity] -Level ``` ## 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/Set-EventsFromEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-EventsFromEmailConfiguration.md index 706bc92788..f2f9e6efff 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EventsFromEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EventsFromEmailConfiguration.md @@ -44,7 +44,7 @@ Set-EventsFromEmailConfiguration [-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 @@ -95,7 +95,7 @@ Accept wildcard characters: False The CreateEventsFromEmailAsPrivate parameter specifies whether to create the events discovered from messages as normal or private events. Valid values are: -- $true: The events are crated as private events. This is the default value. +- $true: The events are crated as private events. This value is the default. - $false: The events are created as normal events. ```yaml @@ -114,7 +114,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: String @@ -136,9 +136,9 @@ The FlightReservationProcessingLevel parameter specifies whether flight reservat - Disabled: Do not discover flight reservations from messages. - Email: Discover flight reservations from messages, but don't automatically add them to the user's calendar. -- Calendar: Discover flight reservations from messages and automatically add them to the user's calendar. This is the default value. +- Calendar: Discover flight reservations from messages and automatically add them to the user's calendar. This value is the default. -Note that these values are case sensitive. +These values are case sensitive. ```yaml Type: String @@ -156,7 +156,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: String @@ -174,7 +174,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: String @@ -196,7 +196,7 @@ The LodgingReservationProcessingLevel parameter specifies whether lodging reserv - Disabled: Do not discover lodging reservations from messages. - Email: Discover lodging reservations from messages however do not automatically add these to the user's calendar. -- Calendar: Discover lodging reservations from messages and automatically add them to the user's calendar. This is the default value. +- Calendar: Discover lodging reservations from messages and automatically add them to the user's calendar. This value is the default. ```yaml Type: String @@ -218,7 +218,7 @@ The ParcelDeliveryProcessingLevel parameter specifies whether parcel deliveries - Disabled: Do not discover parcel deliveries from messages. - Email: Discover parcel deliveries from messages however do not automatically add these to the user's calendar. -- Calendar: Discover parcel deliveries from messages and automatically add them to the user's calendar. This is the default value. +- Calendar: Discover parcel deliveries from messages and automatically add them to the user's calendar. This value is the default. ```yaml Type: String @@ -240,7 +240,7 @@ The RentalCarReservationProcessingLevel parameter specifies whether rental car r - Disabled: Do not discover rental car reservations from messages. - Email: Discover rental car reservations from messages, but don't automatically add them to the user's calendar. -- Calendar: Discover rental car reservations from messages and automatically add them to the user's calendar. This is the default value. +- Calendar: Discover rental car reservations from messages and automatically add them to the user's calendar. This value is the default. ```yaml Type: String @@ -276,7 +276,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md index 01ea6df375..c8d43e777b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md @@ -47,7 +47,7 @@ Set-ExchangeAssistanceConfig [[-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 @@ -215,7 +215,7 @@ Accept wildcard characters: False The ExchangeHelpAppOnline specifies whether your organization uses the public help that's hosted by Microsoft. Valid values are: -- $true: Your organization uses the help that's hosted by Microsoft. This is the default value. +- $true: Your organization uses the help that's hosted by Microsoft. This value is the default. - $false: Your organization doesn't use the help that's hosted by Microsoft. You need to use the ControlPanelHelpURL, ManagementConsoleHelpURL, OWAHelpURL, and OWALightHelpURL parameters to configure the URLs where the help files are hosted. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md index a899325723..fd7e59be88 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md @@ -35,7 +35,7 @@ Set-ExchangeFeature [-Identity] ## DESCRIPTION The Set-ExchangeFeature cmdlet lets you approve or block features flighted via Feature Flighting, a service introduced in the Exchange Server 2019 CU15 (2025H1) update. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Set-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md index 1dc0ff53dd..d57443c90a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md @@ -47,7 +47,7 @@ Set-ExchangeServer [-Identity] ## DESCRIPTION The Set-ExchangeServer cmdlet sets generic Exchange attributes in Active Directory for a specified computer. You can only use this task on one server at a time. If you want to bulk manage your servers running Microsoft Exchange, add this task to a script. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -140,7 +140,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019 -The DataCollectionEnabled parameter specifies whether the EM Service will collect and send diagnostic data to Microsoft using OCS. Valid values are: +The DataCollectionEnabled parameter specifies whether the EM Service collects and send diagnostic data to Microsoft using OCS. Valid values are: - $true: The EM Service collects and sends diagnostic data to Microsoft using OCS. - $false: Data collection is disabled. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md index 84fe110fd6..82fde1fc28 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md @@ -194,7 +194,7 @@ Set-ExchangeSettings [-Identity] -Reason ``` ## 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/Set-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md index 0ff54a190c..42a575f418 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md @@ -35,7 +35,7 @@ Set-ExoPhishSimOverrideRule [-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/Set-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md index c289ce7162..adba6e057d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md @@ -33,7 +33,7 @@ Set-ExoSecOpsOverrideRule [-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/Set-ExternalInOutlook.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExternalInOutlook.md index 618f01f80b..682e01d1e0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExternalInOutlook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExternalInOutlook.md @@ -31,7 +31,7 @@ Set-ExternalInOutlook [[-Identity] ] ## DESCRIPTION If your organization already uses mail flow rules (also known as transport rules) to add text to the subject line of messages from external senders, you should disable those rules before you enable this feature to avoid duplication. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Set-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md index c18d4a1ee1..2f88fa08ee 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md @@ -13,7 +13,7 @@ title: Set-FederatedOrganizationIdentifier # Set-FederatedOrganizationIdentifier ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-FederatedOrganizationIdentifier cmdlet to configure the federated organization identifier for the Exchange organization. @@ -41,7 +41,7 @@ You must configure a federated organization identifier to create an account name You can temporarily disable federation by disabling the organization identifier. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Set-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md index 932434bdf2..9906bb2479 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md @@ -59,7 +59,7 @@ Set-FederationTrust [-Identity] ## DESCRIPTION You can use the Set-FederationTrust cmdlet to manage the certificates used for the federation trust. You can also use the Set-FederationTrust cmdlet to refresh the metadata document from the Microsoft Federation Gateway and download its certificate. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Set-FocusedInbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-FocusedInbox.md index 584d428bc6..7aca252699 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FocusedInbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FocusedInbox.md @@ -31,7 +31,7 @@ Set-FocusedInbox -Identity ## DESCRIPTION Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,7 +79,7 @@ Accept wildcard characters: False The FocusedInboxOn parameter enables or disables Focused Inbox for the mailbox. Valid values are: -- $true: Focused Inbox is enabled. This is the default value. +- $true: Focused Inbox is enabled. This value is the default. - $false: Focused Inbox is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md index 0ff39d0e21..39b7e32309 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md @@ -43,7 +43,7 @@ Set-ForeignConnector [-Identity] ## DESCRIPTION A Foreign connector uses a Drop directory in the Transport service of a Mailbox server to send messages to a local messaging server that doesn't use SMTP as its primary transport mechanism. These messaging servers are known as foreign gateway servers. Non-Microsoft fax gateway servers are examples of foreign gateway servers. The address spaces assigned to a Foreign connector can be SMTP or non-SMTP. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -84,7 +84,7 @@ Accept wildcard characters: False The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`. -- AddressSpaceType: The address space type may be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed. +- AddressSpaceType: The address space type might be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed. - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com isn't permitted. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address type, you can enter any text for the address space. - AddressSpaceCost : The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains a semicolon (;), you must specify the address space cost. @@ -95,7 +95,7 @@ If you specify the address space type or the address space cost, you must enclos - "SMTP:contoso.com" - contoso.com -You may specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`. +You might specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`. To add or remove one or more address space values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. @@ -176,7 +176,7 @@ Accept wildcard characters: False The DropDirectory parameter specifies the name of the Drop directory used by this Foreign connector. All outbound messages sent to address spaces defined by this Foreign connector are put in the specified Drop directory. The location of the Drop directory for each Foreign connector is controlled by the following two items: -- RootDropDirectoryPath parameter in the Set-TransportService cmdlet: This option is used for all Foreign connectors that exist on the Mailbox server. The value of the RootDropDirectoryPath parameter may be a local path or a Universal Naming Convention (UNC) path to a remote server. +- RootDropDirectoryPath parameter in the Set-TransportService cmdlet: This option is used for all Foreign connectors that exist on the Mailbox server. The value of the RootDropDirectoryPath parameter might be a local path or a Universal Naming Convention (UNC) path to a remote server. - DropDirectory parameter in the Set-ForeignConnector cmdlet: This value is set for each Foreign Connector that exists on the server. By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange 2010 installation folder. The default Exchange 2010 installation folder is C:\\Program Files\\Microsoft\\Exchange Server\\. By default, the value of the DropDirectory parameter is the name of the Foreign connector. @@ -217,7 +217,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 1 through 2147483647 bytes. If you enter a value of unlimited, no message size limit is imposed on the Drop directory. The default value is unlimited. @@ -303,7 +303,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. If you enter a value of unlimited, no message size limit is imposed on this Foreign connector. The default value is unlimited. The valid input range for this parameter is from 0 through 2147483647 kilobytes. If you set the value of the MaxMessageSize parameter to 0, you effectively disable the Foreign connector. However, if you set the value of the MaxMessageSize parameter to 0 when the value of the Enabled attribute is $true, you generate event log errors. The preferred method to disable the Foreign connector is to use the Enabled parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md index ae846c4f1f..d9a3a5221e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md @@ -72,7 +72,7 @@ Set-FrontendTransportService [-Identity] ## DESCRIPTION The Front End Transport service runs on all Mailbox servers and acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange organization. The Front End Transport service only communicates with the Transport service on a Mailbox server, and doesn't queue any messages locally. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -164,7 +164,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the AgentLogMaxFileSize parameter must be less than or equal to the value of the AgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log directory. @@ -194,7 +194,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the AgentLogMaxFileSize parameter must be less than or equal to the value of the AgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log files. @@ -323,7 +323,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log directory. @@ -353,7 +353,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log files. @@ -441,7 +441,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the DnsLogMaxFileSize parameter must be less than or equal to the value of the DnsLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the DNS log directory. @@ -471,7 +471,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the DnsLogMaxFileSize parameter must be less than or equal to the value of the DnsLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the DNS log files. @@ -545,7 +545,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000. +The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000. If the value of the ExternalDNSAdapterEnabled parameter is set to $false, the value of the ExternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the ExternalDNSServers parameter is used. @@ -639,7 +639,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000. +The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000. If the value of the InternalDNSAdapterEnabled parameter is set to $false, the value of the InternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the InternalDNSServers parameter is used. @@ -702,7 +702,7 @@ Accept wildcard characters: False The IntraOrgConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging on the implicit and invisible intra-organization Send connector In the Front End Transport service. Valid values are: - None: Protocol logging is disabled for the intra-organization Send connector in the Front End Transport service. -- Verbose: Protocol logging is enabled for the intra-organization Send connector in the Front End Transport service. This is the default value. The location of the log files is controlled by the SendProtocolLogPath parameter. +- Verbose: Protocol logging is enabled for the intra-organization Send connector in the Front End Transport service. This value is the default. The location of the log files is controlled by the SendProtocolLogPath parameter. ```yaml Type: ProtocolLoggingLevel @@ -774,7 +774,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be greater than or equal to the value of the ReceiveProtocolLogMaxFileSize parameter. @@ -808,7 +808,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the ReceiveProtocolLogMaxDirectorySize parameter. @@ -882,7 +882,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the routing table log directory. @@ -956,7 +956,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be greater than or equal to the value of the SendProtocolLogMaxDirectorySize parameter. @@ -990,7 +990,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md index 81ea55b283..1b6156bcc7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md @@ -13,7 +13,7 @@ title: Set-GlobalAddressList # Set-GlobalAddressList ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-GlobalAddressList cmdlet to modify an existing global address list (GAL). @@ -65,7 +65,7 @@ To create flexible filters that use any available recipient property and that ar You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Group.md b/exchange/exchange-ps/ExchangePowerShell/Set-Group.md index f585acbe6c..0d12511a23 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Group.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Group.md @@ -13,7 +13,7 @@ title: Set-Group # Set-Group ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-Group cmdlet to modify group object settings. If the group is a mail-enabled security group or a distribution group, you can use the Set-DistributionGroup cmdlet to modify other Microsoft Exchange settings that aren't available by using the Set-Group cmdlet. @@ -45,7 +45,7 @@ Set-Group [-Identity] ## DESCRIPTION You can't use the Set-Group cmdlet to modify dynamic distribution groups. To modify dynamic distribution groups, use the Set-DynamicDistributionGroup 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 @@ -65,7 +65,7 @@ Add a Notes parameter value of verified. Set-Group -Identity "Human Resources" -IsHierarchicalGroup $true -SeniorityIndex 1 ``` -This example specifies that the group Human Resources is a hierarchical group and will display last within its hierarchy because its index number is 1. +This example specifies that the group Human Resources is a hierarchical group and displays last within its hierarchy because its index number is 1. ## PARAMETERS @@ -344,7 +344,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The SeniorityIndex parameter specifies the order in which this group will display in a hierarchical address book. A group with a value of 2 will display higher in an address book than a group with a value of 1. +The SeniorityIndex parameter specifies the order in which this group displays in a hierarchical address book. A group with a value of 2 displays higher in an address book than a group with a value of 1. ```yaml Type: Int32 diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md index 33d71e298c..275525196e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md @@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the Set-HoldCompliancePolicy cmdlet to modify existing preservation policies in the Microsoft Purview compliance portal. -**Note**: The Set-HoldCompliancePolicy cmdlet has been replaced by the Set-RetentionCompliancePolicy cmdlet. If you have scripts that use Set-HoldCompliancePolicy, update them to use Set-RetentionCompliancePolicy. +**Note**: The Set-HoldCompliancePolicy cmdlet is replaced by the Set-RetentionCompliancePolicy cmdlet. If you have scripts that use Set-HoldCompliancePolicy, update them to use Set-RetentionCompliancePolicy. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -229,7 +229,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md index fd20b54fec..bebc71dc17 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md @@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the Set-HoldComplianceRule cmdlet to modify existing preservation rules in the Microsoft Purview compliance portal. -**Note**: The Set-HoldComplianceRule cmdlet has been replaced by the Set-RetentionComplianceRule cmdlet. If you have scripts that use Set-HoldComplianceRule, update them to use Set-RetentionComplianceRule. +**Note**: The Set-HoldComplianceRule cmdlet is replaced by the Set-RetentionComplianceRule cmdlet. If you have scripts that use Set-HoldComplianceRule, update them to use Set-RetentionComplianceRule. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -221,7 +221,7 @@ The HoldDurationDisplayHint parameter specifies the units that are used to displ - Months - Years -For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration. ```yaml Type: HoldDurationHint diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md index 90a43832ac..015064fe09 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md @@ -35,7 +35,7 @@ Set-HostedConnectionFilterPolicy [-Identity] Applicable: Exchange Online, Exchange Online Protection -The IPAllowList parameter specifies IP addresses from which messages are always allowed. Messages from the IP addresses you specify won't be identified as spam, despite any other spam characteristics of the messages. Valid values are: +The IPAllowList parameter specifies IP addresses from which messages are always allowed. Messages from the IP addresses you specify aren't identified as spam, despite any other spam characteristics of the messages. Valid values are: - Single IP address: For example, 192.168.1.1. - IP address range: You can use an IP address range, for example, 192.168.0.1-192.168.0.254. The maximum number of addresses in the range is 256. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md index ba1f227f67..65a16298ad 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md @@ -84,7 +84,7 @@ Set-HostedContentFilterPolicy [-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). For more information about the limits for allowed and blocked senders, see [Exchange Online Protection Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-protection-service-description/exchange-online-protection-limits). @@ -141,7 +141,7 @@ For example, if you enter the value `This-is-my-custom-header`, the X-header tha If you enter a value that contains spaces or colons (:), the value is ignored, and the default X-header is added to the message (`X-This-Is-Spam: This message appears to be spam.`). -Note that this setting is independent of the AddXHeader value of the TestModeAction parameter. +This setting is independent of the AddXHeader value of the TestModeAction parameter. ```yaml Type: String @@ -306,7 +306,7 @@ The BulkSpamAction parameter specifies the action to take on messages that are m - AddXHeader: Add the AddXHeaderValue parameter value to the message header and deliver the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). -- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). - NoAction - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. @@ -327,7 +327,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages will trigger the action that's specified by the BulkSpamAction parameter. +The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages triggers the action specified by the BulkSpamAction parameter. A higher BCL indicates the message is more likely to generate complaints (and is therefore more likely to be spam). For more information, see [Bulk complaint level (BCL) in EOP](https://learn.microsoft.com/defender-office-365/anti-spam-bulk-complaint-level-bcl-about). @@ -368,7 +368,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: Boolean @@ -386,7 +386,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: Boolean @@ -407,7 +407,7 @@ Accept wildcard characters: False The EnableLanguageBlockList parameter enables or disables marking messages that were written in specific languages as spam. Valid values are: - $true: Mark messages hat were written in the languages specified by the LanguageBlockList parameter as spam. -- $false: Don't mark messages as spam solely based on their languages. This is the default value. +- $false: Don't mark messages as spam solely based on their languages. This value is the default. ```yaml Type: Boolean @@ -428,7 +428,7 @@ Accept wildcard characters: False The EnableRegionBlockList parameter enables or disables marking messages that are sent from specific countries or regions as spam. Valid values are: - $true: Mark messages from senders in the RegionBlockList parameter as spam. -- $false: Don't mark messages as spam solely based on the source country or region. This is the default value. +- $false: Don't mark messages as spam solely based on the source country or region. This value is the default. ```yaml Type: Boolean @@ -446,7 +446,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: SmtpAddress @@ -464,7 +464,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: String @@ -482,7 +482,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: String @@ -500,7 +500,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: Int32 Parameter Sets: (All) @@ -517,7 +517,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. +This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters. ```yaml Type: EsnLanguage @@ -657,8 +657,8 @@ Accept wildcard characters: False The IncreaseScoreWithBizOrInfoUrls parameter increases the spam score of messages that contain links to .biz or .info domains. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. -- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting will be marked as spam. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. +- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting are marked as spam. - Test: The action specified by the TestModeAction parameter is taken on the message. ```yaml @@ -679,8 +679,8 @@ Accept wildcard characters: False The IncreaseScoreWithImageLinks parameter increases the spam score of messages that contain image links to remote websites. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. -- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting will be marked as spam. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. +- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting aree marked as spam. - Test: The action specified by the TestModeAction parameter is taken on the message. ```yaml @@ -701,7 +701,7 @@ Accept wildcard characters: False The IncreaseScoreWithNumericIps parameter increases the spam score of messages that contain links to IP addresses. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain links to IP addresses are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -723,7 +723,7 @@ Accept wildcard characters: False The IncreaseScoreWithRedirectToOtherPort parameter increases the spam score of messages that contain links that redirect to TCP ports other than 80 (HTTP), 8080 (alternate HTTP), or 443 (HTTPS). Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -745,7 +745,7 @@ Accept wildcard characters: False The InlineSafetyTipsEnabled parameter specifies whether to enable or disable safety tips that are shown to recipients in messages. Valid values are: -- $true: Safety tips are enabled. This is the default value. +- $true: Safety tips are enabled. This value is the default. - $false: Safety tips are disabled. ```yaml @@ -766,7 +766,7 @@ Accept wildcard characters: False The IntraOrgFilterState parameter specifies whether to enable anti-spam filtering for messages sent between internal users (users in the same organization). The action that's configured in the policy for the specified spam filter verdicts is taken on messages sent between internal users. Valid values are: -- Default: This is the default value. Currently, HighConfidencePhish. +- Default: This value is the default. Currently, HighConfidencePhish. - HighConfidencePhish - Phish: Includes phishing and high confidence phishing. - HighConfidenceSpam: Includes high confidence spam, phishing, and high confidence phishing. @@ -840,7 +840,7 @@ Accept wildcard characters: False The MarkAsSpamBulkMail parameter allows spam filtering to act on bulk email messages. Valid values are: - Off: The message is stamped with the BCL, but no action is taken for a bulk email filtering verdict. In effect, the values of the BulkThreshold and BulkSpamAction parameters are irrelevant. -- On: This is the default value. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message. +- On: This value is the default. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message. - Test: This value is available, but isn't used for this parameter. ```yaml @@ -861,7 +861,7 @@ Accept wildcard characters: False The MarkAsSpamEmbedTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Embed tag in html` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -883,7 +883,7 @@ Accept wildcard characters: False The MarkAsSpamEmptyMessages parameter marks a message as spam when the message contains no subject, no content in the message body, and no attachments. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Empty messages are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Empty Message` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -905,7 +905,7 @@ Accept wildcard characters: False The MarkAsSpamFormTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Form tag in html` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -927,7 +927,7 @@ Accept wildcard characters: False The MarkAsSpamFramesInHtml parameter marks a message as spam when the message contains HTML \ or \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ or \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: IFRAME or FRAME in HTML` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -949,7 +949,7 @@ Accept wildcard characters: False The MarkAsSpamFromAddressAuthFail parameter marks a message as spam when Sender ID filtering encounters a hard fail. This setting combines an Sender Policy Framework (SPF) check with a Sender ID check to help protect against message headers that contain forged senders. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages where Sender ID filtering encounters a hard fail are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF From Record Fail` is added to the message. ```yaml @@ -970,7 +970,7 @@ Accept wildcard characters: False The MarkAsSpamJavaScriptInHtml parameter marks a message as spam when the message contains JavaScript or VBScript. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain JavaScript or VBScript are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Javascript or VBscript tags in HTML` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -992,7 +992,7 @@ Accept wildcard characters: False The MarkAsSpamNdrBackscatter parameter marks a message as spam when the message is a non-delivery report (also known as an NDR or bounce messages) sent to a forged sender (known as *backscatter*). Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Backscatter is given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Backscatter NDR` is added to the message. ```yaml @@ -1013,7 +1013,7 @@ Accept wildcard characters: False The MarkAsSpamObjectTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain HTML \ tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Object tag in html` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -1035,7 +1035,7 @@ Accept wildcard characters: False The MarkAsSpamSensitiveWordList parameter marks a message as spam when the message contains words from the sensitive words list. Microsoft maintains a dynamic but non-editable list of words that are associated with potentially offensive messages. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain words from the sensitive word list in the subject or message body are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Sensitive word in subject/body` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -1057,7 +1057,7 @@ Accept wildcard characters: False The MarkAsSpamSpfRecordHardFail parameter marks a message as spam when SPF record checking encounters a hard fail. Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages sent from an IP address that isn't specified in the SPF Sender Policy Framework (SPF) record in DNS are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF Record Fail` is added to the message. ```yaml @@ -1078,7 +1078,7 @@ Accept wildcard characters: False The MarkAsSpamWebBugsInHtml parameter marks a message as spam when the message contains web bugs (also known as web beacons). Valid values are: -- Off: The setting is disabled. This is the default value, and we recommend that you don't change it. +- Off: The setting is disabled. This value is the default, and we recommend that you don't change it. - On: The setting is enabled. Messages that contain web bugs are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Web bug` is added to the message. - Test: The action specified by the TestModeAction parameter is taken on the message. @@ -1178,7 +1178,7 @@ Accept wildcard characters: False The PhishZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect phishing in already delivered messages in Exchange Online mailboxes. Valid values are: -- $true: ZAP for phishing messages is enabled. This is the default value. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. +- $true: ZAP for phishing messages is enabled. This value is the default. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. - $false: ZAP for phishing messages is disabled. You configure ZAP for spam with the SpamZapEnabled parameter. @@ -1285,7 +1285,7 @@ The SpamAction parameter specifies the action to take on messages that are marke - AddXHeader: Add the AddXHeaderValue parameter value to the message header, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). -- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. @@ -1335,7 +1335,7 @@ Accept wildcard characters: False The SpamZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect spam in already delivered messages in Exchange Online mailboxes. Valid values are: -- $true: ZAP for spam is enabled. This is the default value. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. +- $true: ZAP for spam is enabled. This value is the default. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message. - $false: ZAP for spam is disabled. You configure ZAP for phishing messages with the PhishZapEnabled parameter. @@ -1358,7 +1358,7 @@ Accept wildcard characters: False The TestModeAction parameter specifies the additional action to take on messages when one or more IncreaseScoreWith\* or MarkAsSpam\* ASF parameters are set to the value Test. Valid values are: -- None: This is the default value, and we recommend that you don't change it. +- None: This value is the default, and we recommend that you don't change it. - AddXHeader: The X-header value `X-CustomSpam: This message was filtered by the custom spam filter option` is added to the message. - BccMessage: Redirect the message to the recipients specified by the TestModeBccToRecipients parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md index 120a069048..d2689d5311 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md @@ -42,7 +42,7 @@ Set-HostedContentFilterRule [-Identity] > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Use the Microsoft Defender portal to create anti-spam policies](https://learn.microsoft.com/defender-office-365/anti-spam-policies-configure#use-the-microsoft-defender-portal-to-create-anti-spam-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md index fe113889c6..bc15d5b3d0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md @@ -39,7 +39,7 @@ Set-HostedOutboundSpamFilterPolicy [-Identity] Applicable: Exchange Online, Exchange Online Protection -**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). +**Note**: This setting is replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). The NotifyOutboundSpam parameter specify whether to notify admins when outgoing spam is detected. Valid values are: - $true: Notify the admins specified by the NotifyOutboundSpamRecipients parameter. -- $false: Don't send notifications. This is the default value. +- $false: Don't send notifications. This value is the default. ```yaml Type: Boolean @@ -232,7 +232,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). +**Note**: This setting is replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users). The NotifyOutboundSpamRecipients parameter specifies the email addresses of admins to notify when an outgoing spam is detected. You can specify multiple email addresses separated by commas. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md index f404f720ce..d5d7fc9ec7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md @@ -39,7 +39,7 @@ Set-HostedOutboundSpamFilterRule [-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/Set-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md index b9750e5e1b..6e76762288 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md @@ -45,7 +45,7 @@ Set-HybridConfiguration ## DESCRIPTION The Set-HybridConfiguration cmdlet modifies the hybrid configuration features, such as enabling secure mail, designating a specific Mailbox server for hybrid functionality, or enabling or disabling free/busy sharing between on-premises Exchange and Exchange Online. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,7 +54,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Set-HybridConfiguration -SecureMailCertificateThumbprint AC00F35CBA8359953F4126E0984B5CCAFA2F4F17 ``` -In Exchange Server 2010, this example specifies that the hybrid configuration will use the certificate with the thumbprint AC00F35CBA8359953F4126E0984B5CCAFA2F4F17 as the certificate for Secure Mail messaging. +In Exchange Server 2010, this example specifies the hybrid configuration uses the certificate with the thumbprint AC00F35CBA8359953F4126E0984B5CCAFA2F4F17 as the certificate for Secure Mail messaging. ### Example 2 ```powershell @@ -210,7 +210,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. There can be only one HybridConfiguration object in an Exchange organization. @@ -277,7 +277,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010. -The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X.509 certificate to be used as the certificate for hybrid deployment secure message transport. This certificate cannot be self-signed, must be obtained from a trusted certificate authority (CA), and must be installed on all Hub Transport servers defined in the TransportServers parameter. +The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X.509 certificate to be used as the certificate for hybrid deployment secure message transport. This certificate can't be self-signed, must be obtained from a trusted certificate authority (CA), and must be installed on all Hub Transport servers defined in the TransportServers parameter. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md index 84722adaa4..31c494d89b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md @@ -13,7 +13,7 @@ title: Set-IRMConfiguration # Set-IRMConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-IRMConfiguration cmdlet to configure Information Rights Management (IRM) features on your organization. @@ -54,7 +54,7 @@ Set-IRMConfiguration [-Identity ] ## DESCRIPTION IRM requires the use of an on-premises AD RMS server or the ILS service. IRM features can be selectively enabled or disabled. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -109,7 +109,7 @@ This parameter is available only in the cloud-based service. The AutomaticServiceUpdateEnabled parameter specifies whether to allow the automatic addition of new features within Azure Information Protection for your cloud-based organization. Valid values are: -- $true: New Azure Information Protection features announced through Microsoft 365 message center will be enabled automatically in your cloud-based organization. +- $true: New Azure Information Protection features announced through Microsoft 365 message center are enabled automatically in your cloud-based organization. - $false: Prevents new Azure Information Protection features from automatically being introduced into your tenant organization. ```yaml @@ -155,7 +155,7 @@ This parameter is available only in on-premises Exchange. The ClientAccessServerEnabled parameter specifies whether Exchange Client Access servers are allowed to authenticate clients that do not have direct access to AD RMS (for example, Outlook on the web, Exchange ActiveSync or remote Outlook Anywhere clients). Valid values are: -- $true: Client Access servers are allowed to authenticate clients. This is the default value. Note that enabling IRM in Outlook on the web requires additional configuration on AD RMS servers. For more information, see [Information Rights Management in Outlook Web App](https://learn.microsoft.com/exchange/information-rights-management-in-outlook-web-app-exchange-2013-help). +- $true: Client Access servers are allowed to authenticate clients. This value is the default. Enabling IRM in Outlook on the web requires additional configuration on AD RMS servers. For more information, see [Information Rights Management in Outlook Web App](https://learn.microsoft.com/exchange/information-rights-management-in-outlook-web-app-exchange-2013-help). - $false: Client Access servers aren't allowed to authenticate clients. ```yaml @@ -199,8 +199,8 @@ This parameter is available only in the cloud-based service. The DecryptAttachmentForEncryptOnly parameter specifies whether mail recipients have unrestricted rights on the attachment or not for Encrypt-only mails sent using Microsoft Purview Message Encryption. Valid values are: -- $true: The recipients will have unrestricted rights on attachments sent using Encrypt-Only policy. -- $false: The recipients will not have unrestricted rights on attachments sent using Encrypt-Only policy. +- $true: The recipients have unrestricted rights on attachments sent using Encrypt-Only policy. +- $false: The recipients don't have unrestricted rights on attachments sent using Encrypt-Only policy. This parameter replaces the deprecated DecryptAttachmentFromPortal parameter. @@ -313,12 +313,12 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The ExternalLicensingEnabled parameter specifies whether Exchange will try to acquire licenses from clusters other than the one it is configured to use. Without this setting, if Exchange receives many messages protected with a random key, the server will devote excessive resources to validating signatures and decrypting messages, even if the keys aren't valid. +The ExternalLicensingEnabled parameter specifies whether Exchange tries to acquire licenses from clusters other than the one it is configured to use. Without this setting, if Exchange receives many messages protected with a random key, the server devotes excessive resources to validating signatures and decrypting messages, even if the keys aren't valid. Valid values are: -- $true: Exchange will try to acquire licenses from clusters other than the one it is configured to use. This value can help prevent denial of service (DoS) attacks. -- $false: Exchange will try to acquire licenses only from clusters that it is configured to use. This is the default value. The *LicensingLocation* parameter specifies the list of allowed clusters. +- $true: Exchange tries to acquire licenses from clusters other than the one it is configured to use. This value can help prevent denial of service (DoS) attacks. +- $false: Exchange tries to acquire licenses only from clusters that it is configured to use. This value is the default. The *LicensingLocation* parameter specifies the list of allowed clusters. ```yaml Type: Boolean @@ -360,8 +360,8 @@ Accept wildcard characters: False The InternalLicensingEnabled parameter specifies whether to enable IRM features for messages that are sent to internal recipients. Valid values are: -- $true: IRM features are enabled for internal messages. This is the default value in Exchange Online. -- $false: IRM features are disabled for internal messages. This is the default value in on-premises Exchange. Note that this value causes the Get-RMSTemplate to return no AD RMS templates. +- $true: IRM features are enabled for internal messages. This value is the default in Exchange Online. +- $false: IRM features are disabled for internal messages. This value is the default in on-premises Exchange. This value causes the Get-RMSTemplate to return no AD RMS templates. ```yaml Type: Boolean @@ -381,7 +381,7 @@ Accept wildcard characters: False The JournalReportDecryptionEnabled parameter specifies whether to enable journal report decryption. Valid values are: -- $true: Journal report encryption is enabled. A decrypted copy of the IRM-protected message is attached to the journal report. This is the default value. Note that journal report decryption requires additional configuration on AD RMS servers. For more information, see [Journal report decryption](https://learn.microsoft.com/exchange/journal-report-decryption-exchange-2013-help). +- $true: Journal report encryption is enabled. A decrypted copy of the IRM-protected message is attached to the journal report. This value is the default. Journal report decryption requires additional configuration on AD RMS servers. For more information, see [Journal report decryption](https://learn.microsoft.com/exchange/journal-report-decryption-exchange-2013-help). - $false: Journal report decryption is disabled. ```yaml @@ -404,7 +404,7 @@ The LicensingLocation parameter specifies the RMS licensing URLs. You can specif Typically, in on-premises Exchange, you only need to use this parameter in cross-forest deployments of AD RMS licensing servers. -**IMPORTANT**: If you specify multiple URLs, always specify the Azure RMS URL first. Otherwise, encryption services won't function properly. +**IMPORTANT**: If you specify multiple URLs, always specify the Azure RMS URL first. Otherwise, encryption services don't function properly. ```yaml Type: MultiValuedProperty @@ -486,7 +486,7 @@ Accept wildcard characters: False The SearchEnabled parameter specifies whether to enable searching of IRM-encrypted messages in Outlook on the web (formerly known as Outlook Web App). Valid values are: -- $true: Searching IRM-encrypted messages in Outlook on the web is enabled. This is the default value. +- $true: Searching IRM-encrypted messages in Outlook on the web is enabled. This value is the default. - $false: Searching IRM-encrypted messages in Outlook on the web is disabled. ```yaml @@ -533,7 +533,7 @@ This parameter is available only in the cloud-based service. The SimplifiedClientAccessEnabled parameter specifies whether to enable the Protect button in Outlook on the web. Valid values are: - $true: The Protect button is enabled in Outlook on the web. -- $false: The Protect button is disabled in Outlook on the web. This is the default value. +- $false: The Protect button is disabled in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -578,7 +578,7 @@ The TransportDecryptionSetting parameter specifies the transport decryption conf - Disabled: Transport decryption is disabled for internal and external messages. - Mandatory: Messages that can't be decrypted are rejected with a non-delivery report (also known as an NDR or bounce message). -- Optional: Messages are decrypted if possible, but are delivered even if decryption fails. This is the default value. +- Optional: Messages are decrypted if possible, but are delivered even if decryption fails. This value is the default. ```yaml Type: TransportDecryptionSetting diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md index 8e5266dbf8..c596ae4a64 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md @@ -59,7 +59,7 @@ Set-ImapSettings [-AuthenticatedConnectionTimeout ] ## DESCRIPTION You can run the Set-ImapSettings cmdlet for a single Exchange server that's running the Microsoft Exchange IMAP4 service, or for all Exchange servers that are running the Microsoft Exchange IMAP4 service. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -98,7 +98,7 @@ Set-ImapSettings -X509CertificateName mail.contoso.com This example specifies the certificate that contains mail.contoso.com is used to encrypt IMAP4 client connections. -**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange IMAP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange IMAP service (you'll receive an error if you try). +**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange IMAP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange IMAP service (you get an error if you try). ## PARAMETERS @@ -148,7 +148,7 @@ Accept wildcard characters: False The CalendarItemRetrievalOption parameter specifies how calendar items are presented to IMAP4 clients. Valid values are: -- 0 or iCalendar. This is the default value. +- 0 or iCalendar. This value is the default. - 1 or IntranetUrl - 2 or InternetUrl - 3 or Custom @@ -213,7 +213,7 @@ Accept wildcard characters: False The EnableExactRFC822Size parameter specifies how message sizes are presented to IMAP4 clients. Valid values are: - $true: Calculate the exact message size. Because this setting can negatively affect performance, you should configure it only if it's required by your IMAP4 clients. -- $false: Use an estimated message size. This is the default value. +- $false: Use an estimated message size. This value is the default. ```yaml Type: Boolean @@ -233,7 +233,7 @@ Accept wildcard characters: False The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Integrated Windows authentication (NTLM) using the Generic Security Services application programming interface (GSSAPI). This setting applies to connections where Transport Layer Security (TLS) is disabled. Valid values are: -- $true: NTLM for IMAP4 connections is enabled. This is the default value. +- $true: NTLM for IMAP4 connections is enabled. This value is the default. - $false: NTLM for IMAP4 connections is disabled. ```yaml @@ -257,7 +257,7 @@ The EnforceCertificateErrors parameter specifies whether to enforce valid Secure The default setting is $false. - $true: If the certificate isn't valid or doesn't match the target IMAP4 server's FQDN, the connection attempt fails. -- $false: The server doesn't deny IMAP4 connections based on certificate errors. This is the default value. +- $false: The server doesn't deny IMAP4 connections based on certificate errors. This value is the default. ```yaml Type: Boolean @@ -277,7 +277,7 @@ Accept wildcard characters: False The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is used. Valid values are: -- None: Extended Protection for Authentication isn't used. This is the default value. +- None: Extended Protection for Authentication isn't used. This value is the default. - Allow: Extended Protection for Authentication is used only if it's supported by the incoming IMAP4 connection. If it's not, Extended Protection for Authentication isn't used. - Require: Extended Protection for Authentication is required for all IMAP4 connections. If the incoming IMAP4 connection doesn't support it, the connection is rejected. @@ -377,8 +377,8 @@ Accept wildcard characters: False The LogFileRollOverSettings parameter specifies how frequently IMAP4 protocol logging creates a new log file. Valid values are: -- 1 or Hourly. This is the default value in Exchange 2019 and Exchange 2016. -- 2 or Daily. This is the default value in Exchange 2013 and Exchange 2010. +- 1 or Hourly. This value is the default in Exchange 2019 and Exchange 2016. +- 2 or Daily. This value is the default in Exchange 2013 and Exchange 2010. - 3 or Weekly. - 4 or Monthly. @@ -404,7 +404,7 @@ The LoginType parameter specifies the authentication method for IMAP4 connection - 1 or PlainTextLogin. - 2 or PlainTextAuthentication. -- 3 or SecureLogin. This is the default value. +- 3 or SecureLogin. This value is the default. ```yaml Type: LoginOptions @@ -432,7 +432,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The default value is 0, which means a new IMAP4 protocol log file is created at the frequency that's specified by the LogFileRollOverSettings parameter. @@ -533,7 +533,7 @@ The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages - 2 or HtmlAndTextAlternative. - 3 or TextEnrichedOnly. - 4 or TextEnrichedAndTextAlternative. -- 5 or BestBodyFormat. This is the default value. +- 5 or BestBodyFormat. This value is the default. - 6 or Tnef. ```yaml @@ -595,7 +595,7 @@ Accept wildcard characters: False The ProtocolLogEnabled parameter specifies whether to enable protocol logging for IMAP4. Valid values are: - $true: IMAP4 protocol logging is enabled. -- $false: IMAP4 protocol logging is disabled. This is the default value. +- $false: IMAP4 protocol logging is disabled. This value is the default. ```yaml Type: Boolean @@ -659,7 +659,7 @@ Accept wildcard characters: False The ShowHiddenFoldersEnabled parameter specifies whether hidden mailbox folders are visible. Valid values are: - $true: Hidden folders are visible. -- $false: Hidden folders aren't visible. This is the default value. +- $false: Hidden folders aren't visible. This value is the default. ```yaml Type: Boolean @@ -704,7 +704,7 @@ Accept wildcard characters: False The SuppressReadReceipt parameter specifies whether to stop duplicate read receipts from being sent to IMAP4 clients that have the Send read receipts for messages I send setting configured in their IMAP4 email program. Valid values are: - $true: The sender receives a read receipt only when the recipient opens the message. -- $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This is the default value. +- $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md index ab649d275a..cd67b28eb5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md @@ -52,7 +52,7 @@ Set-InboundConnector [-Identity] ## DESCRIPTION Inbound connectors accept email messages from remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -117,7 +117,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f Valid values are: -- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. +- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. ```yaml @@ -177,7 +177,7 @@ Accept wildcard characters: False The ConnectorSource parameter specifies how the connector is created. Valid input for this parameter includes the following values: -- Default: The connector is manually created. This is the default value. +- Default: The connector is manually created. This value is the default. - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. @@ -247,7 +247,7 @@ Accept wildcard characters: False The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connectors. Valid values are: - $true: Only the last message source is skipped. -- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This is the default value. +- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This value is the default. ```yaml Type: Boolean @@ -323,7 +323,7 @@ Accept wildcard characters: False The Enabled parameter enables or disables the connector. Valid values are: -- $true: The connector is enabled. This is the default value. +- $true: The connector is enabled. This value is the default. - $false: The connector is disabled. ```yaml @@ -362,7 +362,7 @@ Accept wildcard characters: False The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by a Partner type connector. Valid values are: -- $true: Reject messages if they aren't sent over TLS. This is the default value +- $true: Reject messages if they aren't sent over TLS. This value is the default - $false: Allow messages if they aren't sent over TLS. **Note**: This parameter applies only to Partner type connectors. @@ -386,7 +386,7 @@ Accept wildcard characters: False The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the Partner type connector. Valid values are: - $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value. -- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value. +- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This value is the default. **Note**: This parameter applies only to Partner type connectors. @@ -409,7 +409,7 @@ Accept wildcard characters: False The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses for Partner type connectors. Valid values are: - $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter. -- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value. +- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This value is the default. **Note**: This parameter applies only to Partner type connectors. @@ -514,7 +514,7 @@ Accept wildcard characters: False The TreatMessagesAsInternal parameter specifies an alternative method to identify messages sent from an on-premises organization as internal messages. You should only consider using this parameter when your on-premises organization doesn't use Exchange. Valid values are: - $true: Messages are considered internal if the sender's domain matches a domain that's configured in Microsoft 365. This setting allows internal mail flow between Microsoft 365 and on-premises organizations that don't have Exchange Server 2010 or later installed. However, this setting has potential security risks (for example, internal messages bypass antispam filtering), so use caution when configuring this setting. -- $false: Messages aren't considered internal. This is the default value. +- $false: Messages aren't considered internal. This value is the default. In hybrid environments, you don't need to use this parameter, because the Hybrid Configuration wizard automatically configures the required settings on the Inbound connector in Microsoft 365 and the Send connector in the on-premises Exchange organization (the CloudServicesMailEnabled parameter). diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md index 59223edb84..a9d14c5d20 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md @@ -13,7 +13,7 @@ title: Set-InboxRule # Set-InboxRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-InboxRule cmdlet to modify existing Inbox rules in mailboxes. Inbox rules process messages in the Inbox based on conditions specified and take actions such as moving a message to a specified folder or deleting a message. @@ -100,7 +100,7 @@ The Set-InboxRule cmdlet allows you to modify the rule conditions, exceptions, a When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -905,7 +905,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the ExceptIfWithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of ExceptIfWithinSizeRangeMinimum. @@ -937,7 +937,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the ExceptIfWithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of ExceptIfWithinSizeRangeMaximum. @@ -1016,7 +1016,7 @@ Accept wildcard characters: False The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. -A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet. +A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet. ```yaml Type: SwitchParameter @@ -1816,7 +1816,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the WithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of WithinSizeRangeMinimum. @@ -1848,7 +1848,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the WithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of WithinSizeRangeMaximum. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md index fb7f1e6a95..54ac46f17a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md @@ -13,7 +13,7 @@ title: Set-IntraOrganizationConnector # Set-IntraOrganizationConnector ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-IntraOrganizationConnector cmdlet to modify an existing Intra-Organization connector between two on-premises Exchange forests in an organization, between an on-premises Exchange organization and an Exchange Online organization or between two Exchange Online organizations. @@ -36,7 +36,7 @@ Set-IntraOrganizationConnector [-Identity] Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The TargetAddressDomains parameter specifies the domain namespaces that will be used in the Intra-Organization connector. The domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity. +The TargetAddressDomains parameter specifies the domain namespaces to be used in the Intra-Organization connector. The domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity. ```yaml Type: MultiValuedProperty @@ -174,7 +174,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services that will be used in the Intra-Organization connector. +The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services to be used in the Intra-Organization connector. ```yaml Type: Uri diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md index 7cd7eda4b9..f0a36d4384 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md @@ -13,7 +13,7 @@ title: Set-JournalRule # Set-JournalRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-JournalRule cmdlet to modify an existing journal rule in your organization. @@ -36,7 +36,7 @@ Set-JournalRule [-Identity] ## DESCRIPTION The Set-JournalRule cmdlet modifies an existing journal rule used in your 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/Set-Label.md b/exchange/exchange-ps/ExchangePowerShell/Set-Label.md index fd2b100f35..9afee26214 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Label.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Label.md @@ -159,7 +159,7 @@ Some of the settings that you configure with this parameter are supported only b Supported settings for built-in labeling: -- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting impacts services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `Set-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content). +- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting affects services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `Set-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content). - **Color**: Specifies a label color as a hex triplet code for the red, green, and blue (RGB) components of the color. Example: `Set-Label -Identity 8faca7b8-8d20-48a3-8ea2-0f96310a848e -AdvancedSettings @{color="#40e0d0"}`. For more information, see [Configuring custom colors by using PowerShell](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configuring-custom-colors-by-using-powershell). diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md index 8646340ea5..7d14426eaa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md @@ -416,7 +416,7 @@ Supported settings for built-in labeling: - **teamworkdefaultlabelid**: Outlook and Teams apps that support this setting apply a default label, or no label for meetings. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{teamworkdefaultlabelid="General"}`. For more information about labeling meetings, see [Use sensitivity labels to protect calendar items, Teams meetings, and chat](https://learn.microsoft.com/purview/sensitivity-labels-meetings). -- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) will be displayed. Users can't revert this setting in the app. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}` +- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) are displayed. Users can't revert this setting in the app. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}` - **DisableShowSensitiveContent**: For Office apps that highlight the sensitive content that caused a label to be recommended, turn off these highlights and corresponding indications about the sensitive content. For more information, see [Sensitivity labels are automatically applied or recommended for your files and emails in Office](https://support.microsoft.com/office/sensitivity-labels-are-automatically-applied-or-recommended-for-your-files-and-emails-in-office-622e0d9c-f38c-470a-bcdb-9e90b24d71a1). Supported apps: Word for Windows (version 2311+). Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{DisableShowSensitiveContent="True"}` diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md index 63c3c474f2..5b19885817 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md @@ -32,7 +32,7 @@ Set-LinkedUser [-Identity] ## DESCRIPTION The OLSync service account is the only linked user in your organization. By default, the account is named GALSync-ServiceAccount. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Set-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md index ef3f52b177..4d44abfb09 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md @@ -46,7 +46,7 @@ Set-M365DataAtRestEncryptionPolicy [-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 @@ -62,7 +62,7 @@ This example disabled the Microsoft 365 data-at-rest encryption policy named Ten Set-M365DataAtRestEncryptionPolicy -Identity "Tenant Default Policy" -Refresh ``` -This example updates the Microsoft 365 data-at-rest encryption policy named Tenant Default Policy after one of the associated keys has been rotated in the Azure Key Vault. +This example updates the Microsoft 365 data-at-rest encryption policy named Tenant Default Policy after one of the associated keys is rotated in the Azure Key Vault. ## PARAMETERS @@ -151,7 +151,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md index b33473efcb..321d855a48 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md @@ -26,7 +26,7 @@ Set-M365DataAtRestEncryptionPolicyAssignment -DataEncryptionPolicy ``` ## 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 @@ -367,7 +367,7 @@ This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: -- $true: A DTMF map is created for the recipient. This is the default value. +- $true: A DTMF map is created for the recipient. This value is the default. - $false: A DTMF map isn't created for the recipient. ```yaml @@ -737,7 +737,7 @@ This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -762,7 +762,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -786,7 +786,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -810,7 +810,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -834,7 +834,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -858,7 +858,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -956,7 +956,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -1001,7 +1001,7 @@ Accept wildcard characters: False The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: -- BinHex (This is the default value) +- BinHex (default value) - UuEncode - AppleSingle - AppleDouble @@ -1087,7 +1087,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited. @@ -1146,7 +1146,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited. @@ -1174,7 +1174,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -1200,7 +1200,7 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text -- Mime (This is the default value) +- Mime (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -1259,7 +1259,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -1537,7 +1537,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -1642,7 +1642,7 @@ Accept wildcard characters: False The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are: - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact. -- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. +- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md index 7b5cf8c9e7..08ae62604e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md @@ -13,7 +13,7 @@ title: Set-MailPublicFolder # Set-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 Set-MailPublicFolder cmdlet to configure the mail-related settings of mail-enabled public folders. If you want to configure basic settings that aren't mail-related, use the Set-PublicFolder cmdlet. @@ -91,7 +91,7 @@ Set-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 @@ -791,7 +791,7 @@ Accept wildcard characters: False The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -834,7 +834,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -858,7 +858,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -882,7 +882,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -906,7 +906,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -930,7 +930,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1038,7 +1038,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -1082,7 +1082,7 @@ Accept wildcard characters: False The IgnoreMissingFolderLink parameter specifies whether to exclude the mail-enabled public folder from a specific validation check that's used during a public folder migration. Valid values are: - $true: Skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the public folder is ignored, and the public folder migration can continue. -- $false: Don't skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the entire public folder migration will fail. This is the default value. +- $false: Don't skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the entire public folder migration will fail. This value is the default. ```yaml Type: Boolean @@ -1158,7 +1158,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -1189,7 +1189,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -1245,7 +1245,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -1494,7 +1494,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md index ffe35144e9..8ecd9e7617 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md @@ -13,7 +13,7 @@ title: Set-MailUser # Set-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 Set-MailUser cmdlet to modify mail users. Mail users (also known as mail-enabled users) have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. @@ -945,7 +945,7 @@ Set-MailUser [-Identity] [-UnblockForwardSyncPostCrossTena ``` ## 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 @@ -954,7 +954,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Set-MailUser -Identity "John Woods" -ExternalEmailAddress john@tailspintoys.com ``` -This example modifies the external email address for the mail user named John Woods. Note that the original external email address isn't kept as a proxy address. +This example modifies the external email address for the mail user named John Woods. The original external email address isn't kept as a proxy address. ## PARAMETERS @@ -1257,7 +1257,7 @@ This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: -- $true: A DTMF map is created for the recipient. This is the default value. +- $true: A DTMF map is created for the recipient. This value is the default. - $false: A DTMF map isn't created for the recipient. ```yaml @@ -1653,7 +1653,7 @@ This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -1764,7 +1764,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1788,7 +1788,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1812,7 +1812,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1836,7 +1836,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1860,7 +1860,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1978,7 +1978,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -2103,7 +2103,7 @@ Accept wildcard characters: False The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: -- BinHex (This is the default value) +- BinHex (default value) - UuEncode - AppleSingle - AppleDouble @@ -2207,7 +2207,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -2238,7 +2238,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -2264,7 +2264,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -2290,7 +2290,7 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text -- Mime (This is the default value) +- Mime (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -2369,7 +2369,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -2515,7 +2515,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 30 gigabytes (32212254720 bytes). @@ -2549,7 +2549,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 20 gigabytes (21474836480 bytes). @@ -2890,7 +2890,7 @@ This parameter is available only in the cloud-based service. The ResetPasswordOnNextLogon parameter allows users to require themselves to change their password the next time they log on. Valid values are: - $true: The user is required to change their password then next time they successfully log on. -- $false: The user isn't required to change their password then next time they successfully log on. This is the default value. +- $false: The user isn't required to change their password then next time they successfully log on. This value is the default. You can't use this parameter to require another user to change their password (the parameter is available only via the MyBaseOptions user role). You need to use the ForceChangePasswordNextSignIn value in the PasswordProfile parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. @@ -2912,7 +2912,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -2972,7 +2972,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -3117,7 +3117,7 @@ Accept wildcard characters: False The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are: - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact. -- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. +- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md index b4a48bfc93..0af9d1bc47 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md @@ -13,7 +13,7 @@ title: Set-Mailbox # Set-Mailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-Mailbox cmdlet to modify the settings of existing mailboxes. @@ -1124,7 +1124,7 @@ Set-Mailbox [-Identity] ## DESCRIPTION You can use this cmdlet for one mailbox at a time. To perform bulk management, you can pipeline the output of various Get- cmdlets (for example, the Get-Mailbox or Get-User cmdlets) and configure several mailboxes in a single-line command. You can also use the Set-Mailbox cmdlet in scripts. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -1418,7 +1418,7 @@ This parameter is available only in on-premises Exchange. The AntispamBypassEnabled parameter specifies whether to skip anti-spam processing on the mailbox. Valid values are: - $true: Anti-spam processing is skipped on the mailbox. -- $false: Anti-spam processing occurs on the mailbox. This is the default value +- $false: Anti-spam processing occurs on the mailbox. This value is the default ```yaml Type: Boolean @@ -1597,7 +1597,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The ArchiveQuota value must be greater than or equal to the ArchiveWarningQuota value. @@ -1649,7 +1649,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The ArchiveWarningQuota value must be less than or equal to the ArchiveQuota value. @@ -1698,7 +1698,7 @@ The AuditAdmin parameter specifies the mailbox operations to log for administrat - Create (Enabled by default.) - FolderBind (Enabled by default in on-premises Exchange 2010 or later.) - HardDelete (Enabled by default.) -- MessageBind (This has been deprecated in the cloud-based service.) +- MessageBind (This is deprecated in the cloud-based service.) - ModifyFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - Move (Enabled by default in on-premises Exchange 2010 or later.) - MoveToDeletedItems (Enabled by default.) @@ -1779,7 +1779,7 @@ Accept wildcard characters: False The AuditEnabled parameter specifies whether to enable or disable mailbox audit logging for the mailbox. If auditing is enabled, actions specified in the AuditAdmin, AuditDelegate, and AuditOwner parameters are logged. Valid values are: - $true: Mailbox audit logging is enabled. -- $false: Mailbox audit logging is disabled. This is the default value. +- $false: Mailbox audit logging is disabled. This value is the default. **Note**: In Exchange Online, mailbox auditing on by default was enabled for all organizations in January, 2019. For more information, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes). @@ -1847,7 +1847,7 @@ Accept wildcard characters: False The AuditOwner parameter specifies the mailbox operations to log for mailbox owners as part of mailbox audit logging. Valid values include: -- None (This is the default value in Exchange 2010, Exchange 2013, and Exchange 2016.) +- None (This value is the default in Exchange 2010, Exchange 2013, and Exchange 2016.) - AddFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - ApplyRecord (Available only in the cloud-based service.) - Create @@ -1959,7 +1959,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the RecoverableItemsQuota parameter. @@ -1984,7 +1984,7 @@ Accept wildcard characters: False The CalendarRepairDisabled parameter specifies whether to prevent calendar items in the mailbox from being repaired by the Calendar Repair Assistant. Valid values are: - $true: The Calendar Repair Assistant doesn't repair calendar items in the mailbox. -- $false: The Calendar Repair Assistant repairs calendars items in the mailbox. This is the default value. +- $false: The Calendar Repair Assistant repairs calendars items in the mailbox. This value is the default. ```yaml Type: Boolean @@ -2005,7 +2005,7 @@ Accept wildcard characters: False The CalendarVersionStoreDisabled parameter specifies whether to prevent calendar changes in the mailbox from being logged. Valid values are: - $true: Changes to a calendar item aren't recorded. -- $false: Changes to a calendar item are recorded. This keeps older versions of meetings and appointments. This is the default value. +- $false: Changes to a calendar item are recorded. This keeps older versions of meetings and appointments. This value is the default. ```yaml Type: Boolean @@ -2047,7 +2047,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The ClientExtensions parameter specifies whether the organization-wide client extensions (also called Apps for Outlook) will be installed in the arbitration mailbox (also called the organization mailbox). Only one arbitration mailbox in the organization can be configured to store client extensions. You can use this parameter only on an arbitration mailbox. +The ClientExtensions parameter specifies whether the organization-wide client extensions (also called Apps for Outlook) are installed in the arbitration mailbox (also called the organization mailbox). Only one arbitration mailbox in the organization can be configured to store client extensions. You can use this parameter only on an arbitration mailbox. Valid values are $true or $false. @@ -2092,7 +2092,7 @@ This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: -- $true: A DTMF map is created for the recipient. This is the default value. +- $true: A DTMF map is created for the recipient. This value is the default. - $false: A DTMF map isn't created for the recipient. ```yaml @@ -2441,7 +2441,7 @@ The DefaultAuditSet parameter specifies whether to revert the mailbox operations - Delegate: Reverts the mailbox operations to log for delegate users back to the default list of operations. - Owner: Reverts the mailbox operations to log for mailbox owners back to the default list of operations. -With on-by-default mailbox auditing in the cloud-based service, a set of mailbox operations are logged by default for each logon type. This list of operations is managed by Microsoft, who will automatically add new operations to be audited when they are released. If you change the list of mailbox operations for any logon type (by using the AuditAdmin, AuditDelegate, or AuditOwner parameters), any new mailbox operation released by Microsoft will not be audited; you'll need to explicitly add new mailbox operations to the list of operations for a logon type. Use this parameter to revert the mailbox back to the Microsoft-managed list of mailbox operations that are audited for a logon type. For more information about on-by-default mailbox auditing, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes). +With on-by-default mailbox auditing in the cloud-based service, a set of mailbox operations are logged by default for each logon type. This list of operations is managed by Microsoft, and new mailbox operations are automatically added to auditing as they're released. If you change the list of mailbox operations for any logon type (by using the AuditAdmin, AuditDelegate, or AuditOwner parameters), any new mailbox operation released by Microsoft aren't audited. You need to explicitly add new mailbox operations to the list of operations for a logon type. Use this parameter to revert the mailbox back to the Microsoft-managed list of mailbox operations that are audited for a logon type. For more information about on-by-default mailbox auditing, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes). ```yaml Type: MultiValuedProperty @@ -2513,8 +2513,8 @@ This parameter is available only in on-premises Exchange. The DisableThrottling parameter enables or disables sender rate throttling for the mailbox. Valid values are: -- $true: Messages sent by this mailbox will not be throttled by Sender Rate Control. We only recommend this value for moderation mailboxes. -- $false: Messages will be throttled after the threshold is exceeded. This is the default value. +- $true: Messages sent by this mailbox aren't throttled by Sender Rate Control. We only recommend this value for moderation mailboxes. +- $false: Messages are throttled after the threshold is exceeded. This value is the default. ```yaml Type: Boolean @@ -2575,7 +2575,7 @@ This parameter is available only in on-premises Exchange. The DowngradeHighPriorityMessagesEnabled parameter specifies whether to prevent the mailbox from sending high priority messages to an X.400 mail system. Valid values are: - $true: High priority messages sent to X.400 recipients are changed to normal priority. -- $false: High priority messages set to X.400 recipients remain high priority. This is the default value. +- $false: High priority messages set to X.400 recipients remain high priority. This value is the default. ```yaml Type: Boolean @@ -2641,8 +2641,8 @@ This parameter is available only in the cloud-based service. The ElcProcessingDisabled parameter specifies whether to prevent the Managed Folder Assistant from processing the mailbox. Valid values are: -- $true: The Managed Folder Assistant isn't allowed to process the mailbox. Note that this setting will be ignored if a retention policy that has Preservation Lock enabled is applied to the mailbox. -- $false: The Managed Folder Assistant is allowed to process the mailbox. This is the default value. +- $true: The Managed Folder Assistant isn't allowed to process the mailbox. This setting is ignored if a retention policy that has Preservation Lock enabled is applied to the mailbox. +- $false: The Managed Folder Assistant is allowed to process the mailbox. This value is the default. ```yaml Type: Boolean @@ -2723,7 +2723,7 @@ This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -2771,7 +2771,7 @@ Accept wildcard characters: False The EndDateForRetentionHold parameter specifies the end date for retention hold for messaging records management (MRM). To use this parameter, you need to set the RetentionHoldEnabled parameter to the value $true. -**Important**: Using this parameter does not change the _RetentionHoldEnabled_ value to $false after the specified date. The _RentionHoldEnabled_ will still be $true on the mailbox after the specified date, but MRM will start processing mailbox items as normal. +**Important**: Using this parameter does not change the _RetentionHoldEnabled_ value to $false after the specified date. The _RetentionHoldEnabled_ is still $true on the mailbox after the specified date, but MRM starts processing mailbox items as normal. 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". @@ -2835,7 +2835,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Online. -The ExcludeFromOrgHolds parameter excludes the mailbox from one or more organization-wide Microsoft 365 retention policies. This parameter can only be used for inactive mailboxes. A valid value for this parameter is the GUID of the organization-wide Microsoft 365 retention policy that the inactive mailbox is excluded from. To find the GUID values of organization-wide Microsoft 365 retention policies, run the command Get-OrganizationConfig | Format-List InplaceHolds. Note that retention policies assigned to mailboxes are prefaced by 'mbx'. +The ExcludeFromOrgHolds parameter excludes the mailbox from one or more organization-wide Microsoft 365 retention policies. This parameter can only be used for inactive mailboxes. A valid value for this parameter is the GUID of the organization-wide Microsoft 365 retention policy that the inactive mailbox is excluded from. To find the GUID values of organization-wide Microsoft 365 retention policies, run the command Get-OrganizationConfig | Format-List InplaceHolds. Retention policies assigned to mailboxes are prefaced by 'mbx'. You can specify multiple values by using the syntax: "GUID1","GUID2",..."GUIDX". @@ -2883,7 +2883,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -2907,7 +2907,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -2931,7 +2931,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -2955,7 +2955,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -2979,7 +2979,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -2999,7 +2999,7 @@ Accept wildcard characters: False The ExternalOofOptions parameter specifies the automatic replies or Out of Office (also known OOF) message options that are available for the mailbox. Valid values are: -- External: Automatic replies can be configured for external senders. This is the default value. +- External: Automatic replies can be configured for external senders. This value is the default. - InternalOnly: Automatic replies can be configured only for internal senders. ```yaml @@ -3020,7 +3020,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The FolderHierarchyChildrenCountReceiveQuota parameter specifies the maximum number of subfolders that can be created in a mailbox folder. The mailbox owner won't be able to create a new subfolder when this limit is reached. +The FolderHierarchyChildrenCountReceiveQuota parameter specifies the maximum number of subfolders that can be created in a mailbox folder. The mailbox owner can't create a new subfolder when this limit is reached. To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FolderHierarchyChildrenCountReceiveQuota`. @@ -3064,7 +3064,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The FolderHierarchyDepthReceiveQuota parameter specifies the maximum number of levels in the folder hierarchy of a mailbox folder. The mailbox owner won't be able to create another level in the folder hierarchy of the mailbox folder when this limit is reached. +The FolderHierarchyDepthReceiveQuota parameter specifies the maximum number of levels in the folder hierarchy of a mailbox folder. The mailbox owner can't create another level in the folder hierarchy of the mailbox folder when this limit is reached. To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FolderHierarchyDepthReceiveQuota`. @@ -3108,7 +3108,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The FoldersCountReceiveQuota parameter is used to specify a maximum number of folders within a mailbox, typically a public folder mailbox. If this value is configured and the limit is reached, no new folders will be able to be created. +The FoldersCountReceiveQuota parameter is used to specify a maximum number of folders within a mailbox, typically a public folder mailbox. If this value is configured and the limit is reached, you can't create new folders in the mailbox. To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FoldersCountReceiveQuota`. @@ -3313,7 +3313,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -3363,11 +3363,11 @@ The ImListMigrationCompleted parameter specifies whether a user's Lync or Skype Valid values are: - $true: The user's Lync or Skype for Business contact list is stored in their Exchange 2016 mailbox. This prevents you from migrating the mailbox back to an Exchange 2010 server. -- $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This is the default value. +- $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This value is the default. Lync Server 2013 and Skype for Business Server 2015 support storing the user's contact list in their Exchange 2016 mailbox. This feature is known as the unified contact store (UCS), and it allows applications to show a consistent, up-to-date contact list. However, Exchange 2010 doesn't support the unified contact store. Therefore, before you migrate a user's Exchange 2016 mailbox back to Exchange 2010, you need to move the user's Lync or Skype for Business contact list from the unified contact store back to a Lync 2013 or Skype for Business server. For more information, see [Configuring Microsoft Lync Server 2013 to use the unified contact store](https://learn.microsoft.com/lyncserver/lync-server-2013-configuring-lync-server-to-use-the-unified-contact-store). -If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list has been moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false. +If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list is moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false. ```yaml Type: Boolean @@ -3433,7 +3433,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and won't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user will still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox. +The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and can't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user can still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox. You should use this parameter only during public folder migrations. Don't use this parameter once the initial migration validation is complete. @@ -3503,11 +3503,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. -In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you may be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. +In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you might be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter on the mailbox is set to $true (the default value), the value of the this parameter is ignored, and the mailbox uses the IssueWarningQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. @@ -3681,7 +3681,7 @@ Accept wildcard characters: False The LitigationHoldEnabled parameter specifies whether to place the mailbox on litigation hold. Valid values are: - $true: The mailbox is on litigation hold. -- $false: The mailbox isn't on litigation hold. This is the default value. +- $false: The mailbox isn't on litigation hold. This value is the default. After a mailbox is placed on litigation hold, messages can't be deleted from the mailbox. Deleted items and all versions of changed items are retained in the Recoverable Items folder. Items that are purged from the dumpster are also retained and the items are held indefinitely. If you enable litigation hold, single-item recovery quotas aren't applied. @@ -3937,11 +3937,11 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. -In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. +In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you use this parameter to configure the MaxReceiveSize value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the MaxReceiveSize value for all new mailboxes that you create in the future. @@ -3994,11 +3994,11 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. -In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. +In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you use this parameter to configure the MaxSendSize value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the MaxSendSize value for all new mailboxes that you create in the future. @@ -4027,7 +4027,7 @@ Accept wildcard characters: False The MessageCopyForSendOnBehalfEnabled parameter specifies whether to copy the sender for messages that are sent from a mailbox by users that have the "send on behalf of" permission. Valid values are: - $true: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message is sent to the sender's mailbox. -- $false: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message isn't sent to the sender's mailbox. This is the default value. +- $false: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message isn't sent to the sender's mailbox. This value is the default. You give users permission to send on behalf of a mailbox by using the GrantSendOnBehalfTo parameter on the mailbox. @@ -4052,7 +4052,7 @@ Accept wildcard characters: False The MessageCopyForSentAsEnabled parameter specifies whether to copy the sender for messages that are sent from a mailbox by users that have the "send as" permission. Valid values are: - $true: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message is sent to the sender's mailbox. -- $false: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message isn't sent to the sender's mailbox. This is the default value. +- $false: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message isn't sent to the sender's mailbox. This value is the default. In Exchange Online, you give a user permission to send as a mailbox by running this command: `Add-RecipientPermission -AccessRights SendAs -Trustee `. @@ -4078,7 +4078,7 @@ This parameter is available only in the cloud-based service. The MessageCopyForSMTPClientSubmissionEnabled parameter specifies whether to copy the sender for messages that are sent using SMTP client submission (SMTP AUTH). Valid values are: -- $true: When the user's account sends messages using SMTP AUTH, a copy of the message is sent to the users's mailbox. This is the default value. +- $true: When the user's account sends messages using SMTP AUTH, a copy of the message is sent to the users's mailbox. This value is the default. - $false: When the user's account sends messages using SMTP AUTH, a copy of the message isn't sent to the users's mailbox. ```yaml @@ -4121,7 +4121,7 @@ Accept wildcard characters: False The MessageTrackingReadStatusEnabled parameter specifies whether to include detailed information in delivery reports for messages sent to the mailbox. Valid values are: -- $true: The read status of the message and the date-time that the message was delivered is shown in the delivery report for messages sent to this mailbox. This is the default value. +- $true: The read status of the message and the date-time that the message was delivered is shown in the delivery report for messages sent to this mailbox. This value is the default. - $false: The read status of the message isn't displayed in the delivery report for messages sent to this mailbox. Only the date-time that the message was delivered is shown in the delivery report. ```yaml @@ -4214,7 +4214,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -4493,11 +4493,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value. -In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you may be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. +In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you might be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the ProhibitSendQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. @@ -4527,7 +4527,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. @@ -4691,7 +4691,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. @@ -4727,7 +4727,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsWarningQuota value must be less than or equal to the RecoverableItemsQuota value. @@ -4991,9 +4991,9 @@ This parameter is available only in the cloud-based service. The RemoveOrphanedHolds parameter is used to remove the mailbox (typically, an inactive mailbox) from In-Place Holds that no longer exist, but are still applied to the mailbox. You identify the In-Place Hold by using its GUID value. You can specify multiple GUID values separated by commas. -If you use the GUID value of an In-Place Hold that still exists as a value for this parameter, the command will return an error. If that happens, you'll need to remove the mailbox (or inactive mailbox) from the In-Place Hold. +If you use the GUID value of an In-Place Hold that still exists as a value for this parameter, the command returns an error. If that happens, you need to remove the mailbox (or inactive mailbox) from the In-Place Hold. -In an Exchange hybrid deployment, In-Place Holds that are created in the on-premises organization can be applied to cloud-based mailboxes. In this scenario, it's possible that the hold object hasn't been synced to the cloud-based organization, and using this parameter will remove the specified hold from the cloud-based mailbox even though the hold may still exist. To prevent this from happening, make sure the hold doesn't exist in the on-premises organization before you use this parameter. +In an Exchange hybrid deployment, In-Place Holds that are created in the on-premises organization can be applied to cloud-based mailboxes. In this scenario, it's possible that the hold object hasn't been synced to the cloud-based organization, and using this parameter removes the specified hold from the cloud-based mailbox even though the hold might still exist. To prevent this from happening, make sure the hold doesn't exist in the on-premises organization before you use this parameter. ```yaml Type: String[] @@ -5081,7 +5081,7 @@ This parameter is available only in on-premises Exchange. The ResetPasswordOnNextLogon parameter specifies whether the user is required to change their password the next time they log on to their mailbox. Valid values are: - $true: The user is required to change their password the next time they log on to their mailbox. -- $false: The user isn't required to change their password the next time they log on to their mailbox. This is the default value. +- $false: The user isn't required to change their password the next time they log on to their mailbox. This value is the default. In Exchange Online, administrators can require users to reset their password the next time they log on by using the ResetPasswordOnNextLogon parameter on the Set-User cmdlet. @@ -5184,7 +5184,7 @@ This parameter is available only in on-premises Exchange. The RetainDeletedItemsUntilBackup parameter specifies whether to keep items in the Recoverable Items\\Deletions folder of the mailbox until the next database backup occurs. Valid values are: - $true: Deleted items are kept until the next mailbox database backup. This value could effectively override the DeletedItemRetention and RecoverableItemsQuota parameter values. -- $false: This is the default value. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameter values. +- $false: This value is the default. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameter values. When the UseDatabaseRetentionDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the RetainDeletedItemsUntilBackup parameter value from the mailbox database. To use the RetainDeletedItemsUntilBackup parameter on the mailbox, you need to set the UseDatabaseRetentionDefaults parameter to the value $false. @@ -5233,7 +5233,7 @@ Accept wildcard characters: False The RetentionHoldEnabled parameter specifies whether the mailbox is placed on retention hold. Placing the mailbox on retention hold temporarily suspends the processing of retention policies or managed folder mailbox policies for the mailbox (for example, when the user is on vacation). Valid values are: - $true: The mailbox is placed on retention hold. Retention policies and managed folder policies are suspended for the mailbox, and purging items from the mailbox isn't possible (even using MFCMapi). -- $false: The retention hold is removed from the mailbox. The mailbox is subject to retention policies and managed folder policies. This is the default value. +- $false: The retention hold is removed from the mailbox. The mailbox is subject to retention policies and managed folder policies. This value is the default. To set the start date for retention hold, use the StartDateForRetentionHold parameter. @@ -5368,7 +5368,7 @@ A valid value is a number from 32 to 256 kilobytes (32768 to 262144 bytes). When - B (bytes) - KB (kilobytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. In Exchange Online, Exchange 2019, Exchange 2016, and Exchange 2013, the default value is 256 kilobytes (262,144 bytes). @@ -5394,7 +5394,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -5438,7 +5438,7 @@ The SCLDeleteEnabled parameter specifies whether to silently delete messages tha - $true: Messages that meet or exceed the SCLDeleteThreshold value are silently deleted without sending a non-delivery report (NDR). - $false: Messages that meet or exceed the SCLDeleteThreshold value aren't deleted. -- $null (blank): The value isn't configured. This is the default value. +- $null (blank): The value isn't configured. This value is the default. ```yaml Type: Boolean @@ -5484,7 +5484,7 @@ The SCLJunkEnabled parameter specifies whether messages that exceed(not meet) th - $true: Messages that exceed the SCLJunkThreshold value are moved to the Junk Email folder. Messages that meet the SCLJunkThreshold value aren't moved to the Junk Email folder. - $false: Messages that meet or exceed the SCLJunkThreshold value aren't moved to the Junk Email folder. -- $null (blank): The value isn't configured. This is the default value. +- $null (blank): The value isn't configured. This value is the default. ```yaml Type: Boolean @@ -5530,7 +5530,7 @@ The SCLQuarantineEnabled parameter specifies whether messages that meet or excee - $true: Messages that meet or exceed the SCLQuarantineThreshold value are sent to the quarantine mailbox. - $false: Messages that meet or exceed the SCLQuarantineThreshold value aren't sent to the quarantine mailbox. -- $null (blank): The value isn't configured. This is the default value. +- $null (blank): The value isn't configured. This value is the default. To configure the quarantine mailbox, see [Configure a spam quarantine mailbox](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-quarantine-mailboxes). @@ -5578,7 +5578,7 @@ The SCLRejectEnabled parameter specifies whether messages that meet or exceed th - $true: Messages that meet or exceed the SCLRejectThreshold value are rejected, and an NDR is sent to the sender. - $false: Messages that meet or exceed the SCLRejectThreshold value aren't rejected. -- $null (blank): The value isn't configured. This is the default value. +- $null (blank): The value isn't configured. This value is the default. ```yaml Type: Boolean @@ -5660,7 +5660,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -5732,8 +5732,8 @@ Accept wildcard characters: False The SingleItemRecoveryEnabled parameter specifies whether to prevent the Recoverable Items folder from being purged. Valid values are: -- $true: Single item recovery is enabled. The Recoverable Items folder can't be purged, and deleted or edited items can't be removed. This is the default value in Exchange Online. For more information, see [Enable or disable single item recovery for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-single-item-recovery). -- $false: Single item recovery isn't enabled. The Recoverable Items folder can be purged, and deleted or edited items can be removed. This is the default value in Exchange Server. For more information, see [Enable or disable single item recovery for a mailbox](https://learn.microsoft.com/exchange/recipients/user-mailboxes/single-item-recovery). +- $true: Single item recovery is enabled. The Recoverable Items folder can't be purged, and deleted or edited items can't be removed. This value is the default in Exchange Online. For more information, see [Enable or disable single item recovery for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-single-item-recovery). +- $false: Single item recovery isn't enabled. The Recoverable Items folder can be purged, and deleted or edited items can be removed. This value is the default in Exchange Server. For more information, see [Enable or disable single item recovery for a mailbox](https://learn.microsoft.com/exchange/recipients/user-mailboxes/single-item-recovery). ```yaml Type: Boolean @@ -5958,7 +5958,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The UMGrammar parameter specifies whether the arbitration mailbox (also called an organization mailbox) is used for UM directory speech grammar generation for the organization. UM directory speech grammars will be generated and used on the Mailbox server of this arbitration mailbox. UM directory speech grammars are used in speech-enabled directory search features, such as UM auto attendants. You can use this parameter only on an arbitration mailbox. +The UMGrammar parameter specifies whether the arbitration mailbox (also called an organization mailbox) is used for UM directory speech grammar generation for the organization. UM directory speech grammars are generated and used on the Mailbox server of this arbitration mailbox. UM directory speech grammars are used in speech-enabled directory search features, such as UM auto attendants. You can use this parameter only on an arbitration mailbox. Valid values are $true or $false. @@ -6032,7 +6032,7 @@ This parameter is functional only in on-premises Exchange. The UseDatabaseRetentionDefaults parameter specifies whether the retention settings for items in the Recoverable Items folder in the mailbox are determined by the settings on the mailbox or the corresponding settings on the mailbox database. Valid values are: -- $true: The mailbox uses the applicable retention settings that are configured on the mailbox database. Any corresponding settings that are configured on the mailbox are ignored. This is the default value. +- $true: The mailbox uses the applicable retention settings that are configured on the mailbox database. Any corresponding settings that are configured on the mailbox are ignored. This value is the default. - $false: The mailbox uses its own values for the applicable retention settings. Any corresponding settings that are configured on the mailbox database are ignored. The following retention settings are affected by this parameter: @@ -6040,7 +6040,7 @@ The following retention settings are affected by this parameter: - DeletedItemRetention - RetainDeletedItemsUntilBackup -**Note**: If you set the RetainDeletedItemsUntilBackup parameter on the mailbox database to the value $true when the value of the UseDatabaseRetentionDefaults parameter on a mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet will erroneously appear as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell: +**Note**: If you set the RetainDeletedItemsUntilBackup parameter on the mailbox database to the value $true when the value of the UseDatabaseRetentionDefaults parameter on a mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet erroneously appears as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell: - Run the following command: `Import-Module ActiveDirectory`. - Replace \ with the Alias value of the mailbox, and run the following command: `Get-ADUser -Properties mDBUseDefaults | Format-List mDBUseDefaults`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md index 2ea3be04e4..727665ecc5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md @@ -13,7 +13,7 @@ title: Set-MailboxAuditBypassAssociation # Set-MailboxAuditBypassAssociation ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxAuditBypassAssociation cmdlet to configure mailbox audit logging bypass for user or computer accounts such as service accounts for applications that access mailboxes frequently. @@ -32,9 +32,9 @@ Set-MailboxAuditBypassAssociation [-Identity] ## DESCRIPTION You can disable Automatic Replies for a specified mailbox or 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 @@ -105,7 +105,7 @@ This parameter is functional only in the cloud-based service. The AutoDeclineFutureRequestsWhenOOF parameter specifies whether to automatically decline new meeting requests that are sent to the mailbox during the scheduled time period when Automatic Replies are being sent. Valid values are: - $true: New meeting requests that are received during the scheduled time period are automatically declined. -- $false: Meeting requests received during the scheduled time period aren't automatically declined. This is the default value. +- $false: Meeting requests received during the scheduled time period aren't automatically declined. This value is the default. You can use this parameter only when the AutoReplyState parameter is set to Scheduled. @@ -128,7 +128,7 @@ Accept wildcard characters: False The AutoReplyState parameter specifies whether the mailbox is enabled for Automatic Replies. Valid values are: - Enabled: Automatic Replies are sent for the mailbox. -- Disabled: Automatic Replies aren't sent for the mailbox. This is the default value. +- Disabled: Automatic Replies aren't sent for the mailbox. This value is the default. - Scheduled: Automatic Replies are sent for the mailbox during the time period that's specified by the StartTime and EndTime parameters. The Enabled and Scheduled values require these additional settings: @@ -178,7 +178,7 @@ This parameter is functional only in the cloud-based service. The CreateOOFEvent parameter specifies whether to create a calendar event that corresponds to the scheduled time period when Automatic Replies are being sent for the mailbox. Valid values are: - $true: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, a calendar event is created in the mailbox for those dates. You can specify the subject for the event by using the OOFEventSubject parameter. -- $false: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, no calendar event is created for those dates. This is the default value. +- $false: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, no calendar event is created for those dates. This value is the default. ```yaml Type: Boolean @@ -201,7 +201,7 @@ This parameter is functional only in the cloud-based service. The DeclineAllEventsForScheduledOOF parameter specifies whether to decline all existing calendar events in the mailbox during the scheduled time period when Automatic Replies are being sent. Valid values are: - $true: Existing calendar events in the mailbox that occur during the scheduled time period are declined and removed from the calendar. If the mailbox is the meeting organizer, the events are cancelled for all other attendees. -- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This is the default value. +- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This value is the default. You can use this parameter only when the DeclineEventsForScheduledOOF parameter is set to $true. @@ -231,7 +231,7 @@ The DeclineEventsForScheduledOOF parameter specifies whether it's possible to de To decline specific events during the scheduled time period, use the EventsToDeleteIDs parameter. To decline all events during the scheduled time period, use the DeclineAllEventsForScheduledOOF parameter. -- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This is the default value. +- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This value is the default. You can use this parameter only when the AutoReplyState parameter is set to Scheduled. @@ -346,7 +346,7 @@ The ExternalAudience parameter specifies whether Automatic Replies are sent to e - None: Automatic Replies aren't sent to any external senders. - Known: Automatic Replies are sent only to external senders that are specified in the Contact list of the mailbox. -- All: Automatic Replies are sent to all external senders. This is the default value. +- All: Automatic Replies are sent to all external senders. This value is the default. The value of this parameter is meaningful only when the AutoReplyState parameter is set to Enabled or Scheduled. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md index 72fd48a291..d0f4c94bb5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md @@ -13,7 +13,7 @@ title: Set-MailboxCalendarConfiguration # Set-MailboxCalendarConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxCalendarConfiguration cmdlet to modify mailbox calendar settings for Outlook on the web. This affects how the user's calendar looks and how reminders work in Outlook on the web. This also affects settings that define how meeting invitations, responses, and notifications are sent to the user. @@ -158,7 +158,7 @@ Set-MailboxCalendarConfiguration [-MailboxLocation ] ## DESCRIPTION The Set-MailboxCalendarConfiguration cmdlet primarily allows users to manage their own calendar settings in Outlook on the web Options. However, administrators who are members of the Organization Management or Recipient Management role groups can configure the calendar settings for users by using this cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -381,7 +381,7 @@ Accept wildcard characters: False The ConversationalSchedulingEnabled parameter specifies whether to enable or disable conversational scheduling. Valid values are: -- $true: Conversational scheduling is enabled. This is the default value. +- $true: Conversational scheduling is enabled. This value is the default. - $false: Conversational scheduling is disabled. ```yaml @@ -404,7 +404,7 @@ This parameter is available only in the cloud-based service. The CreateEventsFromEmailAsPrivate parameter specifies whether to create events from email messages as Normal or Private. Valid values are: -- $true: Events from email are created as Private. This is the default value. +- $true: Events from email are created as Private. This value is the default. - $false: Events from email are created as Normal (public). ```yaml @@ -516,7 +516,7 @@ The DefaultOnlineMeetingProvider parameter specifies the default provider for on - RingCentral - SkypeForBusiness - SkypeForConsumer -- TeamsForBusiness (This is the default value.) +- TeamsForBusiness (This value is the default.) - Webex - Zoom @@ -540,12 +540,12 @@ The DefaultReminderTime parameter specifies the length of time before a meeting To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. -Note that the value can't contain seconds. Valid values are: +The value can't contain seconds. Valid values are: - 00:00:00 - 00:05:00 (5 minutes) - 00:10:00 (10 minutes) -- 00:15:00 (15 minutes) This is the default value. +- 00:15:00 (15 minutes) This value is the default. - 00:30:00 (30 minutes) - 01:00:00 (1 hour) - 02:00:00 (2 hours) @@ -601,7 +601,7 @@ This parameter is available only in the cloud-based service. The DiningEventsFromEmailEnabled parameter specifies whether to create dining reservation events from email messages. Valid values are: -- $true: Create dining reservation events from email messages. This is the default value. +- $true: Create dining reservation events from email messages. This value is the default. - $false: Don't create dining reservation events from email messages. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -646,7 +646,7 @@ This parameter is available only in the cloud-based service. The EntertainmentEventsFromEmailEnabled parameter specifies whether to create entertainment reservation events from email messages. Valid values are: -- $true: Create entertainment reservation events from email messages. This is the default value. +- $true: Create entertainment reservation events from email messages. This value is the default. - $false: Don't create entertainment reservation events from email messages. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -671,7 +671,7 @@ This parameter is available only in the cloud-based service. The EventsFromEmailEnabled parameter specifies whether to enable events to be created from email messages. Valid values are: -- $true: Creating events from email messages is enabled. This is the default value. +- $true: Creating events from email messages is enabled. This value is the default. - $false: Creating events from email messages is disabled. When this setting is enabled, you can enable or disable creating specific types of events from email messages by using the following parameters: @@ -701,10 +701,10 @@ Accept wildcard characters: False The FirstWeekOfYear parameter specifies the first week of the year. Valid values are: -- FirstDay: Week numbers start on the first day of the year. This is the default value. +- FirstDay: Week numbers start on the first day of the year. This value is the default. - FirstFourDayWeek: Week numbers start on the first week that has at least four days. - FirstFullWeek: Week numbers start on the first week that has seven days. -- LegacyNotSet: You can't set this value. This is a null value that appears only when the mailbox has been moved from an earlier version of Exchange. +- LegacyNotSet: You can't set this value. This is a null value that appears only when the mailbox is moved from an earlier version of Exchange. You configure the first day of the week by using the WeekStartDay parameter. @@ -728,7 +728,7 @@ This parameter is available only in the cloud-based service. The FlightEventsFromEmailEnabled parameter specifies whether to create flight reservation events from email messages. Valid values are: -- $true: Create flight reservation events from email messages. This is the default value. +- $true: Create flight reservation events from email messages. This value is the default. - $false: Don't create flight reservation events from email messages. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -753,7 +753,7 @@ This parameter is available only in the cloud-based service. The HotelEventsFromEmailEnabled parameter specifies whether to create hotel reservation events from email messages. Valid values are: -- $true: Create hotel reservation events from email messages. This is the default value. +- $true: Create hotel reservation events from email messages. This value is the default. - $false: Don't create hotel reservation events from email messages. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -778,7 +778,7 @@ This parameter is available only in the cloud-based service. The InvoiceEventsFromEmailEnabled parameter specifies whether to allow creating invoices from email messages. Valid values are: -- $true: Creating invoices from messages is enabled. This is the default value. +- $true: Creating invoices from messages is enabled. This value is the default. - $false: Creating invoices from messages is disabled. ```yaml @@ -803,7 +803,7 @@ The LocationDetailsInFreeBusy parameter specifies the level of work location inf - None: No location information is returned. - Building: Only Office or Remote are returned as work location information, if provided. -- Desk: All work location information is returned, including Building and Desk, if provided. This is the default value. +- Desk: All work location information is returned, including Building and Desk, if provided. This value is the default. ```yaml Type: LocationDetailsPermissionInFreeBusy @@ -843,7 +843,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetings as Teams or Skype for Business by default during meeting creation. Currently, this parameter sets the default value, so if the user has already directly interacted with this setting from an Outlook client, this default value will be ignored. Eventually, this parameter will override the Outlook-configured setting. +The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetings as Teams or Skype for Business by default during meeting creation. Currently, this parameter sets the default value, so if the user has already directly interacted with this setting from an Outlook client, this default value is ignored. Eventually, this parameter will override the Outlook-configured setting. Valid values are: @@ -874,7 +874,7 @@ This parameter is available only in the cloud-based service. The PackageDeliveryEventsFromEmailEnabled parameter specifies whether to create package delivery events from email messages. Valid values are: - $true: Create package delivery events from email messages. -- $false: Don't create package delivery events from email messages. This is the default value. +- $false: Don't create package delivery events from email messages. This value is the default. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -916,7 +916,7 @@ Accept wildcard characters: False The RemindersEnabled parameter enables or disables reminders for calendar items. Valid values are: -- $true: Reminders are enabled. This is the default value. +- $true: Reminders are enabled. This value is the default. - $false: Reminders are disabled. When the reminder is first displayed is controlled by the DefaultReminderTime parameter. @@ -939,7 +939,7 @@ Accept wildcard characters: False The ReminderSoundEnabled parameter specifies whether a sound is played along with the reminder. Valid values are: -- $true: A sound is played with the reminder. This is the default value. +- $true: A sound is played with the reminder. This value is the default. - $false: No sound is played with the reminder. This parameter is ignored when the RemindersEnabled parameter is set to $false. @@ -964,7 +964,7 @@ This parameter is available only in the cloud-based service. The RentalCarEventsFromEmailEnabled parameter specifies whether to create rental car reservation events from email messages. Valid values are: -- $true: Create rental car reservation events from email messages. This is the default value. +- $true: Create rental car reservation events from email messages. This value is the default. - $false: Don't create rental car reservation events from email messages. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -1028,7 +1028,7 @@ Accept wildcard characters: False The ShowWeekNumbers parameter specifies whether the week number is displayed in the Outlook on the web calendar. Valid values are: - $true: The week number is displayed. -- $false: The week number isn't displayed. This is the default value. +- $false: The week number isn't displayed. This value is the default. ```yaml Type: Boolean @@ -1067,7 +1067,7 @@ Accept wildcard characters: False The TimeIncrement parameter specifies the scale that the Outlook on the web calendar uses to show time. Valid values are: - FifteenMinutes -- ThirtyMinutes (This is the default value) +- ThirtyMinutes (default value) ```yaml Type: HourIncrement @@ -1088,7 +1088,7 @@ Accept wildcard characters: False The UseBrightCalendarColorThemeInOwa parameter specifies whether to use light colors or bright colors for the calendar in Outlook on the web. Valid values are: - $true: Use bright colors in the calendar. -- $false: Use light colors in the calendar. This is the default value. +- $false: Use light colors in the calendar. This value is the default. ```yaml Type: Boolean @@ -1110,7 +1110,7 @@ This parameter is available only in the cloud-based service. The WeatherEnabled specifies whether weather is displayed in the calendar in Outlook on the web. Valid values are: -- FirstRun (This is the default value) +- FirstRun (default value) - Disabled: Hide weather on the calendar. - Enabled: Show weather on the calendar. @@ -1186,7 +1186,7 @@ This parameter is available only in the cloud-based service. The WeatherUnit parameter specifies the temperature scale that's used to display the weather in the calendar in Outlook on the web. Valid values are: -- Default (This is the default value) +- Default (default value) - Celsius - Fahrenheit @@ -1208,7 +1208,7 @@ Accept wildcard characters: False The WeekStartDay parameter specifies the first day of the week. Valid values are: -- Sunday (This is the default value) +- Sunday (default value) - Monday - Tuesday - Wednesday @@ -1254,7 +1254,7 @@ The WorkDays parameter specifies the work days in the calendar. Valid values are - None - AllDays -- Weekdays (This is the default value) +- Weekdays (default value) - WeekEndDays - Sunday - Monday diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md index d2fe92983d..7ad33e450c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md @@ -13,7 +13,7 @@ title: Set-MailboxCalendarFolder # Set-MailboxCalendarFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxCalendarFolder cmdlet to configure calendar publishing or sharing settings on a mailbox for the visibility of calendar information to external users. To add or modify the permissions so internal users can access the calendar, use the Add-MailboxFolderPermission or Set-MailboxFolderPermission cmdlets. @@ -46,7 +46,7 @@ The Set-MailboxCalendarFolder cmdlet configures calendar publishing information. - Level of detail to publish for the calendar - Whether the published URL of the calendar is enabled for search on the web -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -174,7 +174,7 @@ The PublishDateRangeFrom parameter specifies the start date of calendar informat - ThreeDays - OneWeek - OneMonth -- ThreeMonths (This is the default value) +- ThreeMonths (default value) - SixMonths - OneYear @@ -202,7 +202,7 @@ The PublishDateRangeTo parameter specifies the end date of calendar information - ThreeDays - OneWeek - OneMonth -- ThreeMonths (This is the default value) +- ThreeMonths (default value) - SixMonths - OneYear @@ -227,7 +227,7 @@ Accept wildcard characters: False The PublishEnabled parameter specifies whether to publish the specified calendar information. Valid values are: - $true: The calendar information is published. -- $false: The calendar information is not published. This is the default value. +- $false: The calendar information is not published. This value is the default. ```yaml Type: Boolean @@ -245,7 +245,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The ResetUrl switch replaces the existing non-public URL with a new URL for a calendar that has been published without being publicly searchable. You don't need to specify a value with this switch. +The ResetUrl switch replaces the existing non-public URL with a new URL for a calendar that is published without being publicly searchable. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -266,7 +266,7 @@ Accept wildcard characters: False The SearchableUrlEnabled parameter specifies whether the published calendar URL is discoverable on the web. - $true: The published calendar URL is discoverable on the web. -- $false: The published calendar URL is not discoverable on the web. This is the default value. +- $false: The published calendar URL is not discoverable on the web. This value is the default. This parameter is meaningful only when the PublishEnabled parameter value is $true. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md index 8678125dd0..e700a98c53 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md @@ -63,7 +63,7 @@ Set-MailboxDatabase [-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 @@ -114,7 +114,7 @@ Accept wildcard characters: False The AllowFileRestore parameter specifies whether to allow a database to be restored from a backup. Valid values are: - $true: You can replace an existing database with a newly-created database. You can mount a database that doesn't match the database entry in Active Directory. -- $false: You can't replace an existing database with a newly-created database. You can't mount a database that doesn't match the database entry in Active Directory. This is the default value. +- $false: You can't replace an existing database with a newly-created database. You can't mount a database that doesn't match the database entry in Active Directory. This value is the default. ```yaml Type: Boolean @@ -135,7 +135,7 @@ Accept wildcard characters: False The AutoDagExcludedFromMonitoring parameter specifies whether to exclude the mailbox database from the ServerOneCopyMonitor, which alerts an administrator when a replicated database has only one healthy copy available. Valid values are: - $true: No alert is issued when there's only one healthy copy of the replicated database. -- $false: An alert is issued when there's only one healthy copy of the replicated database. This is the default value. +- $false: An alert is issued when there's only one healthy copy of the replicated database. This value is the default. ```yaml Type: Boolean @@ -173,7 +173,7 @@ Accept wildcard characters: False The BackgroundDatabaseMaintenance parameter specifies whether the Extensible Storage Engine (ESE) performs database maintenance. Valid values are: -- $true: The mailbox database reads the object during database mount and initializes the database to perform background maintenance. This is the default value. +- $true: The mailbox database reads the object during database mount and initializes the database to perform background maintenance. This value is the default. - $false: The mailbox database reads the object during database mount and initializes the database without the option to perform background maintenance. ```yaml @@ -204,7 +204,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the RecoverableItemsQuota parameter. @@ -229,7 +229,7 @@ Accept wildcard characters: False The CircularLoggingEnabled parameter specifies whether circular logging is enabled for the database. Valid values are: - $true: Circular logging is enabled. -- $false: Circular logging is disabled. This is the default value. +- $false: Circular logging is disabled. This value is the default. For more information about circular logging, see [Exchange Native Data Protection](https://learn.microsoft.com/exchange/backup-restore-and-disaster-recovery-exchange-2013-help#exchange-native-data-protection). @@ -296,7 +296,7 @@ The DataMoveReplicationConstraint parameter specifies the throttling behavior fo - CINoReplication (Exchange 2013 or later): Moves shouldn't be throttled to ensure high availability, but the content indexing service must be up to date. - CISecondCopy (Exchange 2013 or later): At least one passive mailbox database copy must have the most recent changes synchronized, and the content indexing service must be up to date. Use this setting to indicate that the database is replicated to one or more mailbox database copies. - CISecondDatacenter (Exchange 2013 or later): At least one passive mailbox database copy in another Active Directory site must have the most recent changes replicated, and the content indexing service must be up to date. Use this setting to indicate that the database is replicated to database copies in multiple Active Directory sites. -- SecondCopy: At least one passive mailbox database copy must have the most recent changes synchronized. This is the default value. Use this setting to indicate that the database is replicated to one or more mailbox database copies. +- SecondCopy: At least one passive mailbox database copy must have the most recent changes synchronized. This value is the default. Use this setting to indicate that the database is replicated to one or more mailbox database copies. - SecondDatacenter: At least one passive mailbox database copy in another Active Directory site must have the most recent changes replicated. Use this setting to indicate that the database is replicated to database copies in multiple Active Directory sites. Any value other than None enables the Microsoft Exchange Mailbox Replication service to coordinate with Active Manager. For more information, see [Active Manager](https://learn.microsoft.com/Exchange/high-availability/database-availability-groups/active-manager). @@ -387,7 +387,7 @@ This parameter is functional only in Exchange 2016 or earlier. The IndexEnabled parameter specifies whether Exchange Search indexes the mailbox database. Valid values are: -- $true: Exchange Search indexes the mailbox database. This is the default value. +- $true: Exchange Search indexes the mailbox database. This value is the default. - $false: Exchange Search doesn't index the mailbox database. ```yaml @@ -427,7 +427,7 @@ Accept wildcard characters: False The IsExcludedFromProvisioning parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are: - $true: The database is excluded from new or move mailbox operations when you don't specify the target mailbox database. -- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This is the default value. +- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This value is the default. The value is automatically set to $true when you set the IsExcludedFromProvisioningDueToLogicalCorruption parameter to $true, and isn't changed back to $false when you set the IsExcludedFromProvisioningDueToLogicalCorruption parameter back to $false. In the case of database corruption, you should set the IsExcludedFromProvisioning parameter back to $false only after you fix the corruption issue or recreate the database. @@ -452,9 +452,9 @@ The IIsExcludedFromProvisioningByOperator parameter specifies whether to exclude Valid values are: - $true: Indicates that you manually excluded the database. The database is excluded from new or move mailbox operations when you don't specify the target mailbox database. -- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This is the default value. +- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This value is the default. -Note that setting this parameter to the value $true has these additional effects on the database: +Setting this parameter to the value $true has these additional effects on the database: - The IsExcludedFromProvisioningReason parameter requires a value if it doesn't already have one. - The unmodifiable IsExcludedFromProvisioningBy property is populated with your user account. @@ -480,9 +480,9 @@ The IsExcludedFromProvisioningDueToLogicalCorruption parameter specifies whether Valid values are: - $true: Indicates that you excluded the database due to database corruption. The database is excluded from new or move mailbox operations when you don't specify the target mailbox database. -- $false: This is the default value. The database can be used in new or move mailbox operations when you don't specify the target mailbox database. You should manually configure this value only after the database corruption is fixed, or after the database is recreated. +- $false: This value is the default. The database can be used in new or move mailbox operations when you don't specify the target mailbox database. You should manually configure this value only after the database corruption is fixed, or after the database is recreated. -Note that setting this parameter to the value $true has these additional effects on the database: +Setting this parameter to the value $true has these additional effects on the database: - The IsExcludedFromProvisioningReason parameter requires a value if it doesn't already have one. - The unmodifiable IsExcludedFromProvisioningBy property is populated with your user account. @@ -538,7 +538,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. @@ -563,9 +563,9 @@ Accept wildcard characters: False The IsSuspendedFromProvisioning parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are: - $true: Indicates that you don't want the exclusion to be permanent. The database is excluded from new or move mailbox operations when you don't specify the target mailbox database. -- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This is the default value. +- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This value is the default. -Note that setting this parameter to the value $true has these additional effects on the database: +Setting this parameter to the value $true has these additional effects on the database: - The IsExcludedFromProvisioningReason parameter requires a value if it doesn't already have one. - The unmodifiable IsExcludedFromProvisioningBy property is populated with your user account. @@ -635,7 +635,7 @@ Accept wildcard characters: False This parameter is functional only in Exchange Server 2010. -The MaintenanceSchedule parameter specifies when maintenance will be performed on the mailbox database. Maintenance includes online defragmentation, removing items that have passed their retention period, removing unused indexes and other cleanup tasks. +The MaintenanceSchedule parameter specifies when maintenance is performed on the mailbox database. Maintenance includes online defragmentation, removing items that have passed their retention period, removing unused indexes and other cleanup tasks. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. @@ -695,7 +695,7 @@ Accept wildcard characters: False The MountAtStartup parameter specifies whether to mount the mailbox database when the Microsoft Exchange Information Store service starts. Valid values are: -- $true: The database is mounted when the service starts. This is the default value. +- $true: The database is mounted when the service starts. This value is the default. - $false: The database isn't mounted when the service starts. ```yaml @@ -766,7 +766,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value. @@ -798,7 +798,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. @@ -896,7 +896,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. @@ -930,7 +930,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsWarningQuota value must be less than or equal to the RecoverableItemsQuota value. @@ -955,13 +955,13 @@ Accept wildcard characters: False The RetainDeletedItemsUntilBackup parameter specifies whether to keep items in the Recoverable Items\\Deletions folder of the mailbox until the next database backup occurs. Valid values are: - $true: Deleted items in mailboxes are kept until the next mailbox database backup. This value could effectively override the deleted DeletedItemRetention and RecoverableItemsQuota parameter values. -- $false: This is the default value. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameters. +- $false: This value is the default. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameters. This settings applies to all mailboxes in the database that don't have their own RetainDeletedItemsUntilBackup value configured. For more information, see [Recoverable Items folder in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder). -**Note**: If you set the value of this parameter to $true when the value of the UseDatabaseRetentionDefaults parameter on a specific mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet will erroneously appear as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell: +**Note**: If you set the value of this parameter to $true when the value of the UseDatabaseRetentionDefaults parameter on a specific mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet erroneously appears as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell: - Run the following command: `Import-Module ActiveDirectory`. - Replace \ with the Alias value of the mailbox, and run the following command: `Get-ADUser -Properties mDBUseDefaults | Format-List mDBUseDefaults`. @@ -986,7 +986,7 @@ This parameter is functional only in Exchange Server 2010. The RpcClientAccessServer parameter specifies the Client Access server or Client Access server array through which RPC clients (for example, Microsoft Office Outlook 2007 clients) access their mailboxes. This feature is supported for all versions of Outlook. -When connecting with Outlook 2003 clients, RPC encryption is disabled by default. Unless RPC encryption is enabled on Outlook 2003 or disabled on the server, Outlook 2003 clients won't be able to connect. For more information, see [Understanding RPC Client Access](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/ee332317(v=exchg.141)). +When connecting with Outlook 2003 clients, RPC encryption is disabled by default. Unless RPC encryption is enabled on Outlook 2003 or disabled on the server, Outlook 2003 clients can't connect. For more information, see [Understanding RPC Client Access](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/ee332317(v=exchg.141)). ```yaml Type: ClientAccessServerOrArrayIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md index f8ef8e0bf2..91532aaab8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md @@ -37,7 +37,7 @@ Set-MailboxDatabaseCopy [-Identity] ## DESCRIPTION With this cmdlet, you can configure the replay lag time, truncation lag time, and activation preference value for a mailbox database copy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -160,7 +160,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service should wait before truncating log files that have replayed into the passive copy of the database. The time period begins after the log has been successfully replayed into the copy of the database. +The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service should wait before truncating log files that have replayed into the passive copy of the database. The time period begins after the log is successfully replayed into the copy of the database. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -224,7 +224,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h The default value is 24:00:00 (24 hours). To disable deferred lagged copy play down, specify the value ([TimeSpan]::Zero). -Note that when the disk is running out of space, the value of this parameter is ignored, and lagged copy play down occurs without delay. +When the disk is running out of space, the value of this parameter is ignored, and lagged copy play down occurs without delay. ```yaml Type: EnhancedTimeSpan diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md index 9800ba7cc0..b81f0286db 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md @@ -15,7 +15,7 @@ title: Set-MailboxExportRequest ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Set-MailboxExportRequest cmdlet to change export request options after the request has been created. You can use the Set-MailboxExportRequest cmdlet to recover from failed export requests. +Use the Set-MailboxExportRequest cmdlet to change export request options after the request is created. You can use the Set-MailboxExportRequest cmdlet to recover from failed export requests. This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). @@ -57,7 +57,7 @@ Set-MailboxExportRequest [-Identity] ## DESCRIPTION You can pipeline the Set-MailboxExportRequest cmdlet from the Get-MailboxExportRequest 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 @@ -175,7 +175,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default value is 30 days. +The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default value is 30 days. ```yaml Type: Unlimited @@ -236,7 +236,7 @@ For more information about maximum message size values, see the following topics - Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) - Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) -Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. +Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request fails if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. @@ -261,7 +261,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md index a49cfbab41..223ac5f5c3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md @@ -13,7 +13,7 @@ title: Set-MailboxFolderPermission # Set-MailboxFolderPermission ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxFolderPermission cmdlet to modify folder-level permissions for users in mailboxes. This cmdlet differs from the Add-MailboxFolderPermission cmdlet in that it modifies existing permission entries. To configure calendar publishing or sharing settings for a mailbox so calendar information is visible to external users, use the Set-MailboxCalendarFolder cmdlet. @@ -32,9 +32,9 @@ Set-MailboxFolderPermission [-Identity] -AccessRights ``` ## DESCRIPTION -In Exchange Online PowerShell, if you don't use the SendNotificationToUser or SharingPermissionFlags parameters, there are no changes to the functionality of the cmdlet. For example, if the user is an existing delegate, and you change their permissions to Editor without using the SendNotificationToUser or SharingPermissionFlags parameters, the user remains a delegate. But, if you use the SendNotificationToUser parameter ($true or $false), the SharingPermissionFlags parameter has the default value None, which can affect delegate access for existing users. For example, you change an existing delegate's permission to Editor, and you use SendNotificationToUser with the value $true. The user will no longer be a delegate and will only have Editor permissions to the folder. +In Exchange Online PowerShell, if you don't use the SendNotificationToUser or SharingPermissionFlags parameters, there are no changes to the functionality of the cmdlet. For example, if the user is an existing delegate, and you change their permissions to Editor without using the SendNotificationToUser or SharingPermissionFlags parameters, the user remains a delegate. But, if you use the SendNotificationToUser parameter ($true or $false), the SharingPermissionFlags parameter has the default value None, which can affect delegate access for existing users. For example, you change an existing delegate's permission to Editor, and you use SendNotificationToUser with the value $true. The user is no longer a delegate and has only Editor permissions to the folder. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -246,10 +246,10 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you modify their calendar permissions. The message will be a normal calendar sharing invitation that can be accepted by the recipient. Valid values are: +The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you modify their calendar permissions. The message is a normal calendar sharing invitation that can be accepted by the recipient. Valid values are: - $true: A sharing invitation is sent. -- $false: No sharing invitation is sent. This is the default value. +- $false: No sharing invitation is sent. This value is the default. This parameter only applies to calendar folders and can only be used with the following AccessRights parameter values: @@ -278,8 +278,8 @@ This parameter is available only in the cloud-based service. The SharingPermissionFlags parameter assigns calendar delegate permissions. This parameter only applies to calendar folders and can only be used when the AccessRights parameter value is Editor. Valid values are: -- None: Removes delegate permissions and updates the meeting message rule so the user stops receiving meeting invites and responses for the mailbox. This is the default value when you use the SendNotificationToUser parameter without specifying a value for the SharingPermissionFlags parameter. -- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value will create the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent. +- None: Removes delegate permissions and updates the meeting message rule so the user stops receiving meeting invites and responses for the mailbox. This value is the default when you use the SendNotificationToUser parameter without specifying a value for the SharingPermissionFlags parameter. +- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value creates the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent. - CanViewPrivateItems: The user can access private items on the calendar. You must use this value with the Delegate value. You can specify multiple values separated by commas. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md index 4d967f1dc5..f4f0e60e87 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md @@ -29,7 +29,7 @@ Set-MailboxIRMAccess -AccessLevel [-Identity] [!NOTE] > This cmdlet works only for delegates who already have Full Access permission to the mailbox. For more information, see [Manage permissions for recipients in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-permissions-for-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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md index 2bcc2e87e1..86bba500cd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md @@ -13,9 +13,9 @@ title: Set-MailboxImportRequest # Set-MailboxImportRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. -Use the Set-MailboxImportRequest cmdlet to change import request options after the request has been created. You can use the Set-MailboxImportRequest cmdlet to recover from failed import requests. +Use the Set-MailboxImportRequest cmdlet to change import request options after the request is created. You can use the Set-MailboxImportRequest cmdlet to recover from failed import requests. This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). @@ -58,7 +58,7 @@ Set-MailboxImportRequest [-Identity] [-RehomeR ## DESCRIPTION You can pipeline the Set-MailboxImportRequest cmdlet from the Get-MailboxImportRequest 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 @@ -148,7 +148,7 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -274,7 +274,7 @@ Valid input for this parameter is an integer or the value unlimited. The default If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -299,7 +299,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md index 5dde63a4e1..7c763e94da 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md @@ -13,7 +13,7 @@ title: Set-MailboxJunkEmailConfiguration # Set-MailboxJunkEmailConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxJunkEmailConfiguration cmdlet to configure the junk email settings on mailboxes. @@ -51,7 +51,7 @@ This cmdlet controls the following junk email settings on the mailbox: For more information, see [Configure Exchange antispam settings on mailboxes](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-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 @@ -160,7 +160,7 @@ Accept wildcard characters: False The ContactsTrusted parameter specifies whether the contacts in the Contacts folder are treated as trusted senders. This parameter corresponds to the Outlook on the web setting: Trust email from my contacts. Valid values are: - $true: Messages from contacts in the Contacts folder that reach the mailbox are never delivered to the Junk Email folder, regardless of the content. -- $false: Messages from contacts in the Contacts folder aren't treated as trusted senders. The email address is a trusted sender only if it's defined in the Safe Senders list. This is the default value. +- $false: Messages from contacts in the Contacts folder aren't treated as trusted senders. The email address is a trusted sender only if it's defined in the Safe Senders list. This value is the default. ```yaml Type: Boolean @@ -200,7 +200,7 @@ Accept wildcard characters: False The Enabled parameter enables or disables the junk email rule on the mailbox (a hidden Inbox rule named Junk E-mail Rule). Valid values are: -- $true: The junk email rule is enabled in the mailbox. This value corresponds to the Outlook on the web setting: Automatically filter junk email. This is the default value. +- $true: The junk email rule is enabled in the mailbox. This value corresponds to the Outlook on the web setting: Automatically filter junk email. This value is the default. In on-premises Exchange, the safelist collection of the mailbox (the Safe Senders list, Safe Recipients list, and Blocked Senders list), and the SCL Junk Email folder threshold (for the organization or the mailbox) delivers messages to the Inbox or the Junk Email folder. @@ -301,7 +301,7 @@ Accept wildcard characters: False The TrustedListsOnly parameter specifies that only messages from senders in the Safe Senders list are delivered to the Inbox. All other messages are treated as junk email. This parameter corresponds to the Outlook on the web setting: Don't trust email unless it comes from someone in my Safe Senders and Recipients list. Valid values are: - $true: Only messages from email address or domain entries in the Safe Senders list and the Safe Recipients list are delivered to the Inbox. All other messages are automatically delivered to the Junk Email folder. -- $false: Messages from other senders, recipients, and domains aren't automatically treated as junk email, and are evaluated individually. This is the default value. +- $false: Messages from other senders, recipients, and domains aren't automatically treated as junk email, and are evaluated individually. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md index eb2d6eb0aa..40134436a3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md @@ -13,7 +13,7 @@ title: Set-MailboxMessageConfiguration # Set-MailboxMessageConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxMessageConfiguration cmdlet to configure the Outlook on the web settings that are applied to specific mailboxes. @@ -94,7 +94,7 @@ Set-MailboxMessageConfiguration [-Identity] ## DESCRIPTION The Set-MailboxMessageConfiguration cmdlet configures Outlook on the web settings for the specified mailbox. These settings include email signature, message format, message options, read receipts, reading pane, and conversations. These settings are not used in Outlook, Exchange ActiveSync, or other email clients. These settings are applied in Outlook on the web only. Some settings also apply to the new Outlook client. Settings that contain the word Mobile are applied in Outlook on the web for devices only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -581,7 +581,7 @@ This parameter is available only in the cloud-based service. The EchoGroupMessageBackToSubscribedSender parameter controls whether subscribed members of Microsoft 365 Groups receive copies of messages that they send to those Groups. Valid values are: - $true: If a subscribed member of a Microsoft 365 Group sends a message to that Group, they'll receive a copy of the message in their Inbox. -- $false: Subscribed members of a Microsoft 365 Group don't receive their own copies of messages that they send to the Group. This is the default value. +- $false: Subscribed members of a Microsoft 365 Group don't receive their own copies of messages that they send to the Group. This value is the default. ```yaml Type: Boolean @@ -603,7 +603,7 @@ This parameter is functional only in on-premises Exchange. The EmailComposeMode parameter specifies how the user creates messages in Outlook on the web. You can use the following values: -- Inline: New messages and replies are created in the preview pane. This is the default value. +- Inline: New messages and replies are created in the preview pane. This value is the default. - SeparateForm: New messages and replies are created in a new browser window. ```yaml @@ -668,7 +668,7 @@ The GlobalReadingPanePosition specifies the default location of the reading pane - Off - Bottom -- Right (This is the default value) +- Right (default value) ```yaml Type: MailReadingPanePosition @@ -752,7 +752,7 @@ Accept wildcard characters: False The IsFavoritesFolderTreeCollapsed parameter specifies whether to collapse the Favorites folder tree by default in Outlook on the web. Valid values are: - $true: The Favorites folder tree is collapsed by default. -- $false: The Favorites folder tree isn't collapsed by default. This is the default value +- $false: The Favorites folder tree isn't collapsed by default. This value is the default ```yaml Type: Boolean @@ -793,7 +793,7 @@ Accept wildcard characters: False The IsMailRootFolderTreeCollapsed parameter specifies whether to collapse the Mail root folder tree by default in Outlook on the web. Valid values are: - $true: The Mail root folder tree is collapsed by default. -- $false: The Mail root folder tree isn't collapsed by default. This is the default value +- $false: The Mail root folder tree isn't collapsed by default. This value is the default ```yaml Type: Boolean @@ -813,7 +813,7 @@ Accept wildcard characters: False The IsReplyAllTheDefaultResponse parameter specifies whether Reply All is the default response for messages in Outlook on the web. Valid values are: -- $true: Reply All is the default response option for messages in the reading pane. This is the default value. +- $true: Reply All is the default response option for messages in the reading pane. This value is the default. - $false: Reply All isn't the default response option for messages in the reading pane. ```yaml @@ -834,7 +834,7 @@ Accept wildcard characters: False The LinkPreviewEnabled parameter specifies whether link preview of URLs in email messages is enabled for the user in Outlook on the web. Valid values are: -- $true: Link preview of URLs in email messages is enabled for the user. This is the default value. +- $true: Link preview of URLs in email messages is enabled for the user. This value is the default. - $false: Link preview of URLs in email messages is disabled for the user. This parameter depends on the value of the LinkPreviewEnabled parameter on the Set-OrganizationConfig cmdlet, which controls the link preview behavior in Outlook on the web for the entire organization. If link preview is disabled for the organization, users can't enable it for themselves. @@ -857,7 +857,7 @@ Accept wildcard characters: False The MailFolderPaneExpanded parameter specifies whether the Mail folder pane is expanded by default in Outlook on the web. Valid values are: -- $true: The Mail folder pane is expanded by default. This is the default value. +- $true: The Mail folder pane is expanded by default. This value is the default. - $false: The Mail folder pane isn't expanded by default. ```yaml @@ -938,7 +938,7 @@ Accept wildcard characters: False The NavigationPaneViewOption parameter specifies the default navigation pane view in Outlook on the web. Valid values are: -- Default: This is the default value +- Default: This value is the default - MailFolders - PeopleFolders - Groups @@ -1010,7 +1010,7 @@ Accept wildcard characters: False The PreferAccessibleContent parameter specifies whether to prefer accessible content in Outlook on the web. Valid values are: - $true: Prefer accessible content. -- $false: Don't prefer accessible content. This is the default value. +- $false: Don't prefer accessible content. This value is the default. ```yaml Type: Boolean @@ -1213,7 +1213,7 @@ Accept wildcard characters: False The ShowPreviewTextInListView parameter specifies whether to show preview text for messages in list view in Outlook on the web. Valid values are: -- $true: Show preview text for messages in list view. This is the default value. +- $true: Show preview text for messages in list view. This value is the default. - $false: Don't show preview text for messages in list view. ```yaml @@ -1235,7 +1235,7 @@ Accept wildcard characters: False The ShowReadingPaneOnFirstLoad parameter specifies whether to show the reading pane when the user opens in Outlook on the web for the first time. Valid values are: - $true: Show the reading pane when the user opens Outlook on the web for the first time. -- $false: Don't show the reading pane when the user opens Outlook on the web for the first time. This is the default value. +- $false: Don't show the reading pane when the user opens Outlook on the web for the first time. This value is the default. ```yaml Type: Boolean @@ -1255,7 +1255,7 @@ Accept wildcard characters: False The ShowSenderOnTopInListView parameter specifies whether to show the message sender on top in list view in Outlook on the web. Valid values are: -- $true: Show the message sender on top in list view. This is the default value. +- $true: Show the message sender on top in list view. This value is the default. - $false: Don't show the message sender on top in list view. ```yaml @@ -1276,7 +1276,7 @@ Accept wildcard characters: False The ShowUpNext parameter specifies whether the next upcoming event should be shown above the mail list view in Outlook on the web. Valid values are: -- $true: Show the next upcoming event above the mail list view. This is the default value. +- $true: Show the next upcoming event above the mail list view. This value is the default. - $false: Don't show the next upcoming event above the mail list view. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md index 0edf3ce269..746b24f47e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md @@ -42,11 +42,11 @@ Set-MailboxPlan [-Identity] ## DESCRIPTION A mailbox plan is a template that automatically configures mailbox properties. Mailbox plans correspond to license types, and are applied when you license the user. The availability of a mailbox plan is determined by your selections when you enroll in the service and the age of your organization. -Modifying the settings in a mailbox plan doesn't affect existing mailboxes that were created using the mailbox plan. The only way to use a mailbox plan to modify the settings on an existing mailbox is to assign a different license to the user, which will apply the corresponding mailbox plan to the mailbox. +Modifying the settings in a mailbox plan doesn't affect existing mailboxes that were created using the mailbox plan. The only way to use a mailbox plan to modify the settings on an existing mailbox is to assign a different license to the user, which applies the corresponding mailbox plan to the mailbox. Each mailbox plan has a corresponding Client Access services (CAS) mailbox plan with the same name and display name value. You can use the Set-CasMailboxPlan cmdlet to enable or disable POP3, IMAP4 or Exchange ActiveSync (EAS) access to new or newly-enabled mailboxes, and you can specify the Outlook on the web (formerly known as Outlook Web App) mailbox policy for the mailboxes. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -158,11 +158,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. -The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. +The maximum value is determined by the mailbox plan. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. ```yaml Type: Unlimited @@ -188,11 +188,11 @@ When you enter a value, qualify the value with one of the following units: - KB (kilobytes) - MB (megabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 150 MB. The default value is 36 MB. -The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. +The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. Use this parameter to change the MaxReceiveSize value for new mailboxes that you create. Use the MaxReceiveSize parameter on the Set-Mailbox cmdlet to configure the value on existing mailboxes. @@ -222,11 +222,11 @@ When you enter a value, qualify the value with one of the following units: - KB (kilobytes) - MB (megabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 150 MB. The default value is 35 MB. -The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. +The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. Use this parameter to change the MaxSendSize value for new mailboxes that you create. Use the MaxSendSize parameter on the Set-Mailbox cmdlet to configure the value on existing mailboxes. @@ -258,11 +258,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value. -The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. +The maximum value is determined by the mailbox plan. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. ```yaml Type: Unlimited @@ -290,7 +290,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. @@ -375,7 +375,7 @@ If you don't set a value for this parameter, existing mailboxes are also updated **Note**: Specifying a value for this parameter has the following potential issues: - If the value of this parameter is not blank ($null), then the specified retention policy must be the default Exchange retention policy that's configured for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. -- If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value. +- If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox is overwritten when changing licenses. You need to manually reset the RetentionPolicy to the original value. - Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates. For more information, see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans). diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md index 3349fad8d4..d9fdf8c9c0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md @@ -13,7 +13,7 @@ title: Set-MailboxRegionalConfiguration # Set-MailboxRegionalConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxRegionalConfiguration cmdlet to modify the regional settings of a mailbox. You can modify the date format, time format, time zone and language of the mailbox. @@ -63,7 +63,7 @@ Set-MailboxRegionalConfiguration [-MailboxLocation ] ## DESCRIPTION As shown in Example 5, you might need to set the DateFormat and TimeFormat parameter values to $null when you change the Language parameter value and you receive an error about invalid DateFormat values. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -180,7 +180,7 @@ Accept wildcard characters: False The DateFormat parameter specifies a valid date format based on the current or specified language for the mailbox. For example, if the language is set to en-US, valid DateFormat parameter values include: -- M/d/yyyy: This is the default value for en-US. +- M/d/yyyy: This value is the default for en-US. - M/d/yy - MM/dd/yy - MM/dd/yyyy @@ -286,7 +286,7 @@ Accept wildcard characters: False The TimeFormat parameter specifies a valid time format based on the current or specified language value for the mailbox. For example, if the language is set to en-us, valid TimeFormat parameter values include: -- h:mm tt: This is the default value for en-US. +- h:mm tt: This value is the default for en-US. - hh:mm tt - H:mm - HH:mm diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md index 31a09c45f0..fc864e68e8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md @@ -13,9 +13,9 @@ title: Set-MailboxRestoreRequest # Set-MailboxRestoreRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. -Use the Set-MailboxRestoreRequest cmdlet to change restore request options after the request has been created. You can use this cmdlet to recover from failed restore requests. +Use the Set-MailboxRestoreRequest cmdlet to change restore request options after the request is created. You can use this cmdlet to recover from failed restore requests. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -61,7 +61,7 @@ Set-MailboxRestoreRequest [-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 @@ -133,7 +133,7 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -261,7 +261,7 @@ Valid input for this parameter is an integer or the value unlimited. The default If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -286,7 +286,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md index 87fa9b177c..0e5035c4d9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md @@ -13,7 +13,7 @@ title: Set-MailboxSearch # Set-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 Set-MailboxSearch cmdlet to modify an existing mailbox search. @@ -65,7 +65,7 @@ If the In-Place eDiscovery search you want to modify is running, stop it before For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and [In-Place Hold and Litigation Hold in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/holds/holds). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -112,7 +112,7 @@ Accept wildcard characters: False The AllPublicFolderSources parameter specifies whether to include all public folders in the organization in the search. Valid values are: - $true: All public folders are included in the search. This value is required when the value of the AllSourceMailboxes parameter is $falseand you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). -- $false: No public folders are included in the search. This is the default value. You can use this value when the value of the AllSourceMailboxes parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). +- $false: No public folders are included in the search. This value is the default. You can use this value when the value of the AllSourceMailboxes parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean @@ -133,7 +133,7 @@ Accept wildcard characters: False The AllSourceMailboxes parameter specifies whether to include all mailboxes in the search. Valid values are: - $true: All mailboxes are included in the search. This value is required when the value of the AllPublicFolderSources parameter is $falseand you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). -- $false: All mailboxes aren't included in the search. This is the default value. You can use this value when the value of the AllPublicFolderSources parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). +- $false: All mailboxes aren't included in the search. This value is the default. You can use this value when the value of the AllPublicFolderSources parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean @@ -274,7 +274,7 @@ Accept wildcard characters: False The ExcludeDuplicateMessages parameter eliminates duplication of messages across mailboxes in an In-Place eDiscovery search. Valid values are: -- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This is the default value. +- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This value is the default. - $false: Copy all instances of a message if the same message exists in multiple folders or mailboxes. ```yaml @@ -334,7 +334,7 @@ Accept wildcard characters: False The IncludeUnsearchableItems parameter specifies whether items that couldn't be indexed by Exchange Search should be included in the results. Valid values are: - $true: Unsearchable items are included in the results. -- $false: Unsearchable items aren't included in the results. This is the default value. +- $false: Unsearchable items aren't included in the results. This value is the default. Unsearchable items aren't placed on hold for a query-based In-Place Hold. If you need to place unsearchable items on hold, you need to create an indefinite hold (a hold without specifying any search parameters, which provides functionality similar to Litigation Hold. @@ -357,11 +357,11 @@ Accept wildcard characters: False The InPlaceHoldEnabled parameter specifies whether to set an In-Place Hold on items in the search results. Valid values are: - $true: In-Place Hold is enabled on the search results. -- $false: In-Place Hold isn't enabled on the search results. This is the default value. +- $false: In-Place Hold isn't enabled on the search results. This value is the default. You can't set an In-Place Hold on the search results when the AllSourceMailboxes parameter is $true. -If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command may succeed but the mailboxes are not placed on In-Place Hold. +If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command might succeed but the mailboxes are not placed on In-Place Hold. ```yaml Type: Boolean @@ -382,7 +382,7 @@ Accept wildcard characters: False The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold onthe mailbox items (all items or the mailbox items that are returned in the search query results). You use this parameter with the InPlaceHoldEnabled parameter to set an In-Place Hold. The duration is calculated from the time the item is received or created in the mailbox. Valid values are: - An integer. -- The value unlimited. This is the default value. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false. +- The value unlimited. This value is the default. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false. ```yaml Type: Unlimited @@ -422,7 +422,7 @@ Accept wildcard characters: False The LogLevel parameter specifies a logging level for the mailbox search. Valid values are: -- Basic: Basic details of the search are kept. This is the default value. +- Basic: Basic details of the search are kept. This value is the default. - Full: In addition to details in the Basic logging level, a full list of all messages returned is included. - Suppress: Logging is suppressed. No logs are kept. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md index 144b54ea09..7a2d21ab4e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md @@ -34,7 +34,7 @@ Set-MailboxSentItemsConfiguration [-Confirm] ## 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 @@ -121,7 +121,7 @@ Accept wildcard characters: False The SendAsItemsCopiedTo parameter specifies where messages that are sent from the mailbox using Send As permission are saved. Valid values are: -- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This is the default value. +- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This value is the default. - SenderAndFrom: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message, and in the Sent Items folder of the mailbox. ```yaml @@ -142,7 +142,7 @@ Accept wildcard characters: False The SendOnBehalfOfItemsCopiedTo parameter specifies where messages that are sent from the mailbox using Send On Behalf Of permission are saved. Valid values are: -- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This is the default value. +- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This value is the default. - SenderAndFrom: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message, and in the Sent Items folder of the mailbox. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md index bed67ec315..7748bd0a40 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md @@ -131,7 +131,7 @@ Set-MailboxServer [-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 @@ -140,7 +140,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Set-MailboxServer -Identity MBX02 -CalendarRepairWorkCycle 7.00:00:00 -CalendarRepairWorkCycleCheckpoint 7.00:00:00 ``` -In Exchange 2013, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2013, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 2 ```powershell @@ -154,42 +154,42 @@ This example changes some of the default settings of the Calendar Repair Assista Set-MailboxServer -Identity MBX02 -CalendarRepairWorkCycle 7.00:00:00 -CalendarRepairWorkCycleCheckpoint 7.00:00:00 ``` -In Exchange 2010, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2010, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 4 ```powershell Set-MailboxServer -Identity MBX02 -ManagedFolderWorkCycle 10.00:00:00 -ManagedFolderWorkCycleCheckpoint 10.00:00:00 ``` -In Exchange 2013, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2013, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 5 ```powershell Set-MailboxServer -Identity MBX02 -ManagedFolderWorkCycle 10.00:00:00 -ManagedFolderWorkCycleCheckpoint 10.00:00:00 ``` -In Exchange 2010, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2010, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 6 ```powershell Set-MailboxServer -Identity MBX02 -SharingPolicyWorkCycle 7.00:00:00 -SharingPolicyWorkCycleCheckpoint 7.00:00:00 -SharingSyncWorkCycle 7.00:00:00 -SharingSyncWorkCycleCheckpoint 7.00:00:00 ``` -In Exchange 2013, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2013, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 7 ```powershell Set-MailboxServer -Identity MBX02 -SharingPolicyWorkCycle 7.00:00:00 -SharingPolicyWorkCycleCheckpoint 7.00:00:00 -SharingSyncWorkCycle 7.00:00:00 -SharingSyncWorkCycleCheckpoint 7.00:00:00 ``` -In Exchange 2010, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2010, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 8 ```powershell Set-MailboxServer -Identity MBX02 -TopNWorkCycle 10.00:00:00 -TopNWorkCycleCheckpoint 10.00:00:00 -UMReportingWorkCycle 10.00:00:00 -UMReportingWorkCycleCheckpoint 10.00:00:00 ``` -In Exchange 2010, this example throttles the TopN Words Assistant and the Unified Messaging Reporting Assistant for mailboxes that reside on the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes that have Unified Messaging enabled will be scanned, and at the end of the period, the process will start over. +In Exchange 2010, this example throttles the TopN Words Assistant and the Unified Messaging Reporting Assistant for mailboxes that reside on the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes that have Unified Messaging enabled are scanned, and at the end of the period, the process starts over. ## PARAMETERS @@ -243,7 +243,7 @@ The AutoDatabaseMountDial parameter specifies the automatic database mount behav - GoodAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to six. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than six, the database doesn't automatically mount. When the copy queue length is less than or equal to six, Exchange attempts to replicate the remaining logs to the passive copy and mounts the database. - Lossless: The database doesn't automatically mount until all logs that were generated on the active copy have been copied to the passive copy. This setting also causes Active Manager's best copy selection algorithm to sort potential candidates for activation based on the database copy's activation preference value and not its copy queue length. -The default value is GoodAvailability. If you specify either BestAvailability or GoodAvailability, and all of the logs from the active copy haven't been replicated to the passive copy, you may lose some mailbox data. However, the Safety Net feature, (which is enabled by default) helps protect against data loss by resubmitting messages that are in Safety Net. +The default value is GoodAvailability. If you specify either BestAvailability or GoodAvailability, and all of the logs from the active copy haven't been replicated to the passive copy, you might lose some mailbox data. However, the Safety Net feature, (which is enabled by default) helps protect against data loss by resubmitting messages that are in Safety Net. ```yaml Type: AutoDatabaseMountDial @@ -297,7 +297,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. If you enter the value unlimited, no size limit is imposed on the calendar repair log directory. @@ -402,7 +402,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The CalendarRepairMissingItemFixDisabled parameter specifies whether the Calendar Repair Assistant won't fix missing calendar items in mailboxes on the Mailbox server.Valid input for this parameter is $true or $false. The default value is $false. +The CalendarRepairMissingItemFixDisabled parameter specifies whether the Calendar Repair Assistant fixes missing calendar items in mailboxes on the Mailbox server.Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean @@ -481,13 +481,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The CalendarRepairWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be scanned by the Calendar Repair Assistant. The default value is 1 day. +The CalendarRepairWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are scanned by the Calendar Repair Assistant. The default value is 1 day. -Calendars that have inconsistencies will be flagged and repaired according to the interval specified by the CalendarRepairWorkCycleCheckpoint parameter. +Calendars that have inconsistencies are flagged and repaired according to the interval specified by the CalendarRepairWorkCycleCheckpoint parameter. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -507,11 +507,11 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The CalendarRepairWorkCycleCheckpoint parameter specifies the time span at which all mailboxes on the Mailbox server will be identified as needing work completed on them. The default value is 1 day. +The CalendarRepairWorkCycleCheckpoint parameter specifies the time span at which all mailboxes on the Mailbox server are identified as needing work completed on them. The default value is 1 day. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -590,11 +590,11 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The DatabaseCopyActivationDisabledAndMoveNow parameter specifies whether to prevent databases from being mounted on this Mailbox server if there are other healthy copies of the databases on other Mailbox servers. It will also immediately move any mounted databases on the server to other servers if copies exist and are healthy. +The DatabaseCopyActivationDisabledAndMoveNow parameter specifies whether to prevent databases from being mounted on this Mailbox server if there are other healthy copies of the databases on other Mailbox servers. It also immediately moves any mounted databases on the server to other servers if copies exist and are healthy. Valid input for this parameter is $true or $false. The default value is $false. -Setting this parameter to $true won't cause databases to move to a server that has the DatabaseCopyAutoActivationPolicy parameter set to Blocked. +Setting this parameter to $true doesn't cause databases to move to a server that has the DatabaseCopyAutoActivationPolicy parameter set to Blocked. ```yaml Type: Boolean @@ -614,9 +614,9 @@ Accept wildcard characters: False The DatabaseCopyAutoActivationPolicy parameter specifies the type of automatic activation available for mailbox database copies on the specified Mailbox server. Valid values for this parameter are: -- Blocked: Databases can't be automatically activated on the specified Mailbox server. In Exchange 2013 prior to Cumulative Update 7 (CU7), this setting stops server locator requests to the specified server, which prevents all client access to manually activated databases on the server if all DAG members are configured with a value of Blocked. In Exchange 2013 CU7 or later versions of Exchange, server locator requests are sent to a blocked server if no other Mailbox servers are available, thus client access is not impacted. +- Blocked: Databases can't be automatically activated on the specified Mailbox server. In Exchange 2013 prior to Cumulative Update 7 (CU7), this setting stops server locator requests to the specified server, which prevents all client access to manually activated databases on the server if all DAG members are configured with a value of Blocked. In Exchange 2013 CU7 or later versions of Exchange, server locator requests are sent to a blocked server if no other Mailbox servers are available, thus client access isn't affected. - IntrasiteOnly: The database copy is allowed to be activated only on Mailbox servers in the same Active Directory site. This prevents cross-site failover and activation. -- Unrestricted: There are no special restrictions on activating mailbox database copies on the specified Mailbox server. This is the default value. +- Unrestricted: There are no special restrictions on activating mailbox database copies on the specified Mailbox server. This value is the default. ```yaml Type: DatabaseCopyAutoActivationPolicyType @@ -1009,9 +1009,9 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010. -The IrmLogPath parameter specifies the default IRM log directory location. The default value is C:\\Program Files\\Microsoft\\Exchange Server\\ v14\\Logging\\IRMLogs. +The IrmLogPath parameter specifies the default IRM log directory location. The default value is %ExchangeInstallPath%Logging\\IRMLogs. -If you set the value of the IrmLogPath parameter to $null, you effectively disable IRM logging. However, if you set the value of the IrmLogPath parameter to $null when the value of the IrmLogEnabled parameter is $true, Exchange will log errors in the Application event log. The preferred way for disabling IRM logging is to set the IrmLogEnabled parameter to $false. +If you set the value of this parameter to $null, you effectively disable IRM logging. However, if the value of the IrmLogEnabled parameter is $true, Exchange adds errors to the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false. ```yaml Type: LocalLongFullPath @@ -1029,9 +1029,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The IsExcludedFromProvisioning parameter specifies that the Mailbox server isn't considered by the OAB provisioning load balancer. Valid input for this parameter is $true or $false. The default value is $false. +The IsExcludedFromProvisioning parameter specifies that the Mailbox server isn't considered by the OAB provisioning load balancer. Valid values are: -If you specify$true, the server won't be used for provisioning a new OAB or for moving existing OABs. +- $true: The server isn't used for provisioning new OABs or for moving existing OABs. +- $false: The server can be used for provisioning new OABs or for moving existing OABs. This value is the default. ```yaml Type: Boolean @@ -1131,7 +1132,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The default value is unlimited, which means no size limit is imposed on the managed folder log directory. @@ -1187,7 +1188,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. If you enter the value unlimited, no size limit is imposed on a managed folder log file. @@ -1334,13 +1335,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The ManagedFolderWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be processed by the Managed Folder Assistant. The default value is 1 day. +The ManagedFolderWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are processed by the Managed Folder Assistant. The default value is 1 day. The Managed Folder Assistant applies retention policies according to the ManagedFolderWorkCycleCheckpoint interval. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Managed Folder Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Managed Folder Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -1360,9 +1361,9 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The ManagedFolderWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day. +The ManagedFolderWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 1 day. -Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle. +Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. @@ -1404,7 +1405,7 @@ Accept wildcard characters: False The MaximumActiveDatabases parameter specifies the maximum number of databases that can be mounted on the Mailbox server. -When the maximum number is reached, the database copies on the server won't be activated if a failover or switchover occurs. If the copies are already active on a server, the Information Store on the server won't allow databases to be mounted. +When the maximum number is reached, the database copies on the server isn't activated if a failover or switchover occurs. If the copies are already active on a server, the Information Store on the server doesn't allow databases to be mounted. The default value is blank ($null), which means no maximum value is configured. @@ -1681,7 +1682,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2013. -The OABGeneratorWorkCycle parameter specifies the time span in which the OAB generation on the Mailbox server will be processed. The default value is 8 hours. +The OABGeneratorWorkCycle parameter specifies the time span in which the OAB generation on the Mailbox server are processed. The default value is 8 hours. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. @@ -2034,13 +2035,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The SharingPolicyWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be scanned by the Sharing Policy Assistant. The default value is 1 day. +The SharingPolicyWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are scanned by the Sharing Policy Assistant. The default value is 1 day. The Sharing Policy Assistant scans all mailboxes and enables or disables sharing policies according to the interval specified by the SharingPolicyWorkCycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -2060,13 +2061,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The SharingPolicyWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day. +The SharingPolicyWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 1 day. -Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle. +Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -2086,13 +2087,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The SharingSyncWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be synced to the cloud-based service by the Sharing Sync Assistant. The default value is 3 hours. +The SharingSyncWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are synced to the cloud-based service by the Sharing Sync Assistant. The default value is 3 hours. -Mailboxes that require syncing will be synced according to the interval specified by the SharingSyncWorkCycleCheckpoint parameter. +Mailboxes that require syncing are synced according to the interval specified by the SharingSyncWorkCycleCheckpoint parameter. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant will then process all mailboxes on this server every 8 hours. +For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant then processes all mailboxes on this server every 8 hours. ```yaml Type: EnhancedTimeSpan @@ -2112,13 +2113,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The SharingSyncWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 3 hours. +The SharingSyncWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 3 hours. -Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle. +Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. -For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant will then process all mailboxes on this server every 8 hours. +For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant then processes all mailboxes on this server every 8 hours. ```yaml Type: EnhancedTimeSpan @@ -2138,7 +2139,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2013. -The SiteMailboxWorkCycle parameter specifies the time span in which the site mailbox information on the Mailbox server will be processed. The default value is 6 hours. +The SiteMailboxWorkCycle parameter specifies the time span in which the site mailbox information on the Mailbox server are processed. The default value is 6 hours. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. @@ -2426,13 +2427,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The TopNWorkCycle parameter specifies the time span in which all mailboxes that have Unified Messaging on the Mailbox server will be scanned by the TopN Words Assistant. The default value is 7 days. +The TopNWorkCycle parameter specifies the time span in which all mailboxes that have Unified Messaging on the Mailbox server are scanned by the TopN Words Assistant. The default value is 7 days. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. The TopN Words Assistant scans voice mail for the most frequently used words to aid in transcription. The most common words are then indexed according to the interval specified by the TopNWorkCycleCheckpoint parameter. -For example, to specify 10 days for this parameter, use 10.00:00:00. The TopN Words Assistant will then process all mailboxes on which Unified Messaging is enabled on this server every 10 days. +For example, to specify 10 days for this parameter, use 10.00:00:00. The TopN Words Assistant then processes all mailboxes on which Unified Messaging is enabled on this server every 10 days. ```yaml Type: EnhancedTimeSpan @@ -2452,13 +2453,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The TopNWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day. +The TopNWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 1 day. -Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle. +Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The TopN Words Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The TopN Words Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -2478,15 +2479,15 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The UMReportingWorkCycle parameter specifies the time span in which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server will be scanned by the Unified Messaging Reporting Assistant. The default value is 1 day. +The UMReportingWorkCycle parameter specifies the time span in which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server are scanned by the Unified Messaging Reporting Assistant. The default value is 1 day. The Unified Messaging Reporting Assistant updates the Call Statistics reports by reading Unified Messaging call data records for an organization on a regular basis. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Unified Messaging Reporting Assistant will then process all mailboxes that have Unified Messaging enabled on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Unified Messaging Reporting Assistant then processes all mailboxes that have Unified Messaging enabled on this server every 2 days. -Changing the default work cycle for this assistant might impact the performance of the Mailbox server. +Changing the default work cycle for this assistant might affect the performance of the Mailbox server. ```yaml Type: EnhancedTimeSpan @@ -2506,7 +2507,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The UMReportingWorkCycleCheckpoint parameter specifies the time span at which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server will be marked by processing. The default value is 1 day. +The UMReportingWorkCycleCheckpoint parameter specifies the time span at which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server are marked by processing. The default value is 1 day. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md index 5dc0433512..ad74531f90 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md @@ -13,7 +13,7 @@ title: Set-MailboxSpellingConfiguration # Set-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 Set-MailboxSpellingConfiguration cmdlet to modify Outlook on the web spelling checker options for a specified user. For example, you can set the dictionary language and configure the spelling checker to ignore mixed digits or words in all uppercase. @@ -34,7 +34,7 @@ Set-MailboxSpellingConfiguration [-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/Set-MailboxTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md index 1cd0ab0e6a..98eb1644f0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md @@ -72,7 +72,7 @@ Set-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 a remote procedure call (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 messages to 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 @@ -178,7 +178,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log directory. @@ -208,7 +208,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log files. @@ -336,7 +336,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxDeliveryAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log directory. @@ -366,7 +366,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxDeliveryAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log files. @@ -424,7 +424,7 @@ Accept wildcard characters: False The MailboxDeliveryConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Valid values are: -- None: Protocol logging is disabled for the mailbox delivery Receive connector. This is the default value. +- None: Protocol logging is disabled for the mailbox delivery Receive connector. This value is the default. - Verbose: Protocol logging is enabled for the mailbox delivery Receive connector. The location of the log files is controlled by the ReceiveProtocolLogPath parameter. ```yaml @@ -445,7 +445,7 @@ Accept wildcard characters: False The MailboxDeliveryConnectorSmtpUtf8Enabled parameters or disables email address internationalization (EAI) support for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Valid values are: -- $true: Mail can be delivered to local mailboxes that have international characters in email addresses. This is the default value +- $true: Mail can be delivered to local mailboxes that have international characters in email addresses. This value is the default - $false: Mail can't be delivered to local mailboxes that have international characters in email addresses. ```yaml @@ -514,7 +514,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxDeliveryThrottlingLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryThrottlingLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the mailbox delivery throttling log directory. @@ -544,7 +544,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxDeliveryThrottlingLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryThrottlingLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the mailbox delivery throttling log files. @@ -632,7 +632,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxSubmissionAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxSubmissionAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log directory. @@ -662,7 +662,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxSubmissionAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxSubmissionAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log files. @@ -780,7 +780,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you may have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null. +The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you might have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null. ```yaml Type: SmtpAddress @@ -836,7 +836,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be greater than or equal to the value of the ReceiveProtocolLogMaxFileSize parameter. @@ -870,7 +870,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the ReceiveProtocolLogMaxDirectorySize parameter. @@ -944,7 +944,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the routing table log directory. @@ -1018,7 +1018,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter. @@ -1052,7 +1052,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value this parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md index 9dc6e6811f..d697405ee3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md @@ -13,7 +13,7 @@ title: Set-MalwareFilterPolicy # Set-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 Set-MalwareFilterPolicy cmdlet to modify malware filter policies in your organization. @@ -55,7 +55,7 @@ Set-MalwareFilterPolicy [-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 @@ -132,7 +132,7 @@ This parameter is available only in on-premises Exchange. The Action parameter specifies the action to take when malware is detected in a message. Valid values are: -- DeleteMessage: Handles the message without notifying the recipients. This is the default value. +- DeleteMessage: Handles the message without notifying the recipients. This value is the default. - DeleteAttachmentAndUseDefaultAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the default alert text. - DeleteAttachmentAndUseCustomAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the custom alert text specified by the CustomAlertText parameter. @@ -175,7 +175,7 @@ This parameter is available only in on-premises Exchange. The BypassInboundMessages parameter enables or disables malware filtering on incoming messages (messages entering the organization). Valid values are: - $true: Malware filtering is disabled on inbound messages. -- $false: Malware filtering is enabled on inbound messages. This is the default value. +- $false: Malware filtering is enabled on inbound messages. This value is the default. ```yaml Type: Boolean @@ -198,7 +198,7 @@ This parameter is available only in on-premises Exchange. The BypassOutboundMessages parameter enables or disables malware filtering on outgoing messages (messages leaving the organization). Valid values are: - $true: Malware filtering is disabled on outbound messages. -- $false: Malware filtering is enabled on outbound messages. This is the default value. +- $false: Malware filtering is enabled on outbound messages. This value is the default. ```yaml Type: Boolean @@ -452,7 +452,7 @@ Accept wildcard characters: False The EnableExternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from external senders, a notification messages is sent to the email address that's specified by the ExternalSenderAdminAddress parameter. -- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This is the default value. +- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This value is the default. **Note**: Admin notifications are sent only for _attachments_ that are classified as malware. @@ -477,7 +477,7 @@ This parameter is available only in on-premises Exchange. The EnableExternalSenderNotifications parameter enables or disables sending notification messages to external senders for malware detections in their messages. Valid values are: - $true: When malware is detected in a message from an external sender, send them a notification message. -- $false: Don't send malware detection notification messages to external message senders. This is the default value. +- $false: Don't send malware detection notification messages to external message senders. This value is the default. ```yaml Type: Boolean @@ -499,7 +499,7 @@ This parameter is available only in the cloud-based service. The EnableFileFilter parameter enables or disables the common attachments filter (also known as common attachment blocking). Valid values are: -- $true: The common attachments filter is enabled. This is the default value. +- $true: The common attachments filter is enabled. This value is the default. - $false: The common attachments filter is disabled. You specify the file types using the FileTypes parameter. @@ -525,7 +525,7 @@ Accept wildcard characters: False The EnableInternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from internal senders, a notification messages is sent to the email address that's specified by the InternalSenderAdminAddress parameter. -- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This is the default value. +- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This value is the default. **Note**: Admin notifications are sent only for _attachments_ that are classified as malware. @@ -550,7 +550,7 @@ This parameter is available only in on-premises Exchange. The EnableInternalSenderNotifications parameter enables or disables sending notification messages to internal senders for malware detections in their messages. Valid values are: - $true: When malware is detected in a message from an internal sender, send them a notification message. -- $false: Don't send malware detection notification messages to internal message senders. This is the default value. +- $false: Don't send malware detection notification messages to internal message senders. This value is the default. ```yaml Type: Boolean @@ -593,7 +593,7 @@ This parameter is available only in the cloud-based service. The FileTypeAction parameter specifies what happens to messages that contain one or more attachments where the file extension is included in the FileTypes parameter (the common attachments filter). Valid values are: - Quarantine: Quarantine the message. Whether or not the recipient is notified depends on the quarantine notification settings in the quarantine policy that's selected for the malware filter policy by the QuarantineTag parameter. -- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This is the default value. +- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This value is the default. This parameter is meaningful only when the value of the EnableFileFilter parameter is $true. @@ -753,7 +753,7 @@ This parameter is available only in the cloud-based service. The ZapEnabled parameter enables or disables zero-hour auto purge (ZAP) for malware in cloud mailboxes. ZAP detects malware in unread messages that have already been delivered to the user's Inbox. Valid values are: -- $true: ZAP for malware is enabled. This is the default value. In Exchange Server, unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. In the cloud-based service, the messages are quarantined. +- $true: ZAP for malware is enabled. This value is the default. In Exchange Server, unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. In the cloud-based service, the messages are quarantined. - $false: ZAP for malware is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md index 92dce6658f..c9a8199c78 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md @@ -13,7 +13,7 @@ title: Set-MalwareFilterRule # Set-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 Set-MalwareFilterRule cmdlet to modify malware filter rules in your organization. @@ -43,7 +43,7 @@ Set-MalwareFilterRule [-Identity] > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Anti-malware policies](https://learn.microsoft.com/defender-office-365/anti-malware-protection-about#anti-malware-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md index dc4dd0fd54..3f204ae47a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md @@ -41,7 +41,7 @@ Set-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 @@ -125,7 +125,7 @@ Accept wildcard characters: False The DeferAttempts parameter specifies the maximum number of times to defer a message that can't be scanned by the Malware agent. Valid input for this parameter is an integer between 1 and 5. The default value is 3. -After the maximum number of deferrals is reached, the action taken by the Malware agent depends on the error. For scan timeouts and engine errors, the action is to fail the message and return a non-delivery report (NDR) to the sender immediately after the last defer attempt. For all other errors, the message is retried for up to 48 hours, with each retry attempt taking place one hour longer than the last one. For example, starting after the last defer attempt, the first retry attempt will occur in 1 hour, the next retry attempt will occur 2 hours after that, the next retry attempt will occur 3 hours after the second retry attempt, and so on for up to 48 hours. After 48 hours have elapsed, the action is to fail the message and return a non-delivery report (NDR) to the sender. +After the maximum number of deferrals is reached, the action taken by the Malware agent depends on the error. For scan timeouts and engine errors, the action is to fail the message and return a non-delivery report (NDR) to the sender immediately after the last defer attempt. For all other errors, the message is retried for up to 48 hours, with each retry attempt taking place one hour longer than the last one. For example, starting after the last defer attempt, the first retry attempt occurs in 1 hour, the next retry attempt occurs 2 hours after that, the next retry attempt occurs 3 hours after the second retry attempt, and so on for up to 48 hours. After 48 hours have elapsed, the action is to fail the message and return a non-delivery report (NDR) to the sender. ```yaml Type: Int32 @@ -188,7 +188,7 @@ Accept wildcard characters: False The ForceRescan parameter specifies that messages should be scanned by the malware agent, even if the message was already scanned by cloud-based protection. Valid values are: - $true: Messages from cloud-based organizations are scanned by the malware agent. -- $false: Messages from cloud-based organizations aren't scanned by the malware agent. This is the default value. +- $false: Messages from cloud-based organizations aren't scanned by the malware agent. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md index ddf16e2394..575e6d948f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md @@ -44,7 +44,7 @@ Managed content settings are settings that you apply to managed folders to contr Although the New-ManagedContentSettings cmdlet has the MessageClass parameter, the Set-ManagedContentSettings cmdlet doesn't. If you want to change the message type to which content settings apply, you must delete and then re-create the content settings. For more information about the MessageClass parameter, see [New-ManagedContentSettings](https://learn.microsoft.com/powershell/module/exchangepowershell/new-managedcontentsettings). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter 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/Set-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md index a5a7ff9c53..a184b0b51e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md @@ -42,7 +42,7 @@ The Set-ManagedFolder cmdlet modifies the specified parameters of a managed fold The Set-ManagedFolder cmdlet accepts a managed custom folder 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 @@ -242,7 +242,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items may be added. Mailbox sizes can be specified in kilobytes (KB) or megabytes (MB), for example, as 100KB or 5MB. The StorageQuota parameter is valid for managed custom folders in Outlook 2007. +The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items might be added. Mailbox sizes can be specified in kilobytes (KB) or megabytes (MB), for example, as 100KB or 5MB. The StorageQuota parameter is valid for managed custom folders in Outlook 2007. ```yaml Type: Unlimited diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md index ab10d066e9..e42e17a347 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md @@ -32,7 +32,7 @@ Set-ManagedFolderMailboxPolicy [-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/Set-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md index 0c8c86b88c..a0c404aed0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md @@ -13,7 +13,7 @@ title: Set-ManagementRoleAssignment # Set-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 Set-ManagementRoleAssignment cmdlet to modify existing management role assignments. @@ -106,7 +106,7 @@ You can create custom management scopes using the New-ManagementScope cmdlet and For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md index de99ac0cc4..5ab67ee695 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md @@ -13,7 +13,7 @@ title: Set-ManagementRoleEntry # Set-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 Set-ManagementRoleEntry cmdlet to change the available parameters on an existing management role entry. @@ -39,7 +39,7 @@ The Set-ManagementRoleEntry cmdlet changes the available parameters on an existi 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 @@ -69,7 +69,7 @@ This example adds the DisplayName and ForwardingAddress parameters to the Set-Ma Set-ManagementRoleEntry "IT Scripts\MailboxAudit" -Parameters Location -AddParameter -UnScopedTopLevel ``` -In on-premises Exchange, this example adds the Location parameter to the MailboxAudit custom script on the IT Scripts unscoped top level role. Note that the UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default. +In on-premises Exchange, this example adds the Location parameter to the MailboxAudit custom script on the IT Scripts unscoped top level role. The UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md index 30b702cd34..8b671cdcef 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md @@ -13,7 +13,7 @@ title: Set-ManagementScope # Set-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 Set-ManagementScope cmdlet to change an existing management scope. @@ -57,11 +57,11 @@ Set-ManagementScope [-Identity] ``` ## DESCRIPTION -If you change a scope that has been associated with management role assignments using the New-ManagementRoleAssignment cmdlet, the updated scope applies to all the associated role assignments. For more information about changing scopes, see [Change a role scope](https://learn.microsoft.com/exchange/change-a-role-scope-exchange-2013-help). +If you change a scope that is associated with management role assignments using the New-ManagementRoleAssignment cmdlet, the updated scope applies to all the associated role assignments. For more information about changing scopes, see [Change a role scope](https://learn.microsoft.com/exchange/change-a-role-scope-exchange-2013-help). 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/Set-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md index 0b55d95639..bd261af787 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md @@ -37,7 +37,7 @@ Set-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 @@ -146,7 +146,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -166,7 +166,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -187,8 +187,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md index 6c39983580..c5de61e4a9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md @@ -13,7 +13,7 @@ title: Set-MessageClassification # Set-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 Set-MessageClassification cmdlet to configure an existing message classification instance in your organization. @@ -38,7 +38,7 @@ Set-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 @@ -141,19 +141,19 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that may be applied to a specified message. Valid values are: +The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that might be applied to a specified message. Valid values are: - Highest - Higher - High - MediumHigh -- Medium (This is the default value) +- Medium (default value) - MediumLow - Low - Lower - Lowest -Although Outlook only lets a user specify a single classification for a message, transport rules may apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter. +Although Outlook only lets a user specify a single classification for a message, transport rules might apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter. ```yaml Type: ClassificationDisplayPrecedenceLevel @@ -213,7 +213,7 @@ Accept wildcard characters: False The PermissionMenuVisible parameter specifies whether the values that you entered for the DisplayName and RecipientDescription parameters are displayed in Outlook as the user composes a message. Valid values are: -- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This is the default value. +- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This value is the default. - $false: Users can't assign the message classification to messages before they're sent, However, messages received with this message classification still display the classification information. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md index 9c8fc8ac44..f6ae4c00ee 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md @@ -13,7 +13,7 @@ title: Set-MigrationBatch # Set-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 Set-MigrationBatch cmdlet to update a migration request for a batch of users. For more information, see [New-MigrationBatch](https://learn.microsoft.com/powershell/module/exchangepowershell/new-migrationbatch). @@ -60,9 +60,9 @@ The Set-MigrationBatch cmdlet configures your existing migration batches to migr - IMAP migration - Google Workspace (formerly G Suite) migration -Some settings can be applied both to the batch as well as to individual users within the batch. It is important to note that when a setting is applied to a user it will override any corresponding setting on the batch. +Some settings can be applied both to the batch as well as to individual users within the batch. A setting applied to a user overrides any corresponding setting on the batch. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -125,7 +125,7 @@ This parameter is available only in on-premises Exchange. The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are: - $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. -- $false: Incremental synchronization is disabled. The migration batch will go into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization. +- $false: Incremental synchronization is disabled. The migration batch enters the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization. ```yaml Type: Boolean @@ -146,7 +146,7 @@ Accept wildcard characters: False The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns in the CSV file that aren't used by migration. Valid values are: - $true: The migration ignores (silently skips) unknown columns in the CSV file (including optional columns with misspelled column headers). All unknown columns are treated like extra columns that aren't used by migration. -- $false: The migration fails if there are any unknown columns in the CSV file. This setting protects against spelling errors in column headers. This is the default value. +- $false: The migration fails if there are any unknown columns in the CSV file. This setting protects against spelling errors in column headers. This value is the default. ```yaml Type: Boolean @@ -168,7 +168,7 @@ This parameter is available only in the cloud-based service. The ApproveSkippedItems switch marks all of the skipped items that were discovered prior to the current time as approved. You don't need to specify a value with this switch. -If the data loss that was detected during this migration is significant, the migration will not be able to complete without approving skipped items. Items may have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. +If the data loss that was detected during this migration is significant, the migration can't complete without approving skipped items. Items might have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits). @@ -210,9 +210,9 @@ Accept wildcard characters: False The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the migration request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the migration request is ready to complete. -Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. +Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request fails if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -232,14 +232,14 @@ Accept wildcard characters: False This parameter is functional only in the cloud-based service. -The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch will start, but completion won't start until the date/time you specify with this parameter. +The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch starts, but completion doesn't start until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. -- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. +- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter. ```yaml Type: DateTime @@ -282,7 +282,7 @@ The CSVData parameter specifies the CSV file that contains information about the A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). -**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes that are specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes. +**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes specified in the CSV file are migrated, even if they're outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes. ```yaml Type: Byte[] @@ -329,7 +329,7 @@ For more information about maximum message size values, see the following topics Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -449,7 +449,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been replaced by the MoveOptions parameter. +This parameter is replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -511,14 +511,14 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration will be prepared, but the actual data migration for users within the batch won't start until the date/time you specify with this parameter. +The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration is prepared, but the actual data migration for users within the batch doesn't start until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. -- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. +- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter. ```yaml Type: DateTime diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md index 0c567f3657..605b6fd87b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md @@ -13,7 +13,7 @@ title: Set-MigrationConfig # Set-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 Set-MigrationConfig cmdlet to edit migration configurations on Exchange servers. @@ -34,7 +34,7 @@ Set-MigrationConfig ``` ## 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/Set-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md index 219d487254..ff7cf2b290 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md @@ -13,7 +13,7 @@ title: Set-MigrationEndpoint # Set-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 Set-MigrationEndpoint cmdlet to edit settings for cutover or staged Exchange migrations, IMAP migrations, Google Workspace (formerly G Suite) migrations, and remote moves. @@ -67,7 +67,7 @@ For more information about the different move and migration scenarios, see: Changes made to an endpoint that affect the individual users within the batch are applied starting at the next time that the batch is processed. If you are running this cmdlet in the cloud-based service and wish to speed up the application of these settings, consider running the Set-MigrationBatch cmdlet with the -Update 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 @@ -313,7 +313,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The MaxConcurrentMigrations parameter specifies the maximum number of mailboxes that will be migrated for this endpoint at a specified time. This parameter is applicable for all migration types. +The MaxConcurrentMigrations parameter specifies the maximum number of migrated mailboxes for this endpoint at a specified time. This parameter is applicable for all migration types. ```yaml Type: Unlimited @@ -474,7 +474,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that has been granted access to your remote tenant is created. +The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that is granted access to your remote tenant is created. A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md index 06f2e1d789..9e26ca12a5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md @@ -37,9 +37,9 @@ Set-MigrationUser [-Identity] ``` ## DESCRIPTION -Some settings can be applied both to the batch as well as to individual users within the batch. It is important to note that when a setting is applied to a user it will override any corresponding setting on the batch. +Some settings can be applied both to the batch as well as to individual users within the batch. A setting applied to a user overrides any corresponding setting on the batch. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -87,7 +87,7 @@ This parameter is available only in the cloud-based service. The ApproveSkippedItems switch marks all of the skipped items that were discovered prior to the current time as approved. You don't need to specify a value with this switch. -If the data loss that was detected during this migration is significant, the migration will not be able to complete without approving skipped items. Items may have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. +If the data loss that was detected during this migration is significant, the migration can't complete without approving skipped items. Items might have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits). @@ -113,7 +113,7 @@ The BadItemLimit parameter specifies the maximum number of bad items that are al Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. -**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -133,7 +133,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The CompleteAfter parameter specifies a delay before the user is completed. Data migration for the user will start, but won't complete until the date/time you specify with this parameter. +The CompleteAfter parameter specifies a delay before the user is completed. Data migration for the user starts but doesn't complete until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". @@ -210,7 +210,7 @@ For more information about maximum message size values, see the following topics Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. -**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -250,7 +250,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The StartAfter parameter specifies a delay before the data migration for the user is started. The migration will be prepared, but the actual data migration for the user won't start until the date/time you specify with this parameter. +The StartAfter parameter specifies a delay before the data migration for the user is started. The migration is prepared, but the actual data migration for the user doesn't start until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md index 8cb8193e53..1418931139 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md @@ -13,7 +13,7 @@ title: Set-MobileDeviceMailboxPolicy # Set-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 Set-MobileDeviceMailboxPolicy cmdlet to modify mobile device mailbox policies. @@ -91,7 +91,7 @@ Some mobile device mailbox policy settings require the mobile device to have spe Some settings in this cmdlet are supported by Outlook for iOS and Android. For more information, see [Leveraging Exchange Online mobile device policies](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/secure-outlook-for-ios-and-android#leveraging-exchange-online-mobile-device-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -901,7 +901,7 @@ Accept wildcard characters: False The MaxInactivityTimeLock parameter specifies the length of time that the mobile device can be inactive before the password is required to reactivate it. Valid values are: - A timespan: hh:mm:ss, where hh = hours, mm = minutes and ss= seconds. The valid input range is 00:01:00 to 01:00:00 (one minute to one hour). -- The value Unlimited. This is the default value. +- The value Unlimited. This value is the default. ```yaml Type: Unlimited @@ -1036,7 +1036,7 @@ Accept wildcard characters: False The PasswordExpiration parameter specifies how long a password can be used on a mobile device before the user is forced to change the password. Valid values are: - A timespan: ddd.hh:mm:ss, where ddd = days, hh = hours, mm = minutes and ss= seconds. The valid input range is 1.00:00:00 to 730.00:00:00 (one day to two years). -- The value Unlimited. This is the default value +- The value Unlimited. This value is the default ```yaml Type: Unlimited diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md index 1c119aad16..ea5a7779aa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md @@ -13,9 +13,9 @@ title: Set-MoveRequest # Set-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 Set-MoveRequest cmdlet to change move request options after the move request has been created. You can use the Set-MoveRequest cmdlet to recover from failed move requests. +Use the Set-MoveRequest cmdlet to change move request options after the move request is created. You can use the Set-MoveRequest cmdlet to recover from failed move requests. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -57,7 +57,7 @@ Set-MoveRequest [-Identity] ## DESCRIPTION You can pipeline the Set-MoveRequest cmdlet from the Get-MoveRequestStatistics, Get-MoveRequest, or Get-Mailbox 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 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -283,7 +283,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013 -The IgnoreRuleLimitErrors parameter specifies that the command won't move the user's rules to the target server running Microsoft Exchange. +The IgnoreRuleLimitErrors parameter specifies whether the command moves the user's rules to the target server running Microsoft Exchange. ```yaml Type: Boolean @@ -301,7 +301,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. This parameter is used together with the CompleteAfter parameter to create a move request that will do periodic incremental syncs after the initial sync is complete. +The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. Use this parameter with the CompleteAfter parameter to create a move request that does periodic incremental syncs after the initial sync is complete. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -354,7 +354,7 @@ Valid input for this parameter is an integer or the value unlimited. The default If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -395,7 +395,7 @@ Accept wildcard characters: False The PreventCompletion parameter specifies whether to run the move request, but not allow it to complete. Valid values are: - $true: The move request is run, but is not allowed to complete. Instead of this value, we recommend using the CompleteAfter parameter. -- $false: This is the default value. The move request is run and allowed to complete. If you created the move request with the SuspendWhenReadyToComplete or PreventCompletion switches, set this parameter to $false before you run the Resume-MoveRequest cmdlet to complete the move request. +- $false: This value is the default. The move request is run and allowed to complete. If you created the move request with the SuspendWhenReadyToComplete or PreventCompletion switches, set this parameter to $false before you run the Resume-MoveRequest cmdlet to complete the move request. ```yaml Type: Boolean @@ -420,7 +420,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest @@ -574,7 +574,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been replaced by the MoveOptions parameter. +This parameter is replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -643,7 +643,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The SkippedItemApprovalTime parameter marks all of the skipped items discovered prior to the specified time as approved. If the data loss that was detected during this migration is significant, the migration will not be able to complete without approving skipped items. Items may have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. +The SkippedItemApprovalTime parameter marks all of the skipped items discovered prior to the specified time as approved. If the data loss that was detected during this migration is significant, the migration can't complete without approving skipped items. Items might have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits). diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md b/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md index a253128a9d..55cdd0e679 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md @@ -13,7 +13,7 @@ title: Set-Notification # Set-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. @@ -49,7 +49,7 @@ Set-Notification -NotificationEmails -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 @@ -79,7 +79,7 @@ The BackgroundColor parameter specifies the background color. Valid values are: - An HTML hexadecimal color code value (#RRGGBB) enclosed in quotation marks. For example, `"#FFFFFF"` is white. - A valid color name value. For example, `yellow` is #ffff00. For a list of the valid color names, see [Background color reference](https://learn.microsoft.com/purview/add-your-organization-brand-to-encrypted-messages#background-color-reference). -- $null (blank). This is the default value. +- $null (blank). This value is the default. ```yaml Type: String @@ -160,7 +160,7 @@ Accept wildcard characters: False This parameter is available only with a Microsoft 365 Advanced Message Encryption subscription. -The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages will never expire. The default value is 0. +The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages never expire. The default value is 0. You can't update the value of this parameter in the default OME configuration. You can only modify this value in a customized configuration. @@ -182,7 +182,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The Image parameter identifies and uploads an image that will be displayed in the email message and in the Microsoft 365 admin center. +The Image parameter identifies and uploads an image to be displayed in the email message and in the Microsoft 365 admin center. A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). @@ -230,7 +230,7 @@ Accept wildcard characters: False The OTPEnabled parameter specifies whether to allow recipients to use a one-time passcode to view encrypted messages. Valid values are: -- $true: Recipients can use a one-time passcode to view encrypted messages. This is the default value. +- $true: Recipients can use a one-time passcode to view encrypted messages. This value is the default. - $false: Recipients can't use a one-time passcode to view encrypted messages. The recipient is required to sign in using a Microsoft 365 work or school account. ```yaml @@ -311,7 +311,7 @@ Accept wildcard characters: False The SocialIdSignIn parameter specifies whether a user is allowed to view an encrypted message in the Microsoft 365 admin center using their own social network id (Google, Yahoo, and Microsoft account). Valid values are: -- $true: Social network ID sign in is allowed. This is the default value. +- $true: Social network ID sign in is allowed. This value is the default. - $false: Social network ID sign in is not allowed. Whether the recipient can use a one-time passcode or their Microsoft 365 work or school account is controlled by the OTPEnabled parameter. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md b/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md index 2372c45de6..7b7c845e23 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md @@ -27,11 +27,11 @@ Set-OMEMessageRevocation -MessageId -Revoke ``` ## DESCRIPTION -When an email has been revoked, the recipient will get the following error when they try to view the encrypted message in the OME portal: "The message has been revoked by the sender". +When an email is revoked, the recipient gets the following error when they try to view the encrypted message in the OME portal: "The message is revoked by the sender". You can revoke encrypted messages if the recipient received a link-based, branded encrypted email message. If the recipient received a native inline experience in a supported Outlook client, then you can't revoke encryption for the message. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,7 +48,7 @@ This example revokes encryption 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. @@ -70,8 +70,8 @@ Accept wildcard characters: False The Revoke parameter specifies whether to revoke encryption for the message. Valid values are: -- $true: Encryption for the specified message is revoked. The recipient will get an error when they try to view the encrypted message in the OME portal -- $false: Encryption for the specified message isn't revoked. This is the default value. +- $true: Encryption for the specified message is revoked. The recipient gets an error when they try to view the encrypted message in the OME portal +- $false: Encryption for the specified message isn't revoked. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md index 5ec25ce2cb..b5baa5d5b7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md @@ -40,7 +40,7 @@ Set-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 @@ -83,7 +83,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. You can use this parameter with the WindowsAuthentication parameter. @@ -149,7 +149,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -169,7 +169,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -190,8 +190,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -288,7 +288,7 @@ Accept wildcard characters: False The RequireSSL parameter specifies whether the client connection to the virtual directory requires Secure Sockets Layer (SSL) encryption. Valid values are: -- $true: SSL encryption is required to connect to the virtual directory. This is the default value. +- $true: SSL encryption is required to connect to the virtual directory. This value is the default. - $false: SSL encryption isn't required to connect to the virtual directory. ```yaml @@ -327,7 +327,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -- $true: Integrated Windows authentication is enabled. This is the default value. +- $true: Integrated Windows authentication is enabled. This value is the default. - $false: Integrated Windows authentication is disabled. You can use this parameter with the BasicAuthentication parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md index e7ba1533af..9aa1ab5a32 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md @@ -13,7 +13,7 @@ title: Set-OfflineAddressBook # Set-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 Set-OfflineAddressBook cmdlet to modify offline address book (OAB) settings. @@ -53,7 +53,7 @@ Set-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 @@ -282,7 +282,7 @@ This parameter is available only in on-premises Exchange. The GlobalWebDistributionEnabled parameter specifies whether all OAB virtual directories in the organization can accept requests to download the OAB. These locations are advertised by the Autodiscover service. Valid values are: - $true: Any OAB virtual directory in the organization can accept requests to download the OAB. You can't use this setting with the VirtualDirectories parameter. -- $false: Only the OAB virtual directories that are specified by the VirtualDirectories parameter accept requests to download the OAB. This is the default value. +- $false: Only the OAB virtual directories that are specified by the VirtualDirectories parameter accept requests to download the OAB. This value is the default. In Exchange 2013 CU7 or later, we recommend that you use the value $true for this parameter. The Client Access services on any Mailbox server can proxy incoming OAB download requests to the correct location. @@ -490,7 +490,7 @@ This parameter is available only in on-premises Exchange. The ShadowMailboxDistributionEnabled parameter specifies whether a read only copy of the OAB (also known as a shadow copy) is distributed to all other OAB generation mailboxes (also known as organization mailboxes). This allows additional Mailbox servers to be endpoints for requests to download the OAB, which can help prevent users from downloading the OAB across slow WAN links. Valid values are: - $true: The OAB is distributed to all other organization mailboxes. -- $false: The OAB is isn't distributed to other organization mailboxes. This is the default value. +- $false: The OAB is isn't distributed to other organization mailboxes. This value is the default. The value of this parameter is only meaningful if you have multiple organization mailboxes, and is only beneficial in Exchange organizations that have multiple Active Directory sites. @@ -625,7 +625,7 @@ Accept wildcard characters: False The ZipOabFilesBeforeUploading specifies whether to use ZIP file compression on the OAB files before uploading them to the server. Valid values are: - $true: ZIP the OAB files. -- $false: Don't ZIP the OAB files. This is the default value. +- $false: Don't ZIP the OAB files. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md index aa0d233348..a6c3d1ea65 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md @@ -35,9 +35,9 @@ Set-OnPremisesOrganization [-Identity] ``` ## DESCRIPTION -The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with a Microsoft 365 organization. Typically, this object is only modified and updated by the Hybrid Configuration wizard. Manual modification of this object may result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization. +The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with a Microsoft 365 organization. Typically, this object is only modified and updated by the Hybrid Configuration wizard. Manual modification of this object might result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -115,7 +115,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration Active Directory object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains may be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com". +The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration Active Directory object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains might be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com". ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md index 763ab36230..35f5f42bd8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md @@ -13,7 +13,7 @@ title: Set-OrganizationConfig # Set-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 Set-OrganizationConfig cmdlet to configure various settings of an Exchange organization. @@ -505,7 +505,7 @@ Set-OrganizationConfig > [!TIP] > The output of the **Get-OrganizationConfig** cmdlet often shows curly braces or `{}` around properties values that accept multiple comma-separated values. Don't use those extra characters in values for the corresponding parameters on this cmdlet. Use the syntax as explained in the parameter descriptions. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -516,11 +516,11 @@ Set-OrganizationConfig -DistributionGroupDefaultOU Users\Groups -DistributionGro This example creates a distribution group naming policy using the following configuration: -Distribution groups will be created in the Users\\Groups container. +Distribution groups are created in the Users\\Groups container. -The words curse, bad, and offensive will be blocked from being used in distribution group names. +The words curse, bad, and offensive are blocked from being used in distribution group names. -All distribution groups will be prefixed with `DL_` and suffixed with an underscore (\_\) and the user's department and country code. +All distribution groups are prefixed with `DL_` and suffixed with an underscore (\_\) and the user's department and country code. ### Example 2 ```powershell @@ -567,7 +567,7 @@ This parameter is available only in the cloud-based service. The ShortenEventScopeDefault parameter specifies whether calendar events start late or end early in the organization. Valid values are: -- 0 or None: Calendar events in the organization don't automatically start late or end early. This is the default value. +- 0 or None: Calendar events in the organization don't automatically start late or end early. This value is the default. - 1 or EndEarly: By default, the end time of all calendar events is reduced by the number of minutes as specified by the values of the DefaultMinutesToReduceLongEventsBy and DefaultMinutesToReduceShortEventsBy parameters. - 2 or StartLate: By default, the start time of all calendar events is delayed by the number of minutes as specified by the values of the DefaultMinutesToReduceLongEventsBy and DefaultMinutesToReduceShortEventsBy parameters. @@ -649,7 +649,7 @@ Accept wildcard characters: False The ActivityBasedAuthenticationTimeoutEnabled parameter enables or disables the inactivity interval for automatic logoff in Outlook on the web (formerly known as Outlook Web App). Valid values are: -- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity that causes logoff in Outlook on the web. This is the default value. +- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity that causes logoff in Outlook on the web. This value is the default. - $false: Automatic logoff based on a period of inactivity in Outlook on the web is disabled. If you're using single sign-on, use the ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled parameter. @@ -698,7 +698,7 @@ Accept wildcard characters: False The ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled parameter enables or disables the inactivity interval for automatic logoff for single sign-on in Outlook on the Web. Valid values are: -- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity in Outlook on the web that causes logoff for single sign-on. This is the default value. +- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity in Outlook on the web that causes logoff for single sign-on. This value is the default. - $false: Automatic logoff based on a period of inactivity in Outlook on the web is disabled for single sign-on. If you aren't using single sign-on, use the ActivityBasedAuthenticationTimeoutEnabled parameter. @@ -853,7 +853,7 @@ Accept wildcard characters: False The AsyncSendEnabled parameter specifies whether to enable or disable async send in Outlook on the web. Valid values are: -- $true: Async send is enabled. This is the default value. +- $true: Async send is enabled. This value is the default. - $false: Async send is disabled. ```yaml @@ -877,7 +877,7 @@ This parameter is available only in the cloud-based service. The AuditDisabled parameter specifies whether to disable or enable mailbox auditing for the organization. Valid values are: - $true: Mailbox auditing is disabled for the organization. -- $false: Allow mailbox auditing in the organization. This is the default value. +- $false: Allow mailbox auditing in the organization. This value is the default. ```yaml Type: Boolean @@ -897,9 +897,14 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The AutodiscoverPartialDirSync parameter is for scenarios where tenants have Directory Synced some of their Active Directory users into the cloud, but still have on-premises Exchange users that are not Directory Synced. Setting this parameter to $true will cause unknown users to be redirected to the on-premises endpoint and will allow on-premises users to discover their mailbox automatically. Online email addresses will be susceptible to enumeration. We recommend full Directory Sync for all Active Directory users and leaving this parameter with the default $false. +The AutodiscoverPartialDirSync parameter is for scenarios where tenants have Directory Synced some of their Active Directory users into the cloud, but still have on-premises Exchange users that are not Directory Synced. Valid values are: -After you enable AutodiscoverPartialDirSync, it will take approximately 3 hours to fully saturate across the cloud. +- $true: Unknown users are redirected to the on-premises endpoint and on-premises users are allowed to discover their mailbox automatically. +- $false: This value is the default. + +We recommend full Directory Sync for all Active Directory users and leaving this parameter with the default value $false. + +After you enable AutodiscoverPartialDirSync, it takes approximately 3 hours to fully saturate across the cloud. ```yaml Type: Boolean @@ -944,7 +949,7 @@ This parameter is available only in the cloud-based service. The AutoExpandingArchive switch enables the auto-expanding archiving feature in an Exchange Online organization. You don't need to specify a value with this switch. -After you enable auto-expanding archiving, additional storage space is automatically added to a user's archive mailbox when it approaches the storage limit. Note that a user's archive mailbox has to be enabled before auto-expanding archiving can take effect. Also note that after you enable auto-expanding archiving for your organization, it can't be disabled. +After you enable auto-expanding archiving, additional storage space is automatically added to a user's archive mailbox when it approaches the storage limit. A user's archive mailbox has to be enabled before auto-expanding archiving can take effect. Also note that after you enable auto-expanding archiving for your organization, it can't be disabled. ```yaml Type: SwitchParameter @@ -987,7 +992,7 @@ This parameter is available only in the cloud-based service. The BlockMoveMessagesForGroupFolders parameter specifies whether to prevent group owners or group members from moving messages between folders in Microsoft 365 Groups. Valid values are: - $true: Group owners or group members can't move messages between folders in Microsoft 365 groups (manually or vial Inbox rules). -- $false: Group owners or group members can move messages between folders in Microsoft 365 groups. This is the default value. +- $false: Group owners or group members can move messages between folders in Microsoft 365 groups. This value is the default. The value of this parameter is meaningful only when the value of the IsGroupFoldersAndRulesEnabled parameter is $true. @@ -1108,7 +1113,7 @@ This parameter is available only in the cloud-based service. The BookingsEnabled parameter specifies whether to enable Microsoft Bookings in an organization. Valid values are: - $true: Bookings is enabled. -- $false: Bookings is disabled. This is the default value. +- $false: Bookings is disabled. This value is the default. Microsoft Bookings is an online and mobile app for small businesses who provide appointment services to customers. @@ -1302,7 +1307,7 @@ This parameter is available only in the cloud-based service. The BookingsPaymentsEnabled parameter specifies whether to enable the online payment node inside Bookings. Valid values are: - $true: Online payments are enabled. -- $false: Online payments are disabled. This is the default value. +- $false: Online payments are disabled. This value is the default. ```yaml Type: Boolean @@ -1388,7 +1393,7 @@ This parameter is available only in the cloud-based service. The BookingsSocialSharingRestricted parameter specifies whether users can see the social sharing options inside Bookings. Valid values are: - $true: Social sharing options are restricted. -- $false: Users can see social sharing options inside Bookings. This is the default value. +- $false: Users can see social sharing options inside Bookings. This value is the default. ```yaml Type: Boolean @@ -1497,7 +1502,7 @@ Accept wildcard characters: False The ConnectorsActionableMessagesEnabled parameter specifies whether to enable or disable actionable buttons in messages (connector cards) from connected apps on Outlook on the web. Valid values are: -- $true: Action buttons in connector cards are enabled, which allows you to take quick actions directly from Outlook on the web (for example, Like or Comment). This is the default value. +- $true: Action buttons in connector cards are enabled, which allows you to take quick actions directly from Outlook on the web (for example, Like or Comment). This value is the default. - $false: Action buttons in connector cards are disabled. For more information about actionable messages in connected apps, see [Connect apps to your inbox in Outlook on the web](https://support.microsoft.com/office/3d41b99c-bf8d-47d4-bc7a-97758b74689d). @@ -1520,7 +1525,7 @@ Accept wildcard characters: False The ConnectorsEnabled parameter specifies whether to enable or disable all connected apps in organization. Valid values are: -- $true: Connectors are enabled. This is the default value. +- $true: Connectors are enabled. This value is the default. - $false: Connectors are disabled. The workloads that are affected by this parameter are Outlook, SharePoint, Teams, and Viva Engage. @@ -1545,7 +1550,7 @@ This parameter is available only in the cloud-based service. The ConnectorsEnabledForOutlook parameter specifies whether to enable or disable connected apps in Outlook on the web. Valid values are: -- $true: Connectors are enabled. This is the default value. +- $true: Connectors are enabled. This value is the default. - $false: Connectors are disabled. To enable and disable the ability to use connectors on specific Microsoft 365 Groups, set the value of this parameter to $true, and then use the ConnectorsEnabled switch on the Set-UnifiedGroup cmdlet. @@ -1572,7 +1577,7 @@ This parameter is available only in the cloud-based service. The ConnectorsEnabledForSharepoint parameter specifies whether to enable or disable connected apps on SharePoint. Valid values are: -- $true: Connectors are enabled. This is the default value. +- $true: Connectors are enabled. This value is the default. - $false: Connectors are disabled. ```yaml @@ -1595,7 +1600,7 @@ This parameter is available only in the cloud-based service. The ConnectorsEnabledForTeams parameter specifies whether to enable or disable connected apps on Teams. Valid values are: -- $true: Connectors are enabled. This is the default value. +- $true: Connectors are enabled. This value is the default. - $false: Connectors are disabled. ```yaml @@ -1618,7 +1623,7 @@ This parameter is available only in the cloud-based service. The ConnectorsEnabledForYammer parameter specifies whether to enable or disable connected apps on Viva Engage. Valid values are: -- $true: Connectors are enabled. This is the default value. +- $true: Connectors are enabled. This value is the default. - $false: Connectors are disabled. ```yaml @@ -1840,7 +1845,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 0 through 2199023254529 bytes(2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. @@ -1870,7 +1875,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 0 through 2199023254529 bytes (2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. @@ -1920,7 +1925,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 0 through 2199023254529 bytes (2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. @@ -1945,7 +1950,7 @@ This parameter is available only in the cloud-based service. The DelayedDelicensingEnabled parameter enables or disables a 30 day grace period for Exchange Online license removals from mailboxes. Valid values are: - $true: Exchange Online license removals from mailboxes are delayed by 30 days. Admins can use the delay to identify potential mistakes and avoid disruptions for affected users. -- $false: Exchange Online license removals from mailboxes aren't delayed. This is the default value. +- $false: Exchange Online license removals from mailboxes aren't delayed. This value is the default. Use the TenantAdminNotificationForDelayedDelicensingEnabled parameter to turn on weekly Service Health advisory notifications for admins about the number of Exchange Online delicensed users who are in the 30 day grace period during the specified 8 day interval. For more information about Service Health, see [How to check Microsoft 365 service health](https://learn.microsoft.com/microsoft-365/enterprise/view-service-health). @@ -1980,7 +1985,7 @@ This parameter is available only in the cloud-based service. The DirectReportsGroupAutoCreationEnabled parameter specifies whether to enable or disable the automatic creation of direct report Microsoft 365 Groups. Valid values are: - $true: The automatic creation of direct report Microsoft 365 Groups is enabled. -- $false: The automatic creation of direct report Microsoft 365 Groups is disabled. This is the default value. +- $false: The automatic creation of direct report Microsoft 365 Groups is disabled. This value is the default. ```yaml Type: Boolean @@ -2120,8 +2125,8 @@ This parameter is available only in the cloud-based service. The ElcProcessingDisabled parameter specifies whether to enable or disable the processing of mailboxes by the Managed Folder Assistant. Valid values are: -- $true: The Managed Folder Assistant isn't allowed to process mailboxes in the organization. Note that this setting will be ignored on a mailbox if a retention policy that has Preservation Lock enabled is applied to that mailbox. -- $false: The Managed Folder Assistant is allowed to process mailboxes in the organization. This is the default value. +- $true: The Managed Folder Assistant isn't allowed to process mailboxes in the organization. This setting is ignored on a mailbox if a retention policy that has Preservation Lock enabled is applied to that mailbox. +- $false: The Managed Folder Assistant is allowed to process mailboxes in the organization. This value is the default. ```yaml Type: Boolean @@ -2184,7 +2189,7 @@ This parameter is available only in on-premises Exchange. The EnableDownloadDomains parameter specifies that Outlook on the web downloads inline images from a different domain than the rest of Outlook on the web. Valid values are: - $true: Outlook on the web uses a different download domain for inline images (for example, downloads.contoso.com). Before you enable this setting, you need to create a CNAME record and certificate for this domain, and add the domain to the ExternalDownloadHostName and InternalDownloadHostName parameters on the Set-OwaVirtualDirectory cmdlet. -- $false: The setting is disabled. This is the default value. +- $false: The setting is disabled. This value is the default. For more information about the security vulnerability that's addressed by this parameter, and for detailed configuration instructions, see [CVE 2021 1730](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-1730). @@ -2249,7 +2254,7 @@ This parameter is available only in the cloud-based service. The EnableOutlookEvents parameter specifies whether Outlook or Outlook on the web (formerly known as Outlook Web App) automatically discovers events from email messages and adds them to user calendars. Valid values are: - $true: Discovery of events from email messages is enabled. -- $false: Discovery of events from email messages is disabled. This is the default value. +- $false: Discovery of events from email messages is disabled. This value is the default. ```yaml Type: Boolean @@ -2272,7 +2277,7 @@ This parameter is available only in the cloud-based service. The EndUserDLUpgradeFlowsDisabled parameter specifies whether to prevent users from upgrading their own distribution groups to Microsoft 365 Groups in an Exchange Online organization. Valid values are: - $true: Users can upgrade distribution groups that they own to Microsoft 365 Groups. -- $false: Users can't upgrade distribution groups that they own to Microsoft 365 Groups. This is the default value. +- $false: Users can't upgrade distribution groups that they own to Microsoft 365 Groups. This value is the default. ```yaml Type: Boolean @@ -2295,7 +2300,7 @@ This parameter is available only in the cloud-based service. The EndUserMailNotificationForDelayedDelicensingEnabled parameter enables or disables periodic email warnings to affected users that have pending Exchange Online license removal requests on their mailboxes. Valid values are: - $true: Affected users receive periodic email notifications about losing access to their mailbox starting ~18 days after the Exchange Online license was removed. -- $false: Affected users don't receive periodic email notifications about losing access to their mailbox. This is the default value. +- $false: Affected users don't receive periodic email notifications about losing access to their mailbox. This value is the default. The value of this parameter is meaningful on when the value of the DelayedDelicensingEnabled parameter is $true. @@ -2400,7 +2405,7 @@ The EwsApplicationAccessPolicy parameter specifies the client applications that - EnforceAllowList: Only applications specified by the EwsAllowList parameter are allowed to access EWS and REST. Access by other applications is blocked. - EnforceBlockList: All applications are allowed to access EWS and REST, except for the applications specified by the EwsBlockList parameter. -Note that if the EwsAllowEntourage, EwsAllowMacOutlook or EwsAllowOutlook parameters are set to a true or false value, they take precedence for access to EWS by Entourage, Mac Outlook, or Outlook, respectively. +If the EwsAllowEntourage, EwsAllowMacOutlook or EwsAllowOutlook parameters are set to a true or false value, they take precedence for access to EWS by Entourage, Mac Outlook, or Outlook, respectively. ```yaml Type: EwsApplicationAccessPolicy @@ -2444,7 +2449,7 @@ The EwsEnabled parameter specifies whether to globally enable or disable EWS acc - $true: All EWS access is enabled. - $false: All EWS access is disabled. -- $null (blank): The setting isn't configured. Access to EWS is controlled individually by the related EWS parameters (for example EwsAllowEntourage). This is the default value. +- $null (blank): The setting isn't configured. Access to EWS is controlled individually by the related EWS parameters (for example EwsAllowEntourage). This value is the default. This parameter has no affect on access to REST. @@ -2562,7 +2567,7 @@ This parameter is available only in the cloud-based service. The FindTimeLockPollForAttendeesEnabled controls whether the **Lock poll for attendees** setting is managed by the organization. Valid values are: -- $true: **Lock poll for attendees** is on. Attendees will not be able to suggest new times or edit other attendees. The meeting organizer can't turn off this setting (always on). +- $true: **Lock poll for attendees** is on. Attendees can't suggest new times or edit other attendees. The meeting organizer can't turn off this setting (always on). - $false: By default, **Lock poll for attendees** is off (initial default) or on (the user saved settings from last poll), but the meeting organizer is allowed to turn the setting off or on to allow or prevent attendees from suggesting new times or editing attendees. This setting overrides individual user settings. @@ -2848,7 +2853,7 @@ This parameter is available only in the cloud-based service. The IsGroupFoldersAndRulesEnabled specifies whether group owners (by default) can create folders and move messages (manually or by using Inbox rules) in Microsoft 365 Groups. Valid values are: - $true: Group owners can create folders and move messages between folders in Microsoft 365 Groups. -- $false: Group owners can't create folders or move messages between folders in Microsoft 365 Groups. This is the default value. +- $false: Group owners can't create folders or move messages between folders in Microsoft 365 Groups. This value is the default. To allow group owners to allow group users to create folders and moved messages in Microsoft 365 Groups, use the IsGroupMemberAllowedToEditContent parameter. @@ -2882,7 +2887,7 @@ The IsGroupMemberAllowedToEditContent parameter specifies whether group owners c • Create, edit, copy, and delete Inbox rules. -- $false: Group owners can't use the **All members will be able to create, edit, move, copy, and delete mail folders and rules within the group** setting in the group properties in Outlook on the web to allow group members to manage folders and messages in Microsoft 365 Groups. Only group owners can manage folders and messages in Microsoft 365 Groups. This is the default value. +- $false: Group owners can't use the **All members will be able to create, edit, move, copy, and delete mail folders and rules within the group** setting in the group properties in Outlook on the web to allow group members to manage folders and messages in Microsoft 365 Groups. Only group owners can manage folders and messages in Microsoft 365 Groups. This value is the default. The value of this parameter is meaningful only when the value of the IsGroupFoldersAndRulesEnabled parameter is $true. @@ -2909,7 +2914,7 @@ Accept wildcard characters: False The LeanPopoutEnabled parameter specifies whether to enable faster loading of pop-out messages in Outlook on the web for Internet Explorer and Microsoft Edge. Valid values are: - $true: Lean pop-outs are enabled. -- $false: Lean pop-outs are disabled. This is the default value. +- $false: Lean pop-outs are disabled. This value is the default. **Notes**: @@ -2934,7 +2939,7 @@ Accept wildcard characters: False The LinkPreviewEnabled parameter specifies whether link preview of URLs in email messages is allowed for the organization. Valid values are: -- $true: Link preview of URLs in email messages is allowed. Users can enable or disable link preview in their Outlook on the web settings. This is the default value. +- $true: Link preview of URLs in email messages is allowed. Users can enable or disable link preview in their Outlook on the web settings. This value is the default. - $false: Link preview of URLs in email messages is not allowed. Users can't enable link preview in their Outlook on the web settings. ```yaml @@ -3087,7 +3092,7 @@ This parameter is available only in on-premises Exchange. The MapiHttpEnabled parameter enables or disables access to mailboxes in Outlook by using MAPI over HTTP. Valid values are: -- $true: Access to mailboxes by using MAPI over HTTP is enabled. This is the default value. +- $true: Access to mailboxes by using MAPI over HTTP is enabled. This value is the default. - $false: Access to mailboxes by using MAPI over HTTP is disabled. You can use the MapiHttpEnabled parameter on the Set-CASMailbox cmdlet to override the global MAPI over HTTP settings for individual users. @@ -3291,7 +3296,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The MicrosoftExchangeRecipientEmailAddresses parameter specifies one or more email addresses for the recipient. All valid Microsoft Exchange email address types may be used. You can specify multiple values for this parameter as a comma-delimited list. If the MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter is set to $true, the email addresses are automatically generated by the default email address policy. This means you can't use the MicrosoftExchangeRecipientEmailAddresses parameter. +The MicrosoftExchangeRecipientEmailAddresses parameter specifies one or more email addresses for the recipient. All valid Microsoft Exchange email address types might be used. You can specify multiple values for this parameter as a comma-delimited list. If the MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter is set to $true, the email addresses are automatically generated by the default email address policy. This means you can't use the MicrosoftExchangeRecipientEmailAddresses parameter. Email addresses that you specify by using the MicrosoftExchangeRecipientEmailAddresses parameter replace any existing email addresses already configured. @@ -3413,11 +3418,9 @@ This parameter is available only in the cloud-based service. The MobileAppEducationEnabled specifies whether to show or hide the Outlook for iOS and Android education reminder in Outlook on the web (formerly known as Outlook Web App). Valid values are: -- $true: Outlook on the web and Outlook desktop will show the education reminder to users who aren't using Outlook for iOS and Android to check their company email and calendar events. This is the default value. +- $true: Outlook on the web and Outlook desktop show the education reminder to users who aren't using Outlook for iOS and Android to check their company email and calendar events. This value is the default. - $false: The Outlook for iOS and Android education reminder is disabled. -This setting will affect Outlook desktop at some point in the future. - ```yaml Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet @@ -3487,7 +3490,7 @@ The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetin - $false: All meetings are not online by default. - $null: If the organization value has not been specified, the default behavior is for meetings to be online. -If a user has already directly interacted with this setting in Outlook or Outlook on the web (formerly known as Outlook Web App or OWA), the value of this parameter is ignored. Eventually, this parameter will override the Outlook-configured setting. +If a user has already directly interacted with this setting in Outlook or Outlook on the web (formerly known as Outlook Web App or OWA), the value of this parameter is ignored. ```yaml Type: Boolean @@ -3530,7 +3533,7 @@ This parameter is available only in the cloud-based service. The OutlookGifPickerDisabled parameter disables the GIF Search (powered by Bing) feature that's built into the Compose page in Outlook on the web. Valid values are: - $true: GIF Search in Outlook on the web is disabled. -- $false: GIF Search in Outlook on the web is enabled. This is the default value. +- $false: GIF Search in Outlook on the web is enabled. This value is the default. ```yaml Type: Boolean @@ -3552,7 +3555,7 @@ This parameter is available only in the cloud-based service. The OutlookMobileGCCRestrictionsEnabled parameter specifies whether to enable or disable features within Outlook for iOS and Android that are not FedRAMP compliant for Microsoft 365 US Government Community Cloud (GCC) customers. Valid values are: -- $true: Disable features that aren't FedRAMP compliant for GCC customers. This is the default value for all GCC customers. +- $true: Disable features that aren't FedRAMP compliant for GCC customers. This value is the default for all GCC customers. - $false: Enable features that aren't FedRAMP compliant for GCC customers. The Outlook for iOS and Android feature and services that are not FedRAMP compliant for Microsoft 365 US Government customers include: @@ -3667,8 +3670,8 @@ This parameter is available only in Exchange Server 2010. The PermanentlyDeleteDisabled parameter specifies whether to disable the PermanentlyDelete retention action for messaging records management (MRM). Valid values are: -- $true The PermanentlyDelete retention action is disabled. This setting only prevents items from being permanently deleted. It doesn't modify existing policies, block the creation of policies with the PermanentlyDelete action or notify users that thePermanentlyDelete action won't actually take effect. -- $false The PermanentlyDelete retention action is enabled. This is the default value. +- $true The PermanentlyDelete retention action is disabled. This setting only prevents items from being permanently deleted. It doesn't modify existing policies, block the creation of policies with the PermanentlyDelete action, or notify users that thePermanentlyDelete action doesn't actually take effect. +- $false The PermanentlyDelete retention action is enabled. This value is the default. A message that's permanently deleted can't be recovered by using the Recoverable Items folder. Additionally, permanently deleted messages aren't returned by a Discovery search, unless litigation hold or single item recovery is enabled for the mailbox. @@ -3690,7 +3693,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -3716,7 +3719,7 @@ The PostponeRoamingSignaturesUntilLater parameter controls whether roaming signa Previously, the only way to disable roaming signatures in Outlook on the web was to open a support ticket. With the introduction of this parameter and value, admins can disable roaming signatures themselves. -- $false: Roaming signatures are enabled for Outlook on the web and the new Outlook for Windows. This is the default value. +- $false: Roaming signatures are enabled for Outlook on the web and the new Outlook for Windows. This value is the default. We recommend that independent software vendors (ISVs) onboard to the [signature API](https://learn.microsoft.com/javascript/api/outlook/office.body#outlook-office-body-setsignatureasync-member(1)) based on [event-based hooks ](https://learn.microsoft.com/office/dev/add-ins/outlook/autolaunch). @@ -3757,7 +3760,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The PublicComputersDetectionEnabled parameter specifies whether Outlook on the web will detect when a user signs from a public or private computer or network, and then enforces the attachment handling settings from public networks. The default is $false. However, if you set this parameter to $true, Outlook on the web will determine if the user is signing in from a public computer, and all public attachment handling rules will be applied and enforced. +The PublicComputersDetectionEnabled parameter specifies whether Outlook on the web detects when a user signs from a public or private computer or network, and then enforces the attachment handling settings from public networks. The default is $false. However, if you set this parameter to $true, Outlook on the web determines if the user is signing in from a public computer, and all public attachment handling rules are applied and enforced. ```yaml Type: Boolean @@ -3800,7 +3803,7 @@ This parameter is available only in on-premises Exchange. The PublicFolderMailboxesLockedForNewConnections parameter specifies whether users are allowed to make new connections to public folder mailboxes. Valid values are: - $true: Users aren't allowed to make new connections to public folder mailboxes. You use this setting during the final stages of public folder migrations. -- $false: Users are allowed to make new connections to public folder mailboxes. This is the default value. +- $false: Users are allowed to make new connections to public folder mailboxes. This value is the default. ```yaml Type: Boolean @@ -3823,7 +3826,7 @@ This parameter is available only in on-premises Exchange. The PublicFolderMailboxesMigrationComplete parameter is used during public folder migration. - $true: Queued messages are rerouted to the new destination. -- $false (This is the default value) +- $false (default value) ```yaml Type: Boolean @@ -3886,7 +3889,7 @@ Accept wildcard characters: False The PublicFolderShowClientControl parameter enables or disables the control access feature for public folders in Microsoft Outlook. Valid values are: - $true: User access to public folders in Outlook is controlled by the value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet (the default value is $false). -- $false: This is the default value. User access to public folders in Outlook is enabled (the control access feature is disabled). The value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet is meaningless. +- $false: This value is the default. User access to public folders in Outlook is enabled (the control access feature is disabled). The value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet is meaningless. ```yaml Type: Boolean @@ -4060,8 +4063,8 @@ This parameter is available only in the cloud-based service. The SendFromAliasEnabled parameter allows mailbox users to send messages using aliases (proxy addresses). Valid values are: -- $true: Aliases on messages will no longer be rewritten to their primary SMTP addresses. Compatible Outlook clients will allow sending from aliases and replying to aliases. Even without an updated Outlook client, users might see changes in behavior because the setting affects all messages sent and received by a mailbox. -- $false: Aliases on messages sent or received will be rewritten to their primary email address. This is the default value. +- $true: Aliases on messages are no longer rewritten to their primary SMTP addresses. Compatible Outlook clients allow sending from aliases and replying to aliases. Even without an updated Outlook client, users might see changes in behavior because the setting affects all messages sent and received by a mailbox. +- $false: Aliases on messages sent or received are rewritten to their primary email address. This value is the default. For more information about the availability of the feature in Outlook on the web, see the [Microsoft 365 roadmap item](https://www.microsoft.com/microsoft-365/roadmap?filters=Exchange&searchterms=59437). For Outlook for Windows, see this [Microsoft 365 roadmap item](https://www.microsoft.com/microsoft-365/roadmap?filters=Outlook&searchterms=64123). @@ -4121,7 +4124,7 @@ Accept wildcard characters: False The SmtpActionableMessagesEnabled parameter specifies whether to enable or disable action buttons in email messages in Outlook on the web. Valid values are: -- $true: Action buttons in email messages are enabled. This is the default value. +- $true: Action buttons in email messages are enabled. This value is the default. - $false: Action buttons in email messages are disabled. ```yaml @@ -4145,7 +4148,7 @@ This parameter is available only in the cloud-based service. The TenantAdminNotificationForDelayedDelicensingEnabled parameter enables or disables weekly admin Service Health advisory notifications that are sent to admins. Valid values are: - $true: Weekly Service Health advisory notifications are sent to admins about the number of Exchange Online delicensed users who are in the 30 day grace period during the specified 8 day interval. -- $false: Disable weekly Service Health advisory notifications about the number of Exchange Online delicensed users. This is the default value. +- $false: Disable weekly Service Health advisory notifications about the number of Exchange Online delicensed users. This value is the default. For more information about Service Health, see [How to check Microsoft 365 service health](https://learn.microsoft.com/microsoft-365/enterprise/view-service-health). @@ -4191,7 +4194,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: MultiValuedProperty @@ -4249,7 +4252,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The VisibleMeetingUpdateProperties parameter specifies whether meeting message updates will be auto-processed on behalf of attendees. Auto-processed updates are applied to the attendee's calendar item, and then the meeting message is moved to the deleted items. The attendee never sees the update in their inbox, but their calendar is updated. +The VisibleMeetingUpdateProperties parameter specifies whether meeting message updates are auto-processed on behalf of attendees. Auto-processed updates are applied to the attendee's calendar item, and then the meeting message is moved to the deleted items. The attendee never sees the update in their inbox, but their calendar is updated. This parameter uses the syntax: `"MeetingProperty1:MeetingStartTimeWithinXMinutes1,MeetingProperty2:MeetingStartTimeWithinXMinutes2,...MeetingPropertyN:MeetingStartTimeWithinXMinutesN"`. @@ -4267,11 +4270,11 @@ The valid meeting properties to monitor for updates are: - Reminder: The reminder time. - AllProperties: Any meeting change. -If you don't specify a MeetingStartTimeWithinXMinutes value for the meeting property, any change to the meeting property will result in visible meeting update messages (regardless of how soon or how far away the meeting is). For updates to recurring meetings, the meeting start time is the start time of the next occurrence in the series. +If you don't specify a MeetingStartTimeWithinXMinutes value for the meeting property, any change to the meeting property results in visible meeting update messages (regardless of how soon or how far away the meeting is). For updates to recurring meetings, the meeting start time is the start time of the next occurrence in the series. The default value is `"Location,AllProperties:15"`: changes to the meeting location at any time, or changes to other meeting properties within 15 minutes of the meeting start time results in visible meeting update messages. -In the following scenarios, meeting update messages are not auto-processed, regardless of the values specified in this parameter. In these scenarios, attendees will always see meeting update messages in their Inbox: +In the following scenarios, meeting update messages are not auto-processed, regardless of the values specified in this parameter. In these scenarios, attendees always see meeting update messages in their Inbox: - The update contains a change to the meeting date, time, or recurrence pattern. - The meeting message is received for a delegated shared calendar. @@ -4321,7 +4324,7 @@ This parameter is available only in the cloud-based service. The WebPushNotificationsDisabled parameter specifies whether to enable or disable Web Push Notifications in Outlook on the Web. This feature provides web push notifications which appear on a user's desktop while the user is not using Outlook on the Web. This brings awareness of incoming messages while they are working elsewhere on their computer. Valid values are: - $true: Web Push Notifications are disabled. -- $false: Web Push Notifications are enabled. This is the default value. +- $false: Web Push Notifications are enabled. This value is the default. ```yaml Type: Boolean @@ -4344,7 +4347,7 @@ This parameter is available only in the cloud-based service. The WebSuggestedRepliesDisabled parameter specifies whether to enable or disable Suggested Replies in Outlook on the web. This feature provides suggested replies to emails so users can easily and quickly respond to messages. Valid values are: - $true: Suggested Replies are disabled. -- $false: Suggested Replies are enabled. This is the default value. +- $false: Suggested Replies are enabled. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md index 32e1291fcb..2e0b8862f8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md @@ -13,7 +13,7 @@ title: Set-OrganizationRelationship # Set-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 Set-OrganizationRelationship cmdlet to modify existing organization relationships. Organization relationships define the settings that are used with external Exchange organizations to access calendar free/busy information or to move mailboxes between on-premises Exchange servers and Exchange Online as part of hybrid deployments. @@ -52,7 +52,7 @@ Set-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 @@ -98,10 +98,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The ArchiveAccessEnabled parameter specifies whether the organization relationship has been configured to provide remote archive access. Valid values are: +The ArchiveAccessEnabled parameter specifies whether the organization relationship is configured to provide remote archive access. Valid values are: - $true: The external organization provides remote access to mailbox archives. -- $false: The external organization doesn't provide remote access to mailbox archives. This is the default value +- $false: The external organization doesn't provide remote access to mailbox archives. This value is the default ```yaml Type: Boolean @@ -143,9 +143,9 @@ Accept wildcard characters: False The DeliveryReportEnabled parameter specifies whether Delivery Reports should be shared over the organization relationship. Valid values are: - $true: Delivery Reports should be shared over the organization relationship. This value means the organization has agreed to share all Delivery Reports with the external organization, and the organization relationship should be used to retrieve Delivery Report information from the external organization. -- $false: Delivery Reports shouldn't be shared over the organization relationship. This is the default value +- $false: Delivery Reports shouldn't be shared over the organization relationship. This value is the default -For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations won't work in either direction. +For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations doesn't work in either direction. ```yaml Type: Boolean @@ -203,7 +203,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable the organization relationship. Valid values are: -- $true: The organization relationship is enabled. This is the default value. +- $true: The organization relationship is enabled. This value is the default. - $false: The organization relationship is disabled. This value completely stops sharing for the organization relationship. ```yaml @@ -245,7 +245,7 @@ Accept wildcard characters: False The FreeBusyAccessEnabled parameter specifies whether the organization relationship should be used to retrieve free/busy information from the external organization. Valid values are: - $true: Free/busy information is retrieved from the external organization. -- $false: Free/busy information isn't retrieved from the external organization. This is the default value. +- $false: Free/busy information isn't retrieved from the external organization. This value is the default. You control the free/busy access level and scope by using the FreeBusyAccessLevel and FreeBusyAccessScope parameters. @@ -344,7 +344,7 @@ Accept wildcard characters: False The MailboxMoveEnabled parameter specifies whether the organization relationship enables moving mailboxes to or from the external organization. Valid values are: - $true: Mailbox moves to or from the external organization are allowed. -- $false: Mailbox moves to from the external organization aren't allowed. This is the default value. +- $false: Mailbox moves to from the external organization aren't allowed. This value is the default. ```yaml Type: Boolean @@ -396,7 +396,7 @@ Accept wildcard characters: False The MailTipsAccessEnabled parameter specifies whether MailTips for users in this organization are returned over this organization relationship. Valid values are: - $true: MailTips for users in this organization are returned over the organization relationship. -- $false: MailTips for users in this organization aren't returned over the organization relationship. This is the default value. +- $false: MailTips for users in this organization aren't returned over the organization relationship. This value is the default. You control the MailTips access level by using the MailTipsAccessLevel parameter. @@ -419,8 +419,8 @@ Accept wildcard characters: False The MailTipsAccessLevel parameter specifies the level of MailTips data externally shared over this organization relationship. This parameter can have the following values: - All: All MailTips are returned, but the recipients in the remote organization are considered external. For the Auto Reply MailTip, the external Auto Reply message is returned. -- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips won't be returned. -- None: No MailTips are returned to the remote organization. This is the default value. +- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips aren't returned. +- None: No MailTips are returned to the remote organization. This value is the default. This parameter is only meaningful when the MailTipsAccessEnabled parameter value is $true. @@ -534,7 +534,7 @@ Accept wildcard characters: False The PhotosEnabled parameter specifies whether photos for users in the internal organization are returned over the organization relationship. Valid values are: - $true: Photos for users in this organization are returned over the organization relationship. -- $false: Photos for users in this organization aren't returned over the organization relationship. This is the default value. +- $false: Photos for users in this organization aren't returned over the organization relationship. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md index b270f10022..aa46e84863 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md @@ -50,7 +50,7 @@ Set-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 @@ -92,7 +92,7 @@ Accept wildcard characters: False The AllAcceptedDomains parameter specifies whether the Outbound connector is used in hybrid organizations where message recipients are in accepted domains of the cloud-based organization. Valid values are: - $true: The Outbound connector is used in hybrid organizations when message recipients are in an accepted domain of the cloud-based organization. This setting requires OnPremises for the ConnectorType value. -- $false: The Outbound connector isn't used in hybrid organizations. This is the default value. +- $false: The Outbound connector isn't used in hybrid organizations. This value is the default. This parameter is effective only for OnPremises connectors. @@ -118,7 +118,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f Valid values are: -- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. +- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. ```yaml @@ -178,7 +178,7 @@ Accept wildcard characters: False The ConnectorSource parameter specifies how the connector is created. Valid values are: -- Default: The connector is manually created. This is the default value for manually created connectors, and we recommend that you don't change this value. +- Default: The connector is manually created. This value is the default for manually created connectors, and we recommend that you don't change this value. - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. @@ -221,7 +221,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable or disable the Outbound connector. Valid values are: -- $true: The connector is enabled. This is the default value. +- $true: The connector is enabled. This value is the default. - $false: The connector is disabled. ```yaml @@ -243,7 +243,7 @@ Accept wildcard characters: False The IsTransportRuleScoped parameter specifies whether the Outbound connector is associated with a transport rule (also known as a mail flow rule). Valid values are: - $true: The connector is associated with a transport rule. -- $false: The connector isn't associated with a transport rule. This is the default value. +- $false: The connector isn't associated with a transport rule. This value is the default. You scope a transport rule to an Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. Messages that match the conditions of the transport rule are routed to their destinations by using the specified Outbound connector. @@ -263,10 +263,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The IsValidated parameter specifies whether the Outbound connector has been validated. Valid values are: +The IsValidated parameter specifies whether the Outbound connector is validated. Valid values are: -- $true: The connector has been validated, -- $false: The connector hasn't been validated. This is the default value. +- $true: The connector is validated, +- $false: The connector hasn't been validated. This value is the default. Use the Validate-OutboundConnector cmdlet to validate the connector. @@ -352,7 +352,7 @@ Accept wildcard characters: False The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises email system. Valid values are: - $true: Messages are routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. -- $false: Messages aren't routed through the on-premises email system. This is the default value. +- $false: Messages aren't routed through the on-premises email system. This value is the default. This parameter is effective only for OnPremises connectors. @@ -375,7 +375,7 @@ Accept wildcard characters: False The SenderRewritingEnabled parameter specifies that all messages that normally qualify for SRS rewriting are rewritten for routing through the on-premises email system. Valid values are: - $true: Messages are rewritten by SRS as needed before being routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. -- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This is the default value. +- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This value is the default. This parameter is effective only for OnPremises connectors. @@ -424,7 +424,7 @@ Accept wildcard characters: False The TestMode parameter specifies whether you want to enabled or disable test mode for the Outbound connector. Valid values are: - $true: Test mode is enabled. -- $false: Test mode is disabled. This is the default value. +- $false: Test mode is disabled. This value is the default. ```yaml Type: Boolean @@ -469,7 +469,7 @@ The TlsSettings parameter specifies the TLS authentication level that's used for - EncryptionOnly: TLS is used only to encrypt the communication channel. No certificate authentication is performed. - CertificateValidation: TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed. - DomainValidation: In addition to channel encryption and certificate validation, the Outbound connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter. -- $null (blank): This is the default value. +- $null (blank): This value is the default. ```yaml Type: TlsAuthLevel @@ -489,7 +489,7 @@ Accept wildcard characters: False The UseMXRecord parameter enables or disables DNS routing for the connector. Valid values are: -- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This is the default value. +- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This value is the default. - $false: The connector delivers email to one or more smart hosts. This setting requires one or more smart hosts for the SmartHosts value. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md index 17d58eac0e..ac591d7859 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md @@ -46,7 +46,7 @@ Set-OutlookAnywhere [-Identity] ## DESCRIPTION For more information about the different authentication methods that you can see in this article, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -122,7 +122,7 @@ The ClientAuthenticationMethod parameter specifies the authentication method tha - Basic - Ntlm -Although you can use this parameter to set only one authentication method, the command won't return an error if you include multiple values. +Although you can use this parameter to set only one authentication method, the command doesn't return an error if you include multiple values. ```yaml Type: AuthenticationMethod @@ -209,7 +209,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -229,7 +229,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -250,8 +250,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -276,7 +276,7 @@ The ExternalClientAuthenticationMethod parameter specifies the authentication me - Basic - Ntlm -- Negotiate (This is the default value) +- Negotiate (default value) You can't use this parameter with the DefaultAuthenticationMethods parameter. @@ -299,7 +299,7 @@ Accept wildcard characters: False The ExternalClientsRequireSsl parameter specifies whether external Outlook Anywhere clients are required to use Secure Sockets Layer (SSL). Valid values are: - $true: Clients connecting via Outlook Anywhere from outside the organization are required to use SSL. -- $false: Clients connecting via Outlook Anywhere from outside the organization aren't required to use SSL. This is the default value. +- $false: Clients connecting via Outlook Anywhere from outside the organization aren't required to use SSL. This value is the default. The value of this parameter is related to the value of the SSLOffloading parameter. @@ -366,7 +366,7 @@ Accept wildcard characters: False The InternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate internal Outlook Anywhere clients. Valid values are: - Basic -- Ntlm (This is the default value) +- Ntlm (default value) - Negotiate You can't use this parameter with the DefaultAuthenticationMethods parameter. @@ -390,7 +390,7 @@ Accept wildcard characters: False The InternalClientsRequireSsl parameter specifies whether internal Outlook Anywhere clients are required to use SSL. Valid values are: - $true: Clients connecting via Outlook Anywhere from inside the organization are required to use SSL. -- $false: Clients connecting via Outlook Anywhere from inside the organization aren't required to use SSL. This is the default value. +- $false: Clients connecting via Outlook Anywhere from inside the organization aren't required to use SSL. This value is the default. The value of this parameter is related to the value of the SSLOffloading parameter. @@ -448,10 +448,10 @@ Accept wildcard characters: False The SSLOffloading parameter specifies whether a network device accepts SSL connections and decrypts them before proxying the connections to the Outlook Anywhere virtual directory on the Exchange server. Valid values are: -- $true: Outlook Anywhere clients using SSL don't maintain an SSL connection along the entire network path to the Exchange server. A network device in front of the server decrypts the SSL connections and proxies the unencrypted (HTTP) client connections to the Outlook Anywhere virtual directory. The network segment where HTTP is used should be a secured network. This is the default value. +- $true: Outlook Anywhere clients using SSL don't maintain an SSL connection along the entire network path to the Exchange server. A network device in front of the server decrypts the SSL connections and proxies the unencrypted (HTTP) client connections to the Outlook Anywhere virtual directory. The network segment where HTTP is used should be a secured network. This value is the default. - $false: Outlook Anywhere clients using SSL maintain an SSL connection along the entire network path to the Exchange server. Only SSL connections are allowed to the Outlook Anywhere virtual directory. -This parameter configures the Require SSL value on the Outlook Anywhere virtual directory. When you set this parameter to $true, Require SSL is disabled. When you set this parameter to $fase, Require SSL is enabled. However, it may take several minutes before the change is visible in IIS Manager. +This parameter configures the Require SSL value on the Outlook Anywhere virtual directory. When you set this parameter to $true, Require SSL is disabled. When you set this parameter to $fase, Require SSL is enabled. However, it might take several minutes before the change is visible in IIS Manager. You need to use the value $true for this parameter if you don't require SSL connections for internal or external Outlook Anywhere clients. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md index 595590c4a5..e7bc6acefb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md @@ -15,7 +15,7 @@ title: Set-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 Set-OutlookProtectionRule cmdlet to modify an existing Microsoft Outlook protection rule. @@ -44,7 +44,7 @@ Outlook protection rules are used to automatically rights-protect email messages Not specifying any conditions results in an Outlook protection rule being applied to all messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md index aca9ccddb2..aa50953b25 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md @@ -38,7 +38,7 @@ Set-OutlookProvider [-Identity] ## DESCRIPTION The Set-OutlookProvider cmdlet creates the global settings for the Autodiscover service. It sets the AutoDiscoverConfig object under the Global Settings object in Active Directory and sets the attributes specified in the parameters listed in the Parameters section. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -172,7 +172,7 @@ The RequiredClientVersions parameter specifies the minimum version of Microsoft MinimumVersion is the version of Outlook in the format xx.x.xxxx.xxxx. For example, to specify Outlook 2010 Service Pack 2 (SP2), use the value 14.0.7012.1000. -ExpirationDate is the UTC date-time when connections by older versions of Outlook will be blocked. The UTC date-time is represented in the ISO 8601 date-time format: yyyy-MM-ddThh:mm:ss.fffZ, where yyyy = year, MM = month, dd = day, T indicates the beginning of the time component, hh = hour, mm = minute, ss = second, fff = fractions of a second and Z signifies Zulu, which is another way to denote UTC. +ExpirationDate is the UTC date-time when connections by older versions of Outlook are blocked. The UTC date-time is represented in the ISO 8601 date-time format: yyyy-MM-ddThh:mm:ss.fffZ, where yyyy = year, MM = month, dd = day, T indicates the beginning of the time component, hh = hour, mm = minute, ss = second, fff = fractions of a second and Z signifies Zulu, which is another way to denote UTC. An example of a valid value for this parameter is `"14.0.7012.1000, 2020-01-01T12:00:00Z"`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md index 4379af8950..fa861191a0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md @@ -13,7 +13,7 @@ title: Set-OwaMailboxPolicy # Set-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 Set-OwaMailboxPolicy cmdlet to configure existing Outlook on the web mailbox policies. @@ -163,9 +163,9 @@ Set-OwaMailboxPolicy [-Identity] ## DESCRIPTION In on-premises Exchange, the default Outlook on the web mailbox policy is named Default. In Exchange Online, the default Outlook on the web mailbox policy is named OwaMailboxPolicy-Default. -Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (`Stop-Service WAS -Force` and `Start-Service W3SVC`). +Changes to Outlook on the web mailbox policies might take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (`Stop-Service WAS -Force` and `Start-Service W3SVC`). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -247,7 +247,7 @@ Accept wildcard characters: False The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file types that aren't specified in the Allow, Block, and Force Save lists for file types and MIME types. Valid values are: -- Allow (This is the default value.) +- Allow (This value is the default.) - ForceSave - Block @@ -271,7 +271,7 @@ This parameter is available only in the cloud-based service. The AdditionalStorageProvidersAvailable parameter specifies whether to allow additional storage providers (for example, Box, Dropbox, Facebook, Google Drive, Egnyte, personal OneDrive) attachments in Outlook on the web. Valid values are: -- $true: Additional storage providers are enabled in Outlook on the web. Users can connect their additional storage providers and share files over email. This is the default value. +- $true: Additional storage providers are enabled in Outlook on the web. Users can connect their additional storage providers and share files over email. This value is the default. - $false: Additional storage providers are disabled in Outlook on the web. Users can't connect their additional storage providers or share files over email. ```yaml @@ -292,7 +292,7 @@ Accept wildcard characters: False The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disable Exchange ActiveSync settings in Outlook on the web. Valid values are: -- $true: ActiveSync is available in Outlook on the web. This is the default value. +- $true: ActiveSync is available in Outlook on the web. This value is the default. - $false: ActiveSync isn't available in Outlook on the web. ```yaml @@ -313,7 +313,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. To enable or disable personal accounts in the new Outlook for Windows, use the PersonalAccountsEnabled parameter. @@ -335,7 +335,7 @@ Accept wildcard characters: False The AllAddressListsEnabled parameter specifies which address lists are available in Outlook on the web. Valid values are: -- $true: All address lists are visible in Outlook on the web. This is the default value. +- $true: All address lists are visible in Outlook on the web. This value is the default. - $false: Only the global address list is visible in Outlook on the web. ```yaml @@ -356,7 +356,7 @@ Accept wildcard characters: False The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can copy the contents of their Contacts folder to a mobile device's native address book when using Outlook on the web for devices. Valid values are: -- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This is the default value. +- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This value is the default. - $false: Contacts can't be copied to the device's address book in Outlook on the web for devices. ```yaml @@ -462,7 +462,7 @@ The AllowOfflineOn parameter specifies when Outlook Web App in offline mode is a - PrivateComputersOnly: Offline mode is available in private computer sessions. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). - NoComputers: Offline mode is disabled. -- AllComputers: Offline mode is available for public and private computer sessions. This is the default value. +- AllComputers: Offline mode is available for public and private computer sessions. This value is the default. When offline mode is available, users can turn offline mode on or off themselves in Outlook Web App. For more information, see [Use offline settings in Outlook on the web](https://support.microsoft.com/office/a34c9d9d-16ac-4020-b730-ffa7c7540ae7). @@ -631,7 +631,7 @@ This parameter is functional only in on-premises Exchange. The CalendarEnabled parameter specifies whether to enable or disable the calendar in Outlook Web App. Valid values are: -- $true: The Calendar is available in Outlook Web App. This is the default value. +- $true: The Calendar is available in Outlook Web App. This value is the default. - $false: The Calendar isn't available in Outlook Web App. ```yaml @@ -654,7 +654,7 @@ This parameter is functional only in on-premises Exchange. The ChangePasswordEnabled parameter specifies whether users can change their passwords from inside Outlook on the web. Valid values are: -- $true: The Change password option is available in Outlook on the web. This is the default value in on-premises Exchange. +- $true: The Change password option is available in Outlook on the web. This value is the default in on-premises Exchange. - $false: The Change password option isn't available in Outlook on the web. ```yaml @@ -677,7 +677,7 @@ This parameter is available only in the cloud-based service. The ChangeSettingsAccountEnabled parameter specifies whether users can change the email account where app-wide settings (for example, theme and privacy settings) are associated in the new Outlook for Windows. Valid values are: -- $true: Users can change their settings account in the new Outlook for Windows. This is the default value. +- $true: Users can change their settings account in the new Outlook for Windows. This value is the default. - $false: Users can't change their settings account in the new Outlook for Windows. **Note**: The settings account is referred to as the primary account in the new Outlook for Windows setting at Settings \> Accounts \> Email accounts \> Manage. @@ -700,7 +700,7 @@ Accept wildcard characters: False The ClassicAttachmentsEnabled parameter specifies whether users can attach local files as regular email attachments in Outlook on the web. Valid values are: -- $true: Users can attach local files to email messages in Outlook on the web. This is the default value. +- $true: Users can attach local files to email messages in Outlook on the web. This value is the default. - $false: Users can't attach local files to email messages in Outlook on the web. ```yaml @@ -723,11 +723,11 @@ This parameter is available only in the cloud-based service. The ConditionalAccessPolicy parameter specifies the Outlook on the Web Policy for limited access. For this feature to work properly, you also need to configure a Conditional Access policy in the Microsoft Entra admin center. -**Note**: When you enable a Conditional Access policy, users will no longer be able to access the light version of Outlook on the web. An error message will direct them to use the default premium experience. +**Note**: When you enable a Conditional Access policy, users can no longer access the light version of Outlook on the web. An error message directs them to use the default premium experience. Valid values are: -- Off: No conditional access policy is applied to Outlook on the web. This is the default value. +- Off: No conditional access policy is applied to Outlook on the web. This value is the default. - ReadOnly: Users can't download attachments to their local computer, and can't enable Offline Mode on non-compliant computers. They can still view attachments in the browser. This doesn't apply to in-line images. - ReadOnlyPlusAttachmentsBlocked: All restrictions from ReadOnly apply, but users can't view attachments in the browser. This doesn't apply to in-line images. @@ -772,7 +772,7 @@ This parameter is functional only in on-premises Exchange. The ContactsEnabled parameter specifies whether to enable or disable Contacts in Outlook Web App. Valid values are: -- $true: Contacts are available in Outlook Web App. This is the default value. +- $true: Contacts are available in Outlook Web App. This value is the default. - $false: Contacts aren't available in Outlook Web App. ```yaml @@ -791,7 +791,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Int32 @@ -811,7 +811,7 @@ Accept wildcard characters: False The DefaultTheme parameter specifies the default theme that's used in Outlook on the web when the user hasn't selected a theme. The default value is blank ($null). For more information about the built-in themes that are available in Outlook on the web, see [Default Outlook on the web themes in Exchange](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016). -Note that this parameter is a text string, and the value you specify isn't validated against the list of available themes. +This parameter is a text string, and the value you specify isn't validated against the list of available themes. ```yaml Type: String @@ -833,7 +833,7 @@ This parameter is functional only in on-premises Exchange. The DelegateAccessEnabled parameter specifies whether delegates can use Outlook on the web or Outlook Web App to open folders that they have delegate access to. Valid values are: -- $true: Delegates can open the mailbox in Outlook on the web. This is the default value. +- $true: Delegates can open the mailbox in Outlook on the web. This value is the default. - $false: Delegates can't open the mailbox in Outlook on the web. ```yaml @@ -854,8 +854,8 @@ Accept wildcard characters: False The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for private computer sessions. Valid values are: -- $true: Open is available for attachments in Outlook on the web for private computer sessions. This is the default value. -- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. +- $true: Open is available for attachments in Outlook on the web for private computer sessions. This value is the default. +- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Office and .pdf documents can still be previewed in Outlook on the web. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. @@ -877,8 +877,8 @@ Accept wildcard characters: False The DirectFileAccessOnPublicComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for public computer sessions. Valid values are: -- $true: Open is available for attachments in Outlook on the web for public computer sessions. This is the default value. -- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. +- $true: Open is available for attachments in Outlook on the web for public computer sessions. This value is the default. +- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Office and .pdf documents can still be previewed in Outlook on the web. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). @@ -927,7 +927,7 @@ Accept wildcard characters: False The DisplayPhotosEnabled parameter specifies whether users see sender photos in Outlook on the web. Valid values are: -- $true: Users see sender photos in Outlook on the web. This is the default value. +- $true: Users see sender photos in Outlook on the web. This value is the default. - $false: Users don't see sender photos in Outlook on the web. ```yaml @@ -1010,7 +1010,7 @@ This parameter is functional only in on-premises Exchange. The ExplicitLogonEnabled parameter specifies whether to allow a user to open someone else's mailbox in Outlook on the web (provided that user has permissions to the mailbox). Valid values are: -- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This is the default value. +- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This value is the default. - $false: A user with the required permissions isn't able to open someone else's mailbox in Outlook on the web. ```yaml @@ -1033,7 +1033,7 @@ This parameter is available only in the cloud-based service. The ExternalImageProxyEnabled parameter specifies whether to load all external images through the Outlook external image proxy. Valid values are: -- $true: All external images are loaded through the Outlook external image proxy. This is the default value. +- $true: All external images are loaded through the Outlook external image proxy. This value is the default. - $false: All external images are loaded through the web browser. This is potentially unsafe, as the images could have mixed content or malformed images that ask for user credentials. ```yaml @@ -1076,7 +1076,7 @@ This cmdlet is available only in the cloud-based service. The FeedbackEnabled parameter specifies whether to enable or disable inline feedback surveys in Outlook on the web. Valid values are: -- $true: Inline feedback surveys are enabled. This is the default value. +- $true: Inline feedback surveys are enabled. This value is the default. - $false: Inline feedback surveys are disabled. Surveys allow users to provide feedback on specific features. For example, for the text predictions feature, the inline feedback "Are the above autocomplete suggestions helpful (yes/no)?" is shown. If a user chooses "no" they can provide specific feedback. @@ -1100,7 +1100,7 @@ Accept wildcard characters: False The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are filtered before they can be saved from Outlook on the web. Valid values are: - $true: The attachments specified by the ForceSaveFileTypes parameter are filtered before they can be saved from Outlook on the web. -- $false: The attachments aren't filtered before they're saved. This is the default value. +- $false: The attachments aren't filtered before they're saved. This value is the default. ```yaml Type: Boolean @@ -1183,7 +1183,7 @@ Accept wildcard characters: False The ForceWacViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) before opening the file in the local application. Valid values are: - $true: Private computers must first preview an Office file as a web page in Office Online Server before opening the file. -- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. +- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. @@ -1206,7 +1206,7 @@ Accept wildcard characters: False The ForceWacViewingFirstOnPublicComputers parameter specifies whether public computers must first preview an Office file as a web page in Office Online Server before opening the file in the local application. Valid values are: - $true: Public computers must first preview an Office file as a web page in Office Online Server before opening the file. -- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. +- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). @@ -1231,7 +1231,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013 The ForceWebReadyDocumentViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: - $true: Private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. -- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. +- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. @@ -1256,7 +1256,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013 The ForceWebReadyDocumentViewingFirstOnPublicComputers parameter specifies whether Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: - $true: Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. -- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. +- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). @@ -1298,7 +1298,7 @@ Accept wildcard characters: False The GlobalAddressListEnabled parameter specifies whether the global address list is available in Outlook on the web. Valid values are: -- $true: The global address list is visible in Outlook on the web. This is the default value. +- $true: The global address list is visible in Outlook on the web. This value is the default. - $false: The global address list isn't visible in Outlook on the web. ```yaml @@ -1341,7 +1341,7 @@ This parameter is functional only in the cloud-based service. The GroupCreationEnabled parameter specifies whether Microsoft 365 Group creation is available in Outlook and Outlook on the web. Valid values are: -- $true: Users can create Microsoft 365 Groups in Outlook and Outlook on the web. This is the default value. +- $true: Users can create Microsoft 365 Groups in Outlook and Outlook on the web. This value is the default. - $false: Users can't create Microsoft 365 Groups in Outlook and Outlook on the web. ```yaml @@ -1365,7 +1365,7 @@ This parameter is available only in the cloud-based service. The HideClassicOutlookToggleOut parameter specifies whether to enable or disable hiding the toggle in new Outlook that allows users to switch back to classic Outlook. Valid values are: - $true: The toggle to switch back to classic Outlook is hidden in new Outlook for Windows. -- $false: The toggle to switch back to classic Outlook isn't hidden in new Outlook for Windows. This is the default value. +- $false: The toggle to switch back to classic Outlook isn't hidden in new Outlook for Windows. This value is the default. ```yaml Type: System.Boolean @@ -1385,7 +1385,7 @@ Accept wildcard characters: False The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. This does not affect chat capabilities provided by Skype for Business or Teams. Valid values are: -- $true: Instant messaging is available in Outlook on the web. This is the default value. +- $true: Instant messaging is available in Outlook on the web. This value is the default. - $false: Instant messaging isn't available in Outlook on the web. ```yaml @@ -1406,8 +1406,8 @@ Accept wildcard characters: False The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are: -- None: This is the default value in on-premises Exchange. -- Ocs: Lync or Skype (formerly known as Office Communication Server). This is the default value in Exchange Online. +- None: This value is the default in on-premises Exchange. +- Ocs: Lync or Skype (formerly known as Office Communication Server). This value is the default in Exchange Online. ```yaml Type: InstantMessagingTypeOptions @@ -1429,7 +1429,7 @@ This parameter is available only in the cloud-based service. The InterestingCalendarsEnabled parameter specifies whether interesting calendars are available in Outlook on the web. Valid values are: -- $true: Interesting calendars are available in Outlook on thew web. This is the default value. +- $true: Interesting calendars are available in Outlook on thew web. This value is the default. - $false: Interesting calendars aren't available in Outlook on the web. ```yaml @@ -1470,7 +1470,7 @@ Accept wildcard characters: False The IRMEnabled parameter specifies whether Information Rights Management (IRM) features are available in Outlook on the web. Valid values are: -- $true: IRM is available in Outlook on the web. This is the default value. +- $true: IRM is available in Outlook on the web. This value is the default. - $false: IRM isn't available in Outlook on the web. ```yaml @@ -1493,7 +1493,7 @@ The IsDefault switch specifies whether the Outlook on the web policy is the defa If another policy is currently set as the default, this switch replaces the old default policy with this policy. -**Note**: In Exchange Online - and excluding resource mailboxes - this value will be superseded by the **OwaMailboxPolicy** parameter in each organization's [CASMailboxPlan](https://learn.microsoft.com/powershell/module/exchangepowershell/set-casmailboxplan). That value will instead be applied per each mailbox's SKU. +**Note**: In Exchange Online - and excluding resource mailboxes - this value is superseded by the _OwaMailboxPolicy_ parameter on the [Set- CASMailboxPlan](https://learn.microsoft.com/powershell/module/exchangepowershell/set-casmailboxplan) cmdlet. That value is applied instead per each mailbox's license. ```yaml Type: SwitchParameter @@ -1516,7 +1516,7 @@ This parameter is available only in the cloud-based service. The ItemsToOtherAccountsEnabled parameter specifies whether users can move or copy email messages between accounts. Valid values are: - $true: Users can move and copy messages to and from external accounts. -- $false: Users can't move or copy messages to and from external accounts. This is the default value. +- $false: Users can't move or copy messages to and from external accounts. This value is the default. **Note:** This policy doesn't affect moving or copying messages between Microsoft 365 Groups and shared mailboxes within the organization. @@ -1538,7 +1538,7 @@ Accept wildcard characters: False The JournalEnabled parameter specifies whether the Journal folder is available in Outlook on the web. Valid values are: -- $true: The Journal folder is visible in Outlook on the web. This is the default value. +- $true: The Journal folder is visible in Outlook on the web. This value is the default. - $false: The Journal folder isn't visible in Outlook on the web. ```yaml @@ -1561,7 +1561,7 @@ This parameter is available only in on-premises Exchange. The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk email management are available in Outlook on the web. Valid values are: -- $true: The Junk Email folder and junk email management are available in Outlook on the web. This is the default value. +- $true: The Junk Email folder and junk email management are available in Outlook on the web. This value is the default. - $false: The Junk Email folder and junk email management aren't available in Outlook on the web. ```yaml @@ -1605,7 +1605,7 @@ This parameter is available only in the cloud-based service. The LocalEventsEnabled parameter specifies whether local events calendars are available in Outlook on the web. Valid values are: - $true: Local events are available in Outlook on the web. -- $false: Local events aren't available in Outlook on the web. This is the default value. +- $false: Local events aren't available in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -1705,7 +1705,7 @@ Accept wildcard characters: False The NotesEnabled parameter specifies whether the Notes folder is available in Outlook on the web. Valid values are: -- $true: The Notes folder is visible in Outlook on the web. This is the default value. +- $true: The Notes folder is visible in Outlook on the web. This value is the default. - $false: The Notes folder isn't visible in Outlook on the web. ```yaml @@ -1728,7 +1728,7 @@ This parameter is available only in the cloud-based service. The NpsSurveysEnabled parameter specifies whether to enable or disable the Net Promoter Score (NPS) survey in Outlook on the web. The survey allows users to rate Outlook on the web on a scale of 1 to 5, and to provide feedback and suggested improvements in free text. Valid values are: -- $true: The NPS survey is available in Outlook on the web. This is the default value. +- $true: The NPS survey is available in Outlook on the web. This value is the default. - $false: The NPS survey isn't available in Outlook on the web. ```yaml @@ -1751,7 +1751,7 @@ This parameter is available only in the cloud-based service. The OfflineEnabledWeb parameter specifies whether offline capabilities are available in Outlook on the web, including saving items to the local device (view items without an internet connection). Valid values are: -- $true: Users can manage offline capabilities in Outlook on the web. This is the default value. +- $true: Users can manage offline capabilities in Outlook on the web. This value is the default. - $false: Users can't manage offline capabilities in Outlook on the web. No items are saved to the user's device. Previously save items are deleted. When offline capabilities are available, users can turn offline capabilities on or off themselves in Outlook on the web at Settings \> General \> Offline. @@ -1776,7 +1776,7 @@ This parameter is available only in the cloud-based service. The OfflineEnabledWin parameter specifies whether offline capabilities are available in the new Outlook for Windows, including saving items to the local device (view items without an internet connection). Valid values are: -- $true: Users can manage offline capabilities in the new Outlook for Windows. This is the default value. +- $true: Users can manage offline capabilities in the new Outlook for Windows. This value is the default. - $false: Users can't manage offline capabilities in the new Outlook for Windows. No items are saved to the user's device. Previously save items are deleted. When offline capabilities are available, users can turn offline capabilities on or off themselves in the New Outlook for Windows at Settings \> General \> Offline. By default, offline capabilities are turned on. @@ -1797,7 +1797,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. To enable or disable personal OneDrive in Outlook on the web, use the AdditionalStorageProvidersAvailable parameter. @@ -1821,7 +1821,7 @@ This parameter is available only in the cloud-based service. The OneWinNativeOutlookEnabled parameter controls the availability of the new Outlook for Windows App. Valid values are: -- $true: The New Outlook for Windows App is available. This is the default value. +- $true: The New Outlook for Windows App is available. This value is the default. - $false: The new Outlook for Windows App isn't available. ```yaml @@ -1841,8 +1841,8 @@ Accept wildcard characters: False The OnSendAddinsEnabled parameter specifies whether a mail item can be edited while an on-send add-in is processing it in Outlook on the web or the new Outlook on Windows. Valid values are: -- $true: A user can't edit a mail item while an on-send add-in is processing the item. -- $false: A user can edit a mail item while an on-send add-in is processing the item. This is the default value. +- $true: On send add-ins are enabled. +- $false: On send add-ins are disabled. This value is the default. ```yaml Type: Boolean @@ -1880,7 +1880,7 @@ Accept wildcard characters: False The OutboundCharset parameter specifies the character set that's used for outgoing messages in Outlook on the web. Valid values are: -- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This is the default value. +- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This value is the default. - AlwaysUTF8: Always use UTF-8 encoded Unicode characters in outgoing messages, regardless of the detected text in the message, or the user's language choice in Outlook on the web. Use this value if replies to UTF-8 encoded messages aren't being encoded in UTF-8. - UserLanguageChoice: Use the user's language choice in Outlook on the web to encode outgoing messages. @@ -1904,7 +1904,7 @@ This parameter is available only in the cloud-based service. The OutlookBetaToggleEnabled parameter specifies whether to enable or disable the Outlook on the web Preview toggle. The Preview toggle allows users to try the new Outlook on the web experience. Valid values are: -- $true: The Outlook on the web Preview toggle is enabled. Users can easily switch back and forth between both experiences. This is the default value. +- $true: The Outlook on the web Preview toggle is enabled. Users can easily switch back and forth between both experiences. This value is the default. - $false: Outlook on the web Preview is disabled. ```yaml @@ -1930,7 +1930,7 @@ The OutlookNewslettersAccessLevelAccess parameter specifies the access level in - NoAccess: No access to Outlook Newsletters in the New Outlook for Windows or Outlook on the web. Users can still read email messages sent or forwarded to them. - ReadOnly: Read newsletters and browse pages in Outlook Newsletters. - ReadWrite: Full authoring permissions to create pages and newsletters in Outlook Newsletters. -- Undefined: This is the default value. Currently, this value is equivalent to NoAccess. +- Undefined: This value is the default. Currently, this value is equivalent to NoAccess. ```yaml Type: OutlookNewslettersAccessLevel @@ -1982,7 +1982,7 @@ The OutlookNewslettersReactions parameter specifies whether reactions are enable - DefaultOff: The controls are turned off. - DefaultOn: The controls are turned on. - Disabled: The controls are disabled for users. -- Undefined: This is the default value. +- Undefined: This value is the default. ```yaml Type: OutlookNewslettersFeatureState @@ -2007,7 +2007,7 @@ The OutlookNewslettersShowMore parameter specifies whether recommendations to ot - DefaultOff: Recommendations are turned off. - DefaultOn: Recommendations are turned on. - Disabled: Recommendations are disabled for users. -- Undefined: This is the default value. +- Undefined: This value is the default. Authors can disable these recommendations for each individual newsletter edition, or admins can use this parameter to globally disable these recommendations. @@ -2029,7 +2029,7 @@ Accept wildcard characters: False The OWALightEnabled parameter controls the availability of the light version of Outlook on the web. Valid values are: -- $true: The light version of Outlook on the web is available. This is the default value. +- $true: The light version of Outlook on the web is available. This value is the default. - $false: The light version of Outlook on the web isn't available. This setting prevents access to Outlook on the web for unsupported browsers that can only use the light version of Outlook on the web. ```yaml @@ -2052,7 +2052,7 @@ This parameter is available only in Exchange Server 2010. The OWAMiniEnabled parameter controls the availability of the mini version of Outlook Web App. Valid values are: -- $true: The mini version of Outlook Web App is available. This is the default value. +- $true: The mini version of Outlook Web App is available. This value is the default. - $false: The mini version of Outlook Web App isn't available. ```yaml @@ -2075,7 +2075,7 @@ This parameter is available only in the cloud-based service. The PersonalAccountCalendarsEnabled parameter specifies whether to allow users to connect to their personal Outlook.com or Google Calendar in Outlook on the web. Valid values are: -- $true: Users can connect to their Outlook.com or Google Calendar to see those events in their Outlook on the web calendar. This is the default value. +- $true: Users can connect to their Outlook.com or Google Calendar to see those events in their Outlook on the web calendar. This value is the default. - $false: Users can't connect to their Outlook.com or Google Calendar in Outlook on the web. ```yaml @@ -2098,7 +2098,7 @@ This parameter is available only in the cloud-based service. The PersonalAccountsEnabled parameter specifies whether to allow users to add their personal accounts (for example, Outlook.com, Gmail, or Yahoo!) in the new Outlook for Windows. Valid values are: -- $true: Users can add their personal accounts in the new Outlook for Windows. This is the default value. +- $true: Users can add their personal accounts in the new Outlook for Windows. This value is the default. - $false: Users can't add their personal accounts in the new Outlook for Windows. ```yaml @@ -2139,7 +2139,7 @@ This parameter is available only in the cloud-based service. The PlacesEnabled parameter specifies whether to enable or disable Places in Outlook on the web. Places lets users search, share, and map location details by using Bing. Valid values are: -- $true: Places is enabled. This is the default value. +- $true: Places is enabled. This value is the default. - $false: Places is disabled. ```yaml @@ -2160,7 +2160,7 @@ Accept wildcard characters: False The PremiumClientEnabled parameter controls the availability of the full version of Outlook Web App. Valid values are: -- $true: The full version of Outlook Web App is available for supported browsers. This is the default value. +- $true: The full version of Outlook Web App is available for supported browsers. This value is the default. - $false: The full version of Outlook Web App isn't available. ```yaml @@ -2183,7 +2183,7 @@ This parameter is available only in the cloud-based service. The PrintWithoutDownloadEnabled specifies whether to allow printing of supported files without downloading the attachment in Outlook on the web. Valid values are: -- $true: Supported files can be printed without being downloaded in Outlook on the web. This is the default value. +- $true: Supported files can be printed without being downloaded in Outlook on the web. This value is the default. - $false: Supported files must be downloaded before they can be printed in Outlook on the web. ```yaml @@ -2209,7 +2209,7 @@ This parameter is available only in the cloud-based service. The ProjectMocaEnabled parameter enables or disables access to Project Moca in Outlook on the web. Valid values are: - $true: Access to Project Moca is enabled in Outlook on the web. -- $false: Access to Project Moca is disabled in Outlook on the web. This is the default value. +- $false: Access to Project Moca is disabled in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2231,7 +2231,7 @@ This parameter is functional only in Exchange Server 2010. The PublicFoldersEnabled parameter specifies whether a user can browse or read items in public folders in Outlook Web App. Valid values are: -- $true: Public folders are available in Outlook Web App. This is the default value. +- $true: Public folders are available in Outlook Web App. This value is the default. - $false: Public folders aren't available in Outlook Web App. ```yaml @@ -2254,7 +2254,7 @@ This parameter is functional only in Exchange Server 2010. The RecoverDeletedItemsEnabled parameter specifies whether a user can use Outlook Web App to view, recover, or delete permanently items that have been deleted from the Deleted Items folder. Valid values are: -- $true: Users can view, recover, or permanently delete items in Outlook Web App. This is the default value. +- $true: Users can view, recover, or permanently delete items in Outlook Web App. This value is the default. - $false: Users can't view, recover, or permanently delete items in Outlook Web App. Items deleted from the Deleted Items folder in Outlook Web App are still retained. ```yaml @@ -2275,7 +2275,7 @@ Accept wildcard characters: False The ReferenceAttachmentsEnabled parameter specifies whether users can attach files from the cloud as linked attachments in Outlook on the web. Valid values are: -- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This is the default value. +- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This value is the default. - $false: Users can't share files in the cloud as linked attachments. They need to download a local copy of the file before attaching the file to the email message. ```yaml @@ -2296,7 +2296,7 @@ Accept wildcard characters: False The RemindersAndNotificationsEnabled parameter specifies whether notifications and reminders are enabled in Outlook on the web. Valid values are: -- $true: Notifications and reminders are enabled in Outlook on the web. This is the default value. +- $true: Notifications and reminders are enabled in Outlook on the web. This value is the default. - $false: Notifications and reminders are disabled in Outlook on the web. This parameter doesn't apply to the light version of Outlook Web App. @@ -2321,7 +2321,7 @@ Accept wildcard characters: False The ReportJunkEmailEnabled parameter specifies whether users can report messages as junk or not junk to Microsoft in Outlook on the web. Valid values are: -- $true: This is the default value. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. +- $true: This value is the default. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. - $false: Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox with no option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk** moves the message to the Junk Email folder with no option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. This parameter is meaningful only when the JunkEmailEnabled parameter is set to $true. @@ -2344,7 +2344,7 @@ Accept wildcard characters: False The RulesEnabled parameter specifies whether a user can view, create, or modify server-side rules in Outlook on the web. Valid values are: -- $true: Users can view, create, or modify server-side rules in Outlook on the web. This is the default value. +- $true: Users can view, create, or modify server-side rules in Outlook on the web. This value is the default. - $false: Users can't view, create, or modify server-side rules in Outlook on the web. ```yaml @@ -2365,7 +2365,7 @@ Accept wildcard characters: False The SatisfactionEnabled parameter specifies whether to enable or disable the satisfaction survey. Valid values are: -- $true: The satisfaction survey is enabled. This is the default value. +- $true: The satisfaction survey is enabled. This value is the default. - $false: The satisfaction survey is disabled. ```yaml @@ -2386,7 +2386,7 @@ Accept wildcard characters: False The SaveAttachmentsToCloudEnabled parameter specifies whether users can save regular email attachments to the cloud. Valid values are: -- $true: Users can save regular email attachments to the cloud. This is the default value. +- $true: Users can save regular email attachments to the cloud. This value is the default. - $false: Users can only save regular email attachments locally. ```yaml @@ -2407,7 +2407,7 @@ Accept wildcard characters: False The SearchFoldersEnabled parameter specifies whether Search Folders are available in Outlook on the web. Valid values are: -- $true: Search Folders are visible in Outlook on the Web. This is the default value. +- $true: Search Folders are visible in Outlook on the Web. This value is the default. - $false: Search Folders aren't visible in Outlook on the Web. ```yaml @@ -2428,7 +2428,7 @@ Accept wildcard characters: False The SetPhotoEnabled parameter specifies whether users can add, change, and remove their sender photo in Outlook on the web. Valid values are: -- $true: Users can manage their photos in Outlook on the web. This is the default value. +- $true: Users can manage their photos in Outlook on the web. This value is the default. - $false: Users can't manage their user photo in Outlook on the web. **Note**: To control whether users can update photos for Exchange Online, see [Configure User Administrator support for profile photo updates](https://learn.microsoft.com/graph/profilephoto-configure-settings#configure-user-administrator-support-for-profile-photo-updates). @@ -2449,7 +2449,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The SetPhotoURL parameter controls where users go to select their photo. Note that you can't specify a URL that contains one or more picture files, as there is no mechanism to copy a URL photo to the properties of the users' Exchange Online mailboxes. +The SetPhotoURL parameter controls where users go to select their photo. You can't specify a URL that contains one or more picture files, as there's no mechanism to copy a URL photo to the properties of Exchange Online mailboxes. ```yaml Type: String @@ -2489,7 +2489,7 @@ Accept wildcard characters: False The SignaturesEnabled parameter specifies whether to enable or disable the use of signatures in Outlook on the web. Valid values are: -- $true: Signatures are available in Outlook on the web. This is the default value. +- $true: Signatures are available in Outlook on the web. This value is the default. - $false: Signatures aren't available in Outlook on the web. ```yaml @@ -2512,7 +2512,7 @@ This parameter is functional only in Exchange Server 2010. The SilverlightEnabled parameter specifies whether a user can use Microsoft Silverlight features in Outlook Web App. Valid values are: -- $true: Silverlight features are available in Outlook Web App. This is the default value. +- $true: Silverlight features are available in Outlook Web App. This value is the default. - $false: Silverlight features aren't available in Outlook Web App. ```yaml @@ -2535,7 +2535,7 @@ This parameter is functional only in the cloud-based service. The SkipCreateUnifiedGroupCustomSharepointClassification parameter specifies whether to skip a custom SharePoint page during the creation of Microsoft 365 Groups in Outlook on the web. Valid values are: -- $true: The custom SharePoint page is skipped when a user creates a Microsoft 365 Group in Outlook on the web. This is the default value. +- $true: The custom SharePoint page is skipped when a user creates a Microsoft 365 Group in Outlook on the web. This value is the default. - $false: The custom SharePoint page is shown when a user creates a Microsoft 365 Group in Outlook on the web. ```yaml @@ -2558,7 +2558,7 @@ This parameter is functional only in Exchange Server 2010. The SMimeEnabled parameter specifies whether users can download the S/MIME control for Outlook Web App and use it to read and compose signed and encrypted messages. Valid values are: -- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This is the default value. +- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This value is the default. - $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated. **Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://learn.microsoft.com/Exchange/policy-and-compliance/smime). @@ -2603,7 +2603,7 @@ This parameter is functional only in Exchange Server 2010. The SpellCheckerEnabled parameter specifies whether to enable or disable the built-in Outlook Web App spell checker in the full version of Outlook Web App. Valid values are: -- $true: Spell checking is available in Outlook Web App. This is the default value. +- $true: Spell checking is available in Outlook Web App. This value is the default. - $false: Spell checking isn't available in Outlook Web App. This parameter doesn't apply to the light version of Outlook Web App. @@ -2628,7 +2628,7 @@ This parameter is functional only in on-premises Exchange. The TasksEnabled parameter specifies whether Tasks folder is available in Outlook Web App. Valid values are: -- $true: The Tasks folder is available in Outlook Web App. This is the default value. +- $true: The Tasks folder is available in Outlook Web App. This value is the default. - $false: The Tasks folder isn't available in Outlook Web App. This parameter doesn't apply to the light version of Outlook Web App. @@ -2653,7 +2653,7 @@ This parameter is available only in the cloud-based service. The TeamSnapCalendarsEnabled parameter specifies whether to allow users to connect to their personal TeamSnap calendars in Outlook on the web. Valid values are: -- $true: Users can connect to their TeamSnap calendars to see those events in their Outlook on the web calendar. This is the default value. +- $true: Users can connect to their TeamSnap calendars to see those events in their Outlook on the web calendar. This value is the default. - $false: Users can't connect to their TeamSnap calendars in Outlook on the web. ```yaml @@ -2674,7 +2674,7 @@ Accept wildcard characters: False The TextMessagingEnabled parameter specifies whether users can send and receive text messages in Outlook on the web. Valid values are: -- $true: Text messaging is available in Outlook on the web. This is the default value. +- $true: Text messaging is available in Outlook on the web. This value is the default. - $false: Text messaging isn't available in Outlook on the web. This parameter doesn't apply to the light version of Outlook on the web. @@ -2697,7 +2697,7 @@ Accept wildcard characters: False The ThemeSelectionEnabled parameter specifies whether users can change the theme in Outlook on the web. Valid values are: -- $true: Users can specify the theme in Outlook on the web. This is the default value. +- $true: Users can specify the theme in Outlook on the web. This value is the default. - $false: Users can't specify or change the theme in Outlook on the web. ```yaml @@ -2738,10 +2738,10 @@ Accept wildcard characters: False The UMIntegrationEnabled parameter specifies whether Unified Messaging (UM) integration is enabled in Outlook on the web. Valid values are: -- $true: UM integration is enabled in Outlook on the web. This is the default value. +- $true: UM integration is enabled in Outlook on the web. This value is the default. - $false: UM integration is disabled in Outlook on the web. -This setting applies only if Unified Messaging has been enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). +This setting applies only if Unified Messaging is enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). This parameter doesn't apply to the light version of Outlook on the web. @@ -2763,7 +2763,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -2783,7 +2783,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -2804,7 +2804,7 @@ Accept wildcard characters: False The UseGB18030 parameter specifies whether to use the GB18030 character set instead of GB2312 in Outlook on the web. Valid values are: - $true: GB18030 is used wherever GB2312 would have been used in Outlook on the web. -- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This is the default value. +- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2825,7 +2825,7 @@ Accept wildcard characters: False The UseISO885915 parameter specifies whether to use the character set ISO8859-15 instead of ISO8859-1 in Outlook on the web. Valid values are: - $true: ISO8859-15 is used wherever ISO8859-1 would have been used in Outlook on the web. -- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This is the default value. +- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2847,7 +2847,7 @@ This parameter is functional only in the cloud-based service. The UserVoiceEnabled parameter specifies whether to enable or disable Outlook UserVoice in Outlook on the web. Outlook UserVoice is a customer feedback area that's available in Microsoft 365. Valid values are: -- $true: Outlook UserVoice is enabled. This is the default value. +- $true: Outlook UserVoice is enabled. This value is the default. - $false: Outlook UserVoice is disabled. ```yaml @@ -2868,7 +2868,7 @@ Accept wildcard characters: False The WacEditingEnabled parameter specifies whether to enable or disable editing documents in Outlook on the web by using Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). Valid values are: -- $true: Users can edit supported documents in Outlook on the web. This is the default value. +- $true: Users can edit supported documents in Outlook on the web. This value is the default. - $false: Users can't edit supported documents in Outlook on the web. ```yaml @@ -2889,7 +2889,7 @@ Accept wildcard characters: False The WacExternalServicesEnabled parameter specifies whether to enable or disable external services when viewing documents in Outlook on the web (for example, machine translation) by using Office Online Server. Valid values are: -- $true: External services are enabled when viewing supported documents in Outlook on the web. This is the default value. +- $true: External services are enabled when viewing supported documents in Outlook on the web. This value is the default. - $false: External services are disabled when viewing supported documents in Outlook on the web. ```yaml @@ -2911,7 +2911,7 @@ Accept wildcard characters: False The WacOMEXEnabled parameter specifies whether to enable or disable apps for Outlook in Outlook on the web in Office Online Server. Valid values are: - $true: apps for Outlook are enabled in Outlook on the web. -- $false: apps for Outlook are disabled in Outlook on the web. This is the default value. +- $false: apps for Outlook are disabled in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2931,7 +2931,7 @@ Accept wildcard characters: False The WacViewingOnPrivateComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents private computer sessions in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). By default, all Outlook on the web sessions are considered to be on private computers. Valid values are: -- $true: In private computer sessions, users can view supported Office documents in the web browser. This is the default value. +- $true: In private computer sessions, users can view supported Office documents in the web browser. This value is the default. - $false: In private computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. @@ -2954,7 +2954,7 @@ Accept wildcard characters: False The WacViewingOnPublicComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents in public computer sessions in Office Online Server. Valid values are: -- $true: In public computer sessions, users can view supported Office documents in the web browser. This is the default value. +- $true: In public computer sessions, users can view supported Office documents in the web browser. This value is the default. - $false: In public computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). @@ -2979,7 +2979,7 @@ This parameter is available only in the cloud-based service. The WeatherEnabled parameter specifies whether to enable or disable weather information in the calendar in Outlook on the web. Valid values are: -- $true: Weather is enabled. This is the default value. +- $true: Weather is enabled. This value is the default. - $false: Weather is disabled. ```yaml @@ -3001,7 +3001,7 @@ Accept wildcard characters: False The WebPartsFrameOptionsType parameter specifies what sources can access web parts in IFRAME or FRAME elements in Outlook on the web. Valid values are: - None: There are no restrictions on displaying Outlook on the web content in a frame. -- SameOrigin: This is the default value and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. +- SameOrigin: This value is the default and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. - Deny: Blocks display of Outlook on the web content in a frame, regardless of the origin of the site attempting to access it. ```yaml @@ -3024,7 +3024,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are: -- $true: All supported attachment types are available for WebReady Document Viewing. This is the default value. +- $true: All supported attachment types are available for WebReady Document Viewing. This value is the default. - $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are available for WebReady Document Viewing (you can remove values from the lists). ```yaml @@ -3047,7 +3047,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingOnPrivateComputersEnabled parameter specifies whether WebReady Document Viewing is available in private computer sessions. Valid values are: -- $true: WebReady Document Viewing is available in private computer sessions. This is the default value. +- $true: WebReady Document Viewing is available in private computer sessions. This value is the default. - $false: WebReady Document Viewing isn't available in private computer sessions. By default in Exchange 2013, all Outlook on the web sessions are considered to be on private computers. @@ -3072,7 +3072,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingOnPublicComputersEnabled parameter specifies whether WebReady Document Viewing is in public computer sessions. Valid values are: -- $true: WebReady Document Viewing is available for public computer sessions. This is the default value. +- $true: WebReady Document Viewing is available for public computer sessions. This value is the default. - $false: WebReady Document Viewing isn't available for public computer sessions. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). @@ -3225,10 +3225,9 @@ Accept wildcard characters: False ``` ### -WSSAccessOnPrivateComputersEnabled - > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -3246,7 +3245,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md index bb19fab87e..f60879da83 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md @@ -156,13 +156,13 @@ Before you run the Set-OwaVirtualDirectory cmdlet, consider the following items: - You must have Write access to virtual directory objects in Active Directory. If you don't have the necessary permissions and you try to run the Set-OwaVirtualDirectory cmdlet on the Active Directory virtual directory object, the cmdlet fails. - You must have Write access to virtual directory objects in the metabase for some properties, such as Authentication and GZip. If you don't have the necessary permissions to run the Set-OwaVirtualDirectory cmdlet on a metabase virtual directory object or on a parameter that writes to the metabase, the cmdlet fails. -- Verify that the data source can be read. Depending on the properties that you want to set on an Outlook on the web virtual directory, you may want to run the cmdlet in a test environment on the Outlook on the web virtual directory object in Active Directory, the metabase, or both. +- Verify that the data source can be read. Depending on the properties that you want to set on an Outlook on the web virtual directory, you might want to run the cmdlet in a test environment on the Outlook on the web virtual directory object in Active Directory, the metabase, or both. - You can run the Set-OwaVirtualDirectory cmdlet on any server that has the Exchange Server administration tools installed. - Several parameters for the Set-OwaVirtualDirectory cmdlet can contain more than one value. These are known as multivalued properties. Make sure that you modify multivalued properties correctly. For information, see [Modifying multivalued properties](https://learn.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help). - Many of the Outlook on the web virtual directory settings require you to restart IIS (Stop-Service WAS -Force and Start-Service W3SVC) before the change takes effect. For example, when you enable or disable forms-based authentication, or when you enable or disable the Private computer option on the sign-in page. - To switch from forms-based authentication to Basic authentication, you must first disable forms-based authentication, and then as a separate task, enable Basic authentication. You can't disable forms-based authentication and enable Basic authentication in a single task. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -212,7 +212,7 @@ Accept wildcard characters: False The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file types that aren't specified in the Allow, Block, and Force Save lists for file types and MIME types. Valid values are: -- Allow (This is the default value.) +- Allow (This value is the default.) - ForceSave - Block @@ -234,7 +234,7 @@ Accept wildcard characters: False The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disable Exchange ActiveSync settings in Outlook on the web. Valid values are: -- $true: ActiveSync is available in Outlook on the web. This is the default value. +- $true: ActiveSync is available in Outlook on the web. This value is the default. - $false: ActiveSync isn't available in Outlook on the web ```yaml @@ -256,7 +256,7 @@ Accept wildcard characters: False The AdfsAuthentication parameter enables or disables Active Directory Federation Services (ADFS) authentication on the Outlook on the web virtual directory. Valid values are: - $true: ADFS authentication is enabled. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $true before you can use this value. -- $false: ADFS authentication is disabled. This is the default value. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $false before you can use this value. +- $false: ADFS authentication is disabled. This value is the default. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $false before you can use this value. ```yaml Type: Boolean @@ -276,7 +276,7 @@ Accept wildcard characters: False The AllAddressListsEnabled parameter specifies which address lists are available in Outlook on the web. Valid values are: -- $true: All address lists are visible in Outlook on the web. This is the default value. +- $true: All address lists are visible in Outlook on the web. This value is the default. - $false: Only the global address list is visible in Outlook on the web. ```yaml @@ -297,7 +297,7 @@ Accept wildcard characters: False The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can copy the contents of their Contacts folder to a mobile device's native address book when using Outlook on the web for devices. Valid values are: -- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This is the default value. +- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This value is the default. - $false: Contacts can't be copied to the device's address book in Outlook on the web for devices. ```yaml @@ -381,7 +381,7 @@ The AllowOfflineOn parameter specifies when Outlook on the web in offline mode i - PrivateComputersOnly: Offline mode is available in private computer sessions. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). - NoComputers: Offline mode is disabled. -- AllComputers: Offline mode is available for public and private computer sessions. This is the default value. +- AllComputers: Offline mode is available for public and private computer sessions. This value is the default. When offline mode is available, users can turn offline mode on or off themselves in Outlook on the web. For more information, see [Use offline settings in Outlook on the web](https://support.microsoft.com/office/a34c9d9d-16ac-4020-b730-ffa7c7540ae7). @@ -403,7 +403,7 @@ Accept wildcard characters: False The AnonymousFeaturesEnabled parameter specifies whether you want to allow Outlook on the web users that are logged on anonymously to access specific features. Valid values are: -- $true: Features are enabled for anonymous users. For example, anonymous users can view and change meeting content. This is the default value. +- $true: Features are enabled for anonymous users. For example, anonymous users can view and change meeting content. This value is the default. - $false: Features are disabled for anonymous users. ```yaml @@ -424,7 +424,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. This parameter can be used with the FormsAuthentication parameter or with the DigestAuthentication and WindowsAuthentication parameters. @@ -530,7 +530,7 @@ Accept wildcard characters: False The CalendarEnabled parameter specifies whether to enable or disable the calendar in Outlook on the web. Valid values are: -- $true: The Calendar is available in Outlook on the web. This is the default value. +- $true: The Calendar is available in Outlook on the web. This value is the default. - $false: The Calendar isn't available in Outlook on the web. ```yaml @@ -553,7 +553,7 @@ This parameter is available only in Exchange Server 2010. The CalendarPublishingEnabled parameter specifies whether users can publish their calendar from Outlook Web App. Valid values are: -- $true: Calendar publishing is enabled. This is the default value. +- $true: Calendar publishing is enabled. This value is the default. - $false: Calendar publishing is disabled. ```yaml @@ -574,7 +574,7 @@ Accept wildcard characters: False The ChangePasswordEnabled parameter specifies whether users can change their passwords from inside Outlook on the web. Valid values are: -- $true: The Change password option is available in Outlook on the web. This is the default value in on-premises Exchange. +- $true: The Change password option is available in Outlook on the web. This value is the default in on-premises Exchange. - $false: The Change password option isn't available in Outlook on the web. ```yaml @@ -595,7 +595,7 @@ Accept wildcard characters: False The ClassicAttachmentsEnabled parameter specifies whether users can attach local files as regular email attachments in Outlook on the web. Valid values are: -- $true: Users can attach local files to email messages in Outlook on the web. This is the default value. +- $true: Users can attach local files to email messages in Outlook on the web. This value is the default. - $false: Users can't attach local files to email messages in Outlook on the web. ```yaml @@ -617,7 +617,7 @@ Accept wildcard characters: False The ClientAuthCleanupLevel parameter specifies how much of the cache is cleared when the user logs off from Outlook on the web. Valid values are: - Low -- High (This is the default value) +- High (default value) This parameter doesn't apply to the light version of Outlook on the web. @@ -660,7 +660,7 @@ Accept wildcard characters: False The ContactsEnabled parameter specifies whether to enable or disable Contacts in Outlook on the web. Valid values are: -- $true: Contacts are available in Outlook on the web. This is the default value. +- $true: Contacts are available in Outlook on the web. This value is the default. - $false: Contacts aren't available in Outlook on the web. ```yaml @@ -704,7 +704,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Int32 @@ -742,7 +742,7 @@ Accept wildcard characters: False The DefaultTheme parameter specifies the default theme that's used in Outlook on the web when the user hasn't selected a theme. The default value is blank ($null). For more information about the built-in themes that are available in Outlook on the web, see [Default Outlook on the web themes in Exchange](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016). -Note that this parameter is a text string, and the value you specify isn't validated against the list of available themes. +This parameter is a text string, and the value you specify isn't validated against the list of available themes. ```yaml Type: String @@ -764,7 +764,7 @@ This parameter is functional only in Exchange Server 2010. The DelegateAccessEnabled parameter specifies whether delegates can use Outlook Web App to open folders that they have delegate access to. Valid values are: -- $true: Delegates can open the mailbox in Outlook Web App. This is the default value. +- $true: Delegates can open the mailbox in Outlook Web App. This value is the default. - $false: Delegates can't open the mailbox in Outlook Web App. ```yaml @@ -786,7 +786,7 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. -- $false: Digest authentication is disabled. This is the default value. +- $false: Digest authentication is disabled. This value is the default. You can use this parameter with the FormsAuthentication parameter. @@ -808,8 +808,8 @@ Accept wildcard characters: False The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for private computer sessions. Valid values are: -- $true: Open is available for attachments in Outlook on the web for private computer sessions. This is the default value. -- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. +- $true: Open is available for attachments in Outlook on the web for private computer sessions. This value is the default. +- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Office and .pdf documents can still be previewed in Outlook on the web. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -831,8 +831,8 @@ Accept wildcard characters: False The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for public computer sessions. Valid values are: -- $true: Open is available for attachments in Outlook on the web for public computer sessions. This is the default value. -- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. +- $true: Open is available for attachments in Outlook on the web for public computer sessions. This value is the default. +- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Office and .pdf documents can still be previewed in Outlook on the web. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -854,7 +854,7 @@ Accept wildcard characters: False The DisplayPhotosEnabled parameter specifies whether users see sender photos in Outlook on the web. Valid values are: -- $true: Users see sender photos in Outlook on the web. This is the default value. +- $true: Users see sender photos in Outlook on the web. This value is the default. - $false: Users don't see sender photos in Outlook on the web. ```yaml @@ -929,7 +929,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: ExchwebProxyDestinations @@ -949,7 +949,7 @@ Accept wildcard characters: False The ExplicitLogonEnabled parameter specifies whether to allow a user to open someone else's mailbox in Outlook on the web (provided that user has permissions to the mailbox). Valid values are: -- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This is the default value. +- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This value is the default. - $false: A user with the required permissions isn't able to open someone else's mailbox in Outlook on the web. ```yaml @@ -974,7 +974,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -998,7 +998,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null (blank): This is the default value. +- $null (blank): This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -1023,8 +1023,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -1166,7 +1166,7 @@ Accept wildcard characters: False The FilterWebBeaconsAndHtmlForms parameter specifies how web beacons are handled in Outlook on the web. Valid values are: -- UserFilterChoice (This is the default value) +- UserFilterChoice (default value) - ForceFilter - DisableFilter @@ -1189,7 +1189,7 @@ Accept wildcard characters: False The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are filtered before they can be saved from Outlook on the web. Valid values are: - $true: The attachments specified by the ForceSaveFileTypes parameter are filtered before they can be saved from Outlook on the web. -- $false: The attachments aren't filtered before they're saved. This is the default value. +- $false: The attachments aren't filtered before they're saved. This value is the default. ```yaml Type: Boolean @@ -1272,7 +1272,7 @@ Accept wildcard characters: False The ForceWacViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) before opening the file in the local application. Valid values are: - $true: Private computers must first preview an Office file as a web page in Office Online Server before opening the file. -- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. +- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -1295,7 +1295,7 @@ Accept wildcard characters: False The ForceWacViewingFirstOnPublicComputers parameter specifies whether public computers must first preview an Office file as a web page in Office Online Server before opening the file in the local application. Valid values are: - $true: Public computers must first preview an Office file as a web page in Office Online Server before opening the file. -- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. +- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -1320,7 +1320,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013 The ForceWebReadyDocumentViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: - $true: Private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. -- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. +- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -1345,7 +1345,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013 The ForceWebReadyDocumentViewingFirstOnPublicComputers parameter specifies whether Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: - $true: Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. -- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. +- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -1367,7 +1367,7 @@ Accept wildcard characters: False The FormsAuthentication parameter enables or disables forms-based authentication on the Outlook on the web virtual directory. Valid values are: -- $true: Forms-based authentication is enabled in Outlook on the web. This is the default value. The BasicAuthentication parameter is also set to $true, and the DigestAuthentication and WindowsAuthentication parameters are set to $false. +- $true: Forms-based authentication is enabled in Outlook on the web. This value is the default. The BasicAuthentication parameter is also set to $true, and the DigestAuthentication and WindowsAuthentication parameters are set to $false. - $false: Forms-based authentication is disabled in Outlook on the web. ```yaml @@ -1406,7 +1406,7 @@ Accept wildcard characters: False The GlobalAddressListEnabled parameter specifies whether the global address list is available in Outlook on the web. Valid values are: -- $true: The global address list is visible in Outlook on the web. This is the default value. +- $true: The global address list is visible in Outlook on the web. This value is the default. - $false: The global address list isn't visible in Outlook on the web. ```yaml @@ -1446,7 +1446,7 @@ Accept wildcard characters: False The GzipLevel parameter sets Gzip configuration information for the Outlook on the web virtual directory. Valid values are: - Off -- Low (This is the default value) +- Low (default value) - High - Error @@ -1486,7 +1486,7 @@ Accept wildcard characters: False The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. This does not affect chat capabilities provided by Skype for Business or Teams. Valid values are: -- $true: Instant messaging is available in Outlook on the web. This is the default value. +- $true: Instant messaging is available in Outlook on the web. This value is the default. - $false: Instant messaging isn't available in Outlook on the web. ```yaml @@ -1525,7 +1525,7 @@ Accept wildcard characters: False The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are: -- None: This is the default value. +- None: This value is the default. - Ocs: Lync or Skype (formerly known as Office Communication Server). ```yaml @@ -1546,7 +1546,7 @@ Accept wildcard characters: False The IntegratedFeaturesEnabled parameter specifies whether to allow Outlook on the web users who are logged on using Integrated Windows authentication to access specific features. Valid values are: -- $true: Integrated features are enabled. For example, users logged on using Integrated Windows authentication can view and change meeting content. This is the default value. +- $true: Integrated features are enabled. For example, users logged on using Integrated Windows authentication can view and change meeting content. This value is the default. - $false: Integrated features are disabled. ```yaml @@ -1625,7 +1625,7 @@ Accept wildcard characters: False The IRMEnabled parameter specifies whether Information Rights Management (IRM) features are available in Outlook on the web. Valid values are: -- $true: IRM is available in Outlook on the web. This is the default value. +- $true: IRM is available in Outlook on the web. This value is the default. - $false: IRM isn't available in Outlook on the web. ```yaml @@ -1647,7 +1647,7 @@ Accept wildcard characters: False The IsPublic parameter specifies whether external users use the virtual directory for Outlook on the web in multiple virtual directory environments (you've configured separate virtual directories on the same server for internal vs. external Outlook on the web connections). Valid values are: - $true: External users use the virtual directory for Outlook on the web. -- $false: External users don't use the virtual directory for Outlook on the web. This is the default value. +- $false: External users don't use the virtual directory for Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -1667,7 +1667,7 @@ Accept wildcard characters: False The JournalEnabled parameter specifies whether the Journal folder is available in Outlook on the web. Valid values are: -- $true: The Journal folder is visible in Outlook on the web. This is the default value. +- $true: The Journal folder is visible in Outlook on the web. This value is the default. - $false: The Journal folder isn't visible in Outlook on the web. ```yaml @@ -1688,7 +1688,7 @@ Accept wildcard characters: False The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk email management are available in Outlook on the web. Valid values are: -- $true: The Junk Email folder and junk email management are available in Outlook on the web. This is the default value. +- $true: The Junk Email folder and junk email management are available in Outlook on the web. This value is the default. - $false: The Junk Email folder and junk email management aren't available in Outlook on the web. ```yaml @@ -1711,7 +1711,7 @@ This parameter is available only in Exchange Server 2010. The LegacyRedirectType parameter specifies the type of redirect that Outlook Web App uses to a legacy Client Access server or Front End server when forms-based authentication isn't used on the Exchange 2010 Outlook Web App virtual directory. Valid values are: -- Silent: A standard redirect is used. This is the default value. +- Silent: A standard redirect is used. This value is the default. - Manual: An intermediate page is displayed to show the legacy URL so that users can change their bookmarks. ```yaml @@ -1754,7 +1754,7 @@ Accept wildcard characters: False The LogonFormat parameter specifies the type of logon format that's required for forms-based authentication on the Outlook on the web sign-in page. Valid values are: -- FullDomain: Requires the format domain\\username. This is the default value. +- FullDomain: Requires the format domain\\username. This value is the default. - UserName: Requires only the username, but you also need to specify a value for the DefaultDomain parameter. - PrincipalName: Requires the user principal name (UPN) (for example, user@contoso.com). This sign-in method works only for users whose UPN name is the same as their email address. @@ -1776,7 +1776,7 @@ Accept wildcard characters: False The LogonPageLightSelectionEnabled parameter specifies whether the Outlook on the web sign-in page includes the option to sign in to the light version of Outlook on the web. Valid values are: -- $true: The option to use the light version of Outlook on the web is available on the sign-in page. This is the default value. +- $true: The option to use the light version of Outlook on the web is available on the sign-in page. This value is the default. - $false: The option to use the light version of Outlook on the web is available on the sign-in page. This parameter is meaningful only for browsers that support the full version of Outlook on the web; unsupported browsers are always required to use the light version of Outlook on the web. @@ -1800,7 +1800,7 @@ Accept wildcard characters: False The LogonPagePublicPrivateSelectionEnabled parameter specifies whether the Outlook on the web sign-in page includes the public/private computer session option at sign-in. Valid values are: - $true: The public/private computer session selection is available on the Outlook on the web sign-in page. -- $false: The public/private computer session selection isn't available on the Outlook on the web sign-in page. All sessions are considered to be on private computers. This is the default value. +- $false: The public/private computer session selection isn't available on the Outlook on the web sign-in page. All sessions are considered to be on private computers. This value is the default. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. Users can only specify public computer sessions if you've set this parameter value to $true. @@ -1824,7 +1824,7 @@ Accept wildcard characters: False The NotesEnabled parameter specifies whether the Notes folder is available in Outlook on the web. Valid values are: -- $true: The Notes folder is visible in Outlook on the web. This is the default value. +- $true: The Notes folder is visible in Outlook on the web. This value is the default. - $false: The Notes folder isn't visible in Outlook on the web. ```yaml @@ -1923,7 +1923,7 @@ Accept wildcard characters: False The OutboundCharset parameter specifies the character set that's used for outgoing messages in Outlook on the web. Valid values are: -- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This is the default value. +- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This value is the default. - AlwaysUTF8: Always use UTF-8 encoded Unicode characters in outgoing messages, regardless of the detected text in the message, or the user's language choice in Outlook on the web. Use this value if replies to UTF-8 encoded messages aren't being encoded in UTF-8. - UserLanguageChoice: Use the user's language choice in Outlook on the web to encode outgoing messages. @@ -1945,7 +1945,7 @@ Accept wildcard characters: False The OWALightEnabled parameter controls the availability of the light version of Outlook on the web. Valid values are: -- $true: The light version of Outlook on the web is available. This is the default value. +- $true: The light version of Outlook on the web is available. This value is the default. - $false: The light version of Outlook on the web is isn't available. This setting prevents access to Outlook on the web for unsupported browsers that can only use the light version of Outlook on the web. ```yaml @@ -1968,7 +1968,7 @@ This parameter is available only in Exchange Server 2010. The OWAMiniEnabled parameter controls the availability of the mini version of Outlook Web App. Valid values are: -- $true: The mini version of Outlook Web App is available. This is the default value. +- $true: The mini version of Outlook Web App is available. This value is the default. - $false: The mini version of Outlook Web App isn't available. ```yaml @@ -1989,7 +1989,7 @@ Accept wildcard characters: False The PremiumClientEnabled parameter controls the availability of the full version of Outlook Web App. Valid values are: -- $true: The full version of Outlook Web App is available for supported browsers. This is the default value. +- $true: The full version of Outlook Web App is available for supported browsers. This value is the default. - $false: The full version of Outlook Web App isn't available. ```yaml @@ -2012,7 +2012,7 @@ This parameter is functional only in Exchange Server 2010. The PublicFoldersEnabled parameter specifies whether a user can browse or read items in public folders in Outlook Web App. Valid values are: -- $true: Public folders are available in Outlook Web App. This is the default value. +- $true: Public folders are available in Outlook Web App. This value is the default. - $false: Public folders aren't available in Outlook Web App. ```yaml @@ -2035,7 +2035,7 @@ This parameter is functional only in Exchange Server 2010. The RecoverDeletedItemsEnabled parameter specifies whether a user can use Outlook Web App to view, recover, or delete permanently items that have been deleted from the Deleted Items folder. Valid values are: -- $true: Users can view, recover, or permanently delete items in Outlook Web App. This is the default value. +- $true: Users can view, recover, or permanently delete items in Outlook Web App. This value is the default. - $false: Users can't view, recover, or permanently delete items in Outlook Web App. Items deleted from the Deleted Items folder in Outlook Web App are still retained. ```yaml @@ -2056,7 +2056,7 @@ Accept wildcard characters: False The RedirectToOptimalOWAServer parameter specifies whether to find the optimal server for Outlook on the web. Valid values are: -- $true: Outlook on the web uses service discovery to find the best Mailbox server to use after a user authenticates. This is the default value. +- $true: Outlook on the web uses service discovery to find the best Mailbox server to use after a user authenticates. This value is the default. - $false: Outlook on the web doesn't redirect clients to the optimal Mailbox server. ```yaml @@ -2077,7 +2077,7 @@ Accept wildcard characters: False The ReferenceAttachmentsEnabled parameter specifies whether users can attach files from the cloud as linked attachments in Outlook on the web. Valid values are: -- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This is the default value. +- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This value is the default. - $false: Users can't share files in the cloud as linked attachments. They need to download a local copy of the file before attaching the file to the email message. ```yaml @@ -2098,7 +2098,7 @@ Accept wildcard characters: False The RemindersAndNotificationsEnabled parameter specifies whether notifications and reminders are enabled in Outlook on the web. Valid values are: -- $true: Notifications and reminders are enabled in Outlook on the web. This is the default value. +- $true: Notifications and reminders are enabled in Outlook on the web. This value is the default. - $false: Notifications and reminders are disabled in Outlook on the web. This parameter doesn't apply to the light version of Outlook Web App. @@ -2121,7 +2121,7 @@ Accept wildcard characters: False This parameter is functional only in Exchange Server 2010. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: RemoteDocumentsActions @@ -2141,7 +2141,7 @@ Accept wildcard characters: False This parameter is functional only in Exchange Server 2010. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: MultiValuedProperty @@ -2161,7 +2161,7 @@ Accept wildcard characters: False This parameter is functional only in Exchange Server 2010. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: MultiValuedProperty @@ -2181,7 +2181,7 @@ Accept wildcard characters: False This parameter is functional only in Exchange Server 2010. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: MultiValuedProperty @@ -2201,7 +2201,7 @@ Accept wildcard characters: False The ReportJunkEmailEnabled parameter specifies whether users can report messages as junk or not junk to Microsoft in Outlook on the web. Valid values are: -- $true: This is the default value. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. +- $true: This value is the default. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. - $false: Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox with no option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk** moves the message to the Junk Email folder with no option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. This parameter is meaningful only when the JunkEmailEnabled parameter is set to $true. @@ -2224,7 +2224,7 @@ Accept wildcard characters: False The RulesEnabled parameter specifies whether a user can view, create, or modify server-side rules in Outlook on the web. Valid values are: -- $true: Users can view, create, or modify server-side rules in Outlook on the web. This is the default value. +- $true: Users can view, create, or modify server-side rules in Outlook on the web. This value is the default. - $false: Users can't view, create, or modify server-side rules in Outlook on the web. ```yaml @@ -2245,7 +2245,7 @@ Accept wildcard characters: False The SaveAttachmentsToCloudEnabled parameter specifies whether users can save regular email attachments to the cloud. Valid values are: -- $true: Users can save regular email attachments to the cloud. This is the default value. +- $true: Users can save regular email attachments to the cloud. This value is the default. - $false: Users can only save regular email attachments locally. ```yaml @@ -2268,7 +2268,7 @@ This parameter is functional only in Exchange Server 2010. The SearchFoldersEnabled parameter specifies whether Search Folders are available in Outlook on the web. Valid values are: -- $true: Search Folders are visible in Outlook on the Web. This is the default value. +- $true: Search Folders are visible in Outlook on the Web. This value is the default. - $false: Search Folders aren't visible in Outlook on the Web. ```yaml @@ -2289,7 +2289,7 @@ Accept wildcard characters: False The SetPhotoEnabled parameter specifies whether users can add, change, and remove their sender photo in Outlook on the web. Valid values are: -- $true: Users can manage their photos in Outlook on the web. This is the default value. +- $true: Users can manage their photos in Outlook on the web. This value is the default. - $false: Users can't manage their user photo in Outlook on the web. ```yaml @@ -2328,7 +2328,7 @@ Accept wildcard characters: False The SignaturesEnabled parameter specifies whether to enable or disable the use of signatures in Outlook on the web. Valid values are: -- $true: Signatures are available in Outlook on the web. This is the default value. +- $true: Signatures are available in Outlook on the web. This value is the default. - $false: Signatures aren't available in Outlook on the web. ```yaml @@ -2351,7 +2351,7 @@ This parameter is functional only in Exchange Server 2010. The SilverlightEnabled parameter specifies whether a user can use Microsoft Silverlight features in Outlook Web App. Valid values are: -- $true: Silverlight features are available in Outlook Web App. This is the default value. +- $true: Silverlight features are available in Outlook Web App. This value is the default. - $false: Silverlight features aren't available in Outlook Web App. ```yaml @@ -2374,7 +2374,7 @@ This parameter is functional only in Exchange Server 2010. The SMimeEnabled parameter specifies whether users can download the S/MIME control for Outlook Web App and use it to read and compose signed and encrypted messages. Valid values are: -- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This is the default value. +- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This value is the default. - $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated. **Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://learn.microsoft.com/Exchange/policy-and-compliance/smime). @@ -2399,7 +2399,7 @@ This parameter is functional only in Exchange Server 2010. The SpellCheckerEnabled parameter specifies whether to enable or disable the built-in Outlook Web App spell checker in the full version of Outlook Web App. Valid values are: -- $true: Spell checking is available in Outlook Web App. This is the default value. +- $true: Spell checking is available in Outlook Web App. This value is the default. - $false: Spell checking isn't available in Outlook Web App. This parameter doesn't apply to the light version of Outlook Web App. @@ -2422,7 +2422,7 @@ Accept wildcard characters: False The TasksEnabled parameter specifies whether Tasks folder is available in Outlook on the web. Valid values are: -- $true: The Tasks folder is available in Outlook on the web. This is the default value. +- $true: The Tasks folder is available in Outlook on the web. This value is the default. - $false: The Tasks folder isn't available in Outlook on the web. This parameter doesn't apply to the light version of Outlook on the web. @@ -2445,7 +2445,7 @@ Accept wildcard characters: False The TextMessagingEnabled parameter specifies whether users can send and receive text messages in Outlook on the web. Valid values are: -- $true: Text messaging is available in Outlook on the web. This is the default value. +- $true: Text messaging is available in Outlook on the web. This value is the default. - $false: Text messaging isn't available in Outlook on the web. This parameter doesn't apply to the light version of Outlook on the web. @@ -2468,7 +2468,7 @@ Accept wildcard characters: False The ThemeSelectionEnabled parameter specifies whether users can change the theme in Outlook on the web. Valid values are: -- $true: Users can specify the theme in Outlook on the web. This is the default value. +- $true: Users can specify the theme in Outlook on the web. This value is the default. - $false: Users can't specify or change the theme in Outlook on the web. ```yaml @@ -2489,10 +2489,10 @@ Accept wildcard characters: False The UMIntegrationEnabled parameter specifies whether Unified Messaging (UM) integration is enabled in Outlook on the web. Valid values are: -- $true: UM integration is enabled in Outlook on the web. This is the default value. +- $true: UM integration is enabled in Outlook on the web. This value is the default. - $false: UM integration is disabled in Outlook on the web. -This setting applies only if Unified Messaging has been enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). +This setting applies only if Unified Messaging is enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). This parameter doesn't apply to the light version of Outlook on the web. @@ -2512,7 +2512,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -2530,7 +2530,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -2551,7 +2551,7 @@ Accept wildcard characters: False The UseGB18030 parameter specifies whether to use the GB18030 character set instead of GB2312 in Outlook on the web. Valid values are: - $true: GB18030 is used wherever GB2312 would have been used in Outlook on the web. -- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This is the default value. +- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2572,7 +2572,7 @@ Accept wildcard characters: False The UseISO885915 parameter specifies whether to use the character set ISO8859-15 instead of ISO8859-1 in Outlook on the web. Valid values are: - $true: ISO8859-15 is used wherever ISO8859-1 would have been used in Outlook on the web. -- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This is the default value. +- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2610,7 +2610,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: VirtualDirectoryTypes @@ -2630,7 +2630,7 @@ Accept wildcard characters: False The WacEditingEnabled parameter specifies whether to enable or disable editing documents in Outlook on the web by using Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). Valid values are: -- $true: Users can edit supported documents in Outlook on the web. This is the default value. +- $true: Users can edit supported documents in Outlook on the web. This value is the default. - $false: Users can't edit supported documents in Outlook on the web. ```yaml @@ -2651,7 +2651,7 @@ Accept wildcard characters: False The WacViewingOnPrivateComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents private computer sessions in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). By default, all Outlook on the web sessions are considered to be on private computers. Valid values are: -- $true: In private computer sessions, users can view supported Office documents in the web browser. This is the default value. +- $true: In private computer sessions, users can view supported Office documents in the web browser. This value is the default. - $false: In private computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -2674,7 +2674,7 @@ Accept wildcard characters: False The WacViewingOnPublicComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents in public computer sessions in Office Online Server. Valid values are: -- $true: In public computer sessions, users can view supported Office documents in the web browser. This is the default value. +- $true: In public computer sessions, users can view supported Office documents in the web browser. This value is the default. - $false: In public computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -2698,7 +2698,7 @@ Accept wildcard characters: False The WebPartsFrameOptionsType parameter specifies what sources can access web parts in IFRAME or FRAME elements in Outlook on the web. Valid values are: - None: There are no restrictions on displaying Outlook on the web content in a frame. -- SameOrigin: This is the default value and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. +- SameOrigin: This value is the default and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. - Deny: Blocks display of Outlook on the web content in a frame, regardless of the origin of the site attempting to access it. ```yaml @@ -2721,7 +2721,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are: -- $true: All supported attachment types are available for WebReady Document Viewing. This is the default value. +- $true: All supported attachment types are available for WebReady Document Viewing. This value is the default. - $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are available for WebReady Document Viewing (you can remove values from the lists). ```yaml @@ -2744,7 +2744,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingOnPrivateComputersEnabled parameter specifies whether WebReady Document Viewing is available in private computer sessions. Valid values are: -- $true: WebReady Document Viewing is available in private computer sessions. This is the default value. +- $true: WebReady Document Viewing is available in private computer sessions. This value is the default. - $false: WebReady Document Viewing isn't available in private computer sessions. By default in Exchange 2013, all Outlook on the web sessions are considered to be on private computers. @@ -2769,7 +2769,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingOnPublicComputersEnabled parameter specifies whether WebReady Document Viewing is in public computer sessions. Valid values are: -- $true: WebReady Document Viewing is available for public computer sessions. This is the default value. +- $true: WebReady Document Viewing is available for public computer sessions. This value is the default. - $false: WebReady Document Viewing isn't available for public computer sessions. In Exchange 2013, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -2928,7 +2928,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter enables or disables Integrated Windows authentication on the virtual directory. Valid values are: - $true: Integrated Windows authentication is enabled on the Outlook on the web virtual directory. -- $false: Integrated Windows authentication is disabled on the Outlook on the web virtual directory. This is the default value. +- $false: Integrated Windows authentication is disabled on the Outlook on the web virtual directory. This value is the default. ```yaml Type: Boolean @@ -2946,7 +2946,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -2964,7 +2964,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md index 7d756ac636..5be97a4965 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md @@ -80,7 +80,7 @@ Set-PartnerApplication [-Identity] ## DESCRIPTION You can configure partner applications such as SharePoint to access Exchange resources. Use the New-PartnerApplication cmdlet to create a partner application configuration for an application that needs 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). We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -140,7 +140,7 @@ Accept wildcard characters: False The AccountType parameter specifies the type of Microsoft account that's required for the partner application. Valid values are: -- OrganizationalAccount: This is the default value +- OrganizationalAccount: This value is the default - ConsumerAccount ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md index 406c4a2b4c..2024688f5a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md @@ -36,7 +36,7 @@ Set-PendingFederatedDomain [[-Identity] ] ## DESCRIPTION This cmdlet allows the Exchange admin center to save domains selected as the FederatedOrganizationIdentifier or federated domains when proof of domain ownership hasn't been 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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md index 49519a0178..b4bb856629 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md @@ -33,7 +33,7 @@ Set-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 @@ -132,7 +132,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Place.md b/exchange/exchange-ps/ExchangePowerShell/Set-Place.md index 0fdf11de3f..8cade9febb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Place.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Place.md @@ -53,7 +53,7 @@ Set-Place [-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 @@ -298,7 +298,7 @@ Accept wildcard characters: False The IsWheelChairAccessible parameter specifies whether the room is wheelchair accessible. Valid values are: - $true: The room is wheelchair accessible. -- $false: The room is not wheelchair accessible. This is the default value. +- $false: The room is not wheelchair accessible. This value is the default. ```yaml Type: Boolean @@ -339,7 +339,7 @@ Accept wildcard characters: False The MTREnabled parameter identifies the room as configured with a Microsoft Teams room system. You can add Teams room systems as audio sources in Teams meetings that involve the room. Valid values are: - $true: The room is has a Teams room system. You can add the Teams room system to Microsoft Teams meetings when selecting to join a meeting with room audio. -- $false: The room is does not have a Teams room system. Users will join Teams meetings using their PC or mobile device audio instead of using room audio. This is the default value. +- $false: The room is does not have a Teams room system. Users join Teams meetings using their PC or mobile device audio instead of using room audio. This value is the default. For more information about Microsoft Teams Rooms, see [Microsoft Teams Rooms](https://learn.microsoft.com/microsoftteams/rooms/). diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md index 6fac58c159..a5938c4bcd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md @@ -321,7 +321,7 @@ The EnableLabelCoauth parameter enables or disables co-authoring support in Offi Disabling co-authoring support in Office desktop apps in the organization has the following consequences: - For apps and services that support the new labeling metadata, they now revert to the original metadata format and location when labels are read or saved. -- The new metadata format and location for Office documents that was used while the setting was enabled will not be copied to the original format and location. As a result, this labeling information for unencrypted Word, Excel, and PowerPoint files will be lost. +- The new metadata format and location for Office documents used while the setting was enabled isn't copied to the original format and location. As a result, this labeling information for unencrypted Word, Excel, and PowerPoint files is lost. - Co-authoring and AutoSave no longer work in your organization for labeled and encrypted documents. - Sensitivity labels remain enabled for Office files in OneDrive and SharePoint. @@ -343,7 +343,7 @@ Accept wildcard characters: False The EnableSpoAipMigration parameter enables or disables built-in labeling for supported Office files in SharePoint and OneDrive. Valid values are: -- $true: Users can apply your sensitivity labels in Office for the web. Users will see the Sensitivity button on the ribbon so they can apply labels, and see any applied label name on the status bar. +- $true: Users can apply your sensitivity labels in Office for the web. Users see the Sensitivity button on the ribbon so they can apply labels, and see any applied label name on the status bar. - $false: Users can't apply your sensitivity labels in Office for the web. ```yaml @@ -589,7 +589,7 @@ Accept wildcard characters: False The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are: - Ignore -- RetryThenBlock (This is the default value) +- RetryThenBlock (default value) ```yaml Type: PolicyRuleErrorAction @@ -610,7 +610,7 @@ Accept wildcard characters: False The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are: -- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This is the default value. +- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default. - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). - HeaderOrEnvelope: Examine senders in the message header and the message envelope. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md index 3cd1fde963..75a9554dd4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md @@ -13,7 +13,7 @@ title: Set-PolicyTipConfig # Set-PolicyTipConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-PolicyTipConfig cmdlet to modify custom Policy Tips in your organization. You can't modify built-in Policy Tips. @@ -31,7 +31,7 @@ Set-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/Set-PopSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md index 47d9968636..0f07bd405a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md @@ -57,7 +57,7 @@ Set-PopSettings [-AuthenticatedConnectionTimeout ] ``` ## 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 @@ -96,7 +96,7 @@ Set-PopSettings -X509CertificateName mail.contoso.com This example specifies the certificate that contains mail.contoso.com is used to encrypt POP3 client connections. -**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange POP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange POP service (you'll receive an error if you try). +**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange POP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange POP service (you get an error if you try). ## PARAMETERS @@ -146,7 +146,7 @@ Accept wildcard characters: False The CalendarItemRetrievalOption parameter specifies how calendar items are presented to POP3 clients. Valid values are: -- 0 or iCalendar. This is the default value. +- 0 or iCalendar. This value is the default. - 1 or IntranetUrl. - 2 or InternetUrl. - 3 or Custom. @@ -211,7 +211,7 @@ Accept wildcard characters: False The EnableExactRFC822Size parameter specifies how message sizes are presented to POP3 clients. Valid values are: - $true: Calculate the exact message size. Because this setting can negatively affect performance, you should configure it only if it's required by your POP3 clients. -- $false: Use an estimated message size. This is the default value. +- $false: Use an estimated message size. This value is the default. ```yaml Type: Boolean @@ -231,7 +231,7 @@ Accept wildcard characters: False The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Integrated Windows authentication (NTLM) by using the Generic Security Services application programming interface (GSSAPI). This setting applies to connections where Transport Layer Security (TLS) is disabled. Valid values are: -- $true: NTLM for POP3 connections is enabled. This is the default value. +- $true: NTLM for POP3 connections is enabled. This value is the default. - $false: NTLM for POP3 connections is disabled. ```yaml @@ -253,7 +253,7 @@ Accept wildcard characters: False The EnforceCertificateErrors parameter specifies whether to enforce Secure Sockets Layer (SSL) certificate validation failures. Valid values are: - $true: If the certificate isn't valid or doesn't match the target POP3 server's FQDN, the connection attempt fails. -- $false: The server doesn't deny POP3 connections based on certificate errors. This is the default value. +- $false: The server doesn't deny POP3 connections based on certificate errors. This value is the default. ```yaml Type: Boolean @@ -273,7 +273,7 @@ Accept wildcard characters: False The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is used for POP3 connections. Valid values are: -- None: Extended Protection for Authentication isn't used. This is the default value. +- None: Extended Protection for Authentication isn't used. This value is the default. - Allow: Extended Protection for Authentication is used only if it's supported by the incoming POP3 connection. If it's not, Extended Protection for Authentication isn't used. - Require: Extended Protection for Authentication is required for all POP3 connections. If the incoming POP3 connection doesn't support it, the connection is rejected. @@ -373,8 +373,8 @@ Accept wildcard characters: False The LogFileRollOverSettings parameter defines how frequently POP3 protocol logging creates a new log file. Valid values are: -- 1 or Hourly. This is the default value in Exchange 2019 and Exchange 2016. -- 2 or Daily. This is the default value in Exchange 2013 and Exchange 2010. +- 1 or Hourly. This value is the default in Exchange 2019 and Exchange 2016. +- 2 or Daily. This value is the default in Exchange 2013 and Exchange 2010. - 3 or Weekly. - 4 or Monthly. @@ -400,7 +400,7 @@ The LoginType parameter specifies the authentication method for POP3 connections - 1 or PlainTextLogin. - 2 or PlainTextAuthentication. -- 3 or SecureLogin. This is the default value. +- 3 or SecureLogin. This value is the default. ```yaml Type: LoginOptions @@ -428,7 +428,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The default value is 0, which means a new POP3 protocol log file is created at the frequency that's specified by the LogFileRollOverSettings parameter. @@ -529,7 +529,7 @@ The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages - 2 or HtmlAndTextAlternative. - 3 or TextEnrichedOnly. - 4 or TextEnrichedAndTextAlternative. -- 5 or BestBodyFormat. This is the default value. +- 5 or BestBodyFormat. This value is the default. - 6 or Tnef. ```yaml @@ -550,7 +550,7 @@ Accept wildcard characters: False The MessageRetrievalSortOrder parameter specifies how retrieved messages are sorted. Valid values are: -- 0 or Ascending. This is the default value. +- 0 or Ascending. This value is the default. - 1 or Descending. ```yaml @@ -612,7 +612,7 @@ Accept wildcard characters: False The ProtocolLogEnabled parameter specifies whether to enable protocol logging for POP3. Valid values are: - $true: POP3 protocol logging is enabled. -- $false: POP3 protocol logging is disabled. This is the default value. +- $false: POP3 protocol logging is disabled. This value is the default. ```yaml Type: Boolean @@ -700,7 +700,7 @@ Accept wildcard characters: False The SuppressReadReceipt parameter specifies whether to stop duplicate read receipts from being sent to POP3 clients that have the Send read receipts for messages I send setting configured in their POP3 email program. Valid values are: - $true: The sender receives a read receipt only when the recipient opens the message. -- $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This is the default value. +- $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md index 552dbc3950..955bf80c98 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md @@ -41,7 +41,7 @@ Set-PowerShellVirtualDirectory [-Identity] ## DESCRIPTION Although it's possible to modify a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -84,7 +84,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. ```yaml @@ -166,7 +166,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -186,7 +186,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -207,8 +207,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -303,7 +303,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -- $true: Integrated Windows authentication is enabled. This is the default value. +- $true: Integrated Windows authentication is enabled. This value is the default. - $false: Integrated Windows authentication is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md b/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md index 5ed5a8d14e..7df4ae0f1e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md @@ -103,8 +103,8 @@ Accept wildcard characters: False The AggregationType parameter specifies the how the alert policy triggers alerts for multiple occurrences of monitored activity. Valid values are: - None: Alerts are triggered for every occurrence of the activity. -- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This is the default value. -- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). Note that it can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. +- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This value is the default. +- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). It can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. ```yaml Type: AlertAggregationType @@ -254,7 +254,7 @@ Accept wildcard characters: False The Disabled parameter enables or disables the alert policy. Valid values are: - $true: The alert policy is disabled. -- $false: The alert policy is enabled. This is the default value. +- $false: The alert policy is enabled. This value is the default. ```yaml Type: Boolean @@ -403,7 +403,7 @@ Accept wildcard characters: False The NotifyUserOnFilterMatch parameter specifies whether to trigger an alert for a single event when the alert policy is configured for aggregated activity. Valid values are: - $true: Even though the alert is configured for aggregated activity, a notification is triggered during a match for the activity (basically, an early warning). -- $false: Alerts are triggered according to the specified aggregation type. This is the default value. +- $false: Alerts are triggered according to the specified aggregation type. This value is the default. You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). @@ -443,10 +443,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications has been reached in the time period, no more notifications are sent for the alert. Valid values are: +The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications is reached in the time period, no more notifications are sent for the alert. Valid values are: - An integer. -- The value $null. This is the default value (no maximum number of notifications for an alert). +- The value $null. This value is the default (no maximum number of notifications for an alert). ```yaml Type: Int32 @@ -467,7 +467,7 @@ Accept wildcard characters: False The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are: - An integer. -- The value $null. This is the default value (no interval for notification throttling). +- The value $null. This value is the default (no interval for notification throttling). ```yaml Type: Int32 @@ -563,7 +563,7 @@ Accept wildcard characters: False The Severity parameter specifies the severity of the detection. Valid values are: -- Low (This is the default value) +- Low (default value) - Medium - High diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md index 1e20ef8860..1482cb835f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md @@ -13,7 +13,7 @@ title: Set-PublicFolder # Set-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 Set-PublicFolder cmdlet to set the attributes of public folders. @@ -52,7 +52,7 @@ Set-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 @@ -232,7 +232,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 1 through 2TB. @@ -322,7 +322,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 1 through 2GB. @@ -437,7 +437,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 1 through 2TB. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md index fd89adf4ff..a1407b777f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md @@ -49,7 +49,7 @@ Set-PublicFolderDatabase [-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 @@ -72,7 +72,7 @@ This example sets the database maintenance schedule on PFDB01 to run daily from Set-PublicFolderDatabase -RetainDeletedItemsUntilBackup $true -Identity 'PFDB01' ``` -This example prevents the deleted items in the public folder database PFDB01 from being permanently deleted until after the database has been backed up. +This example prevents the deleted items in the public folder database PFDB01 from being permanently deleted until after the database is backed up. ## PARAMETERS @@ -433,7 +433,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The ReplicationMessageSize parameter specifies the size of replication messages. Small items may be aggregated into a single replication message that can be as large as this setting, but items larger than this setting are replicated with messages larger than this size. +The ReplicationMessageSize parameter specifies the size of replication messages. Small items might be aggregated into a single replication message that can be as large as this setting, but items larger than this setting are replicated with messages larger than this size. A valid value is a number up to 2 gigabytes (2147482624 bytes). The default value is 300 kilobytes (307200 bytes). @@ -444,7 +444,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. ```yaml Type: ByteQuantifiedSize @@ -462,7 +462,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The ReplicationPeriod parameter specifies the interval at which replication of public folders or content updates may occur. +The ReplicationPeriod parameter specifies the interval at which replication of public folders or content updates might occur. ```yaml Type: UInt32 @@ -480,7 +480,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The ReplicationSchedule parameter specifies the time intervals during which replication of public folders or contents may occur. +The ReplicationSchedule parameter specifies the time intervals during which replication of public folders or contents might occur. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md index d90b6c55ed..a2c4eedfb8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md @@ -56,7 +56,7 @@ Set-PublicFolderMigrationRequest [-Identity] ## DESCRIPTION You can pipeline the Set-PublicFolderMoveRequest cmdlet from the Get-PublicFolderMoveRequestStatistics or Get-PublicFolderMoveRequest 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 @@ -222,7 +222,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md index 3a2ffa3548..bc66a72143 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md @@ -39,7 +39,7 @@ Set-QuarantinePermissions -QuarantinePermissionsObject ## DESCRIPTION To see the current value of the permissions object that you want to modify, run the variable name as a command. For example, run the command `$Perms` to see the quarantine policy permissions stored in the `$Perms` variable. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,7 +79,7 @@ Accept wildcard characters: False The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are: - $true: Allow sender is available for affected messages in quarantine. -- $false: Allow sender isn't available for affected messages in quarantine. This is the default value. +- $false: Allow sender isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -100,7 +100,7 @@ Accept wildcard characters: False The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are: - $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine. -- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This is the default value. +- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -121,7 +121,7 @@ Accept wildcard characters: False The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are: - $true: Delete messages and Delete from quarantine are available for affected messages in quarantine. -- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value. +- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -142,7 +142,7 @@ Accept wildcard characters: False The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are: - $true: The permission is enabled. -- $false: The permission is disabled. This is the default value. +- $false: The permission is disabled. This value is the default. Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. End-users can't download quarantined messages. @@ -165,7 +165,7 @@ Accept wildcard characters: False The PermissionToPreview parameter specifies whether users are allowed to preview quarantined messages. Valid values are: - $true: Preview message is available for affected messages in quarantine. -- $false: Preview message isn't available for affected messages in quarantine. This is the default value. +- $false: Preview message isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -232,7 +232,7 @@ Accept wildcard characters: False The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are: - $true: The permission is enabled. -- $false: The permission is disabled. This is the default value. +- $false: The permission is disabled. This value is the default. Currently, this value has no effect on available actions in quarantine notifications or quarantine for affected messages. View message header is always available for affected messages in quarantine. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md index 20659f9134..a80cbc375e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md @@ -52,7 +52,7 @@ Set-QuarantinePolicy [-Identity] ## DESCRIPTION You can't modify the built-in quarantine policies named AdminOnlyAccessPolicy, DefaultFullAccessPolicy, or DefaultFullAccessWithNotificationPolicy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -398,7 +398,7 @@ Accept wildcard characters: False The ESNEnabled parameter specifies whether to enable quarantine notifications (formerly known as end-user spam notifications) for the policy. Valid values are: - $true: Quarantine notifications are enabled. -- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This is the default value. +- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This value is the default. **Note**: If the value of this parameter is $true and the value of the EndUserQuarantinePermissionsValue parameter is 0 (No access where all permissions are turned off), users can view their messages in quarantine, but the only available action for the messages is **View message header**. @@ -439,7 +439,7 @@ Accept wildcard characters: False The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send quarantine notifications for quarantined messages from blocked sender addresses. Valid values are: - $true: Recipients get quarantine notifications for affected messages from blocked senders. -- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This is the default value. +- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This value is the default. ```yaml Type: Boolean @@ -536,7 +536,7 @@ Accept wildcard characters: False The OrganizationBrandingEnabled parameter enables or disables organization branding in the end-user quarantine notification messages. Valid values are: - $true: Organization branding is enabled. The default Microsoft logo that's used in quarantine notifications is replaced by your custom logo. Before you do this, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your custom logo. -- $false: Organization branding is disabled. The default Microsoft logo is used in quarantine notifications. This is the default value. +- $false: Organization branding is disabled. The default Microsoft logo is used in quarantine notifications. This value is the default. This setting is available only in the built-in quarantine policy named DefaultGlobalTag that controls global settings. To access this quarantine policy, start your command with the following syntax: `Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy | Set-QuarantinePolicy ...`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md index 26d5d4ef44..27c19d4d2b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md @@ -16,7 +16,7 @@ title: Set-RMSTemplate This cmdlet is available only in the cloud-based service. > [!NOTE] -> This cmdlet has been deprecated. If you use AD RMS with Exchange Online, you need to migrate to Azure Information Protection before you can use message encryption. For more information, see [Verify that Azure Rights Management is active](https://learn.microsoft.com/purview/set-up-new-message-encryption-capabilities#verify-that-azure-rights-management-is-active). +> This cmdlet is deprecated. If you use AD RMS with Exchange Online, you need to migrate to Azure Information Protection before you can use message encryption. For more information, see [Verify that Azure Rights Management is active](https://learn.microsoft.com/purview/set-up-new-message-encryption-capabilities#verify-that-azure-rights-management-is-active). Use the Set-RMSTemplate cmdlet to modify the properties of an existing Active Directory Rights Management Services (AD RMS) template in your organization. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md index 4e14c8daab..c84552f4b2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md @@ -83,7 +83,7 @@ Set-ReceiveConnector [-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 @@ -130,7 +130,7 @@ Accept wildcard characters: False The AdvertiseClientSettings parameter specifies whether the SMTP server name, port number, and authentication settings for the Receive connector are displayed to users in the options of Outlook on the web. Valid values are: - $true: The SMTP values are displayed in Outlook on the web. Typically, you would only use this setting for a Receive connector with the usage type Client (authenticated SMTP connections on TCP port 587 for POP3 and IMAP4 clients). -- $false: The SMTP values are displayed in Outlook on the web. This is the default value. +- $false: The SMTP values are displayed in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -182,7 +182,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019 -The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that may be abusing the connection. The default value is 5 seconds. +The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that might be abusing the connection. The default value is 5 seconds. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. @@ -231,7 +231,7 @@ Accept wildcard characters: False The BareLinefeedRejectionEnabled parameter specifies whether this Receive connector rejects messages that contain line feed (LF) characters without immediately preceding carriage return characters (CR) in the SMTP DATA stream. This condition is known as bare line feeds. Valid values are: - $true: Messages that contain bare line feeds are rejected. -- $false: Messages that contain bare line feeds aren't rejected. This is the default value. +- $false: Messages that contain bare line feeds aren't rejected. This value is the default. Although message that contain bare line feeds might be delivered successfully, these messages don't follow SMTP protocol standards and might cause problems on messaging servers. @@ -253,7 +253,7 @@ Accept wildcard characters: False The BinaryMimeEnabled parameter specifies whether the BINARYMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This is the default value. +- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This value is the default. - $false: BINARYMIME is disabled and isn't advertised in the EHLO response. The binary MIME extension is defined in RFC 3030. @@ -301,7 +301,7 @@ Accept wildcard characters: False The ChunkingEnabled parameter specifies whether the CHUNKING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: CHUNKING is enabled and is advertised in the EHLO response. This is the default value. +- $true: CHUNKING is enabled and is advertised in the EHLO response. This value is the default. - $false: CHUNKING is disabled and isn't advertised in the EHLO response. Chunking is defined in RFC 3030. @@ -443,7 +443,7 @@ Accept wildcard characters: False The DeliveryStatusNotificationEnabled parameter specifies whether the DSN (delivery status notification) Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: DSN is enabled and is advertised in the EHLO response. This is the default value. +- $true: DSN is enabled and is advertised in the EHLO response. This value is the default. - $false: DSN is disabled and isn't advertised in the EHLO response. Delivery status notifications are defined in RFC 3461. @@ -489,7 +489,7 @@ The DomainSecureEnabled parameter specifies whether to enable or disable mutual - $true: Mutual TLS authentication is enabled. - $false: Mutual TLS authentication is disabled. -Note that setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication: +Setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication: - The AuthMechanism parameter must contain the value Tls, and can't contain the value ExternalAuthoritative. - The domain that's used for mutual TLS authentication must be configured in the following locations: @@ -515,7 +515,7 @@ Accept wildcard characters: False The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: 8BITMIME is enabled and is advertised in the EHLO response. This is the default value. +- $true: 8BITMIME is enabled and is advertised in the EHLO response. This value is the default. - $false: 8BITMIME is disabled and isn't advertised in the EHLO response. 8-bit data transmission is defined in RFC 6152. @@ -561,7 +561,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable or disable the Receive connector. Valid values are: -- $true: The Receive connector is enabled. This is the default value. +- $true: The Receive connector is enabled. This value is the default. - $false: The Receive connector is disabled. ```yaml @@ -582,7 +582,7 @@ Accept wildcard characters: False The EnhancedStatusCodesEnabled parameter specifies whether the ENHANCEDSTATUSCODES Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This is the default value. +- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This value is the default. - $false: ENHANCEDSTATUSCODES is disabled and isn't advertised in the EHLO response. Enhanced status codes are defined in RFC 2034. @@ -605,9 +605,9 @@ Accept wildcard characters: False The ExtendedProtectionPolicy parameter specifies how you want to use Extended Protection for Authentication on the Receive connector.Valid values are: -- None: Extended Protection for Authentication won't be used. This is the default value. -- Allow: Extended Protection for Authentication will be used only if the connecting host supports it. Otherwise, the connections will be established without Extended Protection for Authentication. -- Require: Extended Protection for Authentication will be required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection will be rejected. +- None: Extended Protection for Authentication aren't used. This value is the default. +- Allow: Extended Protection for Authentication are used only if the connecting host supports it. Otherwise, the connections are established without Extended Protection for Authentication. +- Require: Extended Protection for Authentication is required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection is rejected. Extended Protection for Authentication enhances the protection and handling of credentials when authenticating network connections using Integrated Windows authentication. Integrated Windows authentication is also known as NTLM. We strongly recommend that you use Extended Protection for Authentication if you are using Integrated Windows authentication. @@ -657,7 +657,7 @@ Accept wildcard characters: False The LongAddressesEnabled parameter specifies whether the Receive connector accepts long X.400 email addresses. The X.400 email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. Valid values are: - $true: X.400 email addresses can be up to 1,860 characters long after IMCEA encapsulation. -- $false: The maximum length of a complete SMTP email address is 571 characters. This is the default value. +- $false: The maximum length of a complete SMTP email address is 571 characters. This value is the default. When you set this parameter to the value $true the following changes are made to the Receive connector: @@ -685,7 +685,7 @@ Accept wildcard characters: False This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. -The MaxAcknowledgementDelay parameter specifies the period the transport server delays acknowledgement when receiving messages from a host that doesn't support shadow redundancy. When receiving messages from a host that doesn't support shadow redundancy, a Microsoft Exchange Server 2010 transport server delays issuing an acknowledgement until it verifies that the message has been successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server times out and issues an acknowledgement anyway. The default value is 30 seconds. +The MaxAcknowledgementDelay parameter specifies the period the transport server delays acknowledgement when receiving messages from a host that doesn't support shadow redundancy. When receiving messages from a host that doesn't support shadow redundancy, a Microsoft Exchange Server 2010 transport server delays issuing an acknowledgement until it verifies that the message is successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server times out and issues an acknowledgement anyway. The default value is 30 seconds. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -714,7 +714,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is from 1 to 2147483647 bytes. @@ -872,7 +872,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value for this parameter is from 65536 to 2147483647 bytes. @@ -1004,7 +1004,7 @@ Accept wildcard characters: False The OrarEnabled parameter enables or disables Originator Requested Alternate Recipient (ORAR) on the Receive connector. Valid values are: - $true: ORAR is enabled and is advertised in the XORAR keyword in the EHLO response. The actual ORAR information is transmitted in the RCPT TO SMTP command. -- $false: ORAR is disabled and is isn't advertised in the EHLO response. This is the default value. +- $false: ORAR is disabled and is isn't advertised in the EHLO response. This value is the default. If the email address specified in the ORAR information is a long X.400 email address, you need to set the LongAddressesEnabled parameter to the value $true. @@ -1058,7 +1058,7 @@ Accept wildcard characters: False The PipeliningEnabled parameter specifies whether the PIPELINING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: PIPELINING is enabled and is advertised in the EHLO response. This is the default value. +- $true: PIPELINING is enabled and is advertised in the EHLO response. This value is the default. - $false: PIPELINING is disabled and isn't advertised in the EHLO response. Pipelining is defined in RFC 2920. @@ -1081,7 +1081,7 @@ Accept wildcard characters: False The ProtocolLoggingLevel parameter specifies whether to enable or disable protocol logging for the Receive connector. Valid values are: -- None: Protocol logging is disabled on the Receive connector. This is the default value. +- None: Protocol logging is disabled on the Receive connector. This value is the default. - Verbose: Protocol logging is enabled on the Receive connector. For more information about protocol logging, see [Protocol logging](https://learn.microsoft.com/Exchange/mail-flow/connectors/protocol-logging). @@ -1105,7 +1105,7 @@ Accept wildcard characters: False The RejectReservedSecondLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved second-level domains as specified in RFC 2606 (example.com, example.net, or example.org). Valid value are: - $true: RCPT TO commands that contain reserved second-level domains are rejected. -- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This is the default value. +- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1126,7 +1126,7 @@ Accept wildcard characters: False The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved top-level domains (TLDs) as specified in RFC 2606 (.test, .example, .invalid, or .localhost). Valid value are: - $true: RCPT TO commands that contain reserved TLDs are rejected. -- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This is the default value. +- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1147,7 +1147,7 @@ Accept wildcard characters: False The RejectSingleLabelRecipientDomains parameter specifies whether to reject connections that contain recipients in single-label domains (for example, chris@contoso instead of chris@contoso.com). Valid values are: - $true: RCPT TO commands that contain single-label domains are rejected. -- $false: RCPT TO commands that contain single-label domains aren't rejected. This is the default value. +- $false: RCPT TO commands that contain single-label domains aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1200,7 +1200,7 @@ Accept wildcard characters: False The RequireEHLODomain parameter specifies whether the client must provide a domain name in the EHLO handshake after the SMTP connection is established. Valid values are: - $true: The client must provide a domain name in the EHLO handshake. If it doesn't, the SMTP connection is closed. -- $false: The client isn't required to provide a domain name in the EHLO handshake. This is the default value. +- $false: The client isn't required to provide a domain name in the EHLO handshake. This value is the default. ```yaml Type: Boolean @@ -1221,7 +1221,7 @@ Accept wildcard characters: False The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are: - $true: Inbound messages on the Receive connector require TLS transmission. -- $false: Inbound messages on the Receive connector don't require TLS transmission. This is the default value. +- $false: Inbound messages on the Receive connector don't require TLS transmission. This value is the default. ```yaml Type: Boolean @@ -1259,7 +1259,7 @@ Accept wildcard characters: False The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are: -- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This is the default value. +- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This value is the default. - Disabled: SIZE is disabled and isn't advertised in the EHLO response. - EnabledwithoutValue: SIZE is enabled and is advertised in the EHLO response, but the value of the MaxMessageSize parameter isn't disclosed in the EHLO response. This setting allows messages to bypass message size checks for authenticated connections between Mailbox servers. @@ -1302,7 +1302,7 @@ Accept wildcard characters: False The SuppressXAnonymousTls parameter specifies whether the X-ANONYMOUSTLS Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: X-ANONYMOUSTLS is disabled and isn't advertised in the EHLO response. This setting also requires that you set the UseDownGradedExchangeServerAuth parameter to the value $true on the Set-TransportService cmdlet on the server. -- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This is the default value. +- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This value is the default. The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter contains the value ExchangeServer. @@ -1322,7 +1322,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The TarpitInterval parameter specifies the period of time to delay an SMTP response to a remote server that may be abusing the connection. The default value is 00:00:05 (5 seconds). +The TarpitInterval parameter specifies the period of time to delay an SMTP response to a remote server that might be abusing the connection. The default value is 00:00:05 (5 seconds). To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md index 74a5aae2c5..a2b2f7d24f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md @@ -35,7 +35,7 @@ Set-RecipientFilterConfig [-BlockedRecipients ] ``` ## 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/Set-RecordReviewNotificationTemplateConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md index 862f6a7ab6..fedde7df9c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md @@ -49,7 +49,7 @@ This example configures customized review notification text and review reminder The IsCustomizedNotificationTemplate switch specifies whether to use a customized review notification instead of the system default notification. Valid values are: - $true: Use a customized review notification. You specify the notification text using the CustomizedNotificationDataString parameter. -- $false: Use the default system notification. This is the default value. +- $false: Use the default system notification. This value is the default. ```yaml Type: Boolean @@ -70,7 +70,7 @@ Accept wildcard characters: False The IsCustomizedReminderTemplate switch specifies whether to use a customized review reminder instead of the system default reminder: - $true: Use a customized review reminder. You specify the reminder text using the CustomizedReminderDataString parameter. -- $false: Use the default system reminder. This is the default value. +- $false: Use the default system reminder. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md b/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md index 4379121dc8..1450683bf3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md @@ -47,7 +47,7 @@ The Enabled parameter specifies whether to show or hide the UI option in retenti $true: The option to mark content as a regulatory record is visible in the UI for retention label settings. -$false: The option to mark content as a regulatory record is not visible in the UI for retention label settings. This is the default value. +$false: The option to mark content as a regulatory record is not visible in the UI for retention label settings. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md index 278351fb3b..ed3e25485e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md @@ -13,7 +13,7 @@ title: Set-RemoteDomain # Set-RemoteDomain ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-RemoteDomain cmdlet to configure a managed connection for a remote domain. @@ -57,7 +57,7 @@ Set-RemoteDomain [-Identity] ## DESCRIPTION When you set a remote domain, you can control mail flow with more precision, specify message formatting and policy and specify acceptable character sets for messages sent to or received from the remote domain. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -109,7 +109,7 @@ Accept wildcard characters: False The AllowedOOFType parameter specifies the type of automatic replies or out-of-office (also known as OOF) notifications than can be sent to recipients in the remote domain. Valid values are: -- External: Only automatic replies that are designated as external are sent to recipients in the remote domain. This is the default value. +- External: Only automatic replies that are designated as external are sent to recipients in the remote domain. This value is the default. - ExternalLegacy: Only external automatic replies or automatic replies that aren't designated as internal or external are sent to recipients in the remote domain. - InternalLegacy: Only internal automatic replies or automatic replies that aren't designated as internal or external are sent to recipients in the remote domain. - None: No automatic replies are sent to recipients in the remote domain. @@ -137,8 +137,8 @@ Accept wildcard characters: False The AutoForwardEnabled parameter specifies whether to allow messages that are auto-forwarded by client email programs in your organization. Valid values are: -- $true: Auto-forwarded messages are delivered to recipients in the remote domain. This is the default value for new remote domains that you create and the built-in remote domain named Default in Exchange Online. -- $false: Auto-forwarded messages aren't delivered to recipients in the remote domain. This is the default value for the built-in remote domain named Default in on-premises Exchange. +- $true: Auto-forwarded messages are delivered to recipients in the remote domain. This value is the default for new remote domains that you create and the built-in remote domain named Default in Exchange Online. +- $false: Auto-forwarded messages aren't delivered to recipients in the remote domain. This value is the default for the built-in remote domain named Default in on-premises Exchange. ```yaml Type: Boolean @@ -158,8 +158,8 @@ Accept wildcard characters: False The AutoReplyEnabled parameter specifies whether to allow messages that are automatic replies from client email programs in your organization (for example, automatic reply messages that are generated by rules in Outlook). Valid values are: -- $true: Automatic replies are delivered to recipients in the remote domain. This is the default value for new remote domains that you create and the built-in remote domain named Default in Exchange Online. -- $false: Automatic replies aren't delivered to recipients in the remote domain. This is the default value for the built-in remote domain named Default in on-premises Exchange. +- $true: Automatic replies are delivered to recipients in the remote domain. This value is the default for new remote domains that you create and the built-in remote domain named Default in Exchange Online. +- $false: Automatic replies aren't delivered to recipients in the remote domain. This value is the default for the built-in remote domain named Default in on-premises Exchange. ```yaml Type: Boolean @@ -186,7 +186,7 @@ The ByteEncoderTypeFor7BitCharsets parameter specifies the 7-bit transfer encodi - UseBase64HtmlDetectTextPlain: Use Base64 encoding for HTML and for plain text, unless line wrapping is enabled in plain text. If line wrapping is enabled in plain text, use Base64 encoding for HTML, and use 7-bit encoding for plain text. - UseQPHtml7BitTextPlain: Always use QP encoding for HTML. Always use 7-bit encoding for plain text. - UseBase64Html7BitTextPlain: Always use Base64 encoding for HTML. Always use 7-bit encoding for plain text. -- Undefined: Always use QP encoding for HTML and plain text. This is the default value. +- Undefined: Always use QP encoding for HTML and plain text. This value is the default. ```yaml Type: ByteEncoderTypeFor7BitCharsetsEnum @@ -251,7 +251,7 @@ Accept wildcard characters: False The ContentType parameter specifies the outbound message content type and formatting. Valid values are: -- MimeHtmlText: Converts messages to MIME messages that use HTML formatting, unless the original message is a text message. If the original message is a text message, the outbound message is a MIME message that uses text formatting. This is the default value. +- MimeHtmlText: Converts messages to MIME messages that use HTML formatting, unless the original message is a text message. If the original message is a text message, the outbound message is a MIME message that uses text formatting. This value is the default. - MimeText: Converts all messages to MIME messages that use text formatting. - MimeHtml: Converts all messages to MIME messages that use HTML formatting. @@ -273,7 +273,7 @@ Accept wildcard characters: False The DeliveryReportEnabled parameter specifies whether to allow delivery reports from client software in your organization to recipients in the remote domain. Valid values are: -- $true: Delivery reports are delivered to recipients in the remote domain. This is the default value. +- $true: Delivery reports are delivered to recipients in the remote domain. This value is the default. - $false: Delivery reports aren't delivered to recipients in the remote domain. ```yaml @@ -296,7 +296,7 @@ Accept wildcard characters: False The DisplaySenderName parameter specifies whether to show the sender's Display Name in the From email address for messages sent to recipients in the remote domain. Valid values are: -- $true: Sender names are displayed in messages sent to recipients in the remote domain. This is the default value. +- $true: Sender names are displayed in messages sent to recipients in the remote domain. This value is the default. - $false. Sender names aren't displayed in messages sent to recipients in the remote domain. ```yaml @@ -342,7 +342,7 @@ This parameter is available only in Exchange Server 2010. The IsCoexistenceDomain parameter specifies whether this remote domain is used to represent your Exchange Online organization. Valid values are: - $true: The remote domain represents your Exchange Online organization. -- $false: The remote domain doesn't represent your Exchange Online organization. This is the default value. +- $false: The remote domain doesn't represent your Exchange Online organization. This value is the default. ```yaml Type: Boolean @@ -363,7 +363,7 @@ Accept wildcard characters: False The IsInternal parameter specifies whether the recipients in the remote domain are considered to be internal recipients. Valid values are: - $true: All transport components (for example, transport rules) treat recipients in the remote domain as internal recipients. Typically, you use this value in cross-forest deployments. -- $false: Recipients in the remote domain are treated as external recipients. This is the default value. +- $false: Recipients in the remote domain are treated as external recipients. This value is the default. The value of this parameter is affected by the value of the AllowedOOFType parameter, and vice-versa: @@ -406,7 +406,7 @@ Accept wildcard characters: False The MeetingForwardNotificationEnabled parameter specifies whether to enable meeting forward notifications for recipients in the remote domain. Valid values are: -- $true: Meeting requests forwarded to recipients in the remote domain generate a meeting forward notification to the meeting organizer. This is the default value. +- $true: Meeting requests forwarded to recipients in the remote domain generate a meeting forward notification to the meeting organizer. This value is the default. - $false: Meeting requests forwarded to recipients in the remote domain don't generate a meeting forward notification to the meeting organizer. ```yaml @@ -469,7 +469,7 @@ This parameter is functional only in on-premises Exchange. The NDRDiagnosticInfoEnabled parameter specifies whether diagnostic information is included in non-delivery reports (also known NDRs or bounce messages) that are sent to recipients the remote domain. Valid values are: -- $true: The diagnostic information of an NDR includes details that help administrators troubleshoot delivery problems. This detailed information includes internal server names. This is the default value. +- $true: The diagnostic information of an NDR includes details that help administrators troubleshoot delivery problems. This detailed information includes internal server names. This value is the default. - $false: The diagnostic information section in the NDR body as well as internal server headers from the attached original message headers are removed from the NDR. This parameter is meaningful only when the value of the NDREnabled parameter is $true. @@ -492,7 +492,7 @@ Accept wildcard characters: False The NDREnabled parameter specifies whether to allow non-delivery reports (also known NDRs or bounce messages) from your organization to recipients in the remote domain. Valid values are: -- $true: NDRs from your organization are sent to recipients in the remote domain. This is the default value. +- $true: NDRs from your organization are sent to recipients in the remote domain. This value is the default. - $false: NDRs from your organization aren't sent to recipients in the remote domain. ```yaml @@ -540,7 +540,7 @@ The PreferredInternetCodePageForShiftJis parameter specifies the specific code p - 50220: Use ISO-2022-JP codepage. - 50221: Use ESC-2022-JP codepage. - 50222: Use SIO-2022-JP codepage. -- Undefined: No codepage is defined. This is the default value. +- Undefined: No codepage is defined. This value is the default. ```yaml Type: PreferredInternetCodePageForShiftJisEnum @@ -560,7 +560,7 @@ Accept wildcard characters: False The RequiredCharsetCoverage parameter specifies a percentage threshold for characters in a message that must match to apply your organization's preferred character set before switching to automatic character set detection. -For example, if you set this parameter to 60, the preferred character sets will still be used during content conversion for messages that contain characters from non-preferred character sets as long as the percentage of those characters is 40 percent or less. If the percentage of characters in a message doesn't belong to preferred character sets, Exchange analyzes the Unicode characters and automatically determines the best matching character set to use. +For example, if you set this parameter to 60, the preferred character sets are still used during content conversion for messages that contain characters from non-preferred character sets as long as the percentage of those characters is 40 percent or less. If the percentage of characters in a message doesn't belong to preferred character sets, Exchange analyzes the Unicode characters and automatically determines the best matching character set to use. If recipients in the remote domain use characters that span character sets, you might want to specify a lower percentage to ensure that your organization's preferred character set is used during content conversion. @@ -603,7 +603,7 @@ Accept wildcard characters: False The TargetDeliveryDomain parameter specifies whether the remote domain is used in cross-forest deployments to generate target email addresses for new mail users that represent users in the other organization (for example, all mailboxes hosted on Exchange Online are represented as mail users in your on-premises organization). Valid values are: - $true: The remote domain is used for the target email address of mail users that represent the users in the other forest. -- $false: The remote domain isn't used for the target email address of mail users that represent the users in the other forest. This is the default value. +- $false: The remote domain isn't used for the target email address of mail users that represent the users in the other forest. This value is the default. ```yaml Type: Boolean @@ -625,7 +625,7 @@ The TNEFEnabled parameter specifies whether Transport Neutral Encapsulation Form - $true: TNEF encoding is used on all messages sent to the remote domain. - $false: TNEF encoding isn't used on any messages sent to the remote domain. -- $null (blank): TNEF encoding isn't specified for the remote domain. This is the default value. TNEF encoding for recipients in the remote domain is controlled by the value of the UseMapiRichTextFormat parameter for any mail user or mail contact objects, the sender's per-recipient settings in Outlook, or the sender's default internet message settings in Outlook +- $null (blank): TNEF encoding isn't specified for the remote domain. This value is the default. TNEF encoding for recipients in the remote domain is controlled by the value of the UseMapiRichTextFormat parameter for any mail user or mail contact objects, the sender's per-recipient settings in Outlook, or the sender's default internet message settings in Outlook ```yaml Type: Boolean @@ -645,8 +645,8 @@ Accept wildcard characters: False The TrustedMailInboundEnabled parameter specifies whether messages from senders in the remote domain are treated as trusted messages. Valid values are: -- $true: Inbound messages from senders in the remote domain are considered safe and will bypass content filtering and recipient filtering. -- $false: Inbound messages from senders in the remote domain won't bypass content filtering and recipient filtering. This is the default value. +- $true: Inbound messages from senders in the remote domain are considered safe and skip content filtering and recipient filtering. +- $false: Inbound messages from senders in the remote domain don't bypass content filtering and recipient filtering. This value is the default. ```yaml Type: Boolean @@ -666,8 +666,8 @@ Accept wildcard characters: False The TrustedMailOutboundEnabled parameter specifies whether messages sent to recipients in the remote domain are treated as trusted messages. Valid values are: -- $true: Outbound messages to recipients in the remote domain are considered safe and will bypass content filtering and recipient filtering. We recommend that you use this value in cross-forest deployments. -- $false: Outbound messages to recipients in the remote domain won't bypass content filtering and recipient filtering. This is the default value. +- $true: Outbound messages to recipients in the remote domain are considered safe and skip content filtering and recipient filtering. We recommend that you use this value in cross-forest deployments. +- $false: Outbound messages to recipients in the remote domain don't bypass content filtering and recipient filtering. This value is the default. ```yaml Type: Boolean @@ -688,7 +688,7 @@ Accept wildcard characters: False The UseSimpleDisplayName parameter specifies whether the sender's simple display name is used for the From email address in messages sent to recipients in the remote domain. Valid values are: - $true: Simple display names are used in messages sent to recipients in the remote domain. If the sender doesn't have a simple display name configured, the From email address is `EmailAddress `. -- $false: Simple display names aren't used in messages sent to recipients in the remote domain. This is the default value. +- $false: Simple display names aren't used in messages sent to recipients in the remote domain. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md index 9ddb71e508..c561807539 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md @@ -93,7 +93,7 @@ Some attributes on mailboxes in the service can only be configured by connecting Directory synchronization must be configured correctly for changes made to an on-premises mail user to be applied to a mailbox in the service. Changing the configuration of the mailbox in the service isn't immediate and depends on the directory synchronization schedule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -102,14 +102,14 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Set-RemoteMailbox -Identity davids -Type Room ``` -This example configures the mailbox in the service that's associated with the specified mail user as a room resource mailbox. This example assumes that directory synchronization has been configured. +This example configures the mailbox in the service that's associated with the specified mail user as a room resource mailbox. This example assumes that directory synchronization is configured. ### Example 2 ```powershell Set-RemoteMailbox -Identity kima -AcceptMessagesOnlyFrom davids,"Executive Team",bill@contoso.com ``` -This example configures delivery restrictions for the mailbox in the service that's associated with the specified mail user. This example assumes that directory synchronization has been configured. +This example configures delivery restrictions for the mailbox in the service that's associated with the specified mail user. This example assumes that directory synchronization is configured. ## PARAMETERS @@ -753,7 +753,7 @@ Accept wildcard characters: False The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -798,7 +798,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -822,7 +822,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -846,7 +846,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -870,7 +870,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -894,7 +894,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -933,7 +933,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -1077,7 +1077,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -1149,7 +1149,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. @@ -1181,7 +1181,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsWarningQuota value must be less than or equal to the RecoverableItemsQuota value. @@ -1394,7 +1394,7 @@ Accept wildcard characters: False The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are: - $true: The user is required to change their password the next time they log on. -- $false: The user isn't required to change their password the next time they log on. This is the default value. +- $false: The user isn't required to change their password the next time they log on. This value is the default. ```yaml Type: Boolean @@ -1412,7 +1412,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -1432,7 +1432,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md index 6b3d62ea2d..355d745fa1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md @@ -87,7 +87,7 @@ When you set the email address of the reporting mailbox in the Microsoft Defende Although it's not absolutely required, it makes sense to keep the email address consistent in the related parameters in the \*-ReportSubmissionPolicy and \*-ReportSubmissionRule 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 @@ -212,7 +212,7 @@ Accept wildcard characters: False The DisableQuarantineReportingOption parameter allows or prevents users from reporting messages in quarantine. Valid values are: - $true: Users can't report quarantined messages from quarantine. -- $false: Users can report quarantined messages from quarantine. This is the default value. +- $false: Users can report quarantined messages from quarantine. This value is the default. This parameter is meaningful only reporting in Outlook is enabled as described in the EnableReportToMicrosoft parameter. @@ -271,7 +271,7 @@ Accept wildcard characters: False The EnableCustomNotificationSender parameter specifies whether a custom sender email address is used for result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are: - $true: Use a custom Microsoft 365 sender email address. -- $false: Use the default sender email address. This is the default value. +- $false: Use the default sender email address. This value is the default. You specify the sender email address using the NotificationSenderAddress parameter. @@ -623,7 +623,7 @@ Accept wildcard characters: False The PostSubmitMessageEnabled parameter enables or disables the pop-up Outlook notifications that users see after they report messages using Microsoft reporting tools. Valid values are: -- $true: Users receive pop-up notifications in Outlook after they report messages. This is the default value. +- $true: Users receive pop-up notifications in Outlook after they report messages. This value is the default. - $false: Users don't receive pop-up notifications in Outlook after they report messages. ```yaml @@ -796,7 +796,7 @@ Accept wildcard characters: False The PreSubmitMessageEnabled parameter enables or disables the pop-up Outlook notifications that users see before they report messages using Microsoft reporting tools. Valid values are: -- $true: Users receive pop-up notifications in Outlook before they report messages. This is the default value. +- $true: Users receive pop-up notifications in Outlook before they report messages. This value is the default. - $false: Users don't receive pop-up notifications in Outlook before they report messages. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md index 68ff5bd5f9..16493b60d8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md @@ -42,7 +42,7 @@ If you set the email address of the reporting mailbox in the Microsoft Defender When you use this cmdlet to set the email address of the reporting mailbox, the corresponding parameters in the *\-ReportSubmissionPolicy cmdlets are not updated. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md index 2dd5ae09c4..5c934191af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md @@ -13,7 +13,7 @@ title: Set-ResourceConfig # Set-ResourceConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ResourceConfig cmdlet to create custom resource properties that you can add to room and equipment mailboxes. @@ -32,7 +32,7 @@ Set-ResourceConfig [-Confirm] ## DESCRIPTION After you use this cmdlet to create custom resource properties, you use the ResourceCustom parameter on the Set-Mailbox cmdlet to add one or more of those properties to a room or equipment mailbox. For more information, see the ResourceCustom parameter description in Set-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/Set-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md index 1f7c69fdab..ac27df96d6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md @@ -30,7 +30,7 @@ Set-ResubmitRequest [-Identity] -Enabled Applicable: Security & Compliance -The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: +The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. This parameter doesn't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: - IPM.Note.Microsoft.Conversation - IPM.Note.Microsoft.Conversation.Voice @@ -241,7 +241,7 @@ The ExcludedItemClasses parameter specifies the types of messages to exclude fro - IPM.Note.Microsoft.Voicemail.UM - IPM.Note.Microsoft.Voicemail.UM.CA -Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. Note that the values you specify aren't validated, so the parameter accepts any text value. +Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. The values you specify aren't validated, so the parameter accepts any text value. You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`. @@ -373,7 +373,7 @@ The RetentionDurationDisplayHint parameter specifies the units that are used to - Months - Years -For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration. You can't use this parameter for Teams retention rules. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md index 161fa3536c..be27958761 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md @@ -13,7 +13,7 @@ title: Set-RetentionPolicy # Set-RetentionPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-RetentionPolicy cmdlet to change the properties of an existing retention policy. @@ -36,7 +36,7 @@ Set-RetentionPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -138,14 +138,14 @@ This parameter is available only in the cloud-based service. The IsDefault switch specifies that this retention policy is the default retention policy. You don't need to specify a value with this switch. -When you use this switch, you'll get a warning that this retention policy will replace the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy. +When you use this switch, you get a warning that this retention policy replaces the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy. **Note**: Changing which retention policy is the default might or might not affect new and existing mailboxes based on the value of the RetentionPolicy parameter on all mailbox plans: - $null (blank): Changes to which retention policy is the default are continually reflected in new and existing mailboxes. - A retention policy is specified: The value of the RetentionPolicy parameter for all mailbox plans should be $null (blank) or match the Exchange retention policy that's configured as the default policy for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. For more information see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans). -If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value. +If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox is overwritten when changing licenses. You need to manually reset the RetentionPolicy to the original value. Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md index 5ded99737c..cb2e87b762 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md @@ -13,7 +13,7 @@ title: Set-RetentionPolicyTag # Set-RetentionPolicyTag ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-RetentionPolicyTag cmdlet to modify the properties of a retention tag. @@ -71,13 +71,13 @@ Set-RetentionPolicyTag -Mailbox ## DESCRIPTION Retention tags are used to apply message retention settings to folders and items in 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 ### Example 1 ```powershell -Set-RetentionPolicyTag "AllUsers-DeletedItems" -Comment "Items in the Deleted Items folder will be automatically deleted in 120 days" +Set-RetentionPolicyTag "AllUsers-DeletedItems" -Comment "Items in the Deleted Items folder are automatically deleted in 120 days" ``` This example changes the comment for the AllUsers-DeletedItems retention policy tag. @@ -458,7 +458,7 @@ The RetentionAction parameter specifies the action for the retention policy. Val - DeleteAndAllowRecovery: Deletes a message and allows recovery from the Recoverable Items folder. - MarkAsPastRetentionLimit: Messages are marked as past the retention limit. - MoveToArchive: Moves a message to the user's archive mailbox. You can use this action for retention tags of type All, Personal, and RecoverableItems. -- PermanentlyDelete: Permanently deletes a message. A message that has been permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox. +- PermanentlyDelete: Permanently deletes a message. A message that is permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox. The MoveToDeletedItems and MoveToFolder actions are available, but don't work. These actions are available for upgrades from messaging records management (MRM) 1.0 (managed folders) to MRM 2.0 (retention policies). MRM 2.0 was introduced in Exchange 2010 Service Pack 1 (SP1). @@ -484,7 +484,7 @@ The RetentionEnabled parameter specifies whether the tag is enabled. When set to Messages with a disabled tag are still considered tagged, so any default policy tags in the user's retention policy aren't applied to such messages. -When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users may apply this tag to items that they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later may result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it may be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_`. +When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users might apply this tag to items that they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later might result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it might be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_`. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md index a21a561bda..c7e9c8a83c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md @@ -13,7 +13,7 @@ title: Set-RoleAssignmentPolicy # Set-RoleAssignmentPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-RoleAssignmentPolicy cmdlet to modify existing management role assignment policies in your organization. @@ -37,7 +37,7 @@ You can use the Set-RoleAssignmentPolicy cmdlet to change the name of an assignm For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md index 8f7420c130..085ea64b34 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md @@ -13,7 +13,7 @@ title: Set-RoleGroup # Set-RoleGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-RoleGroup cmdlet to modify who can add or remove members to or from management role groups or change the name of the role group. @@ -58,7 +58,7 @@ If the ManagedBy property is populated with role group managers, the user config For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md index 51433e0ed4..da642097c4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md @@ -40,7 +40,7 @@ The Set-RoutingGroupConnector cmdlet modifies the properties of an existing rout The Exchange 2003 source servers specified in this cmdlet are automatically added to the ExchangeLegacyInterop universal security group. By default, the Exchange 2010 system grants Send to and Receive from permissions on the Hub Transport servers to members of this group. The source and target servers must be computers that have the Exchange 2010 Hub Transport server role installed, or Exchange 2003 bridgehead servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md index e421b16986..0a9bafb950 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md @@ -38,7 +38,7 @@ Outlook 2007 isn't supported in Exchange 2016 or later, so you shouldn't see Out To block Outlook versions for specific mailboxes, use the Set-CASMailbox 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 @@ -99,7 +99,7 @@ You can specify ranges. For example, -13.32767.65535, 14.0.0-14.32767.65535, or You can specify multiple individual values or range values separated by semicolons (;). -Be careful when you restrict client access, because Exchange server components might also use RPC to log on. Some components may report their client version as a text string, while others may report the Exchange build number. Monitor the RPC Client Access log to see the client versions that are connecting to your Exchange server before you block any client versions. +Be careful when you restrict client access, because Exchange server components might also use RPC to log on. Some components might report their client version as a text string, while others might report the Exchange build number. Monitor the RPC Client Access log to see the client versions that are connecting to your Exchange server before you block any client versions. ```yaml Type: String @@ -158,7 +158,7 @@ Accept wildcard characters: False The EncryptionRequired parameter specifies whether encryption is required for RPC client connections. Valid values are: -- $true: Unencrypted RPC client connections are rejected. This is the default value. +- $true: Unencrypted RPC client connections are rejected. This value is the default. - $false: Unencrypted RPC client connections are allowed. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md index 8ad4ecd46d..a68c77dc14 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md @@ -39,7 +39,7 @@ Safe Attachments is a feature in Microsoft Defender for Office 365 that opens em A safe attachment policy can be assigned to only one safe attachment rule by using the SafeAttachmentPolicy parameter on the New-SafeAttachmentRule or Set-SafeAttachmentRule 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 @@ -83,7 +83,7 @@ Accept wildcard characters: False The Action parameter specifies the action for the safe attachment policy. Valid values are: - Allow: Deliver the message if malware is detected in the attachment and track scanning results. This value corresponds to **Monitor** for the **Safe Attachments unknown malware response** property of the policy in the Microsoft Defender portal. -- Block: Block the email message that contains the malware attachment. This is the default value. +- Block: Block the email message that contains the malware attachment. This value is the default. - DynamicDelivery: Deliver the email message with a placeholder for each email attachment. The placeholder remains until a copy of the attachment is scanned and determined to be safe. For more information, see [Dynamic Delivery in Safe Attachments policies](https://learn.microsoft.com/defender-office-365/safe-attachments-about#dynamic-delivery-in-safe-attachments-policies). The value of this parameter is meaningful only when the value of the Enable parameter is $true (the default value is $false). @@ -150,7 +150,7 @@ Accept wildcard characters: False The Enable parameter works with the Action parameter to specify the action for the safe attachment policy. Valid values are: - $true: The Action parameter specifies the action for the safe attachment policy. -- $false: This is the default value. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. $false corresponds to the value **Off** for the **Safe Attachments unknown malware response** setting of the complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell). +- $false: This value is the default. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. $false corresponds to the value **Off** for the **Safe Attachments unknown malware response** setting of the complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell). To enable or disable an existing Safe Attachments policy, use the Enable-SafeAttachmentRule or Disable-SafeAttachmentRule cmdlets. @@ -201,7 +201,7 @@ Accept wildcard characters: False The Redirect parameter specifies whether to deliver messages to an alternate email address if malware is detected in an attachment. Valid values are: - $true: Messages that contain malware attachments are delivered to the email address specified by the RedirectAddress parameter. This value is meaningful only when the value of the Action parameter is Allow. -- $false: Messages that contain malware attachments aren't delivered to another email address. This is the default value. +- $false: Messages that contain malware attachments aren't delivered to another email address. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md index 20758a7322..593ee7140c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md @@ -46,7 +46,7 @@ A safe attachment policy can be assigned only to one safe attachment rule. > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Safe Attachments policy settings](https://learn.microsoft.com/defender-office-365/safe-attachments-about#safe-attachments-policy-settings). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md index da0d2e61a6..828b4ef04b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md @@ -45,7 +45,7 @@ Set-SafeLinksPolicy [-Identity] ## DESCRIPTION Safe Links is a feature in Microsoft Defender for Office 365 that checks links to see if they lead to malicious web sites. When a user clicks a link, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -166,7 +166,7 @@ Accept wildcard characters: False The DeliverMessageAfterScan parameter specifies whether to deliver email messages only after Safe Links scanning is complete. Valid values are: -- $true: Wait until Safe Links scanning is complete before delivering the message. This is the default value. Messages that contain malicious links are not delivered. +- $true: Wait until Safe Links scanning is complete before delivering the message. This value is the default. Messages that contain malicious links are not delivered. - $false: If Safe Links scanning can't complete, deliver the message anyway. ```yaml @@ -232,7 +232,7 @@ Accept wildcard characters: False The EnableForInternalSenders parameter specifies whether the Safe Links policy is applied to messages sent between internal senders and internal recipients within the same Exchange Online organization. Valid values are: -- $true: The policy is applied to internal and external senders. This is the default value. +- $true: The policy is applied to internal and external senders. This value is the default. - $false: The policy is applied only to external senders. ```yaml @@ -254,7 +254,7 @@ Accept wildcard characters: False The EnableOrganizationBranding parameter specifies whether your organization's logo is displayed on Safe Links warning and notification pages. Valid values are: - $true: Organization branding is displayed on Safe Links warning and notification pages. Before you configure this value, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your company logo. -- $false: Organization branding is not displayed on Safe Links warning and notification pages. This is the default value. +- $false: Organization branding is not displayed on Safe Links warning and notification pages. This value is the default. ```yaml Type: Boolean @@ -274,7 +274,7 @@ Accept wildcard characters: False The EnableSafeLinksForEmail parameter specifies whether to enable Safe Links protection for email messages. Valid values are: -- $true: Safe Links is enabled for email. This is the default value. When a user clicks a link in an email, the link will be checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links is enabled for email. This value is the default. When a user clicks a link in an email, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for email. ```yaml @@ -295,10 +295,10 @@ Accept wildcard characters: False The EnableSafeLinksForOffice parameter specifies whether to enable Safe Links protection for supported Office desktop, mobile, or web apps. Valid values are: -- $true: Safe Links scanning is enabled in Office apps. This is the default value. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links scanning is enabled in Office apps. This value is the default. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for Office apps. -Note that this protection applies to links in Office documents, not links in email messages. +This protection applies to links in Office documents, not links in email messages. ```yaml Type: Boolean @@ -318,7 +318,7 @@ Accept wildcard characters: False The EnableSafeLinksForTeams parameter specifies whether Safe Links is enabled for Microsoft Teams. Valid values are: -- $true: Safe Links is enabled for Teams. This is the default value. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links is enabled for Teams. This value is the default. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for Teams. ```yaml @@ -339,7 +339,7 @@ Accept wildcard characters: False The ScanUrls parameter specifies whether to enable or disable real-time scanning of clicked links in email messages. Valid values are: -- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This is the default value. +- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This value is the default. - $false: Real-time scanning of clicked links, including links that point to files, is disabled. ```yaml @@ -360,7 +360,7 @@ Accept wildcard characters: False The TrackClicks parameter specifies whether to track user clicks related to Safe Links protection of links. Valid values are: -- $true: User clicks are tracked. This is the default value. +- $true: User clicks are tracked. This value is the default. - $false: User clicks aren't tracked. ```yaml @@ -382,7 +382,7 @@ Accept wildcard characters: False The UseTranslatedNotificationText specifies whether to use Microsoft Translator to automatically localize the custom notification text that you specified with the CustomNotificationText parameter. Valid values are: - $true: Translate custom notification text to the user's language. -- $false: Don't translate custom notification text to the user's language. This is the default value. +- $false: Don't translate custom notification text to the user's language. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md index 44a150694c..99b959c1d1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md @@ -44,7 +44,7 @@ Safe Links is a feature in Microsoft Defender for Office 365 that checks links i > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Recipient filters in Safe Links policies](https://learn.microsoft.com/defender-office-365/safe-links-about#recipient-filters-in-safe-links-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md index 66cb53e178..71bbfc94b9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md @@ -34,7 +34,7 @@ Set-SearchDocumentFormat [-Identity] -Enabled ## DESCRIPTION Exchange Search includes built-in support for indexing many file formats. If you disable indexing for a supported file format, items containing an attachment of that file type aren't considered unsearchable. When you perform an [In-Place eDiscovery search in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and you select the option to include unsearchable items, only items that are actually unsearchable are returned. Items that weren't searched because the associated file format is set as unsearchable aren't 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/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md index eda358df5f..8e454b0d26 100644 --- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md +++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md @@ -684,9 +684,6 @@ Accept wildcard characters: False > Applicable: Microsoft Teams ->[!NOTE] ->This feature has not been released yet and will have no changes if it is enabled or disabled. - Allows users to use real time text during a call, allowing them to communicate by typing their messages in real time. Possible Values: diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md index eeb72afd3f..de4222da63 100644 --- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md +++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md @@ -1602,9 +1602,6 @@ Accept wildcard characters: False > Applicable: Microsoft Teams ->[!NOTE] ->This feature has not been released yet and will have no changes if it is enabled or disabled. - Allows users to use real time text during a meeting, allowing them to communicate by typing their messages in real time. Possible Values: diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md index 1d0d11adb7..240f14ab0c 100644 --- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md +++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md @@ -687,9 +687,6 @@ Accept wildcard characters: False > Applicable: Microsoft Teams ->[!NOTE] ->This feature has not been released yet and will have no changes if it is enabled or disabled. - Allows users to use real time text during a call, allowing them to communicate by typing their messages in real time. Possible Values: diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md index d250f0f641..8ae549b548 100644 --- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md +++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md @@ -1655,9 +1655,6 @@ Accept wildcard characters: False > Applicable: Microsoft Teams ->[!NOTE] ->This feature has not been released yet and will have no changes if it is enabled or disabled. - Allows users to use real time text during a meeting, allowing them to communicate by typing their messages in real time. Possible Values: