From 386d36a6e636ca75e7e425c49721e9fb666732a8 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Wed, 6 Aug 2025 10:21:01 -0700 Subject: [PATCH] Acrolinx 14 --- .../ExchangePowerShell/Set-LinkedUser.md | 2 +- .../Set-M365DataAtRestEncryptionPolicy.md | 6 +- ...365DataAtRestEncryptionPolicyAssignment.md | 2 +- .../ExchangePowerShell/Set-MailContact.md | 36 +-- .../Set-MailPublicFolder.md | 28 +-- .../ExchangePowerShell/Set-MailUser.md | 46 ++-- .../ExchangePowerShell/Set-Mailbox.md | 138 ++++++------ .../Set-MailboxAuditBypassAssociation.md | 6 +- .../Set-MailboxAutoReplyConfiguration.md | 16 +- .../Set-MailboxCalendarConfiguration.md | 56 ++--- .../Set-MailboxCalendarFolder.md | 14 +- .../ExchangePowerShell/Set-MailboxDatabase.md | 50 ++-- .../Set-MailboxDatabaseCopy.md | 6 +- .../Set-MailboxExportRequest.md | 10 +- .../Set-MailboxFolderPermission.md | 14 +- .../Set-MailboxIRMAccess.md | 2 +- .../Set-MailboxImportRequest.md | 12 +- .../Set-MailboxJunkEmailConfiguration.md | 10 +- .../Set-MailboxMessageConfiguration.md | 32 +-- .../ExchangePowerShell/Set-MailboxPlan.md | 24 +- .../Set-MailboxRegionalConfiguration.md | 8 +- .../Set-MailboxRestoreRequest.md | 12 +- .../ExchangePowerShell/Set-MailboxSearch.md | 20 +- .../Set-MailboxSentItemsConfiguration.md | 6 +- .../ExchangePowerShell/Set-MailboxServer.md | 107 ++++----- .../Set-MailboxSpellingConfiguration.md | 4 +- .../Set-MailboxTransportService.md | 34 +-- .../Set-MalwareFilterPolicy.md | 24 +- .../Set-MalwareFilterRule.md | 4 +- .../Set-MalwareFilteringServer.md | 6 +- .../Set-ManagedContentSettings.md | 2 +- .../ExchangePowerShell/Set-ManagedFolder.md | 4 +- .../Set-ManagedFolderMailboxPolicy.md | 2 +- .../Set-ManagementRoleAssignment.md | 4 +- .../Set-ManagementRoleEntry.md | 6 +- .../ExchangePowerShell/Set-ManagementScope.md | 6 +- .../Set-MapiVirtualDirectory.md | 10 +- .../Set-MessageClassification.md | 12 +- .../ExchangePowerShell/Set-MigrationBatch.md | 30 +-- .../ExchangePowerShell/Set-MigrationConfig.md | 4 +- .../Set-MigrationEndpoint.md | 8 +- .../ExchangePowerShell/Set-MigrationUser.md | 14 +- .../Set-MobileDeviceMailboxPolicy.md | 8 +- .../ExchangePowerShell/Set-MoveRequest.md | 22 +- .../ExchangePowerShell/Set-Notification.md | 6 +- .../Set-OMEConfiguration.md | 12 +- .../Set-OMEMessageRevocation.md | 10 +- .../Set-OabVirtualDirectory.md | 16 +- .../Set-OfflineAddressBook.md | 10 +- .../Set-OnPremisesOrganization.md | 6 +- .../Set-OrganizationConfig.md | 137 +++++------ .../Set-OrganizationRelationship.md | 26 +-- .../Set-OutboundConnector.md | 28 +-- .../ExchangePowerShell/Set-OutlookAnywhere.md | 24 +- .../Set-OutlookProtectionRule.md | 4 +- .../ExchangePowerShell/Set-OutlookProvider.md | 4 +- .../Set-OwaMailboxPolicy.md | 213 +++++++++--------- .../Set-OwaVirtualDirectory.md | 188 ++++++++-------- .../Set-PartnerApplication.md | 4 +- .../Set-PendingFederatedDomain.md | 2 +- .../Set-PhishSimOverridePolicy.md | 4 +- .../ExchangePowerShell/Set-Place.md | 6 +- .../ExchangePowerShell/Set-PolicyConfig.md | 8 +- .../ExchangePowerShell/Set-PolicyTipConfig.md | 4 +- .../ExchangePowerShell/Set-PopSettings.md | 30 +-- .../Set-PowerShellVirtualDirectory.md | 14 +- .../ExchangePowerShell/Set-ProtectionAlert.md | 16 +- .../ExchangePowerShell/Set-PublicFolder.md | 10 +- .../Set-PublicFolderDatabase.md | 12 +- .../Set-PublicFolderMigrationRequest.md | 6 +- .../Set-PublicFolderMoveRequest.md | 6 +- .../Set-QuarantinePermissions.md | 14 +- .../Set-QuarantinePolicy.md | 8 +- .../ExchangePowerShell/Set-RMSTemplate.md | 2 +- .../Set-ReceiveConnector.md | 58 ++--- .../Set-RecipientFilterConfig.md | 2 +- ...-RecordReviewNotificationTemplateConfig.md | 4 +- .../Set-RegulatoryComplianceUI.md | 2 +- .../ExchangePowerShell/Set-RemoteDomain.md | 50 ++-- .../ExchangePowerShell/Set-RemoteMailbox.md | 32 +-- .../Set-ReportSubmissionPolicy.md | 10 +- .../Set-ReportSubmissionRule.md | 2 +- .../ExchangePowerShell/Set-ResourceConfig.md | 4 +- .../ExchangePowerShell/Set-ResubmitRequest.md | 2 +- .../Set-RetentionCompliancePolicy.md | 12 +- .../Set-RetentionComplianceRule.md | 6 +- .../ExchangePowerShell/Set-RetentionPolicy.md | 8 +- .../Set-RetentionPolicyTag.md | 10 +- .../Set-RoleAssignmentPolicy.md | 4 +- .../ExchangePowerShell/Set-RoleGroup.md | 4 +- .../Set-RoutingGroupConnector.md | 2 +- .../ExchangePowerShell/Set-RpcClientAccess.md | 6 +- .../Set-SafeAttachmentPolicy.md | 8 +- .../Set-SafeAttachmentRule.md | 2 +- .../ExchangePowerShell/Set-SafeLinksPolicy.md | 22 +- .../ExchangePowerShell/Set-SafeLinksRule.md | 2 +- .../Set-SearchDocumentFormat.md | 2 +- 97 files changed, 977 insertions(+), 974 deletions(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md index 63c3c474f2..5b19885817 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md @@ -32,7 +32,7 @@ Set-LinkedUser [-Identity] ## DESCRIPTION The OLSync service account is the only linked user in your organization. By default, the account is named GALSync-ServiceAccount. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md index ef3f52b177..4d44abfb09 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md @@ -46,7 +46,7 @@ Set-M365DataAtRestEncryptionPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -62,7 +62,7 @@ This example disabled the Microsoft 365 data-at-rest encryption policy named Ten Set-M365DataAtRestEncryptionPolicy -Identity "Tenant Default Policy" -Refresh ``` -This example updates the Microsoft 365 data-at-rest encryption policy named Tenant Default Policy after one of the associated keys has been rotated in the Azure Key Vault. +This example updates the Microsoft 365 data-at-rest encryption policy named Tenant Default Policy after one of the associated keys is rotated in the Azure Key Vault. ## PARAMETERS @@ -151,7 +151,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md index b33473efcb..321d855a48 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md @@ -26,7 +26,7 @@ Set-M365DataAtRestEncryptionPolicyAssignment -DataEncryptionPolicy ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -367,7 +367,7 @@ This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: -- $true: A DTMF map is created for the recipient. This is the default value. +- $true: A DTMF map is created for the recipient. This value is the default. - $false: A DTMF map isn't created for the recipient. ```yaml @@ -737,7 +737,7 @@ This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -762,7 +762,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -786,7 +786,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -810,7 +810,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -834,7 +834,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -858,7 +858,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -956,7 +956,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -1001,7 +1001,7 @@ Accept wildcard characters: False The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: -- BinHex (This is the default value) +- BinHex (default value) - UuEncode - AppleSingle - AppleDouble @@ -1087,7 +1087,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited. @@ -1146,7 +1146,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited. @@ -1174,7 +1174,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -1200,7 +1200,7 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text -- Mime (This is the default value) +- Mime (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -1259,7 +1259,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -1537,7 +1537,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -1642,7 +1642,7 @@ Accept wildcard characters: False The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are: - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact. -- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. +- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md index 7b5cf8c9e7..08ae62604e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md @@ -13,7 +13,7 @@ title: Set-MailPublicFolder # Set-MailPublicFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailPublicFolder cmdlet to configure the mail-related settings of mail-enabled public folders. If you want to configure basic settings that aren't mail-related, use the Set-PublicFolder cmdlet. @@ -91,7 +91,7 @@ Set-MailPublicFolder [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -791,7 +791,7 @@ Accept wildcard characters: False The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -834,7 +834,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -858,7 +858,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -882,7 +882,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -906,7 +906,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -930,7 +930,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1038,7 +1038,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -1082,7 +1082,7 @@ Accept wildcard characters: False The IgnoreMissingFolderLink parameter specifies whether to exclude the mail-enabled public folder from a specific validation check that's used during a public folder migration. Valid values are: - $true: Skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the public folder is ignored, and the public folder migration can continue. -- $false: Don't skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the entire public folder migration will fail. This is the default value. +- $false: Don't skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the entire public folder migration will fail. This value is the default. ```yaml Type: Boolean @@ -1158,7 +1158,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -1189,7 +1189,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -1245,7 +1245,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -1494,7 +1494,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md index ffe35144e9..8ecd9e7617 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md @@ -13,7 +13,7 @@ title: Set-MailUser # Set-MailUser ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailUser cmdlet to modify mail users. Mail users (also known as mail-enabled users) have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. @@ -945,7 +945,7 @@ Set-MailUser [-Identity] [-UnblockForwardSyncPostCrossTena ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -954,7 +954,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Set-MailUser -Identity "John Woods" -ExternalEmailAddress john@tailspintoys.com ``` -This example modifies the external email address for the mail user named John Woods. Note that the original external email address isn't kept as a proxy address. +This example modifies the external email address for the mail user named John Woods. The original external email address isn't kept as a proxy address. ## PARAMETERS @@ -1257,7 +1257,7 @@ This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: -- $true: A DTMF map is created for the recipient. This is the default value. +- $true: A DTMF map is created for the recipient. This value is the default. - $false: A DTMF map isn't created for the recipient. ```yaml @@ -1653,7 +1653,7 @@ This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -1764,7 +1764,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1788,7 +1788,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1812,7 +1812,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1836,7 +1836,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1860,7 +1860,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -1978,7 +1978,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -2103,7 +2103,7 @@ Accept wildcard characters: False The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: -- BinHex (This is the default value) +- BinHex (default value) - UuEncode - AppleSingle - AppleDouble @@ -2207,7 +2207,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -2238,7 +2238,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits). @@ -2264,7 +2264,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -2290,7 +2290,7 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text -- Mime (This is the default value) +- Mime (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -2369,7 +2369,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -2515,7 +2515,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 30 gigabytes (32212254720 bytes). @@ -2549,7 +2549,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 20 gigabytes (21474836480 bytes). @@ -2890,7 +2890,7 @@ This parameter is available only in the cloud-based service. The ResetPasswordOnNextLogon parameter allows users to require themselves to change their password the next time they log on. Valid values are: - $true: The user is required to change their password then next time they successfully log on. -- $false: The user isn't required to change their password then next time they successfully log on. This is the default value. +- $false: The user isn't required to change their password then next time they successfully log on. This value is the default. You can't use this parameter to require another user to change their password (the parameter is available only via the MyBaseOptions user role). You need to use the ForceChangePasswordNextSignIn value in the PasswordProfile parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. @@ -2912,7 +2912,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -2972,7 +2972,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -3117,7 +3117,7 @@ Accept wildcard characters: False The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are: - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact. -- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. +- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md index b4a48bfc93..0af9d1bc47 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md @@ -13,7 +13,7 @@ title: Set-Mailbox # Set-Mailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-Mailbox cmdlet to modify the settings of existing mailboxes. @@ -1124,7 +1124,7 @@ Set-Mailbox [-Identity] ## DESCRIPTION You can use this cmdlet for one mailbox at a time. To perform bulk management, you can pipeline the output of various Get- cmdlets (for example, the Get-Mailbox or Get-User cmdlets) and configure several mailboxes in a single-line command. You can also use the Set-Mailbox cmdlet in scripts. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -1418,7 +1418,7 @@ This parameter is available only in on-premises Exchange. The AntispamBypassEnabled parameter specifies whether to skip anti-spam processing on the mailbox. Valid values are: - $true: Anti-spam processing is skipped on the mailbox. -- $false: Anti-spam processing occurs on the mailbox. This is the default value +- $false: Anti-spam processing occurs on the mailbox. This value is the default ```yaml Type: Boolean @@ -1597,7 +1597,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The ArchiveQuota value must be greater than or equal to the ArchiveWarningQuota value. @@ -1649,7 +1649,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The ArchiveWarningQuota value must be less than or equal to the ArchiveQuota value. @@ -1698,7 +1698,7 @@ The AuditAdmin parameter specifies the mailbox operations to log for administrat - Create (Enabled by default.) - FolderBind (Enabled by default in on-premises Exchange 2010 or later.) - HardDelete (Enabled by default.) -- MessageBind (This has been deprecated in the cloud-based service.) +- MessageBind (This is deprecated in the cloud-based service.) - ModifyFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - Move (Enabled by default in on-premises Exchange 2010 or later.) - MoveToDeletedItems (Enabled by default.) @@ -1779,7 +1779,7 @@ Accept wildcard characters: False The AuditEnabled parameter specifies whether to enable or disable mailbox audit logging for the mailbox. If auditing is enabled, actions specified in the AuditAdmin, AuditDelegate, and AuditOwner parameters are logged. Valid values are: - $true: Mailbox audit logging is enabled. -- $false: Mailbox audit logging is disabled. This is the default value. +- $false: Mailbox audit logging is disabled. This value is the default. **Note**: In Exchange Online, mailbox auditing on by default was enabled for all organizations in January, 2019. For more information, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes). @@ -1847,7 +1847,7 @@ Accept wildcard characters: False The AuditOwner parameter specifies the mailbox operations to log for mailbox owners as part of mailbox audit logging. Valid values include: -- None (This is the default value in Exchange 2010, Exchange 2013, and Exchange 2016.) +- None (This value is the default in Exchange 2010, Exchange 2013, and Exchange 2016.) - AddFolderPermissions (Available only in Exchange 2019 and the cloud-based service.) - ApplyRecord (Available only in the cloud-based service.) - Create @@ -1959,7 +1959,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the RecoverableItemsQuota parameter. @@ -1984,7 +1984,7 @@ Accept wildcard characters: False The CalendarRepairDisabled parameter specifies whether to prevent calendar items in the mailbox from being repaired by the Calendar Repair Assistant. Valid values are: - $true: The Calendar Repair Assistant doesn't repair calendar items in the mailbox. -- $false: The Calendar Repair Assistant repairs calendars items in the mailbox. This is the default value. +- $false: The Calendar Repair Assistant repairs calendars items in the mailbox. This value is the default. ```yaml Type: Boolean @@ -2005,7 +2005,7 @@ Accept wildcard characters: False The CalendarVersionStoreDisabled parameter specifies whether to prevent calendar changes in the mailbox from being logged. Valid values are: - $true: Changes to a calendar item aren't recorded. -- $false: Changes to a calendar item are recorded. This keeps older versions of meetings and appointments. This is the default value. +- $false: Changes to a calendar item are recorded. This keeps older versions of meetings and appointments. This value is the default. ```yaml Type: Boolean @@ -2047,7 +2047,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The ClientExtensions parameter specifies whether the organization-wide client extensions (also called Apps for Outlook) will be installed in the arbitration mailbox (also called the organization mailbox). Only one arbitration mailbox in the organization can be configured to store client extensions. You can use this parameter only on an arbitration mailbox. +The ClientExtensions parameter specifies whether the organization-wide client extensions (also called Apps for Outlook) are installed in the arbitration mailbox (also called the organization mailbox). Only one arbitration mailbox in the organization can be configured to store client extensions. You can use this parameter only on an arbitration mailbox. Valid values are $true or $false. @@ -2092,7 +2092,7 @@ This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: -- $true: A DTMF map is created for the recipient. This is the default value. +- $true: A DTMF map is created for the recipient. This value is the default. - $false: A DTMF map isn't created for the recipient. ```yaml @@ -2441,7 +2441,7 @@ The DefaultAuditSet parameter specifies whether to revert the mailbox operations - Delegate: Reverts the mailbox operations to log for delegate users back to the default list of operations. - Owner: Reverts the mailbox operations to log for mailbox owners back to the default list of operations. -With on-by-default mailbox auditing in the cloud-based service, a set of mailbox operations are logged by default for each logon type. This list of operations is managed by Microsoft, who will automatically add new operations to be audited when they are released. If you change the list of mailbox operations for any logon type (by using the AuditAdmin, AuditDelegate, or AuditOwner parameters), any new mailbox operation released by Microsoft will not be audited; you'll need to explicitly add new mailbox operations to the list of operations for a logon type. Use this parameter to revert the mailbox back to the Microsoft-managed list of mailbox operations that are audited for a logon type. For more information about on-by-default mailbox auditing, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes). +With on-by-default mailbox auditing in the cloud-based service, a set of mailbox operations are logged by default for each logon type. This list of operations is managed by Microsoft, and new mailbox operations are automatically added to auditing as they're released. If you change the list of mailbox operations for any logon type (by using the AuditAdmin, AuditDelegate, or AuditOwner parameters), any new mailbox operation released by Microsoft aren't audited. You need to explicitly add new mailbox operations to the list of operations for a logon type. Use this parameter to revert the mailbox back to the Microsoft-managed list of mailbox operations that are audited for a logon type. For more information about on-by-default mailbox auditing, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes). ```yaml Type: MultiValuedProperty @@ -2513,8 +2513,8 @@ This parameter is available only in on-premises Exchange. The DisableThrottling parameter enables or disables sender rate throttling for the mailbox. Valid values are: -- $true: Messages sent by this mailbox will not be throttled by Sender Rate Control. We only recommend this value for moderation mailboxes. -- $false: Messages will be throttled after the threshold is exceeded. This is the default value. +- $true: Messages sent by this mailbox aren't throttled by Sender Rate Control. We only recommend this value for moderation mailboxes. +- $false: Messages are throttled after the threshold is exceeded. This value is the default. ```yaml Type: Boolean @@ -2575,7 +2575,7 @@ This parameter is available only in on-premises Exchange. The DowngradeHighPriorityMessagesEnabled parameter specifies whether to prevent the mailbox from sending high priority messages to an X.400 mail system. Valid values are: - $true: High priority messages sent to X.400 recipients are changed to normal priority. -- $false: High priority messages set to X.400 recipients remain high priority. This is the default value. +- $false: High priority messages set to X.400 recipients remain high priority. This value is the default. ```yaml Type: Boolean @@ -2641,8 +2641,8 @@ This parameter is available only in the cloud-based service. The ElcProcessingDisabled parameter specifies whether to prevent the Managed Folder Assistant from processing the mailbox. Valid values are: -- $true: The Managed Folder Assistant isn't allowed to process the mailbox. Note that this setting will be ignored if a retention policy that has Preservation Lock enabled is applied to the mailbox. -- $false: The Managed Folder Assistant is allowed to process the mailbox. This is the default value. +- $true: The Managed Folder Assistant isn't allowed to process the mailbox. This setting is ignored if a retention policy that has Preservation Lock enabled is applied to the mailbox. +- $false: The Managed Folder Assistant is allowed to process the mailbox. This value is the default. ```yaml Type: Boolean @@ -2723,7 +2723,7 @@ This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -2771,7 +2771,7 @@ Accept wildcard characters: False The EndDateForRetentionHold parameter specifies the end date for retention hold for messaging records management (MRM). To use this parameter, you need to set the RetentionHoldEnabled parameter to the value $true. -**Important**: Using this parameter does not change the _RetentionHoldEnabled_ value to $false after the specified date. The _RentionHoldEnabled_ will still be $true on the mailbox after the specified date, but MRM will start processing mailbox items as normal. +**Important**: Using this parameter does not change the _RetentionHoldEnabled_ value to $false after the specified date. The _RetentionHoldEnabled_ is still $true on the mailbox after the specified date, but MRM starts processing mailbox items as normal. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". @@ -2835,7 +2835,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Online. -The ExcludeFromOrgHolds parameter excludes the mailbox from one or more organization-wide Microsoft 365 retention policies. This parameter can only be used for inactive mailboxes. A valid value for this parameter is the GUID of the organization-wide Microsoft 365 retention policy that the inactive mailbox is excluded from. To find the GUID values of organization-wide Microsoft 365 retention policies, run the command Get-OrganizationConfig | Format-List InplaceHolds. Note that retention policies assigned to mailboxes are prefaced by 'mbx'. +The ExcludeFromOrgHolds parameter excludes the mailbox from one or more organization-wide Microsoft 365 retention policies. This parameter can only be used for inactive mailboxes. A valid value for this parameter is the GUID of the organization-wide Microsoft 365 retention policy that the inactive mailbox is excluded from. To find the GUID values of organization-wide Microsoft 365 retention policies, run the command Get-OrganizationConfig | Format-List InplaceHolds. Retention policies assigned to mailboxes are prefaced by 'mbx'. You can specify multiple values by using the syntax: "GUID1","GUID2",..."GUIDX". @@ -2883,7 +2883,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -2907,7 +2907,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -2931,7 +2931,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -2955,7 +2955,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -2979,7 +2979,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -2999,7 +2999,7 @@ Accept wildcard characters: False The ExternalOofOptions parameter specifies the automatic replies or Out of Office (also known OOF) message options that are available for the mailbox. Valid values are: -- External: Automatic replies can be configured for external senders. This is the default value. +- External: Automatic replies can be configured for external senders. This value is the default. - InternalOnly: Automatic replies can be configured only for internal senders. ```yaml @@ -3020,7 +3020,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The FolderHierarchyChildrenCountReceiveQuota parameter specifies the maximum number of subfolders that can be created in a mailbox folder. The mailbox owner won't be able to create a new subfolder when this limit is reached. +The FolderHierarchyChildrenCountReceiveQuota parameter specifies the maximum number of subfolders that can be created in a mailbox folder. The mailbox owner can't create a new subfolder when this limit is reached. To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FolderHierarchyChildrenCountReceiveQuota`. @@ -3064,7 +3064,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The FolderHierarchyDepthReceiveQuota parameter specifies the maximum number of levels in the folder hierarchy of a mailbox folder. The mailbox owner won't be able to create another level in the folder hierarchy of the mailbox folder when this limit is reached. +The FolderHierarchyDepthReceiveQuota parameter specifies the maximum number of levels in the folder hierarchy of a mailbox folder. The mailbox owner can't create another level in the folder hierarchy of the mailbox folder when this limit is reached. To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FolderHierarchyDepthReceiveQuota`. @@ -3108,7 +3108,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The FoldersCountReceiveQuota parameter is used to specify a maximum number of folders within a mailbox, typically a public folder mailbox. If this value is configured and the limit is reached, no new folders will be able to be created. +The FoldersCountReceiveQuota parameter is used to specify a maximum number of folders within a mailbox, typically a public folder mailbox. If this value is configured and the limit is reached, you can't create new folders in the mailbox. To see the current value of this property, run the command `Get-MailboxStatistics | Format-List FoldersCountReceiveQuota`. @@ -3313,7 +3313,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -3363,11 +3363,11 @@ The ImListMigrationCompleted parameter specifies whether a user's Lync or Skype Valid values are: - $true: The user's Lync or Skype for Business contact list is stored in their Exchange 2016 mailbox. This prevents you from migrating the mailbox back to an Exchange 2010 server. -- $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This is the default value. +- $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This value is the default. Lync Server 2013 and Skype for Business Server 2015 support storing the user's contact list in their Exchange 2016 mailbox. This feature is known as the unified contact store (UCS), and it allows applications to show a consistent, up-to-date contact list. However, Exchange 2010 doesn't support the unified contact store. Therefore, before you migrate a user's Exchange 2016 mailbox back to Exchange 2010, you need to move the user's Lync or Skype for Business contact list from the unified contact store back to a Lync 2013 or Skype for Business server. For more information, see [Configuring Microsoft Lync Server 2013 to use the unified contact store](https://learn.microsoft.com/lyncserver/lync-server-2013-configuring-lync-server-to-use-the-unified-contact-store). -If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list has been moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false. +If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list is moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false. ```yaml Type: Boolean @@ -3433,7 +3433,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and won't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user will still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox. +The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and can't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user can still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox. You should use this parameter only during public folder migrations. Don't use this parameter once the initial migration validation is complete. @@ -3503,11 +3503,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. -In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you may be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. +In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you might be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter on the mailbox is set to $true (the default value), the value of the this parameter is ignored, and the mailbox uses the IssueWarningQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. @@ -3681,7 +3681,7 @@ Accept wildcard characters: False The LitigationHoldEnabled parameter specifies whether to place the mailbox on litigation hold. Valid values are: - $true: The mailbox is on litigation hold. -- $false: The mailbox isn't on litigation hold. This is the default value. +- $false: The mailbox isn't on litigation hold. This value is the default. After a mailbox is placed on litigation hold, messages can't be deleted from the mailbox. Deleted items and all versions of changed items are retained in the Recoverable Items folder. Items that are purged from the dumpster are also retained and the items are held indefinitely. If you enable litigation hold, single-item recovery quotas aren't applied. @@ -3937,11 +3937,11 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. -In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. +In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you use this parameter to configure the MaxReceiveSize value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the MaxReceiveSize value for all new mailboxes that you create in the future. @@ -3994,11 +3994,11 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. -In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. +In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you use this parameter to configure the MaxSendSize value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the MaxSendSize value for all new mailboxes that you create in the future. @@ -4027,7 +4027,7 @@ Accept wildcard characters: False The MessageCopyForSendOnBehalfEnabled parameter specifies whether to copy the sender for messages that are sent from a mailbox by users that have the "send on behalf of" permission. Valid values are: - $true: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message is sent to the sender's mailbox. -- $false: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message isn't sent to the sender's mailbox. This is the default value. +- $false: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message isn't sent to the sender's mailbox. This value is the default. You give users permission to send on behalf of a mailbox by using the GrantSendOnBehalfTo parameter on the mailbox. @@ -4052,7 +4052,7 @@ Accept wildcard characters: False The MessageCopyForSentAsEnabled parameter specifies whether to copy the sender for messages that are sent from a mailbox by users that have the "send as" permission. Valid values are: - $true: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message is sent to the sender's mailbox. -- $false: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message isn't sent to the sender's mailbox. This is the default value. +- $false: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message isn't sent to the sender's mailbox. This value is the default. In Exchange Online, you give a user permission to send as a mailbox by running this command: `Add-RecipientPermission -AccessRights SendAs -Trustee `. @@ -4078,7 +4078,7 @@ This parameter is available only in the cloud-based service. The MessageCopyForSMTPClientSubmissionEnabled parameter specifies whether to copy the sender for messages that are sent using SMTP client submission (SMTP AUTH). Valid values are: -- $true: When the user's account sends messages using SMTP AUTH, a copy of the message is sent to the users's mailbox. This is the default value. +- $true: When the user's account sends messages using SMTP AUTH, a copy of the message is sent to the users's mailbox. This value is the default. - $false: When the user's account sends messages using SMTP AUTH, a copy of the message isn't sent to the users's mailbox. ```yaml @@ -4121,7 +4121,7 @@ Accept wildcard characters: False The MessageTrackingReadStatusEnabled parameter specifies whether to include detailed information in delivery reports for messages sent to the mailbox. Valid values are: -- $true: The read status of the message and the date-time that the message was delivered is shown in the delivery report for messages sent to this mailbox. This is the default value. +- $true: The read status of the message and the date-time that the message was delivered is shown in the delivery report for messages sent to this mailbox. This value is the default. - $false: The read status of the message isn't displayed in the delivery report for messages sent to this mailbox. Only the date-time that the message was delivered is shown in the delivery report. ```yaml @@ -4214,7 +4214,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -4493,11 +4493,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value. -In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you may be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. +In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you might be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes. In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the ProhibitSendQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false. @@ -4527,7 +4527,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. @@ -4691,7 +4691,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. @@ -4727,7 +4727,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsWarningQuota value must be less than or equal to the RecoverableItemsQuota value. @@ -4991,9 +4991,9 @@ This parameter is available only in the cloud-based service. The RemoveOrphanedHolds parameter is used to remove the mailbox (typically, an inactive mailbox) from In-Place Holds that no longer exist, but are still applied to the mailbox. You identify the In-Place Hold by using its GUID value. You can specify multiple GUID values separated by commas. -If you use the GUID value of an In-Place Hold that still exists as a value for this parameter, the command will return an error. If that happens, you'll need to remove the mailbox (or inactive mailbox) from the In-Place Hold. +If you use the GUID value of an In-Place Hold that still exists as a value for this parameter, the command returns an error. If that happens, you need to remove the mailbox (or inactive mailbox) from the In-Place Hold. -In an Exchange hybrid deployment, In-Place Holds that are created in the on-premises organization can be applied to cloud-based mailboxes. In this scenario, it's possible that the hold object hasn't been synced to the cloud-based organization, and using this parameter will remove the specified hold from the cloud-based mailbox even though the hold may still exist. To prevent this from happening, make sure the hold doesn't exist in the on-premises organization before you use this parameter. +In an Exchange hybrid deployment, In-Place Holds that are created in the on-premises organization can be applied to cloud-based mailboxes. In this scenario, it's possible that the hold object hasn't been synced to the cloud-based organization, and using this parameter removes the specified hold from the cloud-based mailbox even though the hold might still exist. To prevent this from happening, make sure the hold doesn't exist in the on-premises organization before you use this parameter. ```yaml Type: String[] @@ -5081,7 +5081,7 @@ This parameter is available only in on-premises Exchange. The ResetPasswordOnNextLogon parameter specifies whether the user is required to change their password the next time they log on to their mailbox. Valid values are: - $true: The user is required to change their password the next time they log on to their mailbox. -- $false: The user isn't required to change their password the next time they log on to their mailbox. This is the default value. +- $false: The user isn't required to change their password the next time they log on to their mailbox. This value is the default. In Exchange Online, administrators can require users to reset their password the next time they log on by using the ResetPasswordOnNextLogon parameter on the Set-User cmdlet. @@ -5184,7 +5184,7 @@ This parameter is available only in on-premises Exchange. The RetainDeletedItemsUntilBackup parameter specifies whether to keep items in the Recoverable Items\\Deletions folder of the mailbox until the next database backup occurs. Valid values are: - $true: Deleted items are kept until the next mailbox database backup. This value could effectively override the DeletedItemRetention and RecoverableItemsQuota parameter values. -- $false: This is the default value. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameter values. +- $false: This value is the default. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameter values. When the UseDatabaseRetentionDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the RetainDeletedItemsUntilBackup parameter value from the mailbox database. To use the RetainDeletedItemsUntilBackup parameter on the mailbox, you need to set the UseDatabaseRetentionDefaults parameter to the value $false. @@ -5233,7 +5233,7 @@ Accept wildcard characters: False The RetentionHoldEnabled parameter specifies whether the mailbox is placed on retention hold. Placing the mailbox on retention hold temporarily suspends the processing of retention policies or managed folder mailbox policies for the mailbox (for example, when the user is on vacation). Valid values are: - $true: The mailbox is placed on retention hold. Retention policies and managed folder policies are suspended for the mailbox, and purging items from the mailbox isn't possible (even using MFCMapi). -- $false: The retention hold is removed from the mailbox. The mailbox is subject to retention policies and managed folder policies. This is the default value. +- $false: The retention hold is removed from the mailbox. The mailbox is subject to retention policies and managed folder policies. This value is the default. To set the start date for retention hold, use the StartDateForRetentionHold parameter. @@ -5368,7 +5368,7 @@ A valid value is a number from 32 to 256 kilobytes (32768 to 262144 bytes). When - B (bytes) - KB (kilobytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. In Exchange Online, Exchange 2019, Exchange 2016, and Exchange 2013, the default value is 256 kilobytes (262,144 bytes). @@ -5394,7 +5394,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -5438,7 +5438,7 @@ The SCLDeleteEnabled parameter specifies whether to silently delete messages tha - $true: Messages that meet or exceed the SCLDeleteThreshold value are silently deleted without sending a non-delivery report (NDR). - $false: Messages that meet or exceed the SCLDeleteThreshold value aren't deleted. -- $null (blank): The value isn't configured. This is the default value. +- $null (blank): The value isn't configured. This value is the default. ```yaml Type: Boolean @@ -5484,7 +5484,7 @@ The SCLJunkEnabled parameter specifies whether messages that exceed(not meet) th - $true: Messages that exceed the SCLJunkThreshold value are moved to the Junk Email folder. Messages that meet the SCLJunkThreshold value aren't moved to the Junk Email folder. - $false: Messages that meet or exceed the SCLJunkThreshold value aren't moved to the Junk Email folder. -- $null (blank): The value isn't configured. This is the default value. +- $null (blank): The value isn't configured. This value is the default. ```yaml Type: Boolean @@ -5530,7 +5530,7 @@ The SCLQuarantineEnabled parameter specifies whether messages that meet or excee - $true: Messages that meet or exceed the SCLQuarantineThreshold value are sent to the quarantine mailbox. - $false: Messages that meet or exceed the SCLQuarantineThreshold value aren't sent to the quarantine mailbox. -- $null (blank): The value isn't configured. This is the default value. +- $null (blank): The value isn't configured. This value is the default. To configure the quarantine mailbox, see [Configure a spam quarantine mailbox](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-quarantine-mailboxes). @@ -5578,7 +5578,7 @@ The SCLRejectEnabled parameter specifies whether messages that meet or exceed th - $true: Messages that meet or exceed the SCLRejectThreshold value are rejected, and an NDR is sent to the sender. - $false: Messages that meet or exceed the SCLRejectThreshold value aren't rejected. -- $null (blank): The value isn't configured. This is the default value. +- $null (blank): The value isn't configured. This value is the default. ```yaml Type: Boolean @@ -5660,7 +5660,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. @@ -5732,8 +5732,8 @@ Accept wildcard characters: False The SingleItemRecoveryEnabled parameter specifies whether to prevent the Recoverable Items folder from being purged. Valid values are: -- $true: Single item recovery is enabled. The Recoverable Items folder can't be purged, and deleted or edited items can't be removed. This is the default value in Exchange Online. For more information, see [Enable or disable single item recovery for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-single-item-recovery). -- $false: Single item recovery isn't enabled. The Recoverable Items folder can be purged, and deleted or edited items can be removed. This is the default value in Exchange Server. For more information, see [Enable or disable single item recovery for a mailbox](https://learn.microsoft.com/exchange/recipients/user-mailboxes/single-item-recovery). +- $true: Single item recovery is enabled. The Recoverable Items folder can't be purged, and deleted or edited items can't be removed. This value is the default in Exchange Online. For more information, see [Enable or disable single item recovery for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-single-item-recovery). +- $false: Single item recovery isn't enabled. The Recoverable Items folder can be purged, and deleted or edited items can be removed. This value is the default in Exchange Server. For more information, see [Enable or disable single item recovery for a mailbox](https://learn.microsoft.com/exchange/recipients/user-mailboxes/single-item-recovery). ```yaml Type: Boolean @@ -5958,7 +5958,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The UMGrammar parameter specifies whether the arbitration mailbox (also called an organization mailbox) is used for UM directory speech grammar generation for the organization. UM directory speech grammars will be generated and used on the Mailbox server of this arbitration mailbox. UM directory speech grammars are used in speech-enabled directory search features, such as UM auto attendants. You can use this parameter only on an arbitration mailbox. +The UMGrammar parameter specifies whether the arbitration mailbox (also called an organization mailbox) is used for UM directory speech grammar generation for the organization. UM directory speech grammars are generated and used on the Mailbox server of this arbitration mailbox. UM directory speech grammars are used in speech-enabled directory search features, such as UM auto attendants. You can use this parameter only on an arbitration mailbox. Valid values are $true or $false. @@ -6032,7 +6032,7 @@ This parameter is functional only in on-premises Exchange. The UseDatabaseRetentionDefaults parameter specifies whether the retention settings for items in the Recoverable Items folder in the mailbox are determined by the settings on the mailbox or the corresponding settings on the mailbox database. Valid values are: -- $true: The mailbox uses the applicable retention settings that are configured on the mailbox database. Any corresponding settings that are configured on the mailbox are ignored. This is the default value. +- $true: The mailbox uses the applicable retention settings that are configured on the mailbox database. Any corresponding settings that are configured on the mailbox are ignored. This value is the default. - $false: The mailbox uses its own values for the applicable retention settings. Any corresponding settings that are configured on the mailbox database are ignored. The following retention settings are affected by this parameter: @@ -6040,7 +6040,7 @@ The following retention settings are affected by this parameter: - DeletedItemRetention - RetainDeletedItemsUntilBackup -**Note**: If you set the RetainDeletedItemsUntilBackup parameter on the mailbox database to the value $true when the value of the UseDatabaseRetentionDefaults parameter on a mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet will erroneously appear as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell: +**Note**: If you set the RetainDeletedItemsUntilBackup parameter on the mailbox database to the value $true when the value of the UseDatabaseRetentionDefaults parameter on a mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet erroneously appears as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell: - Run the following command: `Import-Module ActiveDirectory`. - Replace \ with the Alias value of the mailbox, and run the following command: `Get-ADUser -Properties mDBUseDefaults | Format-List mDBUseDefaults`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md index 2ea3be04e4..727665ecc5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md @@ -13,7 +13,7 @@ title: Set-MailboxAuditBypassAssociation # Set-MailboxAuditBypassAssociation ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxAuditBypassAssociation cmdlet to configure mailbox audit logging bypass for user or computer accounts such as service accounts for applications that access mailboxes frequently. @@ -32,9 +32,9 @@ Set-MailboxAuditBypassAssociation [-Identity] ## DESCRIPTION You can disable Automatic Replies for a specified mailbox or organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -105,7 +105,7 @@ This parameter is functional only in the cloud-based service. The AutoDeclineFutureRequestsWhenOOF parameter specifies whether to automatically decline new meeting requests that are sent to the mailbox during the scheduled time period when Automatic Replies are being sent. Valid values are: - $true: New meeting requests that are received during the scheduled time period are automatically declined. -- $false: Meeting requests received during the scheduled time period aren't automatically declined. This is the default value. +- $false: Meeting requests received during the scheduled time period aren't automatically declined. This value is the default. You can use this parameter only when the AutoReplyState parameter is set to Scheduled. @@ -128,7 +128,7 @@ Accept wildcard characters: False The AutoReplyState parameter specifies whether the mailbox is enabled for Automatic Replies. Valid values are: - Enabled: Automatic Replies are sent for the mailbox. -- Disabled: Automatic Replies aren't sent for the mailbox. This is the default value. +- Disabled: Automatic Replies aren't sent for the mailbox. This value is the default. - Scheduled: Automatic Replies are sent for the mailbox during the time period that's specified by the StartTime and EndTime parameters. The Enabled and Scheduled values require these additional settings: @@ -178,7 +178,7 @@ This parameter is functional only in the cloud-based service. The CreateOOFEvent parameter specifies whether to create a calendar event that corresponds to the scheduled time period when Automatic Replies are being sent for the mailbox. Valid values are: - $true: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, a calendar event is created in the mailbox for those dates. You can specify the subject for the event by using the OOFEventSubject parameter. -- $false: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, no calendar event is created for those dates. This is the default value. +- $false: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, no calendar event is created for those dates. This value is the default. ```yaml Type: Boolean @@ -201,7 +201,7 @@ This parameter is functional only in the cloud-based service. The DeclineAllEventsForScheduledOOF parameter specifies whether to decline all existing calendar events in the mailbox during the scheduled time period when Automatic Replies are being sent. Valid values are: - $true: Existing calendar events in the mailbox that occur during the scheduled time period are declined and removed from the calendar. If the mailbox is the meeting organizer, the events are cancelled for all other attendees. -- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This is the default value. +- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This value is the default. You can use this parameter only when the DeclineEventsForScheduledOOF parameter is set to $true. @@ -231,7 +231,7 @@ The DeclineEventsForScheduledOOF parameter specifies whether it's possible to de To decline specific events during the scheduled time period, use the EventsToDeleteIDs parameter. To decline all events during the scheduled time period, use the DeclineAllEventsForScheduledOOF parameter. -- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This is the default value. +- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This value is the default. You can use this parameter only when the AutoReplyState parameter is set to Scheduled. @@ -346,7 +346,7 @@ The ExternalAudience parameter specifies whether Automatic Replies are sent to e - None: Automatic Replies aren't sent to any external senders. - Known: Automatic Replies are sent only to external senders that are specified in the Contact list of the mailbox. -- All: Automatic Replies are sent to all external senders. This is the default value. +- All: Automatic Replies are sent to all external senders. This value is the default. The value of this parameter is meaningful only when the AutoReplyState parameter is set to Enabled or Scheduled. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md index 72fd48a291..d0f4c94bb5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md @@ -13,7 +13,7 @@ title: Set-MailboxCalendarConfiguration # Set-MailboxCalendarConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxCalendarConfiguration cmdlet to modify mailbox calendar settings for Outlook on the web. This affects how the user's calendar looks and how reminders work in Outlook on the web. This also affects settings that define how meeting invitations, responses, and notifications are sent to the user. @@ -158,7 +158,7 @@ Set-MailboxCalendarConfiguration [-MailboxLocation ] ## DESCRIPTION The Set-MailboxCalendarConfiguration cmdlet primarily allows users to manage their own calendar settings in Outlook on the web Options. However, administrators who are members of the Organization Management or Recipient Management role groups can configure the calendar settings for users by using this cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -381,7 +381,7 @@ Accept wildcard characters: False The ConversationalSchedulingEnabled parameter specifies whether to enable or disable conversational scheduling. Valid values are: -- $true: Conversational scheduling is enabled. This is the default value. +- $true: Conversational scheduling is enabled. This value is the default. - $false: Conversational scheduling is disabled. ```yaml @@ -404,7 +404,7 @@ This parameter is available only in the cloud-based service. The CreateEventsFromEmailAsPrivate parameter specifies whether to create events from email messages as Normal or Private. Valid values are: -- $true: Events from email are created as Private. This is the default value. +- $true: Events from email are created as Private. This value is the default. - $false: Events from email are created as Normal (public). ```yaml @@ -516,7 +516,7 @@ The DefaultOnlineMeetingProvider parameter specifies the default provider for on - RingCentral - SkypeForBusiness - SkypeForConsumer -- TeamsForBusiness (This is the default value.) +- TeamsForBusiness (This value is the default.) - Webex - Zoom @@ -540,12 +540,12 @@ The DefaultReminderTime parameter specifies the length of time before a meeting To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. -Note that the value can't contain seconds. Valid values are: +The value can't contain seconds. Valid values are: - 00:00:00 - 00:05:00 (5 minutes) - 00:10:00 (10 minutes) -- 00:15:00 (15 minutes) This is the default value. +- 00:15:00 (15 minutes) This value is the default. - 00:30:00 (30 minutes) - 01:00:00 (1 hour) - 02:00:00 (2 hours) @@ -601,7 +601,7 @@ This parameter is available only in the cloud-based service. The DiningEventsFromEmailEnabled parameter specifies whether to create dining reservation events from email messages. Valid values are: -- $true: Create dining reservation events from email messages. This is the default value. +- $true: Create dining reservation events from email messages. This value is the default. - $false: Don't create dining reservation events from email messages. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -646,7 +646,7 @@ This parameter is available only in the cloud-based service. The EntertainmentEventsFromEmailEnabled parameter specifies whether to create entertainment reservation events from email messages. Valid values are: -- $true: Create entertainment reservation events from email messages. This is the default value. +- $true: Create entertainment reservation events from email messages. This value is the default. - $false: Don't create entertainment reservation events from email messages. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -671,7 +671,7 @@ This parameter is available only in the cloud-based service. The EventsFromEmailEnabled parameter specifies whether to enable events to be created from email messages. Valid values are: -- $true: Creating events from email messages is enabled. This is the default value. +- $true: Creating events from email messages is enabled. This value is the default. - $false: Creating events from email messages is disabled. When this setting is enabled, you can enable or disable creating specific types of events from email messages by using the following parameters: @@ -701,10 +701,10 @@ Accept wildcard characters: False The FirstWeekOfYear parameter specifies the first week of the year. Valid values are: -- FirstDay: Week numbers start on the first day of the year. This is the default value. +- FirstDay: Week numbers start on the first day of the year. This value is the default. - FirstFourDayWeek: Week numbers start on the first week that has at least four days. - FirstFullWeek: Week numbers start on the first week that has seven days. -- LegacyNotSet: You can't set this value. This is a null value that appears only when the mailbox has been moved from an earlier version of Exchange. +- LegacyNotSet: You can't set this value. This is a null value that appears only when the mailbox is moved from an earlier version of Exchange. You configure the first day of the week by using the WeekStartDay parameter. @@ -728,7 +728,7 @@ This parameter is available only in the cloud-based service. The FlightEventsFromEmailEnabled parameter specifies whether to create flight reservation events from email messages. Valid values are: -- $true: Create flight reservation events from email messages. This is the default value. +- $true: Create flight reservation events from email messages. This value is the default. - $false: Don't create flight reservation events from email messages. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -753,7 +753,7 @@ This parameter is available only in the cloud-based service. The HotelEventsFromEmailEnabled parameter specifies whether to create hotel reservation events from email messages. Valid values are: -- $true: Create hotel reservation events from email messages. This is the default value. +- $true: Create hotel reservation events from email messages. This value is the default. - $false: Don't create hotel reservation events from email messages. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -778,7 +778,7 @@ This parameter is available only in the cloud-based service. The InvoiceEventsFromEmailEnabled parameter specifies whether to allow creating invoices from email messages. Valid values are: -- $true: Creating invoices from messages is enabled. This is the default value. +- $true: Creating invoices from messages is enabled. This value is the default. - $false: Creating invoices from messages is disabled. ```yaml @@ -803,7 +803,7 @@ The LocationDetailsInFreeBusy parameter specifies the level of work location inf - None: No location information is returned. - Building: Only Office or Remote are returned as work location information, if provided. -- Desk: All work location information is returned, including Building and Desk, if provided. This is the default value. +- Desk: All work location information is returned, including Building and Desk, if provided. This value is the default. ```yaml Type: LocationDetailsPermissionInFreeBusy @@ -843,7 +843,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetings as Teams or Skype for Business by default during meeting creation. Currently, this parameter sets the default value, so if the user has already directly interacted with this setting from an Outlook client, this default value will be ignored. Eventually, this parameter will override the Outlook-configured setting. +The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetings as Teams or Skype for Business by default during meeting creation. Currently, this parameter sets the default value, so if the user has already directly interacted with this setting from an Outlook client, this default value is ignored. Eventually, this parameter will override the Outlook-configured setting. Valid values are: @@ -874,7 +874,7 @@ This parameter is available only in the cloud-based service. The PackageDeliveryEventsFromEmailEnabled parameter specifies whether to create package delivery events from email messages. Valid values are: - $true: Create package delivery events from email messages. -- $false: Don't create package delivery events from email messages. This is the default value. +- $false: Don't create package delivery events from email messages. This value is the default. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -916,7 +916,7 @@ Accept wildcard characters: False The RemindersEnabled parameter enables or disables reminders for calendar items. Valid values are: -- $true: Reminders are enabled. This is the default value. +- $true: Reminders are enabled. This value is the default. - $false: Reminders are disabled. When the reminder is first displayed is controlled by the DefaultReminderTime parameter. @@ -939,7 +939,7 @@ Accept wildcard characters: False The ReminderSoundEnabled parameter specifies whether a sound is played along with the reminder. Valid values are: -- $true: A sound is played with the reminder. This is the default value. +- $true: A sound is played with the reminder. This value is the default. - $false: No sound is played with the reminder. This parameter is ignored when the RemindersEnabled parameter is set to $false. @@ -964,7 +964,7 @@ This parameter is available only in the cloud-based service. The RentalCarEventsFromEmailEnabled parameter specifies whether to create rental car reservation events from email messages. Valid values are: -- $true: Create rental car reservation events from email messages. This is the default value. +- $true: Create rental car reservation events from email messages. This value is the default. - $false: Don't create rental car reservation events from email messages. This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value). @@ -1028,7 +1028,7 @@ Accept wildcard characters: False The ShowWeekNumbers parameter specifies whether the week number is displayed in the Outlook on the web calendar. Valid values are: - $true: The week number is displayed. -- $false: The week number isn't displayed. This is the default value. +- $false: The week number isn't displayed. This value is the default. ```yaml Type: Boolean @@ -1067,7 +1067,7 @@ Accept wildcard characters: False The TimeIncrement parameter specifies the scale that the Outlook on the web calendar uses to show time. Valid values are: - FifteenMinutes -- ThirtyMinutes (This is the default value) +- ThirtyMinutes (default value) ```yaml Type: HourIncrement @@ -1088,7 +1088,7 @@ Accept wildcard characters: False The UseBrightCalendarColorThemeInOwa parameter specifies whether to use light colors or bright colors for the calendar in Outlook on the web. Valid values are: - $true: Use bright colors in the calendar. -- $false: Use light colors in the calendar. This is the default value. +- $false: Use light colors in the calendar. This value is the default. ```yaml Type: Boolean @@ -1110,7 +1110,7 @@ This parameter is available only in the cloud-based service. The WeatherEnabled specifies whether weather is displayed in the calendar in Outlook on the web. Valid values are: -- FirstRun (This is the default value) +- FirstRun (default value) - Disabled: Hide weather on the calendar. - Enabled: Show weather on the calendar. @@ -1186,7 +1186,7 @@ This parameter is available only in the cloud-based service. The WeatherUnit parameter specifies the temperature scale that's used to display the weather in the calendar in Outlook on the web. Valid values are: -- Default (This is the default value) +- Default (default value) - Celsius - Fahrenheit @@ -1208,7 +1208,7 @@ Accept wildcard characters: False The WeekStartDay parameter specifies the first day of the week. Valid values are: -- Sunday (This is the default value) +- Sunday (default value) - Monday - Tuesday - Wednesday @@ -1254,7 +1254,7 @@ The WorkDays parameter specifies the work days in the calendar. Valid values are - None - AllDays -- Weekdays (This is the default value) +- Weekdays (default value) - WeekEndDays - Sunday - Monday diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md index d2fe92983d..7ad33e450c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md @@ -13,7 +13,7 @@ title: Set-MailboxCalendarFolder # Set-MailboxCalendarFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxCalendarFolder cmdlet to configure calendar publishing or sharing settings on a mailbox for the visibility of calendar information to external users. To add or modify the permissions so internal users can access the calendar, use the Add-MailboxFolderPermission or Set-MailboxFolderPermission cmdlets. @@ -46,7 +46,7 @@ The Set-MailboxCalendarFolder cmdlet configures calendar publishing information. - Level of detail to publish for the calendar - Whether the published URL of the calendar is enabled for search on the web -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -174,7 +174,7 @@ The PublishDateRangeFrom parameter specifies the start date of calendar informat - ThreeDays - OneWeek - OneMonth -- ThreeMonths (This is the default value) +- ThreeMonths (default value) - SixMonths - OneYear @@ -202,7 +202,7 @@ The PublishDateRangeTo parameter specifies the end date of calendar information - ThreeDays - OneWeek - OneMonth -- ThreeMonths (This is the default value) +- ThreeMonths (default value) - SixMonths - OneYear @@ -227,7 +227,7 @@ Accept wildcard characters: False The PublishEnabled parameter specifies whether to publish the specified calendar information. Valid values are: - $true: The calendar information is published. -- $false: The calendar information is not published. This is the default value. +- $false: The calendar information is not published. This value is the default. ```yaml Type: Boolean @@ -245,7 +245,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The ResetUrl switch replaces the existing non-public URL with a new URL for a calendar that has been published without being publicly searchable. You don't need to specify a value with this switch. +The ResetUrl switch replaces the existing non-public URL with a new URL for a calendar that is published without being publicly searchable. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter @@ -266,7 +266,7 @@ Accept wildcard characters: False The SearchableUrlEnabled parameter specifies whether the published calendar URL is discoverable on the web. - $true: The published calendar URL is discoverable on the web. -- $false: The published calendar URL is not discoverable on the web. This is the default value. +- $false: The published calendar URL is not discoverable on the web. This value is the default. This parameter is meaningful only when the PublishEnabled parameter value is $true. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md index 8678125dd0..e700a98c53 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md @@ -63,7 +63,7 @@ Set-MailboxDatabase [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -114,7 +114,7 @@ Accept wildcard characters: False The AllowFileRestore parameter specifies whether to allow a database to be restored from a backup. Valid values are: - $true: You can replace an existing database with a newly-created database. You can mount a database that doesn't match the database entry in Active Directory. -- $false: You can't replace an existing database with a newly-created database. You can't mount a database that doesn't match the database entry in Active Directory. This is the default value. +- $false: You can't replace an existing database with a newly-created database. You can't mount a database that doesn't match the database entry in Active Directory. This value is the default. ```yaml Type: Boolean @@ -135,7 +135,7 @@ Accept wildcard characters: False The AutoDagExcludedFromMonitoring parameter specifies whether to exclude the mailbox database from the ServerOneCopyMonitor, which alerts an administrator when a replicated database has only one healthy copy available. Valid values are: - $true: No alert is issued when there's only one healthy copy of the replicated database. -- $false: An alert is issued when there's only one healthy copy of the replicated database. This is the default value. +- $false: An alert is issued when there's only one healthy copy of the replicated database. This value is the default. ```yaml Type: Boolean @@ -173,7 +173,7 @@ Accept wildcard characters: False The BackgroundDatabaseMaintenance parameter specifies whether the Extensible Storage Engine (ESE) performs database maintenance. Valid values are: -- $true: The mailbox database reads the object during database mount and initializes the database to perform background maintenance. This is the default value. +- $true: The mailbox database reads the object during database mount and initializes the database to perform background maintenance. This value is the default. - $false: The mailbox database reads the object during database mount and initializes the database without the option to perform background maintenance. ```yaml @@ -204,7 +204,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the RecoverableItemsQuota parameter. @@ -229,7 +229,7 @@ Accept wildcard characters: False The CircularLoggingEnabled parameter specifies whether circular logging is enabled for the database. Valid values are: - $true: Circular logging is enabled. -- $false: Circular logging is disabled. This is the default value. +- $false: Circular logging is disabled. This value is the default. For more information about circular logging, see [Exchange Native Data Protection](https://learn.microsoft.com/exchange/backup-restore-and-disaster-recovery-exchange-2013-help#exchange-native-data-protection). @@ -296,7 +296,7 @@ The DataMoveReplicationConstraint parameter specifies the throttling behavior fo - CINoReplication (Exchange 2013 or later): Moves shouldn't be throttled to ensure high availability, but the content indexing service must be up to date. - CISecondCopy (Exchange 2013 or later): At least one passive mailbox database copy must have the most recent changes synchronized, and the content indexing service must be up to date. Use this setting to indicate that the database is replicated to one or more mailbox database copies. - CISecondDatacenter (Exchange 2013 or later): At least one passive mailbox database copy in another Active Directory site must have the most recent changes replicated, and the content indexing service must be up to date. Use this setting to indicate that the database is replicated to database copies in multiple Active Directory sites. -- SecondCopy: At least one passive mailbox database copy must have the most recent changes synchronized. This is the default value. Use this setting to indicate that the database is replicated to one or more mailbox database copies. +- SecondCopy: At least one passive mailbox database copy must have the most recent changes synchronized. This value is the default. Use this setting to indicate that the database is replicated to one or more mailbox database copies. - SecondDatacenter: At least one passive mailbox database copy in another Active Directory site must have the most recent changes replicated. Use this setting to indicate that the database is replicated to database copies in multiple Active Directory sites. Any value other than None enables the Microsoft Exchange Mailbox Replication service to coordinate with Active Manager. For more information, see [Active Manager](https://learn.microsoft.com/Exchange/high-availability/database-availability-groups/active-manager). @@ -387,7 +387,7 @@ This parameter is functional only in Exchange 2016 or earlier. The IndexEnabled parameter specifies whether Exchange Search indexes the mailbox database. Valid values are: -- $true: Exchange Search indexes the mailbox database. This is the default value. +- $true: Exchange Search indexes the mailbox database. This value is the default. - $false: Exchange Search doesn't index the mailbox database. ```yaml @@ -427,7 +427,7 @@ Accept wildcard characters: False The IsExcludedFromProvisioning parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are: - $true: The database is excluded from new or move mailbox operations when you don't specify the target mailbox database. -- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This is the default value. +- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This value is the default. The value is automatically set to $true when you set the IsExcludedFromProvisioningDueToLogicalCorruption parameter to $true, and isn't changed back to $false when you set the IsExcludedFromProvisioningDueToLogicalCorruption parameter back to $false. In the case of database corruption, you should set the IsExcludedFromProvisioning parameter back to $false only after you fix the corruption issue or recreate the database. @@ -452,9 +452,9 @@ The IIsExcludedFromProvisioningByOperator parameter specifies whether to exclude Valid values are: - $true: Indicates that you manually excluded the database. The database is excluded from new or move mailbox operations when you don't specify the target mailbox database. -- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This is the default value. +- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This value is the default. -Note that setting this parameter to the value $true has these additional effects on the database: +Setting this parameter to the value $true has these additional effects on the database: - The IsExcludedFromProvisioningReason parameter requires a value if it doesn't already have one. - The unmodifiable IsExcludedFromProvisioningBy property is populated with your user account. @@ -480,9 +480,9 @@ The IsExcludedFromProvisioningDueToLogicalCorruption parameter specifies whether Valid values are: - $true: Indicates that you excluded the database due to database corruption. The database is excluded from new or move mailbox operations when you don't specify the target mailbox database. -- $false: This is the default value. The database can be used in new or move mailbox operations when you don't specify the target mailbox database. You should manually configure this value only after the database corruption is fixed, or after the database is recreated. +- $false: This value is the default. The database can be used in new or move mailbox operations when you don't specify the target mailbox database. You should manually configure this value only after the database corruption is fixed, or after the database is recreated. -Note that setting this parameter to the value $true has these additional effects on the database: +Setting this parameter to the value $true has these additional effects on the database: - The IsExcludedFromProvisioningReason parameter requires a value if it doesn't already have one. - The unmodifiable IsExcludedFromProvisioningBy property is populated with your user account. @@ -538,7 +538,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. @@ -563,9 +563,9 @@ Accept wildcard characters: False The IsSuspendedFromProvisioning parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are: - $true: Indicates that you don't want the exclusion to be permanent. The database is excluded from new or move mailbox operations when you don't specify the target mailbox database. -- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This is the default value. +- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This value is the default. -Note that setting this parameter to the value $true has these additional effects on the database: +Setting this parameter to the value $true has these additional effects on the database: - The IsExcludedFromProvisioningReason parameter requires a value if it doesn't already have one. - The unmodifiable IsExcludedFromProvisioningBy property is populated with your user account. @@ -635,7 +635,7 @@ Accept wildcard characters: False This parameter is functional only in Exchange Server 2010. -The MaintenanceSchedule parameter specifies when maintenance will be performed on the mailbox database. Maintenance includes online defragmentation, removing items that have passed their retention period, removing unused indexes and other cleanup tasks. +The MaintenanceSchedule parameter specifies when maintenance is performed on the mailbox database. Maintenance includes online defragmentation, removing items that have passed their retention period, removing unused indexes and other cleanup tasks. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. @@ -695,7 +695,7 @@ Accept wildcard characters: False The MountAtStartup parameter specifies whether to mount the mailbox database when the Microsoft Exchange Information Store service starts. Valid values are: -- $true: The database is mounted when the service starts. This is the default value. +- $true: The database is mounted when the service starts. This value is the default. - $false: The database isn't mounted when the service starts. ```yaml @@ -766,7 +766,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value. @@ -798,7 +798,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. @@ -896,7 +896,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. @@ -930,7 +930,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsWarningQuota value must be less than or equal to the RecoverableItemsQuota value. @@ -955,13 +955,13 @@ Accept wildcard characters: False The RetainDeletedItemsUntilBackup parameter specifies whether to keep items in the Recoverable Items\\Deletions folder of the mailbox until the next database backup occurs. Valid values are: - $true: Deleted items in mailboxes are kept until the next mailbox database backup. This value could effectively override the deleted DeletedItemRetention and RecoverableItemsQuota parameter values. -- $false: This is the default value. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameters. +- $false: This value is the default. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameters. This settings applies to all mailboxes in the database that don't have their own RetainDeletedItemsUntilBackup value configured. For more information, see [Recoverable Items folder in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder). -**Note**: If you set the value of this parameter to $true when the value of the UseDatabaseRetentionDefaults parameter on a specific mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet will erroneously appear as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell: +**Note**: If you set the value of this parameter to $true when the value of the UseDatabaseRetentionDefaults parameter on a specific mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet erroneously appears as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell: - Run the following command: `Import-Module ActiveDirectory`. - Replace \ with the Alias value of the mailbox, and run the following command: `Get-ADUser -Properties mDBUseDefaults | Format-List mDBUseDefaults`. @@ -986,7 +986,7 @@ This parameter is functional only in Exchange Server 2010. The RpcClientAccessServer parameter specifies the Client Access server or Client Access server array through which RPC clients (for example, Microsoft Office Outlook 2007 clients) access their mailboxes. This feature is supported for all versions of Outlook. -When connecting with Outlook 2003 clients, RPC encryption is disabled by default. Unless RPC encryption is enabled on Outlook 2003 or disabled on the server, Outlook 2003 clients won't be able to connect. For more information, see [Understanding RPC Client Access](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/ee332317(v=exchg.141)). +When connecting with Outlook 2003 clients, RPC encryption is disabled by default. Unless RPC encryption is enabled on Outlook 2003 or disabled on the server, Outlook 2003 clients can't connect. For more information, see [Understanding RPC Client Access](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/ee332317(v=exchg.141)). ```yaml Type: ClientAccessServerOrArrayIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md index f8ef8e0bf2..91532aaab8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md @@ -37,7 +37,7 @@ Set-MailboxDatabaseCopy [-Identity] ## DESCRIPTION With this cmdlet, you can configure the replay lag time, truncation lag time, and activation preference value for a mailbox database copy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -160,7 +160,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service should wait before truncating log files that have replayed into the passive copy of the database. The time period begins after the log has been successfully replayed into the copy of the database. +The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service should wait before truncating log files that have replayed into the passive copy of the database. The time period begins after the log is successfully replayed into the copy of the database. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -224,7 +224,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h The default value is 24:00:00 (24 hours). To disable deferred lagged copy play down, specify the value ([TimeSpan]::Zero). -Note that when the disk is running out of space, the value of this parameter is ignored, and lagged copy play down occurs without delay. +When the disk is running out of space, the value of this parameter is ignored, and lagged copy play down occurs without delay. ```yaml Type: EnhancedTimeSpan diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md index 9800ba7cc0..b81f0286db 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md @@ -15,7 +15,7 @@ title: Set-MailboxExportRequest ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Set-MailboxExportRequest cmdlet to change export request options after the request has been created. You can use the Set-MailboxExportRequest cmdlet to recover from failed export requests. +Use the Set-MailboxExportRequest cmdlet to change export request options after the request is created. You can use the Set-MailboxExportRequest cmdlet to recover from failed export requests. This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). @@ -57,7 +57,7 @@ Set-MailboxExportRequest [-Identity] ## DESCRIPTION You can pipeline the Set-MailboxExportRequest cmdlet from the Get-MailboxExportRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -175,7 +175,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default value is 30 days. +The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default value is 30 days. ```yaml Type: Unlimited @@ -236,7 +236,7 @@ For more information about maximum message size values, see the following topics - Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits) - Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits) -Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. +Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request fails if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. @@ -261,7 +261,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md index a49cfbab41..223ac5f5c3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md @@ -13,7 +13,7 @@ title: Set-MailboxFolderPermission # Set-MailboxFolderPermission ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxFolderPermission cmdlet to modify folder-level permissions for users in mailboxes. This cmdlet differs from the Add-MailboxFolderPermission cmdlet in that it modifies existing permission entries. To configure calendar publishing or sharing settings for a mailbox so calendar information is visible to external users, use the Set-MailboxCalendarFolder cmdlet. @@ -32,9 +32,9 @@ Set-MailboxFolderPermission [-Identity] -AccessRights ``` ## DESCRIPTION -In Exchange Online PowerShell, if you don't use the SendNotificationToUser or SharingPermissionFlags parameters, there are no changes to the functionality of the cmdlet. For example, if the user is an existing delegate, and you change their permissions to Editor without using the SendNotificationToUser or SharingPermissionFlags parameters, the user remains a delegate. But, if you use the SendNotificationToUser parameter ($true or $false), the SharingPermissionFlags parameter has the default value None, which can affect delegate access for existing users. For example, you change an existing delegate's permission to Editor, and you use SendNotificationToUser with the value $true. The user will no longer be a delegate and will only have Editor permissions to the folder. +In Exchange Online PowerShell, if you don't use the SendNotificationToUser or SharingPermissionFlags parameters, there are no changes to the functionality of the cmdlet. For example, if the user is an existing delegate, and you change their permissions to Editor without using the SendNotificationToUser or SharingPermissionFlags parameters, the user remains a delegate. But, if you use the SendNotificationToUser parameter ($true or $false), the SharingPermissionFlags parameter has the default value None, which can affect delegate access for existing users. For example, you change an existing delegate's permission to Editor, and you use SendNotificationToUser with the value $true. The user is no longer a delegate and has only Editor permissions to the folder. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -246,10 +246,10 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you modify their calendar permissions. The message will be a normal calendar sharing invitation that can be accepted by the recipient. Valid values are: +The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you modify their calendar permissions. The message is a normal calendar sharing invitation that can be accepted by the recipient. Valid values are: - $true: A sharing invitation is sent. -- $false: No sharing invitation is sent. This is the default value. +- $false: No sharing invitation is sent. This value is the default. This parameter only applies to calendar folders and can only be used with the following AccessRights parameter values: @@ -278,8 +278,8 @@ This parameter is available only in the cloud-based service. The SharingPermissionFlags parameter assigns calendar delegate permissions. This parameter only applies to calendar folders and can only be used when the AccessRights parameter value is Editor. Valid values are: -- None: Removes delegate permissions and updates the meeting message rule so the user stops receiving meeting invites and responses for the mailbox. This is the default value when you use the SendNotificationToUser parameter without specifying a value for the SharingPermissionFlags parameter. -- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value will create the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent. +- None: Removes delegate permissions and updates the meeting message rule so the user stops receiving meeting invites and responses for the mailbox. This value is the default when you use the SendNotificationToUser parameter without specifying a value for the SharingPermissionFlags parameter. +- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value creates the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent. - CanViewPrivateItems: The user can access private items on the calendar. You must use this value with the Delegate value. You can specify multiple values separated by commas. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md index 4d967f1dc5..f4f0e60e87 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md @@ -29,7 +29,7 @@ Set-MailboxIRMAccess -AccessLevel [-Identity] [!NOTE] > This cmdlet works only for delegates who already have Full Access permission to the mailbox. For more information, see [Manage permissions for recipients in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-permissions-for-recipients). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md index 2bcc2e87e1..86bba500cd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md @@ -13,9 +13,9 @@ title: Set-MailboxImportRequest # Set-MailboxImportRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. -Use the Set-MailboxImportRequest cmdlet to change import request options after the request has been created. You can use the Set-MailboxImportRequest cmdlet to recover from failed import requests. +Use the Set-MailboxImportRequest cmdlet to change import request options after the request is created. You can use the Set-MailboxImportRequest cmdlet to recover from failed import requests. This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). @@ -58,7 +58,7 @@ Set-MailboxImportRequest [-Identity] [-RehomeR ## DESCRIPTION You can pipeline the Set-MailboxImportRequest cmdlet from the Get-MailboxImportRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -148,7 +148,7 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -274,7 +274,7 @@ Valid input for this parameter is an integer or the value unlimited. The default If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -299,7 +299,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md index 5dde63a4e1..7c763e94da 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md @@ -13,7 +13,7 @@ title: Set-MailboxJunkEmailConfiguration # Set-MailboxJunkEmailConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxJunkEmailConfiguration cmdlet to configure the junk email settings on mailboxes. @@ -51,7 +51,7 @@ This cmdlet controls the following junk email settings on the mailbox: For more information, see [Configure Exchange antispam settings on mailboxes](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-settings). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -160,7 +160,7 @@ Accept wildcard characters: False The ContactsTrusted parameter specifies whether the contacts in the Contacts folder are treated as trusted senders. This parameter corresponds to the Outlook on the web setting: Trust email from my contacts. Valid values are: - $true: Messages from contacts in the Contacts folder that reach the mailbox are never delivered to the Junk Email folder, regardless of the content. -- $false: Messages from contacts in the Contacts folder aren't treated as trusted senders. The email address is a trusted sender only if it's defined in the Safe Senders list. This is the default value. +- $false: Messages from contacts in the Contacts folder aren't treated as trusted senders. The email address is a trusted sender only if it's defined in the Safe Senders list. This value is the default. ```yaml Type: Boolean @@ -200,7 +200,7 @@ Accept wildcard characters: False The Enabled parameter enables or disables the junk email rule on the mailbox (a hidden Inbox rule named Junk E-mail Rule). Valid values are: -- $true: The junk email rule is enabled in the mailbox. This value corresponds to the Outlook on the web setting: Automatically filter junk email. This is the default value. +- $true: The junk email rule is enabled in the mailbox. This value corresponds to the Outlook on the web setting: Automatically filter junk email. This value is the default. In on-premises Exchange, the safelist collection of the mailbox (the Safe Senders list, Safe Recipients list, and Blocked Senders list), and the SCL Junk Email folder threshold (for the organization or the mailbox) delivers messages to the Inbox or the Junk Email folder. @@ -301,7 +301,7 @@ Accept wildcard characters: False The TrustedListsOnly parameter specifies that only messages from senders in the Safe Senders list are delivered to the Inbox. All other messages are treated as junk email. This parameter corresponds to the Outlook on the web setting: Don't trust email unless it comes from someone in my Safe Senders and Recipients list. Valid values are: - $true: Only messages from email address or domain entries in the Safe Senders list and the Safe Recipients list are delivered to the Inbox. All other messages are automatically delivered to the Junk Email folder. -- $false: Messages from other senders, recipients, and domains aren't automatically treated as junk email, and are evaluated individually. This is the default value. +- $false: Messages from other senders, recipients, and domains aren't automatically treated as junk email, and are evaluated individually. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md index eb2d6eb0aa..40134436a3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md @@ -13,7 +13,7 @@ title: Set-MailboxMessageConfiguration # Set-MailboxMessageConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxMessageConfiguration cmdlet to configure the Outlook on the web settings that are applied to specific mailboxes. @@ -94,7 +94,7 @@ Set-MailboxMessageConfiguration [-Identity] ## DESCRIPTION The Set-MailboxMessageConfiguration cmdlet configures Outlook on the web settings for the specified mailbox. These settings include email signature, message format, message options, read receipts, reading pane, and conversations. These settings are not used in Outlook, Exchange ActiveSync, or other email clients. These settings are applied in Outlook on the web only. Some settings also apply to the new Outlook client. Settings that contain the word Mobile are applied in Outlook on the web for devices only. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -581,7 +581,7 @@ This parameter is available only in the cloud-based service. The EchoGroupMessageBackToSubscribedSender parameter controls whether subscribed members of Microsoft 365 Groups receive copies of messages that they send to those Groups. Valid values are: - $true: If a subscribed member of a Microsoft 365 Group sends a message to that Group, they'll receive a copy of the message in their Inbox. -- $false: Subscribed members of a Microsoft 365 Group don't receive their own copies of messages that they send to the Group. This is the default value. +- $false: Subscribed members of a Microsoft 365 Group don't receive their own copies of messages that they send to the Group. This value is the default. ```yaml Type: Boolean @@ -603,7 +603,7 @@ This parameter is functional only in on-premises Exchange. The EmailComposeMode parameter specifies how the user creates messages in Outlook on the web. You can use the following values: -- Inline: New messages and replies are created in the preview pane. This is the default value. +- Inline: New messages and replies are created in the preview pane. This value is the default. - SeparateForm: New messages and replies are created in a new browser window. ```yaml @@ -668,7 +668,7 @@ The GlobalReadingPanePosition specifies the default location of the reading pane - Off - Bottom -- Right (This is the default value) +- Right (default value) ```yaml Type: MailReadingPanePosition @@ -752,7 +752,7 @@ Accept wildcard characters: False The IsFavoritesFolderTreeCollapsed parameter specifies whether to collapse the Favorites folder tree by default in Outlook on the web. Valid values are: - $true: The Favorites folder tree is collapsed by default. -- $false: The Favorites folder tree isn't collapsed by default. This is the default value +- $false: The Favorites folder tree isn't collapsed by default. This value is the default ```yaml Type: Boolean @@ -793,7 +793,7 @@ Accept wildcard characters: False The IsMailRootFolderTreeCollapsed parameter specifies whether to collapse the Mail root folder tree by default in Outlook on the web. Valid values are: - $true: The Mail root folder tree is collapsed by default. -- $false: The Mail root folder tree isn't collapsed by default. This is the default value +- $false: The Mail root folder tree isn't collapsed by default. This value is the default ```yaml Type: Boolean @@ -813,7 +813,7 @@ Accept wildcard characters: False The IsReplyAllTheDefaultResponse parameter specifies whether Reply All is the default response for messages in Outlook on the web. Valid values are: -- $true: Reply All is the default response option for messages in the reading pane. This is the default value. +- $true: Reply All is the default response option for messages in the reading pane. This value is the default. - $false: Reply All isn't the default response option for messages in the reading pane. ```yaml @@ -834,7 +834,7 @@ Accept wildcard characters: False The LinkPreviewEnabled parameter specifies whether link preview of URLs in email messages is enabled for the user in Outlook on the web. Valid values are: -- $true: Link preview of URLs in email messages is enabled for the user. This is the default value. +- $true: Link preview of URLs in email messages is enabled for the user. This value is the default. - $false: Link preview of URLs in email messages is disabled for the user. This parameter depends on the value of the LinkPreviewEnabled parameter on the Set-OrganizationConfig cmdlet, which controls the link preview behavior in Outlook on the web for the entire organization. If link preview is disabled for the organization, users can't enable it for themselves. @@ -857,7 +857,7 @@ Accept wildcard characters: False The MailFolderPaneExpanded parameter specifies whether the Mail folder pane is expanded by default in Outlook on the web. Valid values are: -- $true: The Mail folder pane is expanded by default. This is the default value. +- $true: The Mail folder pane is expanded by default. This value is the default. - $false: The Mail folder pane isn't expanded by default. ```yaml @@ -938,7 +938,7 @@ Accept wildcard characters: False The NavigationPaneViewOption parameter specifies the default navigation pane view in Outlook on the web. Valid values are: -- Default: This is the default value +- Default: This value is the default - MailFolders - PeopleFolders - Groups @@ -1010,7 +1010,7 @@ Accept wildcard characters: False The PreferAccessibleContent parameter specifies whether to prefer accessible content in Outlook on the web. Valid values are: - $true: Prefer accessible content. -- $false: Don't prefer accessible content. This is the default value. +- $false: Don't prefer accessible content. This value is the default. ```yaml Type: Boolean @@ -1213,7 +1213,7 @@ Accept wildcard characters: False The ShowPreviewTextInListView parameter specifies whether to show preview text for messages in list view in Outlook on the web. Valid values are: -- $true: Show preview text for messages in list view. This is the default value. +- $true: Show preview text for messages in list view. This value is the default. - $false: Don't show preview text for messages in list view. ```yaml @@ -1235,7 +1235,7 @@ Accept wildcard characters: False The ShowReadingPaneOnFirstLoad parameter specifies whether to show the reading pane when the user opens in Outlook on the web for the first time. Valid values are: - $true: Show the reading pane when the user opens Outlook on the web for the first time. -- $false: Don't show the reading pane when the user opens Outlook on the web for the first time. This is the default value. +- $false: Don't show the reading pane when the user opens Outlook on the web for the first time. This value is the default. ```yaml Type: Boolean @@ -1255,7 +1255,7 @@ Accept wildcard characters: False The ShowSenderOnTopInListView parameter specifies whether to show the message sender on top in list view in Outlook on the web. Valid values are: -- $true: Show the message sender on top in list view. This is the default value. +- $true: Show the message sender on top in list view. This value is the default. - $false: Don't show the message sender on top in list view. ```yaml @@ -1276,7 +1276,7 @@ Accept wildcard characters: False The ShowUpNext parameter specifies whether the next upcoming event should be shown above the mail list view in Outlook on the web. Valid values are: -- $true: Show the next upcoming event above the mail list view. This is the default value. +- $true: Show the next upcoming event above the mail list view. This value is the default. - $false: Don't show the next upcoming event above the mail list view. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md index 0edf3ce269..746b24f47e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md @@ -42,11 +42,11 @@ Set-MailboxPlan [-Identity] ## DESCRIPTION A mailbox plan is a template that automatically configures mailbox properties. Mailbox plans correspond to license types, and are applied when you license the user. The availability of a mailbox plan is determined by your selections when you enroll in the service and the age of your organization. -Modifying the settings in a mailbox plan doesn't affect existing mailboxes that were created using the mailbox plan. The only way to use a mailbox plan to modify the settings on an existing mailbox is to assign a different license to the user, which will apply the corresponding mailbox plan to the mailbox. +Modifying the settings in a mailbox plan doesn't affect existing mailboxes that were created using the mailbox plan. The only way to use a mailbox plan to modify the settings on an existing mailbox is to assign a different license to the user, which applies the corresponding mailbox plan to the mailbox. Each mailbox plan has a corresponding Client Access services (CAS) mailbox plan with the same name and display name value. You can use the Set-CasMailboxPlan cmdlet to enable or disable POP3, IMAP4 or Exchange ActiveSync (EAS) access to new or newly-enabled mailboxes, and you can specify the Outlook on the web (formerly known as Outlook Web App) mailbox policy for the mailboxes. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -158,11 +158,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value. -The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. +The maximum value is determined by the mailbox plan. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. ```yaml Type: Unlimited @@ -188,11 +188,11 @@ When you enter a value, qualify the value with one of the following units: - KB (kilobytes) - MB (megabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 150 MB. The default value is 36 MB. -The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. +The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. Use this parameter to change the MaxReceiveSize value for new mailboxes that you create. Use the MaxReceiveSize parameter on the Set-Mailbox cmdlet to configure the value on existing mailboxes. @@ -222,11 +222,11 @@ When you enter a value, qualify the value with one of the following units: - KB (kilobytes) - MB (megabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is a number up to 150 MB. The default value is 35 MB. -The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. +The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. Use this parameter to change the MaxSendSize value for new mailboxes that you create. Use the MaxSendSize parameter on the Set-Mailbox cmdlet to configure the value on existing mailboxes. @@ -258,11 +258,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value. -The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. +The maximum value is determined by the mailbox plan. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan. ```yaml Type: Unlimited @@ -290,7 +290,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values. @@ -375,7 +375,7 @@ If you don't set a value for this parameter, existing mailboxes are also updated **Note**: Specifying a value for this parameter has the following potential issues: - If the value of this parameter is not blank ($null), then the specified retention policy must be the default Exchange retention policy that's configured for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. -- If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value. +- If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox is overwritten when changing licenses. You need to manually reset the RetentionPolicy to the original value. - Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates. For more information, see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans). diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md index 3349fad8d4..d9fdf8c9c0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md @@ -13,7 +13,7 @@ title: Set-MailboxRegionalConfiguration # Set-MailboxRegionalConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxRegionalConfiguration cmdlet to modify the regional settings of a mailbox. You can modify the date format, time format, time zone and language of the mailbox. @@ -63,7 +63,7 @@ Set-MailboxRegionalConfiguration [-MailboxLocation ] ## DESCRIPTION As shown in Example 5, you might need to set the DateFormat and TimeFormat parameter values to $null when you change the Language parameter value and you receive an error about invalid DateFormat values. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -180,7 +180,7 @@ Accept wildcard characters: False The DateFormat parameter specifies a valid date format based on the current or specified language for the mailbox. For example, if the language is set to en-US, valid DateFormat parameter values include: -- M/d/yyyy: This is the default value for en-US. +- M/d/yyyy: This value is the default for en-US. - M/d/yy - MM/dd/yy - MM/dd/yyyy @@ -286,7 +286,7 @@ Accept wildcard characters: False The TimeFormat parameter specifies a valid time format based on the current or specified language value for the mailbox. For example, if the language is set to en-us, valid TimeFormat parameter values include: -- h:mm tt: This is the default value for en-US. +- h:mm tt: This value is the default for en-US. - hh:mm tt - H:mm - HH:mm diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md index 31a09c45f0..fc864e68e8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md @@ -13,9 +13,9 @@ title: Set-MailboxRestoreRequest # Set-MailboxRestoreRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. -Use the Set-MailboxRestoreRequest cmdlet to change restore request options after the request has been created. You can use this cmdlet to recover from failed restore requests. +Use the Set-MailboxRestoreRequest cmdlet to change restore request options after the request is created. You can use this cmdlet to recover from failed restore requests. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -61,7 +61,7 @@ Set-MailboxRestoreRequest [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -133,7 +133,7 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -261,7 +261,7 @@ Valid input for this parameter is an integer or the value unlimited. The default If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -286,7 +286,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md index 87fa9b177c..0e5035c4d9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md @@ -13,7 +13,7 @@ title: Set-MailboxSearch # Set-MailboxSearch ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxSearch cmdlet to modify an existing mailbox search. @@ -65,7 +65,7 @@ If the In-Place eDiscovery search you want to modify is running, stop it before For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and [In-Place Hold and Litigation Hold in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/holds/holds). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -112,7 +112,7 @@ Accept wildcard characters: False The AllPublicFolderSources parameter specifies whether to include all public folders in the organization in the search. Valid values are: - $true: All public folders are included in the search. This value is required when the value of the AllSourceMailboxes parameter is $falseand you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). -- $false: No public folders are included in the search. This is the default value. You can use this value when the value of the AllSourceMailboxes parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). +- $false: No public folders are included in the search. This value is the default. You can use this value when the value of the AllSourceMailboxes parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean @@ -133,7 +133,7 @@ Accept wildcard characters: False The AllSourceMailboxes parameter specifies whether to include all mailboxes in the search. Valid values are: - $true: All mailboxes are included in the search. This value is required when the value of the AllPublicFolderSources parameter is $falseand you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). -- $false: All mailboxes aren't included in the search. This is the default value. You can use this value when the value of the AllPublicFolderSources parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). +- $false: All mailboxes aren't included in the search. This value is the default. You can use this value when the value of the AllPublicFolderSources parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]). ```yaml Type: Boolean @@ -274,7 +274,7 @@ Accept wildcard characters: False The ExcludeDuplicateMessages parameter eliminates duplication of messages across mailboxes in an In-Place eDiscovery search. Valid values are: -- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This is the default value. +- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This value is the default. - $false: Copy all instances of a message if the same message exists in multiple folders or mailboxes. ```yaml @@ -334,7 +334,7 @@ Accept wildcard characters: False The IncludeUnsearchableItems parameter specifies whether items that couldn't be indexed by Exchange Search should be included in the results. Valid values are: - $true: Unsearchable items are included in the results. -- $false: Unsearchable items aren't included in the results. This is the default value. +- $false: Unsearchable items aren't included in the results. This value is the default. Unsearchable items aren't placed on hold for a query-based In-Place Hold. If you need to place unsearchable items on hold, you need to create an indefinite hold (a hold without specifying any search parameters, which provides functionality similar to Litigation Hold. @@ -357,11 +357,11 @@ Accept wildcard characters: False The InPlaceHoldEnabled parameter specifies whether to set an In-Place Hold on items in the search results. Valid values are: - $true: In-Place Hold is enabled on the search results. -- $false: In-Place Hold isn't enabled on the search results. This is the default value. +- $false: In-Place Hold isn't enabled on the search results. This value is the default. You can't set an In-Place Hold on the search results when the AllSourceMailboxes parameter is $true. -If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command may succeed but the mailboxes are not placed on In-Place Hold. +If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command might succeed but the mailboxes are not placed on In-Place Hold. ```yaml Type: Boolean @@ -382,7 +382,7 @@ Accept wildcard characters: False The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold onthe mailbox items (all items or the mailbox items that are returned in the search query results). You use this parameter with the InPlaceHoldEnabled parameter to set an In-Place Hold. The duration is calculated from the time the item is received or created in the mailbox. Valid values are: - An integer. -- The value unlimited. This is the default value. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false. +- The value unlimited. This value is the default. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false. ```yaml Type: Unlimited @@ -422,7 +422,7 @@ Accept wildcard characters: False The LogLevel parameter specifies a logging level for the mailbox search. Valid values are: -- Basic: Basic details of the search are kept. This is the default value. +- Basic: Basic details of the search are kept. This value is the default. - Full: In addition to details in the Basic logging level, a full list of all messages returned is included. - Suppress: Logging is suppressed. No logs are kept. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md index 144b54ea09..7a2d21ab4e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md @@ -34,7 +34,7 @@ Set-MailboxSentItemsConfiguration [-Confirm] ## DESCRIPTION By default, when you use Send As or Send On Behalf Of to send a message from another mailbox, the message is saved in your Sent Items folder (not in the Sent Items folder of the source mailbox). In Microsoft Exchange Server 2010 Service Pack 3 (SP3), you can save copies messages in the Sent Items folder of the sender and the source mailbox. For example, consider a shared mailbox that receives customer feedback and is monitored by multiple users. When someone responds to a message in the shared mailbox, you can save the message in the Sent Items folder of the shared mailbox and the sender's mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -121,7 +121,7 @@ Accept wildcard characters: False The SendAsItemsCopiedTo parameter specifies where messages that are sent from the mailbox using Send As permission are saved. Valid values are: -- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This is the default value. +- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This value is the default. - SenderAndFrom: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message, and in the Sent Items folder of the mailbox. ```yaml @@ -142,7 +142,7 @@ Accept wildcard characters: False The SendOnBehalfOfItemsCopiedTo parameter specifies where messages that are sent from the mailbox using Send On Behalf Of permission are saved. Valid values are: -- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This is the default value. +- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This value is the default. - SenderAndFrom: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message, and in the Sent Items folder of the mailbox. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md index bed67ec315..7748bd0a40 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md @@ -131,7 +131,7 @@ Set-MailboxServer [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -140,7 +140,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Set-MailboxServer -Identity MBX02 -CalendarRepairWorkCycle 7.00:00:00 -CalendarRepairWorkCycleCheckpoint 7.00:00:00 ``` -In Exchange 2013, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2013, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 2 ```powershell @@ -154,42 +154,42 @@ This example changes some of the default settings of the Calendar Repair Assista Set-MailboxServer -Identity MBX02 -CalendarRepairWorkCycle 7.00:00:00 -CalendarRepairWorkCycleCheckpoint 7.00:00:00 ``` -In Exchange 2010, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2010, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 4 ```powershell Set-MailboxServer -Identity MBX02 -ManagedFolderWorkCycle 10.00:00:00 -ManagedFolderWorkCycleCheckpoint 10.00:00:00 ``` -In Exchange 2013, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2013, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 5 ```powershell Set-MailboxServer -Identity MBX02 -ManagedFolderWorkCycle 10.00:00:00 -ManagedFolderWorkCycleCheckpoint 10.00:00:00 ``` -In Exchange 2010, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2010, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 6 ```powershell Set-MailboxServer -Identity MBX02 -SharingPolicyWorkCycle 7.00:00:00 -SharingPolicyWorkCycleCheckpoint 7.00:00:00 -SharingSyncWorkCycle 7.00:00:00 -SharingSyncWorkCycleCheckpoint 7.00:00:00 ``` -In Exchange 2013, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2013, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 7 ```powershell Set-MailboxServer -Identity MBX02 -SharingPolicyWorkCycle 7.00:00:00 -SharingPolicyWorkCycleCheckpoint 7.00:00:00 -SharingSyncWorkCycle 7.00:00:00 -SharingSyncWorkCycleCheckpoint 7.00:00:00 ``` -In Exchange 2010, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over. +In Exchange 2010, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over. ### Example 8 ```powershell Set-MailboxServer -Identity MBX02 -TopNWorkCycle 10.00:00:00 -TopNWorkCycleCheckpoint 10.00:00:00 -UMReportingWorkCycle 10.00:00:00 -UMReportingWorkCycleCheckpoint 10.00:00:00 ``` -In Exchange 2010, this example throttles the TopN Words Assistant and the Unified Messaging Reporting Assistant for mailboxes that reside on the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes that have Unified Messaging enabled will be scanned, and at the end of the period, the process will start over. +In Exchange 2010, this example throttles the TopN Words Assistant and the Unified Messaging Reporting Assistant for mailboxes that reside on the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes that have Unified Messaging enabled are scanned, and at the end of the period, the process starts over. ## PARAMETERS @@ -243,7 +243,7 @@ The AutoDatabaseMountDial parameter specifies the automatic database mount behav - GoodAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to six. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than six, the database doesn't automatically mount. When the copy queue length is less than or equal to six, Exchange attempts to replicate the remaining logs to the passive copy and mounts the database. - Lossless: The database doesn't automatically mount until all logs that were generated on the active copy have been copied to the passive copy. This setting also causes Active Manager's best copy selection algorithm to sort potential candidates for activation based on the database copy's activation preference value and not its copy queue length. -The default value is GoodAvailability. If you specify either BestAvailability or GoodAvailability, and all of the logs from the active copy haven't been replicated to the passive copy, you may lose some mailbox data. However, the Safety Net feature, (which is enabled by default) helps protect against data loss by resubmitting messages that are in Safety Net. +The default value is GoodAvailability. If you specify either BestAvailability or GoodAvailability, and all of the logs from the active copy haven't been replicated to the passive copy, you might lose some mailbox data. However, the Safety Net feature, (which is enabled by default) helps protect against data loss by resubmitting messages that are in Safety Net. ```yaml Type: AutoDatabaseMountDial @@ -297,7 +297,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. If you enter the value unlimited, no size limit is imposed on the calendar repair log directory. @@ -402,7 +402,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The CalendarRepairMissingItemFixDisabled parameter specifies whether the Calendar Repair Assistant won't fix missing calendar items in mailboxes on the Mailbox server.Valid input for this parameter is $true or $false. The default value is $false. +The CalendarRepairMissingItemFixDisabled parameter specifies whether the Calendar Repair Assistant fixes missing calendar items in mailboxes on the Mailbox server.Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean @@ -481,13 +481,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The CalendarRepairWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be scanned by the Calendar Repair Assistant. The default value is 1 day. +The CalendarRepairWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are scanned by the Calendar Repair Assistant. The default value is 1 day. -Calendars that have inconsistencies will be flagged and repaired according to the interval specified by the CalendarRepairWorkCycleCheckpoint parameter. +Calendars that have inconsistencies are flagged and repaired according to the interval specified by the CalendarRepairWorkCycleCheckpoint parameter. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -507,11 +507,11 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The CalendarRepairWorkCycleCheckpoint parameter specifies the time span at which all mailboxes on the Mailbox server will be identified as needing work completed on them. The default value is 1 day. +The CalendarRepairWorkCycleCheckpoint parameter specifies the time span at which all mailboxes on the Mailbox server are identified as needing work completed on them. The default value is 1 day. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -590,11 +590,11 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The DatabaseCopyActivationDisabledAndMoveNow parameter specifies whether to prevent databases from being mounted on this Mailbox server if there are other healthy copies of the databases on other Mailbox servers. It will also immediately move any mounted databases on the server to other servers if copies exist and are healthy. +The DatabaseCopyActivationDisabledAndMoveNow parameter specifies whether to prevent databases from being mounted on this Mailbox server if there are other healthy copies of the databases on other Mailbox servers. It also immediately moves any mounted databases on the server to other servers if copies exist and are healthy. Valid input for this parameter is $true or $false. The default value is $false. -Setting this parameter to $true won't cause databases to move to a server that has the DatabaseCopyAutoActivationPolicy parameter set to Blocked. +Setting this parameter to $true doesn't cause databases to move to a server that has the DatabaseCopyAutoActivationPolicy parameter set to Blocked. ```yaml Type: Boolean @@ -614,9 +614,9 @@ Accept wildcard characters: False The DatabaseCopyAutoActivationPolicy parameter specifies the type of automatic activation available for mailbox database copies on the specified Mailbox server. Valid values for this parameter are: -- Blocked: Databases can't be automatically activated on the specified Mailbox server. In Exchange 2013 prior to Cumulative Update 7 (CU7), this setting stops server locator requests to the specified server, which prevents all client access to manually activated databases on the server if all DAG members are configured with a value of Blocked. In Exchange 2013 CU7 or later versions of Exchange, server locator requests are sent to a blocked server if no other Mailbox servers are available, thus client access is not impacted. +- Blocked: Databases can't be automatically activated on the specified Mailbox server. In Exchange 2013 prior to Cumulative Update 7 (CU7), this setting stops server locator requests to the specified server, which prevents all client access to manually activated databases on the server if all DAG members are configured with a value of Blocked. In Exchange 2013 CU7 or later versions of Exchange, server locator requests are sent to a blocked server if no other Mailbox servers are available, thus client access isn't affected. - IntrasiteOnly: The database copy is allowed to be activated only on Mailbox servers in the same Active Directory site. This prevents cross-site failover and activation. -- Unrestricted: There are no special restrictions on activating mailbox database copies on the specified Mailbox server. This is the default value. +- Unrestricted: There are no special restrictions on activating mailbox database copies on the specified Mailbox server. This value is the default. ```yaml Type: DatabaseCopyAutoActivationPolicyType @@ -1009,9 +1009,9 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010. -The IrmLogPath parameter specifies the default IRM log directory location. The default value is C:\\Program Files\\Microsoft\\Exchange Server\\ v14\\Logging\\IRMLogs. +The IrmLogPath parameter specifies the default IRM log directory location. The default value is %ExchangeInstallPath%Logging\\IRMLogs. -If you set the value of the IrmLogPath parameter to $null, you effectively disable IRM logging. However, if you set the value of the IrmLogPath parameter to $null when the value of the IrmLogEnabled parameter is $true, Exchange will log errors in the Application event log. The preferred way for disabling IRM logging is to set the IrmLogEnabled parameter to $false. +If you set the value of this parameter to $null, you effectively disable IRM logging. However, if the value of the IrmLogEnabled parameter is $true, Exchange adds errors to the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false. ```yaml Type: LocalLongFullPath @@ -1029,9 +1029,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The IsExcludedFromProvisioning parameter specifies that the Mailbox server isn't considered by the OAB provisioning load balancer. Valid input for this parameter is $true or $false. The default value is $false. +The IsExcludedFromProvisioning parameter specifies that the Mailbox server isn't considered by the OAB provisioning load balancer. Valid values are: -If you specify$true, the server won't be used for provisioning a new OAB or for moving existing OABs. +- $true: The server isn't used for provisioning new OABs or for moving existing OABs. +- $false: The server can be used for provisioning new OABs or for moving existing OABs. This value is the default. ```yaml Type: Boolean @@ -1131,7 +1132,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The default value is unlimited, which means no size limit is imposed on the managed folder log directory. @@ -1187,7 +1188,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. If you enter the value unlimited, no size limit is imposed on a managed folder log file. @@ -1334,13 +1335,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The ManagedFolderWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be processed by the Managed Folder Assistant. The default value is 1 day. +The ManagedFolderWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are processed by the Managed Folder Assistant. The default value is 1 day. The Managed Folder Assistant applies retention policies according to the ManagedFolderWorkCycleCheckpoint interval. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Managed Folder Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Managed Folder Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -1360,9 +1361,9 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The ManagedFolderWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day. +The ManagedFolderWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 1 day. -Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle. +Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. @@ -1404,7 +1405,7 @@ Accept wildcard characters: False The MaximumActiveDatabases parameter specifies the maximum number of databases that can be mounted on the Mailbox server. -When the maximum number is reached, the database copies on the server won't be activated if a failover or switchover occurs. If the copies are already active on a server, the Information Store on the server won't allow databases to be mounted. +When the maximum number is reached, the database copies on the server isn't activated if a failover or switchover occurs. If the copies are already active on a server, the Information Store on the server doesn't allow databases to be mounted. The default value is blank ($null), which means no maximum value is configured. @@ -1681,7 +1682,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2013. -The OABGeneratorWorkCycle parameter specifies the time span in which the OAB generation on the Mailbox server will be processed. The default value is 8 hours. +The OABGeneratorWorkCycle parameter specifies the time span in which the OAB generation on the Mailbox server are processed. The default value is 8 hours. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. @@ -2034,13 +2035,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The SharingPolicyWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be scanned by the Sharing Policy Assistant. The default value is 1 day. +The SharingPolicyWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are scanned by the Sharing Policy Assistant. The default value is 1 day. The Sharing Policy Assistant scans all mailboxes and enables or disables sharing policies according to the interval specified by the SharingPolicyWorkCycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -2060,13 +2061,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The SharingPolicyWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day. +The SharingPolicyWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 1 day. -Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle. +Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -2086,13 +2087,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The SharingSyncWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be synced to the cloud-based service by the Sharing Sync Assistant. The default value is 3 hours. +The SharingSyncWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are synced to the cloud-based service by the Sharing Sync Assistant. The default value is 3 hours. -Mailboxes that require syncing will be synced according to the interval specified by the SharingSyncWorkCycleCheckpoint parameter. +Mailboxes that require syncing are synced according to the interval specified by the SharingSyncWorkCycleCheckpoint parameter. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant will then process all mailboxes on this server every 8 hours. +For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant then processes all mailboxes on this server every 8 hours. ```yaml Type: EnhancedTimeSpan @@ -2112,13 +2113,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The SharingSyncWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 3 hours. +The SharingSyncWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 3 hours. -Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle. +Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. -For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant will then process all mailboxes on this server every 8 hours. +For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant then processes all mailboxes on this server every 8 hours. ```yaml Type: EnhancedTimeSpan @@ -2138,7 +2139,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2013. -The SiteMailboxWorkCycle parameter specifies the time span in which the site mailbox information on the Mailbox server will be processed. The default value is 6 hours. +The SiteMailboxWorkCycle parameter specifies the time span in which the site mailbox information on the Mailbox server are processed. The default value is 6 hours. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. @@ -2426,13 +2427,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The TopNWorkCycle parameter specifies the time span in which all mailboxes that have Unified Messaging on the Mailbox server will be scanned by the TopN Words Assistant. The default value is 7 days. +The TopNWorkCycle parameter specifies the time span in which all mailboxes that have Unified Messaging on the Mailbox server are scanned by the TopN Words Assistant. The default value is 7 days. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. The TopN Words Assistant scans voice mail for the most frequently used words to aid in transcription. The most common words are then indexed according to the interval specified by the TopNWorkCycleCheckpoint parameter. -For example, to specify 10 days for this parameter, use 10.00:00:00. The TopN Words Assistant will then process all mailboxes on which Unified Messaging is enabled on this server every 10 days. +For example, to specify 10 days for this parameter, use 10.00:00:00. The TopN Words Assistant then processes all mailboxes on which Unified Messaging is enabled on this server every 10 days. ```yaml Type: EnhancedTimeSpan @@ -2452,13 +2453,13 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The TopNWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day. +The TopNWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 1 day. -Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle. +Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The TopN Words Assistant will then process all mailboxes on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The TopN Words Assistant then processes all mailboxes on this server every 2 days. ```yaml Type: EnhancedTimeSpan @@ -2478,15 +2479,15 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The UMReportingWorkCycle parameter specifies the time span in which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server will be scanned by the Unified Messaging Reporting Assistant. The default value is 1 day. +The UMReportingWorkCycle parameter specifies the time span in which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server are scanned by the Unified Messaging Reporting Assistant. The default value is 1 day. The Unified Messaging Reporting Assistant updates the Call Statistics reports by reading Unified Messaging call data records for an organization on a regular basis. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. -For example, to specify 2 days for this parameter, use 2.00:00:00. The Unified Messaging Reporting Assistant will then process all mailboxes that have Unified Messaging enabled on this server every 2 days. +For example, to specify 2 days for this parameter, use 2.00:00:00. The Unified Messaging Reporting Assistant then processes all mailboxes that have Unified Messaging enabled on this server every 2 days. -Changing the default work cycle for this assistant might impact the performance of the Mailbox server. +Changing the default work cycle for this assistant might affect the performance of the Mailbox server. ```yaml Type: EnhancedTimeSpan @@ -2506,7 +2507,7 @@ Accept wildcard characters: False This parameter is available only in Exchange Server 2010 or Exchange Server 2013. -The UMReportingWorkCycleCheckpoint parameter specifies the time span at which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server will be marked by processing. The default value is 1 day. +The UMReportingWorkCycleCheckpoint parameter specifies the time span at which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server are marked by processing. The default value is 1 day. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md index 5dc0433512..ad74531f90 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md @@ -13,7 +13,7 @@ title: Set-MailboxSpellingConfiguration # Set-MailboxSpellingConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MailboxSpellingConfiguration cmdlet to modify Outlook on the web spelling checker options for a specified user. For example, you can set the dictionary language and configure the spelling checker to ignore mixed digits or words in all uppercase. @@ -34,7 +34,7 @@ Set-MailboxSpellingConfiguration [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md index 1cd0ab0e6a..98eb1644f0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md @@ -72,7 +72,7 @@ Set-MailboxTransportService [-Identity] ## DESCRIPTION The Mailbox Transport service runs on all Mailbox servers and is responsible for delivering messages to and accepting messages from local mailbox databases using a remote procedure call (RPC). The Mailbox Transport service also uses SMTP to send messages to and from the Transport service that runs on all Mailbox servers for routing messages to their ultimate destinations. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -178,7 +178,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log directory. @@ -208,7 +208,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log files. @@ -336,7 +336,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxDeliveryAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log directory. @@ -366,7 +366,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxDeliveryAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log files. @@ -424,7 +424,7 @@ Accept wildcard characters: False The MailboxDeliveryConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Valid values are: -- None: Protocol logging is disabled for the mailbox delivery Receive connector. This is the default value. +- None: Protocol logging is disabled for the mailbox delivery Receive connector. This value is the default. - Verbose: Protocol logging is enabled for the mailbox delivery Receive connector. The location of the log files is controlled by the ReceiveProtocolLogPath parameter. ```yaml @@ -445,7 +445,7 @@ Accept wildcard characters: False The MailboxDeliveryConnectorSmtpUtf8Enabled parameters or disables email address internationalization (EAI) support for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Valid values are: -- $true: Mail can be delivered to local mailboxes that have international characters in email addresses. This is the default value +- $true: Mail can be delivered to local mailboxes that have international characters in email addresses. This value is the default - $false: Mail can't be delivered to local mailboxes that have international characters in email addresses. ```yaml @@ -514,7 +514,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxDeliveryThrottlingLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryThrottlingLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the mailbox delivery throttling log directory. @@ -544,7 +544,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxDeliveryThrottlingLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryThrottlingLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the mailbox delivery throttling log files. @@ -632,7 +632,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxSubmissionAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxSubmissionAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log directory. @@ -662,7 +662,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of the MailboxSubmissionAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxSubmissionAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log files. @@ -780,7 +780,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you may have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null. +The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you might have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null. ```yaml Type: SmtpAddress @@ -836,7 +836,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be greater than or equal to the value of the ReceiveProtocolLogMaxFileSize parameter. @@ -870,7 +870,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the ReceiveProtocolLogMaxDirectorySize parameter. @@ -944,7 +944,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the routing table log directory. @@ -1018,7 +1018,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value of this parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter. @@ -1052,7 +1052,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The value this parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md index 9dc6e6811f..d697405ee3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md @@ -13,7 +13,7 @@ title: Set-MalwareFilterPolicy # Set-MalwareFilterPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MalwareFilterPolicy cmdlet to modify malware filter policies in your organization. @@ -55,7 +55,7 @@ Set-MalwareFilterPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -132,7 +132,7 @@ This parameter is available only in on-premises Exchange. The Action parameter specifies the action to take when malware is detected in a message. Valid values are: -- DeleteMessage: Handles the message without notifying the recipients. This is the default value. +- DeleteMessage: Handles the message without notifying the recipients. This value is the default. - DeleteAttachmentAndUseDefaultAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the default alert text. - DeleteAttachmentAndUseCustomAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the custom alert text specified by the CustomAlertText parameter. @@ -175,7 +175,7 @@ This parameter is available only in on-premises Exchange. The BypassInboundMessages parameter enables or disables malware filtering on incoming messages (messages entering the organization). Valid values are: - $true: Malware filtering is disabled on inbound messages. -- $false: Malware filtering is enabled on inbound messages. This is the default value. +- $false: Malware filtering is enabled on inbound messages. This value is the default. ```yaml Type: Boolean @@ -198,7 +198,7 @@ This parameter is available only in on-premises Exchange. The BypassOutboundMessages parameter enables or disables malware filtering on outgoing messages (messages leaving the organization). Valid values are: - $true: Malware filtering is disabled on outbound messages. -- $false: Malware filtering is enabled on outbound messages. This is the default value. +- $false: Malware filtering is enabled on outbound messages. This value is the default. ```yaml Type: Boolean @@ -452,7 +452,7 @@ Accept wildcard characters: False The EnableExternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from external senders, a notification messages is sent to the email address that's specified by the ExternalSenderAdminAddress parameter. -- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This is the default value. +- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This value is the default. **Note**: Admin notifications are sent only for _attachments_ that are classified as malware. @@ -477,7 +477,7 @@ This parameter is available only in on-premises Exchange. The EnableExternalSenderNotifications parameter enables or disables sending notification messages to external senders for malware detections in their messages. Valid values are: - $true: When malware is detected in a message from an external sender, send them a notification message. -- $false: Don't send malware detection notification messages to external message senders. This is the default value. +- $false: Don't send malware detection notification messages to external message senders. This value is the default. ```yaml Type: Boolean @@ -499,7 +499,7 @@ This parameter is available only in the cloud-based service. The EnableFileFilter parameter enables or disables the common attachments filter (also known as common attachment blocking). Valid values are: -- $true: The common attachments filter is enabled. This is the default value. +- $true: The common attachments filter is enabled. This value is the default. - $false: The common attachments filter is disabled. You specify the file types using the FileTypes parameter. @@ -525,7 +525,7 @@ Accept wildcard characters: False The EnableInternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from internal senders, a notification messages is sent to the email address that's specified by the InternalSenderAdminAddress parameter. -- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This is the default value. +- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This value is the default. **Note**: Admin notifications are sent only for _attachments_ that are classified as malware. @@ -550,7 +550,7 @@ This parameter is available only in on-premises Exchange. The EnableInternalSenderNotifications parameter enables or disables sending notification messages to internal senders for malware detections in their messages. Valid values are: - $true: When malware is detected in a message from an internal sender, send them a notification message. -- $false: Don't send malware detection notification messages to internal message senders. This is the default value. +- $false: Don't send malware detection notification messages to internal message senders. This value is the default. ```yaml Type: Boolean @@ -593,7 +593,7 @@ This parameter is available only in the cloud-based service. The FileTypeAction parameter specifies what happens to messages that contain one or more attachments where the file extension is included in the FileTypes parameter (the common attachments filter). Valid values are: - Quarantine: Quarantine the message. Whether or not the recipient is notified depends on the quarantine notification settings in the quarantine policy that's selected for the malware filter policy by the QuarantineTag parameter. -- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This is the default value. +- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This value is the default. This parameter is meaningful only when the value of the EnableFileFilter parameter is $true. @@ -753,7 +753,7 @@ This parameter is available only in the cloud-based service. The ZapEnabled parameter enables or disables zero-hour auto purge (ZAP) for malware in cloud mailboxes. ZAP detects malware in unread messages that have already been delivered to the user's Inbox. Valid values are: -- $true: ZAP for malware is enabled. This is the default value. In Exchange Server, unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. In the cloud-based service, the messages are quarantined. +- $true: ZAP for malware is enabled. This value is the default. In Exchange Server, unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. In the cloud-based service, the messages are quarantined. - $false: ZAP for malware is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md index 92dce6658f..c9a8199c78 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md @@ -13,7 +13,7 @@ title: Set-MalwareFilterRule # Set-MalwareFilterRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MalwareFilterRule cmdlet to modify malware filter rules in your organization. @@ -43,7 +43,7 @@ Set-MalwareFilterRule [-Identity] > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Anti-malware policies](https://learn.microsoft.com/defender-office-365/anti-malware-protection-about#anti-malware-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md index dc4dd0fd54..3f204ae47a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md @@ -41,7 +41,7 @@ Set-MalwareFilteringServer [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -125,7 +125,7 @@ Accept wildcard characters: False The DeferAttempts parameter specifies the maximum number of times to defer a message that can't be scanned by the Malware agent. Valid input for this parameter is an integer between 1 and 5. The default value is 3. -After the maximum number of deferrals is reached, the action taken by the Malware agent depends on the error. For scan timeouts and engine errors, the action is to fail the message and return a non-delivery report (NDR) to the sender immediately after the last defer attempt. For all other errors, the message is retried for up to 48 hours, with each retry attempt taking place one hour longer than the last one. For example, starting after the last defer attempt, the first retry attempt will occur in 1 hour, the next retry attempt will occur 2 hours after that, the next retry attempt will occur 3 hours after the second retry attempt, and so on for up to 48 hours. After 48 hours have elapsed, the action is to fail the message and return a non-delivery report (NDR) to the sender. +After the maximum number of deferrals is reached, the action taken by the Malware agent depends on the error. For scan timeouts and engine errors, the action is to fail the message and return a non-delivery report (NDR) to the sender immediately after the last defer attempt. For all other errors, the message is retried for up to 48 hours, with each retry attempt taking place one hour longer than the last one. For example, starting after the last defer attempt, the first retry attempt occurs in 1 hour, the next retry attempt occurs 2 hours after that, the next retry attempt occurs 3 hours after the second retry attempt, and so on for up to 48 hours. After 48 hours have elapsed, the action is to fail the message and return a non-delivery report (NDR) to the sender. ```yaml Type: Int32 @@ -188,7 +188,7 @@ Accept wildcard characters: False The ForceRescan parameter specifies that messages should be scanned by the malware agent, even if the message was already scanned by cloud-based protection. Valid values are: - $true: Messages from cloud-based organizations are scanned by the malware agent. -- $false: Messages from cloud-based organizations aren't scanned by the malware agent. This is the default value. +- $false: Messages from cloud-based organizations aren't scanned by the malware agent. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md index ddf16e2394..575e6d948f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md @@ -44,7 +44,7 @@ Managed content settings are settings that you apply to managed folders to contr Although the New-ManagedContentSettings cmdlet has the MessageClass parameter, the Set-ManagedContentSettings cmdlet doesn't. If you want to change the message type to which content settings apply, you must delete and then re-create the content settings. For more information about the MessageClass parameter, see [New-ManagedContentSettings](https://learn.microsoft.com/powershell/module/exchangepowershell/new-managedcontentsettings). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md index a5a7ff9c53..a184b0b51e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md @@ -42,7 +42,7 @@ The Set-ManagedFolder cmdlet modifies the specified parameters of a managed fold The Set-ManagedFolder cmdlet accepts a managed custom folder or an identity string as pipelined input. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -242,7 +242,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items may be added. Mailbox sizes can be specified in kilobytes (KB) or megabytes (MB), for example, as 100KB or 5MB. The StorageQuota parameter is valid for managed custom folders in Outlook 2007. +The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items might be added. Mailbox sizes can be specified in kilobytes (KB) or megabytes (MB), for example, as 100KB or 5MB. The StorageQuota parameter is valid for managed custom folders in Outlook 2007. ```yaml Type: Unlimited diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md index ab10d066e9..e42e17a347 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md @@ -32,7 +32,7 @@ Set-ManagedFolderMailboxPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md index 0c8c86b88c..a0c404aed0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md @@ -13,7 +13,7 @@ title: Set-ManagementRoleAssignment # Set-ManagementRoleAssignment ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ManagementRoleAssignment cmdlet to modify existing management role assignments. @@ -106,7 +106,7 @@ You can create custom management scopes using the New-ManagementScope cmdlet and For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md index de99ac0cc4..5ab67ee695 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md @@ -13,7 +13,7 @@ title: Set-ManagementRoleEntry # Set-ManagementRoleEntry ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ManagementRoleEntry cmdlet to change the available parameters on an existing management role entry. @@ -39,7 +39,7 @@ The Set-ManagementRoleEntry cmdlet changes the available parameters on an existi For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -69,7 +69,7 @@ This example adds the DisplayName and ForwardingAddress parameters to the Set-Ma Set-ManagementRoleEntry "IT Scripts\MailboxAudit" -Parameters Location -AddParameter -UnScopedTopLevel ``` -In on-premises Exchange, this example adds the Location parameter to the MailboxAudit custom script on the IT Scripts unscoped top level role. Note that the UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default. +In on-premises Exchange, this example adds the Location parameter to the MailboxAudit custom script on the IT Scripts unscoped top level role. The UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md index 30b702cd34..8b671cdcef 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md @@ -13,7 +13,7 @@ title: Set-ManagementScope # Set-ManagementScope ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ManagementScope cmdlet to change an existing management scope. @@ -57,11 +57,11 @@ Set-ManagementScope [-Identity] ``` ## DESCRIPTION -If you change a scope that has been associated with management role assignments using the New-ManagementRoleAssignment cmdlet, the updated scope applies to all the associated role assignments. For more information about changing scopes, see [Change a role scope](https://learn.microsoft.com/exchange/change-a-role-scope-exchange-2013-help). +If you change a scope that is associated with management role assignments using the New-ManagementRoleAssignment cmdlet, the updated scope applies to all the associated role assignments. For more information about changing scopes, see [Change a role scope](https://learn.microsoft.com/exchange/change-a-role-scope-exchange-2013-help). For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md index 0b55d95639..bd261af787 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md @@ -37,7 +37,7 @@ Set-MapiVirtualDirectory [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -146,7 +146,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -166,7 +166,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -187,8 +187,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md index 6c39983580..c5de61e4a9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md @@ -13,7 +13,7 @@ title: Set-MessageClassification # Set-MessageClassification ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MessageClassification cmdlet to configure an existing message classification instance in your organization. @@ -38,7 +38,7 @@ Set-MessageClassification [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -141,19 +141,19 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that may be applied to a specified message. Valid values are: +The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that might be applied to a specified message. Valid values are: - Highest - Higher - High - MediumHigh -- Medium (This is the default value) +- Medium (default value) - MediumLow - Low - Lower - Lowest -Although Outlook only lets a user specify a single classification for a message, transport rules may apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter. +Although Outlook only lets a user specify a single classification for a message, transport rules might apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter. ```yaml Type: ClassificationDisplayPrecedenceLevel @@ -213,7 +213,7 @@ Accept wildcard characters: False The PermissionMenuVisible parameter specifies whether the values that you entered for the DisplayName and RecipientDescription parameters are displayed in Outlook as the user composes a message. Valid values are: -- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This is the default value. +- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This value is the default. - $false: Users can't assign the message classification to messages before they're sent, However, messages received with this message classification still display the classification information. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md index 9c8fc8ac44..f6ae4c00ee 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md @@ -13,7 +13,7 @@ title: Set-MigrationBatch # Set-MigrationBatch ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MigrationBatch cmdlet to update a migration request for a batch of users. For more information, see [New-MigrationBatch](https://learn.microsoft.com/powershell/module/exchangepowershell/new-migrationbatch). @@ -60,9 +60,9 @@ The Set-MigrationBatch cmdlet configures your existing migration batches to migr - IMAP migration - Google Workspace (formerly G Suite) migration -Some settings can be applied both to the batch as well as to individual users within the batch. It is important to note that when a setting is applied to a user it will override any corresponding setting on the batch. +Some settings can be applied both to the batch as well as to individual users within the batch. A setting applied to a user overrides any corresponding setting on the batch. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -125,7 +125,7 @@ This parameter is available only in on-premises Exchange. The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are: - $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. -- $false: Incremental synchronization is disabled. The migration batch will go into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization. +- $false: Incremental synchronization is disabled. The migration batch enters the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization. ```yaml Type: Boolean @@ -146,7 +146,7 @@ Accept wildcard characters: False The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns in the CSV file that aren't used by migration. Valid values are: - $true: The migration ignores (silently skips) unknown columns in the CSV file (including optional columns with misspelled column headers). All unknown columns are treated like extra columns that aren't used by migration. -- $false: The migration fails if there are any unknown columns in the CSV file. This setting protects against spelling errors in column headers. This is the default value. +- $false: The migration fails if there are any unknown columns in the CSV file. This setting protects against spelling errors in column headers. This value is the default. ```yaml Type: Boolean @@ -168,7 +168,7 @@ This parameter is available only in the cloud-based service. The ApproveSkippedItems switch marks all of the skipped items that were discovered prior to the current time as approved. You don't need to specify a value with this switch. -If the data loss that was detected during this migration is significant, the migration will not be able to complete without approving skipped items. Items may have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. +If the data loss that was detected during this migration is significant, the migration can't complete without approving skipped items. Items might have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits). @@ -210,9 +210,9 @@ Accept wildcard characters: False The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the migration request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the migration request is ready to complete. -Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. +Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request fails if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -232,14 +232,14 @@ Accept wildcard characters: False This parameter is functional only in the cloud-based service. -The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch will start, but completion won't start until the date/time you specify with this parameter. +The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch starts, but completion doesn't start until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. -- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. +- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter. ```yaml Type: DateTime @@ -282,7 +282,7 @@ The CSVData parameter specifies the CSV file that contains information about the A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). -**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes that are specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes. +**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes specified in the CSV file are migrated, even if they're outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes. ```yaml Type: Byte[] @@ -329,7 +329,7 @@ For more information about maximum message size values, see the following topics Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -449,7 +449,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been replaced by the MoveOptions parameter. +This parameter is replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -511,14 +511,14 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration will be prepared, but the actual data migration for users within the batch won't start until the date/time you specify with this parameter. +The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration is prepared, but the actual data migration for users within the batch doesn't start until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options: - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`. -- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter. +- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter. ```yaml Type: DateTime diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md index 0c567f3657..605b6fd87b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md @@ -13,7 +13,7 @@ title: Set-MigrationConfig # Set-MigrationConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MigrationConfig cmdlet to edit migration configurations on Exchange servers. @@ -34,7 +34,7 @@ Set-MigrationConfig ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md index 219d487254..ff7cf2b290 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md @@ -13,7 +13,7 @@ title: Set-MigrationEndpoint # Set-MigrationEndpoint ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MigrationEndpoint cmdlet to edit settings for cutover or staged Exchange migrations, IMAP migrations, Google Workspace (formerly G Suite) migrations, and remote moves. @@ -67,7 +67,7 @@ For more information about the different move and migration scenarios, see: Changes made to an endpoint that affect the individual users within the batch are applied starting at the next time that the batch is processed. If you are running this cmdlet in the cloud-based service and wish to speed up the application of these settings, consider running the Set-MigrationBatch cmdlet with the -Update parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -313,7 +313,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The MaxConcurrentMigrations parameter specifies the maximum number of mailboxes that will be migrated for this endpoint at a specified time. This parameter is applicable for all migration types. +The MaxConcurrentMigrations parameter specifies the maximum number of migrated mailboxes for this endpoint at a specified time. This parameter is applicable for all migration types. ```yaml Type: Unlimited @@ -474,7 +474,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that has been granted access to your remote tenant is created. +The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that is granted access to your remote tenant is created. A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md index 06f2e1d789..9e26ca12a5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md @@ -37,9 +37,9 @@ Set-MigrationUser [-Identity] ``` ## DESCRIPTION -Some settings can be applied both to the batch as well as to individual users within the batch. It is important to note that when a setting is applied to a user it will override any corresponding setting on the batch. +Some settings can be applied both to the batch as well as to individual users within the batch. A setting applied to a user overrides any corresponding setting on the batch. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -87,7 +87,7 @@ This parameter is available only in the cloud-based service. The ApproveSkippedItems switch marks all of the skipped items that were discovered prior to the current time as approved. You don't need to specify a value with this switch. -If the data loss that was detected during this migration is significant, the migration will not be able to complete without approving skipped items. Items may have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. +If the data loss that was detected during this migration is significant, the migration can't complete without approving skipped items. Items might have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits). @@ -113,7 +113,7 @@ The BadItemLimit parameter specifies the maximum number of bad items that are al Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. -**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -133,7 +133,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The CompleteAfter parameter specifies a delay before the user is completed. Data migration for the user will start, but won't complete until the date/time you specify with this parameter. +The CompleteAfter parameter specifies a delay before the user is completed. Data migration for the user starts but doesn't complete until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". @@ -210,7 +210,7 @@ For more information about maximum message size values, see the following topics Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. -**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -250,7 +250,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The StartAfter parameter specifies a delay before the data migration for the user is started. The migration will be prepared, but the actual data migration for the user won't start until the date/time you specify with this parameter. +The StartAfter parameter specifies a delay before the data migration for the user is started. The migration is prepared, but the actual data migration for the user doesn't start until the date/time you specify with this parameter. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md index 8cb8193e53..1418931139 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md @@ -13,7 +13,7 @@ title: Set-MobileDeviceMailboxPolicy # Set-MobileDeviceMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-MobileDeviceMailboxPolicy cmdlet to modify mobile device mailbox policies. @@ -91,7 +91,7 @@ Some mobile device mailbox policy settings require the mobile device to have spe Some settings in this cmdlet are supported by Outlook for iOS and Android. For more information, see [Leveraging Exchange Online mobile device policies](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/secure-outlook-for-ios-and-android#leveraging-exchange-online-mobile-device-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -901,7 +901,7 @@ Accept wildcard characters: False The MaxInactivityTimeLock parameter specifies the length of time that the mobile device can be inactive before the password is required to reactivate it. Valid values are: - A timespan: hh:mm:ss, where hh = hours, mm = minutes and ss= seconds. The valid input range is 00:01:00 to 01:00:00 (one minute to one hour). -- The value Unlimited. This is the default value. +- The value Unlimited. This value is the default. ```yaml Type: Unlimited @@ -1036,7 +1036,7 @@ Accept wildcard characters: False The PasswordExpiration parameter specifies how long a password can be used on a mobile device before the user is forced to change the password. Valid values are: - A timespan: ddd.hh:mm:ss, where ddd = days, hh = hours, mm = minutes and ss= seconds. The valid input range is 1.00:00:00 to 730.00:00:00 (one day to two years). -- The value Unlimited. This is the default value +- The value Unlimited. This value is the default ```yaml Type: Unlimited diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md index 1c119aad16..ea5a7779aa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md @@ -13,9 +13,9 @@ title: Set-MoveRequest # Set-MoveRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. -Use the Set-MoveRequest cmdlet to change move request options after the move request has been created. You can use the Set-MoveRequest cmdlet to recover from failed move requests. +Use the Set-MoveRequest cmdlet to change move request options after the move request is created. You can use the Set-MoveRequest cmdlet to recover from failed move requests. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -57,7 +57,7 @@ Set-MoveRequest [-Identity] ## DESCRIPTION You can pipeline the Set-MoveRequest cmdlet from the Get-MoveRequestStatistics, Get-MoveRequest, or Get-Mailbox cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -161,7 +161,7 @@ Valid input for this parameter is an integer or the value unlimited. The default In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -283,7 +283,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013 -The IgnoreRuleLimitErrors parameter specifies that the command won't move the user's rules to the target server running Microsoft Exchange. +The IgnoreRuleLimitErrors parameter specifies whether the command moves the user's rules to the target server running Microsoft Exchange. ```yaml Type: Boolean @@ -301,7 +301,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. This parameter is used together with the CompleteAfter parameter to create a move request that will do periodic incremental syncs after the initial sync is complete. +The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. Use this parameter with the CompleteAfter parameter to create a move request that does periodic incremental syncs after the initial sync is complete. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -354,7 +354,7 @@ Valid input for this parameter is an integer or the value unlimited. The default If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail. -**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead. +**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead. ```yaml Type: Unlimited @@ -395,7 +395,7 @@ Accept wildcard characters: False The PreventCompletion parameter specifies whether to run the move request, but not allow it to complete. Valid values are: - $true: The move request is run, but is not allowed to complete. Instead of this value, we recommend using the CompleteAfter parameter. -- $false: This is the default value. The move request is run and allowed to complete. If you created the move request with the SuspendWhenReadyToComplete or PreventCompletion switches, set this parameter to $false before you run the Resume-MoveRequest cmdlet to complete the move request. +- $false: This value is the default. The move request is run and allowed to complete. If you created the move request with the SuspendWhenReadyToComplete or PreventCompletion switches, set this parameter to $false before you run the Resume-MoveRequest cmdlet to complete the move request. ```yaml Type: Boolean @@ -420,7 +420,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest @@ -574,7 +574,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been replaced by the MoveOptions parameter. +This parameter is replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -643,7 +643,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The SkippedItemApprovalTime parameter marks all of the skipped items discovered prior to the specified time as approved. If the data loss that was detected during this migration is significant, the migration will not be able to complete without approving skipped items. Items may have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. +The SkippedItemApprovalTime parameter marks all of the skipped items discovered prior to the specified time as approved. If the data loss that was detected during this migration is significant, the migration can't complete without approving skipped items. Items might have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits). diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md b/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md index a253128a9d..55cdd0e679 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md @@ -13,7 +13,7 @@ title: Set-Notification # Set-Notification ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. > [!NOTE] > This cmdlet will be deprecated in the cloud-based service. The classic Exchange admin center was deprecated in the cloud-based service in 2023. @@ -49,7 +49,7 @@ Set-Notification -NotificationEmails -ProcessType ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,7 +79,7 @@ The BackgroundColor parameter specifies the background color. Valid values are: - An HTML hexadecimal color code value (#RRGGBB) enclosed in quotation marks. For example, `"#FFFFFF"` is white. - A valid color name value. For example, `yellow` is #ffff00. For a list of the valid color names, see [Background color reference](https://learn.microsoft.com/purview/add-your-organization-brand-to-encrypted-messages#background-color-reference). -- $null (blank). This is the default value. +- $null (blank). This value is the default. ```yaml Type: String @@ -160,7 +160,7 @@ Accept wildcard characters: False This parameter is available only with a Microsoft 365 Advanced Message Encryption subscription. -The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages will never expire. The default value is 0. +The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages never expire. The default value is 0. You can't update the value of this parameter in the default OME configuration. You can only modify this value in a customized configuration. @@ -182,7 +182,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The Image parameter identifies and uploads an image that will be displayed in the email message and in the Microsoft 365 admin center. +The Image parameter identifies and uploads an image to be displayed in the email message and in the Microsoft 365 admin center. A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`). @@ -230,7 +230,7 @@ Accept wildcard characters: False The OTPEnabled parameter specifies whether to allow recipients to use a one-time passcode to view encrypted messages. Valid values are: -- $true: Recipients can use a one-time passcode to view encrypted messages. This is the default value. +- $true: Recipients can use a one-time passcode to view encrypted messages. This value is the default. - $false: Recipients can't use a one-time passcode to view encrypted messages. The recipient is required to sign in using a Microsoft 365 work or school account. ```yaml @@ -311,7 +311,7 @@ Accept wildcard characters: False The SocialIdSignIn parameter specifies whether a user is allowed to view an encrypted message in the Microsoft 365 admin center using their own social network id (Google, Yahoo, and Microsoft account). Valid values are: -- $true: Social network ID sign in is allowed. This is the default value. +- $true: Social network ID sign in is allowed. This value is the default. - $false: Social network ID sign in is not allowed. Whether the recipient can use a one-time passcode or their Microsoft 365 work or school account is controlled by the OTPEnabled parameter. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md b/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md index 2372c45de6..7b7c845e23 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md @@ -27,11 +27,11 @@ Set-OMEMessageRevocation -MessageId -Revoke ``` ## DESCRIPTION -When an email has been revoked, the recipient will get the following error when they try to view the encrypted message in the OME portal: "The message has been revoked by the sender". +When an email is revoked, the recipient gets the following error when they try to view the encrypted message in the OME portal: "The message is revoked by the sender". You can revoke encrypted messages if the recipient received a link-based, branded encrypted email message. If the recipient received a native inline experience in a supported Outlook client, then you can't revoke encryption for the message. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -48,7 +48,7 @@ This example revokes encryption for the specified message. > Applicable: Exchange Online -The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). You can find the Message ID for a message in Message Trace or the Message Encryption Report in the Microsoft Purview compliance portal. @@ -70,8 +70,8 @@ Accept wildcard characters: False The Revoke parameter specifies whether to revoke encryption for the message. Valid values are: -- $true: Encryption for the specified message is revoked. The recipient will get an error when they try to view the encrypted message in the OME portal -- $false: Encryption for the specified message isn't revoked. This is the default value. +- $true: Encryption for the specified message is revoked. The recipient gets an error when they try to view the encrypted message in the OME portal +- $false: Encryption for the specified message isn't revoked. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md index 5ec25ce2cb..b5baa5d5b7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md @@ -40,7 +40,7 @@ Set-OabVirtualDirectory [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -83,7 +83,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. You can use this parameter with the WindowsAuthentication parameter. @@ -149,7 +149,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -169,7 +169,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -190,8 +190,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -288,7 +288,7 @@ Accept wildcard characters: False The RequireSSL parameter specifies whether the client connection to the virtual directory requires Secure Sockets Layer (SSL) encryption. Valid values are: -- $true: SSL encryption is required to connect to the virtual directory. This is the default value. +- $true: SSL encryption is required to connect to the virtual directory. This value is the default. - $false: SSL encryption isn't required to connect to the virtual directory. ```yaml @@ -327,7 +327,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -- $true: Integrated Windows authentication is enabled. This is the default value. +- $true: Integrated Windows authentication is enabled. This value is the default. - $false: Integrated Windows authentication is disabled. You can use this parameter with the BasicAuthentication parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md index e7ba1533af..9aa1ab5a32 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md @@ -13,7 +13,7 @@ title: Set-OfflineAddressBook # Set-OfflineAddressBook ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-OfflineAddressBook cmdlet to modify offline address book (OAB) settings. @@ -53,7 +53,7 @@ Set-OfflineAddressBook [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -282,7 +282,7 @@ This parameter is available only in on-premises Exchange. The GlobalWebDistributionEnabled parameter specifies whether all OAB virtual directories in the organization can accept requests to download the OAB. These locations are advertised by the Autodiscover service. Valid values are: - $true: Any OAB virtual directory in the organization can accept requests to download the OAB. You can't use this setting with the VirtualDirectories parameter. -- $false: Only the OAB virtual directories that are specified by the VirtualDirectories parameter accept requests to download the OAB. This is the default value. +- $false: Only the OAB virtual directories that are specified by the VirtualDirectories parameter accept requests to download the OAB. This value is the default. In Exchange 2013 CU7 or later, we recommend that you use the value $true for this parameter. The Client Access services on any Mailbox server can proxy incoming OAB download requests to the correct location. @@ -490,7 +490,7 @@ This parameter is available only in on-premises Exchange. The ShadowMailboxDistributionEnabled parameter specifies whether a read only copy of the OAB (also known as a shadow copy) is distributed to all other OAB generation mailboxes (also known as organization mailboxes). This allows additional Mailbox servers to be endpoints for requests to download the OAB, which can help prevent users from downloading the OAB across slow WAN links. Valid values are: - $true: The OAB is distributed to all other organization mailboxes. -- $false: The OAB is isn't distributed to other organization mailboxes. This is the default value. +- $false: The OAB is isn't distributed to other organization mailboxes. This value is the default. The value of this parameter is only meaningful if you have multiple organization mailboxes, and is only beneficial in Exchange organizations that have multiple Active Directory sites. @@ -625,7 +625,7 @@ Accept wildcard characters: False The ZipOabFilesBeforeUploading specifies whether to use ZIP file compression on the OAB files before uploading them to the server. Valid values are: - $true: ZIP the OAB files. -- $false: Don't ZIP the OAB files. This is the default value. +- $false: Don't ZIP the OAB files. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md index aa0d233348..a6c3d1ea65 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md @@ -35,9 +35,9 @@ Set-OnPremisesOrganization [-Identity] ``` ## DESCRIPTION -The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with a Microsoft 365 organization. Typically, this object is only modified and updated by the Hybrid Configuration wizard. Manual modification of this object may result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization. +The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with a Microsoft 365 organization. Typically, this object is only modified and updated by the Hybrid Configuration wizard. Manual modification of this object might result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -115,7 +115,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration Active Directory object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains may be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com". +The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration Active Directory object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains might be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com". ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md index 763ab36230..35f5f42bd8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md @@ -13,7 +13,7 @@ title: Set-OrganizationConfig # Set-OrganizationConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-OrganizationConfig cmdlet to configure various settings of an Exchange organization. @@ -505,7 +505,7 @@ Set-OrganizationConfig > [!TIP] > The output of the **Get-OrganizationConfig** cmdlet often shows curly braces or `{}` around properties values that accept multiple comma-separated values. Don't use those extra characters in values for the corresponding parameters on this cmdlet. Use the syntax as explained in the parameter descriptions. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -516,11 +516,11 @@ Set-OrganizationConfig -DistributionGroupDefaultOU Users\Groups -DistributionGro This example creates a distribution group naming policy using the following configuration: -Distribution groups will be created in the Users\\Groups container. +Distribution groups are created in the Users\\Groups container. -The words curse, bad, and offensive will be blocked from being used in distribution group names. +The words curse, bad, and offensive are blocked from being used in distribution group names. -All distribution groups will be prefixed with `DL_` and suffixed with an underscore (\_\) and the user's department and country code. +All distribution groups are prefixed with `DL_` and suffixed with an underscore (\_\) and the user's department and country code. ### Example 2 ```powershell @@ -567,7 +567,7 @@ This parameter is available only in the cloud-based service. The ShortenEventScopeDefault parameter specifies whether calendar events start late or end early in the organization. Valid values are: -- 0 or None: Calendar events in the organization don't automatically start late or end early. This is the default value. +- 0 or None: Calendar events in the organization don't automatically start late or end early. This value is the default. - 1 or EndEarly: By default, the end time of all calendar events is reduced by the number of minutes as specified by the values of the DefaultMinutesToReduceLongEventsBy and DefaultMinutesToReduceShortEventsBy parameters. - 2 or StartLate: By default, the start time of all calendar events is delayed by the number of minutes as specified by the values of the DefaultMinutesToReduceLongEventsBy and DefaultMinutesToReduceShortEventsBy parameters. @@ -649,7 +649,7 @@ Accept wildcard characters: False The ActivityBasedAuthenticationTimeoutEnabled parameter enables or disables the inactivity interval for automatic logoff in Outlook on the web (formerly known as Outlook Web App). Valid values are: -- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity that causes logoff in Outlook on the web. This is the default value. +- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity that causes logoff in Outlook on the web. This value is the default. - $false: Automatic logoff based on a period of inactivity in Outlook on the web is disabled. If you're using single sign-on, use the ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled parameter. @@ -698,7 +698,7 @@ Accept wildcard characters: False The ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled parameter enables or disables the inactivity interval for automatic logoff for single sign-on in Outlook on the Web. Valid values are: -- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity in Outlook on the web that causes logoff for single sign-on. This is the default value. +- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity in Outlook on the web that causes logoff for single sign-on. This value is the default. - $false: Automatic logoff based on a period of inactivity in Outlook on the web is disabled for single sign-on. If you aren't using single sign-on, use the ActivityBasedAuthenticationTimeoutEnabled parameter. @@ -853,7 +853,7 @@ Accept wildcard characters: False The AsyncSendEnabled parameter specifies whether to enable or disable async send in Outlook on the web. Valid values are: -- $true: Async send is enabled. This is the default value. +- $true: Async send is enabled. This value is the default. - $false: Async send is disabled. ```yaml @@ -877,7 +877,7 @@ This parameter is available only in the cloud-based service. The AuditDisabled parameter specifies whether to disable or enable mailbox auditing for the organization. Valid values are: - $true: Mailbox auditing is disabled for the organization. -- $false: Allow mailbox auditing in the organization. This is the default value. +- $false: Allow mailbox auditing in the organization. This value is the default. ```yaml Type: Boolean @@ -897,9 +897,14 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The AutodiscoverPartialDirSync parameter is for scenarios where tenants have Directory Synced some of their Active Directory users into the cloud, but still have on-premises Exchange users that are not Directory Synced. Setting this parameter to $true will cause unknown users to be redirected to the on-premises endpoint and will allow on-premises users to discover their mailbox automatically. Online email addresses will be susceptible to enumeration. We recommend full Directory Sync for all Active Directory users and leaving this parameter with the default $false. +The AutodiscoverPartialDirSync parameter is for scenarios where tenants have Directory Synced some of their Active Directory users into the cloud, but still have on-premises Exchange users that are not Directory Synced. Valid values are: -After you enable AutodiscoverPartialDirSync, it will take approximately 3 hours to fully saturate across the cloud. +- $true: Unknown users are redirected to the on-premises endpoint and on-premises users are allowed to discover their mailbox automatically. +- $false: This value is the default. + +We recommend full Directory Sync for all Active Directory users and leaving this parameter with the default value $false. + +After you enable AutodiscoverPartialDirSync, it takes approximately 3 hours to fully saturate across the cloud. ```yaml Type: Boolean @@ -944,7 +949,7 @@ This parameter is available only in the cloud-based service. The AutoExpandingArchive switch enables the auto-expanding archiving feature in an Exchange Online organization. You don't need to specify a value with this switch. -After you enable auto-expanding archiving, additional storage space is automatically added to a user's archive mailbox when it approaches the storage limit. Note that a user's archive mailbox has to be enabled before auto-expanding archiving can take effect. Also note that after you enable auto-expanding archiving for your organization, it can't be disabled. +After you enable auto-expanding archiving, additional storage space is automatically added to a user's archive mailbox when it approaches the storage limit. A user's archive mailbox has to be enabled before auto-expanding archiving can take effect. Also note that after you enable auto-expanding archiving for your organization, it can't be disabled. ```yaml Type: SwitchParameter @@ -987,7 +992,7 @@ This parameter is available only in the cloud-based service. The BlockMoveMessagesForGroupFolders parameter specifies whether to prevent group owners or group members from moving messages between folders in Microsoft 365 Groups. Valid values are: - $true: Group owners or group members can't move messages between folders in Microsoft 365 groups (manually or vial Inbox rules). -- $false: Group owners or group members can move messages between folders in Microsoft 365 groups. This is the default value. +- $false: Group owners or group members can move messages between folders in Microsoft 365 groups. This value is the default. The value of this parameter is meaningful only when the value of the IsGroupFoldersAndRulesEnabled parameter is $true. @@ -1108,7 +1113,7 @@ This parameter is available only in the cloud-based service. The BookingsEnabled parameter specifies whether to enable Microsoft Bookings in an organization. Valid values are: - $true: Bookings is enabled. -- $false: Bookings is disabled. This is the default value. +- $false: Bookings is disabled. This value is the default. Microsoft Bookings is an online and mobile app for small businesses who provide appointment services to customers. @@ -1302,7 +1307,7 @@ This parameter is available only in the cloud-based service. The BookingsPaymentsEnabled parameter specifies whether to enable the online payment node inside Bookings. Valid values are: - $true: Online payments are enabled. -- $false: Online payments are disabled. This is the default value. +- $false: Online payments are disabled. This value is the default. ```yaml Type: Boolean @@ -1388,7 +1393,7 @@ This parameter is available only in the cloud-based service. The BookingsSocialSharingRestricted parameter specifies whether users can see the social sharing options inside Bookings. Valid values are: - $true: Social sharing options are restricted. -- $false: Users can see social sharing options inside Bookings. This is the default value. +- $false: Users can see social sharing options inside Bookings. This value is the default. ```yaml Type: Boolean @@ -1497,7 +1502,7 @@ Accept wildcard characters: False The ConnectorsActionableMessagesEnabled parameter specifies whether to enable or disable actionable buttons in messages (connector cards) from connected apps on Outlook on the web. Valid values are: -- $true: Action buttons in connector cards are enabled, which allows you to take quick actions directly from Outlook on the web (for example, Like or Comment). This is the default value. +- $true: Action buttons in connector cards are enabled, which allows you to take quick actions directly from Outlook on the web (for example, Like or Comment). This value is the default. - $false: Action buttons in connector cards are disabled. For more information about actionable messages in connected apps, see [Connect apps to your inbox in Outlook on the web](https://support.microsoft.com/office/3d41b99c-bf8d-47d4-bc7a-97758b74689d). @@ -1520,7 +1525,7 @@ Accept wildcard characters: False The ConnectorsEnabled parameter specifies whether to enable or disable all connected apps in organization. Valid values are: -- $true: Connectors are enabled. This is the default value. +- $true: Connectors are enabled. This value is the default. - $false: Connectors are disabled. The workloads that are affected by this parameter are Outlook, SharePoint, Teams, and Viva Engage. @@ -1545,7 +1550,7 @@ This parameter is available only in the cloud-based service. The ConnectorsEnabledForOutlook parameter specifies whether to enable or disable connected apps in Outlook on the web. Valid values are: -- $true: Connectors are enabled. This is the default value. +- $true: Connectors are enabled. This value is the default. - $false: Connectors are disabled. To enable and disable the ability to use connectors on specific Microsoft 365 Groups, set the value of this parameter to $true, and then use the ConnectorsEnabled switch on the Set-UnifiedGroup cmdlet. @@ -1572,7 +1577,7 @@ This parameter is available only in the cloud-based service. The ConnectorsEnabledForSharepoint parameter specifies whether to enable or disable connected apps on SharePoint. Valid values are: -- $true: Connectors are enabled. This is the default value. +- $true: Connectors are enabled. This value is the default. - $false: Connectors are disabled. ```yaml @@ -1595,7 +1600,7 @@ This parameter is available only in the cloud-based service. The ConnectorsEnabledForTeams parameter specifies whether to enable or disable connected apps on Teams. Valid values are: -- $true: Connectors are enabled. This is the default value. +- $true: Connectors are enabled. This value is the default. - $false: Connectors are disabled. ```yaml @@ -1618,7 +1623,7 @@ This parameter is available only in the cloud-based service. The ConnectorsEnabledForYammer parameter specifies whether to enable or disable connected apps on Viva Engage. Valid values are: -- $true: Connectors are enabled. This is the default value. +- $true: Connectors are enabled. This value is the default. - $false: Connectors are disabled. ```yaml @@ -1840,7 +1845,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 0 through 2199023254529 bytes(2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. @@ -1870,7 +1875,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 0 through 2199023254529 bytes (2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. @@ -1920,7 +1925,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 0 through 2199023254529 bytes (2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder. @@ -1945,7 +1950,7 @@ This parameter is available only in the cloud-based service. The DelayedDelicensingEnabled parameter enables or disables a 30 day grace period for Exchange Online license removals from mailboxes. Valid values are: - $true: Exchange Online license removals from mailboxes are delayed by 30 days. Admins can use the delay to identify potential mistakes and avoid disruptions for affected users. -- $false: Exchange Online license removals from mailboxes aren't delayed. This is the default value. +- $false: Exchange Online license removals from mailboxes aren't delayed. This value is the default. Use the TenantAdminNotificationForDelayedDelicensingEnabled parameter to turn on weekly Service Health advisory notifications for admins about the number of Exchange Online delicensed users who are in the 30 day grace period during the specified 8 day interval. For more information about Service Health, see [How to check Microsoft 365 service health](https://learn.microsoft.com/microsoft-365/enterprise/view-service-health). @@ -1980,7 +1985,7 @@ This parameter is available only in the cloud-based service. The DirectReportsGroupAutoCreationEnabled parameter specifies whether to enable or disable the automatic creation of direct report Microsoft 365 Groups. Valid values are: - $true: The automatic creation of direct report Microsoft 365 Groups is enabled. -- $false: The automatic creation of direct report Microsoft 365 Groups is disabled. This is the default value. +- $false: The automatic creation of direct report Microsoft 365 Groups is disabled. This value is the default. ```yaml Type: Boolean @@ -2120,8 +2125,8 @@ This parameter is available only in the cloud-based service. The ElcProcessingDisabled parameter specifies whether to enable or disable the processing of mailboxes by the Managed Folder Assistant. Valid values are: -- $true: The Managed Folder Assistant isn't allowed to process mailboxes in the organization. Note that this setting will be ignored on a mailbox if a retention policy that has Preservation Lock enabled is applied to that mailbox. -- $false: The Managed Folder Assistant is allowed to process mailboxes in the organization. This is the default value. +- $true: The Managed Folder Assistant isn't allowed to process mailboxes in the organization. This setting is ignored on a mailbox if a retention policy that has Preservation Lock enabled is applied to that mailbox. +- $false: The Managed Folder Assistant is allowed to process mailboxes in the organization. This value is the default. ```yaml Type: Boolean @@ -2184,7 +2189,7 @@ This parameter is available only in on-premises Exchange. The EnableDownloadDomains parameter specifies that Outlook on the web downloads inline images from a different domain than the rest of Outlook on the web. Valid values are: - $true: Outlook on the web uses a different download domain for inline images (for example, downloads.contoso.com). Before you enable this setting, you need to create a CNAME record and certificate for this domain, and add the domain to the ExternalDownloadHostName and InternalDownloadHostName parameters on the Set-OwaVirtualDirectory cmdlet. -- $false: The setting is disabled. This is the default value. +- $false: The setting is disabled. This value is the default. For more information about the security vulnerability that's addressed by this parameter, and for detailed configuration instructions, see [CVE 2021 1730](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-1730). @@ -2249,7 +2254,7 @@ This parameter is available only in the cloud-based service. The EnableOutlookEvents parameter specifies whether Outlook or Outlook on the web (formerly known as Outlook Web App) automatically discovers events from email messages and adds them to user calendars. Valid values are: - $true: Discovery of events from email messages is enabled. -- $false: Discovery of events from email messages is disabled. This is the default value. +- $false: Discovery of events from email messages is disabled. This value is the default. ```yaml Type: Boolean @@ -2272,7 +2277,7 @@ This parameter is available only in the cloud-based service. The EndUserDLUpgradeFlowsDisabled parameter specifies whether to prevent users from upgrading their own distribution groups to Microsoft 365 Groups in an Exchange Online organization. Valid values are: - $true: Users can upgrade distribution groups that they own to Microsoft 365 Groups. -- $false: Users can't upgrade distribution groups that they own to Microsoft 365 Groups. This is the default value. +- $false: Users can't upgrade distribution groups that they own to Microsoft 365 Groups. This value is the default. ```yaml Type: Boolean @@ -2295,7 +2300,7 @@ This parameter is available only in the cloud-based service. The EndUserMailNotificationForDelayedDelicensingEnabled parameter enables or disables periodic email warnings to affected users that have pending Exchange Online license removal requests on their mailboxes. Valid values are: - $true: Affected users receive periodic email notifications about losing access to their mailbox starting ~18 days after the Exchange Online license was removed. -- $false: Affected users don't receive periodic email notifications about losing access to their mailbox. This is the default value. +- $false: Affected users don't receive periodic email notifications about losing access to their mailbox. This value is the default. The value of this parameter is meaningful on when the value of the DelayedDelicensingEnabled parameter is $true. @@ -2400,7 +2405,7 @@ The EwsApplicationAccessPolicy parameter specifies the client applications that - EnforceAllowList: Only applications specified by the EwsAllowList parameter are allowed to access EWS and REST. Access by other applications is blocked. - EnforceBlockList: All applications are allowed to access EWS and REST, except for the applications specified by the EwsBlockList parameter. -Note that if the EwsAllowEntourage, EwsAllowMacOutlook or EwsAllowOutlook parameters are set to a true or false value, they take precedence for access to EWS by Entourage, Mac Outlook, or Outlook, respectively. +If the EwsAllowEntourage, EwsAllowMacOutlook or EwsAllowOutlook parameters are set to a true or false value, they take precedence for access to EWS by Entourage, Mac Outlook, or Outlook, respectively. ```yaml Type: EwsApplicationAccessPolicy @@ -2444,7 +2449,7 @@ The EwsEnabled parameter specifies whether to globally enable or disable EWS acc - $true: All EWS access is enabled. - $false: All EWS access is disabled. -- $null (blank): The setting isn't configured. Access to EWS is controlled individually by the related EWS parameters (for example EwsAllowEntourage). This is the default value. +- $null (blank): The setting isn't configured. Access to EWS is controlled individually by the related EWS parameters (for example EwsAllowEntourage). This value is the default. This parameter has no affect on access to REST. @@ -2562,7 +2567,7 @@ This parameter is available only in the cloud-based service. The FindTimeLockPollForAttendeesEnabled controls whether the **Lock poll for attendees** setting is managed by the organization. Valid values are: -- $true: **Lock poll for attendees** is on. Attendees will not be able to suggest new times or edit other attendees. The meeting organizer can't turn off this setting (always on). +- $true: **Lock poll for attendees** is on. Attendees can't suggest new times or edit other attendees. The meeting organizer can't turn off this setting (always on). - $false: By default, **Lock poll for attendees** is off (initial default) or on (the user saved settings from last poll), but the meeting organizer is allowed to turn the setting off or on to allow or prevent attendees from suggesting new times or editing attendees. This setting overrides individual user settings. @@ -2848,7 +2853,7 @@ This parameter is available only in the cloud-based service. The IsGroupFoldersAndRulesEnabled specifies whether group owners (by default) can create folders and move messages (manually or by using Inbox rules) in Microsoft 365 Groups. Valid values are: - $true: Group owners can create folders and move messages between folders in Microsoft 365 Groups. -- $false: Group owners can't create folders or move messages between folders in Microsoft 365 Groups. This is the default value. +- $false: Group owners can't create folders or move messages between folders in Microsoft 365 Groups. This value is the default. To allow group owners to allow group users to create folders and moved messages in Microsoft 365 Groups, use the IsGroupMemberAllowedToEditContent parameter. @@ -2882,7 +2887,7 @@ The IsGroupMemberAllowedToEditContent parameter specifies whether group owners c • Create, edit, copy, and delete Inbox rules. -- $false: Group owners can't use the **All members will be able to create, edit, move, copy, and delete mail folders and rules within the group** setting in the group properties in Outlook on the web to allow group members to manage folders and messages in Microsoft 365 Groups. Only group owners can manage folders and messages in Microsoft 365 Groups. This is the default value. +- $false: Group owners can't use the **All members will be able to create, edit, move, copy, and delete mail folders and rules within the group** setting in the group properties in Outlook on the web to allow group members to manage folders and messages in Microsoft 365 Groups. Only group owners can manage folders and messages in Microsoft 365 Groups. This value is the default. The value of this parameter is meaningful only when the value of the IsGroupFoldersAndRulesEnabled parameter is $true. @@ -2909,7 +2914,7 @@ Accept wildcard characters: False The LeanPopoutEnabled parameter specifies whether to enable faster loading of pop-out messages in Outlook on the web for Internet Explorer and Microsoft Edge. Valid values are: - $true: Lean pop-outs are enabled. -- $false: Lean pop-outs are disabled. This is the default value. +- $false: Lean pop-outs are disabled. This value is the default. **Notes**: @@ -2934,7 +2939,7 @@ Accept wildcard characters: False The LinkPreviewEnabled parameter specifies whether link preview of URLs in email messages is allowed for the organization. Valid values are: -- $true: Link preview of URLs in email messages is allowed. Users can enable or disable link preview in their Outlook on the web settings. This is the default value. +- $true: Link preview of URLs in email messages is allowed. Users can enable or disable link preview in their Outlook on the web settings. This value is the default. - $false: Link preview of URLs in email messages is not allowed. Users can't enable link preview in their Outlook on the web settings. ```yaml @@ -3087,7 +3092,7 @@ This parameter is available only in on-premises Exchange. The MapiHttpEnabled parameter enables or disables access to mailboxes in Outlook by using MAPI over HTTP. Valid values are: -- $true: Access to mailboxes by using MAPI over HTTP is enabled. This is the default value. +- $true: Access to mailboxes by using MAPI over HTTP is enabled. This value is the default. - $false: Access to mailboxes by using MAPI over HTTP is disabled. You can use the MapiHttpEnabled parameter on the Set-CASMailbox cmdlet to override the global MAPI over HTTP settings for individual users. @@ -3291,7 +3296,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -The MicrosoftExchangeRecipientEmailAddresses parameter specifies one or more email addresses for the recipient. All valid Microsoft Exchange email address types may be used. You can specify multiple values for this parameter as a comma-delimited list. If the MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter is set to $true, the email addresses are automatically generated by the default email address policy. This means you can't use the MicrosoftExchangeRecipientEmailAddresses parameter. +The MicrosoftExchangeRecipientEmailAddresses parameter specifies one or more email addresses for the recipient. All valid Microsoft Exchange email address types might be used. You can specify multiple values for this parameter as a comma-delimited list. If the MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter is set to $true, the email addresses are automatically generated by the default email address policy. This means you can't use the MicrosoftExchangeRecipientEmailAddresses parameter. Email addresses that you specify by using the MicrosoftExchangeRecipientEmailAddresses parameter replace any existing email addresses already configured. @@ -3413,11 +3418,9 @@ This parameter is available only in the cloud-based service. The MobileAppEducationEnabled specifies whether to show or hide the Outlook for iOS and Android education reminder in Outlook on the web (formerly known as Outlook Web App). Valid values are: -- $true: Outlook on the web and Outlook desktop will show the education reminder to users who aren't using Outlook for iOS and Android to check their company email and calendar events. This is the default value. +- $true: Outlook on the web and Outlook desktop show the education reminder to users who aren't using Outlook for iOS and Android to check their company email and calendar events. This value is the default. - $false: The Outlook for iOS and Android education reminder is disabled. -This setting will affect Outlook desktop at some point in the future. - ```yaml Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet @@ -3487,7 +3490,7 @@ The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetin - $false: All meetings are not online by default. - $null: If the organization value has not been specified, the default behavior is for meetings to be online. -If a user has already directly interacted with this setting in Outlook or Outlook on the web (formerly known as Outlook Web App or OWA), the value of this parameter is ignored. Eventually, this parameter will override the Outlook-configured setting. +If a user has already directly interacted with this setting in Outlook or Outlook on the web (formerly known as Outlook Web App or OWA), the value of this parameter is ignored. ```yaml Type: Boolean @@ -3530,7 +3533,7 @@ This parameter is available only in the cloud-based service. The OutlookGifPickerDisabled parameter disables the GIF Search (powered by Bing) feature that's built into the Compose page in Outlook on the web. Valid values are: - $true: GIF Search in Outlook on the web is disabled. -- $false: GIF Search in Outlook on the web is enabled. This is the default value. +- $false: GIF Search in Outlook on the web is enabled. This value is the default. ```yaml Type: Boolean @@ -3552,7 +3555,7 @@ This parameter is available only in the cloud-based service. The OutlookMobileGCCRestrictionsEnabled parameter specifies whether to enable or disable features within Outlook for iOS and Android that are not FedRAMP compliant for Microsoft 365 US Government Community Cloud (GCC) customers. Valid values are: -- $true: Disable features that aren't FedRAMP compliant for GCC customers. This is the default value for all GCC customers. +- $true: Disable features that aren't FedRAMP compliant for GCC customers. This value is the default for all GCC customers. - $false: Enable features that aren't FedRAMP compliant for GCC customers. The Outlook for iOS and Android feature and services that are not FedRAMP compliant for Microsoft 365 US Government customers include: @@ -3667,8 +3670,8 @@ This parameter is available only in Exchange Server 2010. The PermanentlyDeleteDisabled parameter specifies whether to disable the PermanentlyDelete retention action for messaging records management (MRM). Valid values are: -- $true The PermanentlyDelete retention action is disabled. This setting only prevents items from being permanently deleted. It doesn't modify existing policies, block the creation of policies with the PermanentlyDelete action or notify users that thePermanentlyDelete action won't actually take effect. -- $false The PermanentlyDelete retention action is enabled. This is the default value. +- $true The PermanentlyDelete retention action is disabled. This setting only prevents items from being permanently deleted. It doesn't modify existing policies, block the creation of policies with the PermanentlyDelete action, or notify users that thePermanentlyDelete action doesn't actually take effect. +- $false The PermanentlyDelete retention action is enabled. This value is the default. A message that's permanently deleted can't be recovered by using the Recoverable Items folder. Additionally, permanently deleted messages aren't returned by a Discovery search, unless litigation hold or single item recovery is enabled for the mailbox. @@ -3690,7 +3693,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -3716,7 +3719,7 @@ The PostponeRoamingSignaturesUntilLater parameter controls whether roaming signa Previously, the only way to disable roaming signatures in Outlook on the web was to open a support ticket. With the introduction of this parameter and value, admins can disable roaming signatures themselves. -- $false: Roaming signatures are enabled for Outlook on the web and the new Outlook for Windows. This is the default value. +- $false: Roaming signatures are enabled for Outlook on the web and the new Outlook for Windows. This value is the default. We recommend that independent software vendors (ISVs) onboard to the [signature API](https://learn.microsoft.com/javascript/api/outlook/office.body#outlook-office-body-setsignatureasync-member(1)) based on [event-based hooks ](https://learn.microsoft.com/office/dev/add-ins/outlook/autolaunch). @@ -3757,7 +3760,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The PublicComputersDetectionEnabled parameter specifies whether Outlook on the web will detect when a user signs from a public or private computer or network, and then enforces the attachment handling settings from public networks. The default is $false. However, if you set this parameter to $true, Outlook on the web will determine if the user is signing in from a public computer, and all public attachment handling rules will be applied and enforced. +The PublicComputersDetectionEnabled parameter specifies whether Outlook on the web detects when a user signs from a public or private computer or network, and then enforces the attachment handling settings from public networks. The default is $false. However, if you set this parameter to $true, Outlook on the web determines if the user is signing in from a public computer, and all public attachment handling rules are applied and enforced. ```yaml Type: Boolean @@ -3800,7 +3803,7 @@ This parameter is available only in on-premises Exchange. The PublicFolderMailboxesLockedForNewConnections parameter specifies whether users are allowed to make new connections to public folder mailboxes. Valid values are: - $true: Users aren't allowed to make new connections to public folder mailboxes. You use this setting during the final stages of public folder migrations. -- $false: Users are allowed to make new connections to public folder mailboxes. This is the default value. +- $false: Users are allowed to make new connections to public folder mailboxes. This value is the default. ```yaml Type: Boolean @@ -3823,7 +3826,7 @@ This parameter is available only in on-premises Exchange. The PublicFolderMailboxesMigrationComplete parameter is used during public folder migration. - $true: Queued messages are rerouted to the new destination. -- $false (This is the default value) +- $false (default value) ```yaml Type: Boolean @@ -3886,7 +3889,7 @@ Accept wildcard characters: False The PublicFolderShowClientControl parameter enables or disables the control access feature for public folders in Microsoft Outlook. Valid values are: - $true: User access to public folders in Outlook is controlled by the value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet (the default value is $false). -- $false: This is the default value. User access to public folders in Outlook is enabled (the control access feature is disabled). The value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet is meaningless. +- $false: This value is the default. User access to public folders in Outlook is enabled (the control access feature is disabled). The value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet is meaningless. ```yaml Type: Boolean @@ -4060,8 +4063,8 @@ This parameter is available only in the cloud-based service. The SendFromAliasEnabled parameter allows mailbox users to send messages using aliases (proxy addresses). Valid values are: -- $true: Aliases on messages will no longer be rewritten to their primary SMTP addresses. Compatible Outlook clients will allow sending from aliases and replying to aliases. Even without an updated Outlook client, users might see changes in behavior because the setting affects all messages sent and received by a mailbox. -- $false: Aliases on messages sent or received will be rewritten to their primary email address. This is the default value. +- $true: Aliases on messages are no longer rewritten to their primary SMTP addresses. Compatible Outlook clients allow sending from aliases and replying to aliases. Even without an updated Outlook client, users might see changes in behavior because the setting affects all messages sent and received by a mailbox. +- $false: Aliases on messages sent or received are rewritten to their primary email address. This value is the default. For more information about the availability of the feature in Outlook on the web, see the [Microsoft 365 roadmap item](https://www.microsoft.com/microsoft-365/roadmap?filters=Exchange&searchterms=59437). For Outlook for Windows, see this [Microsoft 365 roadmap item](https://www.microsoft.com/microsoft-365/roadmap?filters=Outlook&searchterms=64123). @@ -4121,7 +4124,7 @@ Accept wildcard characters: False The SmtpActionableMessagesEnabled parameter specifies whether to enable or disable action buttons in email messages in Outlook on the web. Valid values are: -- $true: Action buttons in email messages are enabled. This is the default value. +- $true: Action buttons in email messages are enabled. This value is the default. - $false: Action buttons in email messages are disabled. ```yaml @@ -4145,7 +4148,7 @@ This parameter is available only in the cloud-based service. The TenantAdminNotificationForDelayedDelicensingEnabled parameter enables or disables weekly admin Service Health advisory notifications that are sent to admins. Valid values are: - $true: Weekly Service Health advisory notifications are sent to admins about the number of Exchange Online delicensed users who are in the 30 day grace period during the specified 8 day interval. -- $false: Disable weekly Service Health advisory notifications about the number of Exchange Online delicensed users. This is the default value. +- $false: Disable weekly Service Health advisory notifications about the number of Exchange Online delicensed users. This value is the default. For more information about Service Health, see [How to check Microsoft 365 service health](https://learn.microsoft.com/microsoft-365/enterprise/view-service-health). @@ -4191,7 +4194,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: MultiValuedProperty @@ -4249,7 +4252,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The VisibleMeetingUpdateProperties parameter specifies whether meeting message updates will be auto-processed on behalf of attendees. Auto-processed updates are applied to the attendee's calendar item, and then the meeting message is moved to the deleted items. The attendee never sees the update in their inbox, but their calendar is updated. +The VisibleMeetingUpdateProperties parameter specifies whether meeting message updates are auto-processed on behalf of attendees. Auto-processed updates are applied to the attendee's calendar item, and then the meeting message is moved to the deleted items. The attendee never sees the update in their inbox, but their calendar is updated. This parameter uses the syntax: `"MeetingProperty1:MeetingStartTimeWithinXMinutes1,MeetingProperty2:MeetingStartTimeWithinXMinutes2,...MeetingPropertyN:MeetingStartTimeWithinXMinutesN"`. @@ -4267,11 +4270,11 @@ The valid meeting properties to monitor for updates are: - Reminder: The reminder time. - AllProperties: Any meeting change. -If you don't specify a MeetingStartTimeWithinXMinutes value for the meeting property, any change to the meeting property will result in visible meeting update messages (regardless of how soon or how far away the meeting is). For updates to recurring meetings, the meeting start time is the start time of the next occurrence in the series. +If you don't specify a MeetingStartTimeWithinXMinutes value for the meeting property, any change to the meeting property results in visible meeting update messages (regardless of how soon or how far away the meeting is). For updates to recurring meetings, the meeting start time is the start time of the next occurrence in the series. The default value is `"Location,AllProperties:15"`: changes to the meeting location at any time, or changes to other meeting properties within 15 minutes of the meeting start time results in visible meeting update messages. -In the following scenarios, meeting update messages are not auto-processed, regardless of the values specified in this parameter. In these scenarios, attendees will always see meeting update messages in their Inbox: +In the following scenarios, meeting update messages are not auto-processed, regardless of the values specified in this parameter. In these scenarios, attendees always see meeting update messages in their Inbox: - The update contains a change to the meeting date, time, or recurrence pattern. - The meeting message is received for a delegated shared calendar. @@ -4321,7 +4324,7 @@ This parameter is available only in the cloud-based service. The WebPushNotificationsDisabled parameter specifies whether to enable or disable Web Push Notifications in Outlook on the Web. This feature provides web push notifications which appear on a user's desktop while the user is not using Outlook on the Web. This brings awareness of incoming messages while they are working elsewhere on their computer. Valid values are: - $true: Web Push Notifications are disabled. -- $false: Web Push Notifications are enabled. This is the default value. +- $false: Web Push Notifications are enabled. This value is the default. ```yaml Type: Boolean @@ -4344,7 +4347,7 @@ This parameter is available only in the cloud-based service. The WebSuggestedRepliesDisabled parameter specifies whether to enable or disable Suggested Replies in Outlook on the web. This feature provides suggested replies to emails so users can easily and quickly respond to messages. Valid values are: - $true: Suggested Replies are disabled. -- $false: Suggested Replies are enabled. This is the default value. +- $false: Suggested Replies are enabled. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md index 32e1291fcb..2e0b8862f8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md @@ -13,7 +13,7 @@ title: Set-OrganizationRelationship # Set-OrganizationRelationship ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-OrganizationRelationship cmdlet to modify existing organization relationships. Organization relationships define the settings that are used with external Exchange organizations to access calendar free/busy information or to move mailboxes between on-premises Exchange servers and Exchange Online as part of hybrid deployments. @@ -52,7 +52,7 @@ Set-OrganizationRelationship [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -98,10 +98,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -The ArchiveAccessEnabled parameter specifies whether the organization relationship has been configured to provide remote archive access. Valid values are: +The ArchiveAccessEnabled parameter specifies whether the organization relationship is configured to provide remote archive access. Valid values are: - $true: The external organization provides remote access to mailbox archives. -- $false: The external organization doesn't provide remote access to mailbox archives. This is the default value +- $false: The external organization doesn't provide remote access to mailbox archives. This value is the default ```yaml Type: Boolean @@ -143,9 +143,9 @@ Accept wildcard characters: False The DeliveryReportEnabled parameter specifies whether Delivery Reports should be shared over the organization relationship. Valid values are: - $true: Delivery Reports should be shared over the organization relationship. This value means the organization has agreed to share all Delivery Reports with the external organization, and the organization relationship should be used to retrieve Delivery Report information from the external organization. -- $false: Delivery Reports shouldn't be shared over the organization relationship. This is the default value +- $false: Delivery Reports shouldn't be shared over the organization relationship. This value is the default -For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations won't work in either direction. +For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations doesn't work in either direction. ```yaml Type: Boolean @@ -203,7 +203,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable the organization relationship. Valid values are: -- $true: The organization relationship is enabled. This is the default value. +- $true: The organization relationship is enabled. This value is the default. - $false: The organization relationship is disabled. This value completely stops sharing for the organization relationship. ```yaml @@ -245,7 +245,7 @@ Accept wildcard characters: False The FreeBusyAccessEnabled parameter specifies whether the organization relationship should be used to retrieve free/busy information from the external organization. Valid values are: - $true: Free/busy information is retrieved from the external organization. -- $false: Free/busy information isn't retrieved from the external organization. This is the default value. +- $false: Free/busy information isn't retrieved from the external organization. This value is the default. You control the free/busy access level and scope by using the FreeBusyAccessLevel and FreeBusyAccessScope parameters. @@ -344,7 +344,7 @@ Accept wildcard characters: False The MailboxMoveEnabled parameter specifies whether the organization relationship enables moving mailboxes to or from the external organization. Valid values are: - $true: Mailbox moves to or from the external organization are allowed. -- $false: Mailbox moves to from the external organization aren't allowed. This is the default value. +- $false: Mailbox moves to from the external organization aren't allowed. This value is the default. ```yaml Type: Boolean @@ -396,7 +396,7 @@ Accept wildcard characters: False The MailTipsAccessEnabled parameter specifies whether MailTips for users in this organization are returned over this organization relationship. Valid values are: - $true: MailTips for users in this organization are returned over the organization relationship. -- $false: MailTips for users in this organization aren't returned over the organization relationship. This is the default value. +- $false: MailTips for users in this organization aren't returned over the organization relationship. This value is the default. You control the MailTips access level by using the MailTipsAccessLevel parameter. @@ -419,8 +419,8 @@ Accept wildcard characters: False The MailTipsAccessLevel parameter specifies the level of MailTips data externally shared over this organization relationship. This parameter can have the following values: - All: All MailTips are returned, but the recipients in the remote organization are considered external. For the Auto Reply MailTip, the external Auto Reply message is returned. -- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips won't be returned. -- None: No MailTips are returned to the remote organization. This is the default value. +- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips aren't returned. +- None: No MailTips are returned to the remote organization. This value is the default. This parameter is only meaningful when the MailTipsAccessEnabled parameter value is $true. @@ -534,7 +534,7 @@ Accept wildcard characters: False The PhotosEnabled parameter specifies whether photos for users in the internal organization are returned over the organization relationship. Valid values are: - $true: Photos for users in this organization are returned over the organization relationship. -- $false: Photos for users in this organization aren't returned over the organization relationship. This is the default value. +- $false: Photos for users in this organization aren't returned over the organization relationship. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md index b270f10022..aa46e84863 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md @@ -50,7 +50,7 @@ Set-OutboundConnector [-Identity] ## DESCRIPTION Outbound connectors send email messages to remote domains that require specific configuration options. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -92,7 +92,7 @@ Accept wildcard characters: False The AllAcceptedDomains parameter specifies whether the Outbound connector is used in hybrid organizations where message recipients are in accepted domains of the cloud-based organization. Valid values are: - $true: The Outbound connector is used in hybrid organizations when message recipients are in an accepted domain of the cloud-based organization. This setting requires OnPremises for the ConnectorType value. -- $false: The Outbound connector isn't used in hybrid organizations. This is the default value. +- $false: The Outbound connector isn't used in hybrid organizations. This value is the default. This parameter is effective only for OnPremises connectors. @@ -118,7 +118,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f Valid values are: -- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. +- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages. - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector. ```yaml @@ -178,7 +178,7 @@ Accept wildcard characters: False The ConnectorSource parameter specifies how the connector is created. Valid values are: -- Default: The connector is manually created. This is the default value for manually created connectors, and we recommend that you don't change this value. +- Default: The connector is manually created. This value is the default for manually created connectors, and we recommend that you don't change this value. - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. @@ -221,7 +221,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable or disable the Outbound connector. Valid values are: -- $true: The connector is enabled. This is the default value. +- $true: The connector is enabled. This value is the default. - $false: The connector is disabled. ```yaml @@ -243,7 +243,7 @@ Accept wildcard characters: False The IsTransportRuleScoped parameter specifies whether the Outbound connector is associated with a transport rule (also known as a mail flow rule). Valid values are: - $true: The connector is associated with a transport rule. -- $false: The connector isn't associated with a transport rule. This is the default value. +- $false: The connector isn't associated with a transport rule. This value is the default. You scope a transport rule to an Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. Messages that match the conditions of the transport rule are routed to their destinations by using the specified Outbound connector. @@ -263,10 +263,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The IsValidated parameter specifies whether the Outbound connector has been validated. Valid values are: +The IsValidated parameter specifies whether the Outbound connector is validated. Valid values are: -- $true: The connector has been validated, -- $false: The connector hasn't been validated. This is the default value. +- $true: The connector is validated, +- $false: The connector hasn't been validated. This value is the default. Use the Validate-OutboundConnector cmdlet to validate the connector. @@ -352,7 +352,7 @@ Accept wildcard characters: False The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises email system. Valid values are: - $true: Messages are routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. -- $false: Messages aren't routed through the on-premises email system. This is the default value. +- $false: Messages aren't routed through the on-premises email system. This value is the default. This parameter is effective only for OnPremises connectors. @@ -375,7 +375,7 @@ Accept wildcard characters: False The SenderRewritingEnabled parameter specifies that all messages that normally qualify for SRS rewriting are rewritten for routing through the on-premises email system. Valid values are: - $true: Messages are rewritten by SRS as needed before being routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. -- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This is the default value. +- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This value is the default. This parameter is effective only for OnPremises connectors. @@ -424,7 +424,7 @@ Accept wildcard characters: False The TestMode parameter specifies whether you want to enabled or disable test mode for the Outbound connector. Valid values are: - $true: Test mode is enabled. -- $false: Test mode is disabled. This is the default value. +- $false: Test mode is disabled. This value is the default. ```yaml Type: Boolean @@ -469,7 +469,7 @@ The TlsSettings parameter specifies the TLS authentication level that's used for - EncryptionOnly: TLS is used only to encrypt the communication channel. No certificate authentication is performed. - CertificateValidation: TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed. - DomainValidation: In addition to channel encryption and certificate validation, the Outbound connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter. -- $null (blank): This is the default value. +- $null (blank): This value is the default. ```yaml Type: TlsAuthLevel @@ -489,7 +489,7 @@ Accept wildcard characters: False The UseMXRecord parameter enables or disables DNS routing for the connector. Valid values are: -- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This is the default value. +- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This value is the default. - $false: The connector delivers email to one or more smart hosts. This setting requires one or more smart hosts for the SmartHosts value. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md index 17d58eac0e..ac591d7859 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md @@ -46,7 +46,7 @@ Set-OutlookAnywhere [-Identity] ## DESCRIPTION For more information about the different authentication methods that you can see in this article, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -122,7 +122,7 @@ The ClientAuthenticationMethod parameter specifies the authentication method tha - Basic - Ntlm -Although you can use this parameter to set only one authentication method, the command won't return an error if you include multiple values. +Although you can use this parameter to set only one authentication method, the command doesn't return an error if you include multiple values. ```yaml Type: AuthenticationMethod @@ -209,7 +209,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -229,7 +229,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -250,8 +250,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -276,7 +276,7 @@ The ExternalClientAuthenticationMethod parameter specifies the authentication me - Basic - Ntlm -- Negotiate (This is the default value) +- Negotiate (default value) You can't use this parameter with the DefaultAuthenticationMethods parameter. @@ -299,7 +299,7 @@ Accept wildcard characters: False The ExternalClientsRequireSsl parameter specifies whether external Outlook Anywhere clients are required to use Secure Sockets Layer (SSL). Valid values are: - $true: Clients connecting via Outlook Anywhere from outside the organization are required to use SSL. -- $false: Clients connecting via Outlook Anywhere from outside the organization aren't required to use SSL. This is the default value. +- $false: Clients connecting via Outlook Anywhere from outside the organization aren't required to use SSL. This value is the default. The value of this parameter is related to the value of the SSLOffloading parameter. @@ -366,7 +366,7 @@ Accept wildcard characters: False The InternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate internal Outlook Anywhere clients. Valid values are: - Basic -- Ntlm (This is the default value) +- Ntlm (default value) - Negotiate You can't use this parameter with the DefaultAuthenticationMethods parameter. @@ -390,7 +390,7 @@ Accept wildcard characters: False The InternalClientsRequireSsl parameter specifies whether internal Outlook Anywhere clients are required to use SSL. Valid values are: - $true: Clients connecting via Outlook Anywhere from inside the organization are required to use SSL. -- $false: Clients connecting via Outlook Anywhere from inside the organization aren't required to use SSL. This is the default value. +- $false: Clients connecting via Outlook Anywhere from inside the organization aren't required to use SSL. This value is the default. The value of this parameter is related to the value of the SSLOffloading parameter. @@ -448,10 +448,10 @@ Accept wildcard characters: False The SSLOffloading parameter specifies whether a network device accepts SSL connections and decrypts them before proxying the connections to the Outlook Anywhere virtual directory on the Exchange server. Valid values are: -- $true: Outlook Anywhere clients using SSL don't maintain an SSL connection along the entire network path to the Exchange server. A network device in front of the server decrypts the SSL connections and proxies the unencrypted (HTTP) client connections to the Outlook Anywhere virtual directory. The network segment where HTTP is used should be a secured network. This is the default value. +- $true: Outlook Anywhere clients using SSL don't maintain an SSL connection along the entire network path to the Exchange server. A network device in front of the server decrypts the SSL connections and proxies the unencrypted (HTTP) client connections to the Outlook Anywhere virtual directory. The network segment where HTTP is used should be a secured network. This value is the default. - $false: Outlook Anywhere clients using SSL maintain an SSL connection along the entire network path to the Exchange server. Only SSL connections are allowed to the Outlook Anywhere virtual directory. -This parameter configures the Require SSL value on the Outlook Anywhere virtual directory. When you set this parameter to $true, Require SSL is disabled. When you set this parameter to $fase, Require SSL is enabled. However, it may take several minutes before the change is visible in IIS Manager. +This parameter configures the Require SSL value on the Outlook Anywhere virtual directory. When you set this parameter to $true, Require SSL is disabled. When you set this parameter to $fase, Require SSL is enabled. However, it might take several minutes before the change is visible in IIS Manager. You need to use the value $true for this parameter if you don't require SSL connections for internal or external Outlook Anywhere clients. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md index 595590c4a5..e7bc6acefb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md @@ -15,7 +15,7 @@ title: Set-OutlookProtectionRule ## SYNOPSIS **Note**: This cmdlet is no longer supported in the cloud-based service. -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-OutlookProtectionRule cmdlet to modify an existing Microsoft Outlook protection rule. @@ -44,7 +44,7 @@ Outlook protection rules are used to automatically rights-protect email messages Not specifying any conditions results in an Outlook protection rule being applied to all messages. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md index aca9ccddb2..aa50953b25 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md @@ -38,7 +38,7 @@ Set-OutlookProvider [-Identity] ## DESCRIPTION The Set-OutlookProvider cmdlet creates the global settings for the Autodiscover service. It sets the AutoDiscoverConfig object under the Global Settings object in Active Directory and sets the attributes specified in the parameters listed in the Parameters section. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -172,7 +172,7 @@ The RequiredClientVersions parameter specifies the minimum version of Microsoft MinimumVersion is the version of Outlook in the format xx.x.xxxx.xxxx. For example, to specify Outlook 2010 Service Pack 2 (SP2), use the value 14.0.7012.1000. -ExpirationDate is the UTC date-time when connections by older versions of Outlook will be blocked. The UTC date-time is represented in the ISO 8601 date-time format: yyyy-MM-ddThh:mm:ss.fffZ, where yyyy = year, MM = month, dd = day, T indicates the beginning of the time component, hh = hour, mm = minute, ss = second, fff = fractions of a second and Z signifies Zulu, which is another way to denote UTC. +ExpirationDate is the UTC date-time when connections by older versions of Outlook are blocked. The UTC date-time is represented in the ISO 8601 date-time format: yyyy-MM-ddThh:mm:ss.fffZ, where yyyy = year, MM = month, dd = day, T indicates the beginning of the time component, hh = hour, mm = minute, ss = second, fff = fractions of a second and Z signifies Zulu, which is another way to denote UTC. An example of a valid value for this parameter is `"14.0.7012.1000, 2020-01-01T12:00:00Z"`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md index 4379af8950..fa861191a0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md @@ -13,7 +13,7 @@ title: Set-OwaMailboxPolicy # Set-OwaMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-OwaMailboxPolicy cmdlet to configure existing Outlook on the web mailbox policies. @@ -163,9 +163,9 @@ Set-OwaMailboxPolicy [-Identity] ## DESCRIPTION In on-premises Exchange, the default Outlook on the web mailbox policy is named Default. In Exchange Online, the default Outlook on the web mailbox policy is named OwaMailboxPolicy-Default. -Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (`Stop-Service WAS -Force` and `Start-Service W3SVC`). +Changes to Outlook on the web mailbox policies might take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (`Stop-Service WAS -Force` and `Start-Service W3SVC`). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -247,7 +247,7 @@ Accept wildcard characters: False The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file types that aren't specified in the Allow, Block, and Force Save lists for file types and MIME types. Valid values are: -- Allow (This is the default value.) +- Allow (This value is the default.) - ForceSave - Block @@ -271,7 +271,7 @@ This parameter is available only in the cloud-based service. The AdditionalStorageProvidersAvailable parameter specifies whether to allow additional storage providers (for example, Box, Dropbox, Facebook, Google Drive, Egnyte, personal OneDrive) attachments in Outlook on the web. Valid values are: -- $true: Additional storage providers are enabled in Outlook on the web. Users can connect their additional storage providers and share files over email. This is the default value. +- $true: Additional storage providers are enabled in Outlook on the web. Users can connect their additional storage providers and share files over email. This value is the default. - $false: Additional storage providers are disabled in Outlook on the web. Users can't connect their additional storage providers or share files over email. ```yaml @@ -292,7 +292,7 @@ Accept wildcard characters: False The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disable Exchange ActiveSync settings in Outlook on the web. Valid values are: -- $true: ActiveSync is available in Outlook on the web. This is the default value. +- $true: ActiveSync is available in Outlook on the web. This value is the default. - $false: ActiveSync isn't available in Outlook on the web. ```yaml @@ -313,7 +313,7 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. To enable or disable personal accounts in the new Outlook for Windows, use the PersonalAccountsEnabled parameter. @@ -335,7 +335,7 @@ Accept wildcard characters: False The AllAddressListsEnabled parameter specifies which address lists are available in Outlook on the web. Valid values are: -- $true: All address lists are visible in Outlook on the web. This is the default value. +- $true: All address lists are visible in Outlook on the web. This value is the default. - $false: Only the global address list is visible in Outlook on the web. ```yaml @@ -356,7 +356,7 @@ Accept wildcard characters: False The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can copy the contents of their Contacts folder to a mobile device's native address book when using Outlook on the web for devices. Valid values are: -- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This is the default value. +- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This value is the default. - $false: Contacts can't be copied to the device's address book in Outlook on the web for devices. ```yaml @@ -462,7 +462,7 @@ The AllowOfflineOn parameter specifies when Outlook Web App in offline mode is a - PrivateComputersOnly: Offline mode is available in private computer sessions. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). - NoComputers: Offline mode is disabled. -- AllComputers: Offline mode is available for public and private computer sessions. This is the default value. +- AllComputers: Offline mode is available for public and private computer sessions. This value is the default. When offline mode is available, users can turn offline mode on or off themselves in Outlook Web App. For more information, see [Use offline settings in Outlook on the web](https://support.microsoft.com/office/a34c9d9d-16ac-4020-b730-ffa7c7540ae7). @@ -631,7 +631,7 @@ This parameter is functional only in on-premises Exchange. The CalendarEnabled parameter specifies whether to enable or disable the calendar in Outlook Web App. Valid values are: -- $true: The Calendar is available in Outlook Web App. This is the default value. +- $true: The Calendar is available in Outlook Web App. This value is the default. - $false: The Calendar isn't available in Outlook Web App. ```yaml @@ -654,7 +654,7 @@ This parameter is functional only in on-premises Exchange. The ChangePasswordEnabled parameter specifies whether users can change their passwords from inside Outlook on the web. Valid values are: -- $true: The Change password option is available in Outlook on the web. This is the default value in on-premises Exchange. +- $true: The Change password option is available in Outlook on the web. This value is the default in on-premises Exchange. - $false: The Change password option isn't available in Outlook on the web. ```yaml @@ -677,7 +677,7 @@ This parameter is available only in the cloud-based service. The ChangeSettingsAccountEnabled parameter specifies whether users can change the email account where app-wide settings (for example, theme and privacy settings) are associated in the new Outlook for Windows. Valid values are: -- $true: Users can change their settings account in the new Outlook for Windows. This is the default value. +- $true: Users can change their settings account in the new Outlook for Windows. This value is the default. - $false: Users can't change their settings account in the new Outlook for Windows. **Note**: The settings account is referred to as the primary account in the new Outlook for Windows setting at Settings \> Accounts \> Email accounts \> Manage. @@ -700,7 +700,7 @@ Accept wildcard characters: False The ClassicAttachmentsEnabled parameter specifies whether users can attach local files as regular email attachments in Outlook on the web. Valid values are: -- $true: Users can attach local files to email messages in Outlook on the web. This is the default value. +- $true: Users can attach local files to email messages in Outlook on the web. This value is the default. - $false: Users can't attach local files to email messages in Outlook on the web. ```yaml @@ -723,11 +723,11 @@ This parameter is available only in the cloud-based service. The ConditionalAccessPolicy parameter specifies the Outlook on the Web Policy for limited access. For this feature to work properly, you also need to configure a Conditional Access policy in the Microsoft Entra admin center. -**Note**: When you enable a Conditional Access policy, users will no longer be able to access the light version of Outlook on the web. An error message will direct them to use the default premium experience. +**Note**: When you enable a Conditional Access policy, users can no longer access the light version of Outlook on the web. An error message directs them to use the default premium experience. Valid values are: -- Off: No conditional access policy is applied to Outlook on the web. This is the default value. +- Off: No conditional access policy is applied to Outlook on the web. This value is the default. - ReadOnly: Users can't download attachments to their local computer, and can't enable Offline Mode on non-compliant computers. They can still view attachments in the browser. This doesn't apply to in-line images. - ReadOnlyPlusAttachmentsBlocked: All restrictions from ReadOnly apply, but users can't view attachments in the browser. This doesn't apply to in-line images. @@ -772,7 +772,7 @@ This parameter is functional only in on-premises Exchange. The ContactsEnabled parameter specifies whether to enable or disable Contacts in Outlook Web App. Valid values are: -- $true: Contacts are available in Outlook Web App. This is the default value. +- $true: Contacts are available in Outlook Web App. This value is the default. - $false: Contacts aren't available in Outlook Web App. ```yaml @@ -791,7 +791,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Int32 @@ -811,7 +811,7 @@ Accept wildcard characters: False The DefaultTheme parameter specifies the default theme that's used in Outlook on the web when the user hasn't selected a theme. The default value is blank ($null). For more information about the built-in themes that are available in Outlook on the web, see [Default Outlook on the web themes in Exchange](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016). -Note that this parameter is a text string, and the value you specify isn't validated against the list of available themes. +This parameter is a text string, and the value you specify isn't validated against the list of available themes. ```yaml Type: String @@ -833,7 +833,7 @@ This parameter is functional only in on-premises Exchange. The DelegateAccessEnabled parameter specifies whether delegates can use Outlook on the web or Outlook Web App to open folders that they have delegate access to. Valid values are: -- $true: Delegates can open the mailbox in Outlook on the web. This is the default value. +- $true: Delegates can open the mailbox in Outlook on the web. This value is the default. - $false: Delegates can't open the mailbox in Outlook on the web. ```yaml @@ -854,8 +854,8 @@ Accept wildcard characters: False The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for private computer sessions. Valid values are: -- $true: Open is available for attachments in Outlook on the web for private computer sessions. This is the default value. -- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. +- $true: Open is available for attachments in Outlook on the web for private computer sessions. This value is the default. +- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Office and .pdf documents can still be previewed in Outlook on the web. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. @@ -877,8 +877,8 @@ Accept wildcard characters: False The DirectFileAccessOnPublicComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for public computer sessions. Valid values are: -- $true: Open is available for attachments in Outlook on the web for public computer sessions. This is the default value. -- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. +- $true: Open is available for attachments in Outlook on the web for public computer sessions. This value is the default. +- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Office and .pdf documents can still be previewed in Outlook on the web. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). @@ -927,7 +927,7 @@ Accept wildcard characters: False The DisplayPhotosEnabled parameter specifies whether users see sender photos in Outlook on the web. Valid values are: -- $true: Users see sender photos in Outlook on the web. This is the default value. +- $true: Users see sender photos in Outlook on the web. This value is the default. - $false: Users don't see sender photos in Outlook on the web. ```yaml @@ -1010,7 +1010,7 @@ This parameter is functional only in on-premises Exchange. The ExplicitLogonEnabled parameter specifies whether to allow a user to open someone else's mailbox in Outlook on the web (provided that user has permissions to the mailbox). Valid values are: -- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This is the default value. +- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This value is the default. - $false: A user with the required permissions isn't able to open someone else's mailbox in Outlook on the web. ```yaml @@ -1033,7 +1033,7 @@ This parameter is available only in the cloud-based service. The ExternalImageProxyEnabled parameter specifies whether to load all external images through the Outlook external image proxy. Valid values are: -- $true: All external images are loaded through the Outlook external image proxy. This is the default value. +- $true: All external images are loaded through the Outlook external image proxy. This value is the default. - $false: All external images are loaded through the web browser. This is potentially unsafe, as the images could have mixed content or malformed images that ask for user credentials. ```yaml @@ -1076,7 +1076,7 @@ This cmdlet is available only in the cloud-based service. The FeedbackEnabled parameter specifies whether to enable or disable inline feedback surveys in Outlook on the web. Valid values are: -- $true: Inline feedback surveys are enabled. This is the default value. +- $true: Inline feedback surveys are enabled. This value is the default. - $false: Inline feedback surveys are disabled. Surveys allow users to provide feedback on specific features. For example, for the text predictions feature, the inline feedback "Are the above autocomplete suggestions helpful (yes/no)?" is shown. If a user chooses "no" they can provide specific feedback. @@ -1100,7 +1100,7 @@ Accept wildcard characters: False The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are filtered before they can be saved from Outlook on the web. Valid values are: - $true: The attachments specified by the ForceSaveFileTypes parameter are filtered before they can be saved from Outlook on the web. -- $false: The attachments aren't filtered before they're saved. This is the default value. +- $false: The attachments aren't filtered before they're saved. This value is the default. ```yaml Type: Boolean @@ -1183,7 +1183,7 @@ Accept wildcard characters: False The ForceWacViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) before opening the file in the local application. Valid values are: - $true: Private computers must first preview an Office file as a web page in Office Online Server before opening the file. -- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. +- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. @@ -1206,7 +1206,7 @@ Accept wildcard characters: False The ForceWacViewingFirstOnPublicComputers parameter specifies whether public computers must first preview an Office file as a web page in Office Online Server before opening the file in the local application. Valid values are: - $true: Public computers must first preview an Office file as a web page in Office Online Server before opening the file. -- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. +- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). @@ -1231,7 +1231,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013 The ForceWebReadyDocumentViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: - $true: Private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. -- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. +- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. @@ -1256,7 +1256,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013 The ForceWebReadyDocumentViewingFirstOnPublicComputers parameter specifies whether Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: - $true: Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. -- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. +- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). @@ -1298,7 +1298,7 @@ Accept wildcard characters: False The GlobalAddressListEnabled parameter specifies whether the global address list is available in Outlook on the web. Valid values are: -- $true: The global address list is visible in Outlook on the web. This is the default value. +- $true: The global address list is visible in Outlook on the web. This value is the default. - $false: The global address list isn't visible in Outlook on the web. ```yaml @@ -1341,7 +1341,7 @@ This parameter is functional only in the cloud-based service. The GroupCreationEnabled parameter specifies whether Microsoft 365 Group creation is available in Outlook and Outlook on the web. Valid values are: -- $true: Users can create Microsoft 365 Groups in Outlook and Outlook on the web. This is the default value. +- $true: Users can create Microsoft 365 Groups in Outlook and Outlook on the web. This value is the default. - $false: Users can't create Microsoft 365 Groups in Outlook and Outlook on the web. ```yaml @@ -1365,7 +1365,7 @@ This parameter is available only in the cloud-based service. The HideClassicOutlookToggleOut parameter specifies whether to enable or disable hiding the toggle in new Outlook that allows users to switch back to classic Outlook. Valid values are: - $true: The toggle to switch back to classic Outlook is hidden in new Outlook for Windows. -- $false: The toggle to switch back to classic Outlook isn't hidden in new Outlook for Windows. This is the default value. +- $false: The toggle to switch back to classic Outlook isn't hidden in new Outlook for Windows. This value is the default. ```yaml Type: System.Boolean @@ -1385,7 +1385,7 @@ Accept wildcard characters: False The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. This does not affect chat capabilities provided by Skype for Business or Teams. Valid values are: -- $true: Instant messaging is available in Outlook on the web. This is the default value. +- $true: Instant messaging is available in Outlook on the web. This value is the default. - $false: Instant messaging isn't available in Outlook on the web. ```yaml @@ -1406,8 +1406,8 @@ Accept wildcard characters: False The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are: -- None: This is the default value in on-premises Exchange. -- Ocs: Lync or Skype (formerly known as Office Communication Server). This is the default value in Exchange Online. +- None: This value is the default in on-premises Exchange. +- Ocs: Lync or Skype (formerly known as Office Communication Server). This value is the default in Exchange Online. ```yaml Type: InstantMessagingTypeOptions @@ -1429,7 +1429,7 @@ This parameter is available only in the cloud-based service. The InterestingCalendarsEnabled parameter specifies whether interesting calendars are available in Outlook on the web. Valid values are: -- $true: Interesting calendars are available in Outlook on thew web. This is the default value. +- $true: Interesting calendars are available in Outlook on thew web. This value is the default. - $false: Interesting calendars aren't available in Outlook on the web. ```yaml @@ -1470,7 +1470,7 @@ Accept wildcard characters: False The IRMEnabled parameter specifies whether Information Rights Management (IRM) features are available in Outlook on the web. Valid values are: -- $true: IRM is available in Outlook on the web. This is the default value. +- $true: IRM is available in Outlook on the web. This value is the default. - $false: IRM isn't available in Outlook on the web. ```yaml @@ -1493,7 +1493,7 @@ The IsDefault switch specifies whether the Outlook on the web policy is the defa If another policy is currently set as the default, this switch replaces the old default policy with this policy. -**Note**: In Exchange Online - and excluding resource mailboxes - this value will be superseded by the **OwaMailboxPolicy** parameter in each organization's [CASMailboxPlan](https://learn.microsoft.com/powershell/module/exchangepowershell/set-casmailboxplan). That value will instead be applied per each mailbox's SKU. +**Note**: In Exchange Online - and excluding resource mailboxes - this value is superseded by the _OwaMailboxPolicy_ parameter on the [Set- CASMailboxPlan](https://learn.microsoft.com/powershell/module/exchangepowershell/set-casmailboxplan) cmdlet. That value is applied instead per each mailbox's license. ```yaml Type: SwitchParameter @@ -1516,7 +1516,7 @@ This parameter is available only in the cloud-based service. The ItemsToOtherAccountsEnabled parameter specifies whether users can move or copy email messages between accounts. Valid values are: - $true: Users can move and copy messages to and from external accounts. -- $false: Users can't move or copy messages to and from external accounts. This is the default value. +- $false: Users can't move or copy messages to and from external accounts. This value is the default. **Note:** This policy doesn't affect moving or copying messages between Microsoft 365 Groups and shared mailboxes within the organization. @@ -1538,7 +1538,7 @@ Accept wildcard characters: False The JournalEnabled parameter specifies whether the Journal folder is available in Outlook on the web. Valid values are: -- $true: The Journal folder is visible in Outlook on the web. This is the default value. +- $true: The Journal folder is visible in Outlook on the web. This value is the default. - $false: The Journal folder isn't visible in Outlook on the web. ```yaml @@ -1561,7 +1561,7 @@ This parameter is available only in on-premises Exchange. The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk email management are available in Outlook on the web. Valid values are: -- $true: The Junk Email folder and junk email management are available in Outlook on the web. This is the default value. +- $true: The Junk Email folder and junk email management are available in Outlook on the web. This value is the default. - $false: The Junk Email folder and junk email management aren't available in Outlook on the web. ```yaml @@ -1605,7 +1605,7 @@ This parameter is available only in the cloud-based service. The LocalEventsEnabled parameter specifies whether local events calendars are available in Outlook on the web. Valid values are: - $true: Local events are available in Outlook on the web. -- $false: Local events aren't available in Outlook on the web. This is the default value. +- $false: Local events aren't available in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -1705,7 +1705,7 @@ Accept wildcard characters: False The NotesEnabled parameter specifies whether the Notes folder is available in Outlook on the web. Valid values are: -- $true: The Notes folder is visible in Outlook on the web. This is the default value. +- $true: The Notes folder is visible in Outlook on the web. This value is the default. - $false: The Notes folder isn't visible in Outlook on the web. ```yaml @@ -1728,7 +1728,7 @@ This parameter is available only in the cloud-based service. The NpsSurveysEnabled parameter specifies whether to enable or disable the Net Promoter Score (NPS) survey in Outlook on the web. The survey allows users to rate Outlook on the web on a scale of 1 to 5, and to provide feedback and suggested improvements in free text. Valid values are: -- $true: The NPS survey is available in Outlook on the web. This is the default value. +- $true: The NPS survey is available in Outlook on the web. This value is the default. - $false: The NPS survey isn't available in Outlook on the web. ```yaml @@ -1751,7 +1751,7 @@ This parameter is available only in the cloud-based service. The OfflineEnabledWeb parameter specifies whether offline capabilities are available in Outlook on the web, including saving items to the local device (view items without an internet connection). Valid values are: -- $true: Users can manage offline capabilities in Outlook on the web. This is the default value. +- $true: Users can manage offline capabilities in Outlook on the web. This value is the default. - $false: Users can't manage offline capabilities in Outlook on the web. No items are saved to the user's device. Previously save items are deleted. When offline capabilities are available, users can turn offline capabilities on or off themselves in Outlook on the web at Settings \> General \> Offline. @@ -1776,7 +1776,7 @@ This parameter is available only in the cloud-based service. The OfflineEnabledWin parameter specifies whether offline capabilities are available in the new Outlook for Windows, including saving items to the local device (view items without an internet connection). Valid values are: -- $true: Users can manage offline capabilities in the new Outlook for Windows. This is the default value. +- $true: Users can manage offline capabilities in the new Outlook for Windows. This value is the default. - $false: Users can't manage offline capabilities in the new Outlook for Windows. No items are saved to the user's device. Previously save items are deleted. When offline capabilities are available, users can turn offline capabilities on or off themselves in the New Outlook for Windows at Settings \> General \> Offline. By default, offline capabilities are turned on. @@ -1797,7 +1797,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. To enable or disable personal OneDrive in Outlook on the web, use the AdditionalStorageProvidersAvailable parameter. @@ -1821,7 +1821,7 @@ This parameter is available only in the cloud-based service. The OneWinNativeOutlookEnabled parameter controls the availability of the new Outlook for Windows App. Valid values are: -- $true: The New Outlook for Windows App is available. This is the default value. +- $true: The New Outlook for Windows App is available. This value is the default. - $false: The new Outlook for Windows App isn't available. ```yaml @@ -1841,8 +1841,8 @@ Accept wildcard characters: False The OnSendAddinsEnabled parameter specifies whether a mail item can be edited while an on-send add-in is processing it in Outlook on the web or the new Outlook on Windows. Valid values are: -- $true: A user can't edit a mail item while an on-send add-in is processing the item. -- $false: A user can edit a mail item while an on-send add-in is processing the item. This is the default value. +- $true: On send add-ins are enabled. +- $false: On send add-ins are disabled. This value is the default. ```yaml Type: Boolean @@ -1880,7 +1880,7 @@ Accept wildcard characters: False The OutboundCharset parameter specifies the character set that's used for outgoing messages in Outlook on the web. Valid values are: -- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This is the default value. +- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This value is the default. - AlwaysUTF8: Always use UTF-8 encoded Unicode characters in outgoing messages, regardless of the detected text in the message, or the user's language choice in Outlook on the web. Use this value if replies to UTF-8 encoded messages aren't being encoded in UTF-8. - UserLanguageChoice: Use the user's language choice in Outlook on the web to encode outgoing messages. @@ -1904,7 +1904,7 @@ This parameter is available only in the cloud-based service. The OutlookBetaToggleEnabled parameter specifies whether to enable or disable the Outlook on the web Preview toggle. The Preview toggle allows users to try the new Outlook on the web experience. Valid values are: -- $true: The Outlook on the web Preview toggle is enabled. Users can easily switch back and forth between both experiences. This is the default value. +- $true: The Outlook on the web Preview toggle is enabled. Users can easily switch back and forth between both experiences. This value is the default. - $false: Outlook on the web Preview is disabled. ```yaml @@ -1930,7 +1930,7 @@ The OutlookNewslettersAccessLevelAccess parameter specifies the access level in - NoAccess: No access to Outlook Newsletters in the New Outlook for Windows or Outlook on the web. Users can still read email messages sent or forwarded to them. - ReadOnly: Read newsletters and browse pages in Outlook Newsletters. - ReadWrite: Full authoring permissions to create pages and newsletters in Outlook Newsletters. -- Undefined: This is the default value. Currently, this value is equivalent to NoAccess. +- Undefined: This value is the default. Currently, this value is equivalent to NoAccess. ```yaml Type: OutlookNewslettersAccessLevel @@ -1982,7 +1982,7 @@ The OutlookNewslettersReactions parameter specifies whether reactions are enable - DefaultOff: The controls are turned off. - DefaultOn: The controls are turned on. - Disabled: The controls are disabled for users. -- Undefined: This is the default value. +- Undefined: This value is the default. ```yaml Type: OutlookNewslettersFeatureState @@ -2007,7 +2007,7 @@ The OutlookNewslettersShowMore parameter specifies whether recommendations to ot - DefaultOff: Recommendations are turned off. - DefaultOn: Recommendations are turned on. - Disabled: Recommendations are disabled for users. -- Undefined: This is the default value. +- Undefined: This value is the default. Authors can disable these recommendations for each individual newsletter edition, or admins can use this parameter to globally disable these recommendations. @@ -2029,7 +2029,7 @@ Accept wildcard characters: False The OWALightEnabled parameter controls the availability of the light version of Outlook on the web. Valid values are: -- $true: The light version of Outlook on the web is available. This is the default value. +- $true: The light version of Outlook on the web is available. This value is the default. - $false: The light version of Outlook on the web isn't available. This setting prevents access to Outlook on the web for unsupported browsers that can only use the light version of Outlook on the web. ```yaml @@ -2052,7 +2052,7 @@ This parameter is available only in Exchange Server 2010. The OWAMiniEnabled parameter controls the availability of the mini version of Outlook Web App. Valid values are: -- $true: The mini version of Outlook Web App is available. This is the default value. +- $true: The mini version of Outlook Web App is available. This value is the default. - $false: The mini version of Outlook Web App isn't available. ```yaml @@ -2075,7 +2075,7 @@ This parameter is available only in the cloud-based service. The PersonalAccountCalendarsEnabled parameter specifies whether to allow users to connect to their personal Outlook.com or Google Calendar in Outlook on the web. Valid values are: -- $true: Users can connect to their Outlook.com or Google Calendar to see those events in their Outlook on the web calendar. This is the default value. +- $true: Users can connect to their Outlook.com or Google Calendar to see those events in their Outlook on the web calendar. This value is the default. - $false: Users can't connect to their Outlook.com or Google Calendar in Outlook on the web. ```yaml @@ -2098,7 +2098,7 @@ This parameter is available only in the cloud-based service. The PersonalAccountsEnabled parameter specifies whether to allow users to add their personal accounts (for example, Outlook.com, Gmail, or Yahoo!) in the new Outlook for Windows. Valid values are: -- $true: Users can add their personal accounts in the new Outlook for Windows. This is the default value. +- $true: Users can add their personal accounts in the new Outlook for Windows. This value is the default. - $false: Users can't add their personal accounts in the new Outlook for Windows. ```yaml @@ -2139,7 +2139,7 @@ This parameter is available only in the cloud-based service. The PlacesEnabled parameter specifies whether to enable or disable Places in Outlook on the web. Places lets users search, share, and map location details by using Bing. Valid values are: -- $true: Places is enabled. This is the default value. +- $true: Places is enabled. This value is the default. - $false: Places is disabled. ```yaml @@ -2160,7 +2160,7 @@ Accept wildcard characters: False The PremiumClientEnabled parameter controls the availability of the full version of Outlook Web App. Valid values are: -- $true: The full version of Outlook Web App is available for supported browsers. This is the default value. +- $true: The full version of Outlook Web App is available for supported browsers. This value is the default. - $false: The full version of Outlook Web App isn't available. ```yaml @@ -2183,7 +2183,7 @@ This parameter is available only in the cloud-based service. The PrintWithoutDownloadEnabled specifies whether to allow printing of supported files without downloading the attachment in Outlook on the web. Valid values are: -- $true: Supported files can be printed without being downloaded in Outlook on the web. This is the default value. +- $true: Supported files can be printed without being downloaded in Outlook on the web. This value is the default. - $false: Supported files must be downloaded before they can be printed in Outlook on the web. ```yaml @@ -2209,7 +2209,7 @@ This parameter is available only in the cloud-based service. The ProjectMocaEnabled parameter enables or disables access to Project Moca in Outlook on the web. Valid values are: - $true: Access to Project Moca is enabled in Outlook on the web. -- $false: Access to Project Moca is disabled in Outlook on the web. This is the default value. +- $false: Access to Project Moca is disabled in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2231,7 +2231,7 @@ This parameter is functional only in Exchange Server 2010. The PublicFoldersEnabled parameter specifies whether a user can browse or read items in public folders in Outlook Web App. Valid values are: -- $true: Public folders are available in Outlook Web App. This is the default value. +- $true: Public folders are available in Outlook Web App. This value is the default. - $false: Public folders aren't available in Outlook Web App. ```yaml @@ -2254,7 +2254,7 @@ This parameter is functional only in Exchange Server 2010. The RecoverDeletedItemsEnabled parameter specifies whether a user can use Outlook Web App to view, recover, or delete permanently items that have been deleted from the Deleted Items folder. Valid values are: -- $true: Users can view, recover, or permanently delete items in Outlook Web App. This is the default value. +- $true: Users can view, recover, or permanently delete items in Outlook Web App. This value is the default. - $false: Users can't view, recover, or permanently delete items in Outlook Web App. Items deleted from the Deleted Items folder in Outlook Web App are still retained. ```yaml @@ -2275,7 +2275,7 @@ Accept wildcard characters: False The ReferenceAttachmentsEnabled parameter specifies whether users can attach files from the cloud as linked attachments in Outlook on the web. Valid values are: -- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This is the default value. +- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This value is the default. - $false: Users can't share files in the cloud as linked attachments. They need to download a local copy of the file before attaching the file to the email message. ```yaml @@ -2296,7 +2296,7 @@ Accept wildcard characters: False The RemindersAndNotificationsEnabled parameter specifies whether notifications and reminders are enabled in Outlook on the web. Valid values are: -- $true: Notifications and reminders are enabled in Outlook on the web. This is the default value. +- $true: Notifications and reminders are enabled in Outlook on the web. This value is the default. - $false: Notifications and reminders are disabled in Outlook on the web. This parameter doesn't apply to the light version of Outlook Web App. @@ -2321,7 +2321,7 @@ Accept wildcard characters: False The ReportJunkEmailEnabled parameter specifies whether users can report messages as junk or not junk to Microsoft in Outlook on the web. Valid values are: -- $true: This is the default value. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. +- $true: This value is the default. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. - $false: Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox with no option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk** moves the message to the Junk Email folder with no option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. This parameter is meaningful only when the JunkEmailEnabled parameter is set to $true. @@ -2344,7 +2344,7 @@ Accept wildcard characters: False The RulesEnabled parameter specifies whether a user can view, create, or modify server-side rules in Outlook on the web. Valid values are: -- $true: Users can view, create, or modify server-side rules in Outlook on the web. This is the default value. +- $true: Users can view, create, or modify server-side rules in Outlook on the web. This value is the default. - $false: Users can't view, create, or modify server-side rules in Outlook on the web. ```yaml @@ -2365,7 +2365,7 @@ Accept wildcard characters: False The SatisfactionEnabled parameter specifies whether to enable or disable the satisfaction survey. Valid values are: -- $true: The satisfaction survey is enabled. This is the default value. +- $true: The satisfaction survey is enabled. This value is the default. - $false: The satisfaction survey is disabled. ```yaml @@ -2386,7 +2386,7 @@ Accept wildcard characters: False The SaveAttachmentsToCloudEnabled parameter specifies whether users can save regular email attachments to the cloud. Valid values are: -- $true: Users can save regular email attachments to the cloud. This is the default value. +- $true: Users can save regular email attachments to the cloud. This value is the default. - $false: Users can only save regular email attachments locally. ```yaml @@ -2407,7 +2407,7 @@ Accept wildcard characters: False The SearchFoldersEnabled parameter specifies whether Search Folders are available in Outlook on the web. Valid values are: -- $true: Search Folders are visible in Outlook on the Web. This is the default value. +- $true: Search Folders are visible in Outlook on the Web. This value is the default. - $false: Search Folders aren't visible in Outlook on the Web. ```yaml @@ -2428,7 +2428,7 @@ Accept wildcard characters: False The SetPhotoEnabled parameter specifies whether users can add, change, and remove their sender photo in Outlook on the web. Valid values are: -- $true: Users can manage their photos in Outlook on the web. This is the default value. +- $true: Users can manage their photos in Outlook on the web. This value is the default. - $false: Users can't manage their user photo in Outlook on the web. **Note**: To control whether users can update photos for Exchange Online, see [Configure User Administrator support for profile photo updates](https://learn.microsoft.com/graph/profilephoto-configure-settings#configure-user-administrator-support-for-profile-photo-updates). @@ -2449,7 +2449,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The SetPhotoURL parameter controls where users go to select their photo. Note that you can't specify a URL that contains one or more picture files, as there is no mechanism to copy a URL photo to the properties of the users' Exchange Online mailboxes. +The SetPhotoURL parameter controls where users go to select their photo. You can't specify a URL that contains one or more picture files, as there's no mechanism to copy a URL photo to the properties of Exchange Online mailboxes. ```yaml Type: String @@ -2489,7 +2489,7 @@ Accept wildcard characters: False The SignaturesEnabled parameter specifies whether to enable or disable the use of signatures in Outlook on the web. Valid values are: -- $true: Signatures are available in Outlook on the web. This is the default value. +- $true: Signatures are available in Outlook on the web. This value is the default. - $false: Signatures aren't available in Outlook on the web. ```yaml @@ -2512,7 +2512,7 @@ This parameter is functional only in Exchange Server 2010. The SilverlightEnabled parameter specifies whether a user can use Microsoft Silverlight features in Outlook Web App. Valid values are: -- $true: Silverlight features are available in Outlook Web App. This is the default value. +- $true: Silverlight features are available in Outlook Web App. This value is the default. - $false: Silverlight features aren't available in Outlook Web App. ```yaml @@ -2535,7 +2535,7 @@ This parameter is functional only in the cloud-based service. The SkipCreateUnifiedGroupCustomSharepointClassification parameter specifies whether to skip a custom SharePoint page during the creation of Microsoft 365 Groups in Outlook on the web. Valid values are: -- $true: The custom SharePoint page is skipped when a user creates a Microsoft 365 Group in Outlook on the web. This is the default value. +- $true: The custom SharePoint page is skipped when a user creates a Microsoft 365 Group in Outlook on the web. This value is the default. - $false: The custom SharePoint page is shown when a user creates a Microsoft 365 Group in Outlook on the web. ```yaml @@ -2558,7 +2558,7 @@ This parameter is functional only in Exchange Server 2010. The SMimeEnabled parameter specifies whether users can download the S/MIME control for Outlook Web App and use it to read and compose signed and encrypted messages. Valid values are: -- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This is the default value. +- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This value is the default. - $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated. **Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://learn.microsoft.com/Exchange/policy-and-compliance/smime). @@ -2603,7 +2603,7 @@ This parameter is functional only in Exchange Server 2010. The SpellCheckerEnabled parameter specifies whether to enable or disable the built-in Outlook Web App spell checker in the full version of Outlook Web App. Valid values are: -- $true: Spell checking is available in Outlook Web App. This is the default value. +- $true: Spell checking is available in Outlook Web App. This value is the default. - $false: Spell checking isn't available in Outlook Web App. This parameter doesn't apply to the light version of Outlook Web App. @@ -2628,7 +2628,7 @@ This parameter is functional only in on-premises Exchange. The TasksEnabled parameter specifies whether Tasks folder is available in Outlook Web App. Valid values are: -- $true: The Tasks folder is available in Outlook Web App. This is the default value. +- $true: The Tasks folder is available in Outlook Web App. This value is the default. - $false: The Tasks folder isn't available in Outlook Web App. This parameter doesn't apply to the light version of Outlook Web App. @@ -2653,7 +2653,7 @@ This parameter is available only in the cloud-based service. The TeamSnapCalendarsEnabled parameter specifies whether to allow users to connect to their personal TeamSnap calendars in Outlook on the web. Valid values are: -- $true: Users can connect to their TeamSnap calendars to see those events in their Outlook on the web calendar. This is the default value. +- $true: Users can connect to their TeamSnap calendars to see those events in their Outlook on the web calendar. This value is the default. - $false: Users can't connect to their TeamSnap calendars in Outlook on the web. ```yaml @@ -2674,7 +2674,7 @@ Accept wildcard characters: False The TextMessagingEnabled parameter specifies whether users can send and receive text messages in Outlook on the web. Valid values are: -- $true: Text messaging is available in Outlook on the web. This is the default value. +- $true: Text messaging is available in Outlook on the web. This value is the default. - $false: Text messaging isn't available in Outlook on the web. This parameter doesn't apply to the light version of Outlook on the web. @@ -2697,7 +2697,7 @@ Accept wildcard characters: False The ThemeSelectionEnabled parameter specifies whether users can change the theme in Outlook on the web. Valid values are: -- $true: Users can specify the theme in Outlook on the web. This is the default value. +- $true: Users can specify the theme in Outlook on the web. This value is the default. - $false: Users can't specify or change the theme in Outlook on the web. ```yaml @@ -2738,10 +2738,10 @@ Accept wildcard characters: False The UMIntegrationEnabled parameter specifies whether Unified Messaging (UM) integration is enabled in Outlook on the web. Valid values are: -- $true: UM integration is enabled in Outlook on the web. This is the default value. +- $true: UM integration is enabled in Outlook on the web. This value is the default. - $false: UM integration is disabled in Outlook on the web. -This setting applies only if Unified Messaging has been enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). +This setting applies only if Unified Messaging is enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). This parameter doesn't apply to the light version of Outlook on the web. @@ -2763,7 +2763,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -2783,7 +2783,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -2804,7 +2804,7 @@ Accept wildcard characters: False The UseGB18030 parameter specifies whether to use the GB18030 character set instead of GB2312 in Outlook on the web. Valid values are: - $true: GB18030 is used wherever GB2312 would have been used in Outlook on the web. -- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This is the default value. +- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2825,7 +2825,7 @@ Accept wildcard characters: False The UseISO885915 parameter specifies whether to use the character set ISO8859-15 instead of ISO8859-1 in Outlook on the web. Valid values are: - $true: ISO8859-15 is used wherever ISO8859-1 would have been used in Outlook on the web. -- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This is the default value. +- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2847,7 +2847,7 @@ This parameter is functional only in the cloud-based service. The UserVoiceEnabled parameter specifies whether to enable or disable Outlook UserVoice in Outlook on the web. Outlook UserVoice is a customer feedback area that's available in Microsoft 365. Valid values are: -- $true: Outlook UserVoice is enabled. This is the default value. +- $true: Outlook UserVoice is enabled. This value is the default. - $false: Outlook UserVoice is disabled. ```yaml @@ -2868,7 +2868,7 @@ Accept wildcard characters: False The WacEditingEnabled parameter specifies whether to enable or disable editing documents in Outlook on the web by using Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). Valid values are: -- $true: Users can edit supported documents in Outlook on the web. This is the default value. +- $true: Users can edit supported documents in Outlook on the web. This value is the default. - $false: Users can't edit supported documents in Outlook on the web. ```yaml @@ -2889,7 +2889,7 @@ Accept wildcard characters: False The WacExternalServicesEnabled parameter specifies whether to enable or disable external services when viewing documents in Outlook on the web (for example, machine translation) by using Office Online Server. Valid values are: -- $true: External services are enabled when viewing supported documents in Outlook on the web. This is the default value. +- $true: External services are enabled when viewing supported documents in Outlook on the web. This value is the default. - $false: External services are disabled when viewing supported documents in Outlook on the web. ```yaml @@ -2911,7 +2911,7 @@ Accept wildcard characters: False The WacOMEXEnabled parameter specifies whether to enable or disable apps for Outlook in Outlook on the web in Office Online Server. Valid values are: - $true: apps for Outlook are enabled in Outlook on the web. -- $false: apps for Outlook are disabled in Outlook on the web. This is the default value. +- $false: apps for Outlook are disabled in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2931,7 +2931,7 @@ Accept wildcard characters: False The WacViewingOnPrivateComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents private computer sessions in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). By default, all Outlook on the web sessions are considered to be on private computers. Valid values are: -- $true: In private computer sessions, users can view supported Office documents in the web browser. This is the default value. +- $true: In private computer sessions, users can view supported Office documents in the web browser. This value is the default. - $false: In private computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. @@ -2954,7 +2954,7 @@ Accept wildcard characters: False The WacViewingOnPublicComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents in public computer sessions in Office Online Server. Valid values are: -- $true: In public computer sessions, users can view supported Office documents in the web browser. This is the default value. +- $true: In public computer sessions, users can view supported Office documents in the web browser. This value is the default. - $false: In public computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). @@ -2979,7 +2979,7 @@ This parameter is available only in the cloud-based service. The WeatherEnabled parameter specifies whether to enable or disable weather information in the calendar in Outlook on the web. Valid values are: -- $true: Weather is enabled. This is the default value. +- $true: Weather is enabled. This value is the default. - $false: Weather is disabled. ```yaml @@ -3001,7 +3001,7 @@ Accept wildcard characters: False The WebPartsFrameOptionsType parameter specifies what sources can access web parts in IFRAME or FRAME elements in Outlook on the web. Valid values are: - None: There are no restrictions on displaying Outlook on the web content in a frame. -- SameOrigin: This is the default value and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. +- SameOrigin: This value is the default and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. - Deny: Blocks display of Outlook on the web content in a frame, regardless of the origin of the site attempting to access it. ```yaml @@ -3024,7 +3024,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are: -- $true: All supported attachment types are available for WebReady Document Viewing. This is the default value. +- $true: All supported attachment types are available for WebReady Document Viewing. This value is the default. - $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are available for WebReady Document Viewing (you can remove values from the lists). ```yaml @@ -3047,7 +3047,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingOnPrivateComputersEnabled parameter specifies whether WebReady Document Viewing is available in private computer sessions. Valid values are: -- $true: WebReady Document Viewing is available in private computer sessions. This is the default value. +- $true: WebReady Document Viewing is available in private computer sessions. This value is the default. - $false: WebReady Document Viewing isn't available in private computer sessions. By default in Exchange 2013, all Outlook on the web sessions are considered to be on private computers. @@ -3072,7 +3072,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingOnPublicComputersEnabled parameter specifies whether WebReady Document Viewing is in public computer sessions. Valid values are: -- $true: WebReady Document Viewing is available for public computer sessions. This is the default value. +- $true: WebReady Document Viewing is available for public computer sessions. This value is the default. - $false: WebReady Document Viewing isn't available for public computer sessions. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet). @@ -3225,10 +3225,9 @@ Accept wildcard characters: False ``` ### -WSSAccessOnPrivateComputersEnabled - > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -3246,7 +3245,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md index bb19fab87e..f60879da83 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md @@ -156,13 +156,13 @@ Before you run the Set-OwaVirtualDirectory cmdlet, consider the following items: - You must have Write access to virtual directory objects in Active Directory. If you don't have the necessary permissions and you try to run the Set-OwaVirtualDirectory cmdlet on the Active Directory virtual directory object, the cmdlet fails. - You must have Write access to virtual directory objects in the metabase for some properties, such as Authentication and GZip. If you don't have the necessary permissions to run the Set-OwaVirtualDirectory cmdlet on a metabase virtual directory object or on a parameter that writes to the metabase, the cmdlet fails. -- Verify that the data source can be read. Depending on the properties that you want to set on an Outlook on the web virtual directory, you may want to run the cmdlet in a test environment on the Outlook on the web virtual directory object in Active Directory, the metabase, or both. +- Verify that the data source can be read. Depending on the properties that you want to set on an Outlook on the web virtual directory, you might want to run the cmdlet in a test environment on the Outlook on the web virtual directory object in Active Directory, the metabase, or both. - You can run the Set-OwaVirtualDirectory cmdlet on any server that has the Exchange Server administration tools installed. - Several parameters for the Set-OwaVirtualDirectory cmdlet can contain more than one value. These are known as multivalued properties. Make sure that you modify multivalued properties correctly. For information, see [Modifying multivalued properties](https://learn.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help). - Many of the Outlook on the web virtual directory settings require you to restart IIS (Stop-Service WAS -Force and Start-Service W3SVC) before the change takes effect. For example, when you enable or disable forms-based authentication, or when you enable or disable the Private computer option on the sign-in page. - To switch from forms-based authentication to Basic authentication, you must first disable forms-based authentication, and then as a separate task, enable Basic authentication. You can't disable forms-based authentication and enable Basic authentication in a single task. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -212,7 +212,7 @@ Accept wildcard characters: False The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file types that aren't specified in the Allow, Block, and Force Save lists for file types and MIME types. Valid values are: -- Allow (This is the default value.) +- Allow (This value is the default.) - ForceSave - Block @@ -234,7 +234,7 @@ Accept wildcard characters: False The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disable Exchange ActiveSync settings in Outlook on the web. Valid values are: -- $true: ActiveSync is available in Outlook on the web. This is the default value. +- $true: ActiveSync is available in Outlook on the web. This value is the default. - $false: ActiveSync isn't available in Outlook on the web ```yaml @@ -256,7 +256,7 @@ Accept wildcard characters: False The AdfsAuthentication parameter enables or disables Active Directory Federation Services (ADFS) authentication on the Outlook on the web virtual directory. Valid values are: - $true: ADFS authentication is enabled. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $true before you can use this value. -- $false: ADFS authentication is disabled. This is the default value. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $false before you can use this value. +- $false: ADFS authentication is disabled. This value is the default. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $false before you can use this value. ```yaml Type: Boolean @@ -276,7 +276,7 @@ Accept wildcard characters: False The AllAddressListsEnabled parameter specifies which address lists are available in Outlook on the web. Valid values are: -- $true: All address lists are visible in Outlook on the web. This is the default value. +- $true: All address lists are visible in Outlook on the web. This value is the default. - $false: Only the global address list is visible in Outlook on the web. ```yaml @@ -297,7 +297,7 @@ Accept wildcard characters: False The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can copy the contents of their Contacts folder to a mobile device's native address book when using Outlook on the web for devices. Valid values are: -- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This is the default value. +- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This value is the default. - $false: Contacts can't be copied to the device's address book in Outlook on the web for devices. ```yaml @@ -381,7 +381,7 @@ The AllowOfflineOn parameter specifies when Outlook on the web in offline mode i - PrivateComputersOnly: Offline mode is available in private computer sessions. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). - NoComputers: Offline mode is disabled. -- AllComputers: Offline mode is available for public and private computer sessions. This is the default value. +- AllComputers: Offline mode is available for public and private computer sessions. This value is the default. When offline mode is available, users can turn offline mode on or off themselves in Outlook on the web. For more information, see [Use offline settings in Outlook on the web](https://support.microsoft.com/office/a34c9d9d-16ac-4020-b730-ffa7c7540ae7). @@ -403,7 +403,7 @@ Accept wildcard characters: False The AnonymousFeaturesEnabled parameter specifies whether you want to allow Outlook on the web users that are logged on anonymously to access specific features. Valid values are: -- $true: Features are enabled for anonymous users. For example, anonymous users can view and change meeting content. This is the default value. +- $true: Features are enabled for anonymous users. For example, anonymous users can view and change meeting content. This value is the default. - $false: Features are disabled for anonymous users. ```yaml @@ -424,7 +424,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. This parameter can be used with the FormsAuthentication parameter or with the DigestAuthentication and WindowsAuthentication parameters. @@ -530,7 +530,7 @@ Accept wildcard characters: False The CalendarEnabled parameter specifies whether to enable or disable the calendar in Outlook on the web. Valid values are: -- $true: The Calendar is available in Outlook on the web. This is the default value. +- $true: The Calendar is available in Outlook on the web. This value is the default. - $false: The Calendar isn't available in Outlook on the web. ```yaml @@ -553,7 +553,7 @@ This parameter is available only in Exchange Server 2010. The CalendarPublishingEnabled parameter specifies whether users can publish their calendar from Outlook Web App. Valid values are: -- $true: Calendar publishing is enabled. This is the default value. +- $true: Calendar publishing is enabled. This value is the default. - $false: Calendar publishing is disabled. ```yaml @@ -574,7 +574,7 @@ Accept wildcard characters: False The ChangePasswordEnabled parameter specifies whether users can change their passwords from inside Outlook on the web. Valid values are: -- $true: The Change password option is available in Outlook on the web. This is the default value in on-premises Exchange. +- $true: The Change password option is available in Outlook on the web. This value is the default in on-premises Exchange. - $false: The Change password option isn't available in Outlook on the web. ```yaml @@ -595,7 +595,7 @@ Accept wildcard characters: False The ClassicAttachmentsEnabled parameter specifies whether users can attach local files as regular email attachments in Outlook on the web. Valid values are: -- $true: Users can attach local files to email messages in Outlook on the web. This is the default value. +- $true: Users can attach local files to email messages in Outlook on the web. This value is the default. - $false: Users can't attach local files to email messages in Outlook on the web. ```yaml @@ -617,7 +617,7 @@ Accept wildcard characters: False The ClientAuthCleanupLevel parameter specifies how much of the cache is cleared when the user logs off from Outlook on the web. Valid values are: - Low -- High (This is the default value) +- High (default value) This parameter doesn't apply to the light version of Outlook on the web. @@ -660,7 +660,7 @@ Accept wildcard characters: False The ContactsEnabled parameter specifies whether to enable or disable Contacts in Outlook on the web. Valid values are: -- $true: Contacts are available in Outlook on the web. This is the default value. +- $true: Contacts are available in Outlook on the web. This value is the default. - $false: Contacts aren't available in Outlook on the web. ```yaml @@ -704,7 +704,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Int32 @@ -742,7 +742,7 @@ Accept wildcard characters: False The DefaultTheme parameter specifies the default theme that's used in Outlook on the web when the user hasn't selected a theme. The default value is blank ($null). For more information about the built-in themes that are available in Outlook on the web, see [Default Outlook on the web themes in Exchange](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016). -Note that this parameter is a text string, and the value you specify isn't validated against the list of available themes. +This parameter is a text string, and the value you specify isn't validated against the list of available themes. ```yaml Type: String @@ -764,7 +764,7 @@ This parameter is functional only in Exchange Server 2010. The DelegateAccessEnabled parameter specifies whether delegates can use Outlook Web App to open folders that they have delegate access to. Valid values are: -- $true: Delegates can open the mailbox in Outlook Web App. This is the default value. +- $true: Delegates can open the mailbox in Outlook Web App. This value is the default. - $false: Delegates can't open the mailbox in Outlook Web App. ```yaml @@ -786,7 +786,7 @@ Accept wildcard characters: False The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are: - $true: Digest authentication is enabled. -- $false: Digest authentication is disabled. This is the default value. +- $false: Digest authentication is disabled. This value is the default. You can use this parameter with the FormsAuthentication parameter. @@ -808,8 +808,8 @@ Accept wildcard characters: False The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for private computer sessions. Valid values are: -- $true: Open is available for attachments in Outlook on the web for private computer sessions. This is the default value. -- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. +- $true: Open is available for attachments in Outlook on the web for private computer sessions. This value is the default. +- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Office and .pdf documents can still be previewed in Outlook on the web. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -831,8 +831,8 @@ Accept wildcard characters: False The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for public computer sessions. Valid values are: -- $true: Open is available for attachments in Outlook on the web for public computer sessions. This is the default value. -- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web. +- $true: Open is available for attachments in Outlook on the web for public computer sessions. This value is the default. +- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Office and .pdf documents can still be previewed in Outlook on the web. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -854,7 +854,7 @@ Accept wildcard characters: False The DisplayPhotosEnabled parameter specifies whether users see sender photos in Outlook on the web. Valid values are: -- $true: Users see sender photos in Outlook on the web. This is the default value. +- $true: Users see sender photos in Outlook on the web. This value is the default. - $false: Users don't see sender photos in Outlook on the web. ```yaml @@ -929,7 +929,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: ExchwebProxyDestinations @@ -949,7 +949,7 @@ Accept wildcard characters: False The ExplicitLogonEnabled parameter specifies whether to allow a user to open someone else's mailbox in Outlook on the web (provided that user has permissions to the mailbox). Valid values are: -- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This is the default value. +- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This value is the default. - $false: A user with the required permissions isn't able to open someone else's mailbox in Outlook on the web. ```yaml @@ -974,7 +974,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -998,7 +998,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null (blank): This is the default value. +- $null (blank): This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -1023,8 +1023,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -1166,7 +1166,7 @@ Accept wildcard characters: False The FilterWebBeaconsAndHtmlForms parameter specifies how web beacons are handled in Outlook on the web. Valid values are: -- UserFilterChoice (This is the default value) +- UserFilterChoice (default value) - ForceFilter - DisableFilter @@ -1189,7 +1189,7 @@ Accept wildcard characters: False The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are filtered before they can be saved from Outlook on the web. Valid values are: - $true: The attachments specified by the ForceSaveFileTypes parameter are filtered before they can be saved from Outlook on the web. -- $false: The attachments aren't filtered before they're saved. This is the default value. +- $false: The attachments aren't filtered before they're saved. This value is the default. ```yaml Type: Boolean @@ -1272,7 +1272,7 @@ Accept wildcard characters: False The ForceWacViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) before opening the file in the local application. Valid values are: - $true: Private computers must first preview an Office file as a web page in Office Online Server before opening the file. -- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. +- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -1295,7 +1295,7 @@ Accept wildcard characters: False The ForceWacViewingFirstOnPublicComputers parameter specifies whether public computers must first preview an Office file as a web page in Office Online Server before opening the file in the local application. Valid values are: - $true: Public computers must first preview an Office file as a web page in Office Online Server before opening the file. -- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value. +- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -1320,7 +1320,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013 The ForceWebReadyDocumentViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: - $true: Private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. -- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. +- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -1345,7 +1345,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013 The ForceWebReadyDocumentViewingFirstOnPublicComputers parameter specifies whether Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: - $true: Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file. -- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value. +- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -1367,7 +1367,7 @@ Accept wildcard characters: False The FormsAuthentication parameter enables or disables forms-based authentication on the Outlook on the web virtual directory. Valid values are: -- $true: Forms-based authentication is enabled in Outlook on the web. This is the default value. The BasicAuthentication parameter is also set to $true, and the DigestAuthentication and WindowsAuthentication parameters are set to $false. +- $true: Forms-based authentication is enabled in Outlook on the web. This value is the default. The BasicAuthentication parameter is also set to $true, and the DigestAuthentication and WindowsAuthentication parameters are set to $false. - $false: Forms-based authentication is disabled in Outlook on the web. ```yaml @@ -1406,7 +1406,7 @@ Accept wildcard characters: False The GlobalAddressListEnabled parameter specifies whether the global address list is available in Outlook on the web. Valid values are: -- $true: The global address list is visible in Outlook on the web. This is the default value. +- $true: The global address list is visible in Outlook on the web. This value is the default. - $false: The global address list isn't visible in Outlook on the web. ```yaml @@ -1446,7 +1446,7 @@ Accept wildcard characters: False The GzipLevel parameter sets Gzip configuration information for the Outlook on the web virtual directory. Valid values are: - Off -- Low (This is the default value) +- Low (default value) - High - Error @@ -1486,7 +1486,7 @@ Accept wildcard characters: False The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. This does not affect chat capabilities provided by Skype for Business or Teams. Valid values are: -- $true: Instant messaging is available in Outlook on the web. This is the default value. +- $true: Instant messaging is available in Outlook on the web. This value is the default. - $false: Instant messaging isn't available in Outlook on the web. ```yaml @@ -1525,7 +1525,7 @@ Accept wildcard characters: False The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are: -- None: This is the default value. +- None: This value is the default. - Ocs: Lync or Skype (formerly known as Office Communication Server). ```yaml @@ -1546,7 +1546,7 @@ Accept wildcard characters: False The IntegratedFeaturesEnabled parameter specifies whether to allow Outlook on the web users who are logged on using Integrated Windows authentication to access specific features. Valid values are: -- $true: Integrated features are enabled. For example, users logged on using Integrated Windows authentication can view and change meeting content. This is the default value. +- $true: Integrated features are enabled. For example, users logged on using Integrated Windows authentication can view and change meeting content. This value is the default. - $false: Integrated features are disabled. ```yaml @@ -1625,7 +1625,7 @@ Accept wildcard characters: False The IRMEnabled parameter specifies whether Information Rights Management (IRM) features are available in Outlook on the web. Valid values are: -- $true: IRM is available in Outlook on the web. This is the default value. +- $true: IRM is available in Outlook on the web. This value is the default. - $false: IRM isn't available in Outlook on the web. ```yaml @@ -1647,7 +1647,7 @@ Accept wildcard characters: False The IsPublic parameter specifies whether external users use the virtual directory for Outlook on the web in multiple virtual directory environments (you've configured separate virtual directories on the same server for internal vs. external Outlook on the web connections). Valid values are: - $true: External users use the virtual directory for Outlook on the web. -- $false: External users don't use the virtual directory for Outlook on the web. This is the default value. +- $false: External users don't use the virtual directory for Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -1667,7 +1667,7 @@ Accept wildcard characters: False The JournalEnabled parameter specifies whether the Journal folder is available in Outlook on the web. Valid values are: -- $true: The Journal folder is visible in Outlook on the web. This is the default value. +- $true: The Journal folder is visible in Outlook on the web. This value is the default. - $false: The Journal folder isn't visible in Outlook on the web. ```yaml @@ -1688,7 +1688,7 @@ Accept wildcard characters: False The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk email management are available in Outlook on the web. Valid values are: -- $true: The Junk Email folder and junk email management are available in Outlook on the web. This is the default value. +- $true: The Junk Email folder and junk email management are available in Outlook on the web. This value is the default. - $false: The Junk Email folder and junk email management aren't available in Outlook on the web. ```yaml @@ -1711,7 +1711,7 @@ This parameter is available only in Exchange Server 2010. The LegacyRedirectType parameter specifies the type of redirect that Outlook Web App uses to a legacy Client Access server or Front End server when forms-based authentication isn't used on the Exchange 2010 Outlook Web App virtual directory. Valid values are: -- Silent: A standard redirect is used. This is the default value. +- Silent: A standard redirect is used. This value is the default. - Manual: An intermediate page is displayed to show the legacy URL so that users can change their bookmarks. ```yaml @@ -1754,7 +1754,7 @@ Accept wildcard characters: False The LogonFormat parameter specifies the type of logon format that's required for forms-based authentication on the Outlook on the web sign-in page. Valid values are: -- FullDomain: Requires the format domain\\username. This is the default value. +- FullDomain: Requires the format domain\\username. This value is the default. - UserName: Requires only the username, but you also need to specify a value for the DefaultDomain parameter. - PrincipalName: Requires the user principal name (UPN) (for example, user@contoso.com). This sign-in method works only for users whose UPN name is the same as their email address. @@ -1776,7 +1776,7 @@ Accept wildcard characters: False The LogonPageLightSelectionEnabled parameter specifies whether the Outlook on the web sign-in page includes the option to sign in to the light version of Outlook on the web. Valid values are: -- $true: The option to use the light version of Outlook on the web is available on the sign-in page. This is the default value. +- $true: The option to use the light version of Outlook on the web is available on the sign-in page. This value is the default. - $false: The option to use the light version of Outlook on the web is available on the sign-in page. This parameter is meaningful only for browsers that support the full version of Outlook on the web; unsupported browsers are always required to use the light version of Outlook on the web. @@ -1800,7 +1800,7 @@ Accept wildcard characters: False The LogonPagePublicPrivateSelectionEnabled parameter specifies whether the Outlook on the web sign-in page includes the public/private computer session option at sign-in. Valid values are: - $true: The public/private computer session selection is available on the Outlook on the web sign-in page. -- $false: The public/private computer session selection isn't available on the Outlook on the web sign-in page. All sessions are considered to be on private computers. This is the default value. +- $false: The public/private computer session selection isn't available on the Outlook on the web sign-in page. All sessions are considered to be on private computers. This value is the default. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. Users can only specify public computer sessions if you've set this parameter value to $true. @@ -1824,7 +1824,7 @@ Accept wildcard characters: False The NotesEnabled parameter specifies whether the Notes folder is available in Outlook on the web. Valid values are: -- $true: The Notes folder is visible in Outlook on the web. This is the default value. +- $true: The Notes folder is visible in Outlook on the web. This value is the default. - $false: The Notes folder isn't visible in Outlook on the web. ```yaml @@ -1923,7 +1923,7 @@ Accept wildcard characters: False The OutboundCharset parameter specifies the character set that's used for outgoing messages in Outlook on the web. Valid values are: -- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This is the default value. +- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This value is the default. - AlwaysUTF8: Always use UTF-8 encoded Unicode characters in outgoing messages, regardless of the detected text in the message, or the user's language choice in Outlook on the web. Use this value if replies to UTF-8 encoded messages aren't being encoded in UTF-8. - UserLanguageChoice: Use the user's language choice in Outlook on the web to encode outgoing messages. @@ -1945,7 +1945,7 @@ Accept wildcard characters: False The OWALightEnabled parameter controls the availability of the light version of Outlook on the web. Valid values are: -- $true: The light version of Outlook on the web is available. This is the default value. +- $true: The light version of Outlook on the web is available. This value is the default. - $false: The light version of Outlook on the web is isn't available. This setting prevents access to Outlook on the web for unsupported browsers that can only use the light version of Outlook on the web. ```yaml @@ -1968,7 +1968,7 @@ This parameter is available only in Exchange Server 2010. The OWAMiniEnabled parameter controls the availability of the mini version of Outlook Web App. Valid values are: -- $true: The mini version of Outlook Web App is available. This is the default value. +- $true: The mini version of Outlook Web App is available. This value is the default. - $false: The mini version of Outlook Web App isn't available. ```yaml @@ -1989,7 +1989,7 @@ Accept wildcard characters: False The PremiumClientEnabled parameter controls the availability of the full version of Outlook Web App. Valid values are: -- $true: The full version of Outlook Web App is available for supported browsers. This is the default value. +- $true: The full version of Outlook Web App is available for supported browsers. This value is the default. - $false: The full version of Outlook Web App isn't available. ```yaml @@ -2012,7 +2012,7 @@ This parameter is functional only in Exchange Server 2010. The PublicFoldersEnabled parameter specifies whether a user can browse or read items in public folders in Outlook Web App. Valid values are: -- $true: Public folders are available in Outlook Web App. This is the default value. +- $true: Public folders are available in Outlook Web App. This value is the default. - $false: Public folders aren't available in Outlook Web App. ```yaml @@ -2035,7 +2035,7 @@ This parameter is functional only in Exchange Server 2010. The RecoverDeletedItemsEnabled parameter specifies whether a user can use Outlook Web App to view, recover, or delete permanently items that have been deleted from the Deleted Items folder. Valid values are: -- $true: Users can view, recover, or permanently delete items in Outlook Web App. This is the default value. +- $true: Users can view, recover, or permanently delete items in Outlook Web App. This value is the default. - $false: Users can't view, recover, or permanently delete items in Outlook Web App. Items deleted from the Deleted Items folder in Outlook Web App are still retained. ```yaml @@ -2056,7 +2056,7 @@ Accept wildcard characters: False The RedirectToOptimalOWAServer parameter specifies whether to find the optimal server for Outlook on the web. Valid values are: -- $true: Outlook on the web uses service discovery to find the best Mailbox server to use after a user authenticates. This is the default value. +- $true: Outlook on the web uses service discovery to find the best Mailbox server to use after a user authenticates. This value is the default. - $false: Outlook on the web doesn't redirect clients to the optimal Mailbox server. ```yaml @@ -2077,7 +2077,7 @@ Accept wildcard characters: False The ReferenceAttachmentsEnabled parameter specifies whether users can attach files from the cloud as linked attachments in Outlook on the web. Valid values are: -- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This is the default value. +- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This value is the default. - $false: Users can't share files in the cloud as linked attachments. They need to download a local copy of the file before attaching the file to the email message. ```yaml @@ -2098,7 +2098,7 @@ Accept wildcard characters: False The RemindersAndNotificationsEnabled parameter specifies whether notifications and reminders are enabled in Outlook on the web. Valid values are: -- $true: Notifications and reminders are enabled in Outlook on the web. This is the default value. +- $true: Notifications and reminders are enabled in Outlook on the web. This value is the default. - $false: Notifications and reminders are disabled in Outlook on the web. This parameter doesn't apply to the light version of Outlook Web App. @@ -2121,7 +2121,7 @@ Accept wildcard characters: False This parameter is functional only in Exchange Server 2010. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: RemoteDocumentsActions @@ -2141,7 +2141,7 @@ Accept wildcard characters: False This parameter is functional only in Exchange Server 2010. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: MultiValuedProperty @@ -2161,7 +2161,7 @@ Accept wildcard characters: False This parameter is functional only in Exchange Server 2010. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: MultiValuedProperty @@ -2181,7 +2181,7 @@ Accept wildcard characters: False This parameter is functional only in Exchange Server 2010. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: MultiValuedProperty @@ -2201,7 +2201,7 @@ Accept wildcard characters: False The ReportJunkEmailEnabled parameter specifies whether users can report messages as junk or not junk to Microsoft in Outlook on the web. Valid values are: -- $true: This is the default value. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. +- $true: This value is the default. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. - $false: Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox with no option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk** moves the message to the Junk Email folder with no option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. This parameter is meaningful only when the JunkEmailEnabled parameter is set to $true. @@ -2224,7 +2224,7 @@ Accept wildcard characters: False The RulesEnabled parameter specifies whether a user can view, create, or modify server-side rules in Outlook on the web. Valid values are: -- $true: Users can view, create, or modify server-side rules in Outlook on the web. This is the default value. +- $true: Users can view, create, or modify server-side rules in Outlook on the web. This value is the default. - $false: Users can't view, create, or modify server-side rules in Outlook on the web. ```yaml @@ -2245,7 +2245,7 @@ Accept wildcard characters: False The SaveAttachmentsToCloudEnabled parameter specifies whether users can save regular email attachments to the cloud. Valid values are: -- $true: Users can save regular email attachments to the cloud. This is the default value. +- $true: Users can save regular email attachments to the cloud. This value is the default. - $false: Users can only save regular email attachments locally. ```yaml @@ -2268,7 +2268,7 @@ This parameter is functional only in Exchange Server 2010. The SearchFoldersEnabled parameter specifies whether Search Folders are available in Outlook on the web. Valid values are: -- $true: Search Folders are visible in Outlook on the Web. This is the default value. +- $true: Search Folders are visible in Outlook on the Web. This value is the default. - $false: Search Folders aren't visible in Outlook on the Web. ```yaml @@ -2289,7 +2289,7 @@ Accept wildcard characters: False The SetPhotoEnabled parameter specifies whether users can add, change, and remove their sender photo in Outlook on the web. Valid values are: -- $true: Users can manage their photos in Outlook on the web. This is the default value. +- $true: Users can manage their photos in Outlook on the web. This value is the default. - $false: Users can't manage their user photo in Outlook on the web. ```yaml @@ -2328,7 +2328,7 @@ Accept wildcard characters: False The SignaturesEnabled parameter specifies whether to enable or disable the use of signatures in Outlook on the web. Valid values are: -- $true: Signatures are available in Outlook on the web. This is the default value. +- $true: Signatures are available in Outlook on the web. This value is the default. - $false: Signatures aren't available in Outlook on the web. ```yaml @@ -2351,7 +2351,7 @@ This parameter is functional only in Exchange Server 2010. The SilverlightEnabled parameter specifies whether a user can use Microsoft Silverlight features in Outlook Web App. Valid values are: -- $true: Silverlight features are available in Outlook Web App. This is the default value. +- $true: Silverlight features are available in Outlook Web App. This value is the default. - $false: Silverlight features aren't available in Outlook Web App. ```yaml @@ -2374,7 +2374,7 @@ This parameter is functional only in Exchange Server 2010. The SMimeEnabled parameter specifies whether users can download the S/MIME control for Outlook Web App and use it to read and compose signed and encrypted messages. Valid values are: -- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This is the default value. +- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This value is the default. - $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated. **Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://learn.microsoft.com/Exchange/policy-and-compliance/smime). @@ -2399,7 +2399,7 @@ This parameter is functional only in Exchange Server 2010. The SpellCheckerEnabled parameter specifies whether to enable or disable the built-in Outlook Web App spell checker in the full version of Outlook Web App. Valid values are: -- $true: Spell checking is available in Outlook Web App. This is the default value. +- $true: Spell checking is available in Outlook Web App. This value is the default. - $false: Spell checking isn't available in Outlook Web App. This parameter doesn't apply to the light version of Outlook Web App. @@ -2422,7 +2422,7 @@ Accept wildcard characters: False The TasksEnabled parameter specifies whether Tasks folder is available in Outlook on the web. Valid values are: -- $true: The Tasks folder is available in Outlook on the web. This is the default value. +- $true: The Tasks folder is available in Outlook on the web. This value is the default. - $false: The Tasks folder isn't available in Outlook on the web. This parameter doesn't apply to the light version of Outlook on the web. @@ -2445,7 +2445,7 @@ Accept wildcard characters: False The TextMessagingEnabled parameter specifies whether users can send and receive text messages in Outlook on the web. Valid values are: -- $true: Text messaging is available in Outlook on the web. This is the default value. +- $true: Text messaging is available in Outlook on the web. This value is the default. - $false: Text messaging isn't available in Outlook on the web. This parameter doesn't apply to the light version of Outlook on the web. @@ -2468,7 +2468,7 @@ Accept wildcard characters: False The ThemeSelectionEnabled parameter specifies whether users can change the theme in Outlook on the web. Valid values are: -- $true: Users can specify the theme in Outlook on the web. This is the default value. +- $true: Users can specify the theme in Outlook on the web. This value is the default. - $false: Users can't specify or change the theme in Outlook on the web. ```yaml @@ -2489,10 +2489,10 @@ Accept wildcard characters: False The UMIntegrationEnabled parameter specifies whether Unified Messaging (UM) integration is enabled in Outlook on the web. Valid values are: -- $true: UM integration is enabled in Outlook on the web. This is the default value. +- $true: UM integration is enabled in Outlook on the web. This value is the default. - $false: UM integration is disabled in Outlook on the web. -This setting applies only if Unified Messaging has been enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). +This setting applies only if Unified Messaging is enabled for a user (for example, bu using the Enable-UMMailbox cmdlet). This parameter doesn't apply to the light version of Outlook on the web. @@ -2512,7 +2512,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -2530,7 +2530,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -2551,7 +2551,7 @@ Accept wildcard characters: False The UseGB18030 parameter specifies whether to use the GB18030 character set instead of GB2312 in Outlook on the web. Valid values are: - $true: GB18030 is used wherever GB2312 would have been used in Outlook on the web. -- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This is the default value. +- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2572,7 +2572,7 @@ Accept wildcard characters: False The UseISO885915 parameter specifies whether to use the character set ISO8859-15 instead of ISO8859-1 in Outlook on the web. Valid values are: - $true: ISO8859-15 is used wherever ISO8859-1 would have been used in Outlook on the web. -- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This is the default value. +- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -2610,7 +2610,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: VirtualDirectoryTypes @@ -2630,7 +2630,7 @@ Accept wildcard characters: False The WacEditingEnabled parameter specifies whether to enable or disable editing documents in Outlook on the web by using Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). Valid values are: -- $true: Users can edit supported documents in Outlook on the web. This is the default value. +- $true: Users can edit supported documents in Outlook on the web. This value is the default. - $false: Users can't edit supported documents in Outlook on the web. ```yaml @@ -2651,7 +2651,7 @@ Accept wildcard characters: False The WacViewingOnPrivateComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents private computer sessions in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). By default, all Outlook on the web sessions are considered to be on private computers. Valid values are: -- $true: In private computer sessions, users can view supported Office documents in the web browser. This is the default value. +- $true: In private computer sessions, users can view supported Office documents in the web browser. This value is the default. - $false: In private computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. @@ -2674,7 +2674,7 @@ Accept wildcard characters: False The WacViewingOnPublicComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents in public computer sessions in Office Online Server. Valid values are: -- $true: In public computer sessions, users can view supported Office documents in the web browser. This is the default value. +- $true: In public computer sessions, users can view supported Office documents in the web browser. This value is the default. - $false: In public computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -2698,7 +2698,7 @@ Accept wildcard characters: False The WebPartsFrameOptionsType parameter specifies what sources can access web parts in IFRAME or FRAME elements in Outlook on the web. Valid values are: - None: There are no restrictions on displaying Outlook on the web content in a frame. -- SameOrigin: This is the default value and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. +- SameOrigin: This value is the default and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content. - Deny: Blocks display of Outlook on the web content in a frame, regardless of the origin of the site attempting to access it. ```yaml @@ -2721,7 +2721,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are: -- $true: All supported attachment types are available for WebReady Document Viewing. This is the default value. +- $true: All supported attachment types are available for WebReady Document Viewing. This value is the default. - $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are available for WebReady Document Viewing (you can remove values from the lists). ```yaml @@ -2744,7 +2744,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingOnPrivateComputersEnabled parameter specifies whether WebReady Document Viewing is available in private computer sessions. Valid values are: -- $true: WebReady Document Viewing is available in private computer sessions. This is the default value. +- $true: WebReady Document Viewing is available in private computer sessions. This value is the default. - $false: WebReady Document Viewing isn't available in private computer sessions. By default in Exchange 2013, all Outlook on the web sessions are considered to be on private computers. @@ -2769,7 +2769,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201 The WebReadyDocumentViewingOnPublicComputersEnabled parameter specifies whether WebReady Document Viewing is in public computer sessions. Valid values are: -- $true: WebReady Document Viewing is available for public computer sessions. This is the default value. +- $true: WebReady Document Viewing is available for public computer sessions. This value is the default. - $false: WebReady Document Viewing isn't available for public computer sessions. In Exchange 2013, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -2928,7 +2928,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter enables or disables Integrated Windows authentication on the virtual directory. Valid values are: - $true: Integrated Windows authentication is enabled on the Outlook on the web virtual directory. -- $false: Integrated Windows authentication is disabled on the Outlook on the web virtual directory. This is the default value. +- $false: Integrated Windows authentication is disabled on the Outlook on the web virtual directory. This value is the default. ```yaml Type: Boolean @@ -2946,7 +2946,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean @@ -2964,7 +2964,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md index 7d756ac636..5be97a4965 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md @@ -80,7 +80,7 @@ Set-PartnerApplication [-Identity] ## DESCRIPTION You can configure partner applications such as SharePoint to access Exchange resources. Use the New-PartnerApplication cmdlet to create a partner application configuration for an application that needs to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://learn.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -140,7 +140,7 @@ Accept wildcard characters: False The AccountType parameter specifies the type of Microsoft account that's required for the partner application. Valid values are: -- OrganizationalAccount: This is the default value +- OrganizationalAccount: This value is the default - ConsumerAccount ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md index 406c4a2b4c..2024688f5a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md @@ -36,7 +36,7 @@ Set-PendingFederatedDomain [[-Identity] ] ## DESCRIPTION This cmdlet allows the Exchange admin center to save domains selected as the FederatedOrganizationIdentifier or federated domains when proof of domain ownership hasn't been completed. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md index 49519a0178..b4bb856629 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md @@ -33,7 +33,7 @@ Set-PhishSimOverridePolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -132,7 +132,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether the policy is enabled. Valid values are: -- $true: The policy is enabled. This is the default value. +- $true: The policy is enabled. This value is the default. - $false: The policy is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Place.md b/exchange/exchange-ps/ExchangePowerShell/Set-Place.md index 0fdf11de3f..8cade9febb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Place.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Place.md @@ -53,7 +53,7 @@ Set-Place [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -298,7 +298,7 @@ Accept wildcard characters: False The IsWheelChairAccessible parameter specifies whether the room is wheelchair accessible. Valid values are: - $true: The room is wheelchair accessible. -- $false: The room is not wheelchair accessible. This is the default value. +- $false: The room is not wheelchair accessible. This value is the default. ```yaml Type: Boolean @@ -339,7 +339,7 @@ Accept wildcard characters: False The MTREnabled parameter identifies the room as configured with a Microsoft Teams room system. You can add Teams room systems as audio sources in Teams meetings that involve the room. Valid values are: - $true: The room is has a Teams room system. You can add the Teams room system to Microsoft Teams meetings when selecting to join a meeting with room audio. -- $false: The room is does not have a Teams room system. Users will join Teams meetings using their PC or mobile device audio instead of using room audio. This is the default value. +- $false: The room is does not have a Teams room system. Users join Teams meetings using their PC or mobile device audio instead of using room audio. This value is the default. For more information about Microsoft Teams Rooms, see [Microsoft Teams Rooms](https://learn.microsoft.com/microsoftteams/rooms/). diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md index 6fac58c159..a5938c4bcd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md @@ -321,7 +321,7 @@ The EnableLabelCoauth parameter enables or disables co-authoring support in Offi Disabling co-authoring support in Office desktop apps in the organization has the following consequences: - For apps and services that support the new labeling metadata, they now revert to the original metadata format and location when labels are read or saved. -- The new metadata format and location for Office documents that was used while the setting was enabled will not be copied to the original format and location. As a result, this labeling information for unencrypted Word, Excel, and PowerPoint files will be lost. +- The new metadata format and location for Office documents used while the setting was enabled isn't copied to the original format and location. As a result, this labeling information for unencrypted Word, Excel, and PowerPoint files is lost. - Co-authoring and AutoSave no longer work in your organization for labeled and encrypted documents. - Sensitivity labels remain enabled for Office files in OneDrive and SharePoint. @@ -343,7 +343,7 @@ Accept wildcard characters: False The EnableSpoAipMigration parameter enables or disables built-in labeling for supported Office files in SharePoint and OneDrive. Valid values are: -- $true: Users can apply your sensitivity labels in Office for the web. Users will see the Sensitivity button on the ribbon so they can apply labels, and see any applied label name on the status bar. +- $true: Users can apply your sensitivity labels in Office for the web. Users see the Sensitivity button on the ribbon so they can apply labels, and see any applied label name on the status bar. - $false: Users can't apply your sensitivity labels in Office for the web. ```yaml @@ -589,7 +589,7 @@ Accept wildcard characters: False The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are: - Ignore -- RetryThenBlock (This is the default value) +- RetryThenBlock (default value) ```yaml Type: PolicyRuleErrorAction @@ -610,7 +610,7 @@ Accept wildcard characters: False The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are: -- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This is the default value. +- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default. - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field). - HeaderOrEnvelope: Examine senders in the message header and the message envelope. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md index 3cd1fde963..75a9554dd4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md @@ -13,7 +13,7 @@ title: Set-PolicyTipConfig # Set-PolicyTipConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-PolicyTipConfig cmdlet to modify custom Policy Tips in your organization. You can't modify built-in Policy Tips. @@ -31,7 +31,7 @@ Set-PolicyTipConfig [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md index 47d9968636..0f07bd405a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md @@ -57,7 +57,7 @@ Set-PopSettings [-AuthenticatedConnectionTimeout ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -96,7 +96,7 @@ Set-PopSettings -X509CertificateName mail.contoso.com This example specifies the certificate that contains mail.contoso.com is used to encrypt POP3 client connections. -**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange POP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange POP service (you'll receive an error if you try). +**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange POP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange POP service (you get an error if you try). ## PARAMETERS @@ -146,7 +146,7 @@ Accept wildcard characters: False The CalendarItemRetrievalOption parameter specifies how calendar items are presented to POP3 clients. Valid values are: -- 0 or iCalendar. This is the default value. +- 0 or iCalendar. This value is the default. - 1 or IntranetUrl. - 2 or InternetUrl. - 3 or Custom. @@ -211,7 +211,7 @@ Accept wildcard characters: False The EnableExactRFC822Size parameter specifies how message sizes are presented to POP3 clients. Valid values are: - $true: Calculate the exact message size. Because this setting can negatively affect performance, you should configure it only if it's required by your POP3 clients. -- $false: Use an estimated message size. This is the default value. +- $false: Use an estimated message size. This value is the default. ```yaml Type: Boolean @@ -231,7 +231,7 @@ Accept wildcard characters: False The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Integrated Windows authentication (NTLM) by using the Generic Security Services application programming interface (GSSAPI). This setting applies to connections where Transport Layer Security (TLS) is disabled. Valid values are: -- $true: NTLM for POP3 connections is enabled. This is the default value. +- $true: NTLM for POP3 connections is enabled. This value is the default. - $false: NTLM for POP3 connections is disabled. ```yaml @@ -253,7 +253,7 @@ Accept wildcard characters: False The EnforceCertificateErrors parameter specifies whether to enforce Secure Sockets Layer (SSL) certificate validation failures. Valid values are: - $true: If the certificate isn't valid or doesn't match the target POP3 server's FQDN, the connection attempt fails. -- $false: The server doesn't deny POP3 connections based on certificate errors. This is the default value. +- $false: The server doesn't deny POP3 connections based on certificate errors. This value is the default. ```yaml Type: Boolean @@ -273,7 +273,7 @@ Accept wildcard characters: False The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is used for POP3 connections. Valid values are: -- None: Extended Protection for Authentication isn't used. This is the default value. +- None: Extended Protection for Authentication isn't used. This value is the default. - Allow: Extended Protection for Authentication is used only if it's supported by the incoming POP3 connection. If it's not, Extended Protection for Authentication isn't used. - Require: Extended Protection for Authentication is required for all POP3 connections. If the incoming POP3 connection doesn't support it, the connection is rejected. @@ -373,8 +373,8 @@ Accept wildcard characters: False The LogFileRollOverSettings parameter defines how frequently POP3 protocol logging creates a new log file. Valid values are: -- 1 or Hourly. This is the default value in Exchange 2019 and Exchange 2016. -- 2 or Daily. This is the default value in Exchange 2013 and Exchange 2010. +- 1 or Hourly. This value is the default in Exchange 2019 and Exchange 2016. +- 2 or Daily. This value is the default in Exchange 2013 and Exchange 2010. - 3 or Weekly. - 4 or Monthly. @@ -400,7 +400,7 @@ The LoginType parameter specifies the authentication method for POP3 connections - 1 or PlainTextLogin. - 2 or PlainTextAuthentication. -- 3 or SecureLogin. This is the default value. +- 3 or SecureLogin. This value is the default. ```yaml Type: LoginOptions @@ -428,7 +428,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The default value is 0, which means a new POP3 protocol log file is created at the frequency that's specified by the LogFileRollOverSettings parameter. @@ -529,7 +529,7 @@ The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages - 2 or HtmlAndTextAlternative. - 3 or TextEnrichedOnly. - 4 or TextEnrichedAndTextAlternative. -- 5 or BestBodyFormat. This is the default value. +- 5 or BestBodyFormat. This value is the default. - 6 or Tnef. ```yaml @@ -550,7 +550,7 @@ Accept wildcard characters: False The MessageRetrievalSortOrder parameter specifies how retrieved messages are sorted. Valid values are: -- 0 or Ascending. This is the default value. +- 0 or Ascending. This value is the default. - 1 or Descending. ```yaml @@ -612,7 +612,7 @@ Accept wildcard characters: False The ProtocolLogEnabled parameter specifies whether to enable protocol logging for POP3. Valid values are: - $true: POP3 protocol logging is enabled. -- $false: POP3 protocol logging is disabled. This is the default value. +- $false: POP3 protocol logging is disabled. This value is the default. ```yaml Type: Boolean @@ -700,7 +700,7 @@ Accept wildcard characters: False The SuppressReadReceipt parameter specifies whether to stop duplicate read receipts from being sent to POP3 clients that have the Send read receipts for messages I send setting configured in their POP3 email program. Valid values are: - $true: The sender receives a read receipt only when the recipient opens the message. -- $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This is the default value. +- $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md index 552dbc3950..955bf80c98 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md @@ -41,7 +41,7 @@ Set-PowerShellVirtualDirectory [-Identity] ## DESCRIPTION Although it's possible to modify a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -84,7 +84,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. ```yaml @@ -166,7 +166,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -186,7 +186,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -207,8 +207,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. @@ -303,7 +303,7 @@ Accept wildcard characters: False The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are: -- $true: Integrated Windows authentication is enabled. This is the default value. +- $true: Integrated Windows authentication is enabled. This value is the default. - $false: Integrated Windows authentication is disabled. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md b/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md index 5ed5a8d14e..7df4ae0f1e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md @@ -103,8 +103,8 @@ Accept wildcard characters: False The AggregationType parameter specifies the how the alert policy triggers alerts for multiple occurrences of monitored activity. Valid values are: - None: Alerts are triggered for every occurrence of the activity. -- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This is the default value. -- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). Note that it can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. +- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This value is the default. +- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). It can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity. ```yaml Type: AlertAggregationType @@ -254,7 +254,7 @@ Accept wildcard characters: False The Disabled parameter enables or disables the alert policy. Valid values are: - $true: The alert policy is disabled. -- $false: The alert policy is enabled. This is the default value. +- $false: The alert policy is enabled. This value is the default. ```yaml Type: Boolean @@ -403,7 +403,7 @@ Accept wildcard characters: False The NotifyUserOnFilterMatch parameter specifies whether to trigger an alert for a single event when the alert policy is configured for aggregated activity. Valid values are: - $true: Even though the alert is configured for aggregated activity, a notification is triggered during a match for the activity (basically, an early warning). -- $false: Alerts are triggered according to the specified aggregation type. This is the default value. +- $false: Alerts are triggered according to the specified aggregation type. This value is the default. You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity). @@ -443,10 +443,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications has been reached in the time period, no more notifications are sent for the alert. Valid values are: +The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications is reached in the time period, no more notifications are sent for the alert. Valid values are: - An integer. -- The value $null. This is the default value (no maximum number of notifications for an alert). +- The value $null. This value is the default (no maximum number of notifications for an alert). ```yaml Type: Int32 @@ -467,7 +467,7 @@ Accept wildcard characters: False The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are: - An integer. -- The value $null. This is the default value (no interval for notification throttling). +- The value $null. This value is the default (no interval for notification throttling). ```yaml Type: Int32 @@ -563,7 +563,7 @@ Accept wildcard characters: False The Severity parameter specifies the severity of the detection. Valid values are: -- Low (This is the default value) +- Low (default value) - Medium - High diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md index 1e20ef8860..1482cb835f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md @@ -13,7 +13,7 @@ title: Set-PublicFolder # Set-PublicFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-PublicFolder cmdlet to set the attributes of public folders. @@ -52,7 +52,7 @@ Set-PublicFolder [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -232,7 +232,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 1 through 2TB. @@ -322,7 +322,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 1 through 2GB. @@ -437,7 +437,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The valid input range for this parameter is from 1 through 2TB. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md index fd89adf4ff..a1407b777f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md @@ -49,7 +49,7 @@ Set-PublicFolderDatabase [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,7 +72,7 @@ This example sets the database maintenance schedule on PFDB01 to run daily from Set-PublicFolderDatabase -RetainDeletedItemsUntilBackup $true -Identity 'PFDB01' ``` -This example prevents the deleted items in the public folder database PFDB01 from being permanently deleted until after the database has been backed up. +This example prevents the deleted items in the public folder database PFDB01 from being permanently deleted until after the database is backed up. ## PARAMETERS @@ -433,7 +433,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The ReplicationMessageSize parameter specifies the size of replication messages. Small items may be aggregated into a single replication message that can be as large as this setting, but items larger than this setting are replicated with messages larger than this size. +The ReplicationMessageSize parameter specifies the size of replication messages. Small items might be aggregated into a single replication message that can be as large as this setting, but items larger than this setting are replicated with messages larger than this size. A valid value is a number up to 2 gigabytes (2147482624 bytes). The default value is 300 kilobytes (307200 bytes). @@ -444,7 +444,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. ```yaml Type: ByteQuantifiedSize @@ -462,7 +462,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The ReplicationPeriod parameter specifies the interval at which replication of public folders or content updates may occur. +The ReplicationPeriod parameter specifies the interval at which replication of public folders or content updates might occur. ```yaml Type: UInt32 @@ -480,7 +480,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The ReplicationSchedule parameter specifies the time intervals during which replication of public folders or contents may occur. +The ReplicationSchedule parameter specifies the time intervals during which replication of public folders or contents might occur. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md index d90b6c55ed..a2c4eedfb8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md @@ -56,7 +56,7 @@ Set-PublicFolderMigrationRequest [-Identity] ## DESCRIPTION You can pipeline the Set-PublicFolderMoveRequest cmdlet from the Get-PublicFolderMoveRequestStatistics or Get-PublicFolderMoveRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -222,7 +222,7 @@ The Priority parameter specifies the order in which the request should be proces - Lowest - Lower - Low -- Normal: This is the default value. +- Normal: This value is the default. - High - Higher - Highest diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md index 3a2ffa3548..bc66a72143 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md @@ -39,7 +39,7 @@ Set-QuarantinePermissions -QuarantinePermissionsObject ## DESCRIPTION To see the current value of the permissions object that you want to modify, run the variable name as a command. For example, run the command `$Perms` to see the quarantine policy permissions stored in the `$Perms` variable. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -79,7 +79,7 @@ Accept wildcard characters: False The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are: - $true: Allow sender is available for affected messages in quarantine. -- $false: Allow sender isn't available for affected messages in quarantine. This is the default value. +- $false: Allow sender isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -100,7 +100,7 @@ Accept wildcard characters: False The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are: - $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine. -- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This is the default value. +- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -121,7 +121,7 @@ Accept wildcard characters: False The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are: - $true: Delete messages and Delete from quarantine are available for affected messages in quarantine. -- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value. +- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -142,7 +142,7 @@ Accept wildcard characters: False The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are: - $true: The permission is enabled. -- $false: The permission is disabled. This is the default value. +- $false: The permission is disabled. This value is the default. Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. End-users can't download quarantined messages. @@ -165,7 +165,7 @@ Accept wildcard characters: False The PermissionToPreview parameter specifies whether users are allowed to preview quarantined messages. Valid values are: - $true: Preview message is available for affected messages in quarantine. -- $false: Preview message isn't available for affected messages in quarantine. This is the default value. +- $false: Preview message isn't available for affected messages in quarantine. This value is the default. ```yaml Type: Boolean @@ -232,7 +232,7 @@ Accept wildcard characters: False The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are: - $true: The permission is enabled. -- $false: The permission is disabled. This is the default value. +- $false: The permission is disabled. This value is the default. Currently, this value has no effect on available actions in quarantine notifications or quarantine for affected messages. View message header is always available for affected messages in quarantine. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md index 20659f9134..a80cbc375e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md @@ -52,7 +52,7 @@ Set-QuarantinePolicy [-Identity] ## DESCRIPTION You can't modify the built-in quarantine policies named AdminOnlyAccessPolicy, DefaultFullAccessPolicy, or DefaultFullAccessWithNotificationPolicy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -398,7 +398,7 @@ Accept wildcard characters: False The ESNEnabled parameter specifies whether to enable quarantine notifications (formerly known as end-user spam notifications) for the policy. Valid values are: - $true: Quarantine notifications are enabled. -- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This is the default value. +- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This value is the default. **Note**: If the value of this parameter is $true and the value of the EndUserQuarantinePermissionsValue parameter is 0 (No access where all permissions are turned off), users can view their messages in quarantine, but the only available action for the messages is **View message header**. @@ -439,7 +439,7 @@ Accept wildcard characters: False The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send quarantine notifications for quarantined messages from blocked sender addresses. Valid values are: - $true: Recipients get quarantine notifications for affected messages from blocked senders. -- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This is the default value. +- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This value is the default. ```yaml Type: Boolean @@ -536,7 +536,7 @@ Accept wildcard characters: False The OrganizationBrandingEnabled parameter enables or disables organization branding in the end-user quarantine notification messages. Valid values are: - $true: Organization branding is enabled. The default Microsoft logo that's used in quarantine notifications is replaced by your custom logo. Before you do this, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your custom logo. -- $false: Organization branding is disabled. The default Microsoft logo is used in quarantine notifications. This is the default value. +- $false: Organization branding is disabled. The default Microsoft logo is used in quarantine notifications. This value is the default. This setting is available only in the built-in quarantine policy named DefaultGlobalTag that controls global settings. To access this quarantine policy, start your command with the following syntax: `Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy | Set-QuarantinePolicy ...`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md index 26d5d4ef44..27c19d4d2b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md @@ -16,7 +16,7 @@ title: Set-RMSTemplate This cmdlet is available only in the cloud-based service. > [!NOTE] -> This cmdlet has been deprecated. If you use AD RMS with Exchange Online, you need to migrate to Azure Information Protection before you can use message encryption. For more information, see [Verify that Azure Rights Management is active](https://learn.microsoft.com/purview/set-up-new-message-encryption-capabilities#verify-that-azure-rights-management-is-active). +> This cmdlet is deprecated. If you use AD RMS with Exchange Online, you need to migrate to Azure Information Protection before you can use message encryption. For more information, see [Verify that Azure Rights Management is active](https://learn.microsoft.com/purview/set-up-new-message-encryption-capabilities#verify-that-azure-rights-management-is-active). Use the Set-RMSTemplate cmdlet to modify the properties of an existing Active Directory Rights Management Services (AD RMS) template in your organization. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md index 4e14c8daab..c84552f4b2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md @@ -83,7 +83,7 @@ Set-ReceiveConnector [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -130,7 +130,7 @@ Accept wildcard characters: False The AdvertiseClientSettings parameter specifies whether the SMTP server name, port number, and authentication settings for the Receive connector are displayed to users in the options of Outlook on the web. Valid values are: - $true: The SMTP values are displayed in Outlook on the web. Typically, you would only use this setting for a Receive connector with the usage type Client (authenticated SMTP connections on TCP port 587 for POP3 and IMAP4 clients). -- $false: The SMTP values are displayed in Outlook on the web. This is the default value. +- $false: The SMTP values are displayed in Outlook on the web. This value is the default. ```yaml Type: Boolean @@ -182,7 +182,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019 -The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that may be abusing the connection. The default value is 5 seconds. +The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that might be abusing the connection. The default value is 5 seconds. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. @@ -231,7 +231,7 @@ Accept wildcard characters: False The BareLinefeedRejectionEnabled parameter specifies whether this Receive connector rejects messages that contain line feed (LF) characters without immediately preceding carriage return characters (CR) in the SMTP DATA stream. This condition is known as bare line feeds. Valid values are: - $true: Messages that contain bare line feeds are rejected. -- $false: Messages that contain bare line feeds aren't rejected. This is the default value. +- $false: Messages that contain bare line feeds aren't rejected. This value is the default. Although message that contain bare line feeds might be delivered successfully, these messages don't follow SMTP protocol standards and might cause problems on messaging servers. @@ -253,7 +253,7 @@ Accept wildcard characters: False The BinaryMimeEnabled parameter specifies whether the BINARYMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This is the default value. +- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This value is the default. - $false: BINARYMIME is disabled and isn't advertised in the EHLO response. The binary MIME extension is defined in RFC 3030. @@ -301,7 +301,7 @@ Accept wildcard characters: False The ChunkingEnabled parameter specifies whether the CHUNKING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: CHUNKING is enabled and is advertised in the EHLO response. This is the default value. +- $true: CHUNKING is enabled and is advertised in the EHLO response. This value is the default. - $false: CHUNKING is disabled and isn't advertised in the EHLO response. Chunking is defined in RFC 3030. @@ -443,7 +443,7 @@ Accept wildcard characters: False The DeliveryStatusNotificationEnabled parameter specifies whether the DSN (delivery status notification) Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: DSN is enabled and is advertised in the EHLO response. This is the default value. +- $true: DSN is enabled and is advertised in the EHLO response. This value is the default. - $false: DSN is disabled and isn't advertised in the EHLO response. Delivery status notifications are defined in RFC 3461. @@ -489,7 +489,7 @@ The DomainSecureEnabled parameter specifies whether to enable or disable mutual - $true: Mutual TLS authentication is enabled. - $false: Mutual TLS authentication is disabled. -Note that setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication: +Setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication: - The AuthMechanism parameter must contain the value Tls, and can't contain the value ExternalAuthoritative. - The domain that's used for mutual TLS authentication must be configured in the following locations: @@ -515,7 +515,7 @@ Accept wildcard characters: False The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: 8BITMIME is enabled and is advertised in the EHLO response. This is the default value. +- $true: 8BITMIME is enabled and is advertised in the EHLO response. This value is the default. - $false: 8BITMIME is disabled and isn't advertised in the EHLO response. 8-bit data transmission is defined in RFC 6152. @@ -561,7 +561,7 @@ Accept wildcard characters: False The Enabled parameter specifies whether to enable or disable the Receive connector. Valid values are: -- $true: The Receive connector is enabled. This is the default value. +- $true: The Receive connector is enabled. This value is the default. - $false: The Receive connector is disabled. ```yaml @@ -582,7 +582,7 @@ Accept wildcard characters: False The EnhancedStatusCodesEnabled parameter specifies whether the ENHANCEDSTATUSCODES Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This is the default value. +- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This value is the default. - $false: ENHANCEDSTATUSCODES is disabled and isn't advertised in the EHLO response. Enhanced status codes are defined in RFC 2034. @@ -605,9 +605,9 @@ Accept wildcard characters: False The ExtendedProtectionPolicy parameter specifies how you want to use Extended Protection for Authentication on the Receive connector.Valid values are: -- None: Extended Protection for Authentication won't be used. This is the default value. -- Allow: Extended Protection for Authentication will be used only if the connecting host supports it. Otherwise, the connections will be established without Extended Protection for Authentication. -- Require: Extended Protection for Authentication will be required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection will be rejected. +- None: Extended Protection for Authentication aren't used. This value is the default. +- Allow: Extended Protection for Authentication are used only if the connecting host supports it. Otherwise, the connections are established without Extended Protection for Authentication. +- Require: Extended Protection for Authentication is required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection is rejected. Extended Protection for Authentication enhances the protection and handling of credentials when authenticating network connections using Integrated Windows authentication. Integrated Windows authentication is also known as NTLM. We strongly recommend that you use Extended Protection for Authentication if you are using Integrated Windows authentication. @@ -657,7 +657,7 @@ Accept wildcard characters: False The LongAddressesEnabled parameter specifies whether the Receive connector accepts long X.400 email addresses. The X.400 email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. Valid values are: - $true: X.400 email addresses can be up to 1,860 characters long after IMCEA encapsulation. -- $false: The maximum length of a complete SMTP email address is 571 characters. This is the default value. +- $false: The maximum length of a complete SMTP email address is 571 characters. This value is the default. When you set this parameter to the value $true the following changes are made to the Receive connector: @@ -685,7 +685,7 @@ Accept wildcard characters: False This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. -The MaxAcknowledgementDelay parameter specifies the period the transport server delays acknowledgement when receiving messages from a host that doesn't support shadow redundancy. When receiving messages from a host that doesn't support shadow redundancy, a Microsoft Exchange Server 2010 transport server delays issuing an acknowledgement until it verifies that the message has been successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server times out and issues an acknowledgement anyway. The default value is 30 seconds. +The MaxAcknowledgementDelay parameter specifies the period the transport server delays acknowledgement when receiving messages from a host that doesn't support shadow redundancy. When receiving messages from a host that doesn't support shadow redundancy, a Microsoft Exchange Server 2010 transport server delays issuing an acknowledgement until it verifies that the message is successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server times out and issues an acknowledgement anyway. The default value is 30 seconds. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -714,7 +714,7 @@ When you enter a value, qualify the value with one of the following units: - MB (megabytes) - GB (gigabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value is from 1 to 2147483647 bytes. @@ -872,7 +872,7 @@ When you enter a value, qualify the value with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. A valid value for this parameter is from 65536 to 2147483647 bytes. @@ -1004,7 +1004,7 @@ Accept wildcard characters: False The OrarEnabled parameter enables or disables Originator Requested Alternate Recipient (ORAR) on the Receive connector. Valid values are: - $true: ORAR is enabled and is advertised in the XORAR keyword in the EHLO response. The actual ORAR information is transmitted in the RCPT TO SMTP command. -- $false: ORAR is disabled and is isn't advertised in the EHLO response. This is the default value. +- $false: ORAR is disabled and is isn't advertised in the EHLO response. This value is the default. If the email address specified in the ORAR information is a long X.400 email address, you need to set the LongAddressesEnabled parameter to the value $true. @@ -1058,7 +1058,7 @@ Accept wildcard characters: False The PipeliningEnabled parameter specifies whether the PIPELINING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: -- $true: PIPELINING is enabled and is advertised in the EHLO response. This is the default value. +- $true: PIPELINING is enabled and is advertised in the EHLO response. This value is the default. - $false: PIPELINING is disabled and isn't advertised in the EHLO response. Pipelining is defined in RFC 2920. @@ -1081,7 +1081,7 @@ Accept wildcard characters: False The ProtocolLoggingLevel parameter specifies whether to enable or disable protocol logging for the Receive connector. Valid values are: -- None: Protocol logging is disabled on the Receive connector. This is the default value. +- None: Protocol logging is disabled on the Receive connector. This value is the default. - Verbose: Protocol logging is enabled on the Receive connector. For more information about protocol logging, see [Protocol logging](https://learn.microsoft.com/Exchange/mail-flow/connectors/protocol-logging). @@ -1105,7 +1105,7 @@ Accept wildcard characters: False The RejectReservedSecondLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved second-level domains as specified in RFC 2606 (example.com, example.net, or example.org). Valid value are: - $true: RCPT TO commands that contain reserved second-level domains are rejected. -- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This is the default value. +- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1126,7 +1126,7 @@ Accept wildcard characters: False The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved top-level domains (TLDs) as specified in RFC 2606 (.test, .example, .invalid, or .localhost). Valid value are: - $true: RCPT TO commands that contain reserved TLDs are rejected. -- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This is the default value. +- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1147,7 +1147,7 @@ Accept wildcard characters: False The RejectSingleLabelRecipientDomains parameter specifies whether to reject connections that contain recipients in single-label domains (for example, chris@contoso instead of chris@contoso.com). Valid values are: - $true: RCPT TO commands that contain single-label domains are rejected. -- $false: RCPT TO commands that contain single-label domains aren't rejected. This is the default value. +- $false: RCPT TO commands that contain single-label domains aren't rejected. This value is the default. ```yaml Type: Boolean @@ -1200,7 +1200,7 @@ Accept wildcard characters: False The RequireEHLODomain parameter specifies whether the client must provide a domain name in the EHLO handshake after the SMTP connection is established. Valid values are: - $true: The client must provide a domain name in the EHLO handshake. If it doesn't, the SMTP connection is closed. -- $false: The client isn't required to provide a domain name in the EHLO handshake. This is the default value. +- $false: The client isn't required to provide a domain name in the EHLO handshake. This value is the default. ```yaml Type: Boolean @@ -1221,7 +1221,7 @@ Accept wildcard characters: False The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are: - $true: Inbound messages on the Receive connector require TLS transmission. -- $false: Inbound messages on the Receive connector don't require TLS transmission. This is the default value. +- $false: Inbound messages on the Receive connector don't require TLS transmission. This value is the default. ```yaml Type: Boolean @@ -1259,7 +1259,7 @@ Accept wildcard characters: False The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are: -- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This is the default value. +- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This value is the default. - Disabled: SIZE is disabled and isn't advertised in the EHLO response. - EnabledwithoutValue: SIZE is enabled and is advertised in the EHLO response, but the value of the MaxMessageSize parameter isn't disclosed in the EHLO response. This setting allows messages to bypass message size checks for authenticated connections between Mailbox servers. @@ -1302,7 +1302,7 @@ Accept wildcard characters: False The SuppressXAnonymousTls parameter specifies whether the X-ANONYMOUSTLS Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: X-ANONYMOUSTLS is disabled and isn't advertised in the EHLO response. This setting also requires that you set the UseDownGradedExchangeServerAuth parameter to the value $true on the Set-TransportService cmdlet on the server. -- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This is the default value. +- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This value is the default. The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter contains the value ExchangeServer. @@ -1322,7 +1322,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The TarpitInterval parameter specifies the period of time to delay an SMTP response to a remote server that may be abusing the connection. The default value is 00:00:05 (5 seconds). +The TarpitInterval parameter specifies the period of time to delay an SMTP response to a remote server that might be abusing the connection. The default value is 00:00:05 (5 seconds). To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md index 74a5aae2c5..a2b2f7d24f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md @@ -35,7 +35,7 @@ Set-RecipientFilterConfig [-BlockedRecipients ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md index 862f6a7ab6..fedde7df9c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md @@ -49,7 +49,7 @@ This example configures customized review notification text and review reminder The IsCustomizedNotificationTemplate switch specifies whether to use a customized review notification instead of the system default notification. Valid values are: - $true: Use a customized review notification. You specify the notification text using the CustomizedNotificationDataString parameter. -- $false: Use the default system notification. This is the default value. +- $false: Use the default system notification. This value is the default. ```yaml Type: Boolean @@ -70,7 +70,7 @@ Accept wildcard characters: False The IsCustomizedReminderTemplate switch specifies whether to use a customized review reminder instead of the system default reminder: - $true: Use a customized review reminder. You specify the reminder text using the CustomizedReminderDataString parameter. -- $false: Use the default system reminder. This is the default value. +- $false: Use the default system reminder. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md b/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md index 4379121dc8..1450683bf3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md @@ -47,7 +47,7 @@ The Enabled parameter specifies whether to show or hide the UI option in retenti $true: The option to mark content as a regulatory record is visible in the UI for retention label settings. -$false: The option to mark content as a regulatory record is not visible in the UI for retention label settings. This is the default value. +$false: The option to mark content as a regulatory record is not visible in the UI for retention label settings. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md index 278351fb3b..ed3e25485e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md @@ -13,7 +13,7 @@ title: Set-RemoteDomain # Set-RemoteDomain ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-RemoteDomain cmdlet to configure a managed connection for a remote domain. @@ -57,7 +57,7 @@ Set-RemoteDomain [-Identity] ## DESCRIPTION When you set a remote domain, you can control mail flow with more precision, specify message formatting and policy and specify acceptable character sets for messages sent to or received from the remote domain. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -109,7 +109,7 @@ Accept wildcard characters: False The AllowedOOFType parameter specifies the type of automatic replies or out-of-office (also known as OOF) notifications than can be sent to recipients in the remote domain. Valid values are: -- External: Only automatic replies that are designated as external are sent to recipients in the remote domain. This is the default value. +- External: Only automatic replies that are designated as external are sent to recipients in the remote domain. This value is the default. - ExternalLegacy: Only external automatic replies or automatic replies that aren't designated as internal or external are sent to recipients in the remote domain. - InternalLegacy: Only internal automatic replies or automatic replies that aren't designated as internal or external are sent to recipients in the remote domain. - None: No automatic replies are sent to recipients in the remote domain. @@ -137,8 +137,8 @@ Accept wildcard characters: False The AutoForwardEnabled parameter specifies whether to allow messages that are auto-forwarded by client email programs in your organization. Valid values are: -- $true: Auto-forwarded messages are delivered to recipients in the remote domain. This is the default value for new remote domains that you create and the built-in remote domain named Default in Exchange Online. -- $false: Auto-forwarded messages aren't delivered to recipients in the remote domain. This is the default value for the built-in remote domain named Default in on-premises Exchange. +- $true: Auto-forwarded messages are delivered to recipients in the remote domain. This value is the default for new remote domains that you create and the built-in remote domain named Default in Exchange Online. +- $false: Auto-forwarded messages aren't delivered to recipients in the remote domain. This value is the default for the built-in remote domain named Default in on-premises Exchange. ```yaml Type: Boolean @@ -158,8 +158,8 @@ Accept wildcard characters: False The AutoReplyEnabled parameter specifies whether to allow messages that are automatic replies from client email programs in your organization (for example, automatic reply messages that are generated by rules in Outlook). Valid values are: -- $true: Automatic replies are delivered to recipients in the remote domain. This is the default value for new remote domains that you create and the built-in remote domain named Default in Exchange Online. -- $false: Automatic replies aren't delivered to recipients in the remote domain. This is the default value for the built-in remote domain named Default in on-premises Exchange. +- $true: Automatic replies are delivered to recipients in the remote domain. This value is the default for new remote domains that you create and the built-in remote domain named Default in Exchange Online. +- $false: Automatic replies aren't delivered to recipients in the remote domain. This value is the default for the built-in remote domain named Default in on-premises Exchange. ```yaml Type: Boolean @@ -186,7 +186,7 @@ The ByteEncoderTypeFor7BitCharsets parameter specifies the 7-bit transfer encodi - UseBase64HtmlDetectTextPlain: Use Base64 encoding for HTML and for plain text, unless line wrapping is enabled in plain text. If line wrapping is enabled in plain text, use Base64 encoding for HTML, and use 7-bit encoding for plain text. - UseQPHtml7BitTextPlain: Always use QP encoding for HTML. Always use 7-bit encoding for plain text. - UseBase64Html7BitTextPlain: Always use Base64 encoding for HTML. Always use 7-bit encoding for plain text. -- Undefined: Always use QP encoding for HTML and plain text. This is the default value. +- Undefined: Always use QP encoding for HTML and plain text. This value is the default. ```yaml Type: ByteEncoderTypeFor7BitCharsetsEnum @@ -251,7 +251,7 @@ Accept wildcard characters: False The ContentType parameter specifies the outbound message content type and formatting. Valid values are: -- MimeHtmlText: Converts messages to MIME messages that use HTML formatting, unless the original message is a text message. If the original message is a text message, the outbound message is a MIME message that uses text formatting. This is the default value. +- MimeHtmlText: Converts messages to MIME messages that use HTML formatting, unless the original message is a text message. If the original message is a text message, the outbound message is a MIME message that uses text formatting. This value is the default. - MimeText: Converts all messages to MIME messages that use text formatting. - MimeHtml: Converts all messages to MIME messages that use HTML formatting. @@ -273,7 +273,7 @@ Accept wildcard characters: False The DeliveryReportEnabled parameter specifies whether to allow delivery reports from client software in your organization to recipients in the remote domain. Valid values are: -- $true: Delivery reports are delivered to recipients in the remote domain. This is the default value. +- $true: Delivery reports are delivered to recipients in the remote domain. This value is the default. - $false: Delivery reports aren't delivered to recipients in the remote domain. ```yaml @@ -296,7 +296,7 @@ Accept wildcard characters: False The DisplaySenderName parameter specifies whether to show the sender's Display Name in the From email address for messages sent to recipients in the remote domain. Valid values are: -- $true: Sender names are displayed in messages sent to recipients in the remote domain. This is the default value. +- $true: Sender names are displayed in messages sent to recipients in the remote domain. This value is the default. - $false. Sender names aren't displayed in messages sent to recipients in the remote domain. ```yaml @@ -342,7 +342,7 @@ This parameter is available only in Exchange Server 2010. The IsCoexistenceDomain parameter specifies whether this remote domain is used to represent your Exchange Online organization. Valid values are: - $true: The remote domain represents your Exchange Online organization. -- $false: The remote domain doesn't represent your Exchange Online organization. This is the default value. +- $false: The remote domain doesn't represent your Exchange Online organization. This value is the default. ```yaml Type: Boolean @@ -363,7 +363,7 @@ Accept wildcard characters: False The IsInternal parameter specifies whether the recipients in the remote domain are considered to be internal recipients. Valid values are: - $true: All transport components (for example, transport rules) treat recipients in the remote domain as internal recipients. Typically, you use this value in cross-forest deployments. -- $false: Recipients in the remote domain are treated as external recipients. This is the default value. +- $false: Recipients in the remote domain are treated as external recipients. This value is the default. The value of this parameter is affected by the value of the AllowedOOFType parameter, and vice-versa: @@ -406,7 +406,7 @@ Accept wildcard characters: False The MeetingForwardNotificationEnabled parameter specifies whether to enable meeting forward notifications for recipients in the remote domain. Valid values are: -- $true: Meeting requests forwarded to recipients in the remote domain generate a meeting forward notification to the meeting organizer. This is the default value. +- $true: Meeting requests forwarded to recipients in the remote domain generate a meeting forward notification to the meeting organizer. This value is the default. - $false: Meeting requests forwarded to recipients in the remote domain don't generate a meeting forward notification to the meeting organizer. ```yaml @@ -469,7 +469,7 @@ This parameter is functional only in on-premises Exchange. The NDRDiagnosticInfoEnabled parameter specifies whether diagnostic information is included in non-delivery reports (also known NDRs or bounce messages) that are sent to recipients the remote domain. Valid values are: -- $true: The diagnostic information of an NDR includes details that help administrators troubleshoot delivery problems. This detailed information includes internal server names. This is the default value. +- $true: The diagnostic information of an NDR includes details that help administrators troubleshoot delivery problems. This detailed information includes internal server names. This value is the default. - $false: The diagnostic information section in the NDR body as well as internal server headers from the attached original message headers are removed from the NDR. This parameter is meaningful only when the value of the NDREnabled parameter is $true. @@ -492,7 +492,7 @@ Accept wildcard characters: False The NDREnabled parameter specifies whether to allow non-delivery reports (also known NDRs or bounce messages) from your organization to recipients in the remote domain. Valid values are: -- $true: NDRs from your organization are sent to recipients in the remote domain. This is the default value. +- $true: NDRs from your organization are sent to recipients in the remote domain. This value is the default. - $false: NDRs from your organization aren't sent to recipients in the remote domain. ```yaml @@ -540,7 +540,7 @@ The PreferredInternetCodePageForShiftJis parameter specifies the specific code p - 50220: Use ISO-2022-JP codepage. - 50221: Use ESC-2022-JP codepage. - 50222: Use SIO-2022-JP codepage. -- Undefined: No codepage is defined. This is the default value. +- Undefined: No codepage is defined. This value is the default. ```yaml Type: PreferredInternetCodePageForShiftJisEnum @@ -560,7 +560,7 @@ Accept wildcard characters: False The RequiredCharsetCoverage parameter specifies a percentage threshold for characters in a message that must match to apply your organization's preferred character set before switching to automatic character set detection. -For example, if you set this parameter to 60, the preferred character sets will still be used during content conversion for messages that contain characters from non-preferred character sets as long as the percentage of those characters is 40 percent or less. If the percentage of characters in a message doesn't belong to preferred character sets, Exchange analyzes the Unicode characters and automatically determines the best matching character set to use. +For example, if you set this parameter to 60, the preferred character sets are still used during content conversion for messages that contain characters from non-preferred character sets as long as the percentage of those characters is 40 percent or less. If the percentage of characters in a message doesn't belong to preferred character sets, Exchange analyzes the Unicode characters and automatically determines the best matching character set to use. If recipients in the remote domain use characters that span character sets, you might want to specify a lower percentage to ensure that your organization's preferred character set is used during content conversion. @@ -603,7 +603,7 @@ Accept wildcard characters: False The TargetDeliveryDomain parameter specifies whether the remote domain is used in cross-forest deployments to generate target email addresses for new mail users that represent users in the other organization (for example, all mailboxes hosted on Exchange Online are represented as mail users in your on-premises organization). Valid values are: - $true: The remote domain is used for the target email address of mail users that represent the users in the other forest. -- $false: The remote domain isn't used for the target email address of mail users that represent the users in the other forest. This is the default value. +- $false: The remote domain isn't used for the target email address of mail users that represent the users in the other forest. This value is the default. ```yaml Type: Boolean @@ -625,7 +625,7 @@ The TNEFEnabled parameter specifies whether Transport Neutral Encapsulation Form - $true: TNEF encoding is used on all messages sent to the remote domain. - $false: TNEF encoding isn't used on any messages sent to the remote domain. -- $null (blank): TNEF encoding isn't specified for the remote domain. This is the default value. TNEF encoding for recipients in the remote domain is controlled by the value of the UseMapiRichTextFormat parameter for any mail user or mail contact objects, the sender's per-recipient settings in Outlook, or the sender's default internet message settings in Outlook +- $null (blank): TNEF encoding isn't specified for the remote domain. This value is the default. TNEF encoding for recipients in the remote domain is controlled by the value of the UseMapiRichTextFormat parameter for any mail user or mail contact objects, the sender's per-recipient settings in Outlook, or the sender's default internet message settings in Outlook ```yaml Type: Boolean @@ -645,8 +645,8 @@ Accept wildcard characters: False The TrustedMailInboundEnabled parameter specifies whether messages from senders in the remote domain are treated as trusted messages. Valid values are: -- $true: Inbound messages from senders in the remote domain are considered safe and will bypass content filtering and recipient filtering. -- $false: Inbound messages from senders in the remote domain won't bypass content filtering and recipient filtering. This is the default value. +- $true: Inbound messages from senders in the remote domain are considered safe and skip content filtering and recipient filtering. +- $false: Inbound messages from senders in the remote domain don't bypass content filtering and recipient filtering. This value is the default. ```yaml Type: Boolean @@ -666,8 +666,8 @@ Accept wildcard characters: False The TrustedMailOutboundEnabled parameter specifies whether messages sent to recipients in the remote domain are treated as trusted messages. Valid values are: -- $true: Outbound messages to recipients in the remote domain are considered safe and will bypass content filtering and recipient filtering. We recommend that you use this value in cross-forest deployments. -- $false: Outbound messages to recipients in the remote domain won't bypass content filtering and recipient filtering. This is the default value. +- $true: Outbound messages to recipients in the remote domain are considered safe and skip content filtering and recipient filtering. We recommend that you use this value in cross-forest deployments. +- $false: Outbound messages to recipients in the remote domain don't bypass content filtering and recipient filtering. This value is the default. ```yaml Type: Boolean @@ -688,7 +688,7 @@ Accept wildcard characters: False The UseSimpleDisplayName parameter specifies whether the sender's simple display name is used for the From email address in messages sent to recipients in the remote domain. Valid values are: - $true: Simple display names are used in messages sent to recipients in the remote domain. If the sender doesn't have a simple display name configured, the From email address is `EmailAddress `. -- $false: Simple display names aren't used in messages sent to recipients in the remote domain. This is the default value. +- $false: Simple display names aren't used in messages sent to recipients in the remote domain. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md index 9ddb71e508..c561807539 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md @@ -93,7 +93,7 @@ Some attributes on mailboxes in the service can only be configured by connecting Directory synchronization must be configured correctly for changes made to an on-premises mail user to be applied to a mailbox in the service. Changing the configuration of the mailbox in the service isn't immediate and depends on the directory synchronization schedule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -102,14 +102,14 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Set-RemoteMailbox -Identity davids -Type Room ``` -This example configures the mailbox in the service that's associated with the specified mail user as a room resource mailbox. This example assumes that directory synchronization has been configured. +This example configures the mailbox in the service that's associated with the specified mail user as a room resource mailbox. This example assumes that directory synchronization is configured. ### Example 2 ```powershell Set-RemoteMailbox -Identity kima -AcceptMessagesOnlyFrom davids,"Executive Team",bill@contoso.com ``` -This example configures delivery restrictions for the mailbox in the service that's associated with the specified mail user. This example assumes that directory synchronization has been configured. +This example configures delivery restrictions for the mailbox in the service that's associated with the specified mail user. This example assumes that directory synchronization is configured. ## PARAMETERS @@ -753,7 +753,7 @@ Accept wildcard characters: False The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: -- $true: Email address policies are applied to this recipient. This is the default value. +- $true: Email address policies are applied to this recipient. This value is the default. - $false: Email address policies aren't applied to this recipient. ```yaml @@ -798,7 +798,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -822,7 +822,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -846,7 +846,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -870,7 +870,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -894,7 +894,7 @@ To enter multiple values that overwrite any existing entries, use the following To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`. -Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value. +Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value. ```yaml Type: MultiValuedProperty @@ -933,7 +933,7 @@ Accept wildcard characters: False The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. -- $false: The recipient is visible in address lists. This is the default value. +- $false: The recipient is visible in address lists. This value is the default. ```yaml Type: Boolean @@ -1077,7 +1077,7 @@ Accept wildcard characters: False The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. -- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. +- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default. You use the ModeratedBy parameter to specify the moderators. @@ -1149,7 +1149,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value. @@ -1181,7 +1181,7 @@ When you enter a number, you can qualify it with one of the following units: - GB (gigabytes) - TB (terabytes) -Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. +Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. The RecoverableItemsWarningQuota value must be less than or equal to the RecoverableItemsQuota value. @@ -1394,7 +1394,7 @@ Accept wildcard characters: False The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are: - $true: The user is required to change their password the next time they log on. -- $false: The user isn't required to change their password the next time they log on. This is the default value. +- $false: The user isn't required to change their password the next time they log on. This value is the default. ```yaml Type: Boolean @@ -1412,7 +1412,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters. ```yaml Type: String @@ -1432,7 +1432,7 @@ Accept wildcard characters: False The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are: -- Always: Notify all senders when their messages aren't approved. This is the default value. +- Always: Notify all senders when their messages aren't approved. This value is the default. - Internal: Notify senders in the organization when their messages aren't approved. - Never: Don't notify anyone when a message isn't approved. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md index 6b3d62ea2d..355d745fa1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md @@ -87,7 +87,7 @@ When you set the email address of the reporting mailbox in the Microsoft Defende Although it's not absolutely required, it makes sense to keep the email address consistent in the related parameters in the \*-ReportSubmissionPolicy and \*-ReportSubmissionRule cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -212,7 +212,7 @@ Accept wildcard characters: False The DisableQuarantineReportingOption parameter allows or prevents users from reporting messages in quarantine. Valid values are: - $true: Users can't report quarantined messages from quarantine. -- $false: Users can report quarantined messages from quarantine. This is the default value. +- $false: Users can report quarantined messages from quarantine. This value is the default. This parameter is meaningful only reporting in Outlook is enabled as described in the EnableReportToMicrosoft parameter. @@ -271,7 +271,7 @@ Accept wildcard characters: False The EnableCustomNotificationSender parameter specifies whether a custom sender email address is used for result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are: - $true: Use a custom Microsoft 365 sender email address. -- $false: Use the default sender email address. This is the default value. +- $false: Use the default sender email address. This value is the default. You specify the sender email address using the NotificationSenderAddress parameter. @@ -623,7 +623,7 @@ Accept wildcard characters: False The PostSubmitMessageEnabled parameter enables or disables the pop-up Outlook notifications that users see after they report messages using Microsoft reporting tools. Valid values are: -- $true: Users receive pop-up notifications in Outlook after they report messages. This is the default value. +- $true: Users receive pop-up notifications in Outlook after they report messages. This value is the default. - $false: Users don't receive pop-up notifications in Outlook after they report messages. ```yaml @@ -796,7 +796,7 @@ Accept wildcard characters: False The PreSubmitMessageEnabled parameter enables or disables the pop-up Outlook notifications that users see before they report messages using Microsoft reporting tools. Valid values are: -- $true: Users receive pop-up notifications in Outlook before they report messages. This is the default value. +- $true: Users receive pop-up notifications in Outlook before they report messages. This value is the default. - $false: Users don't receive pop-up notifications in Outlook before they report messages. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md index 68ff5bd5f9..16493b60d8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md @@ -42,7 +42,7 @@ If you set the email address of the reporting mailbox in the Microsoft Defender When you use this cmdlet to set the email address of the reporting mailbox, the corresponding parameters in the *\-ReportSubmissionPolicy cmdlets are not updated. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md index 2dd5ae09c4..5c934191af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md @@ -13,7 +13,7 @@ title: Set-ResourceConfig # Set-ResourceConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ResourceConfig cmdlet to create custom resource properties that you can add to room and equipment mailboxes. @@ -32,7 +32,7 @@ Set-ResourceConfig [-Confirm] ## DESCRIPTION After you use this cmdlet to create custom resource properties, you use the ResourceCustom parameter on the Set-Mailbox cmdlet to add one or more of those properties to a room or equipment mailbox. For more information, see the ResourceCustom parameter description in Set-Mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md index 1f7c69fdab..ac27df96d6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md @@ -30,7 +30,7 @@ Set-ResubmitRequest [-Identity] -Enabled Applicable: Security & Compliance -The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: +The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. This parameter doesn't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include: - IPM.Note.Microsoft.Conversation - IPM.Note.Microsoft.Conversation.Voice @@ -241,7 +241,7 @@ The ExcludedItemClasses parameter specifies the types of messages to exclude fro - IPM.Note.Microsoft.Voicemail.UM - IPM.Note.Microsoft.Voicemail.UM.CA -Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. Note that the values you specify aren't validated, so the parameter accepts any text value. +Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. The values you specify aren't validated, so the parameter accepts any text value. You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`. @@ -373,7 +373,7 @@ The RetentionDurationDisplayHint parameter specifies the units that are used to - Months - Years -For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration. +For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration. You can't use this parameter for Teams retention rules. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md index 161fa3536c..be27958761 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md @@ -13,7 +13,7 @@ title: Set-RetentionPolicy # Set-RetentionPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-RetentionPolicy cmdlet to change the properties of an existing retention policy. @@ -36,7 +36,7 @@ Set-RetentionPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -138,14 +138,14 @@ This parameter is available only in the cloud-based service. The IsDefault switch specifies that this retention policy is the default retention policy. You don't need to specify a value with this switch. -When you use this switch, you'll get a warning that this retention policy will replace the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy. +When you use this switch, you get a warning that this retention policy replaces the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy. **Note**: Changing which retention policy is the default might or might not affect new and existing mailboxes based on the value of the RetentionPolicy parameter on all mailbox plans: - $null (blank): Changes to which retention policy is the default are continually reflected in new and existing mailboxes. - A retention policy is specified: The value of the RetentionPolicy parameter for all mailbox plans should be $null (blank) or match the Exchange retention policy that's configured as the default policy for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. For more information see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans). -If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value. +If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox is overwritten when changing licenses. You need to manually reset the RetentionPolicy to the original value. Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md index 5ded99737c..cb2e87b762 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md @@ -13,7 +13,7 @@ title: Set-RetentionPolicyTag # Set-RetentionPolicyTag ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-RetentionPolicyTag cmdlet to modify the properties of a retention tag. @@ -71,13 +71,13 @@ Set-RetentionPolicyTag -Mailbox ## DESCRIPTION Retention tags are used to apply message retention settings to folders and items in a mailbox. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES ### Example 1 ```powershell -Set-RetentionPolicyTag "AllUsers-DeletedItems" -Comment "Items in the Deleted Items folder will be automatically deleted in 120 days" +Set-RetentionPolicyTag "AllUsers-DeletedItems" -Comment "Items in the Deleted Items folder are automatically deleted in 120 days" ``` This example changes the comment for the AllUsers-DeletedItems retention policy tag. @@ -458,7 +458,7 @@ The RetentionAction parameter specifies the action for the retention policy. Val - DeleteAndAllowRecovery: Deletes a message and allows recovery from the Recoverable Items folder. - MarkAsPastRetentionLimit: Messages are marked as past the retention limit. - MoveToArchive: Moves a message to the user's archive mailbox. You can use this action for retention tags of type All, Personal, and RecoverableItems. -- PermanentlyDelete: Permanently deletes a message. A message that has been permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox. +- PermanentlyDelete: Permanently deletes a message. A message that is permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox. The MoveToDeletedItems and MoveToFolder actions are available, but don't work. These actions are available for upgrades from messaging records management (MRM) 1.0 (managed folders) to MRM 2.0 (retention policies). MRM 2.0 was introduced in Exchange 2010 Service Pack 1 (SP1). @@ -484,7 +484,7 @@ The RetentionEnabled parameter specifies whether the tag is enabled. When set to Messages with a disabled tag are still considered tagged, so any default policy tags in the user's retention policy aren't applied to such messages. -When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users may apply this tag to items that they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later may result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it may be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_`. +When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users might apply this tag to items that they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later might result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it might be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_`. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md index a21a561bda..c7e9c8a83c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md @@ -13,7 +13,7 @@ title: Set-RoleAssignmentPolicy # Set-RoleAssignmentPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-RoleAssignmentPolicy cmdlet to modify existing management role assignment policies in your organization. @@ -37,7 +37,7 @@ You can use the Set-RoleAssignmentPolicy cmdlet to change the name of an assignm For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md index 8f7420c130..085ea64b34 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md @@ -13,7 +13,7 @@ title: Set-RoleGroup # Set-RoleGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-RoleGroup cmdlet to modify who can add or remove members to or from management role groups or change the name of the role group. @@ -58,7 +58,7 @@ If the ManagedBy property is populated with role group managers, the user config For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md index 51433e0ed4..da642097c4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md @@ -40,7 +40,7 @@ The Set-RoutingGroupConnector cmdlet modifies the properties of an existing rout The Exchange 2003 source servers specified in this cmdlet are automatically added to the ExchangeLegacyInterop universal security group. By default, the Exchange 2010 system grants Send to and Receive from permissions on the Hub Transport servers to members of this group. The source and target servers must be computers that have the Exchange 2010 Hub Transport server role installed, or Exchange 2003 bridgehead servers. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md index e421b16986..0a9bafb950 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md @@ -38,7 +38,7 @@ Outlook 2007 isn't supported in Exchange 2016 or later, so you shouldn't see Out To block Outlook versions for specific mailboxes, use the Set-CASMailbox cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -99,7 +99,7 @@ You can specify ranges. For example, -13.32767.65535, 14.0.0-14.32767.65535, or You can specify multiple individual values or range values separated by semicolons (;). -Be careful when you restrict client access, because Exchange server components might also use RPC to log on. Some components may report their client version as a text string, while others may report the Exchange build number. Monitor the RPC Client Access log to see the client versions that are connecting to your Exchange server before you block any client versions. +Be careful when you restrict client access, because Exchange server components might also use RPC to log on. Some components might report their client version as a text string, while others might report the Exchange build number. Monitor the RPC Client Access log to see the client versions that are connecting to your Exchange server before you block any client versions. ```yaml Type: String @@ -158,7 +158,7 @@ Accept wildcard characters: False The EncryptionRequired parameter specifies whether encryption is required for RPC client connections. Valid values are: -- $true: Unencrypted RPC client connections are rejected. This is the default value. +- $true: Unencrypted RPC client connections are rejected. This value is the default. - $false: Unencrypted RPC client connections are allowed. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md index 8ad4ecd46d..a68c77dc14 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md @@ -39,7 +39,7 @@ Safe Attachments is a feature in Microsoft Defender for Office 365 that opens em A safe attachment policy can be assigned to only one safe attachment rule by using the SafeAttachmentPolicy parameter on the New-SafeAttachmentRule or Set-SafeAttachmentRule cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -83,7 +83,7 @@ Accept wildcard characters: False The Action parameter specifies the action for the safe attachment policy. Valid values are: - Allow: Deliver the message if malware is detected in the attachment and track scanning results. This value corresponds to **Monitor** for the **Safe Attachments unknown malware response** property of the policy in the Microsoft Defender portal. -- Block: Block the email message that contains the malware attachment. This is the default value. +- Block: Block the email message that contains the malware attachment. This value is the default. - DynamicDelivery: Deliver the email message with a placeholder for each email attachment. The placeholder remains until a copy of the attachment is scanned and determined to be safe. For more information, see [Dynamic Delivery in Safe Attachments policies](https://learn.microsoft.com/defender-office-365/safe-attachments-about#dynamic-delivery-in-safe-attachments-policies). The value of this parameter is meaningful only when the value of the Enable parameter is $true (the default value is $false). @@ -150,7 +150,7 @@ Accept wildcard characters: False The Enable parameter works with the Action parameter to specify the action for the safe attachment policy. Valid values are: - $true: The Action parameter specifies the action for the safe attachment policy. -- $false: This is the default value. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. $false corresponds to the value **Off** for the **Safe Attachments unknown malware response** setting of the complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell). +- $false: This value is the default. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. $false corresponds to the value **Off** for the **Safe Attachments unknown malware response** setting of the complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell). To enable or disable an existing Safe Attachments policy, use the Enable-SafeAttachmentRule or Disable-SafeAttachmentRule cmdlets. @@ -201,7 +201,7 @@ Accept wildcard characters: False The Redirect parameter specifies whether to deliver messages to an alternate email address if malware is detected in an attachment. Valid values are: - $true: Messages that contain malware attachments are delivered to the email address specified by the RedirectAddress parameter. This value is meaningful only when the value of the Action parameter is Allow. -- $false: Messages that contain malware attachments aren't delivered to another email address. This is the default value. +- $false: Messages that contain malware attachments aren't delivered to another email address. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md index 20758a7322..593ee7140c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md @@ -46,7 +46,7 @@ A safe attachment policy can be assigned only to one safe attachment rule. > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Safe Attachments policy settings](https://learn.microsoft.com/defender-office-365/safe-attachments-about#safe-attachments-policy-settings). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md index da0d2e61a6..828b4ef04b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md @@ -45,7 +45,7 @@ Set-SafeLinksPolicy [-Identity] ## DESCRIPTION Safe Links is a feature in Microsoft Defender for Office 365 that checks links to see if they lead to malicious web sites. When a user clicks a link, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -166,7 +166,7 @@ Accept wildcard characters: False The DeliverMessageAfterScan parameter specifies whether to deliver email messages only after Safe Links scanning is complete. Valid values are: -- $true: Wait until Safe Links scanning is complete before delivering the message. This is the default value. Messages that contain malicious links are not delivered. +- $true: Wait until Safe Links scanning is complete before delivering the message. This value is the default. Messages that contain malicious links are not delivered. - $false: If Safe Links scanning can't complete, deliver the message anyway. ```yaml @@ -232,7 +232,7 @@ Accept wildcard characters: False The EnableForInternalSenders parameter specifies whether the Safe Links policy is applied to messages sent between internal senders and internal recipients within the same Exchange Online organization. Valid values are: -- $true: The policy is applied to internal and external senders. This is the default value. +- $true: The policy is applied to internal and external senders. This value is the default. - $false: The policy is applied only to external senders. ```yaml @@ -254,7 +254,7 @@ Accept wildcard characters: False The EnableOrganizationBranding parameter specifies whether your organization's logo is displayed on Safe Links warning and notification pages. Valid values are: - $true: Organization branding is displayed on Safe Links warning and notification pages. Before you configure this value, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your company logo. -- $false: Organization branding is not displayed on Safe Links warning and notification pages. This is the default value. +- $false: Organization branding is not displayed on Safe Links warning and notification pages. This value is the default. ```yaml Type: Boolean @@ -274,7 +274,7 @@ Accept wildcard characters: False The EnableSafeLinksForEmail parameter specifies whether to enable Safe Links protection for email messages. Valid values are: -- $true: Safe Links is enabled for email. This is the default value. When a user clicks a link in an email, the link will be checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links is enabled for email. This value is the default. When a user clicks a link in an email, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for email. ```yaml @@ -295,10 +295,10 @@ Accept wildcard characters: False The EnableSafeLinksForOffice parameter specifies whether to enable Safe Links protection for supported Office desktop, mobile, or web apps. Valid values are: -- $true: Safe Links scanning is enabled in Office apps. This is the default value. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links scanning is enabled in Office apps. This value is the default. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for Office apps. -Note that this protection applies to links in Office documents, not links in email messages. +This protection applies to links in Office documents, not links in email messages. ```yaml Type: Boolean @@ -318,7 +318,7 @@ Accept wildcard characters: False The EnableSafeLinksForTeams parameter specifies whether Safe Links is enabled for Microsoft Teams. Valid values are: -- $true: Safe Links is enabled for Teams. This is the default value. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. +- $true: Safe Links is enabled for Teams. This value is the default. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. - $false: Safe Links isn't enabled for Teams. ```yaml @@ -339,7 +339,7 @@ Accept wildcard characters: False The ScanUrls parameter specifies whether to enable or disable real-time scanning of clicked links in email messages. Valid values are: -- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This is the default value. +- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This value is the default. - $false: Real-time scanning of clicked links, including links that point to files, is disabled. ```yaml @@ -360,7 +360,7 @@ Accept wildcard characters: False The TrackClicks parameter specifies whether to track user clicks related to Safe Links protection of links. Valid values are: -- $true: User clicks are tracked. This is the default value. +- $true: User clicks are tracked. This value is the default. - $false: User clicks aren't tracked. ```yaml @@ -382,7 +382,7 @@ Accept wildcard characters: False The UseTranslatedNotificationText specifies whether to use Microsoft Translator to automatically localize the custom notification text that you specified with the CustomNotificationText parameter. Valid values are: - $true: Translate custom notification text to the user's language. -- $false: Don't translate custom notification text to the user's language. This is the default value. +- $false: Don't translate custom notification text to the user's language. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md index 44a150694c..99b959c1d1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md @@ -44,7 +44,7 @@ Safe Links is a feature in Microsoft Defender for Office 365 that checks links i > [!IMPORTANT] > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Recipient filters in Safe Links policies](https://learn.microsoft.com/defender-office-365/safe-links-about#recipient-filters-in-safe-links-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md index 66cb53e178..71bbfc94b9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md @@ -34,7 +34,7 @@ Set-SearchDocumentFormat [-Identity] -Enabled ## DESCRIPTION Exchange Search includes built-in support for indexing many file formats. If you disable indexing for a supported file format, items containing an attachment of that file type aren't considered unsearchable. When you perform an [In-Place eDiscovery search in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and you select the option to include unsearchable items, only items that are actually unsearchable are returned. Items that weren't searched because the associated file format is set as unsearchable aren't returned. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES