From 7bb4df1e269ea5a14f0dfc8eb9c36e1781650037 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Wed, 6 Aug 2025 10:11:13 -0700 Subject: [PATCH] Acrolinx 13 --- .../ExchangePowerShell/Set-ADSite.md | 7 +- .../ExchangePowerShell/Set-ADSiteLink.md | 4 +- .../Set-ATPBuiltInProtectionRule.md | 2 +- .../Set-ATPProtectionPolicyRule.md | 2 +- .../ExchangePowerShell/Set-AntiPhishPolicy.md | 44 ++++----- .../ExchangePowerShell/Set-AntiPhishRule.md | 2 +- .../exchange-ps/ExchangePowerShell/Set-App.md | 14 +-- .../Set-AppRetentionCompliancePolicy.md | 8 +- .../Set-AppRetentionComplianceRule.md | 6 +- .../Set-ApplicationAccessPolicy.md | 2 +- .../ExchangePowerShell/Set-ArcConfig.md | 2 +- .../Set-AtpPolicyForO365.md | 10 +-- .../Set-AttachmentFilterListConfig.md | 2 +- .../ExchangePowerShell/Set-AuthConfig.md | 4 +- .../ExchangePowerShell/Set-AuthRedirect.md | 4 +- .../ExchangePowerShell/Set-AuthServer.md | 8 +- .../Set-AuthenticationPolicy.md | 6 +- .../Set-AutoSensitivityLabelPolicy.md | 10 +-- .../Set-AutoSensitivityLabelRule.md | 10 +-- .../Set-AutodiscoverVirtualDirectory.md | 20 ++--- .../Set-AvailabilityConfig.md | 4 +- .../Set-AvailabilityReportOutage.md | 2 +- .../ExchangePowerShell/Set-CASMailbox.md | 68 +++++++------- .../ExchangePowerShell/Set-CASMailboxPlan.md | 6 +- .../Set-CalendarNotification.md | 14 +-- .../Set-CalendarProcessing.md | 60 ++++++------- .../ExchangePowerShell/Set-CaseHoldPolicy.md | 2 +- .../ExchangePowerShell/Set-CaseHoldRule.md | 2 +- .../Set-ClassificationRuleCollection.md | 4 +- .../Set-ClientAccessArray.md | 2 +- .../Set-ClientAccessRule.md | 4 +- .../Set-ClientAccessServer.md | 8 +- .../Set-ClientAccessService.md | 2 +- .../ExchangePowerShell/Set-Clutter.md | 4 +- .../Set-CmdletExtensionAgent.md | 2 +- .../Set-ComplianceRetentionEventType.md | 2 +- .../Set-ComplianceSearch.md | 14 +-- .../Set-ComplianceSearchAction.md | 2 +- .../Set-ComplianceSecurityFilter.md | 2 +- .../ExchangePowerShell/Set-Contact.md | 10 +-- .../Set-ContentFilterConfig.md | 18 ++-- .../Set-DataClassification.md | 4 +- .../Set-DataEncryptionPolicy.md | 4 +- .../Set-DatabaseAvailabilityGroup.md | 8 +- .../Set-DatabaseAvailabilityGroupNetwork.md | 2 +- .../Set-DefaultTenantBriefingConfig.md | 2 +- .../Set-DeliveryAgentConnector.md | 2 +- .../ExchangePowerShell/Set-DetailsTemplate.md | 2 +- .../Set-DeviceConditionalAccessPolicy.md | 2 +- .../Set-DeviceConditionalAccessRule.md | 90 +++++++++---------- .../Set-DeviceConfigurationPolicy.md | 2 +- .../Set-DeviceConfigurationRule.md | 88 +++++++++--------- .../Set-DeviceTenantPolicy.md | 2 +- .../Set-DistributionGroup.md | 46 +++++----- .../Set-DkimSigningConfig.md | 8 +- .../Set-DlpCompliancePolicy.md | 6 +- .../Set-DlpComplianceRule.md | 22 ++--- .../ExchangePowerShell/Set-DlpPolicy.md | 4 +- .../Set-DlpSensitiveInformationType.md | 4 +- .../Set-DynamicDistributionGroup.md | 36 ++++---- .../Set-EOPProtectionPolicyRule.md | 2 +- .../Set-EcpVirtualDirectory.md | 18 ++-- .../Set-EdgeSyncServiceConfig.md | 8 +- .../Set-EmailAddressPolicy.md | 6 +- .../Set-EmailTenantSettings.md | 2 +- .../ExchangePowerShell/Set-EventLogLevel.md | 2 +- .../Set-EventsFromEmailConfiguration.md | 22 ++--- .../Set-ExchangeAssistanceConfig.md | 4 +- .../ExchangePowerShell/Set-ExchangeFeature.md | 2 +- .../ExchangePowerShell/Set-ExchangeServer.md | 4 +- .../Set-ExchangeSettings.md | 2 +- .../Set-ExoPhishSimOverrideRule.md | 2 +- .../Set-ExoSecOpsOverrideRule.md | 2 +- .../Set-ExternalInOutlook.md | 2 +- .../Set-FederatedOrganizationIdentifier.md | 4 +- .../ExchangePowerShell/Set-FederationTrust.md | 2 +- .../ExchangePowerShell/Set-FocusedInbox.md | 4 +- .../Set-ForeignConnector.md | 12 +-- .../Set-FrontendTransportService.md | 30 +++---- .../Set-GlobalAddressList.md | 4 +- .../ExchangePowerShell/Set-Group.md | 8 +- .../Set-HoldCompliancePolicy.md | 4 +- .../Set-HoldComplianceRule.md | 4 +- .../Set-HostedConnectionFilterPolicy.md | 5 +- .../Set-HostedContentFilterPolicy.md | 74 +++++++-------- .../Set-HostedContentFilterRule.md | 2 +- .../Set-HostedOutboundSpamFilterPolicy.md | 14 +-- .../Set-HostedOutboundSpamFilterRule.md | 2 +- .../Set-HybridConfiguration.md | 8 +- .../Set-IRMConfiguration.md | 32 +++---- .../ExchangePowerShell/Set-ImapSettings.md | 30 +++---- .../Set-InboundConnector.md | 18 ++-- .../ExchangePowerShell/Set-InboxRule.md | 14 +-- .../Set-IntraOrganizationConnector.md | 8 +- .../ExchangePowerShell/Set-JournalRule.md | 4 +- .../ExchangePowerShell/Set-Label.md | 2 +- .../ExchangePowerShell/Set-LabelPolicy.md | 2 +- 97 files changed, 550 insertions(+), 548 deletions(-) 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-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"}`