diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md index 14512499ab..9b7f139ea5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md @@ -66,7 +66,7 @@ Add-ADPermission [[-Identity] ] -Instance -ForestNam ## DESCRIPTION In Exchange Online, you need to run the New-AvailabilityConfig cmdlet before you run the Add-AvailabilityAddressSpace cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md index ccaca37c2f..7e7cef98c9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md @@ -32,7 +32,7 @@ Add-ContentFilterPhrase [-Phrase] -Influence ## DESCRIPTION The Add-ContentFilterPhrase cmdlet adds phrases to the Allow or Block phrases list. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md index 270c31ad74..8773c97f8a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md @@ -37,7 +37,7 @@ To add a Mailbox server to a DAG, the Mailbox server must be running the Windows To add the first server to a DAG and create a computer object for the DAG, the Exchange Windows Permissions security group must have the appropriate rights to add computer accounts to the domain. Alternatively, a computer account can be created and disabled prior to adding the server. Adding the first server to the DAG enables the computer account for the DAG. Thus, the account used for the task doesn't need permissions to add a computer account to the domain. If you're pre-creating the computer account, the name of the account must match the name for the DAG. For example, if the DAG is named DAG1, the computer account must be named DAG1. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md index b9bf4d3aa9..7b4aa8a16e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md @@ -32,7 +32,7 @@ Add-DistributionGroupMember [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md index 99df25b20e..a955e3dbaa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md @@ -36,7 +36,7 @@ You can add any registered Internet domain to the federated organization identif For more details, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md index c8cbb2af7c..8a81090517 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md @@ -44,7 +44,7 @@ Add-GlobalMonitoringOverride [-Identity] -ItemType -AccessRights ## DESCRIPTION To modify the permissions that are assigned to the user on a mailbox folder, use the Set-MailboxFolderPermission cmdlet. To remove all permissions that are assigned to a user on a mailbox folder, use the Remove-MailboxFolderPermission cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md index 893d646309..e3d74dcb35 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md @@ -67,7 +67,7 @@ Add-MailboxPermission [[-Identity] ] -Instance [!NOTE] > You can use this cmdlet to add a maximum of 500 permission entries (ACEs) to a mailbox. To grant permissions to more than 500 users, use security groups instead of individual users for the User parameter. Security groups contain many members, but only count as one entry. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md index 29a7f33b0f..ae6c6b0762 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md @@ -54,7 +54,7 @@ You can only add a role entry to a management role if the role entry exists in t For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md index 58bb304fa4..7cc7bfea5a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md @@ -58,7 +58,7 @@ Add-PublicFolderAdministrativePermission [-Identity] - ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md index 67c5796bd3..8bfbcd9ac9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md @@ -31,7 +31,7 @@ Add-PublicFolderClientPermission [-Identity] -AccessRi ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md index e6aa528fc3..e1708d0560 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md @@ -31,7 +31,7 @@ Add-RecipientPermission [-Identity] -AccessRights -StartTime ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md index 51471eb69b..a700deba46 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md @@ -39,7 +39,7 @@ In on-premises Exchange, if the role group is a linked role group, you can't use 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 article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md index 868e0d75a3..d0ca5ec943 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md @@ -39,7 +39,7 @@ Add-ServerMonitoringOverride [-Identity] -ItemType -Links ## DESCRIPTION The Clear-TextMessagingAccount cmdlet clears all of a user's text messaging settings, including communication and notification settings. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md index 2c69601d73..83845e82d0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md +++ b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md @@ -34,7 +34,7 @@ The Compare-TextMessagingVerificationCode cmdlet returns the value true if the c When text messaging notifications are enabled on a mailbox, you can configure calendar notifications, voice mail notifications, and email notifications using an inbox rule. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md index 47da89c99b..a8ed9f625e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md @@ -46,7 +46,7 @@ When the finalization process is complete, you can remove the batch by using the If a migration batch has a status of Completed with Errors, you can re-attempt to finalize the failed users. In Exchange Online, use the Start-MigrationBatch cmdlet to retry migration for failed users. In Exchange 2013 or Exchange 2016, use the Complete-MigrationBatch to retry these failed users. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md index cdf4d75bf3..8d4f60535b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md @@ -132,7 +132,7 @@ Use the Remove-Mailbox cmdlet to: - Keep the mailbox in the disabled state before it's permanently deleted, subject to the deleted mailbox retention period (except if you use the Permanent or StoreMailboxIdentity parameters, which immediately deletes the mailbox from the database). - Remove the user account. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md index c071bd6c30..eaa566a1f2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md @@ -45,7 +45,7 @@ Delete-QuarantineMessage -Identity ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md index cec4891367..55e5a4c0fd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md @@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md index 1de3a4b7fd..c525408a82 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md @@ -29,7 +29,7 @@ Disable-AddressListPaging [-Confirm] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md index 7660a78413..3773a17e34 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md @@ -29,7 +29,7 @@ Disable-AntiPhishRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md index ce690bd262..c176a7102c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md @@ -35,7 +35,7 @@ The Disable-App cmdlet requires that the specified app has already been installe For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md index a61981d05a..1ba7f512d3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md @@ -34,7 +34,7 @@ Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and When you disable a cmdlet extension agent, the agent is disabled for the entire organization. When an agent is disabled, it's not made available to cmdlets. Cmdlets can no longer use the agent to perform additional operations. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md index 99d3dee368..81854c040f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md @@ -33,7 +33,7 @@ Disable-DistributionGroup [-Identity] ## DESCRIPTION The Disable-DistributionGroup cmdlet mail-disables existing mail-enabled security groups and distribution groups by removing the email attributes that are required by Exchange. Mail-disabled groups are invisible to the \*-DistributionGroup cmdlets (with the exception of Enable-DistributionGroup). All groups (mail-enabled or not) are visible to the Get-Group and Set-Group cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md index 920747bf5b..41c64fcc70 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md @@ -31,7 +31,7 @@ Disable-DnssecForVerifiedDomain [-DomainName] ## DESCRIPTION For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md index 2dd8ae99b5..0a8a006a20 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md @@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md index 78dae763c9..bc31eef052 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md @@ -29,7 +29,7 @@ Disable-HostedContentFilterRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md index 4ebd303216..4b73d2012f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md @@ -29,7 +29,7 @@ Disable-HostedOutboundSpamFilterRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md index bb1c87a9ed..799ceca694 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md @@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md index fc46a1d3e0..dde3d20511 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md @@ -35,7 +35,7 @@ Disable-InboxRule [-Identity] ## DESCRIPTION When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md index 6fed3d1538..e8dfd114a9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md @@ -36,7 +36,7 @@ The Disable-JournalArchiving cmdlet removes the mail user and converts the journ In hybrid organizations that use DirSync, this cmdlet doesn't remove the mail user. Removal of the mail user is handled by DirSync. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md index b15185faa4..c2e684786c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md @@ -32,7 +32,7 @@ Disable-JournalRule -Identity ## DESCRIPTION You can enable or disable specific journal rules in your organization at any time using the Disable-JournalRule and Enable-JournalRule cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md index 451238f746..66d3cc5e91 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md @@ -33,7 +33,7 @@ Disable-MailContact [-Identity] ## DESCRIPTION The Disable-MailContact cmdlet mail-disables existing mail contacts by removing the email attributes that are required by Exchange. Mail-disabled contacts are invisible to the \*-MailContact cmdlets (with the exception of Enable-MailContact). All contacts (mail-enabled or not) are visible to the Get-Contact and Set-Contact cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md index fe5bfbe28b..19e6f06e0d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md @@ -31,7 +31,7 @@ Disable-MailPublicFolder [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md index 7b7effd7ff..3bc30aea90 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md @@ -34,7 +34,7 @@ Disable-MailUser [-Identity] ## DESCRIPTION The Disable-MailUser cmdlet mail-disables existing mail users by removing the email attributes that are required by Exchange. Mail-disabled users are invisible to the \*-MailUser cmdlets (with the exception of Enable-MailUser). All users (mail-enabled or not) are visible to the Get-User and Set-User cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md index 4edb38bb6f..ffd3bd0dd9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md @@ -79,7 +79,7 @@ The Disable-Mailbox cmdlet also performs the clean-up task on the individual mai Under normal circumstances, a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. However, if the mailbox was disabled or removed while the Exchange Information Store service was stopped, or if it was disabled or removed by an external means other than Exchange management interfaces, the status of the mailbox object in the Exchange mailbox database isn't marked as disconnected. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md index 7082e77db1..69bd293167 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md @@ -70,7 +70,7 @@ Disable-MailboxQuarantine -Server ## DESCRIPTION Mailboxes are quarantined when they affect the availability of the mailbox database. Typically a software fix from Microsoft is required before releasing a mailbox from quarantine. If a fix isn't deployed before releasing the mailbox, the quarantine on the mailbox is re-enabled if the condition recurs. The default quarantine duration is 24 hours. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md index 8127d10f40..3135c19f76 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md @@ -30,7 +30,7 @@ Disable-MalwareFilterRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md index f6ff4cfdb9..cff0f8762f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md @@ -29,7 +29,7 @@ Disable-MetaCacheDatabase -Server ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md index f34bfa0d4a..2be4362dad 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md @@ -46,7 +46,7 @@ When you run this cmdlet, it can take as long as an hour for the settings to bec After the Client Access server is disabled for Outlook Anywhere, you might want to remove the RPC over HTTP proxy Windows networking component. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md index 1b77ff5b57..f294454b97 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md @@ -36,7 +36,7 @@ Outlook protection rules are administrator-created rules applied before a user s 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 article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md index 355b7fb189..45364575b0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md @@ -30,7 +30,7 @@ Disable-PushNotificationProxy [-Confirm] ## DESCRIPTION The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Microsoft 365 to Outlook on the web for devices on the user's device. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md index b6ec895fe5..ce5291ee76 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md @@ -47,7 +47,7 @@ Directory synchronization must be configured correctly for a mailbox to be remov - If you are deprovisioning a cloud mailbox and its associated online archive, you must first disable the online archive with the command `Disable-RemoteMailbox -Archive` and then perform a directory synchronization prior to disabling the remote mailbox. Attempting to disable both the online archive and cloud mailbox without a sync between them might result in an ArchiveGuid mismatch and validation error. - Due to the current service architecture, you need to convert shared mailboxes to user mailboxes prior to running the Disable-RemoteMailbox cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md index a55a45da61..95727eff23 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md @@ -29,7 +29,7 @@ Disable-ReportSubmissionRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md index 10fba35caf..ee21f6286e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md @@ -31,7 +31,7 @@ Disable-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 article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md index e9ce882e5f..24f062ac31 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md @@ -31,7 +31,7 @@ Disable-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 article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md index 3b3cacc2ab..66799f5106 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md @@ -32,7 +32,7 @@ Disable-ServiceEmailChannel [-Identity] ## DESCRIPTION The Disable-ServiceEmailChannel cmdlet deletes the receive folder in the user's mailbox under the root folder. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md index 3ee2297558..9c28890fee 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md @@ -31,7 +31,7 @@ Disable-SmtpDaneInbound [-DomainName] ## DESCRIPTION For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md index ba335e644f..5049dce174 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md @@ -31,7 +31,7 @@ Disable-SweepRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md index a70c5a9d46..675098e0b9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md @@ -31,7 +31,7 @@ Disable-TransportAgent [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md index 2486bc58e6..72a6cd1f6e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md @@ -32,7 +32,7 @@ Disable-TransportRule [-Identity] ## DESCRIPTION To enable rules that are disabled, use the Enable-TransportRule cmdlet. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md index 6d848275c1..55d93cb30b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md @@ -34,7 +34,7 @@ The Disable-UMAutoAttendant cmdlet disables an existing UM auto attendant that's After this task is completed, the UM auto attendant is disabled and doesn't accept incoming calls. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md index 0d7ed908bd..83930d80a6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md @@ -35,7 +35,7 @@ The Disable-UMCallAnsweringRule cmdlet disables the call answering rule by modif When the call answering rule is created, you should disable the call answering rule when you're setting up conditions and actions. This prevents the call answering rule from being processed when an incoming call is received until you've correctly configured the call answering rule. 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 article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md index db54c5c88d..99d701cbe6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md @@ -33,7 +33,7 @@ Disable-UMIPGateway [-Identity] ## DESCRIPTION The status variable for a UM IP gateway can be used to enable or disable call answering destined for the IP gateway. The Disable-UMIPGateway cmdlet disables a UM IP gateway in Active Directory by modifying its status variable. After this task is completed, the UM IP gateway no longer answers incoming calls or makes outgoing calls. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md index ae4ee00bda..de6a75d801 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md @@ -34,7 +34,7 @@ Disable-UMMailbox [-Identity] ## DESCRIPTION After the mailbox is disabled for Unified Messaging, the user can no longer use the UM features that are included in Microsoft Exchange and the Microsoft Exchange Unified Messaging service no longer handle calls for the associated extension number. The mailbox continues to function normally for all other operations that are unrelated to Unified Messaging. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md index 4136f0b40f..090daef048 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md @@ -40,7 +40,7 @@ After this task is completed, the UM server can no longer: - Be used to manage UM-enabled mailboxes - Be queried when a diagnostic task is used -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md index 1dff826b33..f3f2b6c64a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md @@ -42,7 +42,7 @@ After this task is completed, the UM server can no longer: - Be used to manage UM-enabled mailboxes. - Be queried when a diagnostic task is used. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md index 2ad03daf97..27e96b01a7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md +++ b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md @@ -30,7 +30,7 @@ Dismount-Database [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md index f417804b7e..0ec91c54ca 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md +++ b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md @@ -47,7 +47,7 @@ The Dump-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely The Dump-ProvisioningCache cmdlet displays a list of the Windows PowerShell provisioning cache keys. Use the value of these cache keys with the Reset-ProvisioningCache cmdlet to reset provisioning cache data. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md index 543c960817..58eda1bbbf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md @@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md index 78747343ca..bb39c286cd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md @@ -31,7 +31,7 @@ Enable-AddressListPaging [-Confirm] ## DESCRIPTION The Enable-AddressListPaging cmdlet creates the Address List container in Active Directory. Recipient cmdlets, such as Get-Recipient, use the information written to the container to quickly retrieve recipient data. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md index 3bb397ee11..9cd62cc3f6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md @@ -29,7 +29,7 @@ Enable-AntiPhishRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md index 6e033b80c9..5379a54dbe 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md @@ -35,7 +35,7 @@ The Enable-App cmdlet requires that the specified app has already been installed For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md index bd2048d7e4..fa6ec7a67a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md @@ -36,7 +36,7 @@ When you enable a cmdlet extension agent, the agent is run on every Exchange ser Before you enable agents, be sure that you're aware of how the agent works and what effect the agent can have on your organization. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md index 8ef9efc43b..3c3963ce8a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md @@ -35,7 +35,7 @@ Enable-DistributionGroup [-Identity] ## DESCRIPTION The Enable-DistributionGroup cmdlet mail-enables existing universal security groups and universal distribution groups by adding the email attributes that are required by Exchange. Mail-enabled security groups and distribution groups are visible to the other \*-DistributionGroup cmdlets and to the \*-DistributionGroupMember cmdlets. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md index e081e366bc..d538718ea9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md @@ -33,7 +33,7 @@ The output of this cmdlet is an MX record value that you need to add to DNS for For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md index 501ef067ae..a71a9634b9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md @@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md index 903cb865ed..1d42298bb7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md @@ -57,7 +57,7 @@ There are many factors to consider when you configure certificates for Transport Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md index 981b7014dd..3bed2ac086 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md @@ -29,7 +29,7 @@ Enable-HostedContentFilterRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md index 57e3320dfa..4db53e86eb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md @@ -29,7 +29,7 @@ Enable-HostedOutboundSpamFilterRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md index 3a69a851a2..faceb49a5d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md @@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md index 59286152ae..6c3673325b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md @@ -35,7 +35,7 @@ Enable-InboxRule [-Identity] ## DESCRIPTION When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md index 9f5e90cc65..244d0391ce 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md @@ -32,7 +32,7 @@ Enable-JournalRule [-Identity] ## DESCRIPTION You can enable or disable specific journal rules in your organization at any time using the Enable-JournalRule and Disable-JournalRule cmdlets. For more information, see [Journaling in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/journaling/journaling). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md index 685fc2057a..2b9a9f8fda 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md @@ -39,7 +39,7 @@ Enable-MailContact [-Identity] -ExternalEmailAddress ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md index d102ab1df9..ceb3f644e4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md @@ -55,7 +55,7 @@ The Enable-MailUser cmdlet mail-enables existing users by adding the email attri Mail users have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. Email messages sent to mail users are delivered to the specified external email address. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md index 25c3826181..4ca227e302 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md @@ -273,7 +273,7 @@ The Enable-Mailbox cmdlet mailbox-enables existing users, public folders, or Ine When mailbox-enabling an existing user, beware of non-supported characters in the user account or Name property. If you don't specify an Alias value when you mailbox-enable the user, Exchange converts all non-supported characters to question marks (?). To avoid question marks in the Alias, verify that the user account and Name properties have only supported ASCII or Unicode characters or specify an Alias value when you mailbox-enable the user. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md index 867711e84f..d539c0c031 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md @@ -54,7 +54,7 @@ Enable-MailboxQuarantine -Database -StoreMailboxIdentity < ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md index af974853e5..c8d9f1432e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md @@ -30,7 +30,7 @@ Enable-MalwareFilterRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md index dfaa1c8861..860be7f17a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md @@ -29,7 +29,7 @@ Enable-MetaCacheDatabase -Server ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md index bd23fa403a..92019b3cd6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md @@ -43,7 +43,7 @@ You are only required to run the Enable-OrganizationCustomization cmdlet once in Whether or not this command is previously run in an organization is available in the IsDehydrated property of the Get-OrganizationConfig cmdlet: False ($false) = the command has already been run; True ($true) = the command has never been run. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md index 2297a39956..300964c824 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md @@ -57,7 +57,7 @@ When you run this cmdlet, it can take as long as an hour for the settings to bec For more information about the different authentication methods that you can see in this article, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md index c9d18eab91..46b914e2ec 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md @@ -34,7 +34,7 @@ Enable-OutlookProtectionRule [-Identity] ## DESCRIPTION Outlook protection rules are used to automatically Information Rights Management (IRM)-protect messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To rights-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md index 6cf4a5c65c..79a0e49acc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md @@ -34,7 +34,7 @@ Enable-PushNotificationProxy [-Confirm] ## DESCRIPTION The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Microsoft 365 to Outlook on the web for devices on the user's device. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md index 1f12234ec2..26f49783c0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md @@ -102,7 +102,7 @@ Directory synchronization must be configured correctly for a mailbox to be creat The policies that you apply to recipients in the on-premises Exchange organization, such as Unified Messaging or compliance policies, aren't applied to mailboxes in the service. You must configure policies in the service if you want policies to be applied to recipients in the service. -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md index 29852d3479..8cb09e07a1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md @@ -29,7 +29,7 @@ Enable-ReportSubmissionRule [-Identity] ``` ## DESCRIPTION -You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md index 0cd9ec3748..352b045c45 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md @@ -31,7 +31,7 @@ Enable-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 article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). +You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). ## EXAMPLES