From 2ca45d5529b435bf0ae7b31d49e66eab3c670b3b Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Wed, 6 Aug 2025 09:49:09 -0700 Subject: [PATCH] Acrolinx 12 --- .../Remove-OutboundConnector.md | 2 +- .../Remove-OutlookProtectionRule.md | 4 +-- .../Remove-OutlookProvider.md | 2 +- .../Remove-OwaMailboxPolicy.md | 6 ++-- .../Remove-OwaVirtualDirectory.md | 2 +- .../Remove-PartnerApplication.md | 4 +-- .../Remove-PhishSimOverridePolicy.md | 2 +- .../Remove-PolicyTipConfig.md | 4 +-- .../Remove-PowerShellVirtualDirectory.md | 4 +-- .../ExchangePowerShell/Remove-PublicFolder.md | 4 +-- ...ve-PublicFolderAdministrativePermission.md | 2 +- .../Remove-PublicFolderClientPermission.md | 4 +-- .../Remove-PublicFolderDatabase.md | 2 +- ...ove-PublicFolderMailboxMigrationRequest.md | 4 +-- .../Remove-PublicFolderMigrationRequest.md | 2 +- .../Remove-PublicFolderMoveRequest.md | 6 ++-- .../Remove-QuarantinePolicy.md | 2 +- .../Remove-ReceiveConnector.md | 2 +- .../Remove-RecipientPermission.md | 2 +- .../ExchangePowerShell/Remove-RemoteDomain.md | 4 +-- .../Remove-RemoteMailbox.md | 4 +-- .../Remove-ReportSubmissionPolicy.md | 2 +- .../Remove-ReportSubmissionRule.md | 2 +- .../Remove-ResubmitRequest.md | 2 +- .../Remove-RetentionPolicy.md | 6 ++-- .../Remove-RetentionPolicyTag.md | 6 ++-- .../Remove-RoleAssignmentPolicy.md | 4 +-- .../ExchangePowerShell/Remove-RoleGroup.md | 6 ++-- .../Remove-RoleGroupMember.md | 6 ++-- .../Remove-RoutingGroupConnector.md | 2 +- .../Remove-RpcClientAccess.md | 4 +-- .../Remove-SafeAttachmentPolicy.md | 2 +- .../Remove-SafeAttachmentRule.md | 2 +- .../Remove-SafeLinksPolicy.md | 2 +- .../Remove-SafeLinksRule.md | 2 +- .../Remove-SearchDocumentFormat.md | 6 ++-- .../Remove-SecOpsOverridePolicy.md | 2 +- .../Remove-SendConnector.md | 4 +-- .../Remove-ServerMonitoringOverride.md | 4 +-- .../Remove-ServicePrincipal.md | 2 +- .../Remove-SettingOverride.md | 2 +- .../Remove-SharingPolicy.md | 4 +-- .../Remove-SiteMailboxProvisioningPolicy.md | 2 +- .../ExchangePowerShell/Remove-StoreMailbox.md | 2 +- .../ExchangePowerShell/Remove-SweepRule.md | 4 +-- .../Remove-SyncMailPublicFolder.md | 4 +-- .../Remove-SystemMessage.md | 2 +- .../Remove-TenantAllowBlockListItems.md | 4 +-- .../Remove-TenantAllowBlockListSpoofItems.md | 2 +- .../Remove-ThrottlingPolicy.md | 2 +- .../Remove-TransportRule.md | 4 +-- .../Remove-UMAutoAttendant.md | 2 +- .../Remove-UMCallAnsweringRule.md | 4 +-- .../ExchangePowerShell/Remove-UMDialPlan.md | 2 +- .../ExchangePowerShell/Remove-UMHuntGroup.md | 2 +- .../ExchangePowerShell/Remove-UMIPGateway.md | 2 +- .../Remove-UMMailboxPolicy.md | 2 +- .../ExchangePowerShell/Remove-UnifiedGroup.md | 2 +- .../Remove-UnifiedGroupLinks.md | 2 +- .../ExchangePowerShell/Remove-UserPhoto.md | 4 +-- .../Remove-VivaModuleFeaturePolicy.md | 2 +- .../Remove-WebServicesVirtualDirectory.md | 2 +- .../Remove-X400AuthoritativeDomain.md | 2 +- .../Reset-ProvisioningCache.md | 4 +-- .../Restore-DatabaseAvailabilityGroup.md | 2 +- .../Restore-DetailsTemplate.md | 2 +- .../ExchangePowerShell/Restore-Mailbox.md | 8 ++--- .../Restore-RecoverableItems.md | 8 ++--- .../Resume-MailboxDatabaseCopy.md | 2 +- .../Resume-MailboxExportRequest.md | 2 +- .../Resume-MailboxImportRequest.md | 4 +-- .../Resume-MailboxRestoreRequest.md | 4 +-- .../ExchangePowerShell/Resume-Message.md | 4 +-- .../ExchangePowerShell/Resume-MoveRequest.md | 6 ++-- .../Resume-PublicFolderMigrationRequest.md | 2 +- .../Resume-PublicFolderMoveRequest.md | 4 +-- .../Resume-PublicFolderReplication.md | 2 +- .../ExchangePowerShell/Resume-Queue.md | 2 +- .../ExchangePowerShell/Retry-Queue.md | 2 +- .../Rotate-DkimSigningConfig.md | 2 +- .../Search-AdminAuditLog.md | 8 ++--- .../ExchangePowerShell/Search-Mailbox.md | 2 +- .../Search-MailboxAuditLog.md | 6 ++-- .../Search-MessageTrackingReport.md | 4 +-- .../Search-UnifiedAuditLog.md | 12 +++---- .../Send-TextMessagingVerificationCode.md | 4 +-- .../Set-ADServerSettings.md | 2 +- .../ExchangePowerShell/Set-AcceptedDomain.md | 8 ++--- .../Set-AccessToCustomerDataRequest.md | 2 +- .../Set-ActiveSyncDeviceAccessRule.md | 4 +-- .../Set-ActiveSyncDeviceAutoblockThreshold.md | 6 ++-- .../Set-ActiveSyncMailboxPolicy.md | 4 +-- .../Set-ActiveSyncOrganizationSettings.md | 8 ++--- .../Set-ActiveSyncVirtualDirectory.md | 12 +++---- .../Set-AddressBookPolicy.md | 34 ++++++++++++++++--- .../ExchangePowerShell/Set-AddressList.md | 4 +-- .../Set-AdminAuditLogConfig.md | 16 ++++----- 97 files changed, 207 insertions(+), 183 deletions(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md index c2852cf820..9a4192bf4c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md @@ -31,7 +31,7 @@ Remove-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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md index dcfd7ccd4c..9c740ebb31 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md @@ -15,7 +15,7 @@ title: Remove-OutlookProtectionRule ## SYNOPSIS **Note**: This cmdlet is no longer supported in the cloud-based service. -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-OutlookProtectionRule cmdlet to remove Outlook protection rules. @@ -34,7 +34,7 @@ Remove-OutlookProtectionRule [-Identity] ## DESCRIPTION Outlook protection rules use an Active Directory Rights Management Services (AD RMS) rights template to automatically apply Information Rights Management (IRM) protection to messages before they're sent. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md index ca4e1e331e..963f8c71d9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md @@ -32,7 +32,7 @@ Remove-OutlookProvider [-Identity] ## DESCRIPTION The Remove-OutlookProvider cmdlet deletes the AutoDiscoverConfig object under the Global Settings object in Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md index 0bd84f979a..5b620c8bb2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md @@ -13,7 +13,7 @@ title: Remove-OwaMailboxPolicy # Remove-OwaMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-OwaMailboxPolicy cmdlet to remove Outlook on the web mailbox policies from the organization. @@ -31,9 +31,9 @@ Remove-OwaMailboxPolicy [-Identity] ``` ## DESCRIPTION -Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). +Changes to Outlook on the web mailbox policies might take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md index 8eb57c6379..a124400754 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md @@ -37,7 +37,7 @@ You might be required to use the Remove-OwaVirtualDirectory cmdlet in the follow Remove-OwaVirtualDirectory permanently removes an Outlook on the web virtual directory or directories. When you use this cmdlet, make sure that you don't accidentally delete the default Outlook on the web virtual directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md index 1badd61959..936b9caaf0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md @@ -13,7 +13,7 @@ title: Remove-PartnerApplication # Remove-PartnerApplication ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-PartnerApplication cmdlet to remove a partner application configuration. @@ -34,7 +34,7 @@ You can configure partner applications such as Microsoft SharePoint to access Ex We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md index eef6fba7a1..3943fd117f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md @@ -31,7 +31,7 @@ Remove-PhishSimOverridePolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md index e2011f2ab5..d20d920506 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md @@ -13,7 +13,7 @@ title: Remove-PolicyTipConfig # Remove-PolicyTipConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-PolicyTipConfig cmdlet to remove custom data loss prevention (DLP) Policy Tips from your organization. You can't remove built-in Policy Tips. @@ -30,7 +30,7 @@ Remove-PolicyTipConfig [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md index 2174fd682c..72abe8d4c1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md @@ -32,7 +32,7 @@ Remove-PowerShellVirtualDirectory [-Identity] ## DESCRIPTION Although it's possible to remove a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -43,7 +43,7 @@ Remove-PowerShellVirtualDirectory "Internal (Default Web Site)" -Confirm:$False This example removes a Windows PowerShell virtual directory without confirmation. -Be careful when using the Remove-PowerShellVirtualDirectory cmdlet without confirmation. You won't be prompted before the virtual directory is deleted. +Be careful when using the Remove-PowerShellVirtualDirectory cmdlet without confirmation. You aren't prompted before the virtual directory is deleted. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md index c1eeb1b2cd..d3d0cdf444 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md @@ -13,7 +13,7 @@ title: Remove-PublicFolder # Remove-PublicFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-PublicFolder cmdlet to remove an existing public folder. @@ -35,7 +35,7 @@ Remove-PublicFolder [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md index 23f93a12d8..8a8bf774bd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md @@ -48,7 +48,7 @@ Remove-PublicFolderAdministrativePermission [[-Identity] -Acces ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md index bdd0ea1ad5..8f6803762a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md @@ -31,7 +31,7 @@ Remove-PublicFolderDatabase [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). Removing a public folder database can have a broad range of serious consequences. (This is particularly true when removing the last public folder database in the organization.) For more information, see [Remove Public Folder Databases](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd876883(v=exchg.141)). diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md index 72b59a29e3..0667881178 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md @@ -13,7 +13,7 @@ title: Remove-PublicFolderMailboxMigrationRequest # Remove-PublicFolderMailboxMigrationRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-PublicFolderMailboxMigrationRequest cmdlet to remove individual jobs from public folder migration batches that were created by using the New-MigrationBatch cmdlet. @@ -41,7 +41,7 @@ Remove-PublicFolderMailboxMigrationRequest -RequestGuid -RequestQueue -RequestQueue -RequestQueue ## DESCRIPTION You can't remove the built-in quarantine policies named AdminOnlyAccessPolicy or DefaultFullAccessPolicy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md index 1bacd5e932..f8720a5197 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md @@ -32,7 +32,7 @@ Remove-ReceiveConnector [-Identity] ## DESCRIPTION Removing a Receive connector from the server might affect mail flow throughout the organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md index 5532764950..ac050e0a57 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md @@ -36,7 +36,7 @@ Remove-RecipientPermission [-Identity] -AccessRights ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md index 8b72bc15ab..fd6ab9e40a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md @@ -36,7 +36,7 @@ With the Remove-RemoteMailbox cmdlet, you can remove an on-premises mail-enabled Directory synchronization must be configured correctly for a mailbox to be removed from the service. Removal of the mailbox from the service isn't immediate and depends on the directory synchronization schedule. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -45,7 +45,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Remove-RemoteMailbox "Kim Akers" ``` -This example removes the on-premises mail-enabled user Kim Akers and the associated mailbox from the service. This example assumes directory synchronization has been configured. +This example removes the on-premises mail-enabled user Kim Akers and the associated mailbox from the service. This example assumes directory synchronization is configured. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md index 68777847fb..37601a5812 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md @@ -28,7 +28,7 @@ Remove-ReportSubmissionPolicy [-Identity] [< ## DESCRIPTION There's only one report submission policy in an organization, and it's named DefaultReportSubmissionPolicy. You can remove the policy and then use the New-ReportSubmissionPolicy cmdlet to recreate it with the default settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md index fabd608925..40faf43a7b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md @@ -31,7 +31,7 @@ Remove-ReportSubmissionRule [-Identity] ## DESCRIPTION To disable the report submission rule without deleting it, use the Disable-ReportSubmissionRule cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md index 73733485fe..c85c142160 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md @@ -30,7 +30,7 @@ Remove-ResubmitRequest [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md index c8d5021c8d..0475a58a8f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md @@ -13,7 +13,7 @@ title: Remove-RetentionPolicy # Remove-RetentionPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-RetentionPolicy cmdlet to remove a retention policy. @@ -33,9 +33,9 @@ Remove-RetentionPolicy [-Identity] ## DESCRIPTION Retention policies are used to apply message retention settings to folders and items in a mailbox. The Remove-RetentionPolicy cmdlet removes an existing retention policy. -If you remove a retention policy that's assigned to users and they don't have another retention policy assigned, messages in those mailboxes may never expire. This may be a violation of the organization's messaging retention policies. When you attempt to remove a policy that's assigned to users, Microsoft Exchange displays a confirmation message indicating that the policy is assigned to users. Note that this message is in addition to the confirmation prompt displayed when removing a retention policy. +If you remove a retention policy that's assigned to users and they don't have another retention policy assigned, messages in those mailboxes might never expire. This might be a violation of the organization's messaging retention policies. When you attempt to remove a policy that's assigned to users, Microsoft Exchange displays a confirmation message indicating that the policy is assigned to users. This message is in addition to the confirmation prompt displayed when removing a retention policy. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md index 782489d23e..d8d0bfdde8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md @@ -13,7 +13,7 @@ title: Remove-RetentionPolicyTag # Remove-RetentionPolicyTag ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-RetentionPolicyTag cmdlet to remove a retention tag. @@ -32,11 +32,11 @@ Remove-RetentionPolicyTag [-Identity] ## DESCRIPTION Retention tags are added to a retention policy, which is applied to a mailbox. -When you use the Remove-RetentionPolicyTag cmdlet to remove a retention tag, it removes the tag definition stored in Active Directory. The next time the Managed Folder Assistant runs, it processes all items that have the removed tag applied and restamps them. Depending on the number of mailboxes and messages, this process may result in significant resource consumption on all Mailbox servers that contain mailboxes with a retention policy that includes the removed tag. +When you use the Remove-RetentionPolicyTag cmdlet to remove a retention tag, it removes the tag definition stored in Active Directory. The next time the Managed Folder Assistant runs, it processes all items that have the removed tag applied and restamps them. Depending on the number of mailboxes and messages, this process might result in significant resource consumption on all Mailbox servers that contain mailboxes with a retention policy that includes the removed tag. For more information about retention tags, see [Retention tags and retention policies in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mrm/retention-tags-and-retention-policies). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md index 20586d4cb2..5b564b0d0d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md @@ -13,7 +13,7 @@ title: Remove-RoleAssignmentPolicy # Remove-RoleAssignmentPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-RoleAssignmentPolicy cmdlet to remove existing management role assignment policies from your organization. @@ -38,7 +38,7 @@ The assignment policy you want to remove can't be assigned to any mailboxes or m For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md index f23147c627..8823aa5d8b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md @@ -13,7 +13,7 @@ title: Remove-RoleGroup # Remove-RoleGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-RoleGroup cmdlet to remove a management role group. @@ -36,11 +36,11 @@ When you remove a role group, all the management role assignments assigned manag You can't remove built-in role groups. -If the ManagedBy property has been populated with role group managers, the user removing the role group must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. +If the ManagedBy property is populated with role group managers, the user removing the role group must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check. For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md index 7abb07e98f..a7c39c03c7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md @@ -13,7 +13,7 @@ title: Remove-RoleGroupMember # Remove-RoleGroupMember ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-RoleGroupMember cmdlet to remove a member of a management role group. @@ -33,13 +33,13 @@ Remove-RoleGroupMember [-Identity] -Member ``` ## DESCRIPTION -Disabling RPC client access on a server blocks all RPC access through the specified Client Access server. Therefore, RPC clients (for example, clients running Microsoft Office Outlook 2007) with mailboxes on any mailbox databases configured to use the specified Client Access server won't be able to connect. +Disabling RPC client access on a server blocks all RPC access through the specified Client Access server. Therefore, RPC clients (for example, clients running Microsoft Office Outlook 2007) with mailboxes on any mailbox databases configured to use the specified Client Access server can't connect. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md index d79cf3b777..97148431b9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md @@ -32,7 +32,7 @@ Remove-SafeAttachmentPolicy [-Identity] ## DESCRIPTION Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md index 74fae37eb9..28b2b0c067 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md @@ -31,7 +31,7 @@ Remove-SafeAttachmentRule [-Identity] ## DESCRIPTION Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md index e4fcd71186..40c1b76e66 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md @@ -34,7 +34,7 @@ You can't remove the default Safe Links policy (the policy where the IsDefault p Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md index a8c412145f..3fd4cb00d9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md @@ -31,7 +31,7 @@ Remove-SafeLinksRule [-Identity] ## DESCRIPTION Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md index fd539a83c6..f0db065269 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md @@ -30,9 +30,11 @@ Remove-SearchDocumentFormat [-Identity] ``` ## DESCRIPTION -After running the Remove-SearchDocumentFormat cmdlet, your must run the following cmdlet to restart the search service. There will be a brief search outage. +After running the Remove-SearchDocumentFormat cmdlet, you must run the following cmdlet to restart the search service. There will be a brief search outage. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +`Restart-Service HostControllerService` + +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md index 878683aaa8..a8094fee23 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md @@ -31,7 +31,7 @@ Remove-SecOpsOverridePolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md index ef7ec0522d..731a453bec 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md @@ -32,9 +32,9 @@ Remove-SendConnector [-Identity] ## DESCRIPTION The Remove-SendConnector cmdlet deletes the object and the configuration settings for the Send connector. -Although a Send connector is configured locally in the Transport service on a Mailbox server or on an Edge server, deleting a Send connector may affect mail flow throughout the organization. +Although a Send connector is configured locally in the Transport service on a Mailbox server or on an Edge server, deleting a Send connector might affect mail flow throughout the organization. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md index 8797d26742..d4d2e18a65 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md @@ -15,7 +15,7 @@ title: Remove-ServerMonitoringOverride ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Remove-ServerMonitoringOverride cmdlet to remove a managed availability local server override that has been configured for a probe, monitor or responder. +Use the Remove-ServerMonitoringOverride cmdlet to remove a managed availability local server override that is configured for a probe, monitor or responder. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -29,7 +29,7 @@ Remove-ServerMonitoringOverride [-Identity] -ItemType ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md index f1f2727920..be10212190 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md @@ -34,7 +34,7 @@ Remove-SettingOverride [-Identity] ## DESCRIPTION Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and they're lost when you install the next Exchange CU. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md index 2422bc4285..719d9621a8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md @@ -13,7 +13,7 @@ title: Remove-SharingPolicy # Remove-SharingPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-SharingPolicy cmdlet to remove a sharing policy. Before you can remove a sharing policy, you must ensure that no mailbox users are provisioned to use that policy. @@ -30,7 +30,7 @@ Remove-SharingPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md index f896036b30..78406d422b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md @@ -34,7 +34,7 @@ Remove-SiteMailboxProvisioningPolicy [-Identity] ## DESCRIPTION You can't delete the default site mailbox provisioning policy. You need to create a new default policy by using the New-SiteMailboxProvisioningPolicy cmdlet or designate an existing policy as the default policy by using the Set-SiteMailboxProvisioningPolicy cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md index eced30b9b1..7f22253212 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md @@ -37,7 +37,7 @@ A mailbox is marked as Disabled immediately after the Disable-Mailbox or Remove- To view disabled mailboxes, run the Get-MailboxStatistics cmdlet against a database using the property DisconnectReason with a value of Disabled. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md index 35879232b1..3815b75020 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md @@ -13,7 +13,7 @@ title: Remove-SweepRule # Remove-SweepRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Remove-SweepRule cmdlet to remove Sweep rules from mailboxes. @@ -31,7 +31,7 @@ Remove-SweepRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md index 76b893ba88..5b7c3b265b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md @@ -13,7 +13,7 @@ title: Remove-SyncMailPublicFolder # Remove-SyncMailPublicFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. The Remove-SyncMailPublicFolder cmdlet is used by the Sync-MailPublicFolders.ps1 script to remove mail-enabled public folder recipient objects from Exchange Online (the script synchronizes mail-enabled public folder objects from the source on-premises Exchange organization to Exchange Online). Don't use this cmdlet unless you are directed to do so by Microsoft Customer Service and Support or by specific documentation. @@ -32,7 +32,7 @@ Remove-SyncMailPublicFolder [-Identity] ## DESCRIPTION This cmdlet is only used by the Sync-MailPublicFolders.ps1 script. Don't run this cmdlet in the Exchange Management Shell or in Exchange Online PowerShell. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md index 0ee365aefb..159bf7e9fa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md @@ -32,7 +32,7 @@ Remove-SystemMessage [-Identity] ## DESCRIPTION You can't remove a default system message that's included with Exchange. When you remove a custom system message, the message text reverts to the text in the corresponding system message (if any) that's included with Exchange. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md index 7bf6419833..98cf2e12da 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md @@ -38,7 +38,7 @@ Remove-TenantAllowBlockListItems -Ids -ListType ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -139,7 +139,7 @@ Accept wildcard characters: False The ListSubType specifies further specifies the type of entry that you want to remove. Valid values are: - AdvancedDelivery: Use this value for phishing simulation URLs. -- Tenant: This is the default value. +- Tenant: This value is the default. ```yaml Type: ListSubType diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md index be8e893e78..8e2392eaba 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md @@ -31,7 +31,7 @@ Remove-TenantAllowBlockListSpoofItems [-Identity] ``` ## DESCRIPTION -The Remove-UMCallAnsweringRule cmdlet removes an existing UM call answering rule that has been created and stored in a UM-enabled user's mailbox. When you remove an existing call answering rule, all of the remaining call answering rules are still processed in order of their priority. +The Remove-UMCallAnsweringRule cmdlet removes an existing UM call answering rule that is created and stored in a UM-enabled user's mailbox. When you remove an existing call answering rule, all of the remaining call answering rules are still processed in order of their priority. After this task is completed, the cmdlet sets the parameters and the values specified. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md index 9891da4d6d..8f422da9ef 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md @@ -34,7 +34,7 @@ The Remove-UMDialPlan cmdlet deletes an existing UM dial plan from Active Direct After this task is completed, the UM dial plan is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md index 5a6e163d62..6966e94209 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md @@ -34,7 +34,7 @@ The Remove-UMHuntGroup cmdlet deletes an existing UM hunt group from Active Dire After this task is completed, the UM hunt group is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md index f0bb270293..2eb54404fe 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md @@ -36,7 +36,7 @@ The Remove-UMIPGateway cmdlet should be run only by an administrator who fully u After this task is completed, the UM IP gateway is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md index 6e1dbd4616..47622239c9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md @@ -34,7 +34,7 @@ The Remove-UMMailboxPolicy cmdlet deletes or removes a UM mailbox policy. If the After this task is completed, the UM mailbox policy is removed from Active Directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md index cbccda7b2c..28b72dc892 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md @@ -34,7 +34,7 @@ Remove-UnifiedGroup [-Identity] ## DESCRIPTION Microsoft 365 Groups are group objects that are available across Microsoft 365 services. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md index afdf8598ab..494ea656fd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md @@ -34,7 +34,7 @@ Remove-UnifiedGroupLinks [-Identity] -Links Use the Remove-UserPhoto cmdlet to delete the user photo currently associated with a user's account. This cmdlet removes the photo from user's Exchange mailbox root. In on-premises Exchange, it also removes the user's photo from their Active Directory account. Administrators can also use the Exchange admin center (EAC) to delete user photos by accessing the Options page in the user's mailbox in Outlook on the web. -**Notes**: Changes to the user photo won't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image. +**Notes**: Changes to the user photo don't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md index fd0cb8ce9c..fe576b5f2d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md @@ -15,7 +15,7 @@ title: Remove-VivaModuleFeaturePolicy ## SYNOPSIS This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). -Use the Remove-VivaModuleFeaturePolicy cmdlet to delete an access policy for a feature in a Viva module in Viva. Once you delete a policy, the policy is permanently deleted. You cannot undo the deletion. +Use the Remove-VivaModuleFeaturePolicy cmdlet to delete an access policy for a feature in a Viva module in Viva. Once you delete a policy, the policy is permanently deleted. You can't undo the deletion. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md index 4a2b358ce1..146c97aa5f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md @@ -33,7 +33,7 @@ Remove-WebServicesVirtualDirectory [-Identity] ## DESCRIPTION You can remove the default Exchange Web Services virtual directory or another Exchange Web Services virtual directory. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md index 4e966c4f48..d15a9671e2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md @@ -30,7 +30,7 @@ Remove-X400AuthoritativeDomain [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md index 6eda0f1f75..304b16a5f9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md +++ b/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md @@ -47,7 +47,7 @@ The Reset-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely The Reset-ProvisioningCache cmdlet clears the Windows PowerShell provisioning cache of frequently used Active Directory objects. To reduce Active Directory requests, a provisioning cache is initialized in each Windows PowerShell runspace and is used to cache common objects that are frequently used by cmdlets and provisioning handlers. During Exchange cmdlet execution, the provisioning cache loads configuration objects from Active Directory to help run a cmdlet. For example, when you create a mailbox, the New-Mailbox cmdlet obtains properties from Active Directory. When running cmdlets, configuration objects such as database containers, administrative role groups, and LegacyDNs are retrieved from Active Directory. Because these types of objects are stable and don't change for months or years after they're created, they're stored in the provisioning cache used by Windows PowerShell. This increases provisioning efficiency and significantly improves cmdlet performance. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -191,7 +191,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Organizations parameter specifies the organizations that the provisioning cache will be reset. This parameter is used in multi-tenant deployments. +The Organizations parameter specifies the organizations where the provisioning cache is reset. Use this parameter in multi-tenant deployments. ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md index ae01926758..d57df551a4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md @@ -45,7 +45,7 @@ The Restore-DatabaseAvailabilityGroup cmdlet performs several operations that af - Forcibly evicts the servers listed on the StoppedMailboxServers list from the DAG's cluster, thereby reestablishing quorum for the cluster enabling the surviving DAG members to start and provide service. - Configures the DAG to use the alternate witness server if there is an even number of surviving DAG members, or a single surviving DAG member. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md index bfb2fae14f..c535b125f8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md @@ -32,7 +32,7 @@ Restore-DetailsTemplate [-Identity] ## DESCRIPTION Details templates can't be created or deleted, but this task restores the specified template to its default state. All user changes are lost. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md index acdecb4511..88fdd90071 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md @@ -49,7 +49,7 @@ Restore-Mailbox [-Identity] -RecoveryDatabase Applicable: Exchange Server 2010 -The EndDate parameter specifies the end date for filtering content that will be exported from the source mailbox. Only items in the mailbox whose date is prior to the end date are exported. When you enter a specific date, use the short date format defined in the Regional Options settings configured on the local computer. For example, if your computer is configured to use the short date format MM/dd/yyyy, enter 03/01/2010 to specify March 1, 2010. +The EndDate parameter specifies the end date for filtering content to be exported from the source mailbox. Only items in the mailbox whose date is prior to the end date are exported. When you enter a specific date, use the short date format defined in the Regional Options settings configured on the local computer. For example, if your computer is configured to use the short date format MM/dd/yyyy, enter 03/01/2010 to specify March 1, 2010. ```yaml Type: DateTime @@ -475,9 +475,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The ValidateOnly switch tells the command to evaluate the conditions and requirements necessary to perform the operation, and then report whether the operation will succeed or fail. You don't need to specify a value with this switch. - -No changes are made when you use this switch. +The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md b/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md index cd4e7247c4..7dfbf5787e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md @@ -13,7 +13,7 @@ title: Restore-RecoverableItems # Restore-RecoverableItems ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Restore-RecoverableItems items cmdlet to restore deleted items in mailboxes. You use the Get-RecoverableItems cmdlet to find the deleted items to recover. @@ -58,7 +58,7 @@ Restore-RecoverableItems -Identity ## DESCRIPTION Items are restored to the original folder location if the information is available for the item. If the information can't be found, the item is restored to the default folder for the item type (Inbox for messages, Calendar for meetings and appointments, etc.). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -322,7 +322,7 @@ This parameter is available only in the cloud-based service. The RestoreTargetFolder parameter specifies the top-level folder in which to restore data. If you don't specify this parameter, the command restores folders to the top of the folder structure in the target mailbox or archive. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure. -This parameter is available only on primary mailboxes and is ignored on archive mailboxes. A destination folder will be created if it does not exist. Valid paths are: +This parameter is available only on primary mailboxes and is ignored on archive mailboxes. A destination folder is created if it does not exist. Valid paths are: - `/` - `/folder1` @@ -330,7 +330,7 @@ This parameter is available only on primary mailboxes and is ignored on archive - `folder1` - `folder1/folder2` -The preceding or trailing `/` will be ignored. Then, it will be treated as the relative path of the IPM sub-tree: `/Top Of Information Store`. +The preceding or trailing `/` are ignored. Then, it's treated as the relative path of the IPM sub-tree: `/Top Of Information Store`. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md index 1403d54b10..645c002cfe 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md @@ -45,7 +45,7 @@ Resume-MailboxDatabaseCopy [-Identity] ## DESCRIPTION The Resume-MailboxDatabaseCopy cmdlet resumes replication and replay from a suspended state. If a database copy was suspended without administrator intervention, it's because the database copy is in a bad state. You can use the Get-MailboxDatabaseCopyStatus cmdlet to see if there are any messages indicating a failure. If the copy of the database is in a bad state, resuming the copy causes replication to fail and the mailbox database copy to return to a suspended state. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md index e8b277aa9d..9dd5908f7a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md @@ -34,7 +34,7 @@ Resume-MailboxExportRequest [-Identity] ## DESCRIPTION The Resume-MailboxExportRequest cmdlet can be pipelined with the Get-MailboxExportRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md index 298495c2a6..785786b9af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md @@ -13,7 +13,7 @@ title: Resume-MailboxImportRequest # Resume-MailboxImportRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Resume-MailboxImportRequest cmdlet to resume an import request that was suspended or failed. @@ -36,7 +36,7 @@ Resume-MailboxImportRequest [-Identity] ## DESCRIPTION This cmdlet can be pipelined with the Get-MailboxImportRequest cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md index 83322f5be6..fad77ae856 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md @@ -13,7 +13,7 @@ title: Resume-MailboxRestoreRequest # Resume-MailboxRestoreRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Resume-MailboxRestoreRequest cmdlet to resume a restore request that was suspended or failed. @@ -30,7 +30,7 @@ Resume-MailboxRestoreRequest [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md b/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md index 2f95ea5a15..0e3a1e81b7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md @@ -41,7 +41,7 @@ Resume-Message [-Identity] ## DESCRIPTION A message being sent to multiple recipients might be located in multiple queues. If you specify an Identity parameter, the message is resumed in a single queue if that identity matches only a single message. If the identity matches more than one message, you receive an error. To resume a message in more than one queue in a single operation, you must use the Filter parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -54,7 +54,7 @@ This example resumes delivery of all messages in a suspended state and for which - The messages were sent by the sender kweku@contoso.com. - The messages are queued on the server Server1. -- The messages will expire before 15:00 on January 5, 2018. +- The messages expire before 15:00 on January 5, 2018. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md index f03468c869..b1659f57e9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md @@ -13,9 +13,9 @@ title: Resume-MoveRequest # Resume-MoveRequest ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. -Use the Resume-MoveRequest cmdlet to resume a move request that has been suspended or has failed. +Use the Resume-MoveRequest cmdlet to resume a move request that is suspended or has failed. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -32,7 +32,7 @@ Resume-MoveRequest [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md index 0ed306d912..bd11ab1149 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md @@ -32,7 +32,7 @@ Resume-PublicFolderMigrationRequest [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md index fdedc6a3ae..a5ee4bc606 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md @@ -29,7 +29,7 @@ Resume-PublicFolderReplication [-Confirm] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md index 7d18b6c74d..fcd4ceaf1c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md @@ -41,7 +41,7 @@ Resume-Queue [-Identity] ## DESCRIPTION If you use the Identity parameter, the queue is resumed only if that identity matches a single queue. If the identity matches more than one queue, you receive an error. To resume more than one queue in a single operation, you must use the Filter parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md index 42164baa7f..20b8cbb918 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md +++ b/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md @@ -43,7 +43,7 @@ Retry-Queue [-Identity] ## DESCRIPTION The Retry-Queue cmdlet forces a connection attempt for a queue that has a status of Retry. The cmdlet establishes a connection to the next hop if possible. If a connection isn't established, a new retry time is set. To use this command to retry delivery of messages in the Unreachable queue, you must include the Resubmit parameter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md index 894b736a5b..14fd8444d3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md @@ -30,7 +30,7 @@ Rotate-DkimSigningConfig [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md index ead5224ff7..a1fe3fddee 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md @@ -16,7 +16,7 @@ title: Search-AdminAuditLog > [!NOTE] > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Search-AdminAuditLog cmdlet to search the contents of the administrator audit log. Administrator audit logging records when a user or administrator makes a change in your organization (in the Exchange admin center or by using cmdlets). @@ -45,11 +45,11 @@ If you run the Search-AdminAuditLog cmdlet without any parameters, up to 1,000 l In Exchange Online PowerShell, if you don't use the StartDate or EndDate parameters, only results from the last 14 days are returned. -In Exchange Online PowerShell, data is available for the last 90 days. You can enter dates older than 90 days, but only data from the last 90 days will be returned. +In Exchange Online PowerShell, data is available for the last 90 days. You can enter dates older than 90 days, but only data from the last 90 days are returned. For more information about the structure and properties of the audit log, see [Administrator audit log structure](https://learn.microsoft.com/Exchange/policy-and-compliance/admin-audit-logging/log-structure). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -215,7 +215,7 @@ The ObjectIds parameter filters the results by the object that was modified (the - Canonical distinguished name (for example, contoso.com/Users/Akia Al-Zuhairi) - Public folder identity (for example, \\Engineering\\Customer Discussion) -You'll likely need to use other filtering parameters on this cmdlet to narrow down the results and identify the types of objects that you're interested in. In the results of this cmdlet, this property is named **ObjectModified**. +You likely need to use other filtering parameters on this cmdlet to narrow down the results and identify the types of objects that you're interested in. In the results of this cmdlet, this property is named **ObjectModified**. You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md index c2be455ddb..31efc27c8a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md @@ -348,7 +348,7 @@ The LogLevel parameter specifies the logging level for the search. It can have o The default log level is Basic. -When you included this parameter, an email message is created and sent to the mailbox specified by the TargetMailbox parameter. The log file (which is a CSV-formatted file named Search Results.csv) is attached to this email message, and will be located in the folder specified by the TargetFolder parameter. The log file contains a row for each message that's included in the search results when you run the Search-Mailbox cmdlet. +When you included this parameter, an email message is created and sent to the mailbox specified by the TargetMailbox parameter. The log file (which is a CSV-formatted file named Search Results.csv) is attached to this email message, and is located in the folder specified by the TargetFolder parameter. The log file contains a row for each message that's included in the search results when you run the Search-Mailbox cmdlet. ```yaml Type: LoggingLevel diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md index ec79d9383b..8a20ce8c36 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md @@ -16,7 +16,7 @@ title: Search-MailboxAuditLog > [!NOTE] > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: . -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Search-MailboxAuditLog cmdlet to search mailbox audit log entries matching the specified search terms. @@ -62,7 +62,7 @@ The Search-MailboxAuditLog cmdlet performs a synchronous search of mailbox audit In multi-geo environments, when you run this cmdlet in a different region from the mailbox that you're trying to search, you might receive the error, "An error occurred while trying to access the audit log." In this scenario, you need to anchor the PowerShell session to a user in the same region as the mailbox as described in [Connect directly to a geo location using Exchange Online PowerShell](https://learn.microsoft.com/microsoft-365/enterprise/administering-exchange-online-multi-geo#connect-directly-to-a-geo-location-using-exchange-online-powershell). -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -166,7 +166,7 @@ The ExternalAccess parameter specifies whether to return only audit log entries $true: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are returned. -$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This is the default value. +$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md b/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md index d1f91cda9d..87a469ee90 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md @@ -57,7 +57,7 @@ Search-MessageTrackingReport [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -235,7 +235,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md index c468fec3d7..6c403ffeeb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md @@ -48,13 +48,13 @@ The Search-UnifiedAuditLog cmdlet is available in Exchange Online PowerShell. Yo If you want to programmatically download data from the Microsoft 365 audit log, we recommend that you use the Microsoft 365 Management Activity API instead of using the Search-UnifiedAuditLog cmdlet in a PowerShell script. The Microsoft 365 Management Activity API is a REST web service that you can use to develop operations, security, and compliance monitoring solutions for your organization. For more information, see [Management Activity API reference](https://learn.microsoft.com/office/office-365-management-api/office-365-management-activity-api-reference). -This cmdlet is available in Office 365 operated by 21Vianet, but it won't return any results. +This cmdlet is available in Office 365 operated by 21Vianet, but it doesn't return any results. The OutVariable parameter accepts objects of type ArrayList. Here's an example of how to use it: `$start = (Get-Date).AddDays(-1); $end = (Get-Date).AddDays(-0.5); $auditData = New-Object System.Collections.ArrayList; Search-UnifiedAuditLog -StartDate $start -EndDate $end -OutVariable +auditData | Out-Null` -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -74,7 +74,7 @@ Search-UnifiedAuditLog -StartDate "6/1/2023 8:00 AM" -EndDate "6/1/2023 6:00 PM" This example searches the unified audit log for all Exchange admin events from 8:00 AM to 6:00 PM on June 1, 2023. -**Note** If you use the same date for the StartDate and EndDate parameters, you need to include a timestamp; otherwise, no results will be returned because the date and time for the start and end dates will be the same. +**Note** If you use the same date for the StartDate and EndDate parameters, you need to include a timestamp; otherwise, no results are returned because the date and time for the start and end dates are the same. ### Example 3 ```powershell @@ -335,7 +335,7 @@ Accept wildcard characters: False The SessionCommand parameter specifies how much information is returned and how it's organized. This parameter is required if you want to retrieve more than the default limit of 100 results. Valid values are: -- ReturnLargeSet: This value causes the cmdlet to return unsorted data. By using paging, you can access a maximum of 50,000 results. This is the recommended value if an ordered result is not required and has been optimized for search latency. +- ReturnLargeSet: This value causes the cmdlet to return unsorted data. By using paging, you can access a maximum of 50,000 results. This is the recommended value if an ordered result is not required and is optimized for search latency. - ReturnNextPreviewPage: This value causes the cmdlet to return data sorted on date. The maximum number of records returned through use of either paging or the ResultSize parameter is 5,000 records. **Note**: Always use the same SessionCommand value for a given SessionId value. Don't switch between ReturnLargeSet and ReturnNextPreviewPage for the same session ID. Otherwise, the output is limited to 10,000 results. @@ -356,9 +356,9 @@ Accept wildcard characters: False > Applicable: Exchange Online, Exchange Online Protection -The SessionId parameter specifies an ID you provide in the form of a string to identify a command (the cmdlet and its parameters) that will be run multiple times to return paged data. The SessionId can be any string value you choose. +The SessionId parameter specifies an ID string to identify a command (the cmdlet and its parameters) that's run multiple times to return paged data. The SessionId can be any string value you choose. -When the cmdlet is run sequentially with the same session ID, the cmdlet will return the data in sequential blocks of the size specified by ResultSize. +When the cmdlet is run sequentially with the same session ID, the cmdlet returns the data in sequential blocks of the size specified by ResultSize. For a given session ID, if you use the SessionCommand value ReturnLargeSet, and then you use the SessionCommand value ReturnNextPreviewPage, the results are limited to 10,000 records. To have all 50,000 records available, always use the ReturnLargeSet value each time your run the cmdlet for the same session ID. diff --git a/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md index b1af8ec2d7..af84b61d3e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md +++ b/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md @@ -13,7 +13,7 @@ title: Send-TextMessagingVerificationCode # Send-TextMessagingVerificationCode ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Send-TextMessagingVerificationCode cmdlet to send a text messaging verification as part of configuring text message notifications on the mailbox. @@ -32,7 +32,7 @@ Send-TextMessagingVerificationCode [[-Identity] ] ## DESCRIPTION The Send-TextMessagingVerificationCode cmdlet generates a verification code and sends it to a user's mobile phone. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). This cmdlet returns an error if the user requests a verification code more than three times within a 24-hour period. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md index 080dc688ce..537e6dd15f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md @@ -52,7 +52,7 @@ Set-ADServerSettings [[-PreferredServer] ] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md index d4947a9cab..6c681e1ca8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md @@ -13,7 +13,7 @@ title: Set-AcceptedDomain # Set-AcceptedDomain ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-AcceptedDomain cmdlet to modify existing accepted domains in your organization. An accepted domain is any SMTP namespace for which an Exchange organization sends and receives email. @@ -42,7 +42,7 @@ Set-AcceptedDomain [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -166,7 +166,7 @@ Accept wildcard characters: False The DomainType parameter specifies the accepted domain type. Valid values are: -- Authoritative: This is the default value. Your organization is completely responsible for delivering email to recipients in the domain, and for generating non-delivery reports (also known as an NDRs, delivery system notifications, DSNs, or bounce messages) for unresolved recipients. +- Authoritative: This value is the default. Your organization is completely responsible for delivering email to recipients in the domain, and for generating non-delivery reports (also known as an NDRs, delivery system notifications, DSNs, or bounce messages) for unresolved recipients. - InternalRelay: This is a type of non-authoritative domain. Your organization receives email that's sent to recipients in the domain, but the messages are relayed to an external email system that's under your control. The external email system is responsible for generating NDRs for unresolved recipients. Use this value to treat messages that are sent to the domain as internal messages. - ExternalRelay: This is a type of non-authoritative domain that's available only in on-premises Exchange organizations. Your organization receives email that's sent to recipients in the domain, but the messages are relayed to an external email system that's completely outside of your control. The external email system is responsible for generating NDRs for unresolved recipients. @@ -212,7 +212,7 @@ This parameter is available only in on-premises Exchange. The MakeDefault parameter specifies whether the accepted domain is the default domain. Valid values are: $true or $false. -- $true: The accepted domain is the default domain. This is the default value for first accepted domain that's created in the organization. +- $true: The accepted domain is the default domain. This value is the default for first accepted domain that's created in the organization. - $false: The accepted domain isn't the default domain. This the default value for subsequent accepted domains. The default accepted domain is used in sender email addresses when the senders have only non-SMTP email addresses (for example, X.400 addresses). Non-SMTP email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. IMCEA encapsulation uses the default domain value in the SMTP email address. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md index 0f0c11f6da..aaedd38eb6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md @@ -31,7 +31,7 @@ Set-AccessToCustomerDataRequest -ApprovalDecision Your device has been blocked. "] +Set-ActiveSyncDeviceAutoblockThreshold -Identity "UserAgentChanges" BehaviorTypeIncidenceLimit 2 -BehaviorTypeIncidenceDuration 1440 -DeviceBlockDuration 1440 -AdminEmailInsert "Your device is blocked. "] ``` This example sets the autoblock threshold rule UserAgentChanges with several settings. It limits the number of accepted UserAgent changes to 2, specifies that the incidence duration is 1440 minutes and blocks the mobile device for 1440 minutes. Lastly, it inserts a message into the administrative email message sent to the user. ### Example 2 ```powershell -Set-ActiveSyncDeviceAutoblockThreshold -Identity "RecentCommands" BehaviorTypeIncidenceLimit 5 -BehaviorTypeIncidenceDuration 720 -DeviceBlockDuration 720 -AdminEmailInsert "Your device has been blocked. "] +Set-ActiveSyncDeviceAutoblockThreshold -Identity "RecentCommands" BehaviorTypeIncidenceLimit 5 -BehaviorTypeIncidenceDuration 720 -DeviceBlockDuration 720 -AdminEmailInsert "Your device is blocked. "] ``` This example sets the autoblock threshold rule RecentCommands with several settings. It limits the number of accepted RecentCommands changes to 5, specifies that the incidence duration is 720 minutes and blocks the mobile device for 720 minutes. Lastly, it inserts a message into the administrative email message sent to the user. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md index c315385640..d5222a900b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md @@ -13,7 +13,7 @@ title: Set-ActiveSyncMailboxPolicy # Set-ActiveSyncMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ActiveSyncMailboxPolicy cmdlet to apply a variety of Mobile Device mailbox policy settings to a server. You can set any of the parameters by using one command. @@ -90,7 +90,7 @@ With the Set-ActiveSyncMailboxPolicy cmdlet, you can set each parameter in a mai Some Microsoft Mobile Device mailbox policy settings require the mobile device to have specific built-in features that enforce these security and device management settings. If your organization allows all devices, you must set the AllowNonProvisionableDevices parameter to $true. This applies to devices that can't enforce all policy settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md index 3e8b02bfe3..c1e59f6d4b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md @@ -13,7 +13,7 @@ title: Set-ActiveSyncOrganizationSettings # Set-ActiveSyncOrganizationSettings ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-ActiveSyncOrganizationSettings cmdlet to set the Exchange ActiveSync settings for the organization. @@ -38,7 +38,7 @@ Set-ActiveSyncOrganizationSettings [[-Identity] ## DESCRIPTION The Set-ActiveSyncVirtualDirectory cmdlet configures a variety of settings on the virtual directory used for Exchange ActiveSync including security, authentication, and internal and external URL settings. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -148,7 +148,7 @@ Accept wildcard characters: False The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are: -- $true: Basic authentication is enabled. This is the default value. +- $true: Basic authentication is enabled. This value is the default. - $false: Basic authentication is disabled. ```yaml @@ -248,7 +248,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting. - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter. -- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. +- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server. ```yaml Type: MultiValuedProperty @@ -268,7 +268,7 @@ Accept wildcard characters: False The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are: -- $null: This is the default value. +- $null: This value is the default. - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter. ```yaml @@ -289,8 +289,8 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are: -- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value. -- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication. +- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default. +- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication. - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter. **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md index ad5d4f2c0d..3ca49ee585 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md @@ -13,7 +13,7 @@ title: Set-AddressBookPolicy # Set-AddressBookPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-AddressBookPolicy cmdlet to change the settings of an address book policy. @@ -37,7 +37,7 @@ Set-AddressBookPolicy [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -72,7 +72,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The AddressLists parameter specifies the address lists that will be used by mailbox users who are assigned this address book policy. This parameter accepts multiple values, which should be separated by a comma. +The AddressLists parameter specifies the address lists for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the address list. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. + +You can find the identify values of address lists by using the Get-AddressList cmdlet. ```yaml Type: AddressListIdParameter[] @@ -131,7 +139,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The GlobalAddressList parameter specifies the identity of the global address list (GAL) that will be used by mailbox users who are assigned this address book policy. You can specify only one GAL for each address book policy. +The GlobalAddressList parameter specifies the GAL for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the GAL. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can find the identify values of GALs by using the Get-GlobalAddressList cmdlet. + +You can specify only one GAL for each address book policy. ```yaml Type: GlobalAddressListIdParameter @@ -167,7 +183,15 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The OfflineAddressBook parameter specifies the identity of the offline address book (OAB) that will be used by mailbox users who are assigned this address book policy. You can specify only one OAB for each address book policy. +The OfflineAddressBook parameter specifies the OAB for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the OAB. For example: + +- Name +- Distinguished name (DN) +- GUID + +You can find the identify values of OABs by using the Get-OfflineAddressBook cmdlet. + +You can specify only one OAB for each address book policy. ```yaml Type: OfflineAddressBookIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md index bee9b693b5..72c8d4e3e6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md @@ -13,7 +13,7 @@ title: Set-AddressList # Set-AddressList ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-AddressList cmdlet to modify existing address lists. @@ -68,7 +68,7 @@ To create flexible filters that use any available recipient property and that ar You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md index 2039a6a6de..42c5b5bdfa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md @@ -13,7 +13,7 @@ title: Set-AdminAuditLogConfig # Set-AdminAuditLogConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-AdminAuditLogConfig cmdlet to configure the administrator audit logging configuration settings. @@ -44,11 +44,11 @@ When audit logging is enabled, a log entry is created for each cmdlet run, exclu The Set-AdminAuditLogConfig, Enable-CmdletExtensionAgent, and Disable-CmdletExtensionAgent cmdlets are logged when they're run regardless of whether administrator audit logging is enabled or disabled. -Administrator audit logging relies on Active Directory replication to replicate the configuration settings you specify to the domain controllers in your organization. Depending on your replication settings, the changes you make may not be immediately applied to all Exchange servers in your organization. +Administrator audit logging relies on Active Directory replication to replicate the configuration settings you specify to the domain controllers in your organization. Depending on your replication settings, the changes you make might not be immediately applied to all Exchange servers in your organization. -Changes to the audit log configuration may take up to 60 minutes to be applied on computers that have the Exchange Management Shell open at the time a configuration change is made. If you want to apply the changes immediately, close and reopen the Exchange Management Shell on each computer. +Changes to the audit log configuration might take up to 60 minutes to be applied on computers that have the Exchange Management Shell open at the time a configuration change is made. If you want to apply the changes immediately, close and reopen the Exchange Management Shell on each computer. -You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES @@ -151,7 +151,7 @@ This parameter is available only in on-premises Exchange. The AdminAuditLogEnabled parameter specifies whether administrator audit logging is enabled. Valid values are: -- $true: Administrator audit logging is enabled. This is the default value. +- $true: Administrator audit logging is enabled. This value is the default. - $false: Administrator audit logging is disabled. You must specify an administrator audit log mailbox before you enable logging. @@ -281,7 +281,7 @@ This parameter is available only in on-premises Exchange. The LogLevel parameter specifies whether additional properties should be included in the log entries. Valid values are: -- None: The CmdletName, ObjectName, Parameters (values), and the Caller, Succeeded and RunDate properties are included in log entries. This is the default value. +- None: The CmdletName, ObjectName, Parameters (values), and the Caller, Succeeded and RunDate properties are included in log entries. This value is the default. - Verbose: The ModifiedProperties (old and new) and ModifiedObjectResolvedName properties are also included in log entries. ```yaml @@ -327,7 +327,7 @@ This parameter is available only in on-premises Exchange. The TestCmdletLoggingEnabled parameter specifies whether test cmdlets (cmdlet names that begin with the verb Test) results are included in admin audit logging. Valid values are: - $true: Test cmdlets are included in admin audit logging. -- $false: Test cmdlets aren't included in admin audit logging. This is the default value. +- $false: Test cmdlets aren't included in admin audit logging. This value is the default. Test cmdlets can produce a large amount of information. As such, you should only enable logging of test cmdlets for a short period of time. @@ -351,7 +351,7 @@ This parameter is functional only in the cloud-based service. The UnifiedAuditLogIngestionEnabled parameter specifies whether to enable or disable the recording of user and admin activities in the Microsoft 365 audit log. Valid values are: -- $true: User and admin activities are recorded in the Microsoft 365 audit log, and admins can search the Microsoft 365 audit log. This is the default value. +- $true: User and admin activities are recorded in the Microsoft 365 audit log, and admins can search the Microsoft 365 audit log. This value is the default. - $false: User and admin activities aren't recorded in the Microsoft 365 audit log, and admins can't search the Microsoft 365 audit log. ```yaml